Related
I could really use some help here guys. Last night I flashed a new ROM - ThunderShed-v1.6_CM7.2-tbolt using Rom Manager/ClockworkMod (had been using CM7.1 without issue). I also updated the kernal to imoseyon_leanKernel_v6.2.1AOSP (didn't change ANY kernal settings) after reboot and install gapps. Everything seemed fine, however after powering off and back on again. I am now stuck in a boot loop. HTC screen phone vibrates, black screen, then HTC screen. I then attempted to boot into HBoot screen which I was able to do. Clicked on recovery and attempted to get into clockwork mod and restore the backup I'd created. Phone just reboots don't get to recovery and continuous HTC Screen black HTC Screen. This isn't my first rodeo with flashing roms (no expert by any stretch, but I'm pretty familiar with the process). Somehow I've screwed something up badly. I did attempt factory reset. I've also tried to downgrade to an older RUU although the RUU is loaded in HBOOT and seems to install (other than Bootloader is bypassed, due I believe because of Revolutionary ERROR - Can not roll back hboot version). Everything else Boot, recovery, system, splash1, userdata, etc all appear to update and show oK. After rebooting I'm back in the boot loop. I've tried installing stock roms rooted and unrooted without resolving the problem. ADB doesn't help either just never returns the device serial number. Loopfix just sits there waiting for device.
I'm am S-OFF (via Revolutionary)
-Revolutionary-
MECHA XD SHIP S-OFF
HBOOT-6.04.1002
MICROP-/
RADIO-1.16.00.0402w_1
eMMC-boot
Feb 23 2011,20:42:55
There is no PG05IMG.zip file on my SD card. (apparently can cause boot looping)
I googled to my hearts content, browsed every forum and blog I could to find a solution. Found similar issues but was not able to use any of the know fixes out there. Part of the problem is ADB doesn't see my phone. I've looked at 'loop fix' and 'thunderbolt all in one tool' these don't work for me. Any suggestions would be welcome. I'd prefer not to have to throw money at the problem to fix it.
I know I screwed the pooch on this one, maybe someone has the skills to help me unscrew it.
Thanks much in advance!
Rem
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot as PG05IMG. See if that works and you can get into recovery.
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
Windows 7 does signal that it sees a USB device but it shows unknown device. I've tried the HTC Drivers and the android USB drivers from google. Nothing doing. I am currently trying to install CWM via hboot (PG05IMG.zip). Got into CWM once tried to restore back to my backup but after the restore process same thing.
Thank you for your suggestions!
Rem
No problem. Report back with your progress.
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
No problem. Report back with your progress.
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
UPDATE: Unable to get CWR through HBOOT.
Rem
I have the same problem.
I have a brand new(refurbished) thunderbolt. I recently installed
*07-25-2012* JELLYBLUR *V1.3* CM7.2 - SPJESTER Production
I completely wiped and cleared the device. All was running fine, until I unplugged it from the charger then poof, boot loop. I can also access hboot but nothing seems to work. I have flashed a few roms, but I'm out of my depth here.
I will try putting and image on the sd card, since it does try to flash a radio when it boots.
Either of you tried an RUU. Download 605.9 or 605.19, change it PG05IMG.zip and flash it through hboot, see if it goes through.
Sent from my ADR6400L using xda premium
I have successfully flashed both recovery, and the latest mr4 radio from hboot.
Without the sd card, I was able to get it booted once after each flash. Unplugging it forced it right back into boot loop(whether card was in or not).
The only options that work are hboot, and fast boot. Neither connects to adb, or the all in one tool.
Can I flash a regular rom from hboot? I have previous version of thundershed, and various stock roms on the SD card?
dizzyman1180 said:
Either of you tried an RUU. Download 605.9 or 605.19, change it PG05IMG.zip and flash it through hboot, see if it goes through.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I've tried RUU both .9 and .19 both seem to flash fine. But after reboot same boot loop. After trying a few more times flashing various RUU I flashed .19 again. After rebooting the phone I was able to get into the phone, everything setup fine, google account, wireless, etc. But after rebooting again. Back in same boot loop. I've also tried using 2 different SD card to rule out a bad SD. Unfortunately same thing. Starting to think this is hardware not a bad rom or firmware.
Rem
Ok I tried a factory wipe, no go either....
Tried installing regular rom renamed as "pg....." that didn't work.
So I've been told as long as you have hboot you can fix anything...Not sure whats next? At this point I'd be happy to start over.
Okay, I'm gonna try and see if I can get a dev to check out this thread for you guys. Because I am not sure what to tell you to do next at this point. Its exceeded my knowledge.
Sent from my ADR6400L using xda premium
dizzyman1180 said:
Okay, I'm gonna try and see if I can get a dev to check out this thread for you guys. Because I am not sure what to tell you to do next at this point. Its exceeded my knowledge.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Dizzyman any help is appreciated. Thanks for taking an interest and trying to help!
Rem
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
Note the SIM card was not in the phone. I accidentally left it in the other tbolt I am replacing.
I factory wiped, cleared cache, and then installed thundershed from zip on SD. It has booted twice and seems to be running as it should be.
I put the sim card in and now its boot looping again. Removing the sim it boots and runs fine. The sim works fine on another thunderbolt, so I must assume the sim is fine.
I compared phones both were running the same rom and same radios. Kernels were different so I flashed imoseyon kernel to match the working phone. No go still boot looping.
Assurion sent me a "new" retail sim. Verizon told me to use my old one in the new phone. However the "new" phone will boot loop continuosly with old sim card. I have verified that the rom, radios, etc are all the same.
The mystery deepens...
tonyagee said:
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
Note the SIM card was not in the phone. I accidentally left it in the other tbolt I am replacing.
I factory wiped, cleared cache, and then installed thundershed from zip on SD. It has booted twice and seems to be running as it should be.
I put the sim card in and now its boot looping again. Removing the sim it boots and runs fine. The sim works fine on another thunderbolt, so I must assume the sim is fine.
I compared phones both were running the same rom and same radios. Kernels were different so I flashed imoseyon kernel to match the working phone. No go still boot looping.
Assurion sent me a "new" retail sim. Verizon told me to use my old one in the new phone. However the "new" phone will boot loop continuosly with old sim card. I have verified that the rom, radios, etc are all the same.
The mystery deepens...
Click to expand...
Click to collapse
Attempted the above on my device but no luck. Just same reboot loop. Just FYI. Thanks for the tip.
Rem
Even the different sim, eventually led to the same issue. I finally just convinced assurian that my replacement phone is defective (which is may be).
The only thing I can think of is that the jelly rom, combined with the all in one root tool somehow made a bad situation or the phone is simply defective.
Now my task is to see if I can flash something to make this stock...lol...I really don't want to send back a phone to assurion with clockwork and revolution on it if I can help it.
I suspect its going to be tricky as ADB doesn't work..
Here is where I stand.
1. Flashed a stock room, through hboot
2. Flashed a stock hboot through hboot. (this didn't work, revolution is locked)
3. I rebooted back to hboot.
4. removed sim card, and sd car.
5. Then I selected "Recovery" it went into standard recovery i let it sit for a bit, then it rebooted on its own back to stock, unactivated state.
I used the files from this thread
After this is seems to function perfectly normal, except I still have a revolutionary boot loader, and soff.
I let the phone reboot, and once it loaded I was able to get adb to work perfectly fine. I then returned to the above guide and fixed the boot loader, and s-off as directed. Its now completely stock. I mean it might be a version or so from whats current but a simple ota update would take care of it.
Its all brand new...Of course, I am still going to return it to asurian as I have no idea if it had a hardware issue, or what it was.
tonyagee said:
Here is where I stand.
1. Flashed a stock room, through hboot
2. Flashed a stock hboot through hboot. (this didn't work, revolution is locked)
3. I rebooted back to hboot.
4. removed sim card, and sd car.
5. Then I selected "Recovery" it went into standard recovery i let it sit for a bit, then it rebooted on its own back to stock, unactivated state.
I used the files from this thread
After this is seems to function perfectly normal, except I still have a revolutionary boot loader, and soff.
I let the phone reboot, and once it loaded I was able to get adb to work perfectly fine. I then returned to the above guide and fixed the boot loader, and s-off as directed. Its now completely stock. I mean it might be a version or so from whats current but a simple ota update would take care of it.
Its all brand new...Of course, I am still going to return it to asurian as I have no idea if it had a hardware issue, or what it was.
Click to expand...
Click to collapse
Tonyagee that's for the step by step. Tried on my Tbolt. Still boot looping. I appreciate you documenting what you did THANK YOU!
Your welcome...I definitely was on the edge of my skill set for sure....
So my thunderbolt is is in the same boat. The main cause for the boot looping seems to come from unplugging the usb from charging.
Mine will randomly stop the infinite boot looping and boot up. Sometimes it's quick. Sometimes it will take hours.
Most of the time when I manage to get it to run it is very difficult to get back into a custom recovery. It has to reboot the phone to get into recovery which most of the time just puts it into the infinite boot loop again.
If I plug mine into a computer it will charge but will not recognize the phone.
I've tried every fix known to man. No luck. I've come to deal with it as I've had this problem for two or three months now.
Sent from my ADR6400L using Tapatalk 2
---------- Post added at 08:09 PM ---------- Previous post was at 07:37 PM ----------
tonyagee said:
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
The mystery deepens...
Click to expand...
Click to collapse
Mine has done the same thing. I read that one of the failsafe ways to boot up clock work mod recovery is that it will automatically boot up after a battery pull and turn the phone back on with it plugged in.
If I plug the phone in while it is completely shut down it automatically powers it on and 9 times out of 10 it randomly reboots but sometimes it will boot up into recovery.
Sent from my ADR6400L using Tapatalk 2
(My phone is S-ON if that has anything to do with it.)
When I flashed the ROM, the installation went completely fine. I rebooted my phone after installing it and I got stuck at the boot up screen for about 10 minutes. I removed my battery so I could try again, but now my Rezound will not turn on or charge. I tried different sockets, different wires, etc. I honestly don't know how to fix it by this point. I wiped all my data and cache before flashing the ROM, and if it's worth noting I was on CleanROM before flashing this ROM.
Thank You.
xX760Xx said:
(My phone is S-ON if that has anything to do with it.)
When I flashed the ROM, the installation went completely fine. I rebooted my phone after installing it and I got stuck at the boot up screen for about 10 minutes. I removed my battery so I could try again, but now my Rezound will not turn on or charge. I tried different sockets, different wires, etc. I honestly don't know how to fix it by this point. I wiped all my data and cache before flashing the ROM, and if it's worth noting I was on CleanROM before flashing this ROM.
Thank You.
Click to expand...
Click to collapse
Won't boot to bootloader? If not I'd leave the battery out overnight and try to boot to bootloader in the morning
Sent from my ADR6425LVW using xda app-developers app
xX760Xx said:
(My phone is S-ON if that has anything to do with it.)
When I flashed the ROM, the installation went completely fine. I rebooted my phone after installing it and I got stuck at the boot up screen for about 10 minutes. I removed my battery so I could try again, but now my Rezound will not turn on or charge. I tried different sockets, different wires, etc. I honestly don't know how to fix it by this point. I wiped all my data and cache before flashing the ROM, and if it's worth noting I was on CleanROM before flashing this ROM.
Thank You.
Click to expand...
Click to collapse
What recovery are you on?
Sent from my ADR6425LVW using Tapatalk 2
I'm using Clockwork Touch Recovery. I'm able to get into HBOOT now, but when it tries to flash PH98IMG.zip, it just says "Battery voltage is too low! Please change a battery..." And I can press power to continue. I'm assuming it's actually trying to flash PH98IMG.zip, but it can't because the battery is too low? This wouldn't be much of a problem if I could charge it, but it refuses to charge either my stock battery or my extended battery.
xX760Xx said:
I'm using Clockwork Touch Recovery. I'm able to get into HBOOT now, but when it tries to flash PH98IMG.zip, it just says "Battery voltage is too low! Please change a battery..." And I can press power to continue. I'm assuming it's actually trying to flash PH98IMG.zip, but it can't because the battery is too low? This wouldn't be much of a problem if I could charge it, but it refuses to charge either my stock battery or my extended battery.
Click to expand...
Click to collapse
The recharging issue with Clockwork Touch Recovery is a known issue and is discussed in several different places in Rezound forums. You need to flash TWRP or better still Amon Ra which are more reliable and don't have this issue. You need to get a different, fully charged battery, reboot to BOOTLOADER and flash a different recovery. You should then be able to get back to a normal boot if you flashed the kernel after flashing the ROM (you did say you were S-ON, right?) If not, you can either reflash the ROM (the Aroma installer will reboo to bootloader to flash the kernel) or RUU back to stock, reflash Amon Ra, then reflash Nils' ROM. The latter approach shouldn't be required unless you really borked your system.
Ok, so apprently I am running cwm, I thought I was running amon ra to be honest but here is my problem:
Ok, I had cleanrom on my phone, lost 4g so started messing around. When I go into CWM Recover v5.8.1.4 and try to reinstall a rom or anything I just get the little CWM icon, It will not go into any option I choose. I have to pull the battery to restart. But the screen will not turn on when I push the power. Only think I can do is boot into bootloader. VZW rep said they can replace it, but was afraid I would get charged from HTC since its prob my fault. Any suggestions?
Hmm. Boot into bootloader, plug in via usb. Flash Ruu or new recovery (probably RUU)
I think that should work.
Sent from my ADR6425LVW using xda app-developers app
Reaper0294 said:
Hmm. Boot into bootloader, plug in via usb. Flash Ruu or new recovery (probably RUU)
I think that should work.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks reaper, now I cannot even get into bootloader.........some people arent suppose to mess with this stuff...and Im one of them Back to the pre for a few days.
Your battery is probably too low to boot you need to charge it or look for the cwm boot problem thread to get it to boot
Sent from my Dinc... I mean Rezound
yojoe600 said:
Your battery is probably too low to boot you need to charge it or look for the cwm boot problem thread to get it to boot
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
alright I have discovered what I've done wrong....the phone still isnt working but heres how it happened.
I did flash amon ra, and clean rom. Once I got it all setup, I downloaded ROM Manager, this has killed the phone. Like I said everything I try to flash a new rom from zip on sd, the little rom manager dude blocks me. Any suggestions on how to get rid of him so I can reflash. When I plug the phone into my computer to adb device it is not found. I have download HTC Sync.
you need to be in fastboot for it to be found
Ah the old charging problems. That's right. This guide should work. http://forum.xda-developers.com/showthread.php?t=1722989&highlight=clockwork+boot
Your phone isn't bricked, relax. For some reason none of us quite know, when any rezound with clockworkmod on it reaches fully low low battery and turns off it no longer charges correctly.
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
evoman said:
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
Click to expand...
Click to collapse
Have you tried getting into recovery from the boot loader and flashing a rom
Sent from my EVO using xda premium
evoman said:
I went to OTA update MeanRom from 3.1 to 3.2 and after the rom install and reboot my phone kept rebooting, I waited for about 45 minutes just make sure it wasnt going to take.
I then used fastboot to install my last recovery however, the recovery install froze at installing /system for over an hour. I had no choice but to try and reboot as none of the buttons worked. I am now stuck at the HTC screen and can not get into fastboot or phone.
I've tried searching for a solution for a day and still have had no luck. Cant run RUU as it has a USB error which I expected as the phone never boots.
Any help is greatly appreciated.
I am/was on latest radio/firmware/s-off.
Thanks for looking!
Click to expand...
Click to collapse
I'm confused...You were flashing a recovery from fastboot? Or were you doing a nandroid restore? You tried holding volume down + power to get into the bootloader right?
Sent from my EVO LTE
I can not get past the first HTC screen. Holding power and volume down wont work as it wont get past the first screen. I was using a Nandriod.
Thank you.
evoman said:
I can not get past the first HTC screen. Holding power and volume down wont work as it wont get past the first screen. I was using a Nandriod.
Thank you.
Click to expand...
Click to collapse
Did you do the restore from recovery (TWRP) or did you use fastboot? I ask because fastboot isn't typically used to restore from a nandroid backup, so just trying to understand your description. Do you have adb on your pc?
Sent from my EVO LTE
premo15 said:
Did you do the restore from recovery (TWRP) or did you use fastboot? I ask because fastboot isn't typically used to restore from a nandroid backup, so just trying to understand your description. Do you have adb on your pc?
Sent from my EVO LTE
Click to expand...
Click to collapse
I apologize I really wasnt clear. I was using TWRP. I just uninstalled it a couple of weeks ago I will go grab it again right now.
evoman said:
I apologize I really wasnt clear. I was using TWRP. I just uninstalled it a couple of weeks ago I will go grab it again right now.
Click to expand...
Click to collapse
Gotcha...then this is very strange. Once you have adb installed, try plugging the phone into your pc, power it on and when it's at the HTC screen try the "adb reboot recovery" command and see if that gets you into TWRP. I've never tried using adb from that screen so not sure if the phone is capable of communicating at that point, but worth a shot...
Sent from my EVO LTE
Ok installed r20.0.3 of Andriod SDK. I installed Andriod SDK platform tools REV 14. Now what should I do?
premo15 said:
Gotcha...then this is very strange. Once you have adb installed, try plugging the phone into your pc, power it on and when it's at the HTC screen try the "adb reboot recovery" command and see if that gets you into TWRP. I've never tried using adb from that screen so not sure if the phone is capable of communicating at that point, but worth a shot...
Sent from my EVO LTE
Click to expand...
Click to collapse
Premo, I tried that but I get an error device not found. However, I do hear my laptop make the usb connecting noise when I plug in my phone.
Any other suggestions?
Thank you
evoman said:
Premo, I tried that but I get an error device not found. However, I do hear my laptop make the usb connecting noise when I plug in my phone.
Any other suggestions?
Thank you
Click to expand...
Click to collapse
That's what I was afraid of...the only other thing I can think of is to maybe try flashing a new boot image, but you may have the same problem you had with adb in not being able to communicate with the phone. What you would need to do is pull the boot.img file out of the MeanROM zip, put it somewhere on your PC, then with your phone plugged in open the command prompt and type:
Code:
fastboot flash boot <path_to_boot_img>boot.img
It's basically the same process as installing a new kernel on the new hboot version, which is outlined here:
http://forum.xda-developers.com/showthread.php?t=1794867
Typically you have to be in the bootloader for this, but it's worth a try from the HTC screen. I've been successful with the fastboot command when adb does not see the device, so may work in this case as well. If not, then I'm out of ideas. Since you can't get to the bootloader, you should be able to take it into sprint or best buy without them knowing you tampered with it. Just tell them you took the latest OTA and the battery died during the installation or something. Hopefully they will exchange it, but you run the risk of getting one with the new hboot and losing S-OFF Better than no phone at all though, I suppose...
Not too sure if u have a recovery installed but regardless you should be able to simulate a battery pull by holding power button for 10 seconds or until the captive button lights flash 12 times I think. When the phone powers down press and hold volume down only and you should boot into boot loader. From here you should have a better chance of using adb or fastboot or recovery if you have twrp installed. If you can get to boot loader you have options especially since your s-off.
Good luck man
Sent using my LTEVO
Ok I was able to get into bootloader and tried to flash MeanRom after wiping cache/dalvik/factory reset/system three times each with a new download of MeanRom and it said it flashed successfully. I rebooted and it keeps getting almost to setup then reboots. Should I try an RUU again? If so what version should I use?
Bootloader says:
Jewel PVT SHIP S-OFF RL
CID-SPSC_001
HBOOT-1.12.111
RADIO-1.05.11.0606
Thanks again!
evoman said:
Ok I was able to get into bootloader and tried to flash MeanRom after wiping cache/dalvik/factory reset/system three times each with a new download of MeanRom and it said it flashed successfully. I rebooted and it keeps getting almost to setup then reboots. Should I try an RUU again? If so what version should I use?
Thanks again!
Click to expand...
Click to collapse
That's good you can get into the bootloader, as previous poster said, you have a lot more options. I would save RUU as a last resort. See if you can flash a different ROM, like viper 4g or clean ROM. Or maybe an older version of mean ROM.
Sent from my EVO LTE
That's odd that after a full wipe mean ROM won't boot. Wasn't there issues with mean ROM if your recovery wasn't up to date. I would do a full wipe and try to restore a nandroid. Someone with more knowledge than me can defo help you . You can access bootloder, you have a recovery installed so you should be fine.
Sent using my LTEVO
are you on the latest version of TWRP? version 2.2.2, mean rom has had some issues with older versions...
bog3nator said:
are you on the latest version of TWRP? version 2.2.2, mean rom has had some issues with older versions...
Click to expand...
Click to collapse
No I wasnt so I just updated and will try again. Let you know soon. Thank you
Ok upgraded to the latest TWRP and tried MeanROM again. No go so now I will try CM10 to see if that works
Great news CM10 works and so does an old version of MeanROM guess I just cant run version 3.2 or 3.3. Thanks again for all of the help everyone! This place is the best.
Your phone must not like the new kernel.
Sent from my EVO using Tapatalk 2
thicklizard said:
Your phone must not like the new kernel.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am not sure if that is all it is. I tried to install 3.3 and then flashed the stock kernel over it and still couldn't boot properly. Its ok it forced me to try CM10.
I really need some help if possible looks like I bricked my phone
I'm on Hboot 2.09 dirty racun S-off I was running meanbean 3.09 rom
I was trying to flash cm 10.1 for jewel. I used goo manager to download rom super wipe zip and gaps
I flashed the zips in this order super wip cm 10.1 and then gapps using twrp 2.4
It ran through all the steps then said successful I rebooted the system I was waiting for it to reboot about five minutes. I tried to turn power on and nothing happened I tried this several more times and nothing I plugged in charger and no orange light well no light at all I let it go over nite still nothing I plugged USB cord into computer and my computer detected it and installed drivers for something beginning with a q I forgot to write down in my rush headed for work. This is as far as I have gotten is there any help? ?
gscarborough said:
I really need some help if possible looks like I bricked my phone
I'm on Hboot 2.09 dirty racun S-off I was running meanbean 3.09 rom
I was trying to flash cm 10.1 for jewel. I used goo manager to download rom super wipe zip and gaps
I flashed the zips in this order super wip cm 10.1 and then gapps using twrp 2.4
It ran through all the steps then said successful I rebooted the system I was waiting for it to reboot about five minutes. I tried to turn power on and nothing happened I tried this several more times and nothing I plugged in charger and no orange light well no light at all I let it go over nite still nothing I plugged USB cord into computer and my computer detected it and installed drivers for something beginning with a q I forgot to write down in my rush headed for work. This is as far as I have gotten is there any help? ?
Click to expand...
Click to collapse
Sounds like QSUSB DLOAD.. Think that means ya bricked.. Happen to me a while back but i got lucky
Nooblube said:
Sounds like QSUSB DLOAD.. Think that means ya bricked.. Happen to me a while back but i got lucky
Click to expand...
Click to collapse
What did you do to unbrick your phone?
gscarborough said:
What did you do to unbrick your phone?
Click to expand...
Click to collapse
try the racunhunter from unlimited.io
bigdaddy619 said:
try the racunhunter from unlimited.io
Click to expand...
Click to collapse
I have had problems downloading from Goo in the past, the MD5s didn't match a few times so got used to downloading from source and stopped having those issues. Try downloading from the sources, all the things you need, check the MD5s to ensure they aren't corrupt and set aside. Sounds like the cell will power up so try the bootloader methods, power down while turning on and if you can get to the bootloader you should be golden. Just follow the other posters recommendations etc..
good luck.
waterbound said:
I have had problems downloading from Goo in the past, the MD5s didn't match a few times so got used to downloading from source and stopped having those issues. Try downloading from the sources, all the things you need, check the MD5s to ensure they aren't corrupt and set aside. Sounds like the cell will power up so try the bootloader methods, power down while turning on and if you can get to the bootloader you should be golden. Just follow the other posters recommendations etc..
good luck.
Click to expand...
Click to collapse
The problem is I can't turn the device on it doesn't even charge or there is no orange light showing a charge
gscarborough said:
The problem is I can't turn the device on it doesn't even charge or there is no orange light showing a charge
Click to expand...
Click to collapse
I tried the racunhunter but i kept getting device cant be detected. any other options or advice?
Talk to unlimited via support, they will walk you through it.
Sent from my EVO using xda premium
mrlakadaddy said:
Talk to unlimited via support, they will walk you through it.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
i will try that next i hadnt earlier becuase it says support only if using one of their tools.
gscarborough said:
i will try that next i hadnt earlier becuase it says support only if using one of their tools.
Click to expand...
Click to collapse
Well everything failed good thing for best buy insurance my replacement phone will be here Monday
Wow. That's nuts that you actually bricked from wiping and flashing a ROM and gapps. I can't even imagine how that would happen,...even with a bad DL.
From my Evo LTE, yup.
scottspa74 said:
Wow. That's nuts that you actually bricked from wiping and flashing a ROM and gapps. I can't even imagine how that would happen,...even with a bad DL.
From my Evo LTE, yup.
Click to expand...
Click to collapse
So was I . Waterbound said maybe the downloads through goo manager or maybe I just messed up because I flashed kernel separate through flash GUI when I didn't have to because I was dirty racun s-off. Thanks to best buy I will try again next week. Thanks to everyone for the advice