Database Users

[Q] Is there a way to be flash the 4.3 OTA and still be rooted?

I am having some issues with an AOSP 4.3 rom. I would like to stay on 4.3 but with the complete stock rom directly from Google. Is it possible to have root on the ota stock 4.3 rom? I would rather be back on 4.2.2 stock/rooted than rooted 4.3 with too many glitches

Due to some security changes in 4.3 root won't survive an OTA. You'll need the stock recovery to update via OTA. Subsequently, you'll need a custom recovery to flash the latest version of SuperSU and have root again.
What's your current state?

Mercado_Negro said:
Due to some security changes in 4.3 root won't survive an OTA. You'll need the stock recovery to update via OTA. Subsequently, you'll need a custom recovery to flash the latest version of SuperSU and have root again.
What's your current state?
Click to expand...
Click to collapse
I'm on a rooted 4.3 AOSP ROM with TWRP 2.6.0.0. Did a regular wipe while I was 4.2.2 before I flashed. Can you flash a custom recovery on unrooted ota 4.3?

patrickjaden said:
I'm on a rooted 4.3 AOSP ROM with TWRP 2.6.0.0. Did a regular wipe while I was 4.2.2 before I flashed. Can you flash a custom recovery on unrooted ota 4.3?
Click to expand...
Click to collapse
yes. you dont need root for a custom recovery.

patrickjaden said:
I'm on a rooted 4.3 AOSP ROM with TWRP 2.6.0.0. Did a regular wipe while I was 4.2.2 before I flashed. Can you flash a custom recovery on unrooted ota 4.3?
Click to expand...
Click to collapse
Yes, you can.
Did you also flash the latest bootloader and radio? That's important, specially the radio (to avoid compatibilities issues with ROMs).

Mercado_Negro said:
Due to some security changes in 4.3 root won't survive an OTA. You'll need the stock recovery to update via OTA. Subsequently, you'll need a custom recovery to flash the latest version of SuperSU and have root again.
What's your current state?
Click to expand...
Click to collapse
Mercado_Negro said:
Yes, you can.
Did you also flash the latest bootloader and radio? That's important, specially the radio (to avoid compatibilities issues with ROMs).
Click to expand...
Click to collapse
No, that's probably why I'm having so many problems. Where can I find them? and can they be flashed in TWRP

twrp flashable. since youre on tmobile, the hybrid radios are good, thats if you want to use tmobiles lte http://forum.xda-developers.com/showthread.php?t=2087227
patrickjaden said:
No, that's probably why I'm having so many problems. Where can I find them? and can they be flashed in TWRP
Click to expand...
Click to collapse

simms22 said:
yes. you dont need root for a custom recovery.
Click to expand...
Click to collapse
So theoretically if I revert to stock 4.2.2 I can update to the OTA, then flash a custom recovery (I assume I can do that via the toolkit?), then flash the root file, I'll be good? Do I need to relock my bootloader?

patrickjaden said:
No, that's probably why I'm having so many problems. Where can I find them? and can they be flashed in TWRP
Click to expand...
Click to collapse
You can find them here:
http://forum.xda-developers.com/showthread.php?p=43528263
I'm not sure if these zip files are flashable, though.
I'd strongly suggest you to download Google's Factory Images from:
https://developers.google.com/android/nexus/images#occamjwr66v
And extract both from there to be safe (bootloader and radio images).
You won't be able to flash these images from TWRP. In this case, you'll need to use fastboot commands to flash them (but it will be safer, in my opinion).
If you're not familiar with fastboot command lines and don't have the Android ADT Bundle either please let me know, I can walk you through.
[EDIT] I found another link for the radio (a.k.a. baseband) and bootloader. Here it is:
https://www.copy.com/s/JniBu/4.3 files (mako)
I'm 100% sure these are proper versions but since they're images you'll have to flash them via fastboot.

Mercado_Negro said:
You can find them here:
http://forum.xda-developers.com/showthread.php?p=43528263
I'm not sure if these zip files are flashable, though.
I'd strongly suggest you to download Google's Factory Images from:
https://developers.google.com/android/nexus/images#occamjwr66v
And extract both from there to be safe (bootloader and radio images).
You won't be able to flash these images from TWRP. In this case, you'll need to use fastboot commands to flash them (but it will be safer, in my opinion).
If you're not familiar with fastboot command lines and don't have the Android ADT Bundle either please let me know, I can walk you through.
[EDIT] I found another link for the radio (a.k.a. baseband) and bootloader. Here it is:
https://www.copy.com/s/JniBu/4.3 files (mako)
I'm 100% sure these are proper versions but since they're images you'll have to flash them via fastboot.
Click to expand...
Click to collapse
I've never really done fastboot before. Is this way easier than flashing stock 4.2.2 and going from there?

