Hi,
I have become really stuck with this issue
ROM - 2.29.405.2
I origonally had a rooted phone with clockworkmod installed. I subsequently wanted to put it back to stock. Which i ran the latest RUU with the goldcard. I now am getting a continuous white HTC screen then vibrates and keeps doing this. No matter what i do i cannot get the phone into the recovery menu it just starts the reboot loop again.
I can get on fastboot and resend the same RUU to the phone. This installs without any issue and says that it is going to reboot the phone and going straight back to the rebooting loop.
I somehow need to get clockworkmod reinstalled so i can resolve this problem as it seems that the recovery partition is damaged somehow. I have s=on so i cannot force the restore of the recovery console with the colckworkmod as i get signature failure.
Is there an origional HTC recovery file i can use which gets past the signature failure??
"Clear storage" from HBOOT.
And give a try to the other way - download this zip , rename it "PB99IMG.zip" put it in the root of your SD card (not in a folder) , pull battery , plug it back , enter HBOOT (power+volume down) and apply it.
Edit: use goldcard if you are branded. If I understand you correctly, you say this "I subsequently wanted to put it back to stock. Which i ran the latest RUU with the goldcard" - if you flashed your original stock ROM, then you didn't need a gold card.
Branded
Yes i am branded.
Sure i tried this last time where it showed a blue meter on the right hand side. Went all the way and rebooted to the same if i rememeber.
But i will give it another go see if it works. Cheers.
I managed to get it to run the PB99IMG in the end which updated all parts without an issue. On rebooting of the phone it still does it boot loop.
I really done know what is causing this.
Okay, so I'm trying to root my boss' phone: I did warn him that things could go awry but we went ahead and tried anyway. I'm using adb commands from a mac. I downloaded CWM toro (for gnex) and the lastest su.zip file. I unlocked the bootloader, flashed CWM, and was able to push su.zip over to the /sdcard through the command line (it reads 3985 KB/s and how long it took, etc.) - Now still in CWM, I can't seem to access the sdcard. I'm getting a "Couldn't open diretory." which shows up twice, followed by a "no files found" error. But the terminal window shows that the file was pushed over. Rebooting goes into a loop halfway through the splashscreen. Still have access to CWM and able to enter fastboot mode through holding VOL UP and VOL DOWN while powering. Any help would be appreciated!
EDIT: Tried Wiping Cache, reboot to recovery - still no luck. Tried Wiping Dalvik Cache, reboot to recovery - still no luck.
EDIT: Tried downloading appropriate recovery images from Google's website. Flashed files in order from http://forum.xda-developers.com/showthread.php?p=20441992 <--these instructions, everything checked out okay and still looping at boot.
I hope this is reversible. Seriously, anyone? Any help is appreciated.
Didn't think it would go like this as I rooted my GNex with ease (GSM version) using the same method.
Reflash cwm
+1 for reflashing CWM
Your FIRED!
I attempted to force my phone to update to 4.1 as it was stuck at 4.01 which irritated me endlessly.
I now am stuck, I can get to the fast boot menu or I can get to the clockworkmod recovery menu. the phone auto boots to the clockwork menu
I followed this guide to get where I am
http://forum.xda-developers.com/showpost.php?p=28178320&postcount=2
When I try to install zip from sdcard in clockwork recovery The boot loader installs fine (cwm-bootloader-lc03.zip) and the radio installs fine (cwm-radio-i9250-xxlfl.zip) but my image jb-takju.zip fails half way with a bad image error.
I belive that I need to put a new image on my phone but without a physical sd card I need a way to push files to the phone.
I have tried adb but it can not see my phone, even though it still shows up in windows device manager as samsung adb device.
so ether I do not know how to use adb (adb push \path\recovery.img \sdcard\recovery,img = error:device not found) or it does not work.
Is there another way to get files on the phone?
as a side note I am currently downloading the factory image for 4.04 and hope to find a way to reflash the phone with that
(https://dl.google.com/dl/android/aosp/yakju-imm76i-factory-8001e72f.tgz)
I will take any help I can get, thanks
fixed it
I fixed it by restoring the factory image, http://forum.xda-developers.com/showthread.php?t=1366806 this link used a program fast-boot that let me write the 4.04 image
Hi guys I have a mytouch 3G slide and I was able to get the bootloader unlocked. However even before I unlocked the bootloader I was unable to get the phone to work it would stay at the mytouch slide splash screen. Im on the new hboot and a am able to get into fastboot and hboot. However when I click recovery in hboot it takes me to the tmobile slash screen and never gets into recovery. I have flashed the original recovery but still no luck. I can't reboot the phone all they way. Anyone know what's wrong?
Sent from my MB611 using Tapatalk 2
Anyone have a solution
Sent from my MB611 using Tapatalk 2
Hey Moe92,
I'm pretty much in the same situation as you!
I was given a phone to fix that has water damage, the owner disclosed that up front and I can see this based on the moisture sensor on the device.
The phone boots up and is stuck on the splash screen with out any activity after this. This is the same screen that I see when trying to enter recovery.
The only thing the phone can do is go into fastboot and hboot. Let me make a list of all the activities I have tried to perform and what ended up happening. As of now I still cannot fix the phone.
Device Details in Hboot
Code:
ESPRESSO PVT SHIP S-ON
HBOOT-1.02.0002
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.15.35.16
Dec 13 2001,11:34:01
The items I've performed so far are:
* Downloaded two different versions of ESPRIMG.zip and placed them on the SDCARD for the device. Neither loads up by the device and they both fail.
The MD5 hash for each version is: 892b885010563208edc3037dfec40425 and 9e80d53b4afa73ecf0d58f703831ac82
* Created a goldcard and tried to run the above two files with the same result.
* Tried to enter recovery from the device; ends up on the boot splash screen and hangs
* Tried to use fastboot to flash several recovery images: Clockwork 2.5.0.7, recovery-RA-Saphire-v1.7.0, recovery.img from the ESPRIMG.zip files
* Each time fastboot flashes the recovery sucessfully, but trying to get to it ends up with a boot splash screen hang.
I'm starting to believe the phone is bricked, or something occurred internally when it became wet. I have no idea what the software was on it prior to it being wet.
From your experience does this phone have any luck of being restored? I've spent two days looking over the threads and trying to avoid asking a question that may be answered; but have had no success.
Any help would be greatly appreciated.
dustbyter said:
Hey Moe92,
I'm pretty much in the same situation as you!
I was given a phone to fix that has water damage, the owner disclosed that up front and I can see this based on the moisture sensor on the device.
The phone boots up and is stuck on the splash screen with out any activity after this. This is the same screen that I see when trying to enter recovery.
The only thing the phone can do is go into fastboot and hboot. Let me make a list of all the activities I have tried to perform and what ended up happening. As of now I still cannot fix the phone.
Device Details in Hboot
Code:
ESPRESSO PVT SHIP S-ON
HBOOT-1.02.0002
MICROP-0620
TOUCH PANEL-SYNT0102
RADIO-7.15.35.16
Dec 13 2001,11:34:01
The items I've performed so far are:
* Downloaded two different versions of ESPRIMG.zip and placed them on the SDCARD for the device. Neither loads up by the device and they both fail.
The MD5 hash for each version is: 892b885010563208edc3037dfec40425 and 9e80d53b4afa73ecf0d58f703831ac82
* Created a goldcard and tried to run the above two files with the same result.
* Tried to enter recovery from the device; ends up on the boot splash screen and hangs
* Tried to use fastboot to flash several recovery images: Clockwork 2.5.0.7, recovery-RA-Saphire-v1.7.0, recovery.img from the ESPRIMG.zip files
* Each time fastboot flashes the recovery sucessfully, but trying to get to it ends up with a boot splash screen hang.
I'm starting to believe the phone is bricked, or something occurred internally when it became wet. I have no idea what the software was on it prior to it being wet.
From your experience does this phone have any luck of being restored? I've spent two days looking over the threads and trying to avoid asking a question that may be answered; but have had no success.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Actually sometimes and this rarely happens... I can load into the welcome screen but everythine that happens, the phone is in safe mode. When I power down the phone it goes back to the splash screen and hangs there. I have to keep flashing the Tom many many time and pray that it gets into the welcome screen again.
BTW I can unlock the bootloader. Does anyone know what I can do after I unlock the boot loader?. I tried to flash zips via fadtboot but got the error where it cannot determine the signature. When unlocking the hboot, are there specific things I can do via fastboot? Please let me know. Thanks
I have also unlocked the bootloader by using the token provided by htcdev.
What zip did you try to flash to yours? I haven't tried that from fastboot yet. I only tried to flash each component of the ESPRIMG using fastboot with out any luck.
Moe,
Do you have any information on how to boot the device into safe mode?
I tried to use fastboot to flash an update.zip but that method did not work either :crying:
Does anyone have access to the ESPDIAG.zip for this device?
Ran out of ideas at this point .
dustbyter said:
I have also unlocked the bootloader by using the token provided by htcdev.
What zip did you try to flash to yours? I haven't tried that from fastboot yet. I only tried to flash each component of the ESPRIMG using fastboot with out any luck.
Click to expand...
Click to collapse
well when i unlocked the bootloader. i then decided to relock it. once i relocked it. i went to the HTC website and got the 2.2.1 RUU. once the RUU downloaded, i reloaded the phone with the firmware and once it was done, it booted o the entire OS but it was in safe mode. i didnt press any buttons for it to get into safe mode. it went in by itself...
also when i shut the phone off and truend it back on, i was back in square one where i was stuck in the boot loader screen.
Also you can extract the original ESPRIMG.zip file from the offical 2.2.1 ruu. In order to extract the .zip file, you first have to run the RUU. Once you click on the Downloaded RUU program, let it run. once the first page of the RUU comes up, follwo the below directions to extract the .zip file. DO NOT flash the phone with RUU if you want to extract the .zip file.
Here are the step by step instructions
1. open my computer
2. click on the main drive. (for me it was the C: drive)
3. click on users
4. click on you computer name (the one that has the lock on it)
5. click Appdata. (appdata is a hidden folder. to un-hide it, click---> Organize/Folder and search options/view/ scroll down to hidden files and folders/ click on show all files and folders)
6. click on Local (NOT Locallow or Roaming)
7. click on Temp
8. when you get into the folder, sort the files to the DATE MODIFIED
9. when you have it sorted, you will see some folders such as ({95153F7E-B880-4656-B55D-54DD7869F984}), the name of the folders can and will be different. open each folder and when you come across a folder that has the ADB application, scroll down the folder until you reach the LETTER "R". you will then see a .zip file named "rom". copy that file onto the desktop or any other folder. rename it to ESPRIMG.ZIP.
10. format your SD CARD to FAT32. once the format is complete, copy/move the extracted rom/ESPRIMG.zip file into the sd card.
11. put SD card in the phone.
12. Hboot should then detect the esprimg file.
google for mt3srooter
---------- Post added at 06:11 AM ---------- Previous post was at 06:03 AM ----------
open folder u would find esprimg dat de file mt3gs
Thanks! I'll check this out. Unfortunately I returned the phone to its owner, I'll have to get it back to see if I can resolve his issue.
Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.
That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.
Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?
double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...
I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?
double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.
double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe
Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.