I sideloaded the 4.3 OTA and it worked great but now I've lost root.
When I start SuperSU i tells me to re-root but how do I do that? My boot loader is already unlocked so do I lock it and then unlock it again (and loose all my data) or is there another way?
No need to lock/unlock or lose any data. You have to flash the updated su zip file through a custom recovery.
Sent from my Nexus 4 using xda premium
mbeltoft said:
I sideloaded the 4.3 OTA and it worked great but now I've lost root.
When I start SuperSU i tells me to re-root but how do I do that? My boot loader is already unlocked so do I lock it and then unlock it again (and loose all my data) or is there another way?
Click to expand...
Click to collapse
Get ChainFires last SuperSU and flash in recovery.
can i do it via adb? - i really don't wanna install a custom recovery
EDIT:
fastboot should be able to do it using this command: fastboot update UPDATE-SuperSU-v1.43.zip but i get the error:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
mbeltoft said:
can i do it via adb? - i really don't wanna install a custom recovery
EDIT:
fastboot should be able to do it using this command: fastboot update UPDATE-SuperSU-v1.43.zip but i get the error:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
If you don't want to install a custom recovery, you can use fastboot to just boot to it once and install supersu, without actually flashing the recovery. Just download the recovery (I've always used Cwm for this), put it in the folder with fastboot, boot to the bootloader, and type fastboot boot imagename.img. You'll reboot to the custom recovery, but it won't flash it.
Sent from my Nexus 10 using XDA Premium HD app
nyijedi;43986325ust download the recovery (I've always used Cwm for this) said:
Thank you for helping out...I have the same issue but I cannot figure out what to do with your instructions above. Would you be kind enough to provide a more detailed manual of what this means (ie for noob like me)? My nexus 7 was rooted and working fine using SuperSU until I did 4.3 update by OTA. Also, will this delete my user data?
Many thanks
Well for anyone interested, I sorted this by using WugFresh and selected root device. I did not delete my data. Perfect tool for noob.
Click to expand...
Click to collapse
How can I root 4.3 on nexus 10 without losing data. My boot loader is locked and all the instructions need an unlocked boot loader which will delete data to do. In stuck. I had my boot loader unlocked but I licked it with bootlocker from play store before ota update and I used voodoo root keeper but obviously that failed so now I can't reunlock my boot loader and I can't get root. Any help please?
Sent from my Xperia Play (r800x)
fcna72 said:
Thank you for helping out...I have the same issue but I cannot figure out what to do with your instructions above. Would you be kind enough to provide a more detailed manual of what this means (ie for noob like me)? My nexus 7 was rooted and working fine using SuperSU until I did 4.3 update by OTA. Also, will this delete my user data?
Many thanks
Well for anyone interested, I sorted this by using WugFresh and selected root device. I did not delete my data. Perfect tool for noob.
Click to expand...
Click to collapse
You need to download a recovery .img, and in a command prompt/terminal, run:
fastboot boot recovery <path-to-recovery.img> (obviously, if you're running fastboot from an .exe, you'll need to run fastboot.exe boot recovery <path-to-recovery.img> instead). That will send the custom recovery image to the device, load it into memory, and boot once.
abdel12345 said:
How can I root 4.3 on nexus 10 without losing data. My boot loader is locked and all the instructions need an unlocked boot loader which will delete data to do. In stuck. I had my boot loader unlocked but I licked it with bootlocker from play store before ota update and I used voodoo root keeper but obviously that failed so now I can't reunlock my boot loader and I can't get root. Any help please?
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Until we see another locked-bootloader tool like motochopper, you're stuck. I would try using a tool like Helium to grab your backups and then bite the bullet and do an unlock. Given the changes in Android 4.3, the recovery flash is the only known way to get full root right now.
Rirere said:
You need to download a recovery .img, and in a command prompt/terminal, run:
fastboot boot recovery <path-to-recovery.img> (obviously, if you're running fastboot from an .exe, you'll need to run fastboot.exe boot recovery <path-to-recovery.img> instead). That will send the custom recovery image to the device, load it into memory, and boot once.
Until we see another locked-bootloader tool like motochopper, you're stuck. I would try using a tool like Helium to grab your backups and then bite the bullet and do an unlock. Given the changes in Android 4.3, the recovery flash is the only known way to get full root right now.
Click to expand...
Click to collapse
Actually I was able to root without unlocking using n-crys nexus toolkit. Then from there I unlocked my bootloader using the boot unlocked app so I still have all my data
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
How can I root 4.3 on nexus 10 without losing data. My boot loader is locked and all the instructions need an unlocked boot loader which will delete data to do. In stuck. I had my boot loader unlocked but I licked it with bootlocker from play store before ota update and I used voodoo root keeper but obviously that failed so now I can't reunlock my boot loader and I can't get root. Any help please?
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
I have locked bootloader and rooted after 4.3. (Stock recovery and everything)
How i did it was pretty easy:
- Reboot to bootloader (Either manually or "adb reboot bootloader")
- "fastboot boot recovery.img" (latest cwm recovery or whichever you prefer)
- then install latest superSU.zip (either directly from internal memory or via sideload)
- then reboot and you're done (ROM overwrites the "temporary" recovery with stock again when booting)
At least this as far as i understand it, and it works perfectly for me.
Drood said:
I have locked bootloader and rooted after 4.3. (Stock recovery and everything)
How i did it was pretty easy:
- Reboot to bootloader (Either manually or "adb reboot bootloader")
- "fastboot boot recovery.img" (latest cwm recovery or whichever you prefer)
- then install latest superSU.zip (either directly from internal memory or via sideload)
- then reboot and you're done (ROM overwrites the "temporary" recovery with stock again when booting)
At least this as far as i understand it, and it works perfectly for me.
Click to expand...
Click to collapse
Look at the post right above you and you will see I already solved it lol but thanks anyways.
Sent from my Xperia Play (r800x)
abdel12345 said:
Look at the post right above you and you will see I already solved it lol but thanks anyways.
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Haha, yeah true.. sorry about that My eyes aren't what they used to be i guess.. hehe
because we all don't won't someones toolkit...
abdel12345 said:
Look at the post right above you and you will see I already solved it lol but thanks anyways.
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
I'm actually really glad drood posted his method as it doesn't rely on any so called toolkits written by anybody and explains how to just do it with adb and booting one time into a custom recovery. I too am in this same position and have always used chainfires root-keeper to get root back after doing an upgrade.
I've always thought it was pretty cool having bootloader locked, stock recovery, always getting all the OTA's directly and having ROOT! :victory:
Drood said:
I have locked bootloader and rooted after 4.3. (Stock recovery and everything)
How i did it was pretty easy:
- Reboot to bootloader (Either manually or "adb reboot bootloader")
- "fastboot boot recovery.img" (latest cwm recovery or whichever you prefer)
- then install latest superSU.zip (either directly from internal memory or via sideload)
- then reboot and you're done (ROM overwrites the "temporary" recovery with stock again when booting)
At least this as far as i understand it, and it works perfectly for me.
Click to expand...
Click to collapse
fastboot boot recovery.img no longer works on the Nexus 4 because of a change in 4.3. I assume it no longer works on the Nexus 10 also. The new command for the Nexus 4 is fastboot -c "lge.kcal=0|0|0|x" boot recovery.img. I don't know if the same string works on the Nexus 10 or not. Replace recovery.img with the name of the recovery image you want to boot to.
xda6969 said:
fastboot boot recovery.img no longer works on the Nexus 4 because of a change in 4.3. I assume it no longer works on the Nexus 10 also. The new command for the Nexus 4 is fastboot -c "lge.kcal=0|0|0|x" boot recovery.img. I don't know if the same string works on the Nexus 10 or not. Replace recovery.img with the name of the recovery image you want to boot to.
Click to expand...
Click to collapse
Fastboot boot recovery.img worked fine on my N10.
Sent from my Nexus 10 using xda app-developers app
On my N10 when supposed to reboot to recovery is just power down?
Drood said:
I have locked bootloader and rooted after 4.3. (Stock recovery and everything)
How i did it was pretty easy:
- Reboot to bootloader (Either manually or "adb reboot bootloader")
- "fastboot boot recovery.img" (latest cwm recovery or whichever you prefer)
- then install latest superSU.zip (either directly from internal memory or via sideload)
- then reboot and you're done (ROM overwrites the "temporary" recovery with stock again when booting)
At least this as far as i understand it, and it works perfectly for me.
Click to expand...
Click to collapse
The above method worked for me too. :good: No issues with fastboot as descrived above on my nexus 10 with locked bootloader. No data lost. :laugh:
Thank you.
help
PuroKaibil said:
The above method worked for me too. :good: No issues with fastboot as descrived above on my nexus 10 with locked bootloader. No data lost. :laugh:
Thank you.
Click to expand...
Click to collapse
I must be missing something , but I get the following error when i try and boot the recovery,
./fastboot boot openrecovery-twrp-2.6.0.0-mako.img
downloading 'boot.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.010s
Yes my boot loader is locked and im all stocked, but it seems others can do this so im more sure what I'm doing wrong, or have I missed something any help would be great thanks
G/
Nexus 4 & 7 running 4.3 both were rooted, but lost during OTA
Nexus 10 update
Reading through this thread I started to wonder something.
My nexus 10 already downloaded the update to 4.3 and wants to install it.
My nexus 10 is unlocked and rooted, what's the best way to install the update?
I get the feeling the OP installed the update without locking and unrooting, is that okay to do? Or may that cause complications?
Tangonaf said:
Reading through this thread I started to wonder something.
My nexus 10 already downloaded the update to 4.3 and wants to install it.
My nexus 10 is unlocked and rooted, what's the best way to install the update?
I get the feeling the OP installed the update without locking and unrooting, is that okay to do? Or may that cause complications?
Click to expand...
Click to collapse
I'm pretty sure you can just go ahead and install the update.
You will loose root though, but can easily re-root using the earlier mentioned method.
---------- Post added at 04:35 PM ---------- Previous post was at 04:29 PM ----------
gymmy said:
I must be missing something , but I get the following error when i try and boot the recovery,
./fastboot boot openrecovery-twrp-2.6.0.0-mako.img
downloading 'boot.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.010s
Yes my boot loader is locked and im all stocked, but it seems others can do this so im more sure what I'm doing wrong, or have I missed something any help would be great thanks
G/
Nexus 4 & 7 running 4.3 both were rooted, but lost during OTA
Click to expand...
Click to collapse
I'm far from an expert here, and have never seen that error, but maybe try cwm recovery instead of twrp could be worth a try?
And, downloading the latest adb/fastboot, if you haven't already?
Just brainstorming here =)
Related
I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!
mj56gt said:
I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!
Click to expand...
Click to collapse
I would update first then root, and use wug's toolkit to help you through the process.
mj56gt said:
I just purchased a N7 yesterday, and it's supposed to arrive in a couple of days. I'm using a Mac OS computer and comfortable with ADB, so which is better: root first before updating the firmware, or update to the most recent version of firmare and then root? And which rooting method do you recommend with a Mac?
Thanks for your suggestions!
Click to expand...
Click to collapse
I personally have done the following steps:
- I've rooted it first;
- installed OTA RootKeeper (to keep the root after updating - the app must be configured before updating firmware);
- I've updated the firmware to the last version.
I performed all those steps using my notebook which has Windows 7 OS, so for Mac OS I cannot make any recommendation.
I hope this helps you.
Thank you both for the suggestions! Is the Wug's toolkit for Windows OS? Any such toolkit for Mac OS or Linux system? Thanks!
Leonhan said:
I would update first then root, and use wug's toolkit to help you through the process.
Click to expand...
Click to collapse
Good Dog. The OP said he had a Mac.
@OP
May as well do stock firmware upgrade first if it is needed.* On the rare chance that you get a device that suffers some kind of infant mortality - the device will be pure stock for the first little bit of operation (in case an RMA is needed). And the flashing operations which take place IF an OTA is needed will give flash memory a little workout.
Just bear in mind that the bootloader unlock operation will erase everything from /data (factory reset) when the "fastboot unlock" command occurs. So, if you operate the device as pure stock for a while, you will either need to backup stuff or regard your initial customizations as disposable.
fastboot methods are the most expeditious way to proceed on a Mac.
If you use TWRP 2.4.4.0 as your custom recovery, it will peek in /system to see if you are rooted and offer to root your device with SuperSU for you (just before you reboot from within TWRP).
The way I see it, the rooting procedure is 4 steps total:
(Note: use the "tilapia", not grouper recovery image if you have the 3G/LTE Nexus 7)
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Those 4 steps above will leave you with Pure Stock + Rooted ; even the recovery on the tablet will be pure stock until you flash it there (optional step 5 above).
It's up to you to get the Mac SDK (for fastboot & adb) installed and figure out using command lines - search for that, don't ask.
good luck
* I thought I saw a report recently that someone had JDQ39 on a device purchased less than 4 weeks after the last update - your device may not need upgrading yet.
bftb0 said:
@OP
May as well do stock firmware upgrade first if it is needed.* On the rare chance that you get a device that suffers some kind of infant mortality - the device will be pure stock for the first little bit of operation (in case an RMA is needed). And the flashing operations which take place IF an OTA is needed will give flash memory a little workout.
Just bear in mind that the bootloader unlock operation will erase everything from /data (factory reset) when the "fastboot unlock" command occurs. So, if you operate the device as pure stock for a while, you will either need to backup stuff or regard your initial customizations as disposable.
fastboot methods are the most expeditious way to proceed on a Mac.
If you use TWRP 2.4.4.0 as your custom recovery, it will peek in /system to see if you are rooted and offer to root your device with SuperSU for you (just before you reboot from within TWRP).
The way I see it, the rooting procedure is 4 steps total:
(Note: use the "tilapia", not grouper recovery image if you have the 3G/LTE Nexus 7)
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Those 4 steps above will leave you with Pure Stock + Rooted ; even the recovery on the tablet will be pure stock until you flash it there (optional step 5 above).
It's up to you to get the Mac SDK (for fastboot & adb) installed and figure out using command lines - search for that, don't ask.
good luck
* I thought I saw a report recently that someone had JDQ39 on a device purchased less than 4 weeks after the last update - your device may not need upgrading yet.
Click to expand...
Click to collapse
Thanks a lot for the detailed information and the kind help, bftb0! I really appreciated it.
I had a two-year-old version of Mac SDK, and only used adb before. Just finished grabbing the most recent version. I prefer command lines instead of button pushing. Once N7 arrives, I will start to have fun with fastboot...
bftb0 said:
Code:
fastboot unlock
fastboot boot openrecovery-twrp-2.4.4.0-grouper.img
... make a pure stock Nandroid backup
... reboot TWRP and it will offer to install SuperSU for you
(optionally: fastboot flash recovery openrecovery-twrp-2.4.4.0-grouper.img )
Click to expand...
Click to collapse
One more question. Is the first step (unlocking) necessary for the later steps such as root access? The reason I'm asking is that, unlike rooting, unlocking is irreversible, and would avoid the warranty.
Edit: I guess that the bootloader has to be unlocked to flash a custom recovery, right?
Unlocking is necessary to use fastboot commands and it's not irreversible as you can relock it with "fastboot oem lock" but if you want to unlock it another time it will wipe your device again. And if you flash recovery with fastboot then yes your bootloader must be unlocked but you can relock it after.
Nico_60 said:
Unlocking is necessary to use fastboot commands and it's not irreversible as you can relock it with "fastboot oem lock" but if you want to unlock it another time it will wipe your device again. And if you flash recovery with fastboot then yes your bootloader must be unlocked but you can relock it after.
Click to expand...
Click to collapse
That's great! Thanks a lot for the help...
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
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
RohMish said:
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
Click to expand...
Click to collapse
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
flash installs the recovery but nothing works. i have to do a wipe and install the stock recovery to boot it. i wrote it on top
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
RohMish said:
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
Click to expand...
Click to collapse
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
RohMish said:
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
Click to expand...
Click to collapse
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
tried an older version of cwm, touch, everything. but all are having same issues
RohMish said:
tried an older version of cwm, touch, everything. but all are having same issues
Click to expand...
Click to collapse
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
UPDATE: Tried twrp via fastboot boot command. nothing. just a blank screen after the reboot from bootloader (and after google boot screen) for a few seconds, andd then shuts down.
RohMish said:
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
Click to expand...
Click to collapse
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
spaceman860 said:
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
Click to expand...
Click to collapse
not working. says 0 is a not a command. this is as | works as a batch separator in windows
Update: as i remembered modifier <"> will prevent | from kicking into next line, i tried that, and it works!
fastboot -c "lge.kcal=0|0|0|x" boot recoverycwm.img. but still no action. tried a backup, it starts to backup but files are corrupted. and nothing else work.
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
spaceman860 said:
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
Click to expand...
Click to collapse
i loads up but is kind of broken.
any way i can copy the files to my pc to do some analysis. currently the folder which used to save the files has nothing. adb pull /mnt/shell/emulated/clockworkmod/backup/ /android/adbbackupfiles/nexus4 is yielding nothing.
OK. so now i tried using the touch version, and this time there are some files(Still copying). but those are very different than what it was on my older phones and my initial backup. Sorry, I had got away with this due to studies. now the files are .a and.b and the orignal file which is 0KB
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.
My Nexus 7 (2012-wifi) was running 4.4 rooted with CWM. I flashed the 4.4 update zip from recovery which failed late in the flash.
Did it fail because I forgot to unroot before I flashed the update?
At any rate even though the flash failed I also flashed SuperSu in case the update was good enough.
It wasn't, when I boot I get rotating/expanding/contracting colored balls forever.
Is there some way for me to recover from this without wiping the device? I was over confident and didn't do an external backup.
I don't know how to help you fix the problemm but it definitely didn't fail because you were rooted. I was rooted too and all it did was that I lost root (had to root again)
You can try wiping dalvik cache from recovery?
I got into the exact same problem as you.
I fixed it by following the steps here:
http://forum.xda-developers.com/showthread.php?t=2376978
It basically flashes back your 4.3 firmware. Just one thing to note though, DO NOT flash the userdata, YOU MUST SKIP THIS STEP unless you want to lose your files.
Tehloy said:
I got into the exact same problem as you.
I fixed it by following the steps here:
http://forum.xda-developers.com/showthread.php?t=2376978
It basically flashes back your 4.3 firmware. Just one thing to note though, DO NOT flash the userdata, YOU MUST SKIP THIS STEP unless you want to lose your files.
Click to expand...
Click to collapse
I had a look at this. One thing I'm wondering is, doI really need to update the boot loader as in the instructions, or can I go directly to the fastboot flash of the system and boot img?
kmandel said:
I had a look at this. One thing I'm wondering is, doI really need to update the boot loader as in the instructions, or can I go directly to the fastboot flash of the system and boot img?
Click to expand...
Click to collapse
I think you can skip flashing the bootloader. Just jump straight in to flashing the rest.
I got ready to try fastboot flash of the system img. I booted into bootloader mode and adb doesn't see the device. I then went into CWM and it does see the device from there. "adb devices" and "adb shell" work from recovery. However, "fastboot flash" just waits forever for device.
Suggestions?
kmandel said:
I got ready to try fastboot flash of the system img. I booted into bootloader mode and adb doesn't see the device. I then went into CWM and it does see the device from there. "adb devices" and "adb shell" work from recovery. However, "fastboot flash" just waits forever for device.
Suggestions?
Click to expand...
Click to collapse
Never mind, fastboot did work from the bootloader, I was just surprised that adb devices didn't see it. All is good, I'm back on 4.3 with my files intact. I'll try the 4.4 update again tonight.