Develop Bugs

Boot loop with any ROM based on official 2.2

Hi,
I was hoping some of the smart people here might be able to point me in the right direction for a solution to a problem I am having.
As the thread subject says; I've flashed several ROMs based on the official 2.2 release and I end up with a boot loop at the first HTC logo, it never makes it to the quietly brilliant screen, it just re-boots continuously until I pull the battery.
However, ROMs based on 2.1 boot fine, both official ones and modified ones obtained here on the forum. Also, the 2.2 based DeFrost ROM boots fine.
The actual flash process seems to go fine, with no errors being reported.
I've tried wiping/factory reset before I flash, after I flash, but the result is always the same.
I've tried with and without the latest radio installed.
I've tried booting with the SDCard and SIM removed, but no luck.
I've even tried downgrading from bootloader 0.80 to 0.75, again with no difference.
A bit of background info;
My Desire is a generic unbranded model.
Yesterday, I did try to install the OTA 2.2 update, but something messed up during the flash process and I ended up with a corrupted recovery partition and (once again) a boot loop.
Thankfully, I managed to flash an older RUU file and things are back to normal, except for the in-ability to boot any ROM based on the official 2.2 release.
If anyone can help I would be forever in your debt, as this really is driving me crazy.

I had the same problem when I installed the new 2.2 HTC ROM without wiping...
Anyway try to wipe both factory reset and all caches with both amon ra recovery port and clockwork recovery...

Same problem... but fixed I fixed it installing this: http://forum.xda-developers.com/showthread.php?p=7483900

I have same same loop like that
I dont know why? I use r5 modaco custom rom. it seems well. but when I try to use edge/3g, it starts loop booting. if turn off edge/3g, the phone works perfectly.
after that, I tried to flash another ROM, Wipe Factory reset, Wipe Cache, Wipe Dalvik, even wipe ext but it still happens
I put out SIM, the phone boot correctly( maybe just reboot one time). but put SIM in, it reboots.... sometime the phone vibrate 5 time at HTC screen .
somebody can help me?
ps: how to know wipe dalvik work perfectly? I cant see any info about it done

I had the same problem with the first rooted official rom I tried to install, then I restored to my modaco mcr-r5 (2.2) rom, updated to the new radio and then installed the rom from nickiberli via rom manager and it worked.
btw, I selected wipe data in rom manager when prompted, lost all my apps and data but the setup wizard ran when it booted up first time.

Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.

try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now

raz2133 said:
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
Click to expand...
Click to collapse
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.

ratykat said:
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
Click to expand...
Click to collapse
Thanks for the suggestion, but I just tried this ROM and it wont boot for me either.

bakedecake said:
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
Click to expand...
Click to collapse
I do have an ext partition on my SDCard and I have tried ROMs with and without A2SD. In fact, the ROM I have used for most of my tests is "Rooted Official HTC Android 2.2 (FroYo) ROM [Market issue fixed]", which I don't think has A2SD.
I have tried booting with 3 different SDCards so far, and of-course I have tried with no card.

[Q] Help.... phone stuck in saying "CyanogenMod 7"...

HI... i updated my phone with cyanogen 7 rc2, but after it booted up it's stuck in the animation that says cyanogen mod 7 , and the blue android sign... in comes than goes, again it comes... about 20 min stuck... what to do???

It sounds like you need to go into recovery mode and delete all your caches. If you are using ClockworkMod recovery do the following (make sure you are backed up first):
Delete all user data and info (under wipe data/ factory reset),
Wipe cache (under wipe cache partition),
Wipe Dalvik Cache (under advanced).
Then once you've done that try installing and running the ROM again.

i done that one time... for info im using AmonRA.. i cleaned all the cache and everything also... and installed again... nothing happens... fortunately i restored my nand backup and booted my phone with the OTA again... waiting for some answer.... do u think that installing stable version can fix this?

