[Q] Issues after flashing new ROM - Desire HD Q&A, Help & Troubleshooting

Hello. First post here, want to say thank you to everyone that works hard on these images and boards, you all do a great job.
Here's my issue, and I'll try to be as specific as I can. I'm semi-new to all this but I had someone helping me that knows a lot more than I.
Recently, I got an HTC Inspire HD (Same thing as the Desire HD) on the AT&T network. It was a freebie, so I decided to flash some custom stuff on it.
Currently, my backup image is ClockwordMods, and the main OS, I first tried Cynogenmod's unofficial 11 version. When that failed, we removed it and attempted Xperia4.4.2-beta-2 with OTA-2.0.1-for-Beta-2 and ota-2.0.2-for-Beta-2. I used philz custom touch interface which works beautifully. I followed the directions to a T. wiped the phone for a new image, wiped all the cache (even under advanced as it told me), and flashed in the new OS, rebooted, flashed in OTA 1, reboot, flashed in OTA 2, reboot. But it hangs on the HTC screen. Now, it's not bricked, as I can still access the menu.
here is what is getting me. I loaded on an image called PD98IMG found here:
http://forum.xda-developers.com/showthread.php?t=1248608
It rebooted, but it hung at Parsing for 20 minutes. So, after spending 12 hours trying to remove the battery case (Whoever invented this phone can die, and more like 3 minutes, but still a pain in the butt) I popped the battery, rebooted and mounted the SD card and removed the PD file. However, when i got into the bootloader, it would still look for this file! So I put it back on, and now it hangs again at Parsing. So this morning I bought a mini-SD adaptor, slapped it in the PC and removed the PD file again, redownloaded it, and attempted it again. This time it took, it parsed for about 2 seconds and seemed to be fine. So now, I rebooted the phone, and let it sit on the HTC screen for about 15 minutes (5 is norm from what i'm told, 10 is long, I figured 15 was safe), and nothing. It still hangs. I'm going to attempt another flash and put Cynogenmod 11 back on and see if it could be a bad download, but this is where I'm stuck at. Any help would be appreciated. Hopefully this was enough detail.
Edit: Ok, I put cm-11-20140609-UNOFFICIAL on from http://forum.xda-developers.com/showthread.php?t=2533007, i wiped data, cache, etc etc, everything, and still hung on the HTC screen. Not quite sure what's going on.

Related

Fixed: Verizon Vogue Stuck at vzw splash screen

This is the first time I've messed with this phone I've flashed many different models in the passed but this is the only one that is giving me issues and the worst part is that its not mine so any hell i will greatly appreciate it.
Here is what i did read what ever i can to get more accustomed to this phone. and searched everywhere to help me figure out what i can do.
So i flashed the unlocker. Coke 2.31
after i did that i flashed nfsfan's 1.5 rom using usb cable.
no i cant get into the operating system at all it hangs at the vzw splash screen.
Is there a way to get this phone back to normal? i cannot connect thru activesync and when i tried to reflash using sd card it shows the loading screen for a split secon then goes back to the bootloader.
Please help its my bros phone i need it up and running asap.
Thank you
This post helped quite a bit
ArcaneMagus said:
Just thought that I would post what happened to my phone and the steps that eventually recovered it in case it helps somebody else:
My phone was stuck with "No Radio" on the boot loader screen and the SPL as "SPL-2.31.CoKe", but none of the 3.x ROMs would flash properly that I tried. So here are the steps that eventually recovered it (mostly...):
1.) I installed the ROM above from the tri-color screen (power+camera+reset). I still had no radio, but it was letting me past this and booting up to WM. http://forum.xda-developers.com/showthread.php?t=357762
2.) I then re-flashed the 2.31.CoKe boot loader (not sure if this step is necessary but listing what worked...)
3.) I tried to install RUU_Vogue_VZW_WWE_3.14.605.1_Radio_3.37.78_Ship.exe but it failed at 10% restarting to RUUNBH screen and the installer gave me Error [290]: Invalid Command
4.) I then tried to install the latest sprint ROM straight from the HTC site:_Touch by HTC (Sprint)_RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_2_Radio_3.42.30_AM_NV_2.04_Ship this looked like it was going to fail at the same part the Verizon rom did as it rebooted at 10% to RUUNBH screen, but the Sprint installer did something (I heard the computer lose and gain connection multiple times) and eventually it went right back and continued on from 11% and finished successfully.
5.) Rebooted and I had a radio now! Rather then risking trying to install the Verizon ROM again I went straight to the custom ROM I had originally started out with: NFSFAN 6.5 V6 which is working fine for me, except the GPS which is what started out my adventure of the last 3 days...
Just a note: for all flashes except the final one I simply waited till it was at the "Tap the screen..." stage till flashing. I never let any ROM but the final one run it's customization.
Click to expand...
Click to collapse
The above method works on a Vogue that is stuck on the bootloader screen with no radio.
Or if you get a rom to install and it stops at a windows screen that says no radio.
the only difference i tried was i didn't use the HTC Official Sprint rom, as i could not find it.
I used this rom.
RUU_Vogue_4350_ALLTEL_WWE_3.10.671.1_RS3.42.30_NV2.02_PRL30031_SHIP.exe
I let all customizations run on the last rom update.

