So I forgot to backup my stock kernel before flashing franco R23. Can I just extract the boot.img from the update.zip? I'm on LMY47M. Thanks!
chrisbo4 said:
So I forgot to backup my stock kernel before flashing franco R23. Can I just extract the boot.img from the update.zip? I'm on LMY47M. Thanks!
Click to expand...
Click to collapse
yes, assuming that's the build your are running.
flash using fastboot:
fastboot flash boot boot.img
you'll have to root again after, if desired.
PhilDX said:
yes, assuming that's the build your are running.
flash using fastboot:
fastboot flash boot boot.img
you'll have to root again after, if desired.
Click to expand...
Click to collapse
Thanks! I'll give that a try.
It depends what you mean bybuodste.zip. if you mean OTA then no but you can normally get it from the factory images but there isn't one for M so you'll need to find the rooted ROM.zip and extract it from there.
rootSU said:
It depends what you mean bybuodste.zip. if you mean OTA then no but you can normally get it from the factory images but there isn't one for M so you'll need to find the rooted ROM.zip and extract it from there.
Click to expand...
Click to collapse
^^^ this guy is right, I read the OP too quickly and missed the part about update.zip, I just assumed that we were talking about factory images.
I don't think the boot.img changed after D (including E, M and I), but a little digging around should verify that.
factory images are here:
https://developers.google.com/android/nexus/images
whatever you do, do not attempt to relock your boot loader (should you want to for some reason) until everything is working properly.
PhilDX said:
I don't think the boot.img changed after D (including E, M and I), but a little digging around should verify that.
Click to expand...
Click to collapse
Good point.
Could download the OTA files and run an md5sum on all the boot patches. If they match in each, they're patching kernel identically and the factory image version for any 5.1 would be appropriate.
Related
Have at it boys!
http://dl.google.com/dl/android/aosp/nakasi-lrx21p-factory-93daa4d3.tgz
MD5: e68948c23c918436680bd28fc6aaf983)
http://goo.gl/aYbCwf
IM guessing we can flash only system and boot...since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
ADB and Fastboot files attached below, if needed.
Mikey said:
IM guessing we can flash only system and userdata....since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
ADB and Fastboot files attached below, if needed.
Click to expand...
Click to collapse
Don't think that radio needs to be flashed on the N7
Cheers
Tom
I wouldn't flash the recovery partition, either.
The recovery-from-boot.p is in /system. I renamed it before the first boot using TWRP's file manager. I also flashed supersu. It's booting now...need to get to bed, though. Will report tomorrow.
Edit: Boot is successful. L.
Edit: This is my first go around with L. The checking for updates thing at sign on is interesting.
Flashed via fastboot and setting up now. I will report back with initial results and fire away any question you may want specifically answered.
FYI, first boot took about 6 minutes...
tom1807 said:
Don't think that radio needs to be flashed on the N7
Cheers
Tom
Click to expand...
Click to collapse
there is no radio in this....its wifi only....... the commands are generic
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
brizey said:
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
Click to expand...
Click to collapse
Probably needs a patch like for the N9.
Cheers
Tom
tom1807 said:
Probably needs a patch like for the N9.
Cheers
Tom
Click to expand...
Click to collapse
brizey said:
Hmmm...I am not getting supersu to work. Flashing the 2.16 zip in TWRP. The app says the binary is not installed.
Click to expand...
Click to collapse
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
Yep...thanks.
Hmmm...this is not all that useful without Titanium. Will go back to KK in the AM and wait for a patched kernel.
Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
Have to try probably, not sure whether this will run on a newer build of Lollipop
Cheers
Tom
Kernel version?
Any major differences than the couple of versions built from source?
Fyi, you will probably need SuperSU beta 2.19 and modified boot image for root. There is a titanium backup that works with l (beta). There may be a command that reflashes stock recovery on reboot (it's in /system /bin).
Tibu:
https://docs.google.com/file/d/0Bwj2Hf45t6uMSElfSXR6YXdVdVU/edit?usp=docslist_api
SuperSU:
http://forum.xda-developers.com/showthread.php?t=2868133
Nexus 7 5.0
Mikey said:
http://www.ibtimes.co.uk/chainfire-releases-quick-root-fix-android-5-0-lollipop-preview-builds-how-install-1470680
https://plus.google.com/+Chainfire/posts/ZzXaU1W7Uzm
Click to expand...
Click to collapse
tom1807 said:
Have to try probably, not sure whether this will run on a newer build of Lollipop
Cheers
Tom
Click to expand...
Click to collapse
Not good, the Boot.img is for Nexus 7 (2013)
Hangs at the Google logo.
Back to original Boot.img
Cheers
Tom
Mikey said:
IM guessing we can flash only system and boot...since the bootloader is the same. Plus, we don't wanna reflash the factory recovery.
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
Can I use these steps to clean flash the factory image?
I want to wipe everything and start from a fresh and clean flash.
I haven't flashed a factory image for a long time so I'm out of shape ?
Could someone make a flashable zip for multirom or normal flashing. ?
Nexus Root Toolkit
has anyone tried flashing this via nexus root toolkit? that software recently goot updated to 1.9.3 and has the abiloity to flash the Lollipop factory preview on those devices that got it.
That is exactly way I did. Started fresh and running smooth so far!
I used the toolkit to flash latest TWRP but that was all.
qualitymove13 said:
Flashed via fastboot and setting up now. I will report back with initial results and fire away any question you may want specifically answered.
FYI, first boot took about 6 minutes...
Click to expand...
Click to collapse
I was just going to ask about the boot time lol taking forever
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?
RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way
RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache
I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.
I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse
I rooted my Nexus 6 a while ago, bootloader is also unlocked (obviously) and I flashed a custom recovery, the rest remained stock. Now I got the update for 5.1.1 ota but it wouldn't let me install it, not even with the stock recovery (which I flashed later again) because it said something like it expected something different in some system-file. So I backed everything up and tried flashing the whole firmware from the google servers using the flash-all.bat. It flases the bootloader and also the radio, but then it says:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778975696 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I understand that I can flash everything manually and it also works, but what if I get another ota update someday? I won't be able to install it ota, will I? I'll need to flash it manually again then, right? Is there any other way to kinda 'force-flash' the stock firmware?
Thanks in advance for yout help!
Cheetah1024
Cheetah1024 said:
I rooted my Nexus 6 a while ago, bootloader is also unlocked (obviously) and I flashed a custom recovery, the rest remained stock. Now I got the update for 5.1.1 ota but it wouldn't let me install it, not even with the stock recovery (which I flashed later again) because it said something like it expected something different in some system-file. So I backed everything up and tried flashing the whole firmware from the google servers using the flash-all.bat. It flases the bootloader and also the radio, but then it says:
I understand that I can flash everything manually and it also works, but what if I get another ota update someday? I won't be able to install it ota, will I? I'll need to flash it manually again then, right? Is there any other way to kinda 'force-flash' the stock firmware?
Thanks in advance for yout help!
Cheetah1024
Click to expand...
Click to collapse
Flash-all doesn't work. All you need to do is flash the system image and boot image if you've unencrypted or switched kernels. You won't lose your data this way.
Evolution_Tech said:
Flash-all doesn't work. All you need to do is flash the system image and boot image if you've unencrypted or switched kernels. You won't lose your data this way.
Click to expand...
Click to collapse
Oh, so it's normal that flash-all doesn't work?
Cheetah1024 said:
Oh, so it's normal that flash-all doesn't work?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Alright, that' good news ... at least somehow xD
So if i flash every single image via fastboot it would be stock and I would be able to install ota's again?
Cheetah1024 said:
Alright, that' good news ... at least somehow xD
So if i flash every single image via fastboot it would be stock and I would be able to install ota's again?
Click to expand...
Click to collapse
Yes, but why? Just flash the system and boot images of the latest version also if an updated bootloader and radio, flash those too. No need for OTA's on a Nexus.
Evolution_Tech said:
Yes, but why? Just flash the system and boot images of the latest version also if an updated bootloader and radio, flash those too. No need for OTA's on a Nexus.
Click to expand...
Click to collapse
You're right... So personal stuff and app data will only be deleted, if I wipe it or if I flas userdata.img, right?
Cheetah1024 said:
You're right... So personal stuff and app data will only be deleted, if I wipe it or if I flas userdata.img, right?
Click to expand...
Click to collapse
Yes.
Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Alright, you helped me big time mate! Thank You! :laugh:
Go easy....
Wanting to flash some of the newer M ROMs.
Requirements are latest radio, boot loader and TWRP
How do I change those?
I'm root and twrp installed. Are there zips to flash in recovery 1st?
Steps or even a video would be HUGE, and thank you for helping.
The information is everywhere. You have to flash the radio/bootloader in fastboot mode. You can't flash them in recovery.
SirBindy said:
The information is everywhere. You have to flash the radio/bootloader in fastboot mode. You can't flash them in recovery.
Click to expand...
Click to collapse
I beg to differ :
http://forum.xda-developers.com/showthread.php?t=3066052
This is how i did it, in recovery.
It's all just an illusion
robfromga said:
Go easy....
Wanting to flash some of the newer M ROMs.
Requirements are latest radio, boot loader and TWRP
How do I change those?
I'm root and twrp installed. Are there zips to flash in recovery 1st?
Steps or even a video would be HUGE, and thank you for helping.
Click to expand...
Click to collapse
I was in a similar situation, I have MultiRom, and I wanted to preview M out without getting rid of PureNexus. So this is what I did
Download factory image for M
Make sure you have the latest android SDK!!!
extract the factory image
rename bootloader file to bootloader.img; rename radio file to radio.img
connect your device and reboot into bootloader
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
then reboot your phone, and you are good
if you are uncertain about it, take a look at flash-base.sh, or flash-all.bat, and follow those steps.
most bootloaders and radios ARE available via a flashable zips that can be flashed via twrp, you just have to look for them. otherwise, fastboot is very easy.
I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?
robfromga said:
I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?
Click to expand...
Click to collapse
If you flashed the marshmallow radio, the baseband should end in .27r.
It's all just an illusion
robfromga said:
I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?
Click to expand...
Click to collapse
i dont think you can flash the bootloader via flashify.
Does flashing marshmallow factory image not update the boot loader and radio with it ? Ie flashing marshmallow from NRT toolkit ?
bigup7 said:
Does flashing marshmallow factory image not update the boot loader and radio with it ? Ie flashing marshmallow from NRT toolkit ?
Click to expand...
Click to collapse
if you flash the whole thing it does.
simms22 said:
if you flash the whole thing it does.
Click to expand...
Click to collapse
Ahh great. Had me confused for a bit
bigup7 said:
Ahh great. Had me confused for a bit
Click to expand...
Click to collapse
if youre rooted, and dont want to go through the process again, and dont want to lose your data, all you have to do is flash the boot.img and the system.img to update the rom. and then reflash supersu in twrp
Right baseband?
robfromga said:
Right baseband?
Click to expand...
Click to collapse
That's what I have. You should be good.
It's was all just an illusion
Sweet!
So if I'm understanding everything, I'm now on the latest update of TWRP ,bootloader and radio....so its OK to flash M?
Yep
It's was all just an illusion
The only .zip I can find already has a modified boot.img that is rooted. I'm looking for a bone stock one so that I can apply the H21120x OTA via TWRP. (I guess I Could just write out the boot.img update from the updater-script).
Anyone have a copy of this from their device or a way to get it from a KDZ?
pizzaboy192 said:
The only .zip I can find already has a modified boot.img that is rooted. I'm looking for a bone stock one so that I can apply the H21120x OTA via TWRP. (I guess I Could just write out the boot.img update from the updater-script).
Anyone have a copy of this from their device or a way to get it from a KDZ?
Click to expand...
Click to collapse
i think you can using ext2explore-2.2.71 you can then get boot.
raptorddd said:
i think you can using ext2explore-2.2.71 you can then get boot.
Click to expand...
Click to collapse
That worked!
I'd also recommend not doing it the way I did (modifying the update.zip and flashing stock boot.img) it seems to have broken Bluetooth.
raptorddd said:
i think you can using ext2explore-2.2.71 you can then get boot.
Click to expand...
Click to collapse
I was able to get a H81120V boot.img extracted from the kdz, but it looks like flashing the update.zip through TWRP breaks bluetooth.
pizzaboy192 said:
I was able to get a H81120V boot.img extracted from the kdz, but it looks like flashing the update.zip through TWRP breaks bluetooth.
Click to expand...
Click to collapse
sorry i just extract and flash ive never modified boot.