Hi All
Yep, there are a lot of posts about Desire's stuck on boot screens I know - and I've read them all but nothing seems to fins a solution to my problem sadly.
I'm having an issue running Oxygen 2.0.3 signed release on my HTC Desire, spec as follows:
Radio 5.14.05.17
HBoot 0.93
PVT4
S-ON
ClockworkMod Recovery v2.5.0.7
I did all the data, boot, and system wipes/formats recommended before installing new ROMs, and installed the zip from my SD card through ClockworkMod.
All is well on first boot - had it running happily for a couple of days. Then I turned the phone off and on again and it only boots as far as the white screen with the green HTC text, and progresses no further. When I go back to my Nandroid backup of the rooted stock ROM things appear to function as they should, if that makes any difference to a diagnosis.
I've tried reinstalling this ROM twice with the exact same result.
Can anyone help? I've had crashes with pretty much every ROM I've tried so far and, apart from this one considerable problem, Oxygen had been looking the most promising. I'm starting to wish I hadn't rooted at all - can't get a stable OS running at all since doing it, and getting really fed up
Thanks very much for any help.
Mark
I know this is an old treath, but I have exactly the same problem. Does someone knows what could be done to resolve this issue? I did the same thing as the topic starter.
Some info about my phone:
RAVO PVT1 SHIP S-ON
- Oxygen version 2.3.2
- HTC Desire GSM
- HBOOT version 0.93.0001
- RADIO version 5.11.05.27
Thanks in advance!
I have, several times, updated my radio files using the latest PG05IMG.zip found elsewhere in XDA. HBoot says that they are successfully update as MDMK9 and RADIO_V2. However, software number is 2.11.605.5, Android # 2.3.4 and HTC Sense 3.5, Bashband version 1.48.00.0932w_3,0.01.78.0916w_3.
Build number InfectedROM Eternity (NIGHTLY)
In other words, I can't get from 605.5 to 605.9. What am I missing? What am I screwing up? I rooted with Revolt a long time ago.
Thanks to any help,
Ron
I have a TmoUS HTC One S, and I unlocked bootloader, rooted my phone and flashed Pacman 22.3 on my phone. I like the rom, but it has slowed my phone and made it quite buggy. It soft-resets at least once a day and randomly gets stuck on lock-screen and I have to wait a couple minutes to try again. Anyway, those are just a couple of my annoying bugs that I don't want to deal with anymore. I'd like to just go back to the stock rom, but as I've found out, I can't restore from a previous backup.
As I'm relatively new to smart-phones, rooting, installing roms. I need a straightforward tutorial on how to flash the stock rom. I've read through the xda forums but cant seem to find exactly what I'm looking for. Any help would be greatly appreciated. And I apologize in advance if this wasn't the correct thread to post in.
PS - Not sure if this make any difference, but I have CWM installed as my recovery.
bizeekizay said:
I have a TmoUS HTC One S, and I unlocked bootloader, rooted my phone and flashed Pacman 22.3 on my phone. I like the rom, but it has slowed my phone and made it quite buggy. It soft-resets at least once a day and randomly gets stuck on lock-screen and I have to wait a couple minutes to try again. Anyway, those are just a couple of my annoying bugs that I don't want to deal with anymore. I'd like to just go back to the stock rom, but as I've found out, I can't restore from a previous backup.
As I'm relatively new to smart-phones, rooting, installing roms. I need a straightforward tutorial on how to flash the stock rom. I've read through the xda forums but cant seem to find exactly what I'm looking for. Any help would be greatly appreciated. And I apologize in advance if this wasn't the correct thread to post in.
PS - Not sure if this make any difference, but I have CWM installed as my recovery.
Click to expand...
Click to collapse
make backup first
change cid back to original (if needed)
flash stock jb recovery (extract from ruu or ota, or google it on xda)
flash latest tmous jb ruu. (latest ota is also availible in ruu form)
Along time ago I tried out a lot of aosp Roms. I tried cm10.1 and others like that. I have hboot 1.14 and I have s-on. And I'm always having Wi-Fi issues with aosp Roms. OK so about a month ago I was using viper ROM. Wifi was working correctly. It was on 4.1.1. I recently went to united basic ROM. Which is basically the jelly bean update. My kernel is 3.4.1 and I want to use illusion. But I keep hearing things about being on the latest HTC one s jelly bean ROM. (Which I'm not because I keep getting a message saying there is a new update) and I did not do the ota update I just flashed a ROM that gave me it. Please someone help I really am kind of stuck.
Illusion is using the 3.4 kernel. The "problem" with this kernel is that it needs the latest hboot (2.15?) & firmware. There are a few ways to get it, but one of the "easyest" ways is to simply go back to stock HTC RUU & update it. Right after that, you can simply flash illusion like any other rom. If your rom allready updated firmware & hboot, you should be good to go. Shouldn't be on hboot 1.14 anymore tough.
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
pahlerc1 said:
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
Click to expand...
Click to collapse
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Abe21599 said:
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Click to expand...
Click to collapse
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
pahlerc1 said:
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
Click to expand...
Click to collapse
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
pahlerc1 said:
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
Click to expand...
Click to collapse
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Abe21599 said:
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Click to expand...
Click to collapse
It was in a different thread, can't recall which.. I have been doing way too much reading I think it was in one last few pages of the venom rom thread.. I'll just wait for Venom and Skyfall to update their baseband to the latest 1.56 build. No worries. Thanks.
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
ebb said:
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
Click to expand...
Click to collapse
Okay thanks for the help. I always make sure to read first and create a backup, I've made the mistake once and took a long process to get it solved and won't let that happen again that's for sure! Thanks for the response, I just flashed Skyfall 2.5 and it is amazing!