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
Hey guys, I really hate to be the guy that asks these questions, but I've spent the past two days here looking for an answer but haven't found much that's quite like what I'm experiencing.
I have a google play edition of the htc one m8 and I was trying to get s-off and I installed insertcoin via philz recovery (I realize now this was probably a mistake since google play editions aren't compatible with sense based roms?). Ever since I've tried to boot up, it tries, then ends up restarting into recovery mode.
Things I've tried:
Installing the 4.4.4 gpe RUU, this failed with a (99 unknown fail) error.
Restoring a nandroid backup of the google play edition (gpe3.zip) from this thread. This fails with a set_perm issue (error 7).
I'm kinda at a loss. Anyone have any insight here?
GPE partitioning is different from Sense versions. So you can't flash a Sense ROM, unless you change to the Sense partitioning scheme.
I think trying to flash the Sense ROM borked up the partitions, and that is why restoring the GPE nandroid won't work.
GPE RUU should fix you up. You need to relock the bootloader to run the RUU, since you are s-on. That is the reason for the RUU error.
redpoint73 said:
GPE partitioning is different from Sense versions. So you can't flash a Sense ROM, unless you change to the Sense partitioning scheme.
I think trying to flash the Sense ROM borked up the partitions, and that is why restoring the GPE nandroid won't work.
GPE RUU should fix you up. You need to relock the bootloader to run the RUU, since you are s-on. That is the reason for the RUU error.
Click to expand...
Click to collapse
Thanks so much man!
Unfortunately I'm now getting a "12 signature verify failure". I googled this and most of the results said it's because the phone has root (I think the nandroid I mentioned I tried to flash in the previous post comes with root...), so I downloaded the "unsuperuser.zip" from here and tried running it, and restoring the default recovery then locking and trying the ruu again, but still no luck! Any ideas?
technicaltonic said:
Unfortunately I'm now getting a "12 signature verify failure". I googled this and most of the results said it's because the phone has root (I think the nandroid I mentioned I tried to flash in the previous post comes with root...), so I downloaded the "unsuperuser.zip" from here and tried running it, and restoring the default recovery then locking and trying the ruu again, but still no luck! Any ideas?
Click to expand...
Click to collapse
I forgot the GPE RUU is not an "official" signed RUU, so you can't run it with s-on.
What happens if you re-install custom recovery and try to flash a GPE based custom ROM (adb push ROM to the phone, or put on SD card with a USB card reader from your computer)?
technicaltonic said:
Thanks so much man!
Unfortunately I'm now getting a "12 signature verify failure". I googled this and most of the results said it's because the phone has root (I think the nandroid I mentioned I tried to flash in the previous post comes with root...), so I downloaded the "unsuperuser.zip" from here and tried running it, and restoring the default recovery then locking and trying the ruu again, but still no luck! Any ideas?
Click to expand...
Click to collapse
redpoint73 said:
I forgot the GPE RUU is not an "official" signed RUU, so you can't run it with s-on.
What happens if you re-install custom recovery and try to flash a GPE based custom ROM (adb push ROM to the phone, or put on SD card with a USB card reader from your computer)?
Click to expand...
Click to collapse
He can also try doing a factory reset from stock recovery ... that could get the partitions back in order
clsA said:
He can also try doing a factory reset from stock recovery ... that could get the partitions back in order
Click to expand...
Click to collapse
Doubt that would help. All a factory reset does is wipe /data (user data) partition.
redpoint73 said:
Doubt that would help. All a factory reset does is wipe /data (user data) partition.
Click to expand...
Click to collapse
As I understand it, a factory reset from the bootloader/phone does what you described .. however a factory reset from stock recovery actually reformats the data partition returning it to it's correct size. I could have it wrong but that's what works on the M7.
redpoint73 said:
I forgot the GPE RUU is not an "official" signed RUU, so you can't run it with s-on.
What happens if you re-install custom recovery and try to flash a GPE based custom ROM (adb push ROM to the phone, or put on SD card with a USB card reader from your computer)?
Click to expand...
Click to collapse
I tried flashing the skydragon lollipop and it worked!!! Thanks so much man! I feel a bit like an idiot, cause this was my actual goal, and I got caught up thinking it wouldn't work because of the state of my phone.
Thanks much for your help guys!
technicaltonic said:
I tried flashing the skydragon lollipop and it worked!!! Thanks so much man! I feel a bit like an idiot, cause this was my actual goal, and I got caught up thinking it wouldn't work because of the state of my phone.
Thanks much for your help guys!
Click to expand...
Click to collapse
Okay, I spoke too soon. It sorta works... Basically the first run works as long as I don't interrupt it but afterwords it reverts to a boot loop again. If I re-flash it and let it start uninterrupted again things are okay for the first run again but subsequent restarts start the bootloop again. I did notice that the sd card location seems to alternate between /sdcard and /sdcard/0 I assume this is the partitioning scheme thing you guys were talking about... Any idea what might be resetting the partitioning scheme, or causing subsequent restarts to fail?
EDIT: To anyone that may have the same problem, I ended up fixing this by installing the rom from this post. After that I was back to normal. Hallelujah.
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!
Hey guys, hope someone can help me. A few days ago i've flashed the new android m gpe rom and everything was fine. Then somehow i lost root access and tried to fix it. Unfortunately, i'm not even able to flash the fixed rom that was posted a few days later, so i decided to come back to the skydragon sense rom. And for some reason i can't. I try to flash the .zip, it opens in aroma installer, everything goes fine until the installation itself starts. The rom starts to flash, comes to ~20% and then the system just reboots. I've tried both twrp and filz touch, nothing helps.Also supersu doesn't flash properly. I'm not really professional in this, so i might just do somethng wrong, hope someone can help:crying:
Btw i'm s-on.
UPD: I've made an advanced wipe and the everything works now, so if you have the same problem then just try to do the same, see if works.
Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?
redpoint73 said:
Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?
Click to expand...
Click to collapse
I just flashed the GPE ROM, i'm s-on as i said.
Would this ROM work on Verizon HTC One M8
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help
Are you still able to go into TWRP recovery and are you also rooted?
crispinsaro said:
Are you still able to go into TWRP recovery and are you also rooted?
Click to expand...
Click to collapse
Who was this question adreed to? If you asked me, then i am able to get into recovery, but the supersu doesn't seem to flash, at least i don't get the root.
Miramontes said:
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help
Click to expand...
Click to collapse
Well, the problem is that i'm s-on, so i hope there is any other solution for this
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
paulmartyn said:
I've tried both twrp and filz touch, nothing helps.
Click to expand...
Click to collapse
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
Miramontes said:
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue
Click to expand...
Click to collapse
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
Will try to erase everything later,maybe tomorrow. Twrp says everything's fine, and aroma doesn't say about any issues, just reboots. Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is. Anyway, thanks for an advice, will try that and tell if it helps or not
redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
I tried filz just to check, because on skydragon everything was fine.
I use twrp 2.8.7.0
hboot 3.19.0.0000
radio 1.25.21331147a1.o6g(if that's what baseband is)
tomorrow i'll try everything you guys advised, see if there is a solution. thanks for the support man
Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!
crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
well, i've tried to make an adwanced wipe as you advised and it worked thanks man, i thought i'll stay on that rom 4ever.
flashing skydragon now:victory:
crispinsaro said:
Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!
Click to expand...
Click to collapse
guess the problem was caused by different android versions
redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
So i've tried to make a FULL wipe and finally it worked, everithing works fine now, installin' skydragon and waiting for a better 6.0 ROM
Guess i can close the thread now as my problem is resolved.
paulmartyn said:
Guess i can close the thread now as my problem is resolved.
Click to expand...
Click to collapse
Happy that solved your issue, it is normally said that to install a new rom you have to do a full wipe before hand, glad it worked for you though
paulmartyn said:
Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is.
Click to expand...
Click to collapse
You mean flashing SuperSU after Skydragon (you don't specify)? If so, its not necessary, as all custom ROMs are pre-rooted unless explicitly noted.
Also, older versions of SuperSU won't work on Lollipop, so depending on what version SuperSU you tried (again, you don't specify), that may have been the reason for failure.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
crispinsaro said:
I am sure you factory reset through recovery before installing the new ROM
Click to expand...
Click to collapse
I wouldn't be so sure, if the OP didn't state it.
crispinsaro said:
I normally go on advanced wipe and tick all the boxes
Click to expand...
Click to collapse
I would caution users about following this device literally. It is not necessary to wipe internal storage and/or SD card when flashing a ROM (although particular users may have reason to do so for specific reasons). And if the user has their nandroid or ROM.zip on that partition (and they must have the ROM on one of those, unless they intend to sideload it), its going to get wiped out; causing some confusion and probably panic.
The advice I normally give is: Its called "Advanced" for a reason, and don't wipe it unless you know what the result will be; and you have a legitimate reason to do so.
For instance, I've lost count of the times folks have posted that they wiped system, and don't understand why the phone will no longer boot into OS. Or they wiped internal storage or SD card; and didn't know that it would wipe out their nandroids.
The TWRP default wipe (data, cache and Dalvik) says "most of the time, this is the only wipe you will ever need" and it says that for a reason. If one runs into problems flashing a ROM, they might elect to wipe system. So like I said, a legitimate reason to wipe a particular partition.
But on the other hand, I've done a countless number of ROM flashes on a number of devices (including Skydragon), and never wiped any partition outside the "default wipe", and never had any such issues. Even wiping system (which many swear by) I suspect is often a placebo. When you flash a ROM, system will be wiped by definition, so doing it manually is redundant.
I suspect the failure by the OP was not wiping data and/or cache (they never specified they did that originally or not).
Thats true yes, i dont think I made it clear to do the default TWRP wipe first to see if it would solve anything and then try advanced wipe if all fails, but again with caution.
After reading a litte I've got one question...So if I want GPE rom do I need to convert my phone to GPE or just to flash the rom ?!
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.