Sounds like a bad flash. I had rc2 running for a month or so with no issues. I've had times when the rom just doesn't install properly ans reflashing fixes it.
Download the zip again, if possible check md5 to make sure it's all good, make sure you have the desire/bravo GSM version, clear everything and flash just the rom and nothing else. If it boots, then go back and flash your gapps and whatever else you want.
Sent from my HTC Desire using XDA App

thx for replying.. as i was waiting for your reply, i download the cm 6 that is a stable version and checked, it has the same problem too.. i also downloaded GingerVillain 1.6 and it had the same problem too. do u think the problem might be that my phone is "s-on"? and how should i know if my phone is s-on or s-off... when i was rooting my phone with unrevoked, i checked the option that says disable security, but i'm not sure if it's disabled.... because i can't install un-signed zip packages....
any reply?

That definitely sounds odd. Its definitely not an issue with S-ON/OFF, nothing you've done here requires S-OFF to work properly.
Lets just make sure you're following all the steps.
In amonra, you've done your nandroid backup, so no need to do it again. There's no point having a non working backup
Go to wipe and wipe data/factory reset
Wipe davlik cache
Wipe sd-ext (shouldn't need to do this one as you don't have apps2sd yet, but better to be safe)
Now you flash your update.zip, then reboot and you should be fine. The only other thing I can perhaps suggest if every rom you flash sticks at boot is to perhaps try clockwork recovery instead of amonra. Apart from that we might have to wait for folks more knowledgeable than myself cause I'm all out of ideas.

thx for reply.... in meanwhile , i s-off ed my phone and it has the same problem too... i have problem with all cm and gingervillain roms.. but i don't have any problem with leedriod... one more question that maybe the problem is that i have android 2.2 installed, but gingervillain and cm use android 2.3 ... this maybe the problem.... and that's why leedroid works right, because it uses android 2.2.... i'm going to check OxyGen roms... i will post the result here...

i also faced same problem CM7 .. i tried CM6 and it went on fine..

heyyy... right after i posted the reply , i went to recovery and wiped anything, then installed gingervillain 1.6, and everything's fine now... it booted up and now im setting it up.... im going to check the cm 7 too.

i tried cm7 rc2 ... and it was fine and now im using it... here's a how to for solving the problem...:
1.S-OFF your device with AlphaRev : http://forum.xda-developers.com/showthread.php?t=805811
2.Install the AlphaRev Recovery(S-OFF Image will do it automatically).
3.Go to recovery and install the rom...
4.Boot up and it should not go to system and it should stay in loop as the problem was..
5.Now you should reboot your device into recovery... there are two ways to do this... either take the battery off and put it on, then boot to bootloader by pressing the volume down and the power key and select recovery , or the second way connect it to your computer and start adb and run this command:
adb reboot recovery
6.In AlphaRev recovery first wipe the cache partition , wipe user data, and factory reset...
7.then install the rom (either cm7 or gingervillain)...
8. boot up , and now you have the system running...
This solved my problem... reply if it didn't yours...

hooo.. it worked for me now. just kept update.zip in a new SD card and not flashed google apps..

im very happy that i solved one's problem.. ... thread marked as solved...
*UPDATE* : now i realized that we can mark it as solved.. !!! hehe.. Admin do it for us...

[Q] DHD won't stop rebooting...

My phone is rooted and I have had many custom roms on my phone, but now when my phone boots, it gets to the lock screen, and reboots automatically... I can get in to the recovery mode, and I flashed couple of different roms, but it ends up the same way - the moment it boots, it starts restarting itself... Any help??

If you flashed without wiping, that might be a problem. I know that when this happened on my old G1, clearing the dalvik cache helped. To do this, go into recovery, then go to "Advanced > Wipe Dalvik Cache". Also, while your in recovery, Fix permissions (same menu as clear dalvik cache), then reboot. The boot should take as long as a first boot, maybe a little quicker, but it should stop it.

