[Q] Help with semi brick endless reboot - Verizon Droid Incredible 2

Here's my info:
Android version: 2.3.4
S-ON
Kernel: 2.6.35.9-gb5330gc
Radio: 1.09.01-1111
hboot: 0.98
I tried to root my DINC2 using the directions here: http://forum.xda-developers.com/showthread.php?t=1751796. In TACOROOT, I got stuck on the step that said it was going to take a long time (fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip). After an hour of it not doing anything (and needing to catch a flight) I unplugged and ran out the door. Later the phone booted up fine and seemed to act like it was going to work and let me start over.
So I start over at the beginning and go through the list of instructions for TACOROOT. When I get to that same step again the command prompt says waiting for the phone, the phone reboots... gets through the loading screens... I unlock the screen and it says "loading..." like it does when you first turn it on. Then, right after the SD card is loaded, right as the sense widgets load, it turns off and starts again.
This loops continuously for a very long time and the step never finishes. Now that seems to be all it does.
I've tried restoring stock everything via hboot, clearing the cache, factory reset. Each time, I can activate the phone and it lives, but as soon as I reboot once it's stuck in the loop again.
In truth, I'd be happy just to get it usable again. Any help is appreciated!

I'd really love to give this phone as a present, but it looks like it'll have to wait until after I'm able to get it up and running again. Any help at all is appreciated!
Thank you in advance and Merry Christmas!

Bump? I'm still stuck and not sure what else to try. Do you need more information?

You're still s-on?
Sent from PAC-nation

Rushead said:
You're still s-on?
Sent from PAC-nation
Click to expand...
Click to collapse
yes, still s-on

unrealnighthawk said:
yes, still s-on
Click to expand...
Click to collapse
Check the md5 sum for all the files included in that zip. Any discrepancies, redownload and check again.
Also, did you remove the space in the word "Radio" in the RUU?

Rushead said:
Check the md5 sum for all the files included in that zip. Any discrepancies, redownload and check again.
Also, did you remove the space in the word "Radio" in the RUU?
Click to expand...
Click to collapse
I've went through this process a few different times (checking the md5 checksum each time), but iI can try again. I was sure to fix that radio space too.
I'm virtualizing windows on my mac via virtualBox. would that make a difference? I've also tried it on a Windows computer I borrowed, it's just harder to get ahold of. Is there a decent osx solution? I wasn't able to find one that worked any better. I could also burn a Linux boot disk if that would work better.
Thank you!

Windows user here. Not sure about a mac, but probably that's where the issue is. Try a Linux boot & see if that works.
Sent from my Incredible 2 using xda app-developers app

Progress!... ?
Okay, so I think I've been able to make some progress. When I got home on my PC I was able to follow the instructions again and actually get past the step that had taken so long before (the don't forget to fix 'radio' in fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip step). It didn't take quite so long this time and finished successfully, so woot!
So I continued on and got to the next 'long' step: fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip. I get the error message "FAILED (remote: 12 signature verify fail)". I re-ran the MP5 checksum and it matches. To verify, the prompts for the last two commands are below.
Code:
C:\Android>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\Android\]
1.09.01.0312_vivow_Radio_PG32IMG.zip ea6b98be48210d7797e62362f49ff751
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.262s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.529s
I'm worried now that one of the other solutions for restoring the phone to stock or rooting in a different manner changed something else. What debugging can I do to troubleshoot this? Is there an alternative file I should download to flash for the radio?
Thanks again!

I don't know if this is helpful, but here's what it shows on my phone
Code:
VIVO_W XB SHIP S-ON RL
HBOOT-0.97.0000
RADIO-1.09.01.0622
eMMC-BOOT
Apr 13 2011, 21:20:09

Try flashing the radio in hboot. Did you run revolutionary? The radio can always be flashed l8r.
Sent from my Incredible 2 using xda app-developers app

Rushead said:
Try flashing the radio in hboot. Did you run revolutionary? The radio can always be flashed l8r.
Click to expand...
Click to collapse
How do I get into hboot? I'll try revolutionary and see if that works. Thanks!

unrealnighthawk said:
How do I get into hboot? I'll try revolutionary and see if that works. Thanks!
Click to expand...
Click to collapse
Make sure fast boot is disabled under settings -> power and then reboot phone. When the capacitive lights go out hold volume down. Or you could turn off phone and then power up holding the volume down button.

Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root? I tried to uninstall one of the lame stock apps, but there wasn't an uninstall option. Is there a better way to check, or does that not come until I flash another rom?
Thanks again, espectially to Rushead! I couldn't have done it without you!

unrealnighthawk said:
Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root? I tried to uninstall one of the lame stock apps, but there wasn't an uninstall option. Is there a better way to check, or does that not come until I flash another rom?
Thanks again, espectially to Rushead! I couldn't have done it without you!
Click to expand...
Click to collapse
No worries! Do you have superuser installed? If not, you need to push it via adb. The file should be available in the download package you downloaded initially.
Sent from my Incredible 2 using xda app-developers app