patrickjaden said:
I've never really done fastboot before. Is this way easier than flashing stock 4.2.2 and going from there?
Click to expand...
Click to collapse
No, it's not easier at all but you'll learn a lot in the process which will surely help you a lot in the future if you run into problems.
It's up to you

Mercado_Negro said:
No, it's not easier at all but you'll learn a lot in the process which will surely help you a lot in the future if you run into problems.
It's up to you
Click to expand...
Click to collapse
I kinda wanna revert to 4.2.2 and OTA update to 4.3 so I can be 100% stock. I don't know if I can trust the dev who's making this AOSP ROM. Does my bootloader need to be locked to update?

bootloader will need to be unlocked. thats easy, you dont need a toolkit, you wont learn anything that way. you will need to install fastboot to your computer. you boot into your bootloader, connect to your computer via usb, start fastboot, open a command window, type.. fastboot devices(this is to check if fastboot sees your device), then type.. fastboot oem unlock(then look at your n4 screen to press yes or no). this will unlock your bootloader. download your recovery to your computer, stick it into the same folder as fastboot(do this before you start), then type in the command window.. fastboot flash recovery recoveryname.img(this will flash your custom recovery). then, in the bootloader, press your volume keys to scroll to the word recovery, press your power button to boot into recovery.

patrickjaden said:
I kinda wanna revert to 4.2.2 and OTA update to 4.3 so I can be 100% stock. I don't know if I can trust the dev who's making this AOSP ROM. Does my bootloader need to be locked to update?
Click to expand...
Click to collapse
No, you don't need a locked bootloader to update via OTA.
Out of curiosity, how are you going to revert to 4.2.2 if you've never used fastboot command lines? You're in an AOSP 4.3 ROM right now, with 4.2.2 bootloader and radio. Do you have a flashable 4.2.2? That's the only way I can see it happen (unless I'm missing something which is probable).

Mercado_Negro said:
No, it's not easier at all but you'll learn a lot in the process which will surely help you a lot in the future if you run into problems.
It's up to you
Click to expand...
Click to collapse
Mercado_Negro said:
No, you don't need a locked bootloader to update via OTA.
Out of curiosity, how are you going to revert to 4.2.2 if you've never used fastboot command lines? You're in an AOSP 4.3 ROM right now, with 4.2.2 bootloader and radio. Do you have a flashable 4.2.2? That's the only way I can see it happen (unless I'm missing something which is probable).
Click to expand...
Click to collapse
Could I use the toolkit/is it usable with 4.3? Or is there a way to flash the stock via recovery?

patrickjaden said:
Could I use the toolkit/is it usable with 4.3? Or is there a way to flash the stock via recovery?
Click to expand...
Click to collapse
I'd never suggest any toolkit because you won't learn anything from it. I'm not sure how's current state of toolkits so I can't comment on their proper functioning with 4.3.

Mercado_Negro said:
I'd never suggest any toolkit because you won't learn anything from it. I'm not sure how's current state of toolkits so I can't comment on their proper functioning with 4.3.
Click to expand...
Click to collapse
Okay, is there a 4.2.2 zip I can flash that will let me get the OTA?

patrickjaden said:
Okay, is there a 4.2.2 zip I can flash that will let me get the OTA?
Click to expand...
Click to collapse
Sorry, I don't know if there's one.

is it possible to flash a hybrid radio onto stock 4.3?

patrickjaden said:
is it possible to flash a hybrid radio onto stock 4.3?
Click to expand...
Click to collapse
Yes, it is. You can pretty much flash any baseband on stock or ROMs. The question is, is it worth it? It may work flawlessly but it could also cause issues. I'd do it but I'd keep my eyes on it if something goes wrong all of a sudden.

Flashable Factory Image zips - Android 5.0 LRX21P