another thing it could be is the wifi, on CM7 for example i'd get bootloops if i enabled the wifi on the 1st boot, dunno if the current nightly still does it coz i dont enable my wifi until i done one complete reboot after flashing a new ROM.
Or flash http://forum.xda-developers.com/showthread.php?t=868720
Full wipe 1.3 for ext3 and 1.5 for Ext4 roms , then re flash the Rom ur having problems with.

hmohammed43 said:
If you flashed without wiping, that might be a problem. I know that when this happened on my old G1, clearing the dalvik cache helped. To do this, go into recovery, then go to "Advanced > Wipe Dalvik Cache". Also, while your in recovery, Fix permissions (same menu as clear dalvik cache), then reboot. The boot should take as long as a first boot, maybe a little quicker, but it should stop it.
Click to expand...
Click to collapse
I tried all of this... still no luck... It's the same - boots up, the lock screen shows it self, and then it keeps rebooting...
Any new ideas?

Hmmmmm
What rom are you on at the moment?

It doesn't matter. I've changed couple of them. It started on ARHD, but it's the same when i flash cyanogen... Maybe I should try flashing radio? Because, when it boot's up, just before restarting, i see that it's not connected to the mobile network... And it first started happening when I landed in Turkey... Can it have something to do with their network??

I wouldn't think it's anything to do with the network....but i would flash the reccomended radio (the one from the 4th of january)
http://forum.xda-developers.com/showthread.php?t=877295
Also, wipe every partition manually (except /sdcard !) from the advanced menu in clockworkmod recovery, then use the wipe/factory reset option in the main menu, then flash the rom. If that doesn't work, the only thing i could suggest is using a WWE RUU from here:
http://forum.xda-developers.com/showthread.php?t=824357
Make sure you flash one for either 1.32.405.3 or 1.32.405.6 (those are the only rootable firmwares, and the unbranded ones don't like being downgraded, so you'll need a goldcard if you flash higher). When the RUU finishes, it'll bring you back to stock, then you can root the phone again

As I thought, flashing radio helped!! Thank you very much!!

[Q] boot loop on reboot

Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:

You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img

BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail

In fastboot type fastboot erase cache

Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?

With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?

BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.

Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.

I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.

same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.

boot.img

Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.

BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics

Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.

[Q] Stuck at "Google Logo" after Rom Flash?

I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.

ThePedigree said:
I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.
Click to expand...
Click to collapse
need to reformat /system as well.

dipole said:
need to reformat /system as well.
Click to expand...
Click to collapse
..,before or after I flash it?

ThePedigree said:
..,before or after I flash it?
Click to expand...
Click to collapse
Before, you need to clear out remnents of old rom, reformat cache, dalvik, data (not sd) and system then flash rom and gapps if needed. Reboot.

dipole said:
Before, you need to clear out remnents of old rom, reformat cache, dalvik, data (not sd) and system then flash rom and gapps if needed. Reboot.
Click to expand...
Click to collapse
Thank you for your advice. I wish I had better news...
I Wiped the parts you mentioned. Installed ROM. Cleared Cache and Dalvik using the TWRP button that shows after installation. Rebooted, and there was no different result.
Tried it with both ROMs. Same results both times, except the non-stock ROM gives up and reboots in recovery mode after about three minutes. The stock ROM just stays stuck at Google logo.
Restore from backup still works.
Any other ideas, folks?

ThePedigree said:
Thank you for your advice. I wish I had better news...
I Wiped the parts you mentioned. Installed ROM. Cleared Cache and Dalvik using the TWRP button that shows after installation. Rebooted, and there was no different result.
Tried it with both ROMs. Same results both times, except the non-stock ROM gives up and reboots in recovery mode after about three minutes. The stock ROM just stays stuck at Google logo.
Restore from backup still works.
Any other ideas, folks?
Click to expand...
Click to collapse
Did you convert to GPE? If so you can't flash back to sense just yet
Also, check md5 of your download, might be corrupted

