[Q&A] [ROM] 5.0.2 Stock-ROM - LG D415 L90 - LG Optimus L90

Q&A for [ROM] 5.0.2 Stock-ROM - LG D415 L90
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] 5.0.2 Stock-ROM - LG D415 L90. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

brossovitch said:
Xposed framework crashes the phone.. Testing will not commence..
I never needed it anyway..
Click to expand...
Click to collapse
This is kind of a deal breaker for me, that and the broken rar archive. BUT when it starts working I would like to use your ROM because I love stock roms with minor modifications and debloat. Did you use this xposed framework? http://forum.xda-developers.com/showthread.php?t=3034811
When I flashed the completely stock version, it broke, no data/wifi/bluetooth, and everything crashed. I think it was because I wiped first and since this is an OTA I shouldn't have done that, but now I am worried about trying again, since I just got my phone back up and running. I must say thanks for that, because flashing using TWRP and your ROM gave me TWRP back, so I was able to downgrade back to 410c stock from your ROM. I'll wait for the radio problem to be fixed before I try again.
Hi, I'm new here, but not to android.

imonlyhumanoid said:
This is kind of a deal breaker for me, that and the broken rar archive. BUT when it starts working I would like to use your ROM because I love stock roms with minor modifications and debloat. Did you use this xposed framework? http://forum.xda-developers.com/showthread.php?t=3034811
When I flashed the completely stock version, it broke, no data/wifi/bluetooth, and everything crashed. I think it was because I wiped first and since this is an OTA I shouldn't have done that, but now I am worried about trying again, since I just got my phone back up and running. I must say thanks for that, because flashing using TWRP and your ROM gave me TWRP back, so I was able to downgrade back to 410c stock from your ROM. I'll wait for the radio problem to be fixed before I try again.
Hi, I'm new here, but not to android.
Click to expand...
Click to collapse
You can flash safely with TWRP. Go ahead and upgrade to Stock Lollipop via KDZ then you can try flashing one of brossovitch's ROM. It worked for me. Just follow this http://forum.xda-developers.com/showthread.php?t=3088131 guide if you get broken IMEI or/and Baseband. It will help you get it back as well as get Lollipop on you phone.
Good luck!

So if I read that right, you have to flash the Stock 5.0.2 using TWRP, then flash the Stock 4.4.2 using the LG Flash Tool, then flash the Stock 5.0.2 using the LG Flash Tool, then root then unlock bootloader (is that necessary with the D415? I never did that before) and then use Rashr to flash TWRP and then flash brossovitch's LollipOptimus ROM, just to get the IMEI/Baseband to work? Seems like a lot of hurdles. Why not just flash the 5.0.2 KDZ and then root and flash TWRP possibly with or without bootloader unlocking and then flash the LollipOptimus ROM, or even just flashing it like an OTA from TWRP? Will the LG Official OTA break the IMEI/Baseband?
And has anyone tried the linked Xposed framework?
Thanks for your help!

imonlyhumanoid said:
So if I read that right, you have to flash the Stock 5.0.2 using TWRP, then flash the Stock 4.4.2 using the LG Flash Tool, then flash the Stock 5.0.2 using the LG Flash Tool, then root then unlock bootloader (is that necessary with the D415? I never did that before) and then use Rashr to flash TWRP and then flash brossovitch's LollipOptimus ROM, just to get the IMEI/Baseband to work? Seems like a lot of hurdles. Why not just flash the 5.0.2 KDZ and then root and flash TWRP possibly with or without bootloader unlocking and then flash the LollipOptimus ROM, or even just flashing it like an OTA from TWRP? Will the LG Official OTA break the IMEI/Baseband?
And has anyone tried the linked Xposed framework?
Thanks for your help!
Click to expand...
Click to collapse
No, that is if you had a failed flashed and did not have Stock Download mode which you lose if you unlock the boot loader (which is technically unlocked). Unlocking bootloader is optional, I should put that.
If you have unlocked boot loader then you need to either flash the lag.img or bross's stock ROM with laf.img in it.

