I would like to receive OTA updates in the future so I left the recovery untouched on my Nexus 4. In the past I used "fastboot boot recovery.img" to boot into CWM recovery and flash an "update.zip" of SuperSU. So I get a rooted Nexus 4 without flashing custom recovery.
However, things changed after I flashed my Nexus 4 with Android 4.3 factory image listed on Google Developers' page.
In fastboot mode, I tried to use my old routine of "fastboot boot recovery.img", the command line shows:
Code:
$ sudo fastboot boot recovery-clockwork-6.0.3.4-mako.img
downloading 'boot.img'...
OKAY [ 0.398s]
booting...
OKAY [ 0.002s]
finished. total time: 0.400s
Screen goes off, Google logo appears, screen dimmed, a few minutes passed, nothing happened.
My phone has already "fastboot oem unlock", of course. I tried it again and again. With different CWM recoverys and TWRP, the results are same.
I tried "fastboot flash recovery recovery.img", it works, and I can boot into recovery. But I want to preseve stock recovery so I flashed it back.
I just don't know why "fastboot boot" does not work in Android 4.3 any more while "fastboot flash recovery" still works?
To test it out, I tried these on the Nexus 4 of a friend of mine:
1. Her Nexus 4 was 4.2.2.
2. "fastboot boot recovery.img" works.
3. Flash factory image of Android 4.3, everything's fine.
4. "fastboot boot recovery.img" does not work any more! (neither CWM nor TWRP)
5. "fastboot flash recovery recovery.img" works.
So, the results are exactly same on my Nexus 4 and my friend's. There must be something wrong with Android 4.3, e.g. new security enforcements. Do anyone know something about this? Google did not return any valuable results.
EDIT: Problem solved. As 3rdstring explains: http://forum.xda-developers.com/showpost.php?p=44004032&postcount=6 , the new version of bootloader shipped with Android 4.3 factory image changed some of the "fastboot boot" command so you need to specify a kernel commandline to use "fastboot boot" command. For Nexus 4, the command is:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Yea Google took out fastboot boot for some reason.... Fastboot flash works fine though
Sent from my Nexus 4 using Tapatalk 4 Beta
italia0101 said:
Yea Google took out fastboot boot for some reason.... Fastboot flash works fine though
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well... I did not see any documentation announacing that... So we cannot use "fastboot boot" in Android 4.3 and future releases?
wzyboy said:
Well... I did not see any documentation announacing that... So we cannot use "fastboot boot" in Android 4.3 and future releases?
Click to expand...
Click to collapse
So far no, looks like it was taken out of the updated bootloader.... Maybe security? Maybe they want people who have root to have an unlocked bootloader etc
Sent from my Nexus 4 using Tapatalk 4 Beta
italia0101 said:
So far no, looks like it was taken out of the updated bootloader.... Maybe security? Maybe they want people who have root to have an unlocked bootloader etc
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
You usually have to unlock you're bootloader to be able to use fastboot boot anyway
Sent from my Nexus 4 using xda app-developers app
Google changed something but it's still possible according to this thread.
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
For what it's worth fastboot boot fails on the new Nexus 7 as well, but flash works fine.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
For what it's worth fastboot boot fails on the new Nexus 7 as well, but flash works fine.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So I have read through here quite a bit and I see the new commands for fastboot boot. My problem is I can't even connect with fastboot. Adb works but fastboot just days waiting for device. I deleted my existing SDK and downloaded the newest version (7/29/13). Still no luck. Windows 8 64 bit. Any suggestions?
Interesting
Works Again?
For the record: "fastboot boot recovery.img" just worked fine for me on a Nexus 5 with 4.4.4
even after flashing recovery, device shows stock recovery. I advise folks to visit MiUi forum for the twrp, that way it was quick and easy
3rdstring said:
Google changed something but it's still possible according to this thread.
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Click to expand...
Click to collapse
what is lge.kcal=0|0|0|x
I dont always boot into recovery from fastboot but when i do, i use
fastboot reboot-recovery
Keep flashing, my friends!
Related
So I used the Nexus Root Toolkit to flash stock and unroot it, but after using it, I got stuck at the bootloader screen. So I pushed the start button to reboot, and my nexus 7 is still rooted. Help plz?
Give it a try again? I have use this 5 times, work great for me, u have adb fastboot mode on ur desktop?
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Download the stock image and flash in fastboot .
Sent from my Nexus 7 using xda premium
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
zeiloz said:
So when i try to fastboot the bootloader .img manually, it says:
sending bootloader ... okay
'writing bootlader'.... failed (remote: (invalid state))
so what do i need to do to fix that?
Click to expand...
Click to collapse
Is your bootloader locked?
Sent from my Nexus 7 using xda premium
it said lock status: unlock
So i would presume its unlocked...
zeiloz said:
it said lock status: unlock
So i would presume its unlocked...
Click to expand...
Click to collapse
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
El Daddy said:
OK. I've never seen that error before. And a quick google search doesn't come up with anything either.
You could try restarting the bootloader with
Code:
fastboot reboot-bootloader
and trying again.
The only thing I can think of is you could be trying to flash the wrong bootloader (which i doubt) Just to confirm you are trying to flash bootloader-grouper-3.34.img
Also, to just unroot you don't need to reflash the bootloader. Just boot.img and system.img
Click to expand...
Click to collapse
Yes, I am trying to flash bootloader.grouper-3.34.img
And Im flashing bootloader because its I'm told to do in this thread? http://forum.xda-developers.com/showthread.php?t=1781250
I will try what you told me and see if it will work
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
zeiloz said:
So i rebooted the bootloader, and it still gives me the same thing. Whats the command to boot.img and system .img?
Click to expand...
Click to collapse
Both the boot.img and the system.img are in the image-nakasi-jro03d.zip you must extract them first.
Then run: fastboot devices (to make sure you're connected) if it returns the serial number then proceed.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
This should maintain your data and unroot your nexus.
However, I am a bit concerned about the invalid state error. I can't find anything about it at all. I'm worried your nand might be corrupted and proceeding with this might lead to an unrecoverable state. Maybe someone else can weigh in on this... I don't want to scare you but I don't want to be responsible if something goes wrong.
hmm... I hope more people would weigh in on this? Cuz im exchanging the nexus 7 due to flickering screens, and im new to the rooting/unrooting stuff so i dont want to brick this device cuz im a n00b.
hmm... I hope someone else weigh in on this to help, cuz I'm going to exchange this nexus 7 for another 1 because of flickering issues...
Restart, carefully check
My nexus had the ghosting issue and I had to unroot my device to ship back today. Heres how I did it.
1. Download stock ROM from Google.
2. Unzip stock ROM from Google. The unzipped file will have 4 files in it. (Boot loader grouper image, flash all.sh, flash base.sh and the image.zip)
3. Unlock your device by clicking the unlock button on nexus root toolkit
4. When your device wakes turns on set it back up. No need to log into Google.
5. turn a dB back on in development
6. Click flash stock + unroot
7. click other/browse
8. For choice click I did this already.
9. Click OK
10. browse to your unzipped file location with the 4 files in it.
11. click OK
12. Done
Sent from my Desire HD using xda premium
I'm facing a similar problem.
http://forum.xda-developers.com/showthread.php?p=31128926
Did you find a way to flash the Bootloader?
I'm thinking about a hardware issue as well. Are there any Devices, with corrupted NAND's known?
Marcus
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Hello guys, i've been trying to install a custom recovery on my Nexus 4 but it has been unsuccessful all the time.
The problem is just that I can't get to boot into the custom recovery, When i flash or temporarily boot a custom recovery with fast boot (fastboot flash recovery.IMG or fastboot boot recovery.IMG) it goes without any errors, but the problem comes when its time boot into the recovery, it just stays frozen at the Google screen and then i have to do a battery pull to get out of there.
I hope you can help me guys because i cant even root my phone without a custom recovery. Ive tried rooting using the Nexus roottoolkit but it doesnt work... Apparently my phone also cant boot a custom boot.img because it also stays frozen at the google screen. My phone is unlocked...
Thanks!:laugh:
Guillermo095 said:
Hello guys, i've been trying to install a custom recovery on my Nexus 4 but it has been unsuccessful all the time.
The problem is just that I can't get to boot into the custom recovery, When i flash or temporarily boot a custom recovery with fast boot (fastboot flash recovery.IMG or fastboot boot recovery.IMG) it goes without any errors, but the problem comes when its time boot into the recovery, it just stays frozen at the Google screen and then i have to do a battery pull to get out of there.
I hope you can help me guys because i cant even root my phone without a custom recovery. Ive tried rooting using the Nexus roottoolkit but it doesnt work... Apparently my phone also cant boot a custom boot.img because it also stays frozen at the google screen. My phone is unlocked...
Thanks!:laugh:
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img not fastboot flash recoveryname.img. you have to tell it which partition it goes into.
simms22 said:
fastboot flash recovery recoveryname.img not fastboot flash recoveryname.img. you have to tell it which partition it goes into.
Click to expand...
Click to collapse
OK. I just tried that and still nothing it hangs up on the Google screen... But that can't be the problem because booting it temporarily would have worked anyways...
fastboot oem unlock
Guillermo095 said:
OK. I just tried that and still nothing it hangs up on the Google screen... But that can't be the problem because booting it temporarily would have worked anyways...
Click to expand...
Click to collapse
try it 2 or 3 times in a row
fastboot oem unlock
Sent from my Nexus 4 using xda premium
androidtoy09 said:
fastboot oem unlock
Click to expand...
Click to collapse
this, if you havent done it yet.
simms22 said:
this, if you havent done it yet.
Click to expand...
Click to collapse
It says failed because i´m already unlocked, and also tried flashing multiple times but it still stays at the google screen...
Are you getting the boot loader screen? You should see the word start in green letters at the top.
If so then you may be flashing the wrong recovery.
If you have the right one try flashing the bootloader
Sent from my Nexus 4 using xda premium
kthejoker20 said:
Are you getting the boot loader screen? You should see the word start in green letters at the top.
If so then you may be flashing the wrong recovery.
If you have the right one try flashing the bootloader
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes, the bootloader works perfectly... I´m flashing the recovery through there... I don´t think I have the wrong recovery, I downloaded it from clockworkmod.com/rommanager and I have the latest Jelly Bean 4.2.2
Guillermo095 said:
Yes, the bootloader works perfectly... I´m flashing the recovery through there... I don´t think I have the wrong recovery, I downloaded it from clockworkmod.com/rommanager and I have the latest Jelly Bean 4.2.2
Click to expand...
Click to collapse
Could you try another custom recovery like TWRP. Might be an incomplete or corrupted download as well (Check md5sum before flashing).
I would download it directly from clockworkmod. Google it.
The make sure you put it in the same folder that your fast boot is in. Rename the file to recovery.img
Then at boot loader type fastboot flash recovery recovery.img
Sent from my Nexus 4 using xda premium
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Guillermo095 said:
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Click to expand...
Click to collapse
Make sure your SDK/ADB is up to date. Older versions have issues with flashing files to the Nexus 4 that can cause your phone to get stuck at boot. If your N4 isn't booting at all, you might want to reflash the entire stock software using the download from Google's Nexus build page, after you've updated your SDK/ADB suite, just to make sure your partition tables haven't gotten messed up.
you could try downloadong the stock rom from google then flashall file.
then try to install the custom recovery after it reset
Sent from my Nexus 4 using xda premium
Guillermo095 said:
I tried both of your solutions but still nothing, I really don't understand why it doesn't allow custom recoveries :S
Click to expand...
Click to collapse
hello,
I have exactly the same problem .... what finally made?
My device now is Rooted with superSU but with no custom recovery.
I return to stock recovery (after downloading the stock rom and flash only the recovery)
bbsnick said:
hello,
I have exactly the same problem .... what finally made?
My device now is Rooted with superSU but with no custom recovery.
I return to stock recovery (after downloading the stock rom and flash only the recovery)
Click to expand...
Click to collapse
I have same problem, when i install custom recovery it goes as follows(completes without error)
boot flash recovery recovery-clockwork-touch-6.0.3.1-mako.img
sending 'recovery' (7560 KB)...
OKAY [ 0.475s]
writing 'recovery'...
OKAY [ 0.402s]
finished. total time: 0.877s
but when I try to go into custom recovery, it shoes android bot icon with back open and exclamation mark.
Then when i ran
boot boot recovery-clockwork-touch-6.0.3.1-mako.img
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
OKAY [ 0.021s]
finished. total time: 0.498s
It booted into custom recovery, but custom recovery was never installed. Any help?
1. Rename CWM to recovery.img (not recovery.img.img)
2. fastboot flash recovery recovery.img
3. fastboot reboot-bootloader
4. Done
EddyOS said:
1. Rename CWM to recovery.img (not recovery.img.img)
2. fastboot flash recovery recovery.img
3. fastboot reboot-bootloader
4. Done
Click to expand...
Click to collapse
It worked, thanks
Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks
download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.
Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app
dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.
YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app
Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk
Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help
I have a defective device and in preparing to return it, I locked the bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
I was afraid that the N9 was like the N5 & 7 with the "tamper" flag, but after some digging (and advice from others out here), I decided to restore the factory image to see if that would overwrite the image. Yes! No more big fat red "I unlocked my bootloader and may have voided my warranty" message.
I can't take credit for this, but I thought I would consolidate everything I was finding in the Q&A threads into one spot, so I put this little tutorial together. Thank you @Pilz, @jd1639 & @PhilDX for your various posts.
Step 1 - Prepare your system
[Windows]
Since your bootloader is unlocked, you probably already have ADB and fastboot, but if not, grab the SDK from here, unzip and add the "platform-tools" directory to your PATH statement
If your drivers are set up properly and your device has Android debugging enabled, connect USB and execute `adb devices` from a command prompt you should see your device listed
Download the factory image for "volantis" here
The image is double zipped, so unzip, untar, then unzip the image-volantis-lrx21q.zip file into the same directory that contains the bootloader*.img file
Step 2 - Unlock bootloader
If you locked your bootloader, unlock again:
Code:
adb reboot bootloader
fastboot oem unlock
Step 3 - Flash stock image
The flash-all.bat script is broken, so you have to do it by hand:
Open a command prompt
cd into the directory where you unzipped the factory image files
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Before rebooting, relock the bootloader:
Code:
fastboot oem lock
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Typo: fastboot oem unlock
hirndurst said:
Typo: fastboot oem unlock
Click to expand...
Click to collapse
Hahaha! Thanks.
always good to know! thanks!
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
DarthSudo said:
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
Click to expand...
Click to collapse
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Thanks for this thread. Great guide.
jd1639 said:
You could also use fastboot -w instead of the erases
Click to expand...
Click to collapse
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Thanks for this. I RMA'd my Nexus 9 and sending it back tomorrow
DarthSudo said:
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Click to expand...
Click to collapse
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
jd1639 said:
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You guys are all right. I looked back at some of my notes and I've flashed plenty of devices w/o formatting the other partitions first. Just userdata and cache. Thanks!
Hey guys, just wanted to thank you for the fixed "script". This is now my flash-stock.sh script I use whenever I need to flash a nexus device as the one delivered by google just doesn't work (reboot loop due to crashing apps on startup or "missing system.img").
Works perfect and I always like to not dirty but rather make a clean flash as it just reduces the number of possible faults .
Cheers
Creamy
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
bruce7373 said:
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
DarthSudo said:
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
Click to expand...
Click to collapse
Thx, that seems simple enough. But I made the initial system (stock) backup before I rooted. That's why I was thinking restoring that would work. I just wasn't sure about the recovery, whether the restore would put the stock recovery back or not.
Sent from my Nexus 6 using Tapatalk
DarthSudo said:
I have a defective device and in preparing to return it, I locked to bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Click to expand...
Click to collapse
Hi,
is there a way to get rid of that red message if your bootloader is locked and you cannot boot into OS?
Thanks!
EDIT* Nevermind
Hey. Sorry for reviving this thread.
I installed Remix OS on my N9 and (after discovering that performance is horrible, with ~80% RAM usage on idle) after a reboot, Remix OS won't get past it's boot splash. I am attempting to flash my device back to stock.
I never touched the bootloader (never did any 'fastboot flash bootloader ...' or anything), so it it still necessary to flash the bootloader image, or can I just flash the system.img, boot.img, vendor.img etc.?
The bootloader had never changed so there is no reason to flash it.
Sent from my Nexus 9 using XDA Free mobile app