ThePedigree said:
I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.
Click to expand...
Click to collapse
Did you flash a gpe rom or convert using ruu?

an0ther said:
Did you flash a gpe rom or convert using ruu?
Click to expand...
Click to collapse
Converted using ruu. Thanks for your interest!

ThePedigree said:
Converted using ruu. Thanks for your interest!
Click to expand...
Click to collapse
You have to convert back to sense. The gpe partitions are the incorrect size for a sense rom. Follow steps in post #2 in this link to get back. Next time just flash a gpe rom. The only advantage to converting is ota updates, which in a rom, they will update those too.
http://forum.xda-developers.com/showthread.php?t=2708589
if you get lost let me know, when it says flash firmware, you have to use the "fastboot oem rebootRUU" mode that you used in the conversion

ThePedigree said:
Converted using ruu. Thanks for your interest!
Click to expand...
Click to collapse
HOW TO RETURN TO SENSE:
-Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
(fastboot oem rebootRUU, fastboot flash zip (whatever you name it).zip FLASH TWICE 1ST WILL FAIL )
-Boot Into OS
-Get Decrypt Error
-Boot back into Bootloader
-Flash TWRP- http://techerrata.com/file/twrp2/m8/...2.7.0.2-m8.img
(fastboot flash recovery recovery.img)
-Boot into Recovery
IMPORTANT!!!!!!
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom

charlieb620 said:
HOW TO RETURN TO SENSE:
-Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
(fastboot oem rebootRUU, fastboot flash zip (whatever you name it).zip FLASH TWICE 1ST WILL FAIL )
-Boot Into OS
-Get Decrypt Error
-Boot back into Bootloader
-Flash TWRP- http://techerrata.com/file/twrp2/m8/...2.7.0.2-m8.img
(fastboot flash recovery recovery.img)
-Boot into Recovery
IMPORTANT!!!!!!
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom
Click to expand...
Click to collapse
Thanks for your continued attention and generous efforts.
By "Boot into OS" do you mean simply reboot after the flash? I've done that and it shows the animated Google logo with the four squares of moving color. It seems to stay there for as long as I let the phone sit.
When does the Decrypt Error come into play?
Thank you!

ThePedigree said:
Thanks for your continued attention and generous efforts.
By "Boot into OS" do you mean simply reboot after the flash? I've done that and it shows the animated Google logo with the four squares of moving color. It seems to stay there for as long as I let the phone sit.
When does the Decrypt Error come into play?
Thank you!
Click to expand...
Click to collapse
Fastboot reboot
Also if that doesn't work, try wiping everything with Philz recovery
Sent from my HTC One_M8 using Tapatalk

charlieb620 said:
Fastboot reboot
Also if that doesn't work, try wiping everything with Philz recovery
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Just to clarify.... after flashing ROM I simply "fastboot reboot". How long (approx) should I wait and watch the Google logo before I assume things didn't work? Is more than 10 minutes normal?
Thanks much!

Less than 3 mins. If nothing change recoveries and start the process over. Try Virtuous rom fresh flash
Sent from my HTC One_M8 using Tapatalk

charlieb620 said:
Less than 3 mins. If nothing change recoveries and start the process over. Try Virtuous rom fresh flash
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Charlie, just curious, I'm happy with GPE conversion, but with your instructions are you saying that you reset the partitions back to sense? Or are you simply forcing the sense ROMS to use the GPE partitioning scheme?

dipole said:
Charlie, just curious, I'm happy with GPE conversion, but with your instructions are you saying that you reset the partitions back to sense? Or are you simply forcing the sense ROMS to use the GPE partitioning scheme?
Click to expand...
Click to collapse
Putting the partitions back where they belong if you want to go back to sense.
Sent from my HTC One_M8 using Tapatalk

whew thanks for this thread