imonlyhumanoid said:
So if I read that right, you have to flash the Stock 5.0.2 using TWRP, then flash the Stock 4.4.2 using the LG Flash Tool, then flash the Stock 5.0.2 using the LG Flash Tool, then root then unlock bootloader (is that necessary with the D415? I never did that before) and then use Rashr to flash TWRP and then flash brossovitch's LollipOptimus ROM, just to get the IMEI/Baseband to work? Seems like a lot of hurdles. Why not just flash the 5.0.2 KDZ and then root and flash TWRP possibly with or without bootloader unlocking and then flash the LollipOptimus ROM, or even just flashing it like an OTA from TWRP? Will the LG Official OTA break the IMEI/Baseband?
And has anyone tried the linked Xposed framework?
Thanks for your help!
Click to expand...
Click to collapse
I'm going to try xposed again.
I'm also going to upload the partitions needed to make the bseband work.. There's a way to be easily flash them to go to either.
Stock lollipop is just different. And the custom roms are based on KK. so we gotta be able to go back if we want..
We can.

With L90 utilities you can flash your laf partition or toggle it between fastboot mode & s/w Upgrade (firmware download) mode.
From there you can use adb to flash the proper partitions.
IE:"fastboot flash radio modem.bin"
Which would likely work..

brossovitch said:
With L90 utilities you can flash your laf partition or toggle it between fastboot mode & s/w Upgrade (firmware download) mode.
From there you can use adb to flash the proper partitions.
IE:"fastboot flash radio modem.bin"
Which would likely work..
Click to expand...
Click to collapse
Way cool! Where is this LG L90 tool?

SamsungIsBetterThanApple said:
Way cool! Where is this LG L90 tool?
Click to expand...
Click to collapse
You're on XDA dude.....
....learning to search for and find what you want is a priority..
All I'm going to say, is........ @shinobisoft
May the Droid be with you, young Padawan....:good:

brossovitch said:
You're on XDA dude.....
....learning to search for and find what you want is a priority..
All I'm going to say, is........ @shinobisoft
May the Droid be with you, young Padawan....:good:
Click to expand...
Click to collapse
Haha! Thanks, but just you wait. Soon the student will becoms the master.

SamsungIsBetterThanApple said:
Haha! Thanks, but just you wait. Soon the student will becoms the master.
Click to expand...
Click to collapse
I truly hope so.
When I was young, we had house phones with cords..
Pulse tone hacking is all we had back then.. LOL!

Just restored your latest nandroid and is WORKING GREAT SO FAR !!! Just one thing , how did you guys get rid of the annoying t-mobile voicemail notification ?

Am new to TWRP so excuse me for asking, but since I restored back to 4.4.2 my phone is better than it was before. I would like to upgrade, but I'd like to be able to revert back to 4.4.2 if I have a bad experience. I backed up my phone with TWRP, can I flash the kdz with the LG tool, and then root and get back to TWRP and flash the ROM to make the radio work, and then back up the 5.0.2 ROM and switch between the two?

imonlyhumanoid said:
Am new to TWRP so excuse me for asking, but since I restored back to 4.4.2 my phone is better than it was before. I would like to upgrade, but I'd like to be able to revert back to 4.4.2 if I have a bad experience. I backed up my phone with TWRP, can I flash the kdz with the LG tool, and then root and get back to TWRP and flash the ROM to make the radio work, and then back up the 5.0.2 ROM and switch between the two?
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showthread.php?t=3088131 guide If you have Downlode Mode, skip step 1 and since you are on KK, skip step 3.
Sent from my LollipOptimus™

Since I cannot reply directly to the main thread or the How to fix IMEI/Baseband Unknown Issue (D415) thread, I will ask here.
I am currently running the KitKat stock and rooted, with the original laf.img and TWRP recovery, de-odexed system, and several unwanted stock apps uninstalled.
From my arrangement, to upgrade, I can go to download mode using Vol + and Plug USB (because I haven't zero'd out my laf, right?), and use the 2014 LG tool to flash the Lollipop KDZ. This will cause the data/wifi/bluetooth signals to stop working, as well as losing root and TRWP (correct me if wrong). From there I would need to root and flash back TWRP and then from TWRP flash the LP-[5.0.2]_L90_D415[boot-system-laf-aboot-modem.zip] to get the signals back.
At this point, would I then be at stock rooted lollipop with TWRP and download mode and have a useable phone? If I do a CES flash as recommended, would I lose all of my currently installed apps and data? If so, I should disable xposed first, right?