This is essentially the Nexus 7 2013 WiFi's factory stock image in flashable zip format, so you can flash the device back to factory stock using CWM or TWRP, without having to rely on fastboot. It is useful for people who broke their USB port, but still have custom recovery. Or messing with roms on the go and wanting to return to stock without having access to a computer.
Included are separate zip files that will flash specific partitions of the device. To have a complete stock form of the device and preventing any issues, make sure you flash all zip files. More advance users can choose to only flash specific partitions to suit their needs.
>>> DOWNLOAD: razor_lrx21p_stock_flashable_zips <<<​
Flash instruction (Important):
0. (optional) Create a full nandroid backup before flashing is recommended.
1. To have a working and stable OS, make sure you flash all the zip files, unless you know what you're doing.
2. To prevent serious incompatibilities, do a factory reset if you are coming from KitKat or from a custom rom. I would only skip doing a factory reset if the device is already running stock Lollipop.
Note: If you do not want to erase your custom recovery, do not flash the "recovery.zip", this will return your custom recovery back to stock.
I have tested flashing these multiple times with my Nexus 7 WiFi 32gb with no issues. Before proceeding with flashing, each zip files will check to make sure if the device is a Nexus 7 2013 WiFi (flo), so it won't allow you to accidentally flash on a wrong device.
If you have any issues after flashing these, even after factory resetting, follow this guide to use fastboot instead to return the device to stock.
MD5 Checksum:
File: razor_lrx21p_boot.zip
MD5: 9c12f5f7a83facf80cf596a6de1187ab
File: razor_lrx21p_bootloader_4.04.zip
MD5: 818864adb28b3559fd9d7107115de57c
File: razor_lrx21p_ddr.zip
MD5: d4ee8ae2ec00a37dc9af589cee87f9e0
File: razor_lrx21p_recovery.zip
MD5: 86d2f2d8b784ee108153b0606220040f
File: razor_lrx21p_system.zip
MD5: a0d5c8ce8fbaadc2c304f1f78e9bd6cc

Thanks a lot.
I am currently using Cleanrom. I have download the stock rooted Lolipop, and wish to flash that. It was said in that thread, that I need the latest bootloader. So from the zip file above, should I only flash the bootloader and then flash L? Or would it not make a difference if I flashed all the zips (besides the recovery)?
No, I do not want to get rid of my custom recovery. I am using the latest version of TWRP

Flashed with TWRP, works well. Thanks a lot!
eksasol said:
This is essentially the Nexus 7 2013 WiFi's factory stock image in flashable zip format, so you can flash the device back to factory stock using CWM or TWRP, without having to rely on fastboot. It is useful for people who broke their USB port, but still have custom recovery. Or messing with roms on the go and wanting to return to stock without having access to a computer.
Included are separate zip files that will flash specific partitions of the device. To have a complete stock form of the device and preventing any issues, make sure you flash all zip files. More advance users can choose to only flash specific partitions to suit their needs.
>>> DOWNLOAD: razor_lrx21p_stock_flashable_zips <<<​
Flash instruction (Important):
0. (optional) Create a full nandroid backup before flashing is recommended.
1. To have a working and stable OS, make sure you flash all the zip files, unless you know what you're doing.
2. To prevent serious incompatibilities, do a factory reset if you are coming from KitKat or from a custom rom. I would only skip doing a factory reset if the device is already running stock Lollipop.
Note: If you do not want to erase your custom recovery, do not flash the "recovery.zip", this will return your custom recovery back to stock.
I have tested flashing these multiple times with my Nexus 7 WiFi 32gb with no issues. Before proceeding with flashing, each zip files will check to make sure if the device is a Nexus 7 2013 WiFi (flo), so it won't allow you to accidentally flash on a wrong device.
If you have any issues after flashing these, even after factory resetting, follow this guide to use fastboot instead to return the device to stock.
MD5 Checksum:
File: razor_lrx21p_boot.zip
MD5: 9c12f5f7a83facf80cf596a6de1187ab
File: razor_lrx21p_bootloader_4.04.zip
MD5: 818864adb28b3559fd9d7107115de57c
File: razor_lrx21p_ddr.zip
MD5: d4ee8ae2ec00a37dc9af589cee87f9e0
File: razor_lrx21p_recovery.zip
MD5: 86d2f2d8b784ee108153b0606220040f
File: razor_lrx21p_system.zip
MD5: a0d5c8ce8fbaadc2c304f1f78e9bd6cc
Click to expand...
Click to collapse

Flawless as usual, thanks Eksasol

