761 replies to this topic

[Memnoch73]

Any chance there will be any love for the Bionic?

 

Nope.. Feel free to read the original post.

[SceneZombie]

So now that the bootloader is unlocked. After rooting and installing a CM/AOSP/AOKP ROM when they come out in daily driver form for method then editing the build.prop, I take it Google Wallet will finally (in theory at least) work? Like full on install, open, run, and function work?

[altspeed]

Any chance there will be any love for the Bionic?

The bionic gets more love than all other moto devices combined from the bionic community. The bootloader won't ever be unlocked though. It s hardware locked permanently.

sliced with my RAZR MAXX via tapa2

[vasy]

Man... you are simply best.  I tried lots of rooting method on my chinese made 5.8 inch screen running android jelly bean.  None of the method worked for me, after long search I saw this thread.  As it mentioned, initially I thought this method will work only for Motorola but it worked on my device too.  Thanks a ton and safing my time. 

[livinginkaos]

Man... you are simply best.  I tried lots of rooting method on my chinese made 5.8 inch screen running android jelly bean.  None of the method worked for me, after long search I saw this thread.  As it mentioned, initially I thought this method will work only for Motorola but it worked on my device too.  Thanks a ton and safing my time. 

What is the device? It would benefit others to know.

[hiveminded462]

i tried to run the root exploit but its says adb is not reconized as an internal or external command, operable program or batch file. can anyone help ?

[amd1361]

Hello there
After trying hard and reading a lot of forums i failed to root my asus memopad 7 in ubuntu.
The problem is related to "" BUS ERROR ""

Here is what I did :
-------------------------------------------------------------------------------------------------------------------------------------------
amd1361@amd1361-desktop:~/Desktop/asus$ $adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
amd1361@amd1361-desktop:~/Desktop/asus$
amd1361@amd1361-desktop:~/Desktop/asus$ echo "[*] Device found."[*] Device found.
amd1361@amd1361-desktop:~/Desktop/asus$
amd1361@amd1361-desktop:~/Desktop/asus$ echo "[*] Pushing exploit..."[*] Pushing exploit...
amd1361@amd1361-desktop:~/Desktop/asus$ $adb push pwn /data/local/tmp/pwn
5737 KB/s (1283460 bytes in 0.218s)
amd1361@amd1361-desktop:~/Desktop/asus$ $adb shell chmod 755 /data/local/tmp/pwnamd1361@amd1361-desktop:~/Desktop/asus$
amd1361@amd1361-desktop:~/Desktop/asus$ echo "[*] Pushing root tools..."[*] Pushing root tools...
amd1361@amd1361-desktop:~/Desktop/asus$ $adb push su /data/local/tmp/su
5532 KB/s (91980 bytes in 0.016s)
amd1361@amd1361-desktop:~/Desktop/asus$ $adb push busybox /data/local/tmp/busybox
5787 KB/s (1867568 bytes in 0.315s)
amd1361@amd1361-desktop:~/Desktop/asus$ $adb install Superuser.apk
5979 KB/s (969701 bytes in 0.158s)
pkg: /data/local/tmp/Superuser.apk
Success
amd1361@amd1361-desktop:~/Desktop/asus$
amd1361@amd1361-desktop:~/Desktop/asus$ echo "[*] Rooting phone..."[*] Rooting phone...
amd1361@amd1361-desktop:~/Desktop/asus$ $adb shell /data/local/tmp/pwn
[+] This may take a few minutes.
Bus error
amd1361@amd1361-desktop:~/Desktop/asus$
amd1361@amd1361-desktop:~/Desktop/asus$ echo "[*] Cleaning up..."[*] Cleaning up...
amd1361@amd1361-desktop:~/Desktop/asus$ $adb shell rm /data/local/tmp/pwn
amd1361@amd1361-desktop:~/Desktop/asus$ $adb shell rm /data/local/tmp/su
amd1361@amd1361-desktop:~/Desktop/asus$ $adb shell rm /data/local/tmp/busybox
amd1361@amd1361-desktop:~/Desktop/asus$
amd1361@amd1361-desktop:~/Desktop/asus$ echo "[*] Exploit complete. Press enter to reboot and exit."[*] Exploit complete. Press enter to reboot and exit.
amd1361@amd1361-desktop:~/Desktop/asus$ read -n 1
amd1361@amd1361-desktop:~/Desktop/asus$ adb reboot
amd1361@amd1361-desktop:~/Desktop/asus$ $adb kill-server
-------------------------------------------------------------------------------------------------------------------------------------------
When I run adb devices the following message appears:

