Related
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Freeza, you rule... Just saying
Sent from my Nexus 7 using Tapatalk 4
Nice work!
Quick question for you, will the bootloader and firmware updates persist after custom ROM updates or will I need to reflash each time?
for example, I'm running CarbonRom at the moment which is based on JSS15Q - I've flashed this zip without any problems but will I need to reflash it when I install the next nightly?
Cheers
Macca
It will persist. No need to reflash.
sfhub said:
It will persist. No need to reflash.
Click to expand...
Click to collapse
Cheers, that's what I thought but there was no harm in checking
BigMacca said:
Cheers, that's what I thought but there was no harm in checking
Click to expand...
Click to collapse
I should be more clear, in the example you gave, it will persist, but if you do something that will flash the bootloader like factory restore or its updates, the bootloader could change
sfhub said:
I should be more clear, in the example you gave, it will persist, but if you do something that will flash the bootloader like factory restore or its updates, the bootloader could change
Click to expand...
Click to collapse
Yeah, I should have been clearer as well - I was basically checking that custom roms don't flash the bootloader (I'd assumed that a factory restore / ota update would)
Nice to see ya here Freeza!
I am currently on [JSS15Q] - CleanROM 1.6 I am wondering if this would work with my current rom as a dirty flash? anyone tired while on CleanRom 1.6?
DC_MTP said:
Nice to see ya here Freeza!
I am currently on [JSS15Q] - CleanROM 1.6 I am wondering if this would work with my current rom as a dirty flash? anyone tired while on CleanRom 1.6?
Click to expand...
Click to collapse
No problems here DC.
D
everything seems to be going well (using FLO Kangs cm10.2 Sep 5 build) will update if anything bad happens
Does firmware mean the audio driver, sensor driver, wifi driver etc?
bland.life said:
Does firmware mean the audio driver, sensor driver, wifi driver etc?
Click to expand...
Click to collapse
No, it means bootloader, resource power manager, trusted zone.
Quick queastion , I was on JSS15J when stock, flashed ROM that says now JLS36C. If I flash this will it erase everything and do I even need to? Thanks for the help.
It won't erase any user data. Whether you want to flash is up to you. You'll get it automatically if you wait for jls36g ota.
Why is the 3.15 bootloader not available as .img file in the google recovery as always? I normally flash bootloader ONLY by using fastboot?!
Awesome!
I flashed this and my dead gold fish came back to life!
You're the man, OP!
freeza said:
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Click to expand...
Click to collapse
Will this work on stock? I can't get the ota to install.
Still JSS15Q after flashing?
freeza said:
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Click to expand...
Click to collapse
After successful flashing this zip-file on my rooted JSS15Q version with TWRP the Android version is still JSS15Q. That's right? I expected JSS15R.
Greetings
Zorro16
relaxxer said:
Why is the 3.15 bootloader not available as .img file in the google recovery as always? I normally flash bootloader ONLY by using fastboot?!
Click to expand...
Click to collapse
If you want the 3.15 bootloader .img to flash in fastboot, I added it to the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2448015
Zorro16 said:
After successful flashing this zip-file on my rooted JSS15Q version with TWRP the Android version is still JSS15Q. That's right? I expected JSS15R.
Greetings
Zorro16
Click to expand...
Click to collapse
This is just the bootloader that came with 15R. If you want 15R, download and flash the full rom package.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hello,
I've found a link to the supposedly OTA, but it didn't work with the same method for the 5.0.2, I mean copying to the memory of the phone and trying to update from the settings. I don't know if it is really the 5.1 OTA but feel free to give it a try. I've found it on a comment in a brasilian site: http://www.androidpit.com.br/moto-x-android-update. If any of you guys know how to update please let me know.
Link: https://mega.co.nz/#!48E0VZBR!lphA3SijKt1yhbvUGuSi535yXNinoNamFoIw3dDOjtc
pd.: sorry for my bad english, and sorry if I'm not supposed to post links this way.
ECassinelli said:
Hello,
I've found a link to the supposedly OTA, but it didn't work with the same method for the 5.0.2, I mean copying to the memory of the phone and trying to update from the settings. I don't know if it is really the 5.1 OTA but feel free to give it a try. I've found it on a comment in a brasilian site: http://www.androidpit.com.br/moto-x-android-update. If any of you guys know how to update please let me know.
Link: https://mega.co.nz/#!48E0VZBR!lphA3SijKt1yhbvUGuSi535yXNinoNamFoIw3dDOjtc
pd.: sorry for my bad english, and sorry if I'm not supposed to post links this way.
Click to expand...
Click to collapse
Can I use this on my device. I am on us cellular XT1055?
cdiamond said:
Can I use this on my device. I am on us cellular XT1055?
Click to expand...
Click to collapse
I don't know, it is the brazilian firmware so I think it deppends if you have updated the to 5.0.2 brazilian firmware previously.
cdiamond said:
Can I use this on my device. I am on us cellular XT1055?
Click to expand...
Click to collapse
Goto the Confirmed Android 5.1 thread, around page 16, there is a mega link of a nadroid backup of 5.1 Brazil for twrp. Download it, extract it to the TWRP/backup folder, boot to recovery, backup your present ROM. Then restore the downloaded nandroid, wipe data, cache, and davlik cache only, reboot into system, profit. This way gpt and boot partitions remained in touched, and no need to revert to Brazilian KitKat, then to 5.0.2, then to 5.1 painful process.
flipm00de said:
Goto the Confirmed Android 5.1 thread, around page 16, there is a mega link of a nadroid backup of 5.1 Brazil for twrp. Download it, extract it to the TWRP/backup folder, boot to recovery, backup your present ROM. Then restore the downloaded nandroid, wipe data, cache, and davlik cache only, reboot into system, profit. This way gpt and boot partitions remained in touched, and no need to revert to Brazilian KitKat, then to 5.0.2, then to 5.1 painful process.
Click to expand...
Click to collapse
Ok will do thank you
cdiamond said:
Ok will do thank you
Click to expand...
Click to collapse
In running it right now, and it is nice thus far
flipm00de said:
Goto the Confirmed Android 5.1 thread, around page 16, there is a mega link of a nadroid backup of 5.1 Brazil for twrp. Download it, extract it to the TWRP/backup folder, boot to recovery, backup your present ROM. Then restore the downloaded nandroid, wipe data, cache, and davlik cache only, reboot into system, profit. This way gpt and boot partitions remained in touched, and no need to revert to Brazilian KitKat, then to 5.0.2, then to 5.1 painful process.
Click to expand...
Click to collapse
Do you know how can I update without being root? I'm in the brazilian 5.0.2.
flipm00de said:
In running it right now, and it is nice thus far
Click to expand...
Click to collapse
What carrier are u on?
ECassinelli said:
Do you know how can I update without being root? I'm in the brazilian 5.0.2.
Click to expand...
Click to collapse
cdiamond said:
What carrier are u on?
Click to expand...
Click to collapse
I'm in united States using cricket wireless.
You do not need to be rooted for this. You must have unlocked boot loader though because you need twrp
Oh I'm rooted matter of fact I'm on the N5X based ROM and its really Good..and I will extract and put inside the backup folder
flipm00de said:
I'm in united States using cricket wireless.
You do not need to be rooted for this. You must have unlocked boot loader though because you need twrp
Click to expand...
Click to collapse
Is there any other way? I dont have twrp, I updated to 5.0.2 just copying the ota zip on my phone.
flipm00de said:
In running it right now, and it is nice thus far
Click to expand...
Click to collapse
Ok could I flash back to stock 4.4.2 if I don't want to be on 5.1 anymore?
cdiamond said:
Ok could I flash back to stock 4.4.2 if I don't want to be on 5.1 anymore?
Click to expand...
Click to collapse
I was wondering the same thing
Tested on my XT1058, worked like a charm! No need to mess with bootloader, fastboot nor any other tool... Download, add to memory, install, be happy!
Just as other OTA zips...
Ah, remember to install 5.0.2 OTA before this, link can be found on other threads...
---------- Post added at 11:56 AM ---------- Previous post was at 11:52 AM ----------
truelove_shinn said:
I was wondering the same thing
Click to expand...
Click to collapse
Please don't! Many people bricked the device when trying to roll back from 5.X... If you install the soak test, it is better to wait for the final OTA update...
How to update
Yesterday I found out why in some cases when you place the file in the internal memory it doesn't work, you need to follow the updates sequence to make it work.
So from 4.4.4 you update to 5.0.2 (AKA .31):
Blur_Version.221.41.31.ghost_row.Brasil.en.BR
Then you apply this small patch that still 5.0.2 (AKA .38):
Blur_Version.221.41.38.ghost_row.Brasil.en.BR
And finally you apply the update to 5.1 (AKA .2)
Blur_Version.222.21.2.ghost_row.Brasil.en.BR
Happy flashing.
Kind regards,
Johnny
JohNNyum said:
Yesterday I found out why in some cases when you place the file in the internal memory it doesn't work, you need to follow the updates sequence to make it work.
Click to expand...
Click to collapse
Yes. All OTA's have been incremental so far, and have a pre-flash validation check to ensure your phone is on the correct level, and if your phone isn't, it wont flash.
It doesn't surprise me that this follows that pattern especially based on its size
KidJoe said:
Yes. All OTA's have been incremental so far, and have a pre-flash validation check to ensure your phone is on the correct level, and if your phone isn't, it wont flash.
It doesn't surprise me that this follows that pattern especially based on its size
Click to expand...
Click to collapse
What will happen with the official 5.1 release then? They never released an official 5.0.2, so how can they expect people to be upgrading from 5.0.2?
joaoBeno said:
Tested on my XT1058, worked like a charm! No need to mess with bootloader, fastboot nor any other tool... Download, add to memory, install, be happy!
Just as other OTA zips...
Ah, remember to install 5.0.2 OTA before this, link can be found on other threads...
---------- Post added at 11:56 AM ---------- Previous post was at 11:52 AM ----------
Please don't! Many people bricked the device when trying to roll back from 5.X... If you install the soak test, it is better to wait for the final OTA update...
Click to expand...
Click to collapse
Thanks a lot for the kind warning. After posting this comment I went through many other posts, especially the one by KidJoe. Chances are quite real that one can hard-brick his device by downgrading then upgrading through OTA again.
justaway2 said:
What will happen with the official 5.1 release then? They never released an official 5.0.2, so how can they expect people to be upgrading from 5.0.2?
Click to expand...
Click to collapse
For those were invited to the MFN Test or Soak, Moto has their IMEI, knows what is on their phone, and will push them the appropriate update to 5.1 final, hence this file's preflash check looking for a particular 5.02. Since we know of two different 5.02 versions (one for the Brazil xt1058 and one for the XT1053), there will be at least two different 5.1 versions that Moto will push to those on the MFN test/soak list.
For the those NOT invited, as in the past Moto will likely compile and push a 4.4.4 -> 5.1 OTA zip for each carrier/model which will have a preflash check looking for the 4.4.4 for the particular carrier/model.
For those that manually applied the 5.x leaks because they were NOT invited to the MFN test/soak, Moto will NOT have their IMEI to push a special version, they will be off stock 4.4.4, and so any 5.1 push from the carrier/moto will fail to install due to the preflash check. They'll either need to revert to 4.4.4 (where GPT.BIN/Motoboot.img have been the cause of many bricks in the past when downgrading, so its expected to continue to be risky going forward), or wait for a leak of the OTA zip they need, or wait for a leak of the 5.1 SBF for their carrier/model.
That is why some suggested if you're not part of the MFN invites, you should wait on installing the 5.x leaks.
Credits mega link for me haha
http://www.motoforum.com.br/topic/33-ota-android-51-lollipop-moto-x/?page=1
My Nexus 6P is rooted and running Android Marshmallow (6.0.1) (supposed to be systemless but not sure anymore)
I have unlocked the bootloader and have twrp as my recovery.
I have exposed framework with some modules installed and working (notification bar clock now shows the seconds and stuff like that....)
So I recently got my Nexus 6p and the first thing I did was root and install twrp via adb and fast boot so I could use exposed framework. I would like to know what my options are in receiving ota updates? I have the Android security patch from January 1, 2016 and I just got an Android system update notification that includes a newer security patch from February and I'm not sure if I can get a specific ota that is flashable through twrp or if I'll need to back up my stuff and flash stock or if there's an easier way to do this because I'd prefer to not have to set up everything all over again.
If you need me to provide any further information about my device just tell me.
---
I'm currently on build MMB29P and I have checked the Google dev page on Factory Images for Nexus Devices
And apparently MHC19I is the newest.
use flashfire
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
fireeyeeian said:
My Nexus 6P is rooted and running Android Marshmallow (6.0.1) (supposed to be systemless but not sure anymore)
I have unlocked the bootloader and have twrp as my recovery.
I have exposed framework with some modules installed and working (notification bar clock now shows the seconds and stuff like that....)
So I recently got my Nexus 6p and the first thing I did was root and install twrp via adb and fast boot so I could use exposed framework. I would like to know what my options are in receiving ota updates? I have the Android security patch from January 1, 2016 and I just got an Android system update notification that includes a newer security patch from February and I'm not sure if I can get a specific ota that is flashable through twrp or if I'll need to back up my stuff and flash stock or if there's an easier way to do this because I'd prefer to not have to set up everything all over again.
If you need me to provide any further information about my device just tell me.
---
I'm currently on build MMB29P and I have checked the Google dev page on Factory Images for Nexus Devices
And apparently MHC19I is the newest.
Click to expand...
Click to collapse
I have all the OTA zips listen in my index. As previously mentioned you can use Flashfire to flash them without having to undo your modifications.
But with flashfire you will still lose all of your modifications like xposed apps? You have to redo it all? Anyone have a direct link to the new feb security update?
Heisenberg said:
I have all the OTA zips listen in my index. As previously mentioned you can use Flashfire to flash them without having to undo your modifications.
Click to expand...
Click to collapse
I've used flash fire back on my s4 so this is good but
Should I disable my exposed modules before I flash with flash fire as i can also reinstall exposed along with the ota? It's my First time using exposed because my s4 has a locked bootloader.
squall458 said:
But with flashfire you will still lose all of your modifications like xposed apps? You have to redo it all? Anyone have a direct link to the new feb security update?
Click to expand...
Click to collapse
Downloaded modules should stay intact. However, I am not sure if the OTA update has library changes, that may affect Xposed installation. Anyhow, simply flashing the Xposed Installer zip will suffice.
DJBhardwaj said:
Downloaded modules should stay intact. However, I am not sure if the OTA update has library changes, that may affect Xposed installation. Anyhow, simply flashing the Xposed Installer zip will suffice.
Click to expand...
Click to collapse
Thanked you!
Will the latest google image for the 6p already have the security patch in it? I dont see a changelog or a timestamp so I cant tell if its just the old image.
squall458 said:
Thanked you!
Will the latest google image for the 6p already have the security patch in it? I dont see a changelog or a timestamp so I cant tell if its just the old image.
Click to expand...
Click to collapse
No need to thank, just add this to your knowledge for future reference. That will be more than enough for me.
Which security patch are you talking about, specifically? The latest Google factory image as of now, contains the March security update. You can read a more detailed article here: https://source.android.com/security/bulletin/2016-03-01.html
DJBhardwaj said:
No need to thank, just add this to your knowledge for future reference. That will be more than enough for me.
Which security patch are you talking about, specifically? The latest Google factory image as of now, contains the March security update. You can read a more detailed article here: https://source.android.com/security/bulletin/2016-03-01.html
Click to expand...
Click to collapse
Ok i just used flashfire to update with the image file. Made sure to follow the instructions and even got it to flash xposed for me after.
It all went smoothly. But upon reboot it looked like it was doing an android app update but it stopped and everything seems like it was before. The security update didnt work. Still says january.
squall458 said:
Ok i just used flashfire to update with the image file. Made sure to follow the instructions and even got it to flash xposed for me after.
It all went smoothly. But upon reboot it looked like it was doing an android app update but it stopped and everything seems like it was before. The security update didnt work. Still says january.
Click to expand...
Click to collapse
What did you flash, image files or OTA zip?
DJBhardwaj said:
What did you flash, image files or OTA zip?
Click to expand...
Click to collapse
The system image file. Not the ota one. I got it from the google developer site with my matching build.
squall458 said:
The system image file. Not the ota one. I got it from the google developer site with my matching build.
Click to expand...
Click to collapse
Well then you just flash the system partition only. I would say, flash the OTA zip.
Wait! "with my matching build" ? Which build did you download?
DJBhardwaj said:
Well then you just flash the system partition only. I would say, flash the OTA zip.
Wait! "with my matching build" ? Which build did you download?
Click to expand...
Click to collapse
My build is MMB29P. I got the 6.0.1 matching my build. Did I pick the wrong one?
squall458 said:
My build is MMB29P. I got the 6.0.1 matching my build. Did I pick the wrong one?
Click to expand...
Click to collapse
Yes. You will need to pick MHC19I factory image, and extract the system.img from it. Flash it, and also the vendor.img too.
Every thing worked out I had downloaded the most recent build and exposed installer flashed through flash fire everything seems good so far.
DJBhardwaj said:
Yes. You will need to pick MHC19I factory image, and extract the system.img from it. Flash it, and also the vendor.img too.
Click to expand...
Click to collapse
Ohhh ic! I dont pick my matching build? I just pick the last one which is the latest update?
squall458 said:
Ohhh ic! I dont pick my matching build? I just pick the last one which is the latest update?
Click to expand...
Click to collapse
Picking the current build is simply reflashing it. To update, you will need to flash the system.img from the latest factory image.
---------- Post added at 09:17 PM ---------- Previous post was at 08:59 PM ----------
fireeyeeian said:
Every thing worked out I had downloaded the most recent build and exposed installer flashed through flash fire everything seems good so far.
Click to expand...
Click to collapse
Great.
DJBhardwaj said:
Picking the current build is simply reflashing it. To update, you will need to flash the system.img from the latest factory image.
---------- Post added at 09:17 PM ---------- Previous post was at 08:59 PM ----------
Great.
Click to expand...
Click to collapse
It worked! You are the best. Ppl like you make xda such an awesome forum! Bless you
squall458 said:
It worked! You are the best. Ppl like you make xda such an awesome forum! Bless you
Click to expand...
Click to collapse
People like all of us, you, me, and everyone else, make this a better community. Belonging to different countries and cultures, and we still understand each other very well. :highfive:
Hello XDA
Since @Blueblob stopped his work with the vendor-images I thought I could pick it up
I have unpacked and uploaded the vendor image from google images, I havent touched anything on it.
Download and flash image in twrp/recovery of pref.
Updated 02.05.17
Bootloader
Radio
Vendor
Flash at your own risk.
Thanks Google
@LoverBoy2415 is this something for your index post?
Also I hope this is ok for the mods to stay up.
Stopped because TWRP can flash .img
Thanks for mirror ?
Envoyé de mon Nexus 5X en utilisant Tapatalk
[BUMP] Updated 02.05.17
Updated with vendor, bootloader and radio for May
[BUMP] Updated 06.06.17
New vendor image uploaded, radio and bootloader is same as last month
[BUMP] Updated 08.07.17
Updated the vendor image, radio and bootloader is same as before
[BUMP] Updated 08.08.17
Uploaded with latest, still same radio and boot as before
[BUMP] Updated 14.09.17
Updated with Android 8 (Oreo) images
Nothing for Android 7.x
bjorn96 said:
Updated with Android 8 (Oreo) images
Nothing for Android 7.x
Click to expand...
Click to collapse
So the sep vendor image won't work on 7.1.2?
Sent from my LG Nexus 5X using XDA Labs
Skittles9823 said:
So the sep vendor image won't work on 7.1.2?
Click to expand...
Click to collapse
Nope.
bjorn96 said:
Nope.
Click to expand...
Click to collapse
Okay. Thanks for the speedy response.
Sent from my LG Nexus 5X using XDA Labs
hey everyone,
I recently purchased a used Nexus 5x that is running fine so far. my only problem is i get the message "internal problem, contact manufacturer" after every boot.
the phone is running android 7.0 (NDR90S) and the seller told me he trie to root and flash custom firmware but somehow the boot loader always locked itself. Now its not possible to perform an OTA update to 8.0 (get it offered all the time).
According to the developer setting the Bootloader is unlocked. I read that it should be fine to flash the vendor.image. Is this correct so far?
laspecas said:
hey everyone,
I recently purchased a used Nexus 5x that is running fine so far. my only problem is i get the message "internal problem, contact manufacturer" after every boot.
the phone is running android 7.0 (NDR90S) and the seller told me he trie to root and flash custom firmware but somehow the boot loader always locked itself. Now its not possible to perform an OTA update to 8.0 (get it offered all the time).
According to the developer setting the Bootloader is unlocked. I read that it should be fine to flash the vendor.image. Is this correct so far?
Click to expand...
Click to collapse
You may want to do a full firmware flash. Simply get the latest firmware image from googles website for this device and run the installer script that comes with it. You'll be wiped clean and hopefully any issues are fixed. (You'll need to unlock the bootloader again if you plan to root or flash custom roms).
Sent from my Nexus 5X using XDA Labs
I'm on NPN25. 137-33. Flashed back to my stock backup for various reasons, am now getting a notification for whatever update is available.....a couple of things. How do I disable the update? And is there a stock rom of the latest build available for the US variant that's TWRP flashable? I don't see it. I was on the stock debloated rom which seemed fine but I couldn't get it to root with superuser or magisk.
carnivalrejectq said:
I'm on NPN25. 137-33. Flashed back to my stock backup for various reasons, am now getting a notification for whatever update is available.....a couple of things. How do I disable the update? And is there a stock rom of the latest build available for the US variant that's TWRP flashable? I don't see it. I was on the stock debloated rom which seemed fine but I couldn't get it to root with superuser or magisk.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B6-Tz_7kDyxsczVpLTFjZW9vR28/view
Flash in twrp its latest. 67
dayask said:
https://drive.google.com/file/d/0B6-Tz_7kDyxsczVpLTFjZW9vR28/view
Flash in twrp its latest. 67
Click to expand...
Click to collapse
Thank you. Will it break TWRP though and is it root able?
carnivalrejectq said:
Thank you. Will it break TWRP though and is it root able?
Click to expand...
Click to collapse
Yes u need to flash through twrp... And I think its rootable
.67 is for the Indian G5+, but works on the US variant (RETUS). .35-5 is the most current firmware and .43 is for Verizon users (fixes call/VoLTE issues) of RETUS but is a March security patch instead of May like .35-5. The .67 has a different kernel source and March security patch. I'd go with .35-5. It's available here. But none of these are flashable through TWRP. You can fastboot though...
atrac17 said:
.67 is for the Indian G5+, but works on the US variant (RETUS). .35-5 is the most current firmware and .43 is for Verizon users (fixes call/VoLTE issues) of RETUS but is a March security patch instead of May like .35-5. The .67 has a different kernel source and March security patch. I'd go with .35-5. It's available here. But none of these are flashable through TWRP. You can fastboot though...
Click to expand...
Click to collapse
You lose recovery if you flash through fast boot though right? And so the one posted above you through retus isn't compatible with twrp?
carnivalrejectq said:
You lose recovery if you flash through fast boot though right? And so the one posted above you through retus isn't compatible with twrp?
Click to expand...
Click to collapse
I believe the one posted above linked via gdrive is flashable through TWRP and was created by @GtrCraft and is based off RETIN or RETUE. You loose TWRP, but fastboot it right back.
I was just trying to help answer your original question about the most up to date RETUS firmware. Moto has made it difficult to track with all the variants.
atrac17 said:
I believe the one posted above linked via gdrive is flashable through TWRP and was created by @GtrCraft and is based off RETIN or RETUE. You loose TWRP, but fastboot it right back.
I was just trying to help answer your original question about the most up to date RETUS firmware. Moto has made it difficult to track with all the variants.
Click to expand...
Click to collapse
Thanks for all. What is the fasboot command to flash a zip?
My apologies if this isn't the right place to ask, but the discussion seems to be right in line with my issue. I'm running -35 (RETUS), rooted (SuperSU) and TWRP. I got the notification to update yesterday, and being partly distracted by screaming kids, I accepted.
It, of course, failed. But more importantly, now any power/boot cycle dumps me into TWRP every time. The only way back to the OS is to boot to bootloader and click "start". I honestly could care less about the security update (as I'm sure a TWRP friendly version is on the horizon). But having to go through the bootloader to simply power up/reboot the phone is a royal PITA.
Is there a quick fix to the hook that seems to redirect to the recovery? As bad as that is, I'd live with it if it means I don't have to wipe and start from scratch.
erkme73 said:
My apologies if this isn't the right place to ask, but the discussion seems to be right in line with my issue. I'm running -35 (RETUS), rooted (SuperSU) and TWRP. I got the notification to update yesterday, and being partly distracted by screaming kids, I accepted.
It, of course, failed. But more importantly, now any power/boot cycle dumps me into TWRP every time. The only way back to the OS is to boot to bootloader and click "start". I honestly could care less about the security update (as I'm sure a TWRP friendly version is on the horizon). But having to go through the bootloader to simply power up/reboot the phone is a royal PITA.
Is there a quick fix to the hook that seems to redirect to the recovery? As bad as that is, I'd live with it if it means I don't have to wipe and start from scratch.
Click to expand...
Click to collapse
I'd start from scratch and make a backup of your current now, flash stock .35-5 that I linked above with RSDlite (update if on Verizon - your choice), fastboot TWRP again and restore. I accidentally did it with .35 and this was the process I did to get out of bootloop recovery hell. Hope that helps...
I posted the .43 update if you don't get the update and required it for Verizon.