HOW TO ROOT YOUR DEVICE WITHOUT FLASHING RECOVERY
This can be done with two methods.
ADB or FASTBOOT.
I have tested both methods and they worked for me.
I tested this on JSS15J. I am not sure about any other versions but I guess it should work.
SOME BASIC INFORMATION
Usually when you want to root your device, you must have UNLOCKED BOOTLOADER.
A CUSTOM RECOVERY is usually used to flash SuperSU to gain root access.
CUSTOM RECOVERIES ARE USUALLY FLASHED (they permanently replace your stock recovery)
In this guide, You BOOT into custom recovery by going into BOOTLOADER and then using fastboot/adb tools to flash SuperSU .
Booting is temporary and thus once you restart from recovery, the custom recovery will be gone
Make sure, you have USB debugging mode enabled. To go into bootloader you can either use adb commands ( Type [adb reboot bootloader] in cmd in platform tools directory with your device connected) or do it manually by turning it off and then holding power and volume down.
You must also have platform tools of SDK (Fastboot and ADB) for this to work. MAKE SURE YOU OPEN CMD into the folder where platform tools are present.
Try it on OWN risk. I will not be responsible for bricked devices or any damage.
ADB METHOD
Connect to your PC and make sure USB debugging is on.
COMMANDS IN BRACKETS. DON'T WRITE THEM. COMMAND WOULD BE LIKE : fastboot boot recovery.img
MAKE SURE YOUR DEVICE HAS UNLOCKED BOOTLOADER
(fastboot boot [recovery.img])--------------------- Name of recovery to be here
Mount /system and push the necessary files once the recovery has started:
(adb push su /system/xbin)
(adb push Superuser.apk /system/app)
Set correct permissions:
(adb shell)------------------------------ You have got into your device's shell
(chmod 06755 /system/xbin/su)
(chmod 0644 /system/app/SuperSU.apk)
(exit)
Reboot:
(adb reboot)
FASTBOOT METHOD
This is relatively easier as you will boot into custom recovery temporarily and then flash ZIP of SuperSU. Afterwards I recommend to clear davik cache and restart.
UNLOCKED BOOTLOADER REQUIRED
Boot into bootloader.
Type these commands to boot into custom recovery. This will not flash recovery and you will have stock recovery once you restart.
fastboot boot recovery recovery.img where recovery.img will be the file name of recovery
(After 4.4, use this command "fastboot boot recovery.img" instead of above mentioned)
After booting into reccovery, flash SuperSU and you are done.
I recommend clearing dalvik cache before leaving and restart.
And you are done.
YOU CAN ALSO USE A PREROOTED KERNEL WHICH YOU CAN FLASH VIA FASTBOOT. I AM NOT SURE IF THERE IS ANY
For information on how to retain root after OTA, please refer to this :
Update Super SU is also taken from this guide.
http://forum.xda-developers.com/showthread.php?t=2415497
For Recovery/SuperSU/TWRP
http://forum.xda-developers.com/showthread.php?t=2382051
CWM
http://forum.xda-developers.com/showthread.php?t=2381544
PLATFORM TOOLS:
http://www.androidfilehost.com/?fid=9390355257214632011
If you are stuck in a bootloop, make sure you have cleared dalvik cache in custom recovery.
I got bootloop when i tried with fastboot method as I was new to twrp, I explored it a bit and tried to remove system and tried overwriting data to see how it is different from CWM and check its strength. I got an error clearing cache so I rebooted into custom recovery to clear dalvik and my nexus booted fine (DON'T TRY THIS, JUST CLEAR CACHE AND WIPE DATA and restart)
REMEMBER, UNLOCKING BOOTLOADER WILL DELETE ALL YOUR DATA AND DOING WIPES WILL ALSO DELETE ALL YOUR DATA.
DALVIK WON'T DELETE YOUR DATA BUT
MAKE SURE YOU HAVE MADE A BACKUP using BACKUP PRO (non rooted) or Helium (non rooted) and Titanium Backup Pro (Daah, you are not rooted so this won't work)
GOOD LUCK
Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.
sfhub said:
Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.
Click to expand...
Click to collapse
I got bootloop but then realised it might due to trying to wipe system in twrp. Clearing dalvik worked fine .SuperSU used
So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)
Muikkuman said:
So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
You will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
[UPDATE]
http://forum.xda-developers.com/showthread.php?t=2415497
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone
Hnk1 said:
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
This way you will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone
Click to expand...
Click to collapse
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)
Muikkuman said:
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Anytime mate
How do we clear dalvik without a custom recovery?
Master619 said:
How do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
You restart your device. Boot into bootloader and use fastboot to Boot into custom recovery(command given in post above).Once Into recovery, you can easily clear dalvik cache.
And remember, it might not require clearing cache because I was exploring twrp n overwriting data n tried To delete system to see how powerful the recovery is. I will update guide now
muikkuman said:
so you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my nexus 7 (2013)
Click to expand...
Click to collapse
master619 said:
how do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
guide updated. Check it.
Platform tools are being attached
The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.
gunner49 said:
The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.
Click to expand...
Click to collapse
Did you try: fastboot boot recovery.img ?
mdamaged said:
Did you try: fastboot boot recovery.img ?
Click to expand...
Click to collapse
That worked a treat! Thanks a lot mate!
Those who finding difficulty in rooting Nexus 7 (2013) can use Wugfresh Nexus Root Toolkit. It is so powerful that you would find every function you would like to do on your Nexus 7, from the comfort of your PC. Also watch qbking77 's video on using the Toolkit for further information.
Related
Made a silly mistake. I was going to flash M-kernel to my device after updating to 4.2.2 and while I was in Team Win recovery I chose to wipe cache and system. I flashed the kernel and now when I select to reboot it says "No OS installed! Are you sure you wish to reboot?" I still have the file to flash 4.2.2 but don't know how I can get it on the device in it's current state. Any help would be greatly appreciated.
I tried this method here: http://forum.xda-developers.com/showthread.php?t=1667929 however I can't get Unmount/sdcard to work in the recovery menu and therefore can't push the OS file using the cmd prompt.
You may have to fastboot the system.img and boot.img into place. How did you root? Did you use root and unlock? Did you use wugs? Do you have android sdk and fastboot installed?
Btw, I did this too. I was preparing to flash a rom, did a factory reset, wipe system, and (understand I had just gotten this device at the time LOL) wiped internal storage. Which meant my backups and update.zips were gone. The nexus 7 doesn't seem to have a way to mount twrp from recovery to side load files so I just used fastboot to fix it.
hlxanthus said:
You may have to fastboot the system.img and boot.img into place. How did you root? Did you use root and unlock? Did you use wugs? Do you have android sdk and fastboot installed?
Btw, I did this too. I was preparing to flash a rom, did a factory reset, wipe system, and (understand I had just gotten this device at the time LOL) wiped internal storage. Which meant my backups and update.zips were gone. The nexus 7 doesn't seem to have a way to mount twrp from recovery to side load files so I just used fastboot to fix it.
Click to expand...
Click to collapse
I use Root Tool Kit to root and unlock. I have android sdk installed on the PC but not sure what fasboot is. Can you explain how to "fasboot the system.img and boot.img into place"?
If you are using the toolkit, just select your device, select flash stock firmware and connect your nexus in bootloader mode (fastboot mode, hold volume down and power when it's turned off)
Sent from my Nexus 7 running Android 4.2.2
mihahn said:
If you are using the toolkit, just select your device, select flash stock firmware and connect your nexus in bootloader mode (fastboot mode, hold volume down and power when it's turned off)
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Will doing this cause me to lose everything I have on the Nexus already?
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
This is still possible but the command for booting into custom recovery changed.
This helps.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
The short answer is no, you need a custom recovery to install superuser. The long answer is you can flash a custom recovery and install superuser and then flash back the stock recovery. If that doesn't work then your out of luck.
kzoodroid said:
The short answer is no, you need a custom recovery to install superuser. The long answer is you can flash a custom recovery and install superuser and then flash back the stock recovery. If that doesn't work then your out of luck.
Click to expand...
Click to collapse
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
rajendra82 said:
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
Click to expand...
Click to collapse
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
ajay_zalavadia said:
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
Click to expand...
Click to collapse
Follow @efrant's guide. Section E is enough assuming you are on stock android.
That will do the trick.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
Sorry for asking about your reason, but if you install the TWRP (or some other) custom recovery then can't you simply manually flash the OTA yourself? That's how I upgraded to 4.3.
ajay_zalavadia said:
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
Click to expand...
Click to collapse
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
adb reboot-bootloader
Click to expand...
Click to collapse
Then, once you're booted into Bootloader, type
fastboot -c "lge.kcal=0|0|0|x" boot customrecoveryname.img
Click to expand...
Click to collapse
Flash SuperSU 1.51 zip and then reboot your device.
rajendra82 said:
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
Click to expand...
Click to collapse
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Mercado_Negro said:
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
Then, once you're booted into Bootloader, type
Flash SuperSU 1.51 zip and then reboot your device.
Click to expand...
Click to collapse
thank you, will try when I get chance :good:
kzoodroid said:
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Click to expand...
Click to collapse
I just prefer the command line booting instead of having to flash a recovery twice. I already knew that I could flash the custom recovery to get it done, although I didn't clearly state that in the original post.
Mercado_Negro said:
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
Then, once you're booted into Bootloader, type
Flash SuperSU 1.51 zip and then reboot your device.
Click to expand...
Click to collapse
Thanks for you guide, but for use it, do I nerd unlocke the bootloader ?
Inviato dal mio Nexus 4 con Tapatalk 2
futuro82 said:
Thanks for you guide, but for use it, do I nerd unlocke the bootloader ?
Inviato dal mio Nexus 4 con Tapatalk 2
Click to expand...
Click to collapse
Yes
Thanks
Inviato dal mio Nexus 4 con Tapatalk 2
kzoodroid said:
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Click to expand...
Click to collapse
LOL.. You were still wrong though bro. Don't get upset about it. He didn't seem to be...
Sent from my Nexus 4 using xda app-developers app
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
RedBullet said:
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
Click to expand...
Click to collapse
I would recommend flashing the 4.4 stock factory image from here in fastboot mode. Then once your device is booting up properly again I would recommend taking a look at this guide to properly install the 4.4.1 update.
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
planet_x69 said:
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
Click to expand...
Click to collapse
Thanks, I eventually got it. I was really puzzled that I couldn't select recovery from the bootloader. All set now though, thanks!
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
jalize said:
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
Click to expand...
Click to collapse
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
RedBullet said:
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
Click to expand...
Click to collapse
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
jalize said:
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
Click to expand...
Click to collapse
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
RedBullet said:
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
Click to expand...
Click to collapse
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
jalize said:
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
Click to expand...
Click to collapse
Hi,
Try flashing it fresh stock again, factory reset your device from recovery, download the stock image file from here, untar it, then unzip the zip inside the tar and you'll get some files (.img). Copy those files to your fastboot folder and then open a cmd there. (Guessing that you're using Windows)
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
If you're using Linux, do the same, but instead of only fastboot use:
Code:
sudo ./fastboot
Then boot it. I had the same problem when I updated mine to 4.4.1, but I did one thing a little different... Instead of fully "stocking" it again, I flashed back 4.3, flashed 4.4 OTA and then let it boot, without wiping my data, after all it was running like this before. Worked. But as I'm unsure of your situation I think it's more secure and easier to fully stock it again.
Hope this helps,
~Lord
PS.: Remember to put your device in fastboot mode!
First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk
newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.
Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.
If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.
Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!