I'm currently rooted with a custom recovery and s on. There is an OTA available for my phone. What do I do?
Sent from my HTC 10 using XDA-Developers mobile app
flash the RUU that's for your phone variant to go back to stock, take the OTA, reinstall twrp, then reinstall superuser and your good to go. you can also wait to see if someone uploads the OTA here and youll be able to skip going back to stock but you have to wait a bit longer till someone does that.
afuller42 said:
flash the RUU that's for your phone variant to go back to stock, take the OTA, reinstall twrp, then reinstall superuser and your good to go. you can also wait to see if someone uploads the OTA here and youll be able to skip going back to stock but you have to wait a bit longer till someone does that.
Click to expand...
Click to collapse
Does this require wiping the phone? Where would I get the RUU?
most RUUs will not wipe your personal data or sdcard. where to get the RUU depends on your phone carrier
afuller42 said:
most RUUs will not wipe your personal data or sdcard. where to get the RUU depends on your phone carrier
Click to expand...
Click to collapse
Not true. RUU will wipe internal data. You dont need to run RUU. Just restore your stock unmodified system image, boot and recovery then boot to system and take ota. There is a thread in the guides section with all the info and downloads you will need
yldlj said:
Not true. RUU will wipe internal data. You dont need to run RUU. Just restore your stock unmodified system image, boot and recovery then boot to system and take ota. There is a thread in the guides section with all the info and downloads you will need
Click to expand...
Click to collapse
the RUUs i ever used never wipe internal storage or data, they do wipe system removing root
afuller42 said:
the RUUs i ever used never wipe internal storage or data, they do wipe system removing root
Click to expand...
Click to collapse
Are you sure? RUU makes your phone completely stock.
yldlj said:
Are you sure? RUU makes your phone completely stock.
Click to expand...
Click to collapse
I'm very sure 110% about the ones I have used do not wipe data.
yeah they make them 100% stock but your data is still there. what you wont have is twrp, superuser, and whatever rom you used before. youll still have to factory reset before or after the ruu installs to have your stuff removed, I prefer doing a format in twrp first. There may be some ruus that do a whole wipe but I have never seen/ used one personally.
They also do not relock bootloaders or make you s-on again
I've flashed RUUs that wipes internal storage such as the one I ran recently before I sold my M9 and others that didn't. If unsure I would suggest backing up internal just in case.
RUU also won't touch S-OFF. cmd must be ran in bootloader to set it back to S-ON
Related
EDIT: What the frick! -.- I fond the answer only seconds after posting this in a thread labeled something entirely different. Oh well. For anyone else looking for the answer to this, my below assumption is correct, aside from having to lock the bootloader again.
More detailed description in this thread.
Original post below:
--------------------
Right, so I rooted and installed CWM on my phone to get rid of that incessantly annoying menu-bar. However, only days after, HTC decided that they'd release an OTA to fix a number of things (internal storage space, for one).
Now, if I've understood this right, there is absolutely no way for me to install the OTA, since I've completely replaced the stock recovery. So what I've gathered from different threads, guides and god knows, is this:
- I need to fastboot write the old recovery back
- Lock my bootloader
- Let the phone update
- Unlock
- Install CWM again
Am I correct? For I am assuming that it's not simply as easy as to flash the new RUU ROM with CWM, since CWM can't access radio, for instance.
MoonshineFox said:
EDIT: What the frick! -.- I fond the answer only seconds after posting this in a thread labeled something entirely different. Oh well. For anyone else looking for the answer to this, my below assumption is correct, aside from having to lock the bootloader again.
More detailed description in this thread.
Original post below:
--------------------
Right, so I rooted and installed CWM on my phone to get rid of that incessantly annoying menu-bar. However, only days after, HTC decided that they'd release an OTA to fix a number of things (internal storage space, for one).
Now, if I've understood this right, there is absolutely no way for me to install the OTA, since I've completely replaced the stock recovery. So what I've gathered from different threads, guides and god knows, is this:
- I need to fastboot write the old recovery back
- Lock my bootloader
- Let the phone update
- Unlock
- Install CWM again
Am I correct? For I am assuming that it's not simply as easy as to flash the new RUU ROM with CWM, since CWM can't access radio, for instance.
Click to expand...
Click to collapse
Where to find the old stock recovery back?
phonixloo said:
Where to find the old stock recovery back?
Click to expand...
Click to collapse
You'll find it in the thread I linked.
Or if you want,
1. Do a CWM backup
2. Relock
3. Perform RUU install
4. Unlock
5. Install CWM
6. Restore CWM backup
7 (optional). wipe cache and Dalvik cache
I use this method as your OTA method means losing root and CWM as Unlocking it after the OTA will erase your data partitions.
jonshipman said:
Or if you want,
1. Do a CWM backup
2. Relock
3. Perform RUU install
4. Unlock
5. Install CWM
6. Restore CWM backup
7 (optional). wipe cache and Dalvik cache
I use this method as your OTA method means losing root and CWM as Unlocking it after the OTA will erase your data partitions.
Click to expand...
Click to collapse
Yeah, I didn't actually need to lock the bootloader. It wasn't necessary. Flash old recovery, install OTA, reflash CWM, make sure root works, if not, reflash SU.
I ended up having to factory reset on the unlock again. Bad move
I have a SIM free M8 running stock 2.22.401.5 (inc recovery) but S-Off.
Got the OTA notification and selected to install it. It reboots to stock recovery but after a few seconds when the green progress bar is about a 1/3 full, it stops and a red warning triangle appears.
After a couple more minutes the phone reboots and is still on the old version. Tried again but the same result.
Any advice would be warmly welcomed.
Any errors messages?
HTC One M8
Elisha said:
Any errors messages?
HTC One M8
Click to expand...
Click to collapse
None at all.
I dont believe it matters as the last OTA was successful, but I am also superCID and bootloader unlocked.
I've also just wiped the cache partition using stock recovery but still no dice.
Did you installed any system mods? Like H/K sound mod or custom kernel?
K-a-M-u-Z-u said:
Did you installed any system mods? Like H/K sound mod or custom kernel?
Click to expand...
Click to collapse
No. I haven't even rooted since the previous ota.
stuart0001 said:
No. I haven't even rooted since the previous ota.
Click to expand...
Click to collapse
maybe a stupid question, but do you have enough free space on the device?
K-a-M-u-Z-u said:
maybe a stupid question, but do you have enough free space on the device?
Click to expand...
Click to collapse
Yep, 6GB of internal free.
I feel a factory reset impending.
stuart0001 said:
Yep, 6GB of internal free.
I feel a factory reset impending.
Click to expand...
Click to collapse
If you are going to do a factory reset, you can save all your data easily.
you can flash TWRP recovery, make a backup of DATA partition, Wipe factory reset and reflash Stock recovery, apply the OTA.re flash TWRP recovery again and Restore only DATA partition backup.after that you can revert back to stock recovery if that your wish.
this way you will have all you user data with a clean SYSTEM partition without having to install and reconfigure all your system from scratch.
K-a-M-u-Z-u said:
If you are going to do a factory reset, you can save all your data easily.
you can flash TWRP recovery, make a backup of DATA partition, Wipe factory reset and reflash Stock recovery, apply the OTA.re flash TWRP recovery again and Restore only DATA partition backup.after that you can revert back to stock recovery if that your wish.
this way you will have all you user data with a clean SYSTEM partition without having to install and reconfigure all your system from scratch.
Click to expand...
Click to collapse
That's great advice Thank you. [emoji106]
I'm still getting the same issue after a factory reset. Any ideas?
Do I need to relock my bootloader?
stuart0001 said:
I'm still getting the same issue after a factory reset. Any ideas?
Do I need to relock my bootloader?
Click to expand...
Click to collapse
Your phone is not rooted?
Edit: I read the previous posts and i think is because u have SuperCID, i think u must have your original CID.
same here.. i also flashed the 3.xx update. im on s-off, supercid and my custom rom was viperone 2.5... when i was flashing the update, error 24 appeared. im already on supercid so i wonder why would it fail. so i reflashed the previous firmware which is 2.22.401.5.. it went well but then when im alrady on my homescreen, i notice that i don't have a signal from my mobile network and after a few minutes the phone restarts. could you help me?
I'm officially a dumbass. I managed to open the stock recovery right after it failed and saw the issue. It said.
platform.xml unexpected content
This was from when I applied a previous SD card write fix patch.
After reflaahing a stock ROM it updated fine.
A couple of things puzzle me though. Why did the system restore not revert this file to original and why did the last OTA go through ok when I'd had the patch installed prior to that also.
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Vesten said:
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Click to expand...
Click to collapse
what exact version of twrp?
Is the backup a system IMAGE backup?
are you entering TWRP in read-only mode?
When you try to restore now, what does the terminal output say?
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Vesten said:
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Click to expand...
Click to collapse
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
I'll have to check, but don't think it does.
I'll try that new version of TWRP and report back.
Many thanks for the help, greatly appreciated.
jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Vesten said:
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Click to expand...
Click to collapse
What happens when you restore your backup and reboot without installing supersu?
jollywhitefoot said:
What happens when you restore your backup and reboot without installing supersu?
Click to expand...
Click to collapse
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Vesten said:
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Click to expand...
Click to collapse
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
jollywhitefoot said:
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
Click to expand...
Click to collapse
Interesting. There's nothing saying it couldn't write anything..
Just tried opening SuperSU from my restored backup, and hits me with "There is no SuperSU binary installed!" This is a problem, blah, blah, etc.
Then tried check-boxing the 'system' box in the Mount section. Then tried flashing UPDATESuperSu.VsXX and just gave me the usual as said above. Crashed and reboots.
https://www.dropbox.com/s/cvkclw8xuzua4u3/2015-07-20 21.56.37.png?dl=0
Losing the will to live! Ha
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Vesten said:
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Click to expand...
Click to collapse
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
jollywhitefoot said:
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
Click to expand...
Click to collapse
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Vesten said:
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Click to expand...
Click to collapse
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
jollywhitefoot said:
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
Click to expand...
Click to collapse
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Vesten said:
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Click to expand...
Click to collapse
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
jollywhitefoot said:
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
Click to expand...
Click to collapse
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Vesten said:
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Click to expand...
Click to collapse
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Wow, thankyou! I've been Googling RUU's all night at work and found nothing like this. Think I'll do that and flash the RUU and start afresh!
Getting a killer 17.4 kbp/s though. 100mb connection wasted. Ha!
jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Yay it worked! Using a stock image from that link. Something must of been really screwed up. I'm now re-rooted! Many thanks for your help!
Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS I hope I left everything else intact..
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
mount failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
Package expects build fingerprint of htc/htc_europe/htc_m8:5.0.1./LRX22C/448934. 13:user/release-keys...
Click to expand...
Click to collapse
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
My bootloader is unlocked atm and S-on...
Is it possible to recover the os in any way?
------
After trying to flash like 5 roms flashing InsertCoin worked somehow...
Qitsch said:
Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS
Click to expand...
Click to collapse
Why did you flash such an old version TWRP? That one is from about 3 years ago, and will cause lots of problems!
Couple simple rules to live by, when modding these phones:
1) Do not wipe things in TWRP willy-nilly, without knowing what they are, or what the result will be. The option to wipe "system" is in the Advance wipe section. It's called "Advanced" for a reason. That alone would have been a warning to be careful, and not mess with things, unless you know what you are doing. It also clearly says in TWRP wipe screen, that most of the time, the default wipe (cache, Dalvik/ART and data) is all you ever need. It says that for a reason.
2) Right after you install TWRP, and before messing around with anything, you should make a TWRP backup of your current stock ROM. Definitely do that, before trying to flash root, ROMs, or any other mods. That way, if anything goes wrong (or you simply screw up, and wipe system) you have a backup, that you can easily restore.
Qitsch said:
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
Click to expand...
Click to collapse
In general, you should never flash a file named "OTA" unless you know exactly what you are doing. The requirements for an OTA on this device are steep:
a) Must currently have the version number directly before the OTA number (you can't skip or flash the same number OTA)
b) Must have stock recovery installed (not TWRP)
c) Must match your version (CID, MID). Do you have the Euro version? You never stated this info.
Qitsch said:
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
Click to expand...
Click to collapse
This RUU is only for the US Developer's Edition version M8. Will not work on any other version.
Even if you had the US Dev Ed (which is unlikely) this RUU would require the firmware being flashed, before the RUU will install (thus, Error 155).
In short, it seems like you are just guessing at solutions. Not a good idea.
I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.
You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.
Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.
If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.