unrealnighthawk said:
Hey, I think it worked! Revolutionary was successful, then went back through and flashed the radio. Now it boots up, no problem. I can confirm s-off from fastboot, but how can I confirm root?
Click to expand...
Click to collapse
I'm having the same 12 signature verify fail problem.
Just to clarify: Despite the failure to flash the radio, you continued on to run revolutionary, then went back to flash the radio afterwards? Just want to make sure that I can duplicate your workaround in my case
Thanks!

jncryer said:
I'm having the same 12 signature verify fail problem.
Just to clarify: Despite the failure to flash the radio, you continued on to run revolutionary, then went back to flash the radio afterwards? Just want to make sure that I can duplicate your workaround in my case
Thanks!
Click to expand...
Click to collapse
Yup. It failed on my first go, but I continued. Later I was able to go back and flash the radio. It worked that time. Good luck!

Phone boots after flash but stuck in reboot afterwards
hey guys i need a little help with my Di2. Ive had it rooted for the past almost year ive been flashing roms and whatnot i have basic common knowledge of what im doing with the phone however i seen the ics 4.0.4 rom that was released for the incredible 2 and after flashing that i then decided to flash back the stock gingerbread ruu i did this via the bootloader not recovery and now my phone will boot up perfectly the first time i flashed the file (PG32IMG) but when i reboot the phone it will load all the way up and turn on about long enough for me to pull down the lock screen slider and bam cuts off doing the exact same thing from then on out.. I am able to get to the bootloader screen however with all the latest attempts of wiping the data and and cache and whatnot i still have this exact same outcome i would really appreciate some help guys it would be much appreciated ive looked on the internet and in these forums and cant find any thing that quite helps yet ive downloaded so many PG32IMG files and tried to flash them via bootloader it is not even funny >.>... aha anyways thank you guys id like to turn this brick i had for the last few days back into the phone i love i dont even care if its rooted anymore i just want the thing working.. aha ive replaced the screen charging port and bought plenty of accessories id hate to see all that money down the drain. Thanks guys. Any replys are appreciated.

Have you tried flashing back to one of the older radios ? The ICS firmware maby boot looping your phone
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2

Are you s-off?
Sent from my ADR6350 using xda app-developers app

Related

Possible brick. Bootloader access but no recovery. Any suggestions?

