Hoping somebody can help me resolve my bootloader issue. 9/10 times, when I turn on my phone, it does not go past the boot loader. Sometimes it does boot but says "Shutting Down" anywhere between 5-30 minutes after booting. My bootloader screen says the following:
MECHA XD ENG S-OFF
HBOOT-1.04.20000 (PG0510000)
MICROP-/
RADIO-1.16.00.0223r
eMMC-boot
Feb 23, 2011
I didn't have any issues post root (except for slow GPS lock), and I kept declining the firmware update before this happened, however, I don't believe it was pushed as I am still prompted to update the firmware when I successfully boot. I must admit, however, that the PG0510000 doesn't look familiar. I'm thinking that may have changed. Any suggestions or assistance would be greatly appreciated. Thanks in advance!
Maybe update your CWM to the latest version.
Absent that, maybe go through the downgrade process to apply the RUU. It will wipe your data.
Then once you have that rooted, booted & backed up, maybe download and install a rooted stock ROM.
The PG doesn't sound like it's for the thunderbolt. I'd remove it from the SD card. Assume the SD card is FAT32 format with ample space?
Sent from my ADR6400L using XDA Premium App
I had a very similar issue that turned out to be a kernel conflict or corruption. If you are running a Sense ROM, download and flash a new kernel such as Ziggy's or Imoseyon's. Boot into recovery/clockwork and flash it there. Boot up and see if that works! Also, clear the Dalvik cache and regular cache before you boot up.
Related
My problem is that the phone wont boot pass the Android flash screen. It does get past the first Vodafone screen.
My hardware is the 32B running Hboot = 1.33.0004 (SAPP10000)
what I have done so far is to be able to boot to RAv1.2.1G I have been able to back my phone up using android (and restore).
I thought using this procedures I would be able to able to add customs ROM by just renaming them to update.zip, they seem to load into the phone just get stuck on the above screen.
I haven't done anything with the SPL (Hboot) as to me it appeared booting to Rav1.2.1G does this for me.
I also have not flashed the Rav1.2.1G image to the phone, instead using the fastboot option each time I was to perform the rom update.
Any ideas way the phone wont get past the second screen?
make sure you have 'wiped' data, if you have the 3 partitions on your sd card, make sure you have formatted over the ext3/4 one.
Update the zip again, and pray lol
I have tried wiping the data after the upgrade and not the before, I'll give the before a go.
I only have one partition on the sdcard which was formated in windows 7
Cheers wiping data just before the update of the ROM fixed the issue.
pls connect the usb to pc and post the output of
Code:
adb shell logcat
cheers
EDIT: nevermind, you solved in the meantime
hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.
It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?
I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.
eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?
So I have a weird problem.
I have a Sensation that's been rooted and unlocked to S-OFF. Recovery flashed ok and works but no matter what rom I try, it will boot to the splash screen then show the beginning splash animation (quietlly brilliant) and hang there and make zero progress.
-4Ext touch recovery works fine. I can boot into it and it does everything just fine in regards to clearing cache/data/dalvik etc and flashing roms.
-bootloader reports S-OFF but also says *LOCKED* at the top
-When resetting the phone and also when charging, the LED flash fires.
- Have tried wiping phone, reformatting, clearing data/cache/dalvik etc none do anything
-4ext recovery tools report that the partitions are misaligned?
So, technically it's not bricked but it wont run any ROM I install on it. Does anyone recognize these symptoms? How do I get past this? Thanks for any information.
If you are trying to flash ics roms you need to have the latest firmware installed. Have you done this?
Sent from outer space 3000 years in the future (with my now extremely outdated, but still freaking awesome, HTC Sensation Z710e)
PaulieP said:
So I have a weird problem.
I have a Sensation that's been rooted and unlocked to S-OFF. Recovery flashed ok and works but no matter what rom I try, it will boot to the splash screen then show the beginning splash animation (quietlly brilliant) and hang there and make zero progress.
-4Ext touch recovery works fine. I can boot into it and it does everything just fine in regards to clearing cache/data/dalvik etc and flashing roms.
-bootloader reports S-OFF but also says *LOCKED* at the top
-When resetting the phone and also when charging, the LED flash fires.
- Have tried wiping phone, reformatting, clearing data/cache/dalvik etc none do anything
-4ext recovery tools report that the partitions are misaligned?
So, technically it's not bricked but it wont run any ROM I install on it. Does anyone recognize these symptoms? How do I get past this? Thanks for any information.
Click to expand...
Click to collapse
Hi,
It sounds like your are missing the firmware update.
Look HERE
Read it carefully,and follow all the step.
Long time listener, first time caller.
I have the latest hboot 1.45.0013, S-On, Unlocked with HTC Dev Tool.
I used the Hasoon2000 tool to install SU, CWM, and a recovery image. I then used the instructions in the thread (http://forum.xda-developers.com/showthread.php?t=1508556) to install ICS and obtain root installing pyr-o-ice sense 1.1.1 (http://forum.xda-developers.com/showthread.php?t=1469615) Everything worked, created nandroid backup and installed titanium.
Some buttons didn't work, so I looked for updates and found Virtuous ROMs. So, I used CWM to clear dalvic, flashed boot image of the Virtuous Inquisition then used CWM to install zip. Bootloop. ROM just hangs on black screen with white V for 15 to 20 minutes.
MT4GS thread stated that Primadonna and Inquisition were comparable, so I followed the same proceedure, flashed Primadonna boot image then installed ROM through CWM. This time there was tmobile splash screen, but the same system hang.
At this point I tried to restore a recovery, but CWM could not find one. Used Astro to delete all boot images from SD root, assuming this may be the problem, and flashed a Virtuous ROM again. Same problem.
Based on this thread, I thought it might be the kernal, and tried flashing the pyr-o-ice boot image that worked initially. (http://forum.xda-developers.com/archive/index.php/t-1628171.html). No dice. CWM could not install the ROM (error 1)
So, at this point, I used CWM factory reset and wipe all data. And of course that made things worse, because the SD card with recoveries was wiped. I used adb to push the recoveries from Hansoon's toolkit, but stock recovery was not available (red triangle screen hang) and cwm could not mount the SD card.
So, at this point I used CWM to format SD card (blank anyway), and at this point adb failed to recognize the decive and I could no longer fastboot into recovery or hboot through adb. (volume down + power stopped working with pyr-o-ice install)
if i remove the battery and hold power + volume while using an adb reboot hboot command i can get into hboot about every 10th attempt. adb doesn't recognize the device ("waiting on device", or adb devices yields a blank list); however the phone in hboot will transfer to usb fastboot when connected with a cable.
i looked at pushing a zip file through adb to the sd root, but that was ineffective (adb does have write access to the sd root, maybe because i am s-on?). i purchased a second sd card, and copied the recovery images from hansoons toolkit and rebooted into recovery. still went to tmobile splash, followed by V-screen bootloop.
i looked at placing a stock ruu on the sd and naming the file PG59IMG.zip, but because i'm S-on i can't flash radios, so that's out.
So, here we are. Iffy access to fastboot, 2 sd cards, a lot of determination, and a persistent bootloop.
Can someone, PLEASE help me?
Thanks!
AFAIK, you cannot flash the boot.img with CWM if you are S-ON, you *MUST* use Fastboot to flash that. So, before you messed it all up, if you had just extracted the boot.img from the ROM and flashed it using Fastboot, it likely would have worked just beautifully.
Try booting into recovery and doing a regular flash of the ROM, THEN a fastboot flash of the boot.img.
SOLVED!!
Thanks to the folks heading up the HTC Unbricking Project (http://forum.xda-developers.com/showthread.php?t=1627881) ESPECIALLY Dexter93!! who patiently unraveled this for me, and Blue6IX for the Restore to Stock instructions in the Developers Reference Guide (http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24) I'm back to stock, and ready to try it all again!
Can someone send me an apk that automatically clicks the thanks button for selected developers at regular intervals?
Thanks again!
Solved???
Fuzi0719, thanks for your reply. I may have written this inappropriately, but what coded in the command prompt was "fastboot flash boot boot.img".
The ROM zip file was placed on the SD card, and I rebooted into recovery, and used CWM to install zip from SD. I'm new to this so I may have used the wrong term for installing the zip through CWM, the boot image file was always handled through the above command.
I'm back to "stock" at this point, but when I boot into the bootloader, the phone looks for PG59DIAG.zip and PG59DIAG.nbh before PG59IMG.zip.
It then asks if I want to install the update. (This is after I have already installed the "update", and the phone reset itself even with my old wallpaper.) When I got to the home screen there was a white circle in upper left corner of the status bar, with "check content" message. Each time the screen locked (default 30 seconds) unlocking it took me to the mytouch splash screen with the green circle and white background for about 10 seconds before resuming.
Each time I check to see if the phone registers requiring any updates. It doesn't. Two installs of the PG59IMG.zip. "recovery" eliminates the unlock splashscreen, and wiped any customizations. However, the phone will not manually boot into the bootloader; I have to use adb. Hboot reinstalls the PG59IMG.zip as an update every time.
If I accept it reboots within seconds like a fresh doubleshot. If I decline the "update" it reboots to the Tmobile MyTouch 4G Slide text splash screen, then moved to the green circle screen for a few minutes before I get to the homescreen.
Blue6IX was looking for help with these last month (http://forum.xda-developers.com/showthread.php?t=1580077), so maybe they are just extraction files that HTC sends with the OTA update that would prevent my phone from trying to install the "update" every time?
In any case, my question at this point is after coming from such an unstable point with my phone, is this what every relocked bootloader does? Or, is this a problem that means something else is still wrong with the system? Because taking it back to stock has not solved this.
Thanks.
Thanks for clarifying, you wouldn't believe the number of people who fail to follow that one simple step of fastboot flashing the boot.img, so that's why I stated that. So, now you have the phone relocked, and running a stock ROM (the 1.55?), but with CWM 5.0.2.7? Were you wanting to update to the 1.63 ROM? I'm unclear on what it is you want to do. For one thing, if you've already flashed the PG59IMG then I would delete it off the sd card so it doesn't keep trying to load it.
Yup.
It was just that simple.
Mainly I wanted to make sure that my phone was stable before I went back to unlock the bootloader, etc.
Went back to HTC, got a new token (just in case), and I'm creating a nandroid backup right now. Thanks.
I really appreciate it.
Hopefully the next time I get stuck, it's just as simple to fix, but far less embarrassing.
Hey guys, I sold my One M8 to my little brother's friend a few months ago. It's Unlocked, S=Off, and SuperCID with the following:
HBOOT = 3.16.0.0000
RADIO = 0.56.20.0321
OpenDSP - V38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
TWRP V2.7.0.2
Since he's had it, he says he's only flashed Liquidsmooth, MIUI, and the stock rom. He swears the phone was running great for the past month or so on the stock rom. According to him, he hasn't flashed anything in at least a month. Last night, he plugged it up like usualand woke up to the phone completely powered off. When he booted it, it boots normally and soon after unlocking it, it reboots. This has been the case since I received it back from him (to fix). It's stuck in a bootloop that I cannot fix. Shortly after booting the rom (stock), it will reboot.
What I've tried:
Flashing a new rom in TWRP.
Wiping everything in TWRP (including system w/ and w/o the system partition mounted)
Fixing permissions in TWRP
Flashing SuperSu in TWRP (don't ask why, Googled it and someone said it fixed theirs)
All of this just continues to reboot to the same stock rom that it was already on. Shortly after booting, it would reboot as if I'd made no changes, wipes, etc.
So I figured I'd update TWRP. I downloaded TWRP_Recovery_2.8.2.1_M8_CPTB.img and flashed it in fastboot (without using fastboot oem rebootRUU) It was successful (or so it seemed). When I reboot recovery it still shows 2.7.0.2. So I downloaded ruuM8_TWRP_2_7.zip, tried to flash it from fastboot but when I "Fastboot oem rebootRUU" it jumps back to the bootloop so I put it on the ext_sdcard and renamed it to 0P6BIMG.zip. Hboot flashed it successfully but still the version didn't change.
So after all has failed, let's flash the stock RUU......So I grabbed this RUU - http://forum.xda-developers.com/showthread.php?t=2727831, renamed it to 0P6BIMG.zip and put in on the external sdcard (remember fastboot just kicks me into a bootloop when I fastboot oem rebootRUU). Using the sd card method, It took forever to flash the system partition, extracting and installing about a half dozen times. Eventually everything passed and it prompted me to press power up to reboot. AND IT BOOTS BACK TO THE SAME LOCK SCREEN.....AND REBOOTS AFTER A FEW SECONDS. I've flashed the stock RUU several times now with the same results. It's as if this phone can't flash anything although it acts as if it flashes successfully.
Anybody have any experience with this? Any suggestions are appreciated.
Sounds like emmc is fried. Send it in for repair.
joshw0000 said:
Hey guys, I sold my One M8 to my little brother's friend a few months ago. It's Unlocked, S=Off, and SuperCID with the following:
HBOOT = 3.16.0.0000
RADIO = 0.56.20.0321
OpenDSP - V38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
TWRP V2.7.0.2
Since he's had it, he says he's only flashed Liquidsmooth, MIUI, and the stock rom. He swears the phone was running great for the past month or so on the stock rom. According to him, he hasn't flashed anything in at least a month. Last night, he plugged it up like usualand woke up to the phone completely powered off. When he booted it, it boots normally and soon after unlocking it, it reboots. This has been the case since I received it back from him (to fix). It's stuck in a bootloop that I cannot fix. Shortly after booting the rom (stock), it will reboot.
What I've tried:
Flashing a new rom in TWRP.
Wiping everything in TWRP (including system w/ and w/o the system partition mounted)
Fixing permissions in TWRP
Flashing SuperSu in TWRP (don't ask why, Googled it and someone said it fixed theirs)
All of this just continues to reboot to the same stock rom that it was already on. Shortly after booting, it would reboot as if I'd made no changes, wipes, etc.
So I figured I'd update TWRP. I downloaded TWRP_Recovery_2.8.2.1_M8_CPTB.img and flashed it in fastboot (without using fastboot oem rebootRUU) It was successful (or so it seemed). When I reboot recovery it still shows 2.7.0.2. So I downloaded ruuM8_TWRP_2_7.zip, tried to flash it from fastboot but when I "Fastboot oem rebootRUU" it jumps back to the bootloop so I put it on the ext_sdcard and renamed it to 0P6BIMG.zip. Hboot flashed it successfully but still the version didn't change.
So after all has failed, let's flash the stock RUU......So I grabbed this RUU - http://forum.xda-developers.com/showthread.php?t=2727831, renamed it to 0P6BIMG.zip and put in on the external sdcard (remember fastboot just kicks me into a bootloop when I fastboot oem rebootRUU). Using the sd card method, It took forever to flash the system partition, extracting and installing about a half dozen times. Eventually everything passed and it prompted me to press power up to reboot. AND IT BOOTS BACK TO THE SAME LOCK SCREEN.....AND REBOOTS AFTER A FEW SECONDS. I've flashed the stock RUU several times now with the same results. It's as if this phone can't flash anything although it acts as if it flashes successfully.
Anybody have any experience with this? Any suggestions are appreciated.
Click to expand...
Click to collapse
Had one of these where the radio died. Did the same exact thing. Kmsg revealed an attempt to start the radio and the subsequent failure. I got it back to locked (not relocked) and s-on and opted for a replacement from HTC.
I can't relock it. I can't even overwrite TWRP.
joshw0000 said:
I can't relock it. I can't even overwrite TWRP.
Click to expand...
Click to collapse
Like I said earlier, its broken. Get it fixed if you can.