[Q] DINC2 dev unlocked S on bricked? - Verizon Droid Incredible 2

Hey guys ive looked over and over and i can only find bits and pieces that are similar. My phone was acting up so i decided to try and run a ROM, i found out that since my version that its hard to go back to 2.3.3 so i ran the htcdev unlocker (dumb idea) then i tried to update the rom. I get a white HTC screen now and i cannot access it via command line. I can get into the bootloader by pressing the power and volume buttons. Ive tried numerous PG32IMG files with no luck either it says its invalid or the phone gets stuck on "checking PG32IMG.zip" any ideas or is the phone a lost cause?

Do you have a recovery?
Sent from my Incredible 2 using xda app-developers app

make sure u have one zip at the end, wins usually will ad zip to it giving u 2 zips at the end. bootloader wont recognize the PG32IMG.zip if theres a PMG32IMG.zip.zip just delete the extra zip. and check md5 may have a bad download. condemed has the factory ota posted look for it try it. If u unlocked ur bl relock it then try the rom,

Related

DEAD EVO! Help please..

I really need some help. Im s%*& bricks right now.
I have Damage Control 3.2.2 with the OTA 1.47 installed. I am rooted
I have to return my Evo for warranty exchange to The shack.
I did a stupid thing and tried to run [ROM]RUU_Supersonic_1.32.651.1 exe
RUU ran about 14% and then gave me error.
NOW Evo wont pass the White htc EVO 4G screen!!!! I can still access clock recovery and do nandroid restores, but it still wont get pass the white htc screen! am I toast?
If you can get into recovery, then just download a new rom and flash. Hboot will work with usb.
Sent from Ye Olde Evo
hboot on the device? Ive never used Hboot? Can you give me a 1,2 step if you dont mind. sorry for my noobness
Hold volume down then power as well.
Flash the stock rom via recovery or use nandroid to restore your Evo then try RUU one more time?
xavier1022 said:
I really need some help. Im s%*& bricks right now.
I have Damage Control 3.2.2 with the OTA 1.47 installed. I am rooted
I have to return my Evo for warranty exchange to The shack.
I did a stupid thing and tried to run [ROM]RUU_Supersonic_1.32.651.1 exe
RUU ran about 14% and then gave me error.
NOW Evo wont pass the White htc EVO 4G screen!!!! I can still access clock recovery and do nandroid restores, but it still wont get pass the white htc screen! am I toast?
Click to expand...
Click to collapse
Sounds like a similar problem I was having a week ago... I couldn't load any of the DC ROMs, but I could install Fresh 0.3 (but not 0.5), Aloysious, and the 1.47 Rooted stock ROM. Try to install one of these, and see if they will load. Also, search for the PC36 file that is used to ROOT the phone. Put that on the SD card, power off, then hold Vol.Down and power on. It should try to find the PC36 file. If you get a message saying the main version is older, it is the EXACT problem I had... You will have to do Toast's part 2 of the ROOT to restore it. The biggest problem, is getting it to see the PC36 file. you will need to flash the mtd-eng file in toast's method. Where I had the problem, is I couldn't get the sd card to recognize in adb. Someone had posted up an ADB code to get the SD card mounted so it would be able to flash the mtd-eng file, but I can no longer fid that code.... Hopefully someone will see this and know what I am talking about...
Thanks guys I had tried most of these solutions before posting . Nothing would change my screen. I did fix it though... It was there easiest thing ever..I just flashed the new Ruu 1.47 . I guess it won't let you downgrade . Now I'm stuck with non rooted Evo ... I guess I'll make my way over to dev forum . Thanks again
Sent from my Evo using XDA App

Tried to downgrade to stock. Help

