Related
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!
How to get Stock kernel back to get nexus 7 ota updates
i once used DR BEATS audio mod it is not installed now but still i cannot install OTA update which i still repent installing that mod
The easiest way for you would be to do the update manually:
- Get the factory image and extract the following files:
- bootloader-grouper-4.23.img
- boot.img
- system.img
If you want to keep root, get
- UPDATE-SuperSU-v1.51.zip
and copy it to /sdcard and be sure, that you have a custom recovery installed.
Do a nandroid backup before starting and then do a
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
reboot into recovery and flash UPDATE-SuperSU-v1.51.zip
Do a reboot system and, congrats, you should be on Android 4.3 without loosing any data.
AndDiSa said:
The easiest way for you would be to do the update manually:
- Get the factory image and extract the following files:
- bootloader-grouper-4.23.img
- boot.img
- system.img
If you want to keep root, get
- UPDATE-SuperSU-v1.51.zip
and copy it to /sdcard and be sure, that you have a custom recovery installed.
Do a nandroid backup before starting and then do a
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
reboot into recovery and flash UPDATE-SuperSU-v1.51.zip
Do a reboot system and, congrats, you should be on Android 4.3 without loosing any data.
Click to expand...
Click to collapse
Can you guide me how to fastboot flash is it in cwm custom recovery or i need to do that with wugfresh toolkit
Sent from my Nexus 7 using Tapatalk HD
Neither you need a PC to do it. Read about both adb and fastboot instead of having everything spoon fed. That way when something goes wrong you have some idea what to do.
Sent from my Nexus 7 using Tapatalk 4 Beta
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
Hi Guys...
My nexus 4 Stocked on logo last friday, I try to recovery, wipe cache, and nothing.
So I learn that some devices of Nexus 4 after update to 4.4 are having this problem.
By the way I try to flashtool on a 4.3 version, the system was installed, but I am still stocked on logo...
Anyone have any Idea, how I can fix this?
I have no access to adb, only by flashtool
here are the way that I installed the old stock version:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader D:\Nexus\SDK\android-sdk-windows\platform-tools\bootloader-mako-makoz20i.img
fastboot reboot botloader
fastboot flash radio D:\Nexus\SDK\android-sdk-windows\platform-tools\radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot bootloader
fastboot -w update D:\Nexus\SDK\android-sdk-windows\platform-tools\image-occam-jwr66y.zip
Thanks btw
Have you done a factory reset in the stock recovery?
Sent from my Nexus 5 using XDA Free mobile app
I tried to wipe cache and delete all user data, but nothing works.
I read on net that I have to be pressing the volume(-) button on google animation to make a factory reset, this never worked for me....
I was thinking in install a custom firmware to try to fix this...
Do I have to hcange the bootloader, or a stock bootloader will be enough...
for example I wanna try this:
[ROM] NEXUS 5 PORT 4.4.2 KOT49H odexed 10/12/2013
http://forum.xda-developers.com/nexus-4/development/rom-nexus-5-port-4-4-2-kot49h-odexed-10-t2507021
But the problem that as my nexus are not working I have no access to adb commands, so how I can fix that?
Just by now i was able to sideload to flash my phone
So I tried a old 4.2.2 google version.
But I have a failure:
" Signature verification failed"
Why this failure happens if I am using a oficial stock from google?
Dark_Hyoga said:
Just by now i was able to sideload to flash my phone
So I tried a old 4.2.2 google version.
But I have a failure:
" Signature verification failed"
Why this failure happens if I am using a oficial stock from google?
Click to expand...
Click to collapse
Are you trying to flash a rom in the stock recovery? It won't work, you need a custom recovery. You can try to install a custom recovery by flashing an image file in fastboot. Or you can flash the factory image in fastboot and start all over. I'm not sure what stage your device is on right now
Sent from my Nexus 5 using XDA Free mobile app
I installed the most old version 4.2.2 of stock version by flash mode, I dont know why, but on versions 4.3 and 4.4 the precess always stops on some part of the flastool.. thats why I try the sideload.
4.2.2 was ok,
now I finally get over the stuck logo and can access the phone, but the phone its nothing find the network, But I am still working on it.
Now I understand Why......
I lost my IMEi on the process
*#06# shows no IMEI...
Now I have to find a tool to burn the IMEI again...
Anyone knows some, I just find the OCtoplus, but I have to buy....
There is one free?
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L