Modified Boot Image Android L (5.0.0_LRX21P) - Nexus 7 (2013) Android Development

Guys, use this modified boot image to flash the newest Android L (5.0.0_LRX21P)
Flash in Bootloader (this is not a flashable zip)!!!!
Flash the stock root able rom, here available on xda.
Don't worry it's for our FLO device, just a name. Sorry, i was in a hurry.
Have fun

Jerome-X said:
Guys, use this modified boot image to flash the newest Android L (5.0.0_LRX21P)
Flash in Bootloader (this is not a flashable zip)!!!!
Flash the stock root able rom, here available on xda.
Don't worry it's for our FLO device, just a name. Sorry, i was in a hurry.
Have fun
Click to expand...
Click to collapse
Whats modified about it?

use this, if you want to flash the stock rooted rom via twrp etc...
if you use the stock one, your bootloader is locked after flash the stock rom

Jerome-X said:
use this, if you want to flash the stock rooted rom via twrp etc...
if you use the stock one, your bootloader is locked after flash the stock rom
Click to expand...
Click to collapse
Incorrect mate, it's still unlocked after flashing factory images. I flashed factory files yesterday and I only lost root and recovery which I expected to happen.

topgeardave said:
Incorrect mate, it's still unlocked after flashing factory images. I flashed factory files yesterday and I only lost root and recovery which I expected to happen.
Click to expand...
Click to collapse
Correct!
Op tell me exactly what you did here? Your talking about one thing but saying another. I dont get it

scrosler said:
Correct!
Op tell me exactly what you did here? Your talking about one thing but saying another. I dont get it
Click to expand...
Click to collapse
It's just the latest bootloader.img, he thinks if you flash it separately you won't lock your bootloader before flashing the stock rom via recovery.

To my knowledge, nothing locks the bootloader, except you (via fastboot or a toolkit).

So i can install the stock image i downloaded from google and still keep root? What about recovery?
Sorry for noob question, i've only used custom ROMs in the past.

If you flash the stock L image with fastboot, you lose root and recovery but your boot loader stays locked/unlocked (whatever it was before).
To get recovery back, just flash it with fastboot.
To get root back, flash the boot image from the OP or a modified kernel like ElementalX and then flash SuperSU.
Done.
Sent from my LG-D801

Thanks for the answer.

Related

Fastboot boot img

Hello all. Im new to this particular forum. I own a Galaxy Nexus, but I am unlocking/rooting my buddies One S for him. I have gone through the loops already; unlocked the bootloader, rooted, and installed custom recovery (CWM) with no issues. I was pleasantly surprised to find out that it was a snap compared to his previous HTC Legend. Nightmare.
Anyway, forgive me if this has in fact been answered as I have been searching. After a custom ROM is flashed you still have to flash a boot img via fastboot? I attempted to install CM10 yesterday and get stuck at the HTC boot screen?? Luckily I made a nandroid of the stock ROM and easily reverted. Where do I find the appropriate boot img? Is it just the img that is found in the unpacked ROM? Couldn't find anything pertaining to this in the ROM write up. I know with my Nexus you flash the ROM via recovery and that is it. Strange that you need to also flash the boot img following the ROM flash.
Any help is appreciated.
brunswick000 said:
Hello all. Im new to this particular forum. I own a Galaxy Nexus, but I am unlocking/rooting my buddies One S for him. I have gone through the loops already; unlocked the bootloader, rooted, and installed custom recovery (CWM) with no issues. I was pleasantly surprised to find out that it was a snap compared to his previous HTC Legend. Nightmare.
Anyway, forgive me if this has in fact been answered as I have been searching. After a custom ROM is flashed you still have to flash a boot img via fastboot? I attempted to install CM10 yesterday and get stuck at the HTC boot screen?? Luckily I made a nandroid of the stock ROM and easily reverted. Where do I find the appropriate boot img? Is it just the img that is found in the unpacked ROM? Couldn't find anything pertaining to this in the ROM write up. I know with my Nexus you flash the ROM via recovery and that is it. Strange that you need to also flash the boot img following the ROM flash.
Any help is appreciated.
Click to expand...
Click to collapse
Hello there, since you installed cwm recovery, you have to flash the boot.img via fastboot, if you have the twrp recovery you may not need to flash it via fastboot, it does it for you if you have an hboot under 1.14 but if its over that hboot your going to have to flash the boot.img for any Rom via fastboot. It still wouldn't hurt to flash the boot.img via fastboot but that's just me, well I hope I helped you and if I did then good, and if you wanna know more just ask...
If I helped then just press the thanks button
Sent from my One S
leohdz148 said:
Hello there, since you installed cwm recovery, you have to flash the boot.img via fastboot, if you have the twrp recovery you may not need to flash it via fastboot, it does it for you if you have an hboot under 1.14 but if its over that hboot your going to have to flash the boot.img for any Rom via fastboot. It still wouldn't hurt to flash the boot.img via fastboot but that's just me, well I hope I helped you and if I did then good, and if you wanna know more just ask...
If I helped then just press the thanks button
Sent from my One S
Click to expand...
Click to collapse
Got it to work. Thank you. :good:
brunswick000 said:
Got it to work. Thank you. :good:
Click to expand...
Click to collapse
Hi,
I was using CM10 and now I want to revert back to my previously used stock ROM. However after restoring I'm still unable to boot (I'm using ClockworkMod Touch). Do I need to flash the stock boot.img too? Where I can find it?
Thanks in advance!
TnTonly said:
Hi,
I was using CM10 and now I want to revert back to my previously used stock ROM. However after restoring I'm still unable to boot (I'm using ClockworkMod Touch). Do I need to flash the stock boot.img too? Where I can find it?
Thanks in advance!
Click to expand...
Click to collapse
Its in the rom.zip just extract it. Also look for Flash Image Gui in apps section as enables you too flash a boot.img direct from your phone whilst booted in a rom and will even extract the files for you from the new rom.zip!
Edit: Link to Flash Image Gui - http://forum.xda-developers.com/showthread.php?t=1954121
shadowch31 said:
Its in the rom.zip just extract it. Also look for Flash Image Gui in apps section as enables you too flash a boot.img direct from your phone whilst booted in a rom and will even extract the files for you from the new rom.zip!
Edit: Link to Flash Image Gui - http://forum.xda-developers.com/showthread.php?t=1954121
Click to expand...
Click to collapse
I can't find the zip file for stock HTC ROM
Anyway, I found the boot.img in the nandroid backup folder and it's all good now.
Thank you for the link! ^_^
I would also switch to TWRP. Seems to have less issues, if any, for most folks
Get it thru Goo Manager from PlayStore--