amd1361@amd1361-desktop:~/Desktop/asus$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
QTCYFV40E3050332E device

Please help me if i can do anything with it or else lets report that this method doesn't work on asus me172v
Thanks

[cmh714]

i tried to run the root exploit but its says adb is not reconized as an internal or external command, operable program or batch file. can anyone help ?

Sounds like your not in the correct directory/folder to run the utility. You need to be in the same folder where you extracted all the files in order to work.

[SamuriHL]

No, it sounds like they're running it from the zip.  The files need to be extracted to a folder and run from the folder.

[hiveminded462]

alright it worked thanks a lot samuriHL

[kadeo666]

My wife got the latest 4.1.2 update early through motorola and only kept partial root on her RAZR M.  I just used motochopper and got full root back with no problems as of yet.  Thanks for helping us get back the ability to do as we please with our own device

[italyguy01]

How can the Bionic be hardware locked when it was just a software update?   There has to be something someone can do?

[SamuriHL]

Guys, this root exploit will not work on the OMAP hardware.  Let's take the Bionic chatter elsewhere.  Thank you.

[Kawapowa]

Thank you for this amazing tool. I was going crazy trying to get Motofail to work (original I used to root last year). This tool made it a lot easier. Worked on the first attempt. I was about to go insane without my wifi tether.

[wtaylor810]

Does this work for XT897 - Photon Q?  Ran the file and said it was good to go, Superuser is there but when opened says needs to update.  Unfortunately it fails to do so.  Rootchecker shows Not Rooted.    I've tried the Moto2fail method as well but can't get the phone to generate a bug report with "Vol+ & Power"  fml.  Any help is appreciated.  I guess if this requires JB then I am SOL.  Be that the case can anyone tell me how to trigger a bug report for the moto2fail method?

[shayneglasgow]

what do i do after successful root?

[mmb27]

How long does it take for the batch file to run? I've been sitting at the same line *daemon started successfully* for 40 minutes now. My phone is in debugging and plugged in USB.

 

Make sure once your phone is connected you click on the open files, otherwise it will just sit after the daemon started successfully, I had the same problem, but once I opened the files folder it worked perfectly.

 

Thank you very much for your hard work finding the exploits to allow root. 

[Trylek09]

I just wanted to confirm:

 

Did 4.1.2 Update this morning and broke my root. Re-rooted with motochooper successfully. Ran this exploit and unlocked my bootloader for the first time. 

 

Thanks for the exploits! Its nice to see on the other forums (like Droidlife) where people are being laughed it for saying "its impossible"

[Trylek09]

I just wanted to confirm:

 

Did 4.1.2 Update this morning and broke my root. Re-rooted with motochooper successfully. Ran this exploit and unlocked my bootloader for the first time. 

 

Thanks for the exploits! Its nice to see on the other forums (like Droidlife) where people are being laughed it for saying "its impossible"

[dontmindme]

so, I used the tool on my at&t atrix hd, because after the 4.1 update ota root keeper didn't save the root to jelly bean (had superuser, but no root prompts)

This tool claimed complete success, yet now I have two superusers (one with blue and white #, other with pirate android head). problem is, still no root prompt, and the binaries appear out of date (3.0.3.2). the phone is essentially unrooted because of no prompts (however, previously when there were apps associated with superuser, they still worked, i only had problems with new prompts)

 

what can I do to fix this? does anyone know what happened? I would greatly appreciate any help. If you need more info, feel free to ask.