Develop Bugs

I need help please

Hello all...My One X is in a mess. I tried to restore my nandroid back up but my phone keeps bootlooping. Ive wiped dalvik, fixed permissions, etc... and i even fastboot erase cache in cmd prompt. Still nothing. Im charging it now in recovery, but i have no other ROM in the memory to try and flash. I downloaded an RUU for O2 but, i cant even use that because i didnt update my phone prior to flashing ROMS, so the RUU is wrong and i cannot find the older version. Any guidance would be appreciated. Thanks.

mgf8384 said:
Hello all...My One X is in a mess. I tried to restore my nandroid back up but my phone keeps bootlooping. Ive wiped dalvik, fixed permissions, etc... and i even fastboot erase cache in cmd prompt. Still nothing. Im charging it now in recovery, but i have no other ROM in the memory to try and flash. I downloaded an RUU for O2 but, i cant even use that because i didnt update my phone prior to flashing ROMS, so the RUU is wrong and i cannot find the older version. Any guidance would be appreciated. Thanks.
Click to expand...
Click to collapse
So you didn't even flash the boot.img for the backup? It's located in /sdcard/clockworkmod/backups

mgf8384 said:
Hello all...My One X is in a mess. I tried to restore my nandroid back up but my phone keeps bootlooping. Ive wiped dalvik, fixed permissions, etc... and i even fastboot erase cache in cmd prompt. Still nothing. Im charging it now in recovery, but i have no other ROM in the memory to try and flash. I downloaded an RUU for O2 but, i cant even use that because i didnt update my phone prior to flashing ROMS, so the RUU is wrong and i cannot find the older version. Any guidance would be appreciated. Thanks.
Click to expand...
Click to collapse
I originally tried to flash ARHD but the file was corrupt and aborted. I managed to flash the boot.img and superwipe before hand. I'm wondering if this is why my phone wont boot up when i try to restore backup. Dont know what to do now.

tomascus said:
So you didn't even flash the boot.img for the backup? It's located in /sdcard/clockworkmod/backups
Click to expand...
Click to collapse
No...does that mean im screwed?

Try to flash different rom
If i helped you in any way then do click thanks
Sent by XDA Premium

coolprateek.kumar said:
Try to flash different rom
If i helped you in any way then do click thanks
Sent by XDA Premium
Click to expand...
Click to collapse
How do i get another ROM on my phone if my phone wont boot up? I'm stuck. Keeps bootlooping. I cannot find any boot.img for my nandroid backup either.

Hold power + volm down for 10-15 seconds until you get to bootloader screen man... if it doesn't work then you're doing it wrong.

tomascus said:
Hold power + volm down for 10-15 seconds until you get to bootloader screen man... if it doesn't work then you're doing it wrong.
Click to expand...
Click to collapse
I know how to get into the bootloader. I dont have any other ROM on my phone to flash. I have my back up which i tried to restore but i'm stuck in a bootloop. I dont have the boot.img in my phone for the nandroid.

Just a taught....
I don't know if you changed or upgraded the rom after you did the nandroid backup but if you have a bootloop it means boot.img doesn't match the rom.zip
You also need to flash boot.img with the ADB tools that matches your nandroid backup.
If you are not sure anymore, wisest and easiest thing to do is flash a new custom rom.
I would recommend you >> ARHD rom as they have a Superwipe script as well to clear all fat but leave storage in tact.
Your storage you can reach with Clockworkmod/mounts and storage/Mount USB Storage to copy the rom.zip and superwipe.zip to it.
Keep in mind that you will lose all your personal data like contacts and sms etc, all in internal memory.
mgf8384 said:
Hello all...My One X is in a mess. I tried to restore my nandroid back up but my phone keeps bootlooping. Ive wiped dalvik, fixed permissions, etc... and i even fastboot erase cache in cmd prompt. Still nothing. Im charging it now in recovery, but i have no other ROM in the memory to try and flash. I downloaded an RUU for O2 but, i cant even use that because i didnt update my phone prior to flashing ROMS, so the RUU is wrong and i cannot find the older version. Any guidance would be appreciated. Thanks.
Click to expand...
Click to collapse

