Related
Hi guys ...sorry if this is repeated thread but find in internet and not find anything .today when i backing up by apps with root tools v1.9 than it said busybox not installed ,After this i downloaded busybox installer from market but when i installed busybox none of version installed .now i trying flash android 2.3.5 but it said waiting for device.please anyone help
You probably need drivers. Look around in the FAQ thread
Sent from my D255 using XDA App
I think u know i'm using swiftdroid .So i have drivers already
Try a different USB port
Sent from my D255 using XDA App
Root again?
You could try rooting your phone again or put it in fastboot then flash it?
Flash this in recovery. Should fix any issues. If you can't transfer it over to device, just download it using your phone. The finished download will be in /sdcard/download/
Also, for driver issues, download the LG Mobile Update Tool and re-install the drivers using that.
I upgraded to 4.2.2 and it seems I have lost my Root Access. I has SuperSU Pro with OTA Survival mode on installed as a system app before the upgrade but it seems it did not keep Root access. I used Root Checker and it's telling me I am not rooted. I am still seeing the unlock Icon at boot so I assume my boot loader is still unlocked.
Is there an easy way to get my Root access back?
Thanks.
Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app
Thanks for your reply. I will try to follow the steps you outlined however, most of what you said is new to me. I initially rooted my device with the Nexus 7 Toolkit so it was a fairly simple procedure. I have never used the SDK or twrp are there any tutorials on how these work on 4.2.2? Also they will probably update Nexus 7 toolkit to support 4.2.2 eventually, so if I can't figure out the steps indicated I may have to wait.
Another noob question: After the update I can still open busybox and SupeSU, how come these apps still run if I am no longer rooted?
gastonwalpole said:
Hey I had the same happen to me, ended up having to fastboot flash recovery to get twrp back and then downloaded the supersu recovery bootable zip and flashed supersu back. Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb. Hope this helps.
Before trying all this maybe try installing busy box, I dunno I'm a bit of a noob
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
hey man yeh i didnt get how i still had supersu but i definitely wasnt rooted. its all a bit complicated aye, basically you need to download the andriod sdk bundle [now called adt bundle] for whatever you have eg. windows 7 32/64, and the jdk java development kit, look for guides on these, there two youtubers who have helpful channels: driodmodderx and wwjoshdew. also search threads here. you want your device to be recognized by the comp, sdk and jdk do this. twrp is a custom recovery that you can use to flash roms zips etc, you use your comp to send this custom recovery to your device. i would have stayed on 4.2.1 because i dont think you can use custom roms on 4.2.2 bootloader, still 4.2.2 is very smooth, i like it.
Sent from my Nexus 7 using XDA Premium HD app
gastonwalpole said:
Don't forget to update your SDK tools with SDK manager before you flash twrp because 4.2.2 has this added security prompt thing when you connect your tablet it will appear offline in cmd, when you update sdktools and enter adb devices in cmd it will appear offline, check your tablet it will ask you to allow adb.
Click to expand...
Click to collapse
Boy did your post make me happy! I had the exact same problem. Managed to install 4.2.2 with modified OTA update (original was failing due to some discrepency in GoogleCalendar.apk) but even though I had SuperSU in survival mode, I lost my root. I've been trying all afternoon to connect via adb to my Nexus and just couldn't - it was always offline.. I tried 3 different computers and my SGNII phone (which worked) but N7 just wouldn't stop being offline...
I hope this is the solution! Thanx a BUNCH!
One question - my bootloader is unlocked telling by the icon on boot "google" screen - will I lose my apps and data after "re-rooting" that is, after flashing custom recovery and SuperSU?
THANX!!!!!!!!!!!!!
you won't lose anything by flashing recovery or su
I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.
burnitdown said:
you won't lose anything by flashing recovery or su
Click to expand...
Click to collapse
Great, managed to do it, everything fine. Thanx again!
SimonP2 said:
I just checked the Nexus Root Toolkit site and he says he'll have a new version out very soon that will root 4.2.2 so sit tight, we'll soon be able to root again Just fire up the program from time to time and it should automatically update when it's ready.
Click to expand...
Click to collapse
And if you can't wait, the workaround is there on http://www.wugfresh.com/nrt/ under IMPORTANT NOTICE.
Newbie here.
Pls guide me..
Many tks!
Sent from my SM-N9005 using xda app-developers app
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Issues with rooting (4.4), stuck after flashing recovery
I just got my Nexus 10, and unlocked the boot loader, then flashed the custom recovery. All was fine, and I could boot into recovery, however recovery can not mount any filesystems. So I rebooted, now the Nexus does not boot, but hangs on the intro animation, normally meaning in my experience that the kernel is looped and is no longer finding (or else) booting the OS. I've tried booting 3 times.
So then, the steps I took,
enable USB debugging
were copy over the zip file for supersu
reboot to (fastboot mode), verify device
unlock boot loader "fastboot oem unlock"
flash the recovery "recovery-clockwork-touch-6.0.4.3-manta"
reboot into recovery
Failed to mount filesystems
for instance "E: Can't mount /cache/recovery/command or E:Can't mount /sdcard .... (you get the idea).
rebooting again a leaving it does nothing.
I also tried side loading a new image in my case "ThunderKat_manta-KRT16S-20131201" and after installing the "UniversalAdbDriverSetup", I was able to do so, I also was also able to side load the google apps "GoogleAppsPack-4.4-20131128", in both cases I get a success message after the install, however there after when I attempt to reboot I'm still stuck looking at the boot animation.
Now I'm really confused as if if the OS was destroyed when I unlocked the device, then side load of the zip contains a new kernel and OS image so it should be working, but it is not. In fact, recovery while still working throws the same can not mount exceptions after the flash as it did before (I rebooted) as I was previously getting and a factory reset, fails to mount /data, but does flash /cache and sd-ext without issues, so again I'm lost as to what to do.
Best guess I have is that partitions such as /data are just missing, I have no idea the state of teh device in such a case, but recovery and side loading using adb are working, how do I recover a working ANDROID OS from here?
Thanks,
ERIC
stuck in loading screen
Hi,
i just got my Nexus 10 yesterday. I tried to root it, but it is stuck in the loading screen. What can i do now? Can i like undo it to get it back to work?
I have the same issue egandt described.
Edit: I just got it back with this tutorial to android 4.2.2 and now i am updating it back up
nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
I unlocked nexus10,
Flashed cwm,
Installed su, but whn i turned it on, su not found, rootchecker shows no root access..
I also encounter bootloop initially,
Need to wide data / factory reset then its normally booted..
Sent from my SM-N9005 using xda app-developers app
Agreed the factory reset was required to fix the issues I encountered, then installing super-su worked.
I still cannot root the Nexus10..
Any one can help?
Thanks in advance!
XxLordxX said:
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Click to expand...
Click to collapse
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
xing369 said:
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
Click to expand...
Click to collapse
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
shimp208 said:
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
Click to expand...
Click to collapse
Thanks for your kind offering of hands!
Last night I tried again to re-flashed latest TWRP as well as latest SuperSU.
I ran 2x Root Checker,
1 said rooted,
1 said no root access, no BusyBox available.
I tried some apps like GMD Gesture, no working or no root access.
So,
Should I redo everything: enable USB Debugging then unlock bootloader then flash CWM then install SuperSU?
I initially gone thru above steps w/o enabling USB Debug..
Many thanks!
Sent from my SM-N9005 using xda app-developers app
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
xing369 said:
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
fritzhy said:
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
Click to expand...
Click to collapse
Very much appreciated for reviving my nexus!
However, after flashing latest TWRP, and installed SuperSU 1.80,
It seems my nexus still unrooted.
Any ideas?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
fritzhy said:
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
If it's needed the app will say so when you open it.
fritzhy said:
If it's needed the app will say so when you open it.
Click to expand...
Click to collapse
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
xing369 said:
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Not that I can think of, nope...
I just installed TWRP on my N4 and have never used it before. I always used CWM and I just wiped it through recovery. My issue is that I wiped EVERYTHING. It says "no OS detected" and won't boot past the Google logo. Can't install drivers when connected to the computer, and I can't for the life of me figure out how to flash a stock image, or fix it with the nexus root toolkit. Could someone PLEASE give me a walkthrough for a noob of how to go about fixing this? I don't understand a lot that deals with ADB and all that. Thank you.
Sent from my Z665C using xda app-developers app
Google tool adb fastboot drivers. Then Google nexus 4 factory image and download that. Use 7-zip to extract it. Flash the flash-all.bat while your phone is in fastboot mode and connected to your pc
Sent from my Nexus 5
Do I she the factory image it originally had which was 4.2.2 or do I use the image I updated to which was 4.3? Don't know if it matters, but I've never done this so I don't want to make anything worse.
Sent from my Z665C using xda app-developers app
If you don't understand, this time right now seems a good reason to learn about it right?
As to you problem, can you boot into recovery..the twrp? If yes, then it is easy. Just sideload a rom (preferably a 4.2.2 rom as it was the last rom on your device). Oh and yeah, sideload does use a bit of adb command (see how important it is for us, the nexus user?).
The other way is to simply use toolkits (which is a shortcut, not good as you will learn nothing of the whole process and it just takes all the fun away). Look in original android dev section for wugfresh toolkits (but I really, really, really hope that you learn ADB. After all, we need to learn to count before we start using a calculator right? ). Good luck. Don't sweat it so much.
p/s: That video there can be used for any android version and any rom of nexus 4.
Sounds easy enough. My only issue has been that I couldn't install any drivers. I can boot into twrp, but that's it. Any guide I've researched says to turn on USB debugging, which I can't figure out how to do since it won't boot past the Google logo, and the drivers won't install correctly when I connect the nexus to a computer.
Sent from my Z665C using xda app-developers app
Use wugfresh nexus root tool kit to flash a stock rom.
USB debugging is not required to flash a stock ROM via fastboot.
sinndissension said:
Sounds easy enough. My only issue has been that I couldn't install any drivers. I can boot into twrp, but that's it. Any guide I've researched says to turn on USB debugging, which I can't figure out how to do since it won't boot past the Google logo, and the drivers won't install correctly when I connect the nexus to a computer.
Sent from my Z665C using xda app-developers app
Click to expand...
Click to collapse
The easiest in my opinion would be sideloading a new rom, like cm11, paranoidandroid etc. Then you could easily install it on your n4
See here how to do it: http://teamw.in/ADBSideload , http://forum.xda-developers.com/showthread.php?t=2559200 , http://forum.xda-developers.com/showpost.php?p=45798359&postcount=825
Tried the toolkit yesterday. Didn't work because it couldn't install the drivers
Sent from my Z665C using xda app-developers app
Install drivers manually. Just Google "nexus 4 USB drivers" download and install. Then get toolkit and flash stock image.
Sent from my Nexus 4 using xda app-developers app
I'll try again. I was able to figure the drivers out. Tried flashing a stock image I downloaded, but I still wouldn't boot past the Google logo. I flashed it to the system partition, but I didn't know what partition to flash it to. Do I need to use the modified boot image it wants me to download, or am I supposed to flash it to a certain partition?
Sent from my Z665C using xda app-developers app
FIXED IT!!! thank you all for your help.
For anyone else with this problem, I downloaded "universal naked drivers" and installed them manually, use the Nexus Root Toolkit selected "soft brick, than flash stock/unroot, let it download RETORT and the modified boot image, flash it in fast-food, then when it booted up, re-rooted. (You lose root access when you do this).
Nexus 4 rooted and unlocked, TWRP 3.0.
Yesterday I updated with the CM13 nightly, which locked up the phone. No big deal, I thought I would just wipe and restore. Except I discovered my restore image wasn't there. Now I have no OS, but worse I can't connect to the phone via ADB/Fastboot.
The phone doesn't show up in the device manager at all on my pc after many driver uninstalls and installs. Then i installed ADB/Fastboot drivers on my macbook. Terminal commands for ADB/Fastboot work, but no device is found while in bootloader.
Any guidance is appreciated.
rickp1777 said:
Nexus 4 rooted and unlocked, TWRP 3.0.
Yesterday I updated with the CM13 nightly, which locked up the phone. No big deal, I thought I would just wipe and restore. Except I discovered my restore image wasn't there. Now I have no OS, but worse I can't connect to the phone via ADB/Fastboot.
The phone doesn't show up in the device manager at all on my pc after many driver uninstalls and installs. Then i installed ADB/Fastboot drivers on my macbook. Terminal commands for ADB/Fastboot work, but no device is found while in bootloader.
Any guidance is appreciated.
Click to expand...
Click to collapse
What happens when in the bootloader you choose recovery? What happens when you try to boot normally? Did you do anything special when you installed the nightly? What did you wipe?
Sent from my Nexus 4 using XDA Labs
rickp1777 said:
Nexus 4 rooted and unlocked, TWRP 3.0.
Yesterday I updated with the CM13 nightly, which locked up the phone. No big deal, I thought I would just wipe and restore. Except I discovered my restore image wasn't there. Now I have no OS, but worse I can't connect to the phone via ADB/Fastboot.
The phone doesn't show up in the device manager at all on my pc after many driver uninstalls and installs. Then i installed ADB/Fastboot drivers on my macbook. Terminal commands for ADB/Fastboot work, but no device is found while in bootloader.
Any guidance is appreciated.
Click to expand...
Click to collapse
Been there, does your phone show up as Qualcomm HUSB device in device manager ?
Sent from my Nexus 4 using XDA-Developers mobile app
Same happened here it originally booted up and just get stuck on cyan mod symbol boot loop so I restarted it and thought that would help but it didn't so I was told to factory reset it witch I did now it just gets stuck on Google so I tried re installing through recovery but nothing is there not even an os just recovery logs so I tried using a toolkit on my pc that didn't work because of the adb can't be turned on which now just insta ****s all solutions I have found so far I too am or rather was using nightly cm13