imonlyhumanoid said:
Since I cannot reply directly to the main thread or the How to fix IMEI/Baseband Unknown Issue (D415) thread, I will ask here.
I am currently running the KitKat stock and rooted, with the original laf.img and TWRP recovery, de-odexed system, and several unwanted stock apps uninstalled.
From my arrangement, to upgrade, I can go to download mode using Vol + and Plug USB (because I haven't zero'd out my laf, right?), and use the 2014 LG tool to flash the Lollipop KDZ. This will cause the data/wifi/bluetooth signals to stop working, as well as losing root and TRWP (correct me if wrong). From there I would need to root and flash back TWRP and then from TWRP flash the LP-[5.0.2]_L90_D415[boot-system-laf-aboot-modem.zip] to get the signals back.
At this point, would I then be at stock rooted lollipop with TWRP and download mode and have a useable phone? If I do a CES flash as recommended, would I lose all of my currently installed apps and data? If so, I should disable xposed first, right?
Click to expand...
Click to collapse
You WILL lose all data but you need to use CES to fix, I believe, the partitions. You DO NOT have to flash the LP-[5.02]_L90_D415[boot-system-laf-aboot-modem.zip] if you go to KK then to L using Lg Flash tool. After succesful Lolli flash, then root, install twrp, and flash one of Bross's rom.

But if I want to go to stock 5.0, with twrp and download mode intact, what do I do? Flash using LG Flash Tool, root and flash twrp and I'm done? This won't cause radio problems?

imonlyhumanoid said:
But if I want to go to stock 5.0, with twrp and download mode intact, what do I do? Flash using LG Flash Tool, root and flash twrp and I'm done? This won't cause radio problems?
Click to expand...
Click to collapse
I promise, if you follow my guide, everything will be fixed. You only lose radio if you flash something wrong. For example, flashing one of bross's ROMs while on kk. That is a bad idea. After you flash to lolli with lg flash tool, you can root and flash twrp. You WILL NOT lose Download Mode unless you zero out the laf by following the Unlocking Boot loader guide.
---------- Post added at 06:24 PM ---------- Previous post was at 06:24 PM ----------
imonlyhumanoid said:
But if I want to go to stock 5.0, with twrp and download mode intact, what do I do? Flash using LG Flash Tool, root and flash twrp and I'm done? This won't cause radio problems?
Click to expand...
Click to collapse
And PLEASE do a CES flash

Related