mgf8384 said:
I know how to get into the bootloader. I dont have any other ROM on my phone to flash. I have my back up which i tried to restore but i'm stuck in a bootloop. I dont have the boot.img in my phone for the nandroid.
Click to expand...
Click to collapse
The boot.img should be inside the backup folder

Download a different rom and copy it to sd card through different phone....then install that rom
If i helped you in any way then do click thanks
Sent by XDA Premium

Nothing to Worry!
Ohk..Calm Down..there is nothing to worry at all.
Till the time u can go to Clockwork recocert all is well.
Now.
1.Download the ROM u want to flash.(And the boot.img Provided with it)
2.Boot ur into recovery Mode.
3.There will be a option mounts and storage.
4.Select Mount SD card(Connect ur phone to the computer before this)
5.Ur HTC ONE X STOrage will come up.now copy the ROM and the boot img on d card ..
6.Reboot and install the rom and flash the boot img.
Simple

Laurentius26 said:
Just a taught....
I don't know if you changed or upgraded the rom after you did the nandroid backup but if you have a bootloop it means boot.img doesn't match the rom.zip
You also need to flash boot.img with the ADB tools that matches your nandroid backup.
If you are not sure anymore, wisest and easiest thing to do is flash a new custom rom.
I would recommend you >> ARHD rom as they have a Superwipe script as well to clear all fat but leave storage in tact.
Your storage you can reach with Clockworkmod/mounts and storage/Mount USB Storage to copy the rom.zip and superwipe.zip to it.
Keep in mind that you will lose all your personal data like contacts and sms etc, all in internal memory.
Click to expand...
Click to collapse
Worked perfectly...thanx!

aman360elite said:
Ohk..Calm Down..there is nothing to worry at all.
Till the time u can go to Clockwork recocert all is well.
Now.
1.Download the ROM u want to flash.(And the boot.img Provided with it)
2.Boot ur into recovery Mode.
3.There will be a option mounts and storage.
4.Select Mount SD card(Connect ur phone to the computer before this)
5.Ur HTC ONE X STOrage will come up.now copy the ROM and the boot img on d card ..
6.Reboot and install the rom and flash the boot img.
Simple
Click to expand...
Click to collapse
Worked perfect. Thank You.

[Q] TWRP asking for encryption password after factory reset?

Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.

eris170 said:
Thought I'd try out the encryption in AOKP on my Nexus 7 (2013) and decided I didn't like it. I read that a "factory reset" in TWRP was supposed to remove it, although it would nuke all my files, sdcard, apps, etc. No problem, the thing is brand new so nothing really on it. After wiping however, when I boot into recovery now, TWRP is still asking for the encryption PIN. I thought I would just get into the shell over ADB and see what's going on but not able to do that either. I just get "?????????" when trying to view the device with "adb devices". I read something about erasing userdata, system and cache from fastboot and also another piece of info about flashing the stock recovery back to it, but not sure that's the best route. Any thoughts? Thanks.
Click to expand...
Click to collapse
A factory reset from inside TWRP does NOT wipe internal storage/sdcard. If you want to wipe everything you can either do it from inside TWRP with "advanced wipe" or just do a normal factory reset from Settings/Backup and reset. If you fastboot flash the userdata and cache images that would also be like a factory reset. If you wipe/erase the system you will need to fastboot flash the system image or flash a rom BEFORE you try and reboot.

wantabe said:
A factory reset from inside TWRP does NOT wipe internal storage/sdcard.
Click to expand...
Click to collapse
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else. When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things.
Should I just go find the stock OS image and recovery image and flash them over?