EDIT: Check post 10 for an update on progress after running the stock RUU
Been reading XDA for awhile, first time posting. I'll try to put as much information on here as possible so please excuse the long drawn out post.
Have been running MIUI 11.16 release on Evo 4g until two days ago. My evo began bootlooping in my pocket, which happens sometimes but usually on the splash screen. This is usually fixed by a battery pull and a ROM reflash in Clockwork Recover. However, on this occasion my phone has been bootlooping on the HTC screen. I booted into bootloader and attempted to then boot into recovery but the loop continued.
I have the original PC361.zip still on my SD card so decided to run the update and see if that would reset things. The update was successful and I attempted to boot recovery . The HTC screen flashes and proceeds to a black screen with 5 vibrates and a blinking LED. This now happens every time I turn on the phone with booting into the bootloader.
I attempted (perhaps incorrectly) to flash clockwork recovery through Fastboot USB through my Mac Terminal, but have been unable to do so as it won't allow a remote flash.
./fastboot flash /recovery /Users/****/Desktop/android-sdk-mac_x86/tools/recovery-clockwork-1.8.1.7-supersonic.zip
sending '/recovery' (808 KB)... OKAY
writing '/recovery'... FAILED (remote: not allowed)
So, to recap. Normal boot results in 5 vibrates and a green LED flash that is only reset by a battery pull. Fastboot access is available, but perhaps not usable by remote access. No access to recovery. Cannot mount SD card onto my Mac (not sure if that's a given). Top of bootloader screen says the following:
Supersonic EVT2- 3 ship s-off
HBOOT-0.79.0000
MicroP-041f
Touch Panel-ATMEL224_16ab
Radio-1.39.00.04.26
April 14 2010, 15:41:34
I've done a lot of forum hopping and reading and it seems like this is the most relevant information for trying to fix this problem. At this point, my only real goal is to make a phone call or two so I'm not worried about keeping my root since that can be fixed later. Any suggestions would be much appreciated and I can furnish any information you might need.
Thanks
Have you tried flashing a stock ROM RUU updater from www.shipped-roms.com?
This may not get you into your rooted state with your custom rom, but should at least get you into a usable state.
You should still be rooted afterwards, but will need to run UNREVOKED FOREVER, to get your clockwork recovery back.
Just downloaded an executable RUU filed from Shipped ROM's. I'll go find a Windows system and give it a shot. I'll update in a bit.
I think the .exe is finding the android device, but doesn't do anything after update is hit. Is there a way to connect my phone to the computer to run this .exe through bootloader?
agrim0091 said:
I think the .exe is finding the android device, but doesn't do anything after update is hit. Is there a way to connect my phone to the computer to run this .exe through bootloader?
Click to expand...
Click to collapse
Select hboot usb and make sure the drivers install (probably windows only, sorry) then run the ruu. I think the needed drivers are included with the htc sync software (windows only as well I believe)
DomSim said:
Select hboot usb and make sure the drivers install (probably windows only, sorry) then run the ruu. I think the needed drivers are included with the htc sync software (windows only as well I believe)
Click to expand...
Click to collapse
Just tried with hboot usb plug hooked up and it didn't recognise. I'll try to install HTC Sync and give it another shot. Thank you guys for the help so far.
The RUU successfully installed and booting the phone no longer causes the 5 vibrations and the green LED. The phone is still bootlooping at the HTC screen going to a black screen and then rebooting.
This is the first breakthrough I've made in days. Any ideas on where I should go from here?
I would think maybe flash radio, then they to flash recovery. Maybe wait until someoe else chimes in though
DomSim said:
I would think maybe flash radio, then they to flash recovery. Maybe wait until someoe else chimes in though
Click to expand...
Click to collapse
I tried to flash recovery through Fastboot and my Mac terminal, but I'm still being denied remote access.
A quick update on the situation to try to consolidate any progress so far...
I successfully flashed the stock RUU which should have returned everything back to stock. I'm still stuck in a bootloop from the HTC screen to black screen but no longer have the 5 vibrates and the flashing green LED.
My Bootloader heading is as thus...
Supersonic EV2-3 Ship S-off
hboot- 0.93.0000
microp-014f
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010, 16:41:47
Booting into recovery from Bootloader still causes the boot cycle meaning that the RUU didn't fix everything. Also, S-OFF still seems to mean that the root appears to be in place (maybe?) so no luck of returning it to sprint. Still cannot remote flash from the command prompt in windows.
I'm not sure what to do next. If I had to wager a guess it would have something to do with the PC36img.zip file, even though I'm not totally sure what this means or which one I should attempt to load. If this is the case, I can go buy an SD card reader today and attempt to load another up if anyone can suggest one.
Again, thanks for all of the help.
agrim0091 said:
A quick update on the situation to try to consolidate any progress so far...
I successfully flashed the stock RUU which should have returned everything back to stock. I'm still stuck in a bootloop from the HTC screen to black screen but no longer have the 5 vibrates and the flashing green LED.
My Bootloader heading is as thus...
Supersonic EV2-3 Ship S-off
hboot- 0.93.0000
microp-014f
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010, 16:41:47
Booting into recovery from Bootloader still causes the boot cycle meaning that the RUU didn't fix everything. Also, S-OFF still seems to mean that the root appears to be in place (maybe?) so no luck of returning it to sprint. Still cannot remote flash from the command prompt in windows.
I'm not sure what to do next. If I had to wager a guess it would have something to do with the PC36img.zip file, even though I'm not totally sure what this means or which one I should attempt to load. If this is the case, I can go buy an SD card reader today and attempt to load another up if anyone can suggest one.
Again, thanks for all of the help.
Click to expand...
Click to collapse
did you try to unroot don't know if you used unrevoked but if you did try to flash the s-on tool and then flash the 3.29 ruu that should put you back up to stock and load good but if it doesn't then you may have a corrupted nand. Don't take my word for it cause i know computers more than these phones i know enough to get me by thats about it but if they are anything like computers i would venture that as the problem
Jbcarrera said:
did you try to unroot don't know if you used unrevoked but if you did try to flash the s-on tool and then flash the 3.29 ruu that should put you back up to stock and load good but if it doesn't then you may have a corrupted nand. Don't take my word for it cause i know computers more than these phones i know enough to get me by thats about it but if they are anything like computers i would venture that as the problem
Click to expand...
Click to collapse
Any idea how to flash this through Fastboot or the Bootloader?
agrim0091 said:
Any idea how to flash this through Fastboot or the Bootloader?
Click to expand...
Click to collapse
adb but i'm trying to find out how for you
Jbcarrera said:
adb but i'm trying to find out how for you
Click to expand...
Click to collapse
Just realized my old BlackBerry has microSD support. So I can load something onto my Evo SD card via that quite easily if you think a certain PC36img.zip file would work. I just have no idea what those PC36img.zip files are or do. :/
Jbcarrera said:
adb but i'm trying to find out how for you
Click to expand...
Click to collapse
Just found a PC36img.zip file for clockwork recover. Update was "Successful" but the Boot cycle continues.
Is this the pc36img you tried? If not try it.
http://forum.xda-developers.com/showthread.php?t=780141
Try hboot usb and start adb type push unrevokeds-on.zip that should give you s-on then run the 3.29 Thu that should work
sent from my EVO at the edge of hell
No internet access last night at the apartment for some reason :/. I'll try flashing the PC36img.zip and if that doesnt work i'll try to adb push the s-on file and get it back to total stock to bring it back to sprint.
Thinking about it though, I'm not sure if I had adb access from hboot. I'll update you guys soon.
DomSim said:
Is this the pc36img you tried? If not try it.
http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
Flashed this PC36IMG.zip. Update was successful but the phone is still looping.
Jbcarrera said:
Try hboot usb and start adb type push unrevokeds-on.zip that should give you s-on then run the 3.29 Thu that should work
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I can't get adb to recognize my device with hboot usb plug showing. I tried adb devices and nothing will pop up.
I'm having this same exact issue you did. Did you ever end up finding a solution?

[Q] Crap - I'm stuck.... (urgent help needed)

Ok, I can't figure this out, despite researching across a bunch of threads.
I've been trying to root my fiancee's Evo for almost 2 hours now to no avail.
First I tried the "autoroot" method, but it failed. Then I tried the unrEVOked method, and it kept getting hung up on "installing unrevoked service...".
Somehow, after getting through bootloader, et. al. a few times, I got to the screen with triangles\exclamations in each corner. I got out of that by running an RUU. Well, that apparently wasn't right, because then I could not get any of the Root methods to work.
I downloaded an older version - EvoRoot - and tried it. Seemed to be working....until it went to flash recovery, and now I'm stuck going between the Bootloader screen and the red triangle-exclamation.
I can't, for the life of me, figure out how I can get out of this mess.
The Evo has never been rooted and it's only a few weeks old. It was originally on this:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
And is definitely Android 2.2.
I think I accidentally ran this:
RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444_signed
to get myself out of the 4 exclamation point screen.
Can anyone help me at all?
Well the red triangle with an exclamation means you are going into recovery. but no recovery is installed. Boot into the rom use/download rom manager, and flash clockworkmod recovery. That should do it.
teh roxxorz said:
Well the red triangle with an exclamation means you are going into recovery. but no recovery is installed. Boot into the rom use/download rom manager, and flash clockworkmod recovery. That should do it.
Click to expand...
Click to collapse
I can do one of a few things:
V-Up + Power = 4 options. I can't "update.zip" because it says "no such file or directory". Wiping does nothing, just returns me to red ! screen.
Get to Bootloader - nothing I do there does anything but take me to red ! screen.
bhamhawker said:
I can do one of a few things:
V-Up + Power = 4 options. I can't "update.zip" because it says "no such file or directory". Wiping does nothing, just returns me to red ! screen.
Get to Bootloader - nothing I do there does anything but take me to red ! screen.
Click to expand...
Click to collapse
No, don't boot into the bootloader, just start the phone up normally; or can you not do that?
teh roxxorz said:
No, don't boot into the bootloader, just start the phone up normally; or can you not do that?
Click to expand...
Click to collapse
Rebooting the phone normally just brings me straight to the red ! screen after showing me the htc EVO 4G white intro screen.
I'm attaching amon_ra recovery [I run clockwork, but this works just as well]
Take the battery off, and mount your sd card to your computer via adapter, put that file on the root of the sd card, do not modify or extract it. Once done, start the phone up and boot into the bootloader, it should ask you if you want to update, and say yes.
Ok, downloaded, added to card. Upon booting into bootloaded, it reads the .zip and then just kicks me back to the bootloader. It won't ask if I want to update at all.
Also, I can give some more info on the phone real quick:
Supersonic EVT2-3 Ship S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
Radio-2.15.00.07.28
Oct 15 2010, 12:07:00
I can jump on a number of chat accounts if anyone would rather walk me through it in that fashion.
Well you're S-ON...no bueno. Try running unrevoked3 again. But before you do, do you have the Hboot drivers installed?
teh roxxorz said:
Well you're S-ON...no bueno. Try running unrevoked3 again. But before you do, do you have the Hboot drivers installed?
Click to expand...
Click to collapse
Yep, HBoot was installed fine.
Is there some way to factory reset using my SDCard to mount images?
bhamhawker said:
Yep, HBoot was installed fine.
Is there some way to factory reset using my SDCard to mount images?
Click to expand...
Click to collapse
The only real way is to run the RUU.
Try running the 3rd option.
http://www.shipped-roms.com/shipped/Supersonic/ Let me know what happens.
Ok, downloading a stock rom and going to rename it to update.zip. Hopefully I can get that to work through the Android recovery.
I haven't heard that method, but I'll be around so I'll check back in, in a couple.
Ok, the "update.zip" file opens, but then says "Signature Verification Failed".
How do I run the RUU? While the device has the red ! screen?
You need a factory reset PCIMG36.zip of the RUU I believe.
Sent from my PC36100 using XDA App
bhamhawker said:
Ok, the "update.zip" file opens, but then says "Signature Verification Failed".
How do I run the RUU? While the device has the red ! screen?
Click to expand...
Click to collapse
In the recovery, where it says install from zip, scroll down to signature verification, and select it to toggle it off, so it doesn't check and it should run.
Boot into the bootloader, and select fastboot, then run the RUU exe.
teh roxxorz said:
In the recovery, where it says install from zip, scroll down to signature verification, and select it to toggle it off, so it doesn't check and it should run.
Boot into the bootloader, and select fastboot, then run the RUU exe.
Click to expand...
Click to collapse
Neither of these worked. However, with my screen just at the HTC Evo "white" screen, I was getting the error "Your battery is under 30%" when I ran the RUU*.exe file on my comp. I switched to a different battery (with an unknown charge) and tried, but got the same. Have one of the batteries charging right now, so maybe that will change my luck??
I'm downloading the stock RUU PC36IMG right now (I think), too.
It is a very bad idea to try different root methods one right after another and to randomly flash stuff unless you are purposely trying to brick your phone. The bootloader stopped you from doing just that when it locked you in the black htc screen but if you would have had your nand unlocked you may not have been so lucky.
If you flash the 3.70 RUU so that you have a clean start you should be able to root fine. There's no telling if you will still have 4G or if anything has became permanently corrupted though. Just run it as a normal exe, do not use it as an PC36IMG.
Ok, Holy Mary Mother of Tebow, but I'm finally out of the pseudo-brick state.
Thanks a ton for your help on this. I really, really appreciate it.
I now am setup with the following:
Android 2.2
Baseband 2.15.00.07.28
Kernel 2.6.32.15-g746f4f0 [email protected] #58
Build 3.26.651.6
Can anyone help me successfully root this phone now?
bhamhawker said:
Ok, Holy Mary Mother of Tebow, but I'm finally out of the pseudo-brick state.
Thanks a ton for your help on this. I really, really appreciate it.
I now am setup with the following:
Android 2.2
Baseband 2.15.00.07.28
Kernel 2.6.32.15-g746f4f0 [email protected] #58
Build 3.26.651.6
Can anyone help me successfully root this phone now?
Click to expand...
Click to collapse
Okay good. Now run unrevoked3. Once it starts, just put the phone down and let it run. Should reboot 2 times, let it run the full course.
teh roxxorz said:
Okay good. Now run unrevoked3. Once it starts, just put the phone down and let it run. Should reboot 2 times, let it run the full course.
Click to expand...
Click to collapse
How long should the program be hung up on "Installing unrevoked service"?

[Q] Bootloop of Death...

Remember the group of people sometime last year who got into infinite bootloops, with access to bootloader but no recovery?
Yeah. That's me right now. Problem is, I can't remember if we ever found a solution, if anything would work. So I come before y'all for any help
Was running latest CM build before with Tiamat 4.1.0, just shut off during Google Navigation while charging and entered infinite bootloop.
004 Evo
2.18.0001 HBOOT S-OFF
Newest radio, Wimax, PRI, NV
Amon Ra (No access)
It does charge (or says it does - light is on)
So yeah. Access to HBOOT, no access to recovery, still have S-Off. Any help appreciated
tropicalbrit said:
Remember the group of people sometime last year who got into infinite bootloops, with access to bootloader but no recovery?
Yeah. That's me right now. Problem is, I can't remember if we ever found a solution, if anything would work. So I come before y'all for any help
Was running latest CM build before with Tiamat 4.1.0, just shut off during Google Navigation while charging and entered infinite bootloop.
004 Evo
2.18.0001 HBOOT S-OFF
Newest radio, Wimax, PRI, NV
Amon Ra (No access)
It does charge (or says it does - light is on)
So yeah. Access to HBOOT, no access to recovery, still have S-Off. Any help appreciated
Click to expand...
Click to collapse
have you attempted to reflash recovery?
Had this happen the other day and pulled battery and then held power button and volume button down and it went right into Recovery... 1st time ever for me
Just reflashed recovery. Still nothing. Goes into bootloop as I enter recovery.
Note: It does not show boot animation, only splash screen. Just clarifying
Give it some time some times after a crash/hotstart takes a little longer..
Sent from my EVO using XDA App
tropicalbrit said:
Just reflashed recovery. Still nothing. Goes into bootloop as I enter recovery.
Note: It does not show boot animation, only splash screen. Just clarifying
Click to expand...
Click to collapse
Tried a ruu yet?
Sent from my PC36100 using XDA App
evo4gnoob said:
Tried a ruu yet?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just did. 2.16.0001 HBOOT S-OFF with 2.15.00.0808 radio.
No access to recovery (HTC or custom after flashing recovery)
Same bootloop.
tropicalbrit said:
Just did. 2.16.0001 HBOOT S-OFF with 2.15.00.0808 radio.
No access to recovery (HTC or custom after flashing recovery)
Same bootloop.
Click to expand...
Click to collapse
might need to wait till Captian_Throwback gets online he'll probably know a way to fix it. He fixed his when he got bricked by TWRP
No, there never was a solution, other than the doc I attached, which may not work and again.. someone running CM get's this Boot Loop issue....
evo4gnoob said:
might need to wait till Captian_Throwback gets online he'll probably know a way to fix it. He fixed his when he got bricked by TWRP
Click to expand...
Click to collapse
Nice of you to think of me!
Umm, yeah . . . my problem was a little bit different, as I was still able to boot into a ROM. So, any suggestions I offer here will be purely theoretical. But, perhaps the same fix will apply. Maybe the misc partition needs to be "reset"? Since you have access to fastboot, we'll need you to flash a bootloader version where fastboot commands will work. Since you have a hardware 0004, I think 2.18 is the only option. Get that from here: PC36IMG_HBOOT_2.18.0001.zip (flashable via bootloader). You'll also need to download the "mtd-eng.img" file from toast's thread here: mtd.eng.zip, and you'll need the fastboot.exe from the Android SDK.
After you get the 2.18 HBOOT flashed, select fastboot to get into FASTBOOT USB mode. I assume you already have the fastboot drivers installed on your computer, so I won't get into detail on that.
Put the mtd-eng.img in the folder with fastboot and open a command prompt. Navigate to that folder and issue the commandEDIT: I just tried this and it didn't work. I think you're going to have to go with the above method . It was a good ol' college try, I guess.
Code:
fastboot flash misc mtd-eng.img
It should flash successfully, since you're S-OFF. Once that's done, try rebooting the bootloader, and see if you can get into recovery.
The mtd partition seems to be the thing that messes everything up, so I figure that's the best place to start and see if it's that easy to fix .
EDIT: I guess if the above doesn't work, HipKat's method will be the next thing to try. I don't envy you if you have to try that . . .
Captain_Throwback said:
Since you have a hardware 0004, I think 2.18 is the only option. Get that from here: PC36IMG_HBOOT_2.18.0001.zip (flashable via bootloader). You'll also need to download the "mtd-eng.img" file from toast's thread here: mtd.eng.zip, and you'll need the fastboot.exe from the Android SDK.
After you get the 2.18 HBOOT flashed, select fastboot to get into FASTBOOT USB mode. I assume you already have the fastboot drivers installed on your computer, so I won't get into detail on that.
Click to expand...
Click to collapse
I get the error attached below in attachments, fails to write. I am up to 2.18.0001 HBOOT S-OFF with the HBOOT you included
HipKat, the RUU is downloading. The Evo Softbrick.zip link you have in there leads to me to: "The file link that you requested is not valid."
very simple
reflash by doing adb push update update.zip then format sd
by adb mount/sdcard
then adb erase sdcard
then do fastboot flash update update.zip
erase all data
then should be good to go.....
thats how i fixed mine
HipKat said:
No, there never was a solution, other than the doc I attached, which may not work and again.. someone running CM get's this Boot Loop issue....
Click to expand...
Click to collapse
I just ran the RUU, that is all I've done because of the down link. I'm now at 0.79.0000 HBOOT S-OFF with 1.39.00.0426 radio. Now whenever I turn on my phone it goes straight to bootloader. Entering recovery gives me 5 vibrations with notification light blinking green
Edit: It no longer goes to bootloader whenever I turn it on. It gives me 5 vibrations with blinking green notification light. Still have access to HBOOT
That means it's in maintenance mode. As for that document, it's s few months old.maybe you can do a search for that missing file.
Swyped From The Hippest MIUI'd phone Using XDA Premium
I now have HBOOT 2.10 ENG S-OFF (Hex-edited one from here). So I have fastboot command capabilities. Trying to flash mtd-eng.img gives me the attached error.
Going to start searching for that file. I have fastboot capabilities, so I think I need the nv.img so it's time to go hunting
Edit: So I had HBOOT 2.10 ENG S-OFF. I followed the document HipKat posted, was unable to erase nv, microp, and radio. I flashed nv.img, then I ran the RUU again.
Back to .79 HBOOT S-OFF. Turning the phone on vibrates it 5 times and flashes green light. No access to recovery either.
Starting to think we are out/almost out of options... Guess it is time to start talking about getting S-On with somewhat recent HBOOT and radios.
you don't have to get S-on. If all it does is go to that Maintenance Mode, then just take it to Sprint. They'll probably replace it
HipKat said:
you don't have to get S-on. If all it does is go to that Maintenance Mode, then just take it to Sprint. They'll probably replace it
Click to expand...
Click to collapse
I can still access HBOOT, however. I have a couple of friends at the local Sprint store (due to a Samsung Intercept for my sister - worst phone ever). The problem is, several of the managers there check the HBOOT. They've checked it in front of me (I had S-On) and for recovery on the Intercept. When I asked why they checked, they said they support repairs but not replacements (could go through Asurion) with rooted devices.
Sent from my SPH-M900 using xda premium
Wow, that's the first time I've seen that someone at Sprint checks for Root.
HipKat said:
Wow, that's the first time I've seen that someone at Sprint checks for Root.
Click to expand...
Click to collapse
They do check them. I had mine checked the two times I needed service. Last time they even updated the phone to the latest 4.67 update without consent.
atapia984 said:
They do check them. I had mine checked the two times I needed service. Last time they even updated the phone to the latest 4.67 update without consent.
Click to expand...
Click to collapse
I've seen so many posts about Sprint doing updates without consent. If you ask them to not do the update, they ask questions.
Well, I shall search for a way to get S-On with no access to recovery; I'll continue flashing to see if I can get something to stick before that though. My fallback plan is a Samsung Moment I have sitting around...

[Q] HOX struggling to get back to stock....

Ok guys ive not posted much as ive had no need to... im fairly competant when it comes to messing with my phone but im baffled now.... Ive rooted desire hd, sensation xl and a few other phones so im not a complete noob i wouldnt say... although you lot may haha
OK, so ive tried to go stock from all of the different nandroid back ups that correspond with my device (because my hard drive crashed and killed all my data,) on this site to no avail. Every single one no matter how i do it, or in what manner, give me the same issue, an md5 checksum mismatch error. Doesn't matter what its called or where its unzipped too, i get the exact same thing every time. Also since starting this process abd no longer works.... The laptop sees the phone and if i try to use fastboot or any of the fastboot commands they work fine. If i do adb devices it shows nothing in the list. I can fastboot boot boot.img and then clear the cash but i just cannot get it to restore the back up at all so i can then flash the recovery after and get it running again.
Im currently in the process of downloading what i believe is the RUU for this phone so we will see if this works.
I need to reset back to factory because i want to sell the phone as a stock unrooted phone to a family member who will want to be able to do ota updates etc. And if it ever breaks or needs sending back it needs to be stock. so........ i was wondering if anyone on here could help me in any way to get my current brick back to a working stock HOX.
CID is H3G_001
version is 2.17.771.3
currently on the lastest CWM
on my fastboot screen ive got
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.12.0000
CPLD-None
MI CROP-None
RADIO-2.1204.135.20H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH : OFF
Jun 28 2012,11:31:28
Now is it possible usb debugging may have been turned off thus stopping the adb commands? I cannot get past the boot loop so i am unable to check...
All im trying to do is get back to the stock phone. If anyone is able to help me do that i would gladly show my appreciation....
Kind Regards
Brett (Nibbzy)
1. DL this: http://androidfiles.org/ruu/securek...adio_2.1204.135.20H_release_277220_signed.exe
2. do 'fastboot oem lock' (locks the bootloader)
3. Phone in fastboot mode, right click on RUU and run as admin.
3. Sit back and wait.
TToivanen said:
1. DL this: linky
2. do 'fastboot oem lock' (locks the bootloader)
3. Phone in fastboot mode, right click on RUU and run as admin.
3. Sit back and wait.
Click to expand...
Click to collapse
HI mate,
My bootloader is now in ***RELOCKED *** status. I
Ive already got 2 x copies of that exact file from that exact link. but it tells me to turn the phone on and will not do anything untill i do. If it turn it on. it boots for about 30 seconds and goes right back round to htc screen again and then just loops eternally.
thanks for your help....
edit.... i think it was the admin rights i was missing! your an absolute legend and if you have a donate button anywhere post me the link in a pm.
Hold the volume down and power button pressed together as long as it takes to see the bootloader ....
Do not let go of the buttons
Hold volume down and power. Then in the bootloader menu, select fastboot. EDIT:
TToivanen said:
Hold volume down and power. Then in the bootloader menu, select fastboot. EDIT:
Click to expand...
Click to collapse
ABSOLUTE PAIR OF LEGENDS.... 8 HRS ive been ready to smash the b**tard thing for..... lolol
Ha ha
Don't mention it
TToivanen said:
Ha ha
Don't mention it
Click to expand...
Click to collapse
Ive been struggling with a similar problem. i want to get back to stock so that i can sim unlock my device. It seems to me that i need to run the correct RUU file in order to get back to stock, however im not sure which file i should be running. my CID is ORANG001 and my HBOOT is 1.36.
LiamKenny said:
Ive been struggling with a similar problem. i want to get back to stock so that i can sim unlock my device. It seems to me that i need to run the correct RUU file in order to get back to stock, however im not sure which file i should be running. my CID is ORANG001 and my HBOOT is 1.36.
Click to expand...
Click to collapse
Please do the fastboot command 'fastboot getvar version-main'
Sent from my Nexus⁴ using Tapatalk 4 Beta
version main: 3.16.61.6
TToivanen said:
Please do the fastboot command 'fastboot getvar version-main'
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
version main: 3.16.61.6
LiamKenny said:
version main: 3.16.61.6
Click to expand...
Click to collapse
RUU is not available but you can get back to stock using a nandroid backup. Download the one that matches your main version here: http://forum.xda-developers.com/showthread.php?t=1975140
If it's zip/far, extract it and copy the files onto your sdcard nandroid folder. Then restore the backup in recovery just like you normally would. You may also flash stock recovery and lock the boot loader if you want.
Sent from my Nexus⁴ using Tapatalk 4 Beta
i went into clockwork mod and did a factory reset data, then i wiped the dalvik cache and then tried to restore the file which you linked to me, but it says "MD5 mismatch". do you know where i have gone wrong?
LiamKenny said:
i went into clockwork mod and did a factory reset data, then i wiped the dalvik cache and then tried to restore the file which you linked to me, but it says "MD5 mismatch". do you know where i have gone wrong?
Click to expand...
Click to collapse
Maybe a bad download? Did you extract it?
Sent from my Nexus⁴ using Tapatalk 4 Beta
yeah, i did. and then i put the extracted folder on my sd card. ill download it again and see if it works, but can you tell me what are all of the steps i need to do, in case I'm a complete noob and missed out something crucial
I've downloaded the nandroid backup from a few places now and none of them seem to work. the phone just stops on the boot animation and goes no further
I had the same on my hox flashed boot img erased cache,stuck on boot animation
Sent from my 801n M7_UL

Need Help to unbrick verizon desire 526 (htcd100lvw)

I'm pretty new at this. Was just given this phone, was going to do the update from HTC Sync, which I have since realized I shouldnt have done anyway, the phone got disconnected during the update and is now bricked. I can hold the volume button and power and get to the htc download mode. When I press reboot to bootloader, the boot to recovery mode it shows an exclamation point in an upside down triangle.
I've searched for hours trying to find a way to reflash the factory firmware and am not having any luck. If anyone could help I would greatly appreciate it.
Download the RUU and flash it
Thats my problem, where do I get it?
I'd really appreciate any help. I've got no phone right now, lol.
deernet said:
I'd really appreciate any help. I've got no phone right now, lol.
Click to expand...
Click to collapse
The RUU attached to this post should work beautifully for you.
https://forum.xda-developers.com/desire-526/general/verizon-htc-desire-526-boot-loader-root-t3587118
You can also read through that thread of mine to unlock your bootloader and root the phone.
Heres a direct link to the RUU.
http://www.mediafire.com/file/bd2u64...y4/0PM3IMG.zip
Unzip the download.
Copy the 0PM3IMG.zip that is inside to a SD Card.
Put the sdcard in the phone.
Boot the phonr into download mode.
Hit volume up key to flash the ruu.
You will most likely need to do it 2 times.
Possibly more. If the phone reboots without flashing everything do it again.
You will see when it flashes system files. If it flashes system it is good to go.
Reboot the phone.
Enjoy the Fresh Out of the Box phone.
Please hit the thanks button.
@deernet Did what @BigCountry907 shared help you fix your phone?
It was a copy of the factory RUU. Rom Update Utility.
HTC way of running an update from the sd
Most of the time you can find them.
BigCountry907 said:
The RUU attached to this post should work beautifully for you.
https://forum.xda-developers.com/desire-526/general/verizon-htc-desire-526-boot-loader-root-t3587118
You can also read through that thread of mine to unlock your bootloader and root the phone.
Heres a direct link to the RUU.
http://www.mediafire.com/file/bd2u64...y4/0PM3IMG.zip
Unzip the download.
Copy the 0PM3IMG.zip that is inside to a SD Card.
Put the sdcard in the phone.
Boot the phonr into download mode.
Hit volume up key to flash the ruu.
You will most likely need to do it 2 times.
Possibly more. If the phone reboots without flashing everything do it again.
You will see when it flashes system files. If it flashes system it is good to go.
Reboot the phone.
Enjoy the Fresh Out of the Box phone.
Please hit the thanks button.
Click to expand...
Click to collapse
I am having the same problem. I followed your directions exactly, but I receive a failed message. I've tried several times without success. Is there any thing else I can try?
badHTC526 said:
I am having the same problem. I followed your directions exactly, but I receive a failed message. I've tried several times without success. Is there any thing else I can try?
Click to expand...
Click to collapse
I successfully flashed a RUU on this device. I can walk you through it
Sent from my Desire 526 using XDA Labs
Figlet said:
I successfully flashed a RUU on this device. I can walk you through it
Sent from my Desire 526 using XDA Labs
Click to expand...
Click to collapse
I also received a failed message -2,19. Any help would be appreciated. Wondering if maybe the zip is just corrupted as I downloaded it with ADM?
Vyrrus2k9 said:
I also received a failed message -2,19. Any help would be appreciated. Wondering if maybe the zip is just corrupted as I downloaded it with ADM?
Click to expand...
Click to collapse
If I remember right, I booted to fastboot and typed 'fastboot oem RebootRuu' (without quotes) to get to the RUU flashing fastboot partition, then I flashed the smaller hboot ruu zip first, and the other large ruu 2nd.
I used the file downloaded by htc sync manager and cancelled the software update before it finished decompressing the archive.
I sold the one I was using but I have another at the house. I need to order a battery and screen for it and then I'll record a step by step of my method. Might be a week or so
(Sorry for the edits; I forgot the quote)
Thank you. Any help is greatly appreciated.
Well, I still haven't ordered anything for it. Taxes are coming back late, so I'm flat broke, but I haven't forgot about you. I remember it taking me a few tries to get the order just right, but once I figured it out the phone updated like butter. I had ended up soft-bricking it using the bootloader unlock method provided by @BigCountry907.
Have you gone back and tried it again? A lot of times I'll put a phone up in the box and come back to it and have it done in minutes if I just leave it alone for a while.
Will download zip file again and try it again. You never know. Can't hurt!
Any direction as to how to flash my phone if it keeps failing with my previously stated errors? I think it has a virus and it is acting possessed and generally driving me crazy. Thanks in advance!
mediafire link is dead
Thank work now :good:
Mediafire Link is Dead again
Anybody having this 0PM3IMG.zip file somewhere?

Categories

Resources