Well, I've come across an embarassing situation. My problem is in the title, and for those with a keen eye, yes, I'm a Sprint tech so laugh about that if you will, don't care. Gotten that on several other forums and no help. Apparently people hate us lol. Point is, telling me I need to take the phone in isn't really much help since I'm the person you'd normally go see. Anyway on to the issue.
A while ago I came across a phone that the owner didn't want anymore, and lo and behold it turns out the reason for that was a soft brick (I can't think of what else to call it.) I'll boot the phone, it loads up to the splash screen, and at different points will just flash grey and stop loading, then after a while of being left alone try and boot up again and then freeze up. I've pretty much exhausted the range of my knowledge (Owned samsung all my life, my rooting journey has been pretty much strictly that), so I come to you guys. Below I'll list what I've tried and my specs, hopefully I don't have a paperweight with a kickstand on my hands.
Things I've tried:
RUU's out the ass, had trouble getting them to even connect to the phone (triggered it at certain points during the boot til I found the sweet spot), and when it did its thing, simply gave me Error 132 (Signature Verification failed), which apparently is fixed with s-off. Leading me to...
Revolutionary. This I did really not expecting it to work, since the last time I've used this for someone else I had to enable USB debugging and everything, meaning I need to boot into the OS. No dice here.
ADB push I'm pretty new to this particular bit, so I tried to push a custom recovery onto the device, which failed due to S-ON. (At my wits end at this point, figured, "what the **** maybe I'll get lucky.")
Specs:
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.10.0001
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
And the date and time, which is incorrect so here
Oct 15 2010, 12:07:00
I don't think I need to point out yes, I've tried hard resetting and all the basic BS most normal users are surprised to find out they can do themselves. I'm fresh out of ideas, so before I begin the painstaking process of using other peoples solutions to other problems and hoping it works for mine, I've come for some direct advice/help. I think ADB might be my best bet at this point, but I have no real idea how, and after 7 hours reading through other peoples' stuff, you can imagine I'd rather just be told if it is or isn't going to work.
tl;dr, bricked evo, pls help.
Since ur the techy guy take a old evo that might have been smashed or something but the mother board still works swap the mother board and ur good to go I guess bcuz the other evo is now just trash
Sent from my PC36100 using xda premium
lreyes15 said:
Since ur the techy guy take a old evo that might have been smashed or something but the mother board still works swap the mother board and ur good to go I guess bcuz the other evo is now just trash
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Easier said than done; phones i send in have to match the ESN on the sticker as well as on the board, so no luck with that. ALso bump.
Have you tried unlocking it with unrEVOked?
EDIT: Well that won't work if you can't get the phone to boot up. Will the phone stay on in Bootloader or Fastboot modes? You cam flash an RUU while in Fastboot. If it stays on, either that or a PC36IMG.zip might work.
Captain_Throwback said:
Have you tried unlocking it with unrEVOked?
EDIT: Well that won't work if you can't get the phone to boot up. Will the phone stay on in Bootloader or Fastboot modes? You cam flash an RUU while in Fastboot. If it stays on, either that or a PC36IMG.zip might work.
Click to expand...
Click to collapse
It'll stay on in either of those two modes. I've tried a PC36IMG as well as the RUU for the phone's Radio, and neither works. I get error 132 for the RUU and PC36IMG doesn't get detected, unless I'm doing something wrong. It's in the root of the SD card and when I boot into the bootloader it tells me nothing's there on that initial check.
psych0r3bel said:
It'll stay on in either of those two modes. I've tried a PC36IMG as well as the RUU for the phone's Radio, and neither works. I get error 132 for the RUU and PC36IMG doesn't get detected, unless I'm doing something wrong. It's in the root of the SD card and when I boot into the bootloader it tells me nothing's there on that initial check.
Click to expand...
Click to collapse
Try a newer PC36IMG, like the one from the 4.54.651.1 ROM.
Related
Hey everyone. I have an HTC Desire CDMA on U.S. Cellular. I had the pre-installed version of Android, 2.1, and I had rooted it using the unrEVOked method. Recently, the 2.2 update became available on the HTC website, so I decided to attempt an update. During the update, it hung at a screen with silver HTC letters and gave me error 171, being that there was a USB connection problem. I unplugged the USB cord and the screen switched to an HBoot type of screen with EUU selected, but nothing was able to be clicked on. If I plugged the cord back in, it would go back to the HTC screen. The only way to get out of it was to remove the battery.
Well I went on like this for a few more tries, with compatibility mode on the PC, running as administrator, switching which mode the phone was in when it was plugged in, and I never got it to work. I read somewhere that I needed to enable S-ON, but the utility to do that never worked.
There's a lot more tinkering I did, but nothing major. Eventually, I went into the recovery part of HBoot and wiped everything I could see. Now my phone would no longer boot into Android 2.1 as it had been doing before. When I started it up, it would just go to the HBoot screen and recovery screens.
I have attempted a few images of said-to-be-working U.S. Cellular HTC ROMs, but nothing has worked. I currently have a phone stuck in HBoot, and the only way I can get into it is to mount the SD card in the recovery screen and access files there. I can still install .zips from the SD card, so if there is one that would help me out, that would be just fabulous.
Now, the ideal thing would be to be able to just move right onto 2.2. Unfortunately, I don't think this will work. So I will be just fine if someone can help me restore it to 2.1, like it was when I first got it.
Also, I've been contemplating just taking it to my U.S. Cellular booth in the mall and asking if she can do a complete wipe/restore of the original software. Can the people in the stores do that? When I got it, the woman there didn't seem like she knew much about Android, so I don't think she would be able to tell that I had rooted it. Would she give me a replacement phone? What should I tell her that happened? By stretching the truth, I could say that it messed up during the update and I'm stuck with nothing on my phone now, but I don't know if she could do anything about it.
Anyway, I would REALLY like to get this fixed this weekend, and if that isn't possible, then within the next two weeks. If you have questions, feel free to ask. I'm new to these forums, but I would guess that it would email me if I get replies to this thread. If it doesn't, please email me at gavin at gavinroskamp dot com, where I'll be sure to reply.
Thanks again everyone, and I really really hope I can get this thing fixed!!!
By
GavinRoskamp said:
Hey everyone. I have an HTC Desire CDMA on U.S. Cellular. I had the pre-installed version of Android, 2.1, and I had rooted it by. During the update, it hung at a screen with silver HTC letters and gave me error 171................
Anyway, I would REALLY like to get this fixed this weekend.
Thanks again everyone, and I really really hope I can get this thing fixed!!!
Click to expand...
Click to collapse
Do you know anyone else with the same phone and carrier? You need to make a gold card so that you can recover ur phone with a non US Cellular ROM.ZIP or RUU. If you know someone then you can use their phone to make ur SDCard in to a goldcard which then let's u flash another carriers ROM.
Also have a read of this thread it has a lot of useful info....albeit related to gsm Desire but you might find some trick from the first post: http://forum.xda-developers.com/showthread.php?t=831734
Sent with Tapatalk & Desire
I did some researching for you and possibly others with the same effect as you had, i found this info posted by Joehunni on AndroidForums but it originally came from XDA so the original author is unknown. the similarity is the 171 ERROR that you reported:
"....Ok, so I know i'm not nearly the only person whos had a ****load of problems trying to run an RUU so this is for some of you that had the same issues as myself. I originally saw this posted on an xda forum and it worked for me so i'm passing it along. If you are trying to RUU and keep getting stuck at the "waiting for bootloader" screen and then it ultimately fails with usb connection error 171, try this. After going through said process, instead of unplugging the phone, pulling the battery, hanging your head, and saying FML, all you have to do is leave the phone as is after first failed RUU attempt then re-run it. I know it sounds rediculously simple and impossible but trust me, just run it a second time without messing with the phone or anything (still stuck at the black HTC screen) and then run the RUU installer again, IT'S THAT EASY, enjoy! Hoped this makes someone elses day, or rather, lifetime of the phone!...."
THIS THREAD gives you the RUU but alas not for US Cellular but will get you back to a working phone I think.....: http://forum.xda-developers.com/showthread.php?t=850617
I have found out. From doing this on my uscc desire. that the 171 error comes from a failed loading of the htc boot drivers. Try reinstalling the drivers that you can get from unrevoked.
I do know someone with the same phone/carrier, but she lives about 50 miles away. I'm not sure when the next time I'll see her will be, but it won't be until a major holiday. I've looked at a generic guide to making a goldcard, and it looks pretty intense. I feel that I would be able to do it if I had to though.
Now for the non-U.S. Cellular RUU. If I were to go this route, would I simply load a rom.zip onto my sdcard and boot, would I load it on into a folder and under recovery, choose to install it, or would it be like the 2.2 U.S. Cellular RUU that I have that requires verification that I have the 2.1 official software or whatever? Also, when I go to update to 2.2 using the U.S. Cellular RUU, will it fail again?
Overall, my ideal situation now would be to first get my phone back to a working condition, as in being able to receive phone calls/texts and stuff on U.S. Cellular, and it doesn't matter what ROM I have to use, as long as it makes the phone work as a phone. Then, the next step would be to reset to a default image and/or update to the HTC/U.S. Cellular 2.2 RUU.
I'm also kinda confused with the goldcard thing. If I get the goldcard, will I then be able to flash an HTC Desire ROM for alltel or whatever the carrier is? Will it disconnect me from U.S. Cellular if I try flashing it? At this point, I'm willing to try just about anything. I won't be able to make it to town this weekend (or most likely this week either) to see if the U.S. Cellular lady can completely wipe/restore or replace the phone, so I will try as many things as possible before then.
Hey guys, I got it working again! Turns out I was able to extract the ROM from the RUU updater for 2.2 for my phone, rename it to PB99IMG.ZIP, put it on the SD Card, boot into HBOOT, and it installed 2.2 and everything is working again! No need for anything else at all. I'm surprised!
If anyone needs the 2.2 image for an HTC Desire CDMA on U.S. Cellular because you accidentally did something wrong, or even if your RUU utility isn't working, just message me or reply to this or something and I'll send you a link to it. The best way to get ahold of me is gavin at gavinroskamp dot com, or to ask me on Twitter. @GavinRoskamp.
Cheers!
Glad you got it working again and also on US Cellular!
To make goldcard is two click software, its very easy just use the Goldcard tool for windows. I will email the program to you. Making a goldcard now just adds some table code to ur existing card and you can still use it as normal. Also that code is not removed even if you reformat the SDCard. The code is only read by your phone at the time of a ROM update, it allows non carrier ROMs to be flashed such as a "stock rooted" ROM which don't have all of the carrier bloatwares and an restrictions that your carrier may have built in.
EDIT: I got a bounce back from your e-mail when i attached the Goldcard tool so here is the direct link: http://www.multiupload.com/Z4OE18SV7J all this info is contained in the first thread that i pointed you towards in post #2.
Sent with Tapatalk & Desire
What address did you try sending to? Was it over 20 MB?
Thanks for the link nevertheless.
GavinRoskamp said:
What address did you try sending to? Was it over 20 MB?
Thanks for the link nevertheless.
Click to expand...
Click to collapse
No its below 1mb. I sent to the same email as u posted and where I sent you some info about 20 hours ago
Sent with Tapatalk & Desire
Hmm. Not sure why it didn't work. Thanks for the link though!
Hi guys, I just got an Evo that will Boot up to saying "HTC EVO 4g" on the white screen, then "evo 4g" with the Android caracter, then Says "Droid" with the droid voice... after that it gets stuck in loop.... specifics are below
NO FACTORY SD Card in it... Though I have a 16gb micro sd i can put in it.
I can boot into where I see this info.
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-AMTEL224_16ab
RADIO-1.39.00.04.26
Apr 14 2010, 15:41:34
showing these options below that say
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I'm sure there are probably files that might be needed to be on the SD card to get it back booting up properly
What do I need to do, or what files do I need?
Thanks in advance!
02busa said:
Hi guys, I just got an Evo that will Boot up to saying "HTC EVO 4g" on the white screen, then "evo 4g" with the Android caracter, then Says "Droid" with the droid voice... after that it gets stuck in loop.... specifics are below
NO FACTORY SD Card in it... Though I have a 16gb micro sd i can put in it.
I can boot into where I see this info.
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-AMTEL224_16ab
RADIO-1.39.00.04.26
Apr 14 2010, 15:41:34
showing these options below that
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I'm sure there are probably files that are needed to be on the SD card that it uses to boot...
What do I need to do, or what files do I need?
Thanks in advance!
Click to expand...
Click to collapse
Okay. A few problems I see. Problem number one. You are S-on. You need to be S-off in order to flash anything. Two, your radio version is waay out of date. Did you just get the phone, used? because you said "i just got an Evo..." Have you ever had it running? If not, I probably suggest flashing back to stock, then re rooting. Do you have a custom recovery right now? From the bootloader screen (the screen you posted the info above from), what happens when you select the 'recovery' option? Do you get a red triangle? Or do you get to a custom recovery screen? (would be clockwork or Amon Ra)
HTCRALEIGHFAN, I got the phone without the original sd card, so no backup that I know of.
k2buckley, phone is used, never booted up completely since i've had it, It does go into recovery with a red triangle. I do have a good 16gb micro sd card for it. I'm just trying to get it back up and running to stock first then go from there. Thanks
02busa said:
HTCRALEIGHFAN, I got the phone without the original sd card, so no backup that I know of.
k2buckley, phone is used, It does go into recovery with a red triangle. I do have a good 16gb micro sd card for it. just trying to get it back to stock first then go from there. Thanks
Click to expand...
Click to collapse
Okay cool. I agree, that getting back to stock is your best option from where you are right now. At that point, you can leave it, or root it and get into flashing custom roms and what not. To get back to stock, you have two options. You can either run an RUU, or flash a PC36IMG from your bootloader. Here is a link to the RUU's and PC36IMG's. http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
To run the RUU, you need to have HTC Sync installed on your computer. You need to set your Evo into 'fastboot' mode, from the bootloader screen. Once it's in fastboot, connect to the computer and run the RUU. I'm not sure if you can run the most recent RUU (3.70 software), or if you need to run an older one, to match to the .79 hboot that you have. I would first try the 3.70 RUU, and see if that works. That should put you on the latest software, and update all your radios to the most recent, and update your hboot to 2.10. If you have trouble with the RUU, you can download the PC36IMG, be sure it's named exactly PC36IMG, put it on the main directory of your sd card (then put the sd card in the phone), and boot to the bootloader (power and volume down). The bootloader should then find the PC36IMG and ask you if you want to update, Select volume up to say yes. Either of those methods should flash you back to stock.
k2buckley said:
Okay cool. I agree, that getting back to stock is your best option from where you are right now. At that point, you can leave it, or root it and get into flashing custom roms and what not. To get back to stock, you have two options. You can either run an RUU, or flash a PC36IMG from your bootloader. Here is a link to the RUU's and PC36IMG's. http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
To run the RUU, you need to have HTC Sync installed on your computer. You need to set your Evo into 'fastboot' mode, from the bootloader screen. Once it's in fastboot, connect to the computer and run the RUU. I'm not sure if you can run the most recent RUU (3.70 software), or if you need to run an older one, to match to the .79 hboot that you have. I would first try the 3.70 RUU, and see if that works. That should put you on the latest software, and update all your radios to the most recent, and update your hboot to 2.10. If you have trouble with the RUU, you can download the PC36IMG, be sure it's named exactly PC36IMG, put it on the main directory of your sd card (then put the sd card in the phone), and boot to the bootloader (power and volume down). The bootloader should then find the PC36IMG and ask you if you want to update, Select volume up to say yes. Either of those methods should flash you back to stock.
Click to expand...
Click to collapse
Thanks, ran the Original RUU and that got it up and rolling! thanks again! gonna update to the latest RUU next then go from there... What's the best root option Unrevoked???
EDIT: ran the latest RUU, and now on Froyo 2.2
02busa said:
Thanks, ran the Original RUU and that got it up and rolling! thanks again! gonna update to the latest RUU next then go from there... What's the best root option Unrevoked???
EDIT: ran the latest RUU, and now on Froyo 2.2
Click to expand...
Click to collapse
Nice, glad it worked for you. Unrevoked is easy, and has worked fine for me many times. Just uninstall htc sync from your computer, install the hboot drivers, be sure no programs on your computer can try to communicate with your evo, and run unrevoked. That's it. Just read up before diving in.
Edit: Here's a good tutorial on how to properly use Unrevoked. I've seen a bunch of people have problems with it, but I've always followed these instructions, and I've never had trouble on any of the Evo's I've rooted. Just don't use the files linked in that post, as they're most likely out of date. Download Unrevoked and the hboot drivers from the Unrevoked site, in the 'more info' section. Good luck.
instructions:
http://forum.xda-developers.com/showthread.php?t=787304
Download Unrevoked 3.xx
http://unrevoked.com/recovery/
download hboot drivers here
http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Sent from my PC36100 using XDA App
k2buckley said:
Nice, glad it worked for you. Unrevoked is easy, and has worked fine for me many times. Just uninstall htc sync from your computer, install the hboot drivers, be sure no programs on your computer can try to communicate with your evo, and run unrevoked. That's it. Just read up before diving in.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks again for your help! I'm very familiar with Android. But HTC's are just totally different than my Samsung Galaxy so the processes are different. Bought the EVO with the Intent on fixing the boot Issue, and using it as an "Android Alternative" to an iPod Touch/MP3 Player. I don't have service with Sprint either. But I paid $50 for the EVO, and it's specs simply B****slap the iPod's. Gonna Root it, Throw an Otterbox on it, and give Steve Jobs the finger once again!
02busa said:
Thanks again for your help! I'm very familiar with Android. But HTC's are just totally different than my Samsung Galaxy so the processes are different. Bought the EVO with the Intent on fixing the boot Issue, and using it as an "Android Alternative" to an iPod Touch/MP3 Player. I don't have service with Sprint either. But I paid $50 for the EVO, and it's specs simply B****slap the iPod's. Gonna Root it, Throw an Otterbox on it, and give Steve Jobs the finger once again!
Click to expand...
Click to collapse
You're welcome
Haha, nice! Damn, you bought it for $50 dollars [email protected]@>>?? I should try to find an evo that won't boot for 50 bucks and see if I can fix it. You got a good deal on it, is it in otherwise good shape? You can still use it on wifi too, don't forget. And you'll still have a ton more functions to use in addition to Mp3. (video, other cools apps/games, and don't forget, we have FULL HDMI mirroring for the Evo now) Good luck with your Evo, and I edited my previous post with more clear instructions on how to use unrevoked.
And yea, the Samsung Galaxy S is completely different, as far as flashing methods and terminology at least. I was just reading up on rooting and flashing for Fascinate's (to help a friend out), and I felt like a complete noob again. I had to read quite a bit to catch on to things over there. It was a completely different world!
As k2buckley said, always need to keep the radios up to date, but you should be fine now. And though rooting is the same, its different for each device. I'm soon gona root my girl friend's desire, and I had to get all the things now and do my reading so when she comes to visit I know what I'm doing.
k2buckley said:
You're welcome
Haha, nice! Damn, you bought it for $50 dollars [email protected]@>>?? I should try to find an evo that won't boot for 50 bucks and see if I can fix it. You got a good deal on it, is it in otherwise good shape? You can still use it on wifi too, don't forget. And you'll still have a ton more functions to use in addition to Mp3. (video, other cools apps/games, and don't forget, we have FULL HDMI mirroring for the Evo now) Good luck with your Evo, and I edited my previous post with more clear instructions on how to use unrevoked.
And yea, the Samsung Galaxy S is completely different, as far as flashing methods and terminology at least. I was just reading up on rooting and flashing for Fascinate's (to help a friend out), and I felt like a complete noob again. I had to read quite a bit to catch on to things over there. It was a completely different world!
Click to expand...
Click to collapse
Yeah, I've gotta replace the digitizer.. Ordered one already. Got an Otterbox Commuter on the way also.. I'll have roughly $100 in it, and it kicks the $hit outta any iPod or iPhone out there...
Yeah, The Galaxy S line of phones is waaaaaaaaaaaaaaaaay more of a pain in the ass considering every variant has a different firmware version. Thinking i'm gonna jump to GSM soon and pop my sim card in whatever phone i wanna use that day.. lol. I like the specs of the Galaxy S II http://galaxys2.samsungmobile.com/html/specification.html
Also thanks for the help, it can definately be a pain jumping from dealing with one phone to the other.. especially at 2a.m. things start to run together.. lol
teh roxxorz said:
As k2buckley said, always need to keep the radios up to date, but you should be fine now. And though rooting is the same, its different for each device. I'm soon gona root my girl friend's desire, and I had to get all the things now and do my reading so when she comes to visit I know what I'm doing.
Click to expand...
Click to collapse
Yeah can definately be annoying jumping between phones...
I know theres probably a thousand topics on this but none of them seem to have the same exact problem or they do and dont have a solution. I can boot my ROM and i cant boot recovery. the only thing i can get to is HBOOT. I have tried many of the PB31IMG.zip files but none of them work. i have also tried the RUU exe program but that did not work either. im kinda graspin at straws here cuz i dont have a phone right now. im also wondering if i should just take it to verizon, but with that im worried about them finding out its rooted, because it still says "S-off" on the HBOOT menu. Any suggestions on what to do?
To my knowledge if you are in a bootloop with no secondary recovery such as Amon-Ra or CWR, the only other option is the RUU downgrade your Inc through the Android HBOOT Recovery. Use these guides here:
http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
gdaysoccer said:
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
Click to expand...
Click to collapse
For whatever it's worth, my phone was s-off when I took it in to Verizon. (I was having the vibrations-of-death)
They saw the phone wasn't booting up, and even saw my unrevoked splash screen, and that was good enough for them to send me a new phone.
Honestly, I don't think a majority of those sales reps would even know how to get into hboot, and really don't know a whole lot about Android. I'm not saying it'd be impossible to get someone that lurks XDA in their spare time, but... it's unlikely.
And if they did lurk xda they probably wouldn't make an issue of you being rooted
Sent from my ADR6300 using XDA App
I actually just had the same issue as you and spent around 21 hours trying to get things fixed with a few devs and we had no luck. basically the phone would act as if it would take the ruu flash and claim it did and update the hboot like it did but made no change in order to complete a boot cycle. I had no recovery no rom just hboot and fastboot worked. every other option failed. we chalked this up to a hardware failure of some sort. I flashed the lastest Ruu and called *611 explained the problem and they overnighted me a new inc. I still have S-off on the phone but every other item radio/hboot/kernal is all stock. I doubht they wil lreally notice the S-off. all in all the phone is back to stock full wipe. Good luck.
I ended up taking it to the Verizon store today and the rep thought it might have been the battery so he tried a new one of those, but that wasnt the issue. I'm pretty sure he booted into HBOOT because he was playing around with the power and volume buttons, but he didnt ask me anything about it being s-off or rooted or anything and so theyre sending me a new phone, because unluckily they didnt have any in stock at the store i went to, and i have to send this one back. So, so far, it looks like no one really cares or even knows where to check for it being rooted.
Well i've been working for the past 9 hours trying ever possible thing i could find trying to fix my issue without any progress. How do i get back to stock so i can start over?!
Supersonic EVT1 ENG s-off
hboot-2.10.0001 (pc36*****)
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.05.02
mar 30 2010, 11:24:04
I was rooted with unrevoked after reverting back from the newest OTA using a guide from the XDA forums. everything was working wonderfully but my dumbass had to try and downgrade to an ancient ENG Hboot. using thefredelement's guide to get back to ENG .76. NOT NOTICING i shouldn't try it with HW version 003/004. unfortunately my phone is HW 003. idk what i need to do to get this fixed or if i bricked my phone. I've got a warranty still so i can always just report it lost pay the 50 and restore from my backup sd card.
anyways, my computer is able to see my phone with fastboot but not adb. i get errors when trying to flash new recoveries or anything but radios (such as fail PU, image update error, data length too large, etc) Trying to do anything with adb shell just says "device not found" (yes, i have the correct drivers installed) I CANNOT get into recovery (i had CWM 5.0.2.2) it just reboots back to hboot or the screen with the three droids skateboarding when i try. sorry ahead of time if this is posted in the wrong section/i just killed some brain cells with my stupidity and lack of experience. thanks in advance for any help and advice i can get! (sorry for the double post, idk how to delete postings)
Xexus said:
Well i've been working for the past 9 hours trying ever possible thing i could find trying to fix my issue without any progress. How do i get back to stock so i can start over?!
Supersonic EVT1 ENG s-off
hboot-2.10.0001 (pc36*****)
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.05.02
mar 30 2010, 11:24:04
I was rooted with unrevoked after reverting back from the newest OTA using a guide from the XDA forums. everything was working wonderfully but my dumbass had to try and downgrade to an ancient ENG Hboot. using thefredelement's guide to get back to ENG .76. NOT NOTICING i shouldn't try it with HW version 003/004. unfortunately my phone is HW 003. idk what i need to do to get this fixed or if i bricked my phone. I've got a warranty still so i can always just report it lost pay the 50 and restore from my backup sd card.
anyways, my computer is able to see my phone with fastboot but not adb. i get errors when trying to flash new recoveries or anything but radios (such as fail PU, image update error, data length too large, etc) Trying to do anything with adb shell just says "device not found" (yes, i have the correct drivers installed) I CANNOT get into recovery (i had CWM 5.0.2.2) it just reboots back to hboot or the screen with the three droids skateboarding when i try. sorry ahead of time if this is posted in the wrong section/i just killed some brain cells with my stupidity and lack of experience. thanks in advance for any help and advice i can get! (sorry for the double post, idk how to delete postings)
Click to expand...
Click to collapse
Remain calm. Let's see if we can get you fully functional.
First, let's upgrade that HBOOT. That by itself might fix you up, if it'll flash through the bootloader. Try the PC36IMG.zip attached to this post. It's for HBOOT 2.15.
If it flashes successfully, it should reboot the bootloader for you. If it doesn't, choose the fastboot option that does, and when it comes back up, try getting into recovery. If you can get into recovery, the next thing you should do is retire CWM and flash RA-supersonic.
thx capt. I actually just filed a clain through asurion, and for my $100 deductible i've getting a brand new evo3d xD so jumping the gun for the replacement actually worked out for me this time!
Xexus said:
thx capt. I actually just filed a clain through asurion, and for my $100 deductible i've getting a brand new evo3d xD so jumping the gun for the replacement actually worked out for me this time!
Click to expand...
Click to collapse
A shame to send back a perfectly fine OG . But I'm glad it worked out for you. Personally I like the challenge of trying to rescue a soft-bricked device. But I guess we'll never know if it was possible, now . . .
i would have loved to have found out myself. but being on probation and in the process of finding a job I just didnt have the time to mess with it i've still got it so once i get some time i'm going to attempt to unbrick it still. although its useless now that it's been deactivated lol
Let me explain:
I use i9300, and I'm completely unfamiliar with HTC environment and treating. My girlfriend's Desire Z froze recently. I rebooted it, and it didnt go through bootloader.
It did it once, but it was the only time. Then i turned it off to put in the simcard. It didnt come back. Still stuck on the HTC logo. Before, it was going to the HTC quietly brilliant, but now it's just freezing on HTC.
Everything is stock. Phone has never been rooted. I decided, to go through the hboot (correct me if im wrong) and try to do something there.
When I hit factory reset, phone freezes on that menu. I decided to go around that by rooting it, or reinstalling software from that recovery menu, or through usb, or memory card. Well, anything that might make it work.
I tried to find a proper help for that. Unfortunately, I found some threat here, but it had a link on the top saying "go to actual method", it took me to another threat, which had a link to another "actual method". There, i was given three different techniques vision, one for temp, one for perm root, s-off, SDK, ADB and all this freakin stuff. I DONT GET IT!
Please, provide me with step by step instruction (links, whatever) so I can fix this bloody phone. I dont know what is the difference between temporary and permanent root, what is s-off, and what to download from where to make it freaking work.
I'm struggling with this 3rd day now, trying to understand what is all of this instructions. I still cant tell if it's a software, or hardware problem, because i cant diagnose it! I cant spend another day on educating myself about htc rooting.
Please, provide me with some tips on how to fix it, or instructions to perform the system factory reset from hboot menu.
Let me give you the details i get in that menu:
VISION PVT SHIP S-ON
HBOOT- 0.85.0013
MICROP-0425
RADIO- 26.10.04.03_M
eMMC-boot
Apr 11 2011, 23:26:27
It looks bad, like a fried emmc. Not being rooted limits your chances of fixing as well as your chances of even confirming the failure
http://forum.xda-developers.com/showthread.php?p=35236029
read through this a bit and see if it helps any, your best chance is to attempt an ruu but if it is a bad chip then there is noting you can do other then warranty exchange or get a new phone
Sent from my Nexus 7 using xda premium