[Q]Unlocked Bootloader,TWRP and 4.4.2 Update

Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.
dray_jr said:
if you take the 4.4.2 update you will loose root and wont be able to get it back till who knows when.
but you need to flash your phone back to 100% stock just like you did when root your device but instead of using the 4.2.2 CU firmware use the 4.4
here is all the firmware for the Moto X
http://sbf.droid-developers.org/phone.php?device=0
your device is a Att model so you should be able to flash the ATT 4.4 firmware but im not 100% sure but maybe you will find your carrier listed there.
Click to expand...
Click to collapse
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy
msespindola said:
yeah,i know,aware of loosing root,but,mine is retail,and i've found the brazilian retail one(Blur_Version.143.44.8.ghost_row.Brasil.en.BR)!
How do i revert back to stock?never done that before!
Thx for the help so far buddy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.
dray_jr said:
http://forum.xda-developers.com/showthread.php?t=2446515
there are two ways in this guide i like the manual way. but your choice make sure you read everything because if you do this wrong you can brick.
Click to expand...
Click to collapse
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?
msespindola said:
Okay buddy,will take a look when i get home from work!
One questiona buddy managed to get the fastboot img for me,if i just flash the stock recovery img and then try to update will it work?
Click to expand...
Click to collapse
idk i dont like to doing things half way there have been way to many bricks lately.
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
this is why i dont read on my phone i miss crap anyway if you flash 4.4.2 yes you can flash the 4.4 TWRP and then SuperSU with a unlocked bootloader.. sorry for my miss read thanks for the catch
dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Schaweet said:
If he has an unlocked bootloader, why would he not be able to get root back?
I thought when the bootloader was unlocked you had free reign over the device. Shouldn't he be able to upgrade to 4.4.2 and use SU and TWRP to get root back? I don't get why he wouldn't be able to do that.
Flash 4.4.2
Flash TWRP via mfastboot
Install SU zip via TWRP
Boot
Install SU app
What am I missing?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thx guys, I'll do this later, thx for the awesome responses
Sent from my XT1058 using xda app-developers app
dray_jr said:
idk i dont like to doing things half way there have been way to many bricks lately.
Click to expand...
Click to collapse
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.
NPOA556 said:
Can someone else please chime in on this? I have a Dev Edition VZW Moto X, and when the 4.4.2 update is finally available, I want to know what to do. My phone is unlocked & rooted with TWRP installed. Can I just flash the factory recovery and then take the OTA? Or do I have to revert to 100% stock? If I only flash stock recovery and take the OTA, data won't be wiped, will it? That is the big reason I would like to avoid going back to 100% stock if I can.
Click to expand...
Click to collapse
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Sent from my Dev Edition Moto X
Schaweet said:
My hope is that someone on here will repackage the OTA for us to sideload. That would be the best case scenario.
If not, I think you just need a stock recovery, but I could be wrong. I've seen someone say you need to flash stock system as well. I have the same questions as you if we don't get a side loadable zip.
Click to expand...
Click to collapse
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
What I've read is you need to go back to stock recovery and also make sure any /system files are unchanged. For example I renamed my old exchange apk's (in /system/app) when I put in the new ones from the nexus 5 on 4.4.2, so I would need to name those files back.
NPOA556 said:
It's not the end of the world if I have to wipe data and restore everything from TiBu, but it's still a PITA I would like to avoid if possible. More importantly, I don't want to run into any issues when installed the update. So if there is any question as to whether stock recovery alone is sufficient for the update to install properly, I will probably go back to full stock to be safe. I guess I have some time to let smarter people figure it out, since there is no update for VZW yet.
Click to expand...
Click to collapse
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Sent from my Dev Edition Moto X
Schaweet said:
I'm sure some nice developer will help us along.
What have you done to take you off of stock?
I just have custom recovery and xposed. Xposed shouldn't cause any issues.
Click to expand...
Click to collapse
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.
NPOA556 said:
I guess nothing, other than TWRP, Xposed, and obviously root. I have seen several people say that you have to unroot before installed an OTA, but I don't know if that applies to the Dev X or just the standard version. A lot of people seem to indicate that you have to go back to stock, so I just want to clarify what is really required.
Click to expand...
Click to collapse
Good questions. I'm not sure. We certainly root differently than a non Dev edition. They might have some files modified that we don't have to modify. Also, I wonder is going to stock recovery will unroot us.
I guess we wait and stay patient.
Sent from my Dev Edition Moto X
Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.
Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
The only hope you have is if someone decides to take that factory image and runnit through kitchen to make it a flashable zip. You will also need the updated modem from either 4.4 or 4.4.2 to prevent system settings from fc ing
This goes for any moto, retail and or developer edition
You may also attempt to flash the sbf firmware and remove the delete userdata from the XML but no guarantee that you will not have issues
Hope that helps
Sent on my Gummy running Lenoto X
To take an ota you must be stock. Meaning everything. As long as you haven't flashed an updated bootloader you can just flash system.IMG and recovery.IMG from the sbf your phone is currently on you can take an ota. A successful ota does NOT require a data wipe.
---------- Post added at 04:08 PM ---------- Previous post was at 04:04 PM ----------
finalarcadia said:
Surely there must be a way to flash updates through TWRP?
I want to grab one of these
http://sbf.droid-developers.org/phone.php?device=0
and flash it through TWRP. Anyone know if this is possible?
Wouldn't mind 4.4.2 right now on my dev ed, to see if my bluetooth problem gets fixed.
Click to expand...
Click to collapse
You cannot flash any of those through twrp! If you want to flash 4.4.2 you need to fastboot the system.IMG and boot.IMG and you will need to wipe your data. If you choose this route you will not be able to take the ota when its available you'd have to wait for the sbf file to be released and update through house of moto, rsd, or fastboot.
flashallthetime said:
Unfortunately you can not take the ota if
1- you have custom recovery
2- root
3- changed any system file
It will bootloop
Clearing data is always required after any ota
...
Click to expand...
Click to collapse
some questions.. and comments...
I agree with #1. You must have STOCK recovery for an OTA to install properly. And #3, because the OTA generally has a file list with check sums to compare against what is on your device to make sure all required files are there and the correct version/size/etc before it will start to install.
#2 I have a question on as I've not had an issue with this unless the root process makes changes to system files (thus causing a problem for #3). I've lost root taking an OTA, but that is it.
Then again, I have a Dev X with unlocked bootloader, and I don't know enough about RockMyMoto, SlapMyMoto, etc was of rooting the X, except that initially they replaced the recovery partition with an image that when selected/booted allowed write to system, etc. This would cause issue with #1 (no longer have stock recovery on the recovery partition), but not sure what, if any system files get touched or altered from stock.
Finally, you mention clearing data being required... This would wipe you back to factory defaults and remove your apps/data. I don't believe its "required" but rather just suggested as it can make the device run smoother after the update is done.
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
msespindola said:
Guys,i have Retail 1058 Moto X with unlocked Bootloader,TWRP(latest and rooted) and i want to upgrade to 4.4.2!
Some guys already received the 4.4.2 brazilian update via OTA,and extracted the zip file,but,since im on custom recovery,the OTA doesnt reboot the phone into stock and go straight to TWRP,therefore,doesnt conclude the update,and keep restarting!
Since i need the phone,i did a factory reset via TWRP just to get things going!
But,i want to upgrade to 4.4.2!
Is there a way to do that?remove TWRP ou something else?
I've seen some people saying that i need to flash the 4.4 img which it is inside the zip but,i dont have that zip anymore!
Thx in advance!
Click to expand...
Click to collapse
Depends on how you rooted.
If you've downloaded the SBF file for the ROM on your device (if you don't have it, see if its available from -> http://sbf.droid-developers.org/phone.php?device=0 ), you can unzip it, and fastboot flash the stock recovery from it onto your device, take the OTA, and then later fastboot flash TWRP back on and install SuperSU again to root.
This assumes you did NOT touch any system files the update will check for prior to running/installing. If you did touch system files, edit build prop, removed/renamed any APK's... then fastboot flash recovery and system before taking the OTA