Great, will do this tomorrow! Thanks
Envoyé de ma Nexus 7.2 depuis tapatalk

particular order?
Thank you very much eksasol!
Is there a particular order in which these files should be flashed?
Cheers,
Sandor

schermvlieger said:
Thank you very much eksasol!
Is there a particular order in which these files should be flashed?
Cheers,
Sandor
Click to expand...
Click to collapse
No they should all work. The phone will boot correctly as long as you have all the proper kernel (boot), system (OS) and bootloader installed.

timrock said:
Thanks a lot.
I am currently using Cleanrom. I have download the stock rooted Lolipop, and wish to flash that. It was said in that thread, that I need the latest bootloader. So from the zip file above, should I only flash the bootloader and then flash L? Or would it not make a difference if I flashed all the zips (besides the recovery)?
No, I do not want to get rid of my custom recovery. I am using the latest version of TWRP
Click to expand...
Click to collapse
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.

Marvellous!

eksasol said:
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Click to expand...
Click to collapse
Would a factory reset delete the files I have on my device? If so, the ROM is in a folder on my device.
Sent from my Nexus 7 using Tapatalk

Which one of these zips controls user data? I want to try and dirty flash, as I dont want to lose any data if I dont have to. Any suggestions?

I have not done a factory reset yet; and add away tells me the device is not rooted.
Did the update remove root, or is this one of those issues related to not doing a factory reset?
All else seems to be working at the moment.

eksasol said:
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Click to expand...
Click to collapse
So the bootloader and DDR zips can be flashed through TWRP to update the bootloader only, and then a separate rooted ROM (ie scrosler's) can be flashed through TWRP with the help of the updated bootloader?
I did try to flash the bootloader only, but it failed. The need for the DDR would explain why.
Cheers.

Thanks this is what ive been looking for.
Bought my nexus 7 2013 3weeks ago it came with 4.4.2 and i towelrooted it n flashed twrp now on a custom rom but wish i didnt coz i wanted the updates 5.0 but i dont have a pc so this is what i needed.
So if i flash all zips does that mean il be stock 5.0 and ready for future updates?
Aslo my bootloader is already 4.04 so should i stil flash the one above?
Is it possable to flash jus system+boot zips as a second rom (multirom)?

I am not going to install 5.0 yet because some of the apps I use are not yet compatible. If I just flashed the boot loader but stayed with my current ROM , cleanrom, would that be a problem?
Sent from my Nexus 7 using Tapatalk

Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?

James_Feltham said:
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
Click to expand...
Click to collapse
Hi James,
You'll need to re-root your device after you flashed these images.
CF-Autoroot will help you here; click.
You'll need to reinstall your custom bootloader as well if the stock bootloader does not meet your requirements.

timrock said:
Would a factory reset delete the files I have on my device? If so, the ROM is in a folder on my device.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It depends, for normal Android devices, if you factory reset using stock recovery it will wipe everything in the device. For TWRP and CWM, if you factory reset it will leave your internal storage alone.
MWFD said:
Which one of these zips controls user data? I want to try and dirty flash, as I dont want to lose any data if I dont have to. Any suggestions?
Click to expand...
Click to collapse
None of them control userdata, I excluded that partition image. If you want to dirty flash, just don't do a factory reset or wipe your /data folder.
toonarmy4life said:
Thanks this is what ive been looking for.
Bought my nexus 7 2013 3weeks ago it came with 4.4.2 and i towelrooted it n flashed twrp now on a custom rom but wish i didnt coz i wanted the updates 5.0 but i dont have a pc so this is what i needed.
So if i flash all zips does that mean il be stock 5.0 and ready for future updates?
Aslo my bootloader is already 4.04 so should i stil flash the one above?
Is it possable to flash jus system+boot zips as a second rom (multirom)?
Click to expand...
Click to collapse
Do not flash these zip as a secondary rom for multirom, this is meant to flash for the entire device only. This is factory images, not roms. You could download some type of stock based roms and use it with multirom instead. If you have the latest bootloader you don't need to flash it again, but it won't hurt if you do. Yes, flashing all the zips and factory resetting will return the device to stock.
timrock said:
I am not going to install 5.0 yet because some of the apps I use are not yet compatible. If I just flashed the boot loader but stayed with my current ROM , cleanrom, would that be a problem?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That should not be any problem.
James_Feltham said:
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
Click to expand...
Click to collapse
Because this is Android 5, it have extra security to prevent rooting like in the past. I believe to get root you need try Chainfire's CF-AutoRoot method, or use a custom kernel and flash SuperSu.
schermvlieger said:
I have not done a factory reset yet; and add away tells me the device is not rooted.
Did the update remove root, or is this one of those issues related to not doing a factory reset?
All else seems to be working at the moment.
Click to expand...
Click to collapse
This isn't an update. It is a factory image that return the device to stock form. You will lose root and every changes to the system partition in the process.

Can this file be flashed on any device??

#divy said:
Can this file be flashed on any device??
Click to expand...
Click to collapse
No only on Nexus 7 2013 WiFi 32gb

[REF] [RADIO] Nexus 6 Modem Collection | LYZ48E Radio Added

Background
This is a list of radios for the Nexus 6 (shamu). With the new OTA release, some people may have better signals with the old radio or want to tinker with the new one so here is a list that will be updated to allow users to switch to their preferred radio/modem.
Radios are independent of Android version, use the radio that provides you the best signal. It varies from user to user, there is no best radio/modem Why? Different carriers, different locations, and more. There are so many factors that play into cellular signal so just because a particular radio is the best for someone doesn't mean its the best for you. We can obtain a consensus on which radio performs the "best" for the largest % of users though.
How to Flash?
1) Fastboot: Download the .img file below then flash it using Fastboot.
Code:
fastboot flash radio radio.img
Download (newest on top)
MPZ79M ("M" Developer Preview 2 - 07/10/2015)
MDM9625_104651.11.05.17R - flashable zip
Download: https://www.androidfilehost.com/?fid=24052804347771581
MPZ44Q ("M" Developer Preview - 05/28/2015)
MDM9625_104651.11.05.16R - flashable zip
Download: https://www.androidfilehost.com/?fid=23991606952615113
LYZ48E (5.1.1 T-Mobile - Extracted from OTA - 05/23/2015)
MDM9625_104649.09.05.14R - flashable zip
Download: https://www.androidfilehost.com/?fid=23991606952608807
LMY47D (5.1.0 Verizon - Extracted from factory image)
MDM9625_104446.01.02.98R -- fastboot
Download: https://www.androidfilehost.com/?fid=95916177934543195
LMY47D (5.1.0 OTA - 03/11/2015):
MDM9625_104446.01.02.95R -- flash in TWRP
Download: https://www.androidfilehost.com/?fid=95916177934540317
LRX22C (5.0.1 OTA - 12/10/2014): MDM9625_104335.118.02.55.04R
Download: https://www.androidfilehost.com/?fid=95851939534733360
LRX21O (5.0.0 OTA - XX/XX/2014): MDM9625_104335.118.02.55.03R
Download: https://www.androidfilehost.com/?fid=95851939534733359