eris170 said:
Sorry, I meant to say I did the advanced wipe and smoked the data partition. I was going to go back and edit my post but it wouldn't let me do it for another five minutes and I went off and did something else.
Click to expand...
Click to collapse
I'm pretty sure that wiping data from inside advanced wipe will have wiped everything, that should have been enough to get rid of your encryption.
eris170 said:
When you say "fastboot flash" the system image, do you mean re-install TWRP with "fastboot flash recovery twrp.img" ?
Click to expand...
Click to collapse
No. The system image I was talking about is from the factory image. You have to extract/unzip the factory image a couple times before you can see the zip folder with all the images ( boot (kernel), cache, recovery, system and userdata). You had mentioned in your first post "erasing userdata, system and cache." If you erase system you will need to replace it otherwise your device does not have an os (operating system) anymore. One of many ways to replace it would be to fastboot flash the system image (fastboot flash system system.img) that is extracted from the factory image.
eris170 said:
I tried a different comp and was able to get to the device over ADB so I pushed aokp_flo_jb-mr2_milestone-1.zip over ADB to /sdcard and did the same with gapps-jb-20130813-signed.zip. TWRP installed them OK, but after reboot, the zygote process now keeps trying to restart com.google.android.setupwizard which errors out with a dialog box which says "Unfortunately, Setup Wizard has stopped". I touch "Ok" but the dialog just comes back. Looks like I've made a real mess of things
Click to expand...
Click to collapse
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
eris170 said:
Should I just go find the stock OS image and recovery image and flash them over?
Click to expand...
Click to collapse
I think in your case the easiest thing to do would be to flash the factory image and start over. You will then need to reinstall TWRP and then use TWRP to install/flash the supersu zip. My advice would be to do lots of research before flashing custom roms and custom kernels. After you get back to the factory rom you really need to use TWRP to do a backup (nandroid) BEFORE you flash any custom roms and kernels, with that done it will be easy as hell to get back to stock after experimenting with whatever! Don't rely on toolkits, install the android sdk and learn adb fastboot commands, it's not hard, hell even I can do it!
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4
I've never used this but looks interesting. [TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)

wantabe said:
. I've always used the stock rom on my Nexus devices so I'm not much help with anything else. But... just from looking at the names on the zips you installed I'm guessing the "jb" means Jelly Bean and the gapps you installed are almost a year old. So... WTH? ; )
Click to expand...
Click to collapse
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
wantabe said:
I think in your case the easiest thing to do would be to flash the factory image and start over.
Click to expand...
Click to collapse
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.

eris170 said:
Meh.. I like running the older stuff because it's usually faster... I mean as long as there isn't some gaping vulnerability in it.
Thanks for the link that saved me some time! Downloaded an flashed and encryption is finally gone. \o/ . Should be all good now.
Click to expand...
Click to collapse
One of the great things about android is having the ability to change what you don't like and for the most part it isn't hard to do. I did notice with the update to 4.4 better performance and fluidity on both my N5 and N7 so it might be worth checking out at some point. I didn't care for some of the changes like the ui sounds with the 4.4.1 update but it's all easy to modify. Anyway.. glad you got it sorted out.

[Q] Boot loop + Blue LED Flashing on rooted device

Hey everyone so I took my phone out of my pocket and it was stuck in a boot loop. I tried taking the battery out, volume up + power + home, volume down + power + home but nothing. I've tried booting it also without a battery.
I have Quantum running on my phone, and have never had any problems. The occasional restart but now my phone won't even get to the home screen. I get just a boot loop with normal sounds, and then my LED begins to flash. Then it just loops again ..
Don't really know what to do.
UPDATE: Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.

DELETED - irrelevant information.

StoneyJSG said:
DELETED
Click to expand...
Click to collapse
Why ?

Rovon said:
Why ?
Click to expand...
Click to collapse
Will your computer detect it if connected? (Odin, Heimdall, adb)

dawgdoc said:
Will your computer detect it if connected? (Odin, Heimdall, adb)
Click to expand...
Click to collapse
Yes computer is detecting it with Odin.

Rovon said:
Yes computer is detecting it with Odin.
Click to expand...
Click to collapse
What is on the phone's screen while the device is detected by Odin?
There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.

dawgdoc said:
What is on the phone's screen while the device is detected by Odin?
There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.
Click to expand...
Click to collapse
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"

Rovon said:
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"
Click to expand...
Click to collapse
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.

Rovon said:
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
Click to expand...
Click to collapse
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...
Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.

jason2678 said:
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...
Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.
Click to expand...
Click to collapse
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.
Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.