[Q] Upgrading to Lollipop from locked bootloader, rooted, Kitkat.

Hello all,
With news that the Z3 and Z3 compact are starting to get Lollipop today I am sure a lot of people are going to be coming to the boards asking this exact question. So I wanted to start a thread that can help people find the answer quickly. (I'll update the OP as useful info comes in.)
I am currently on a D5803 running 4.4.4, with a locked bootloader and am rooted. I used This how-to to get where I am.
What is the best way to upgrade to Lollipop for me?
Is there a way to keep root? A pre-rooted FTF file?
Will all DRM features remain?
Will I need to reinstall anything? Recovery? Busy Box? SU?
Does this upgrade require a full wipe?
Thanks for any help
If anyone wants to check if their bootloader is locked:
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?
TheTomcraft said:
just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?
Click to expand...
Click to collapse
You root on KK then you can update to Lollipop and keep root.
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!
gruev said:
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!
Click to expand...
Click to collapse
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
q.
frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
Did you wipe? or flash over?
newbie2006 said:
Did you wipe? or flash over?
Click to expand...
Click to collapse
I wiped it (had too much crap on the phone anyway, so worth it), restored what I wanted with Titanium Backup when done.
---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------
I also tried with flashing lockeddualrecovery but recovery doesn't work. So need to wait for an update on that one I guess.
Any ideas about what could go bad if I don't wipe data?
Also, do you still have drm?
I succesfully flashed lolipop with this method without data wipe. I still have root and DRM keys. The only thing I lost was data of some app's with external data linked to SD card with Link2SD. And some root app's started to claim about busybox not installed properly. Besides that everything works like a charm
frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
When you flash those do you have system read and write as well? Do we need to worry about the RICDefeat in doing all this for the upgrade? Is RICDefeat integrated into that?
1.Flash the tft of lollipop
2.Get the zip of XZDualRecovery 2.8.3 Advanced Stock Kernel from http://nut.xperia-files.com/ and supersu from http://forum.xda-developers.com/showthread.php?t=1538053
3.Flash the boot.img in AndroPlusKernel with cable on flashtool
4.Reboot in recovery
5.Flash XZDualRecovery 2.8.3 Advanced Stock and supersu
6.Enjoy
Sorry,it should be with UB
about not working recovery
Dont know it thats issue, but I have same clue.
On KitKat after applying all steps to root 4.4.4 rom recovery was working until I changed busybox.
Oryginaly busybox was in version 1.20.2-jb - with that recovery was working.
I need some other tools and updated busbox to version 1.22.1 and recovery wasnt working (starting recovery end up with bootloop, but could start to system).
Returning back to recovery 1.20.2-jb fixed problem.
frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
I was hoping by adding step 4, it would be possible the encrypt device. Sadly it still creates a bootloop.
in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?
skaarax said:
in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?
Click to expand...
Click to collapse
I want to know about this too.
And what is a safe process for us (locked bootloader, rooted 4.4) to upgrade to 5.02 or 5.1 in the future.
I heard that unlocking bootloader will causes the camera not working properly (at least the auto mode would be messed up)
Does TWRP requiring unlocking bootloader?
Thanks guys.
I'm resurrecting this thread as I've got the same question as previous posters and I've not been able to find an answer elsewhere on the forum.
Basically, I've got a phone with a Bootloader which can't be unlocked. I upgraded/rooted it last year. It's still on KitKat. Is there any way I can upgrade it to Lollipop or Marshmallow without going through the downgrade/flash pre-rooted ROM procedure, without losing root? In other words, can I make use of TWRP which I installed in order to flash the rooted ROM last time? If so, how? (I'm not keen on using KingRoot unless somebody can convince me that handing over my IMEI info is safe.)
Thanks in advance.
Just flash a pre-rooted 5.1 zip made with prf creator whilst still on root+recovery KK. That's how I updated my M2 from rooted 4.4.4 KK to rooted 5.1 lollipop whilst retaining my locked bootloader. No sure if it's working for mm yet though this way

