Develop Bugs

[Q]CM7 Nightly #186 keeps freezing on bootscreen?

So I boot my phone, and sometimes when I get to the unlock screen, the screen will lock itself up. Then, when I push the lock button to turn off the screen it wont turn back on so I have to remove battery etc. What do I do to stop it?

what CPU settings do you have? any extra apps running that could cause a wakelock problem? Alternate kernels or settings?
Did you happen to restore system data with Titanium Backup after you flashed or anything?
It could be any number of things causing wake problems.
Need a bit more info but if you haven't messed around with too many things after flashing, you may have done a bad flash and you might have to do a superwipe and reflash again.

Im running on 1.1 ghz (1113 mhz)
2. dont know
3. Yes
4. Bout to flash V rom lite 1.0.3

gkenga said:
Im running on 1.1 ghz (1113 mhz)
2. dont know
3. Yes
4. Bout to flash V rom lite 1.0.3
Click to expand...
Click to collapse
if you came from another ROM that wasn't CM7, and used a program (like titanium backup) to backup system data, and then restored it to CM7 you could be having an issue there.
Also, if you didn't properly wipe data/factory reset before flashing CM7, again it could be problems with that.
I'd recommend you do a superwipe and re-flash and give it another go unless you want to do some advanced troubleshooting into problem apps or processes.

Same thing with pyromod, it would work for a while, then it would bootloop or hang on HTC boot screen. What's a superwipe?

superwipe is a flashable .zip that wipes everything it can thru recovery to ensure you have a clean flash when you install a ROM.
I'm really not sure what can cause the issue on 2 different ROMs unless you're restoring some bad stuff with Titanium Backup thats causing issues.

Search superwipe it wipes the phone and clears efs, make sure after reflash you don't restore system data.

killj0y said:
Search superwipe it wipes the phone and clears efs, make sure after reflash you don't restore system data.
Click to expand...
Click to collapse
Elaborate on the last part, and I already installed it lol, for some reason idk if im doing it right but everytime I do it, it wont either reboot into recovery or it wont let me load a rom afterwards

That's strange it shoud go back to recovery, but does it still wipe your phone? Are you running it in recovery by installing from sd option and using the trackpad? And in TB when you batch restore it has an option for restore missing apps with data first option under restore, use that one and not the one a few down that says restore apps + system data.

I honestly can't remember if it goes back to recovery or boots the rom. But as long as it says wipe successful, efs successful and the rom reflects it you should be good.

Well when I do it, my phone wont boot into recovery, and it wont install a rom right without me installing it a couple of times
---------- Post added at 04:39 AM ---------- Previous post was at 04:37 AM ----------
killj0y said:
That's strange it shoud go back to recovery, but does it still wipe your phone? Are you running it in recovery by installing from sd option and using the trackpad? And in TB when you batch restore it has an option for restore missing apps with data first option under restore, use that one and not the one a few down that says restore apps + system data.
Click to expand...
Click to collapse
No im not using the trackpad and im installing from sd root
---------- Post added at 05:31 AM ---------- Previous post was at 04:39 AM ----------
Actually nevermind, My phone was getting stuck because cmw 5.0.2.0 has bugs which was getting stuck on the HTC screen. gonna try the 4.000 versions

In recovery you make selections from the trackpad, the power button is kinda like a back button. In the bootloader ther power button is for selections. Make sure your using the volume buttons to move up and down and the trackpad button for selections in recovery. Also if it is wiping for whatever reason, when the phone finally boots up te normal way regardless of how. Is it wiped ie stock, no apps that didn't come with the rom etc...

gkenga said:
Actually nevermind, My phone was getting stuck because cmw 5.0.2.0 has bugs which was getting stuck on the HTC screen. gonna try the 4.000 versions
Click to expand...
Click to collapse
Try 3.0.2.4, that should be the last perfectly working one.

x2 3.0.2.4 all the way

martonikaj said:
Try 3.0.2.4, that should be the last perfectly working one.
Click to expand...
Click to collapse
That's the one I flashed because it seemed perfect. Phone has been working fine now ever since, now I'm going to try PyroMod again, or stick with CM7 nightly 186 and find a good kernel, any suggestions?
Btw, already performed superwipe.

gkenga said:
That's the one I flashed because it seemed perfect. Phone has been working fine now ever since, now I'm going to try PyroMod again, or stick with CM7 nightly 186 and find a good kernel, any suggestions?
Btw, already performed superwipe.
Click to expand...
Click to collapse
The stock CM7 kernel is superb.

martonikaj said:
The stock CM7 kernel is superb.
Click to expand...
Click to collapse
Very much so sir. I had bluetooth, GPS, WiFi, signed on battery draining apps and it stood on 30 minutes on 100 and max brightness.

Cant't flash any roms

First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.

just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.

scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.

lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?

drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.

lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.

scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download

lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.

lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).

drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.

If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem

drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.

lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)

drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...

hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.

lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.

[Q] restored a nandroid backup and now stuck on boot screen

help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options

houston33 said:
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
Click to expand...
Click to collapse
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.

xunholyx said:
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
Click to expand...
Click to collapse
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?

408
so from where i am now i can just go to twrp and install android rev 21? or do i have to use adb sideload?
is 21 even compatible?
i swore i wasnt gonna mess on with this phone.........

houston33 said:
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
Click to expand...
Click to collapse
You sure can. The newer firmware is needed for 4.4.4 ROMs. If you had 2.5, reflash it. It will work with the newest firmware as well. Just not the old stuff.
Here's a pointer: A dirty flash of the ROM you are currently running will reset your tweaks, and often fix problems you are having. When I start having glitches, I first reboot. If that didn't work; and I can't find a solution on XDA easily, I reflash my ROM; the dirty way. It really does help to clear up stuff, especially if you are using themes and tweaks.

Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp

houston33 said:
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
Click to expand...
Click to collapse
In TWRP, you can manage files easily.
Click advanced > file manager
There you can copy files, move them and change permissions. Plus deleting and renaming them.

[please close]Can't flash any other rom after flashing the Android 6.0 gpe rom

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 ?!

TWRP - Unable to mount storage (Moto Z Play on Nougat)

​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.