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.
Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!
Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk
If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk
So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?
Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.
I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.
What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.
At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App
To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!
Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
TheLastGringo said:
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
Click to expand...
Click to collapse
Hi,
Did you root your phone?
Did you flash the superwipe zip first?
Also are you getting full reboots with HTC splash screen then animation or just the animation looping? Sometimes I have to let mine loop for 5 minutes after first boot of new rom before it settles.
Sent from my Sensation XE using XDA App
I guess I hadn't done everything.. I didn't factory reset before flashing the new ROM... As soon as I did that it boot right in. That's a bit odd to me, as I didn't have to do that with my last phone.
Anywho, solved.
Sent from my Sensation using XDA App
Hello. I have a problem. At first I unlocked bootloader, rooted, put custom recovery, all the things, than I installed faux's hybrid first from fastboot ,but wifi would automaticaly turn off if i try to turn it on, so i flashed it with cwm as was one of the replies with the same problem. After that wifi was working properly. Than i installed xposed framework and uninstalled it uncorrectly and whatnot tried to change to art which turned to be a mistake. Basicaly my phone was really messed up, cuz i played a little too much with it. So i completely wiped it and went by the guide on how to restore stock firmware. I now have us retail version, but from the startup (with the original kernel) the wifi wasn't working. So i tried to install the kernel via cwm, but that didn't fix it. I don't know what's the problem. I also tried to copy /system/lib/modules files for hybrid kernel but nothing changes.. Maybe i could try with stock us retail 4.3 xt1032 files if anyone has them? I don't know im still a noob so if anyone of you has a solution or someething it would be kindly appreciated.
Thanks
I got my one SV k2_cl from boost a little over a month ago and got the bootloader unlocked and rooted, working fine until one morning it wouldn'tmake calls or texts. I tried to factory reset and when I tried to boot got stuck at the HTC logo. Took me 2 weeks to get it to even flash a Rom on here that will somewhat work. I've got WiFi and partial 3g 4g connectivity but no voice at all. When I try to use the phones its activation tool-error, tried manually programming phone- nothing. I'm stumped. Can someone please help me out here. Don't want to have to buy another phone if I can help it. The only guess I've got at the moment is that if I could get a stock original rom to flash I'd be good to go probably and just hold out on doing anything else to it until after the kitkat ota is launched. The few stock roms I've tried either wouldn't download for some reason or just won't flash right. Thanks in advance for any help guys. I've always been more of a hardware geek more so than software but I can usually muddle through following guides of course.
I'm not much into boost, but did you try to flash the available RUU?
help...
As a matter of fact I have tried that and unfortunetly the installer locked up on a reboot of the phone because the phone wants to do the "Android is upgrading # of #" on every boot. That was why I was thinking since adb/fastboot and the HTC One Toolkit all sorta work that if I could get ahold of a working stock rom to flash on there and I have a stock CWM backup still on my laptop from when I first got the phone rooted and everything working. But of course thanks for the tip anyway. I wish that would work. It seems to be the easiest way to install back to stock.