My brother tried to install a rom in rom manager. Did not work. He got stuck at the hboot screen. He panicked and tried fixing by flashing the newest ruu. It does the update then when you reboot it gets stuck at the white htc screen for ever. Not sure what he did is even fixable im used to the samsung phone and we just odin back. I have tried to reinstall his cwm and flash the ruu thru there but same result. He was rooted running bamf and he still has s-off even after flashing ruu. Any help or ideas would be greatly appreciated and to save time hit me up on gtalk @ [email protected]. Thanks fellows.
Did he make a nandroid?
Stratejaket said:
Did he make a nandroid?
Click to expand...
Click to collapse
That would have been to easy...lol. nope sure didnt!
Wow fail on the no backup! I'd try to reboot into recovery, load a new rom on the SD and try to flash that.
What did he use to gain root?
Can you verify he still has s-off?
Bootloader version?
Stratejaket said:
Wow fail on the no backup! I'd try to reboot into recovery, load a new rom on the SD and try to flash that.
What did he use to gain root?
Can you verify he still has s-off?
Bootloader version?
Click to expand...
Click to collapse
He used revolutinary to root. Still has s-off and hboot is 6.04.1002
Do a system wipe, cache and dalvik. Then try to reinstall a rom, not the RUU.
Stratejaket said:
Do a system wipe, cache and dalvik. Then try to reinstall a rom, not the RUU.
Click to expand...
Click to collapse
tried and no good. just goes to htc screen and keeps rebooting.
might be time to smash and file a warranty....lol
Is there a pg05img.zip still on the root of the sdcard? If so delete it.
mongo41 said:
My brother tried to install a rom in rom manager. Did not work. He got stuck at the hboot screen. He panicked and tried fixing by flashing the newest ruu. It does the update then when you reboot it gets stuck at the white htc screen for ever. Not sure what he did is even fixable im used to the samsung phone and we just odin back. I have tried to reinstall his cwm and flash the ruu thru there but same result. He was rooted running bamf and he still has s-off even after flashing ruu. Any help or ideas would be greatly appreciated and to save time hit me up on gtalk @ [email protected]. Thanks fellows.
Click to expand...
Click to collapse
I wish more people would stop flashing roms in Rom manager. Reboot to recovery clear data,cache,davlik cache, hell format system while you are at it, wipe it all 3 times for good measure. I have always followed the same steps from day 1 and never any issues with roms other than known bugs. Another thing when something doesn't go right don't just flash with no reguard to your device. If something does not work try to clear everything and reflash again. If that does not work clear everything and flash your backup (yes you should always make a back up) rant over.
If I helped you in any way please use the thank you button
Is your problems resolved?
Related
Hi guys. So here's my problem. I recently tried to update my phone to the latest version of NRG's Energy Rom using CWM. In the process I did a factory data wipe, and wiped the dalvik cache. I then flashed the rom as normal, but when I rebooted all I got was the white screen with the green HTC logo. It refuses to go any further. I can still get into recovery if needed, and I've tried a ton of different things, but to no avail. Anybody have any ideas as to what I need to do or is this thing hosed?
The phone is S-ON at the moment with an unlocked bootloader.
Any help is appreciated.
Mr.Moo52 said:
Hi guys. So here's my problem. I recently tried to update my phone to the latest version of NRG's Energy Rom using CWM. In the process I did a factory data wipe, and wiped the dalvik cache. I then flashed the rom as normal, but when I rebooted all I got was the white screen with the green HTC logo. It refuses to go any further. I can still get into recovery if needed, and I've tried a ton of different things, but to no avail. Anybody have any ideas as to what I need to do or is this thing hosed?
The phone is S-ON at the moment with an unlocked bootloader.
Any help is appreciated.
Click to expand...
Click to collapse
Flash the wipe script, flash the rom you wanted, when the phone boots up, let it sit for a few minutes, like 10 should be good.
Well I'll be damned. I could have sworn I tried that, but there we go. Thank you so much for the help.
Mr.Moo52 said:
Well I'll be damned. I could have sworn I tried that, but there we go. Thank you so much for the help.
Click to expand...
Click to collapse
Also, get rid of CWM and use 4ext recovery. It's in the dev section... And its the preferred recovery by most amaze users. I have a thread in Dev section
It allows you to flash kernel automatically when flashing ROM, that way you don't have to use a kernel flasher. Plus many other features.
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks for the info. I've been looking at recent posts and it seems I'm behind on a few things, including getting s-off.
Weird Problem
I had the same problem but I don't want to lock and re-unlock my bootloader. And this has never happened but my CWM Recovery isn't working. I didn't use 4ext bc this happened last time with that recovery. Is there any way to find the wipe script to use it from fastboot?
Tried kernel flashing; re-flashing recovery...second time this happened with s-on on speed rom
Had to re-wipe phone and re-flash everything...Got it working again! Weird problem though?!?!
Hopefully I can get some help from you guys I'm currently on hboot 1.12 HTC devunlock and I'm running TWRP 2.2.1. I tried flashing CMX but I get "unfortunately phone isn't responding" right after that it says the UI isn't responding and the dialog boxes keep appearing. So I can't get past the lock screen. I've already tried wiping and reflashing and it didn't help. Any help would be appreciated.
gespinal0301 said:
Hopefully I can get some help from you guys I'm currently on hboot 1.12 HTC devunlock and I'm running TWRP 2.2.1. I tried flashing CMX but I get "unfortunately phone isn't responding" right after that it says the UI isn't responding and the dialog boxes keep appearing. So I can't get past the lock screen. I've already tried wiping and reflashing and it didn't help. Any help would be appreciated.
Click to expand...
Click to collapse
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
megabiteg said:
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
Click to expand...
Click to collapse
I thought it was only if you had updated to 1.15 for the hboot that you have to flash the bootimg..... nvm ill try it once i get home
Definitely sounds like you might have a bad download. Also download the superwipe zip and use that too. With hboot 1.12 you should be fine to flash without any special procedures.
Sent from my EVO using xda premium
A known issue in CMX is that phone process will crash, it does this while the phone searches for a signal, once a signal is found it should stop. Just try waiting it out, it doesn't really affect anything, once the message is gone you will be fine
durandetto said:
Definitely sounds like you might have a bad download. Also download the superwipe zip and use that too. With hboot 1.12 you should be fine to flash without any special procedures.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
om4 said:
A known issue in CMX is that phone process will crash, it does this while the phone searches for a signal, once a signal is found it should stop. Just try waiting it out, it doesn't really affect anything, once the message is gone you will be fine
Click to expand...
Click to collapse
i tried the bootimg and i still had the same problem, but ill try waiting it out
megabiteg said:
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
Click to expand...
Click to collapse
That is only for HBOOT 1.15 and up. HBOOT 1.12 allows for flashing of kernel from recovery with S-ON.
When you say you tried "wiping and reflashing", what exactly did you wipe? You should do a factory reset, then wipe data, system, cache, and dalvik. Then flash the ROM.
bilbo524 said:
That is only for HBOOT 1.15 and up. HBOOT 1.12 allows for flashing of kernel from recovery with S-ON.
When you say you tried "wiping and reflashing", what exactly did you wipe? You should do a factory reset, then wipe data, system, cache, and dalvik. Then flash the ROM.
Click to expand...
Click to collapse
Im running Viper4g on my evo lte 4g its a sense based rom i wipe the system, then dalvik cache, and cache. Ill try the factory reset now.
gespinal0301 said:
Im running Viper4g on my evo lte 4g its a sense based rom i wipe the system, then dalvik cache, and cache. Ill try the factory reset now.
Click to expand...
Click to collapse
Don't forget data too
One user kept corrupting his phone with a backup of user data, I don't know how or where he got the relevant knowledge to obtain just an image apps and user data but it was corrupt and he stuck himself in an endless cycle of reformat and reflash apps and data. A human boot loop lol I was thinking about adding it to the troubleshooting guide but what are the odds that someone who doesn't know what they are doing will create a zip install of backed up data (or fail really since it is corrupt) and flash it *looks around in baited breath* well OK then
Well i think the factory reset worked now i get a not so frequent dialog saying process.phone.android has stopped. Should i reflash or just wait it out? lol
I would wait it out
I had this exact same problem. My issue was I had flashed a modified mail app that got rid of the Exchange Security Lock. Once I factory reset I was fine. When I tried flashing that Mail app again, I got the same Phone has quit error over and over.
gespinal0301 said:
Well i think the factory reset worked now i get a not so frequent dialog saying process.phone.android has stopped. Should i reflash or just wait it out? lol
Click to expand...
Click to collapse
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
xuohtx said:
I had this exact same problem. My issue was I had flashed a modified mail app that got rid of the Exchange Security Lock. Once I factory reset I was fine. When I tried flashing that Mail app again, I got the same Phone has quit error over and over.
Click to expand...
Click to collapse
I didn't use titanium backup the Play Store just started installing everything I needed which was why I thought it was weird. Everything is working great so far. Thanks to everyone for their input and help.
Google market back up has been a long time feature. Its just that OEMS won't include it or for some reason disable it. Every HTC Android phone I have own has asked permission for Google market back up but upon factory reset or flash, sense will disable it the automatic restore
bilbo524 said:
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
Click to expand...
Click to collapse
I also get the force close of the phone when I toggle airplane mode. Sometimes it doesn't stop and I have to reboot.
Sent from my EVO using Tapatalk 2
bilbo524 said:
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
Click to expand...
Click to collapse
echo....echo...echo..nah I kid, just a bit bored haha
Hey guys, I've searched the forum for a while but haven't quite found an answer to this, so I thought I'd post here. Before I start, I'd like to say, yes I am an experienced flasher and know most of my basic things. I've got a pyramid working perfectly, but this has been giving me many problems.
Basically, I just s-offed my HTC Evo 3D GSM, with an old CID of RO____001(I think), and HBOOT 1.53.
So now here I am, with my unlocked phone, running HBOOT 1.49, with SuperCID. My old ROM was Cool ICS, and I couldn't stand it, so I wanted to change over to stock Jelly bean, preferably AOKP. I've got the latest AOKP ROM, and 4EXT Recovery. I went into recovery and wiped my user data and cache and tried flashing the ROM, and Gapps of course, and then I rebooted, but it booted into Cool ICS again! With this happening, I tried wiping all partitions(including system, no SD card) and then my phone booted into a bright white HTC screen and didn't exit it. Parents are mad that my phone is broken now.
Please help! Much appreciated!
Flash stock and try again
Sent from my Evo 3D CDMA using Tapatalk 2
italy2200 said:
I tried wiping all partitions(including system, no SD card) and then my phone booted into a bright white HTC screen and didn't exit it. Parents are mad that my phone is broken now.
Please help! Much appreciated!
Click to expand...
Click to collapse
Sounds more like the actual ROM is corrupt.
Redownload the ROM you want to run. Do a full wipe of the phone, including cache. Then transfer over the files. You can use 4EXT to transfer files to the phone via usb storage mode.
Then try flashing the ROM.
If it still doesn't work, try flashing a different ROM.
If that still doesn't work, report back here or feel free to PM me.
DjDom said:
Sounds more like the actual ROM is corrupt.
Redownload the ROM you want to run. Do a full wipe of the phone, including cache. Then transfer over the files. You can use 4EXT to transfer files to the phone via usb storage mode.
Then try flashing the ROM.
If it still doesn't work, try flashing a different ROM.
If that still doesn't work, report back here or feel free to PM me.
Click to expand...
Click to collapse
Thanks for the reply, DjDom. I'm kind of in a bigger pickle here. My recovery partition won't even work now. This was happening before I formatted all partitions, each time I wiped my data, it wiped the 4EXT app and the recovery partition. Does this mean I need to use the RUU again? And will the RUU re s-on the phone?
italy2200 said:
Thanks for the reply, DjDom. I'm kind of in a bigger pickle here. My recovery partition won't even work now. This was happening before I formatted all partitions, each time I wiped my data, it wiped the 4EXT app and the recovery partition. Does this mean I need to use the RUU again? And will the RUU re s-on the phone?
Click to expand...
Click to collapse
Damn if you can't access your recovery then you are in a bit of a trouble.
Maybe your downloaded ROM got corrupted or it didn't complete downloading that's why it's always recommended to check the HASH after you download something.
Good Luck on recovering your device back!
Hreidmar said:
Damn if you can't access your recovery then you are in a bit of a trouble.
Maybe your downloaded ROM got corrupted or it didn't complete downloading that's why it's always recommended to check the HASH after you download something.
Good Luck on recovering your device back!
Click to expand...
Click to collapse
Na, I can still access recovery by simply flashing the .img... The ROM did finish downloading, as the HASH was proper, there's just a problem with recovery actually flashing to system.
Bump.. Come on guys, I really need help.. It won't even load bootloader anymore.
Flash a new recovery with Fastboot USB (I recommend TWRP or 4ext as recovery) Then go onto your recovery an flash the desired ROM.
Goodluck!
Lost data after Beast 4.3 / or to sideloading and dirty-installing the M7 rom. Flashing different roms/radios made no difference.
SOLUTION TO DATA LOSS:
LakerStar25 said:
Just a heads up to anyone that's on the Verizon version having extreme data loss. If you messed with your apn it could have screwed something up were you might need to run the RUU to fix. It happened to me and micromod. So if that has happened and have tried to get data back and nothing has worked you will need to
1. Nandroid then install the pre ota hboot
2. Relock
3. Backup internal memory then Run RUU
4. After RUU finishes do a factory reset.
5. Reboot and data should be back.
6. Unlock if desired or just install ENG hboot and install recovery and flash your nandroid and good to go.
Click to expand...
Click to collapse
Watercycle said:
Was running Newt's M7, and flashed beast 4.1 fine, wanted to try flashing beast 4.3
After flash it began to boot-loop and ( foolishly ) without a backup I had to use ADB sideload to reflash M7. That worked, but now I have no data, it won't detect the sim card. Tried reflashing the radios+hboot ( yes unlocked and S-off ) to no avail.
Backed up to a stock rom made after S-off but that also doesn't have data ( and keeps yelling "droid" every 10 seconds ).
Click to expand...
Click to collapse
at this point I would suggest going back and read the flashing your recovery. Then after you do that go back in and try and flash kernel again.seems like all your problems are caused by bad last of the kernel.
Watercycle said:
Was running Newt's M7, and flashed beast 4.1 fine, wanted to try flashing beast 4.3
After flash it began to boot-loop and ( foolishly ) without a backup I had to use ADB sideload to reflash M7. That worked, but now I have no data, it won't detect the sim card. Tried reflashing the radios+hboot ( yes unlocked and S-off ) to no avail.
Backed up to a stock rom made after S-off but that also doesn't have data ( and keeps yelling "droid" every 10 seconds ).
Click to expand...
Click to collapse
have you tried reseating your sim card?
slimc84 said:
have you tried reseating your sim card?
Click to expand...
Click to collapse
Yes, tried reseating, no luck.
Also just tried cube's 'return to stock' zip along with reflashing beast 4.1, still without phone/data
Watercycle said:
Yes, tried reseating, no luck.
Also just tried cube's 'return to stock' zip along with reflashing beast 4.1, still without phone/data
Click to expand...
Click to collapse
reboot your phone and toggle airplane mode off and on waiting about 20 seconds in between
slimc84 said:
reboot your phone and toggle airplane mode off and on waiting about 20 seconds in between
Click to expand...
Click to collapse
Tried airplane spam for 3 minutes or so, no go.
Currently on stock and just flashed cubed kernel and modules, still no data.
Watercycle said:
Tried airplane spam for 3 minutes or so, no go.
Currently on stock and just flashed cubed kernel and modules, still no data.
Click to expand...
Click to collapse
sounds like it may be a SIM card error...might have to get a new one....
SOLUTION TO DATA LOSS:
LakerStar25 said:
Just a heads up to anyone that's on the Verizon version having extreme data loss. If you messed with your apn it could have screwed something up were you might need to run the RUU to fix. It happened to me and micromod. So if that has happened and have tried to get data back and nothing has worked you will need to
1. Nandroid then install the pre ota hboot
2. Relock
3. Backup internal memory then Run RUU
4. After RUU finishes do a factory reset.
5. Reboot and data should be back.
6. Unlock if desired or just install ENG hboot and install recovery and flash your nandroid and good to go.
Click to expand...
Click to collapse
I have spent the whole day flashing and trying to get my data back. I am so happy that LakerStar took the time to write out those steps. After flashing RUU there was still no data, but factory reset afterwards did the trick!
Watercycle said:
SOLUTION TO DATA LOSS:
I have spent the whole day flashing and trying to get my data back. I am so happy that LakerStar took the time to write out those steps. After flashing RUU there was still no data, but factory reset afterwards did the trick!
Click to expand...
Click to collapse
awesome. Please change your OP title to note fix found please.
Hi,
I have a very strange problem now (at least for me).
First some facts about the phone: It's unlocked Virgin Mobile phone, S-off, rooted, and has a usable 4ext recovery installed.
I also did some days ago when 4ext was installed a backup before trying anything else.
After that I tried different ROMs and most of them booted fine after flashing, and I used the last 2 days a JB 4.3 ROM until I found problems with the camera and wanted to see how this is for one of the other ROMs I tried before.
But after try to flash another ROM, it was stuck with on the HTC logo (the same ROM I flashed before without any problems, and of course after wiping all internal partitions like always). Also flashing any other ROM didn't help - even restoring the backup from the original ROM didn't solved this. Only using fastboot from the computer to write the boot image changed the hanging on th HTC logo in a boot loop now - and still no usable flashing is possible.
Does anyone has any ideas what the reason for this could be and how it can be solved to have a working phone again?
Thanks!
mec75 said:
Hi,
I have a very strange problem now (at least for me).
First some facts about the phone: It's unlocked Virgin Mobile phone, S-off, rooted, and has a usable 4ext recovery installed.
I also did some days ago when 4ext was installed a backup before trying anything else.
After that I tried different ROMs and most of them booted fine after flashing, and I used the last 2 days a JB 4.3 ROM until I found problems with the camera and wanted to see how this is for one of the other ROMs I tried before.
But after try to flash another ROM, it was stuck with on the HTC logo (the same ROM I flashed before without any problems, and of course after wiping all internal partitions like always). Also flashing any other ROM didn't help - even restoring the backup from the original ROM didn't solved this. Only using fastboot from the computer to write the boot image changed the hanging on th HTC logo in a boot loop now - and still no usable flashing is possible.
Does anyone has any ideas what the reason for this could be and how it can be solved to have a working phone again?
Thanks!
Click to expand...
Click to collapse
Maybe your sd card is corrupted. Try another card if you have one around
What hboot?
Try wiping everything, then reboot recovery, wipe everything again
Then try and flash again
If all else fails try ruu through bootloader, you will still have s off
Sent from my PG86100 using xda app-developers app
donkeykong1 said:
Maybe your sd card is corrupted. Try another card if you have one around
Click to expand...
Click to collapse
It's the same with another SD-card.
hossman said:
What hboot?
Click to expand...
Click to collapse
It's hboot 1.50.5050
The hboot was only changed at the beginning after getting s-off. With this hboot all the ROMs I try now were working before.
However, for the original restore maybe this version could be a problem (hboot 1.58 was on the phone before), but should be no reason for the other ROMs to fail.
Try wiping everything, then reboot recovery, wipe everything again
Then try and flash again
Click to expand...
Click to collapse
Well, this works!
So far I wiped everything but then installed directly the ROM after it without a reboot. No I did like you proposed - wipe, reboot, wipe, flash - and it works again.
Is there a reason why it hasn't worked directly after wiping and needed a reboot between?
If all else fails try ruu through bootloader, you will still have s off
Click to expand...
Click to collapse
Just in case for the next time:
I can only find RUU for Sprint but not VM - do you have a link to a file for a VM phone?
Thanks a lot for the help!
Glad it worked, don't know why but there must have been an issue with recovery
Here is the pg86img I use for vm.
https://db.tt/eBcYZ7yu
Place on root of your sd and rename pg86img.zip
Reboot to bootloader and accept update
This will give you stock Rom and recovery and hboot...s off stays
So if you want to flash again, all you need to do is flash recovery...no unlocking necessary
Sent from my PG86100 using xda app-developers app