Database Info

[Q] Desire HD problems with LeeDroid ROM

Hi all,
I'm new to this but I do have a fair knowledge of computers and moding so this is not all chinese to me. I recently got my new HTC Desire HD and decided to installa Lee's ROM.
Rooted my phone, did both Radio S-Off and S-Off, got ROM Manager installed clockwork recovery and flashed latest radio (26.04.02.17_M2). After applying the flash zip and rebooting phone stayed in HTC white screen for like 30 mins and still nothing happened. I did remove the battery and restarted holding down the volume button to go into recovery and restored the backup I previously made. Phone still stuck in HTC screen for over 20 mins now and nothing happens even after restoring original ROM. The only step I missed was to wipe data/factory reset. Should I do this now and then restore my backup or what? Help me pls on this, the phone is 1 week old I don't want to kill it already...
PS. Sorry for posting a new thread but as a new user it wouldn't let me reply to Lee's.
Thank you all in advance,
Cheers!

You should of at least made this thread under Desire HD section, plus you would get more response.
You got a boot loop. Nothing major and not a big deal since you can still get into recovery and such. How did you apply the new radio? You can't flash radios through the recovery.
If you haven't, then flash radio this way http://forum.xda-developers.com/showthread.php?t=896597 and see if you still get the boot loop.

Desire stuck on boot screen with Oxygen ROM - please help :S

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!

[Q] ROM and recovery issue after successful rooting

Hi everyone.. first post here.
I just successfully rooted my Nexus S (GT-I9020T, 2.3.4, GRJ22) using adb, recovery clockwork herring and su 2.3.6.1.
ROM Manager is working fine but I do have a couple of issues.
The recovery doesn't always stick and reverts back to the stock one from time to time (I have to flash again then from inside ROM Manager). Which could be a problem due to the next issue..
I've been trying to install some ROMs (Cynogen for instance) but in one version I get a looping boot screen and in an other it keeps going to the recovery screen. Luckily, it's the right one and I can restore a backup. I'm afraid it might revert to the stock recovery at some point and screw me.
Any thoughts on this?

I should have read some more threads first..
I fixed the recovery issue by renaming install-recover.sh using Root Explorer
So I guess I should just experiment to find good ROMs now.
Can anyone suggest a good ROM? I'm looking for improved battery use, slimmed down system, needs email apps (all google apps probably)

Sorted it all out (mount/unmount, delete caches, etc.)
It's working swimmingly now.
Running Cynogenmod 7 and loving it.

I am using Infinity 1.0.0, stable, fast and great battery life, it is a 2.3.4 rom

[Q] Help: ROM installation problem

Hello,
I have obtained S-OFF and root for my sensation. My first attempt at installing a new rom was successful, and I used Android Revolution 3.6.1. Success, and I was happy. Now I decided to change to 4.1.2 and it hangs on the boot screen after installing the rom.
Can someone please tell me why 3.6.1 works, and 4.1.2 doesn't? The procedure should be the same, correct?
Thanks in advance!

Did you use the Super Wipe zip?
Sent from my HTC Sensation 4G using XDA App

Yes, I used super wipe before installing each rom.

it might be your radio if you haven't updated it yet. thats the only other thing that could be missing. many people including myself have had successful flashes with 4.1.2 so thats not the problem. try updating your radio and super wipeing again.

Thanks for the suggestion. I updated my radio, but 4.1.2 still hangs on startup.

Did you forget something? Check Mike's tips and follow it. I flashed 4.1.2 four times today, it's ok.
Try another ClockworkMod Recovery. 4.0.1.4 from AlphaRev or 5.0.1.0 from ROM Manager is recommand in Mike's post. Mine is 5.0.2.0, just ok.

I followed the same procedure to flash 3.6.1 and when I flashed 4.1.2. For some reason, I can get only the first one to work, and not the other. I am certain both roms are working properly, but I was hoping to get some help as to why the one won't work on my phone.

Fixed: Let that be a lesson to you, remember to check your md5 checksum! Rom is now working perfectly.

I had faith in you the whole time been thinking about the possibilities all day

Thanks! Its all part of the learning experience I suppose.

Issues with kernel on 4.1.2, it has been superceded by 4.1.3, which is working fine and available now.
You did nothing wrong.
P.

having problem flashing deamonspeed
after i have succesfully flashed deamonspeed, my sensation bootloops at the htc screen..im using the cyanogenmod7 rom....could that be why its not working?

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.

I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk

I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA

Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.

Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.

I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though

I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).

I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.