great, needed, thread :good:

Nice job zephik
Sent from my NEXUS 6

Can you do fastboot method with terminal emulator...just broke pc lol

cwalker0906 said:
Can you do fastboot method with terminal emulator...just broke pc lol
Click to expand...
Click to collapse
No. Fastboot is only for the computer.
I'll have to do flashable zips later, if someone beats me to it I'll include it in OP and give credits.
Currently preparing for finals and this is all the time I have for now.
You'd need to write the radio to /dev/block/platform/msm_sdcc.1/by-name/modem via updater-script.

I thought it was "fastboot flash radio radio.img" ? (that's what I used)

Neejay said:
I thought it was "fastboot flash radio radio.img" ? (that's what I used)
Click to expand...
Click to collapse
Rename the file you downloaded from OP to "radio.img" (ensure its not actually radio.img.img).
Or type fastboot flash radio the-whole-radio-name.img. I personally rename to radio as its easier for me to type.

zephiK said:
Rename the file you downloaded from OP to "radio.img" (ensure its not actually radio.img.img).
Or type fastboot flash radio the-whole-radio-name.img. I personally rename to radio as its easier for me to type.
Click to expand...
Click to collapse
Yeah, I did the whole location+name, but in the OP you have "fastboot flash modem <name-of-modem>.bin" I wasn't sure if I was missing something, as I've never seen a .bin referenced. Hopefully this doesn't come off as being an asshole, I was just genuinely curious.

Neejay said:
Yeah, I did the whole location+name, but in the OP you have "fastboot flash modem <name-of-modem>.bin" I wasn't sure if I was missing something, as I've never seen a .bin referenced. Hopefully this doesn't come off as being an ******, I was just genuinely curious.
Click to expand...
Click to collapse
Oh you're right, I copy pasted the modem collection OP i had from the OnePlus One which they use .bin. I changed the extension to .img.
Sorry about that! its fixed now. And you're not being a... "you know", no need for me to say it as XDA doesn't appreciate that language
But yeah for <name-of-modem> is just a placeholder for depending what the user selects as a radio.

zephiK said:
Oh you're right, I copy pasted the modem collection OP i had from the OnePlus One which they use .bin. I changed the extension to .img.
Sorry about that! its fixed now. And you're not being a... "you know", no need for me to say it as XDA doesn't appreciate that language
But yeah for <name-of-modem> is just a placeholder for depending what the user selects as a radio.
Click to expand...
Click to collapse
Well I'm now soft bricked and don't know what to do. I used the "fastboot flash modem [modem name].img" command. I now realized from reading other threads I'm supposed to use "fastboot flash radio [radio name].img".
What do I do? The image fully flashed and now when I reboot it stick on the four colors swirling around splash screen just before boot up. I'm guessing there isn't a "modem" section for shamu? Just radio...
I tried going into TWRP and wiping cache. It says "E: Unable to mount '/firmware'".

xidium said:
Well I'm now soft bricked and don't know what to do. I used the "fastboot flash modem [modem name].img" command. I now realized from reading other threads I'm supposed to use "fastboot flash radio [radio name].img".
What do I do? The image fully flashed and now when I reboot it stick on the four colors swirling around splash screen just before boot up. I'm guessing there isn't a "modem" section for shamu? Just radio...
I tried going into TWRP and wiping cache. It says "E: Unable to mount '/firmware'".
Click to expand...
Click to collapse
I had the same problem with /firmware. I seem to just ignore it.
Go into fastboot and then just reflash the radio using fastboot flash radio radio.img and then reboot. If that doesn't work go back into TWRP and wipe Cache and Dalvik and then your phone should start up as it rebuilds the cache.
So far the flashable zips in the typical method I use are not sticking when it comes to the flashable zips.

xidium said:
Well I'm now soft bricked and don't know what to do. I used the "fastboot flash modem [modem name].img" command. I now realized from reading other threads I'm supposed to use "fastboot flash radio [radio name].img".
What do I do? The image fully flashed and now when I reboot it stick on the four colors swirling around splash screen just before boot up. I'm guessing there isn't a "modem" section for shamu? Just radio...
I tried going into TWRP and wiping cache. It says "E: Unable to mount '/firmware'".
Click to expand...
Click to collapse
try reflashing twrp

zephiK said:
Oh you're right, I copy pasted the modem collection OP i had from the OnePlus One which they use .bin. I changed the extension to .img.
Sorry about that! its fixed now. And you're not being a... "you know", no need for me to say it as XDA doesn't appreciate that language
But yeah for <name-of-modem> is just a placeholder for depending what the user selects as a radio.
Click to expand...
Click to collapse
zephiK said:
I had the same problem with /firmware. I seem to just ignore it.
Go into fastboot and then just reflash the radio using fastboot flash radio radio.img and then reboot. If that doesn't work go back into TWRP and wipe Cache and Dalvik and then your phone should start up as it rebuilds the cache.
So far the flashable zips in the typical method I use are not sticking when it comes to the flashable zips.
Click to expand...
Click to collapse
simms22 said:
try reflashing twrp
Click to expand...
Click to collapse
Hmm not sure which one worked but I think flashing TWRP again fixed it. I'm booted back up again and with the new modem. Thanks guys

Can we use Flashify to flash the modem image? Thanks.

slick4mitch said:
Can we use Flashify to flash the modem image? Thanks.
Click to expand...
Click to collapse
I tried thst but not sure if it worked. Can someone tell me the baseband version of the new radio please?

chris6278 said:
I tried thst but not sure if it worked. Can someone tell me the baseband version of the new radio please?
Click to expand...
Click to collapse
This is the 5.0 (LRX210) Radio
MDM9625_104335.118.02.55.03R

slick4mitch said:
Can we use Flashify to flash the modem image? Thanks.
Click to expand...
Click to collapse
Don't think you can use Flashify, that's for Zips, Recoveries and Boot Images ( Kernels )
You can use Fastboot, or if you're not comfortable with that you could use Wug's Toolkit and just download the latest modem to your PC and select Flash Modem under Advanced settings.... Select your downloaded modem file and within 1 minute the Toolkit will do it all for you.

chris6278 said:
I tried thst but not sure if it worked. Can someone tell me the baseband version of the new radio please?
Click to expand...
Click to collapse
You can't flash the radio using flashify.
The new base band ends with. 04R if it says that then you're on the newest radio.
Sent from my Nexus 6 using Tapatalk

zephiK said:
You can't flash the radio using flashify.
The new base band ends with. 04R if it says that then you're on the newest radio.
Sent from my Nexus 6 using Tapatalk[/QUOTE
Yea i know thanx
Click to expand...
Click to collapse

chris6278 said:
zephiK said:
You can't flash the radio using flashify.
The new base band ends with. 04R if it says that then you're on the newest radio.
Sent from my Nexus 6 using Tapatalk[/QUOTE
Yea i know thanx
Click to expand...
Click to collapse
Not seeing .04r , I flashed full build from Google website. Compared the 5.00 and 5.01 modems they are the same. May have done something wrong. Can anyone post a screenshot of the latest modem# .?
Click to expand...
Click to collapse

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.

In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app

nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.

nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.

MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...

nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.

v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.

nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:

@nhatminhng How did you get your phone fixed? is your phone unlocked?

tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.

nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.

tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.

tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.

v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.

v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.

7.1.2 via flashfire but?

Was rooted on stock 7.0 and SuperSu, TWRP.
Flashed latest april factory image 7.1.2 using Flashfire which went Great. Rebooted to twrp recovery and flashed pixel mod, great.
Noticed I'm still on bootloader 3.62 and radio 3.72. ? So I guess flashfire doesn't update those.
I'm on Verizon.
Do I need to update to latest bl 3.67 and radio 3.81?
By what method? Fastboot, Flashfire, TWRP
Thanks much

Born<ICs said:
Was rooted on stock 7.0 and SuperSu, TWRP.
Flashed latest april factory image 7.1.2 using Flashfire which went Great. Rebooted to twrp recovery and flashed pixel mod, great.
Noticed I'm still on bootloader 3.62 and radio 3.72. ? So I guess flashfire doesn't update those.
I'm on Verizon.
Do I need to update to latest bl 3.67 and radio 3.81?
By what method? Fastboot, Flashfire, TWRP
Thanks much
Click to expand...
Click to collapse
Hello,
Reboot to bootloader,
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Done... :good:
Cheers...

Figured fastboot works but..
Phone seems to function fine so...
Do I actually want/need to flash the latest BL & Radio?
Curious why flashfire skips over these and if it's possible to add these images separately in the flashfire sequence.
Thanks

Born<ICs said:
Figured fastboot works but..
Phone seems to function fine so...
Do I actually want/need to flash the latest BL & Radio?
Curious why flashfire skips over these and if it's possible to add these images separately in the flashfire sequence.
Thanks
Click to expand...
Click to collapse
Hello,
I keep my bootloader up to date. Because it's part of the system, maybe security flaws have been patched... If it was useless, they wouldn't release a new one.
The radio? Well, maybe it will improve your reception or maybe not. It could even be worse. Radio version doesn't matter. If you want, you can flash the new one and if you don't see an improvement, you can flash your current one back. It's up to you...
Check this: https://flashfire.chainfire.eu/settings/#flash_bootloaders
The part about flashing bootloader. Didn't see infos regarding radio though.
Cheers...

5.1 said:
Hello,
I keep my bootloader up to date. Because it's part of the system, maybe security flaws have been patched... If it was useless, they wouldn't release a new one.
The radio? Well, maybe it will improve your reception or maybe not. It could even be worse. Radio version doesn't matter. If you want, you can flash the new one and if you don't see an improvement, you can flash your current one back. It's up to you...
Check this: https://flashfire.chainfire.eu/settings/#flash_bootloaders
The part about flashing bootloader. Didn't see info's regarding radio though.
Cheers...
Click to expand...
Click to collapse
Oh, OK thanks for the link. Fastboot it is then.

There's actually someone on XDA who created a flashable zip that can be used to update the bootloader and radio through TWRP. Not being great at command lines on the computer I usually use that and have never had a problem.

OK thanks I found the post. Took a chance and downloaded the latest bootloader radio combo zip and flashed via twrp.
All good