(Q) what's the easiest way to update Bootloader and Radios?

So I'm currently running BlissPop 5.0.2 and I wanna upgrade to a 5.1 ROM, but I was told I need to update bootloader and Radios, sorry I don't have much experience on this Subject, So what would be the easiest way to update both of these?? Thanx
And say the ROM I'm flashing doesn't work out for me for whatever reason and I need to Restore my nandroid backup (5.0.2 ROM) would I have to downgrade or whatever the bootloader and Radios again?? I'm confused lol thank you
owyheendn said:
So I'm currently running BlissPop 5.0.2 and I wanna upgrade to a 5.1 ROM, but I was told I need to update bootloader and Radios, sorry I don't have much experience on this Subject, So what would be the easiest way to update both of these?? Thanx
And say the ROM I'm flashing doesn't work out for me for whatever reason and I need to Restore my nandroid backup (5.0.2 ROM) would I have to downgrade or whatever the bootloader and Radios again?? I'm confused lol thank you
Click to expand...
Click to collapse
easiest way to update is with fastboot and google images here is link to images https://developers.google.com/android/nexus/images
if you want to keep data or it wont flash follow this http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/ but you need to erase data because your on a custom rom and it probably wont be compatible with stock rom once you have updated everything reflash a custom recovery or dont flash the stock one at all then flash a 5.1 rom and good to go
What about all the Bootloader and radio zips that can be flashed through TWRP? I've read about people flashing the updates while still being on their 5.0.2 ROMs and everything still works fine, I don't have access to a computer I would like to just update straight from my phone without a Computer if possible? Think I could flash the Bootloader and radio updates through TWRP then reboot n after everything is all good go back and flash the new 5.1 ROM and gapps?
owyheendn said:
What about all the Bootloader and radio zips that can be flashed through TWRP? I've read about people flashing the updates while still being on their 5.0.2 ROMs and everything still works fine, I don't have access to a computer I would like to just update straight from my phone without a Computer if possible? Think I could flash the Bootloader and radio updates through TWRP then reboot n after everything is all good go back and flash the new 5.1 ROM and gapps?
Click to expand...
Click to collapse
i don't know if anyone has twrp flashables for the updating bootloader and radios your searching is as good as mine here i am not experienced with that i always used factory images or ota updates to update those things.
but if you happen to have a backup of your stock rom in twrp you maybe able to just go back to stock then flash back your stock recovery then update with an ota but for an ota to work it has to be all stock no root no nothing just stock.
billycar11 said:
i don't know if anyone has twrp flashables for the updating bootloader and radios your searching is as good as mine here i am not experienced with that i always used factory images or ota updates to update those things.
but if you happen to have a backup of your stock rom in twrp you maybe able to just go back to stock then flash back your stock recovery then update with an ota but for an ota to work it has to be all stock no root no nothing just stock.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3066052