stock recovery~~~~

Hi. i cant use stock recovery.:crying:
i am looking for the stock recovery zip file p[ease.
saladink said:
Hi. i cant use stock recovery.:crying:
i am looking for the stock recovery zip file p[ease.
Click to expand...
Click to collapse
What are you trying to do with the stock recovery? Have you overwritten it with something?
sbdags said:
What are you trying to do with the stock recovery? Have you overwritten it with something?
Click to expand...
Click to collapse
tf700t booting RCK, result is 'booting failed'.
I have rooted tf700t, and installed custom rom/recovery.
but i want to return stock status.
More details please. Did you unlock your bootloader? Which firmware version was installed, and which custom recovery and ROM did you install?
_that said:
More details please. Did you unlock your bootloader? Which firmware version was installed, and which custom recovery and ROM did you install?
Click to expand...
Click to collapse
bootloader was Unlocked.
latest firmware version(JB 10.4.4.25) was installed.
Now custom rom/recovery is not installed, stock fimware was installed.
Before stock firmware was installed, tf700t had beeb rooted and installed CWM Recovery/cleanrom ODEX 3.2.
and just i coverd Stock firmware in tf700t.
So you now have:
- JB bootloader
- no working recovery
- Stock 10.4.4.25 Android, unrooted
In this situation, you need to install a recovery using fastboot from a PC via USB. The easiest way would be to first flash CWM again, then use that to install the stock recovery.
Why do you want to revert to stock firmware?
_that said:
So you now have:
- JB bootloader
- no working recovery
- Stock 10.4.4.25 Android, unrooted
In this situation, you need to install a recovery using fastboot from a PC via USB. The easiest way would be to first flash CWM again, then use that to install the stock recovery.
Why do you want to revert to stock firmware?
Click to expand...
Click to collapse
Ah~~ i sold tf700t. but buyer want perfect stock status!!
Thanx!!! But i dont have stock recovery zip file.
saladink said:
Ah~~ i sold tf700t. but buyer want perfect stock status!!
Click to expand...
Click to collapse
Not 100% possible, you cannot re-lock the bootloader. Well, in theory you can, but there is no way to get Asus warranty back.
_that said:
Not 100% possible, you cannot re-lock the bootloader. Well, in theory you can, but there is no way to get Asus warranty back.
Click to expand...
Click to collapse
I know that i cannot re-lock the bootloader.
but i just want stock firmware and stock recovery.
I flashed CWM recovery and i dont have stock recovery file......:crying:
saladink said:
I know that i cannot re-lock the bootloader.
but i just want stock firmware and stock recovery.
I flashed CWM recovery and i dont have stock recovery file......:crying:
Click to expand...
Click to collapse
Get the full firmware file from Asus and flash that via CWM ... it includes the stock recovery and will overwrite your CWM.
Hmm....ThanX
After Flashing Full stock firmware, i enter into RCK, BUT red `!` is showing again.
Sent from my SHV-E210S using xda app-developers app
saladink said:
Hmm....ThanX
After Flashing Full stock firmware, i enter into RCK, BUT red `!` is showing again.
Click to expand...
Click to collapse
The "dead android" with the red "/!\" is the normal function of the stock recovery if there is no update to install.
OMG!!!!
I really didnt know that.
I have known dead android is error or custom's problem.
Now i know that. Kkkkkk
I can explain buyer dead android's mean.
Really Thanks!!
Sent from my SHV-E210S using xda app-developers app

[Q] Error message while installing android lollipop on Nexus 5

Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.

(NEED HELP ASAP) Phone wont boot after updating Bootloader via flashify

I have to go to uni in 1 hour and updated my bootloader via flashify, now its stuck in bootloader and wont boot. TWRP is the only accesible option for me. Tried to reflash the bootloader via fast boot but nothings happening.
Bootloader : hhz11k
Rom : N5X 5.0 AOSP Ver. 5.4
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
EddyOS said:
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
Click to expand...
Click to collapse
I'm restoring right now. Doy you know why this happened? Isn't flashify able to flash the bootloader, and if that was the case, shouldn't a flash via fastboot be the solution to my problem?
Anyways thx for your quick answer!
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
EddyOS said:
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
Click to expand...
Click to collapse
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Escoban said:
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Click to expand...
Click to collapse
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Ben36 said:
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
rootSU said:
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
Click to expand...
Click to collapse
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Escoban said:
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Click to expand...
Click to collapse
Were you flashing zips instead do you mean?
rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Glad i said "le'ts google it" before going full wipe, i owe you dude.
I downloaded 5.1 radio and bootloader and flashed them using Flashify, then i got the same problem as OP. Reflashing the kernel fixed it.
*deletes Flashify*

How to OTA upgrade to NOF26V?

a little background information
current build: NMF260
recovery: TWRP RC1
kernel: elemental x 1.03
rooted: yes
Mods: weta audio 9.1
So I have completely forgotten how to do a manual sideload for an OTA. Could someone give me step by step, hand holding instructions?
What I have downloaded onto PC
sailfish-ota-nof26v -4bbb310d.zip
twrp-3.0.2-0-RC1-fastboot-sailfish.img
boot.img from nof26v build (that is for recovery right?)
and i have twrp zips for supersu, elemental x, and twrp rc1
basically i forgot how to flash stock recovery, because I need to to manually update OTA right? also do I need to remove the weta audio 9.1 mod first before doing the OTA? or can i just flash over it? anyone know?
Thanks!
https://developers.google.com/android/images <---- Click Full OTA update and follow instructions. Will not wipe anything. You do need to be on official.
If you want to just flash the peices download all of them and boot into bootloader then use fastboot commands per each item. Google the commands for bootloader, radio and the kind. Very easy.
cstrife999 said:
https://developers.google.com/android/images <---- Click Full OTA update and follow instructions. Will not wipe anything. You do need to be on official.
If you want to just flash the peices download all of them and boot into bootloader then use fastboot commands per each item. Google the commands for bootloader, radio and the kind. Very easy.
Click to expand...
Click to collapse
hey thanks but I have TWRP recovery, those instructions are if youre on stock recovery. do you know how to get back onto stock recovery?
With the OTA zip flash the recovery using command.. flash recovery (recovery name.zip)
cstrife999 said:
With the OTA zip flash the recovery using command.. flash recovery (recovery name.zip)
Click to expand...
Click to collapse
where can we get the stock recovery.img?
that is not in the ota.zip file and neither in the full factory image zip file
I'm not rooted but since no one answered as of yet then I do believe stock recovery is now in the boot.img file. Search the Pixel XL forums too.
Stock recovery is in the OTA under boot.
kazemitsui said:
hey thanks but I have TWRP recovery, those instructions are if youre on stock recovery. do you know how to get back onto stock recovery?
Click to expand...
Click to collapse
No need for stock recovery. TWRP has a sideload option. Check my guide here.
spiller37 said:
No need for stock recovery. TWRP has a sideload option. Check my guide here.
Click to expand...
Click to collapse
thanks ill remember that for future uses, i used skipsoft to reflash stock recovery and all that.

Categories

Resources