Rovon said:
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.
Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.
Click to expand...
Click to collapse
So I keep getting a bunch of errors with TWR. I tried installing AOKP but got stuck at a boot screen again, and after trying to wipe my phone I get an error message saying "Failed". Now I'm trying install Quantum again but get an error message saying "Zip file is corrupt". T__T
Going to try another rom..
Update: I've tried Quantum again and it finally installed but now I'm stuck in a bootloop again. This is so frustrating ...

It seems like you are on the correct track. Don't give up.
Hopefully it is not a matter of the internal sdcard going bad.
If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.

dawgdoc said:
It seems like you are on the correct track. Don't give up.
Hopefully it is not a matter of the internal sdcard going bad.
If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.
Click to expand...
Click to collapse
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything

Rovon said:
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything
Click to expand...
Click to collapse
Couple of thoughts:
Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.
It could be that a full wipe before trying again to flash the ROM would be what you need.
If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.

dawgdoc said:
Couple of thoughts:
Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.
It could be that a full wipe before trying again to flash the ROM would be what you need.
If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.
Click to expand...
Click to collapse
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.
Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.

Rovon said:
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.
Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.
Click to expand...
Click to collapse
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.

jason2678 said:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
Click to expand...
Click to collapse
+1
also to confirm modem , type in ...
getprop | grep version.baseband
"all i can really do , is stay out of my own way and let the will of heaven be done"

jason2678 said:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
Click to expand...
Click to collapse
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.
My bootloader is: I747UCDLK3
I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.
mrrocketdog said:
+1
also to confirm modem , type in ...
getprop | grep version.baseband
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Hmm .. that command didn't seem to pull anything up for me.

Rovon said:
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.
My bootloader is: I747UCDLK3
I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.
Hmm .. that command didn't seem to pull anything up for me.
Click to expand...
Click to collapse
LK3 is a pretty out of date bootloader, and in this case that might be a good thing.
You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/
For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.
This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.

jason2678 said:
LK3 is a pretty out of date bootloader, and in this case that might be a good thing.
You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/
For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.
This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.
Click to expand...
Click to collapse
Alright I'm downloading this now. Assuming this works, should I do an OTA update then root or am I safe to root the device from odin as soon as this bootloader is installed?

[Q] Can't boot after SuperSU binary update

Hey hey,
Today I had a SuperSU update through the Play Store which I installed. When that was done it told me I needed to update my binary or something along those lines. Since I have an HTC it told me I should install it through a custom recovery like TWRP. I already had TWRP installed, so I went ahead and did that. After it did its thing, it rebooted. Or well, tried. I stared at the boot animation for about 10 minutes, and then I rebooted. I still didn't get past the boot animation. Then I shut it off, went into my bootloader and via there into the recovery. Downloaded the latest SuperSU zip and flashed it through TWRP. Rebooted, but no dice. A couple of reboots later and I'm unable to properly shut off my phone or get into the bootloader/recovery. When I try to shut it off with Power+Volume up it simply reboots. I also can't see my phone through ADB.
My M8 has been converted to Lollipop GPE and have had no issues at all before. I am sort of familiar with ADB, recovery's etc, but I would not call myself an expert. Right now I'm at a loss, and any help would be great.
Edit: Tried pressing Power + Volume down in the 3 seconds it's off before rebooting after doing Power + volume down. I can now access the bootloader and recovery, but I'm still not quite sure what to do next.

Phone needs to be booted into OS or in recovery for adb to work, so that is probably the cause of your adb issue right there.
Does fastboot work (phone needs to be in bootloader fastboot mode)? If so, try fastboot erase cache and install TWRP again by fastboot.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
jsmits447 said:
Edit: Tried pressing Power + Volume down in the 3 seconds it's off before rebooting after doing Power + volume down. I can now access the bootloader and recovery, but I'm still not quite sure what to do next.
Click to expand...
Click to collapse
Since you can now boot recovery, restore your nandroid that you made.