[Q] rooted, unlocked, TWRP recovery, stock, Verizon OTA help

I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.

Latest KitKat stock ROM available

So I've reset my HTC One back to stock 2 days ago and since then have received a lot of OTA updates.
Then I found that I had lost root.
I managed to reinstall TWRP and root today, but got another OTA update notification.
Because I don't want to lose root (and because TWRP says you should not update with custom recoveries), I'm looking for another way to update.
TWRP suggests to "wait for the developers to create a new ROM" but honestly, finding something in this forum is not easy...
My update is 6.09.401, but if there is something more recent I'll take that (but still KitKat). I've looked in the ROM collection but the latest seems to be 5.x or jump to 7.xx.
If I have to do some work (e.g. more research) please direct me to the right direction and I'll be happy to do it.
Will RUUs work? Still not clear what they are.
algiogia said:
So I've reset my HTC One back to stock 2 days ago and since then have received a lot of OTA updates.
Then I found that I had lost root.
Click to expand...
Click to collapse
Yep, you'll always loose root after an OTA update. Must ppl doesn't matter about that since it only takes a few minutes to root again.
I managed to reinstall TWRP and root today, but got another OTA update notification.
Because I don't want to lose root (and because TWRP says you should not update with custom recoveries), I'm looking for another way to update.
Click to expand...
Click to collapse
The only way to use ota update is by flashing back the stock recovery that match your version-main. Like said above, you'll loose root after an update. You can also update your phone by flashing a RUU but you'll also loose root and all your file since the RUU will make your phone stock, like if it was brand new.
TWRP suggests to "wait for the developers to create a new ROM" but honestly, finding something in this forum is not easy...
Click to expand...
Click to collapse
My update is 6.09.401,?but if there is something more recent I'll take that (but still KitKat). I've looked in the ROM collection but the latest seems to be 5.x or jump to 7.xx.
Click to expand...
Click to collapse
The latest Kitkat version is 6.09.401.12 otherwise its lollipop 7.19.401.x
I think the simplest solution since you want to stay on kitkat is to reflash your stock recovery 6.09.401.? (you didn't typed the last number), install the ota updates until you are on 6.09.401.11 or 6.09.401.12, reflash twrp and flash Supersu to re-root.
If I have to do some work (e.g. more research) please direct me to the right direction and I'll be happy to do it.
Will RUUs work? Still not clear what they are.[/QUOTE]
RUU are packages that will restore then entire phone Software and firmware partitions.
Thanks alray.
So are you saying there is not pre-rooted 6.09.401.11 ROM available to flash on the forum?
Where shall I look for it?
algiogia said:
Thanks alray.
So are you saying there is not pre-rooted 6.09.401.11 ROM available to flash on the forum?
Where shall I look for it?
Click to expand...
Click to collapse
Maybe i don't know. All roms are posted in the development section. Why not simply updating your phone and flashing Supersu again? It will take you maybe 20 min to install the update, reflash twrp and root...
alray said:
Maybe i don't know. All roms are posted in the development section. Why not simply updating your phone and flashing Supersu again? It will take you maybe 20 min to install the update, reflash twrp and root...
Click to expand...
Click to collapse
I'll have to find and flash the stock ROM first, do the updates, then flash TWRP and SuperSu.
If there is a way to flash only once why should I waste time (and increase chances of bricking the phone)?
algiogia said:
I'll have to find and flash the stock ROM first, do the updates, then flash TWRP and SuperSu.
If there is a way to flash only once why should I waste time (and increase chances of bricking the phone)?
Click to expand...
Click to collapse
You already are on the stock rom, just flash the stock recovery over twrp, install ota update(s) until you are on the desired version, flash twrp and supersu. There isn't really any chances to brick....
Code:
fastboot flash recovery your_stock_recovery.img
fastboot erase cache
fastboot reboot
Then boot the phone, install update(s). Once updated to the desired version, reflash twrp:
Code:
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
Boot in twrp, install supersu 2.46.zip then reboot in the OS and you're done.
But yes if you prefer you can find a stock rooted rom of 6.09.401.11 if there is still one somewhere.

Categories

Resources