I rooted and installed the leaked OTA. After hearing about the possible 2.2 I tried to downgrade the radio. Something messed up along the way and now I'm stuck with an incredible that is showing no internal memory (won't even let me save a picture), will not read an SD card and keeps rebooting when I remove the usb cable. I'm stuck in a real hard place. If anyone can assist me in restoring my phone and how to go about it, it would be appreciated. Also it is now showing my phone as an unknown device when I connect to the pc and I can not get into adb.
Can you reboot into recovery? (power off, then hold volume down while powering back on) then select recovery?
If you can get into clockworkmod recovery, we can get you back up and running.
do a hard reset. if that doesnt work, take it back to vzw and make up a story on how it got the way it is.
TIP: i dont think you can downgrade the radio.
Sent from my Incredible using XDA App
I started following this tutorial http://www.youtube.com/watch?v=eeuiURZZZds and after trying to run 'flash_image misc mtd0.img', it said I did not have enough memory so I just unplugged the phone and tried to reboot, but it brought me to the recovery console and it's the stock one. So the stock img was able to install. I don't even have clockwork now. I should have left it alone. I have a constant sd card icon with a ?.
just hard reset or ruu . if this doesnt work, then i think you bricked your radoio. do you have 3g?
Sent from my Incredible using XDA App
Jd is right. Just ruu back to the leaked ota. If you can get to stock recovery you should be able to ruu. Once your back up and running we might be able to help you downgrade. First things first.
Just tried the hard reset it was a no go. I have 3G service and I made some calls to make sure it worked. After the hard reset it is still showing the sd card icon with ?. For the RUU do I need any drivers because the phone is showing up now as an unknown device.
Just give it a shot.
ruu is the way to go. your problem is more sever than hard reset fixijg.
Sent from my Incredible using XDA App
P.s. If you follow the downgrade tutorial by "IncredibleDoes" you can use an sdcard adapter and put the card into your pc (since your phone usb drivers aren't working), copy the "pb31img" file over, then reboot back into hboot, and it will put you right back to the original stock in one step.
If you have a card reader on your pc, turn the phone off, put the card in the pc and make sure it's formatted properly. Then put the ruu file on the card. (Follow the instructions in the unroot sticky topic.) Then put card back in phone and boot into stock recovery. It should apply the update.
Sent from Incredible using Tapatalk.
[email protected]
hows the ruu going?
Sent from my Incredible using XDA App
I'm still trying. It's not looking good. Hboot is still version .79 after I flashed the stock img. I'm probably going to have to call it a night for now though. I'll be back tomorrow to trouble shoot it some more. I'll write more after I try it again. Thanks for the help tonight!
of you need additional help feel free to pm me anytime.
Sent from my Incredible using XDA App
Hboot is NOT going to downgrade....no matter what you do. The stock (pre-ota) rom will run fine with the newer hboot version.
samwathegreat said:
Hboot is NOT going to downgrade....no matter what you do. The stock (pre-ota) rom will run fine with the newer hboot version.
Click to expand...
Click to collapse
Yes it will downgrade, as the ota leak is a newer version of .79. that is, if you follow the procedure right.
Also, yes you can downgrade the radio, in response to an earlier post.
If you got out of memory type messages running through that method, then you did it wrong. Maybe you tried it outside of clockwork? I haven't watched the video to do it, but seeing how I made the original post for it, I know it works.
Interesting! I wasn't aware of that breakthrough (hboot downgrade).
In that case, I suggest ruu'ing back to the leaked OTA (so that your USB and SD are both working again), then try following the instructions that adrynalyne referenced.
Good Luck.
http://forum.xda-developers.com/showthread.php?t=727263
I ruu'ed the img. The phone starts up and works normally. Except it still shows the internal and SD card memory as unavailable and the usb restarting after removing the cable. I tried to reload the leaked OTA through recovery, but it gets an error saying the file is not on the SD card.

[Q] Bricked if I cannot reach recovery?

Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.

Help with root please yes ive read and done alot!

Hey all and sorry for this thread as i know you ahve probably seen them before but for the past week i have been trying to root my Wildfire S which was given to me after i sold my other phone.
Now i have read many posts and tried many things but so far i have gotten no where and i have no idea what im doing wrong, i have been to the HTC website and signed up i have then downloaded the right exe file (o2de/en if i remember right) started to run that then when the phone reboots the applicatin dies and the white screen i get when i unplug the cable is "ruu..." and thats it no other text.
I have also tried installing zip files onto the sd card and running them but these have failed too specially when it comes to the root.zip al i get is a red triangle with an explanation mark (up +power > install from sd = nothing)
Can someone help me out, i basically want to try soem roms out i have teh one thats on i have been using go launcher with ICS on it but it does not work fully to my likening plus if its possible i want to change the start up screen adn also get rid of some of the bloat wear.
Thanks in advance if someone is willing to take the time to look and help out. Im near the end of my teather and re-installing go launcher and evrything else (wiped the phone clean before attempting to root)
Btw ive tried guides on this site and on many others using htc website, pg76img (3.75 and 3.50mb versions) and now like i said im stuck.
Phone is wildfire s
software 2.13.206.1
htc files ive tried:
O2DE/UK 2.13.206.1 PG7610000 Download < one i need and keeps failing
HTC EU 2.13.401.3 PG7610000 Download
This one helped me when i was in your condition...hope this qill help you too
androidforums.com/wildfire-s-all-things-root/480954-guide-how-root-wildfire-s-s-finally.html
Sent from my Wildfire S using XDA
abhi8569 said:
This one helped me when i was in your condition...hope this qill help you too
Sent from my Wildfire S using XDA
Click to expand...
Click to collapse
Yeh tried that tutorial before and always got stuck on this part: C:\​Users\​[YourLoginNameHere]\​AppData\​Local\​Temp​\​{82B23FCD-D5D0-45CA-A3A2-5350D3926551}
Anyway finally got round it by using CCleaner and finding the right app an now installing the SDK. Dunno why i didnt think of clearing out the temp folder before doh! Will report back if i have another issue. =)
Nope stuck, this was the issue i was having before. I thought i just fixed it but nope not getting any further.
I am upto fastboot oem get_identifier_token, the issue i had was i would plug in the usb cable get 3 short fast beeps from the computer (not recognized) which i have since fixed so it makes the correct beep. But soon as i do the following:
cmd
cd \
cd android
fastboot oem get_identivier_token
I get "waiting for device".
I will have another shot tomorrow been a good hour now iphone was alot easier to do lol
Guess im staying unrooted then im stuck =(
waiting for device means it's not connecting in fastboot mode.
you need to boot the phone by holding vol- and power, then after it's finished reading the sd card, press power again to select fastboot mode (the writing at the top should say "fatboot usb" in re writing.
is your phone bl-unlocked or s-off? because i think you need one of those first before you can try flashing custom recovery?
::EDIT::
if you're having problems with HTCdev site etc....I think there was a tool floating around somewhere that could unlock bootloader without HTCdev site....
::EDIT2::
http://forum.xda-developers.com/showthread.php?t=1576844
try this tool for BL-unlock without htcdev.

[Q] Desire HD Not Booting (Flashing Orange LED)

Hi Guys, hoping someone can help me:
I have a Desire HD that has been rooted with S-OFF, after flashing a new ROM, the device wouldn't boot, when trying to start the device up, it will vibrate 3 times and flash the LED. If I try boot into recovery, it vibrates 5 times with a flashing green LED.
At the moment all I have is ADB access (no fastboot) and can't boot into the bootloader screen.
Through ADB I was able to reflash the recovery using the flash_image tool and I can boot into recovery by connecting the USB cable, I have flashed a few different ROMS through recovery, but the device will still not boot after this, I'm thinking the issue might be the radio image, which I have not been able to flash through flash_image (get -1 error code when trying this).
Any suggestions on how to proceed or what to try would be much appreciated, I'm also not fully clued up on what all can be done through ADB, so any suggestions on that front would also be appreciated.
Did u try runing a ruu.. use AAHK it will help u to flash the ruu provided ur phone is recognised by the computer..
Sent from my Desire HD using xda premium
adilrenzu said:
Did u try runing a ruu.. use AAHK it will help u to flash the ruu provided ur phone is recognised by the computer..
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Thanks for your response.
I have tried running RUU from the PC, which I got from here:
http://shipped-roms.com/index.php?category=android&model=Ace
The utility gives an error saying it cannot connect to the device, does the update utility not require me to boot into the bootloader to work?
I also tried downloading a few of the RUU zips there, but so far I haven't been able to flash them, just get an error "Can't to open <Filename>.zip (bad)", however I have checked that the zips are not corrupt, and I am able to flash other custom roms, not sure why it fails on these.
I also tried a bit with AAHK, but couldn't get it to flash anything, I put the custom rom in the folder as per the instructions, but it failed... perhaps I'm doing it wrong? maybe a bit of a walk through on how I would just flash the ROM through AAHK would help.
When you rooted phone did it say if its s-off in hboot. Try entering hboot. Power phone off then power up phone holding power button and volume down button at same time. If you can enter hboot and it says s-off get the rooted stock pd98img zip which also includes radio. Place on root of sd (no folder) power back up into hboot and let it do its thing. Volume up for yes when asked to install power button when asked to reboot.
Sent from my ICE COLD Inspire 4G
Reinaldo33897 said:
When you rooted phone did it say if its s-off in hboot. Try entering hboot. Power phone off then power up phone holding power button and volume down button at same time. If you can enter hboot and it says s-off get the rooted stock pd98img zip which also includes radio. Place on root of sd (no folder) power back up into hboot and let it do its thing. Volume up for yes when asked to install power button when asked to reboot.
Sent from my ICE COLD Inspire 4G
Click to expand...
Click to collapse
Yip, my phone was rooted with S-OFF a good while ago, only got the issue recently after flashing a new rom. I can't get into HBOOT, when I try, it vibrates 5 times and flashes the green LED with a blank screen.
Sounds like your bootloader is messed up and not the radio. Search how to push the bootloader img.
Edit: sorry I'm on way to work or I would help you search. But I know there is a thread how to fix bootloader since you cant enter hboot which sounds like its your problem. You need to fix the bootloader. Do a google see what comes up from xda.
Sent from my ICE COLD Inspire 4G
Reinaldo33897 said:
Sounds like your bootloader is messed up and not the radio. Search how to push the bootloader img.
Edit: sorry I'm on way to work or I would help you search. But I know there is a thread how to fix bootloader since you cant enter hboot which sounds like its your problem. You need to fix the bootloader. Do a google see what comes up from xda.
Sent from my ICE COLD Inspire 4G
Click to expand...
Click to collapse
Ok, thanks, have looked around, not found anything yet, but I'll carry on looking and see what I come up with, appreciate the help.
Any luck with this. I'm in the same pickle. Running JellyTime and it just stopped working. Will not boot, and recovery mode just flashed amber light. It is an android desire hd.
I would say that its a fried emmc chip, if that isn't the case (I doubt) you can use a JTAG and a riff box to recover the phone over OPST, the equipment needed can be quite costly, so taking it to a mobile repair shop that does jtagging, should work
Sent from my Desire HD using Tapatalk 4 Beta
ftj2006 said:
Ok, thanks, have looked around, not found anything yet, but I'll carry on looking and see what I come up with, appreciate the help.
Click to expand...
Click to collapse
Are you able to flash any rom at all? I would try flashing a stock rom if possible. The re-root.
thekool said:
Are you able to flash any rom at all? I would try flashing a stock rom if possible. The re-root.
Click to expand...
Click to collapse
Nope, can't flash anything, gave up on it a while ago now though and got a new phone on my contract upgrade.
raczyk said:
Any luck with this. I'm in the same pickle. Running JellyTime and it just stopped working. Will not boot, and recovery mode just flashed amber light. It is an android desire hd.
Click to expand...
Click to collapse
Didn't manage to get the device working unfortunately... seemed like the issue may have been hardware related though, hope it's not the same for you and you get it sorted.
raczyk said:
Any luck with this. I'm in the same pickle. Running JellyTime and it just stopped working. Will not boot, and recovery mode just flashed amber light. It is an android desire hd.
Click to expand...
Click to collapse
Think it might have been, read that a few places as well but just wanted to try what I could first, thanks for the input though.

Categories

Resources