redpoint73 said:
Phone needs to be booted into OS or in recovery for adb to work, so that is probably the cause of your adb issue right there.
Does fastboot work (phone needs to be in bootloader fastboot mode)? If so, try fastboot erase cache and install TWRP again by fastboot.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
Since you can now boot recovery, restore your nandroid that you made.
Click to expand...
Click to collapse
Thanks for the reply. My last nandroid was quite a while ago. Got so many things changed I might as well do a reset. That would have the same effect, yes?
I suppose there is not a way for me to fix what is wrong? I prefer not to lose anything obviously, but if I would it wouldn't be that much of a big deal.

jsmits447 said:
Thanks for the reply. My last nandroid was quite a while ago. Got so many things changed I might as well do a reset. That would have the same effect, yes?
Click to expand...
Click to collapse
No, not the same at all. Folks constantly misunderstand what a factory reset does. All it does is wipe user data, it doesn't touch the ROM. This sounds like the opposite of what you want.
At least you have a nandroid! I was half expecting you to say you never made one (all too common on these forums lately, for some reason).
jsmits447 said:
I suppose there is not a way for me to fix what is wrong? I prefer not to lose anything obviously, but if I would it wouldn't be that much of a big deal.
Click to expand...
Click to collapse
I'm like 95% sure we can fix it. Couple options I can think of: restore your TWRP nandroid, and just select to restore SYSTEM and BOOT (and not DATA) and this will just restore the ROM without restoring your user data.
This is assuming your nandroid was taken with the current GPE ROM at least?
Other idea is to find the same stock GPE ROM (assuming that is what you have) as a flashable zip, and either adb push it to the phone, or put it on removeable SD using a card reader connected to your computer. Then boot into TWRP and flash the ROM.
I'm thinking all that has happened is that the SuperSU flash somehow damaged the ROM, and we just need to restore the ROM.

redpoint73 said:
No, not the same at all. Folks constantly misunderstand what a factory reset does. All it does is wipe user data, it doesn't touch the ROM. This sounds like the opposite of what you want.
At least you have a nandroid! I was half expecting you to say you never made one (all too common on these forums lately, for some reason).
I'm like 95% sure we can fix it. Couple options I can think of: restore your TWRP nandroid, and just select to restore SYSTEM and BOOT (and not DATA) and this will just restore the ROM without restoring your user data.
This is assuming your nandroid was taken with the current GPE ROM at least?
Other idea is to find the same stock GPE ROM (assuming that is what you have) as a flashable zip, and either adb push it to the phone, or put it on removeable SD using a card reader connected to your computer. Then boot into TWRP and flash the ROM.
I'm thinking all that has happened is that the SuperSU flash somehow damaged the ROM, and we just need to restore the ROM.
Click to expand...
Click to collapse
Yeah, for once I decided to create a backup when I'm told to. I'm actually not sure it's the Lollipop nandroid. I made it 10 februari 2014, but there's a chance it's the one from Kitkat before I upgraded to Lollipop. Any way I could figure out? Could I make my problem worse by flashing the Kitkat one on the Lollipop if I wanted to try and see which one it is by flashing?
Thanks for clearing up what a factory reset does! Great to know.

jsmits447 said:
Could I make my problem worse by flashing the Kitkat one on the Lollipop if I wanted to try and see which one it is by flashing?
Click to expand...
Click to collapse
It might lead to a firmware-ROM mismatch (the nandroid backs up and restores the ROM and user data, but not firmware), breaking WiFi or other things. But nothing that isn't reversible.
Just make a nandroid of your current setup. Then worst case if you just restore back to your present situation.

redpoint73 said:
It might lead to a firmware-ROM mismatch (the nandroid backs up and restores the ROM and user data, but not firmware), breaking WiFi or other things. But nothing that isn't reversible.
Just make a nandroid of your current setup. Then worst case if you just restore back to your present situation.
Click to expand...
Click to collapse
Alright, will do. Be right back.

Just restored the nandroid from the 10th of december in twrp. It now asks me if I want to install SuperSU. Should I?

I went ahead and also installed SuperSU when it asked me to. Didnt even get to the boot animation then. Only saw "Google" and the little open lock. I have now restored to my Lollipop nandroid I just made.

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