[Q] Note 2 locks on boot

OK, I seem to be having a hell of an issue with my note 2. I rooted it about a week ago and installed TWRP, a couple days ago I decided to try a new rom. It booted up and everything seed fine except that I would keep getting some type of out of service error, so I decided to try a different rom, SwampMonster. I installed it though the TWRP (obviously) and it was successful, at least so TWRP said anyways. So Upon first boot it seemed to be booting fine with the Orange circle and after about 20 seconds it stops and the screen went black. As I have seen this plenty of times before I let it sit for over five minutes. Also when the Orange circle disappeared the computer beeped to indicate that it had been disconnected. Now I can only get into recovery and kies will not connect. I also cannot access TWRP.. can anyone give my a bit of advice. I was thinking of using a rom that I can install with oden but I can only find zip file based roms. Thanks in advance. Oh also, ODIN does make a connection

[Q] Question about RUU

Hi All,
I have a VZW Htc One M8, and I have been playing with it when have gotten the chance recently. I have installed/flashed an RUU before to correct an issue I ran into (trying to take an OTA) and everything went smoothly. As I said I took the OTA, but kept the RUU from the previous time I used it (first mistake). I am s off so I am hoping that is going to save me here.... This brings me to my problem.
I was trying to flash Viper Rom, but at the end of the setup I kept getting a popup saying setup has stopped, and I was unable to see a homescreen, but the phone was working. I decided to revert back to stock using the old RUU (be gentle) and it loaded and I hit yes to begin. About 10 second in it stopped and wanted me to reboot... I was in the middle of doing something else when it happened so I rebooted back to the bootloader and my OS line was in red. I then went back to recovery and restored my very recently created backup of my stock rom, which worked. I then went back to the boot loader to look at what was in red more closely and it is now blank. It says OS but then nothing after.
I have since gotten the new RUU that I should have used, but it seem to hang on the last part of the loading (put in on my external sd card) and my phone works... but the boot take forever and the VZW logo doesn't come up anymore. It almost seem like the phone boots fine but the HTC ONE logo stays until the phone screen turns off and when I hit the power button to turn the screen back on the phone is booted. My question is... should I 1) try the old RUU again and then take the ota since I am s off I have seen that technically it should work. 2) let the phone sit at the loading of the newer RUU and see what happens (I haven't tried seeing if the old RUU will load yet) or 3) count my blessings and deal with a non completely broken phone?
I realize I made a few errors while doing this, but I am hoping that s off will allow me to correct the problem. Any help would be greatly appreciated.
Issue should be resolved
Sorry to everyone that read this... I didn't make it all the way through the thread where I found the new RUU, and the thread tells how to resolve the problem with not loading all the way. I am going to try the fix after work.
Edit 1: problem resolved... I am an idiot

Can H811 Bootloader Be Re-Locked?

I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?

Stuck on google logo boot screen after twrp recovery & then factory reset

Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.

Categories

Resources