Related
I have done the one step root and it doesnt seem to work. I go to superuser permissions and it just force closes. This phone was rooted before perfectly fine with the same method. Even SetCPU doesnt open. Its always that dumb superuser force close.
EDIT: I dont have any one click root errors or any other errors while in samsung recovery. It said it applied the update when I go to reinstall packages. No errors whatesoever.
EDIT: I tried the 1.5.5 and it just gets stuck in the loop and says to disable usb debugged. I unplugged phone and disabled usb debugging but when I do that it gets stuck on waiting for device.
Have you used Z4root its not on market anymore but here is a link for it
http://www.4shared.com/file/HvJ7Anrq/z4root130.htm
Sent from my SGH-T959 using XDA App
Double post sorry
you can also use the OCLF app to root, thats what i always use
It worked with z4root but now how do I flash my cyanogenmod on it? I did the install rom from sd card and it took me to samsung recovery.
Eric-1987 said:
It worked with z4root but now how do I flash my cyanogenmod on it? I did the install rom from sd card and it took me to samsung recovery.
Click to expand...
Click to collapse
You have to install clockworkmod, then click reboot to recovery, click install from packages, then should be good (if it doesn't go to clockworkmod after that, reboot, and repeat). I have rooted several of these bad boys for co-workers the last couple weeks, and found clockworkmod didn't always take first time through as it does on other devices I have modded.
I flashed the galaxy s cm6.1.2 beta 1 and it gets stuck on boot screen and says Galaxy S GTI9000. I cant get to recovery by holding the volume key up. I dont know what to do now.
I have recently updated to the new jb ota (which i Iove I might add) but I'm having problems re rooting. Stupid as I am, I never temporarily unrooted with root keeper. So I updated and of coarse lost root. I am having the worst trouble rerooting. I downloaded an updated version of the su and superuser.apk and tried to replace them in motofail and it didn't work still. It just says "daemon not running. Starting it now" then the cmd promt does nothing. I even tried removing the su in system bin and tried tried to remove superuser.apk and it didn't work. I don't have too much experience using adb so if there's another way to solve this it would be greatly appreciated. Otherwise, I'm so stuck! Thanks for your responses
got the exploit to start running again because i forgot to enable usb debugging >.< but this is what comes up.
[*] Motofail2Go: Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Atrix HD, Photon Q, Razr M, and Razr i
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Installing fake package...
2075 KB/s (0 bytes in 564403.000s)
pkg: /data/local/tmp/Sudoku.apk
Failure [INSTALL_FAILED_UID_CHANGED]
[*] Preparing for exploit...
2378 KB/s (0 bytes in 380532.000s)
1912 KB/s (0 bytes in 1468798.000s)
1823 KB/s (0 bytes in 1867568.001s)
2006 KB/s (0 bytes in 64208.000s)
run-as: Package 'com.motorola.bug2go' is unknown
[*] Please trigger a bugreport on your phone by pressing
[*] Volume Up + Power simultaneously. If successful, your device
[*] will vibrate. Make sure this vibration is distinct from the
[*] vibration that occurs when you turn the volume all the way
[*] down. Press enter once you have successfully triggered a
[*] bugreport.
Press any key to continue . . .
[*] Getting root...
[*] This may take a minute or two.
[-] Exploit failed.
[*] Cleaning up...
Failure
[*] Exploit complete!
[*] Press any key to reboot and exit.
Press any key to continue . . .
im sooo lost!
If I remember correctly, if you are getting the "'com.motorola.bug2go' is unknown" part, it means you need to do a wipe (both data and cache) in recovery, and try again. That fixed it for me after I flashed. You might also need an updated version of moto2fail for JB: www dot droidrzr.com/index.php/topic/5151-root-for-droid-razr-m/
However, not sure on the other failure (INSTALL_FAILED_UID_CHANGED).
ChuckLezz said:
If I remember correctly, if you are getting the "'com.motorola.bug2go' is unknown" part, it means you need to do a wipe (both data and cache) in recovery, and try again. That fixed it for me after I flashed. You might also need an updated version of moto2fail for JB: www dot droidrzr.com/index.php/topic/5151-root-for-droid-razr-m/
However, not sure on the other failure (INSTALL_FAILED_UID_CHANGED).
Click to expand...
Click to collapse
I did a factory reset twice and it still won't work. It completes the exploit successfully and gives me super user but no root when trying to verify with root checker ;(
EDIT
got it to work. I was having issues with bug report.
Sent from my XT907 using xda app-developers app
I'm having the exact same problem. What exactly did you do to get it to work? I was rooted, then "unrooted" to get the OTA Jellybean update. Now I can't root.
Any help is appreciated.
- Sonny
jarzy00 said:
I did a factory reset twice and it still won't work. It completes the exploit successfully and gives me super user but no root when trying to verify with root checker ;(
EDIT
got it to work. I was having issues with bug report.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
yeah I cant get it to work .... Bugreport just wont happen ... Thinking about going back to ICS and taking the OTA after I unroot.
Weirdly enough it did succesfully complete the motofail2 but no root was acquired.
Are you guys mounting the phone as MTP? or you do get the option to mount as mass storage?
Also I am having trouble booting into recovery:
after I get the android with the open chest image with the "!", nothing happens, and no options are displayed, therefore I cant clean the cache.
How I got mine working again was replacing the su and superuser.apk files in the exploit and running the script again. Except this time, its really hard to get the bug report to work. Took me 6 tries. U need to wait for a second or third vibrate during this process. If ur phone vibrates once it will not work. As for khalilcr, I'm having the issue with recovery as well. Pressing both up and down in recovery won't work but it does if you wait like 10 seconds then try again. Try that and see if it works. Oh also I was mounted as MTP and it worked. Don't have the mass storage option available anymore.
Sent from my XT907 using xda premium
Confusion
jarzy00 said:
How I got mine working again was replacing the su and superuser.apk files in the exploit and running the script again. Except this time, its really hard to get the bug report to work. Took me 6 tries. U need to wait for a second or third vibrate during this process. If ur phone vibrates once it will not work. As for khalilcr, I'm having the issue with recovery as well. Pressing both up and down in recovery won't work but it does if you wait like 10 seconds then try again. Try that and see if it works. Oh also I was mounted as MTP and it worked. Don't have the mass storage option available anymore.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I am downloading the updates for my RAZR M to JB right now, but trying to keep root...should I install rootkeeper or not? (By "downloading" I mean I am manually running it with the ZIP files). I have root on 4.0.4 but I am unsure of whether I should be keeping root with a rootkeeper, or trying to root it freshly once the update to JB finishes....clarification, please?
Sooo, sorry if I ask a dumb question here, but what did you replace the su and superuser.apk files with??
I also can't get into recovery...same situation. Up/down arrow and Power gets me the menu, but if I don't select "Recovery" or something real fast it will boot normally on its own. If I do manage to select Recovery, I get the red triangle out of the droid's chest image.
Any further help is much appreciated!
jarzy00 said:
How I got mine working again was replacing the su and superuser.apk files in the exploit and running the script again. Except this time, its really hard to get the bug report to work. Took me 6 tries. U need to wait for a second or third vibrate during this process. If ur phone vibrates once it will not work. As for khalilcr, I'm having the issue with recovery as well. Pressing both up and down in recovery won't work but it does if you wait like 10 seconds then try again. Try that and see if it works. Oh also I was mounted as MTP and it worked. Don't have the mass storage option available anymore.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
http://androidsu.com/superuser/ go there and download the 3.1.3 arm signed zip. They have the 2 replacement files then open up the exploit and simply replace them.
Sent from my XT907 using xda premium
Tanko Risch said:
I am downloading the updates for my RAZR M to JB right now, but trying to keep root...should I install rootkeeper or not? (By "downloading" I mean I am manually running it with the ZIP files). I have root on 4.0.4 but I am unsure of whether I should be keeping root with a rootkeeper, or trying to root it freshly once the update to JB finishes....clarification, please?
Click to expand...
Click to collapse
Either or will do but I did hear root keeper works but when I did it I forgot to temporarily unroot lol so try it out.
Sent from my XT907 using xda premium
Ok, so, because bricking my phone would be disastrous, I refresh all the system apps, run the rootkeeper, run the manual update, then I should be good?
Sent from my XT907 using xda app-developers app
You da man! That worked. Oddly enough, I had to re-check the USB Debugging box because it somehow manage to uncheck itself. And you're right, the vol-up/power for the bug report is hard to get. For those reading this, you'll know the bug report works when you get 3 really short but fast vibrations. I had to volume down all the way a couple times.
Thanks again!
jarzy00 said:
http://androidsu.com/superuser/ go there and download the 3.1.3 arm signed zip. They have the 2 replacement files then open up the exploit and simply replace them.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Hey Lostpilot, could you give a review of the steroids you took in rooting? Namely, the ICS you came from, were you root from there? Also, (noob question, sorry) when the whole process is finished, is any data lost? Sorry for being so noobish, I'm brand new to Android
Sent from my XT907 using xda app-developers app
Glad it worked out for ya and yes tanko that should work just fine. If not, u can always re run the exploit script and do it that way.
Sent from my XT907 using xda premium
Ummm, yeah...steroids? Not sure what you're asking! But, I was on the OTA Jellybean ROM. I was on ICS, but rooted it. Then had to un-root it to get the OTA JB ROM to work. After that, I couldn't get it to re-root. Because I did a factory reset, I lost all my apps, but I backed everything up in Titanium Backup before I started. Also did an export of my contacts to a vCard on my SD card.
Basically, I am starting over in configuring this thing...but at least I'm rooted.
Tanko Risch said:
Hey Lostpilot, could you give a review of the steroids you took in rooting? Namely, the ICS you came from, were you root from there? Also, (noob question, sorry) when the whole process is finished, is any data lost? Sorry for being so noobish, I'm brand new to Android
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok, I am sorry, typo; "steps" to "steroids". I'll be running the upgrade from rooted ICS to JB with rootkeeper installed, if I don't post my success in an hour, then we know what process shouldn't be taken xD
Sent from my XT907 using xda app-developers app
---------- Post added at 11:16 PM ---------- Previous post was at 10:42 PM ----------
Can't get this to work; thought I copied the full set of system apps back in, but Android can see some changes still.
Sent from my XT907 using xda app-developers app
OK I read your post I'm in same situation here did the ran batch program to root phone said exploit complete super user is installed but it is not rooted so what is the best way to remove super user if obviously not rooted ? So I can run the rooting process again?
Sent from my XT907 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:16 AM ----------
Lost pilot: she you get to recovery mode with the android with triangle try pushing down both volume keys at same time couple of times until you get your options which are in blue this worked for me
Sent from my XT907 using xda app-developers app
droidman89 said:
OK I read your post I'm in same situation here did the ran batch program to root phone said exploit complete super user is installed but it is not rooted so what is the best way to remove super user if obviously not rooted ? So I can run the rooting process again?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Re run the batch and see if you are getting this issue com.motorola.bug2go is unknown or UID failed. If so, perform a factory reset and follow my steps above about replacing the su and superuser.apk. you do not have to remove superuser in order for this to work because it should over write it. Worked for me. But if it doesn't work and you still want it removed u cant. It won't work in root explorer or anything like that. The only way I found to do it was by freezing it to my knowledge unless u RSD back to ICS and re flash jb.. but this method SHOULD work for you just fine. Let me know if your getting those errors
Sent from my XT907 using xda premium
Ok, got it to work ...
Here is what I did:
Since I could not get into recovery I erased data from within the os
did not complete setup
executed motofail2go with updated files
after a few tries I finally got the second vibration
after regaining root I unrooted using supersu
tried to get into recovery to erase cashe and data but nothing so I erased data from within the os one more time
after such I finnaly got into recovery after going crazy and pressing volume up and dows for about 30 times while in the android with the ! on his chest
Phone is much better now
Hope this helps someone
Thanks for your help bud that did the trick I guess I assent holding the keys to get bug report long enough to get second vibrate and yea it did overwrite other super user apk with the new one I placed.
Sent from my XT907 using xda app-developers app
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
stator said:
For the first time I did an OTA while rooted. I upgraded to 4.3 and now I've lost the following:
SuperSU dowsn't work
Busybox does't work
Can't run bootloader or recovery
My system still shows as a rooted system upon boot. When I connect to my pc and run wugfresh's toolkit, it fails to find adb. I have verified that the driver is installed correctly and debugging mode is on. I can't unlock, root or even return to stock. I do remember seing a thread about a similar issue quite some time ago but I have been unable to find ut. Any help will be greatly appreciated.
Btw, it has just a plain root, no custom roms installed.
Thanks in advance.
Click to expand...
Click to collapse
Hi, stator...
Your post isn't quite clear... does the device boot normally? If so, you should have no problems booting into the bootloader.
But first download the latest UPDATE-SuperSU-v1.51.zip to your Nexus 7.
Shutdown the Nexus as normal. Then press and hold the VOL down button... whilst continuing to hold, press the POWER ON button.
This should boot you into the bootloader (in fastboot mode).
From there, and from your PC, Fastboot flash a custom recovery... (Chainfire recommends TWRP)... with the line...
Code:
fastboot flash recovery recovery.img
Where recovery.img is the name of your custom recovery. I usually just rename it to 'recovery.img' (without quotes) anyway - makes for less typing at the command prompt.
Ensure you get the correct recovery for your device....
TWRP for Nexus 7 Wi-Fi ('Grouper') or TWRP for Nexus 7 3G ('Tilapia')
Although a new version of TWRP is now available (2.6), I had some weird issues with this... particularly when copying Nandroid backups off of my Nexus 7 to my PC. Random 'permission denied' messages would crop up running an ADB PULL command... copying via MTP didn't fair much better either. TWRP 2.5 works without problems though, and it's the version I would recommend.
Anyway... back on topic...
Upon completion of flashing TWRP, boot into that recovery (whilst still in the bootloader)... and select INSTALL... navigate to the folder where you downloaded Chainfires SU root updater (usually, the 'download' folder)... and SWIPE to confirm.
Reboot as normal... you should now be rooted. This can be confirmed by any one of the numerous Root Checker apps available in Playstore.
I haven't experimented with busybox... if you mean this version, I haven't installed it, and nor am I going to... at least not for a while.
My Nexus 7 is still in the process of being rebuilt from the ground up, after having fastboot flashed the factory image, necessitating a full wipe (I was running a custom ROM/Kernel combo before)... so I'm taking this slowly, re-installing apps carefully.
It seems that some apps that worked fine under 4.2.2 are broken under 4.3. MX Player and Adobe Flash Player to name a couple.... but QuickPic and Titanium have now been fixed and work fine under 4.3. I'm under no illusions that Adobe Flash Player will be fixed anytime soon... it's been technically deprecated by Adobe for a while anyway.
Anyway... good luck... and hope you get root sorted.
Rgrds,
Ged.
I am having problems with Busybox as well even though i did not take the OTA. I flashed CleanRom, and Faux kernel.
Just fyi
Sent from my Nexus 7 using xda premium
First and foremost I would like to apologize for taking so long to reply. Real life had me out of town and I didn't have my tablet with me. I tried the advice given but it didn't work at first. It took multiple attempts but I finally got my tablet back to stock. I guess my Nexus 7 didn't agree with the 4.3
OTA while rooted. I can now unlock, root, and even change roms once again. I don't know for sure what was causing the problem but it's all good now. Also, I was always able to use my tablet during my little crisis. I was just unable to unroot or even flash a new rom. Thanks again for all the help.
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
shevich said:
You could have hit thanks, a guy wrote you a gigantic step-by-step instructions just to help you out
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I sincerely hope this is a joke. I most definitely said thanks. I even apologized for taking so long to reply. Please try to be constructive or don't bother to post. I've been frequenting this site for quite sometime although I've never posted or even joined until recently. This community has been extremely helpful. The last thing that is needed is another troll. Thank you.
He was talking about using the thanks button.
Sent from my Galaxy Nexus
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
minjiet said:
i received the ota today...when i tried to update. it fail...then it show me the android screen with messege 'no command'...what should i do now?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
jalize said:
If you are rooted and have StickMount installed or had it installed you might need to replace the \system\bin\debuggerd file before doing the upgrade again.
See also http://forum.xda-developers.com/showthread.php?t=2419468
Search for how to sideload the security update using adb
Click to expand...
Click to collapse
Ya, i'm rooted, now the n10 cant boot at all....what can i do?
anyone can show me step by step guide?
Or flash the Factory image with a bit editing. This should do: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
I got that as well on my N10. Stock, stock recovery rooted. Booting into recovery didn't help. The next morning it was the same thing, but after a while it shut itself off and when I was ready to flash a stock img, had the USB cable plugged into the laptop, I look at the N10 and it's booting just fine, then starts applying the update.
Not helpful I know, but just wanted to let you know it fixed itself, I did nothing. Good luck.
Same problem on stock rooted. Impossible to boot and to switch off the device. I've wait the nexus shut down by himself and after the update have been automaticaly installed on the boot. I'm always rooted. Strange.
Use http://www.afterdawn.com/software/s...l_devices/nexus_root_toolkit.cfm#all_versions app is the best to fix and very easy
Sent from my Nexus 10 using XDA Premium 4 mobile app
---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------
A fixed all my problems, i am on stock with the same problem on jelly bean 4.3, now rooted and again with a custom recovery.
Sent from my Nexus 10 using XDA Premium 4 mobile app
thanks for the help...my n10 back to normal automatically after i plug in charger...weird
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
DEinspanjer said:
Okay, something pretty similar happened to me twice now. I'll share what I saw and did.
Unboxed brand new n10 and immediately went through the process to unlock and root it. I did *not* install a custom recovery.
After a couple of hours playing, it prompted me to install an update. I *think* it was actually on 4.2 before and this was the update to 4.3.
Applied the update and it rebooted and went to the "No Command" screen. As others stated, it felt very stuck.
I eventually gave up and figured it was soft-bricked so I use the Nexus Root Toolkit to download and install a factory fresh 4.3 (v). Lost all my customizations.
Fast forward to this morning. It prompted me for a new update to 4.3. I made a full backup using Nexus Root Toolkit and tried it, but again, it just got stuck on the "No Command" screen.
This time, I tried pressing all three buttons (power, vol down, vol up) quickly, but it did not bring up the stock recovery screen until I actually pressed them in order, (power, vol down [next to power], vol up [farthest from power]). At that point it brought up the recovery menu and I selected the option to wipe cache.
It took a while, but after wiping, I rebooted and it went straight into Android without a problem and it *looked* like it finished the upgrade. Oddly, it still reports it is 4.3 (v) rather than 4.3 , so i don't know if I ended up aborting the upgrade or if it was just trying to re-install (v) for some reason.
Click to expand...
Click to collapse
When you cleared cache you lost the update package I believe, so it didn't update, when I received my OTA I had TWRP installed and it went through nicely. Maybe you should try it and then installing Stock Recovery again.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
I have a Nexus 10. I just took and installed the OTA that arriced 08/27/2013. I am not rooted or unlocked. It is only a wifi (not a carrier specific).
I have been sick since i took the first Ota several weeks ago. I was constantly having to reboot because it would drop the connection. Firefox was useless. And above all, I was unable to get Grassland Live wallpaper and Wind Turbine 3D to work.
It all works now!
Sent from my Nexus 10 using xda app-developers app
I just read in another thread that the issue as described is caused by apply the OTA when rooted. Just unroot then apply the OTA update and reboot. Assuming you are using SuperSU., it has an unroot option in the settings panel.
Good luck.
I flashed my D801 to stock because I accidentally wiped both internal data and system in recovery. Now when I try to root using the root tool, I get this. It says the apk is installed already (because I tried it multiple times) but the actualy binaries required for root arent being pushed (probably because it can't mount system)
aranurea said:
I flashed my D801 to stock because I accidentally wiped both internal data and system in recovery. Now when I try to root using the root tool, I get this. It says the apk is installed already (because I tried it multiple times) but the actualy binaries required for root arent being pushed (probably because it can't mount system)
Click to expand...
Click to collapse
SOLVED
Sent from my LG-D801 using XDA Premium 4 mobile app
Put the phone in download mode by turning off device. Hold the volume up button and plug in a usb cable it will tell you if its rooted or unrooted u may still be rootedvif not flash a rooted stock rom
tbishop91 said:
Put the phone in download mode by turning off device. Hold the volume up button and plug in a usb cable it will tell you if its rooted or unrooted u may still be rootedvif not flash a rooted stock rom
Click to expand...
Click to collapse
I appreciate your help but this has been solved as stated above.
Sent from my LG-D801 using XDA Premium 4 mobile app