I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
LaloHigh said:
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
Click to expand...
Click to collapse
What do you mean record what software I started with? I had 2.02, now have 0.76 (But my screen says 2.10). I've tried both the exe and the PC36IMG.zip that you've linked.
Using .exe gives me a Error 170 (Not recognizing my phone is plugged in)
Putting PC36IMG.zip on sd and using hboot gives me Failed-PU, Partition Update Fail! for every category but Radio_V2. BTW I'm supposed to use the first two files from that link
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Greenfieldan said:
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
Click to expand...
Click to collapse
Well what I did was messup the way it sees my partition. I have a nwer partition scheme i believe but the 0.76 software thinks I have the older partition settup.
If you mean unroot method from this post http://forum.xda-developers.com/showthread.php?t=829045 the one I rooted with then I can't do it cause I have no recovery. I can't get to it cause bad partition settup.
I know I can run fastboot erase commands, do you guys think I should run
Code:
fastboot erase boot
to create an unbootable system. One that doesn't even have the screen turn on?
*Which if any partition can I delete in order to never have the phone even turn the screen on?
Here's the choices (wimax, misc, recovery, boot, system, cache, userdata)
if your getting error 170, the RUU can't communicate with the phone.\
Can you get Hboot USb on? IF so, the RUU may run with it.
Drivers installed on computer?
Otherwise, you mave have blown out USB port, like I did.
Try putting the RUU, rom.zip (rename rom.zip to PC36IMG.zip) to your sd card, and see if that saves your a$$.
If that don't work, better run it over with a car or something and take it back.
The good news is you are still in your 30 day warranty. The solution I would suggest is try to flash the bootloader back to hboot 2.10. I would find a pc36 with 2.10 and flash away. Maybe even fastboot erase every partition except boot and hboot first. Don't do radio or wimax either or it will brick your radio and wimax. Then flash a full pc36. Other than that, manually brick. I would erase hboot and boot to brick.
Good luck
If you erase boot.img, it will still go to hboot. Erase the touchpanel image. That way they cant see it. By the time your phone gets to its repair destination, "they" wont be looking for that type of thing. They will just repartition. Also, it wont let you erase hboot
What error are you seeing when you select recovery from the bootloader menu?
The RUU that you tried, what version was it? You MUST use the 3.70.651.1 RUU because your phone thinks you are on hboot 2.10. Do not try an older RUU.
--------------------------------
Try the following
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
4) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
-----------------------------------------------
If that does not work then try the following:
1) Download the img file for the modified Amon_Ra Recovery
2) Put evo-test.img on the root of your sdcard
3) Put the phone in fastboot mode
4) fastboot boot evo-test.img
5) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
josh4trunks said:
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
Click to expand...
Click to collapse
But if you can't flash a RUU.exe, then you can probably flash a zip file of a ROM.
This can or be or is not correct, I am just curious how this well happened to you.
nope tried flashing ROM through hboot, fastboot... Tried 'fastboot erase boot' didn't do anything. I'm gonna update the OP on the current situation, giving up...
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
i think he said multiple times that he was totally screwed and his partitions were messed up so he either needs a total memory reflash or god's private java code
illogos said:
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
Click to expand...
Click to collapse
Can't flash through bootloader. Get Fail-PU
Which is a Partition Update Error
Ok so here's the deal I have been working on this STUPID Incredible for a buddy of mine for like the last 4 hours trying to fix his boot loop issue. I have scoured the internet looking for a way to fix this problem and downloaded countless *.img and *.zip files and who knows what else...
[EDIT] Also if I reboot to bootloader (either through adb fastboot or through the phone (VOL (-) + POWER) adb can't find the phone I can only access the phone when it's actually trying to boot up
[THE ISSUE]
The phone boots up shows the white htc incredible screen than proceeds to boot into cyanogenmod 7.blah.blah.blah (don't know the exact version it's from a couple months ago) and than just continuously shows the skateboard dude and doesn't proceed past that point.
When I reboot the phone and load up the bootloader it runs fine and than when I try to do the recovery option it will vibrate for a second show the htc incredible screen and than show the fastboot usb options (bootloader, reboot, reboot bootloader, power down) and if I select reboot it just reboots to the same problem.
If I choose Factory Reset it goes to the fastboot usb menu but I can't choose any of the options and it just sits there, I actually have to do a battery pull in order to do anything.
I know that clockword mod was installed on this phone but I can't access it by any means.
I hooked the phone up to my computer and loaded up adb (which is installed correctly as I've used it on my phone and the htc drivers are installed correctly) if I try to access my internal sd card through an adb shell it doesn't list anything and I have root in the shell (#) and if I try to cd to sd-ext it says "can't cd to sd-ext) so I can put something on the cards and load them up (as far as I know) to get the recovery working or anything...
adb does see the phone sees the files on the phone I can do a adb reboot it and that works fine.
Here's some info from the bootloader:
incrediblec xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.15.00.07.28
Jul 23 2010, 18:06:51
Ok so that got longer than I thought it would be (whoops) I hope I explained this well enough for everyone and didn't make it to confusing. I don't care if I have to go back to stock or what I just need to get this phone up and running again...
Thanks for reading this horribly long thread and for any feedback you have!
Sounds like something is borked with your install, and your recovery has vamooshed. Yes, those are the technical terms for it. Try an RUU.
http://pvillecomp.com/?page_id=22
That will give you stock everything, including recovery, you just have to flash CWM, then in CWM wipe everything (wipe data/factory reset, wipe boot, wipe system), then flash a ROM.
Edit: try Pons' method first.
First, the phone isn't stupid...it's Incredible. I mean seriously /s
Can you reformat the sd card, download CWM to the root of your sd card, then install CWM through hboot that way?
CWM is available from pvillecomp.com, download the file under the heading "Recoveries" and rename it to: PB31IMG.zip
Couple questions:
What started the bootloop issue? What steps have you taken to try resolving this issue?
G33kman said:
Ok so here's the deal I have been working on this STUPID Incredible for a buddy of mine for like the last 4 hours trying to fix his boot loop issue. I have scoured the internet looking for a way to fix this problem and downloaded countless *.img and *.zip files and who knows what else...
[EDIT] Also if I reboot to bootloader (either through adb fastboot or through the phone (VOL (-) + POWER) adb can't find the phone I can only access the phone when it's actually trying to boot up
[THE ISSUE]
The phone boots up shows the white htc incredible screen than proceeds to boot into cyanogenmod 7.blah.blah.blah (don't know the exact version it's from a couple months ago) and than just continuously shows the skateboard dude and doesn't proceed past that point.
When I reboot the phone and load up the bootloader it runs fine and than when I try to do the recovery option it will vibrate for a second show the htc incredible screen and than show the fastboot usb options (bootloader, reboot, reboot bootloader, power down) and if I select reboot it just reboots to the same problem.
If I choose Factory Reset it goes to the fastboot usb menu but I can't choose any of the options and it just sits there, I actually have to do a battery pull in order to do anything.
I know that clockword mod was installed on this phone but I can't access it by any means.
I hooked the phone up to my computer and loaded up adb (which is installed correctly as I've used it on my phone and the htc drivers are installed correctly) if I try to access my internal sd card through an adb shell it doesn't list anything and I have root in the shell (#) and if I try to cd to sd-ext it says "can't cd to sd-ext) so I can put something on the cards and load them up (as far as I know) to get the recovery working or anything...
adb does see the phone sees the files on the phone I can do a adb reboot it and that works fine.
Here's some info from the bootloader:
incrediblec xc ship s-off
hboot-0.92.0000
microp-0417
touch panel-atmel224_16ab
radio-2.15.00.07.28
Jul 23 2010, 18:06:51
Ok so that got longer than I thought it would be (whoops) I hope I explained this well enough for everyone and didn't make it to confusing. I don't care if I have to go back to stock or what I just need to get this phone up and running again...
Thanks for reading this horribly long thread and for any feedback you have!
Click to expand...
Click to collapse
Have you tried to reflash cwm recovery thru hboot? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip Then ser if you can access it. If you can wipe everything and flash a rom of your choosing. If that dosent work try an ruu thru hboot. http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip
WIN!
cmlusco said:
Have you tried to reflash cwm recovery thru hboot? Then ser if you can access it. If you can wipe everything and flash a rom of your choosing. If that dosent work try an ruu thru hboot.
Click to expand...
Click to collapse
Oh man thanks guys for the feedback I thought it would be something easy enough. I officially have cwm recovery working and am currently install cyanogenmod 9 as we speak! You guys are lifesavers seriously thank you!
CWM Boot Loop - Unable to access via Odin/ADB
I have the boot loader problem too... Last night, for no apparent reason, my phone turned off and didn't want to come back on again. I didn't change anything, plug it into anything, or do anything fancy, it just turned itself off and now it's stuck in a boot loop.
It boots into download mode okay, but I can't get it into recovery.
Win here too!
i bricked my phone running cm7 also and had the exact same problems right down to the T. ...SO!, that program that i installed on my computer took complete control of the phone and reset the rom. this is a wonderful piece of software. if you have an incredible download this program and dont worry about bricking your phone again.
how to obtain s-on now?
After I used the program from the website in the previous post, it brought me back to stock Rom and everything. Now it's still s-off, but I can't get into cwm, just hboot. My main goal is just to get this back to stock (unrooted and s-on). Can someone please explain how I go about doing this? I can get.any info needed ie. Radio etc.
Problem right now is in order to get into the phone I have to do the entire setup which includes activating it,which I cannot do.
Thank you guys much for this useful info.
brandonb0013 said:
After I used the program from the website in the previous post, it brought me back to stock Rom and everything. Now it's still s-off, but I can't get into cwm, just hboot. My main goal is just to get this back to stock (unrooted and s-on). Can someone please explain how I go about doing this? I can get.any info needed ie. Radio etc.
Problem right now is in order to get into the phone I have to do the entire setup which includes activating it,which I cannot do.
Thank you guys much for this useful info.
Click to expand...
Click to collapse
Why do you want it unrooted and s-on? All you need to do is flash cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot. From there you can flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip and be rooted if so desired. If you really want s-on and stock you need to flash cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, flash the 2.15.00.07.28 radio http://dinc.does-it.net/Radios/2.15.00.07.28/PB31IMG.zip thru hboot, and then flash the unrevoked s-on patch http://dinc.does-it.net/Unrevoked/unrevoked-forever-son.zip thru recovery. Once s-on flash a official ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip thru hboot and you will be stock s-on. Also if you want to bypass the activation just cancel it 3 or 4 times and it will let you skip it.
cmlusco said:
Also if you want to bypass the activation just cancel it 3 or 4 times and it will let you skip it.
Click to expand...
Click to collapse
Tapping each corner going clockwise, starting in the top left, is an easier way to skip the setup.
thanks
Thanks guys. I ended up calling customer service and they got me past the activate screen. From there I re rooted the phone so I could use cwm recovery again and flash s-on then unrooted it and all is good now. Thanks
First of all, I gotta give props to Albinoman for getting the Incredible to where he has (Jellybean, on the Incredible!... wow!)
http://forum.xda-developers.com/showthread.php?t=1778190
I've been following Albinoman's progress and while I was trying to troubleshoot the "low space notification" we're all too familiar with, I made a HUGE mistake.... I was using Albinoman's Beta 2, which worked great, but I tried restoring a nandroid backup and it failed, due to a corrupt SD card. Then, I tried restoring to another backup, which also failed. I then set out to run a scandisk on the SD card, so I shut off my phone thinking I could just boot back into recovery no problem right?!? WRONG!
After fixing the SD card, I was unable to even boot into recovery, I was getting the scary 5 vibrates of death, and I found this thread, which was half-helpful:
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/showthread.php?t=1110865
It was able to get my SD card working (previously it didn't at all), but I still cannot boot without having a USB cable plugged in (otherwise I get the 5 vibrates and a blank screen).
The thread suggested using z4root to gain temporary root but when I try that, it just sits there for a very long time and times out.
Here's where my biggest problems come in...
I'm currently running Gingerbread 2.3.4, S-ON, and ADB is BROKEN on my phone
My HBoot is version 1.07.0000 (I was 0.92.0000, but now I flashed cmlusco's newer HTC rom, so it changed)
What I currently have to work with (what works):
Wifi, SD Card (new one of course), 3G, and I'm able to boot, and I got my bootloader unlocked!
I cannot find any way to root my phone based on my current situation.
I have found plenty of ways to root (I'm used unrevoked plenty of times but it wont help me now because ADB wont work with my phone because it's broken, but I can't fix ADB, because I can't get root, it's really a sad situation)
I've tried HTC's RUU official root method, other RUU's, and Unrevoked, but they all don't work because my ADB is messed up
Also, I don't know if this helps, I can use fastboot, and I was able to flash an image using fastboot commands, but it's been awhile since I've tried that, and I don't know of anything I can flash via fastboot to help my situation.
My main goal is, I just need to get rooted again so that I can re-flash Albinoman's sweet Beta 3 ROM which I've been unable to even try
Thanks for the help you guys are amazing!
UPDATE: It's FIXED!!!! Here's the short version of how (in case it happens to anyone else)
To start, my phone A: Would not boot B: Would not read the SD card, or EMMC, EVEN in recovery C: all USB was broken including ADB (but fastboot worked) and D: I managed to lose root by flashing like mad in hopes of fixing AB and C
Step 1: I flashed cmlusco's ROM that he suggested which got my hboot up to date etc...
Step 2: I went to http://htcdev.com/bootloader/ and unlocked my bootloader (BUT I skipped straight to step 8 (the fastboot part, since everything before that was a waste of my time since my USB/ADB was hosed))
Step 3: I flashed this recovery image and ran "fastboot flash recovery recovery.img"
Step 4: I downloaded superuser and loaded it through recovery, now that my SD card worked
Step 5: I then was able to do the following in order to fix the USB/ADB problem:
using this file and this file and running them in an android emulator app I downloaded from google play (since my USB was broken)
Terminal emulator & ADB commands:
Code:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd-eng.img > /data/mtd-eng.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd-eng.img
reboot
(credits for this to this thread)
Step 6: I was now fixed, so I just wiped my phone and flashed Albinoman's Jellybean ROM because it rocks!
Thanks to tiny4579 and cmlusco for both of your help!
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
meadowsjared said:
First of all, I gotta give props to Albinoman for getting the Incredible to where he has (Jellybean, on the Incredible!... wow!)
http://forum.xda-developers.com/showthread.php?t=1778190
I've been following Albinoman's progress and while I was trying to troubleshoot the "low space notification" we're all too familiar with, I made a HUGE mistake.... I was using Albinoman's Beta 2, which worked great, but I tried restoring a nandroid backup and it failed, due to a corrupt SD card. Then, I tried restoring to another backup, which also failed. I then set out to run a scandisk on the SD card, so I shut off my phone thinking I could just boot back into recovery no problem right?!? WRONG!
After fixing the SD card, I was unable to even boot into recovery, I was getting the scary 5 vibrates of death, and I found this thread, which was half-helpful:
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/showthread.php?t=1110865
It was able to get my SD card working (previously it didn't at all), but I still cannot boot without having a USB cable plugged in (otherwise I get the 5 vibrates and a blank screen).
The thread suggested using z4root to gain temporary root but when I try that, it just sits there for a very long time and times out.
Here's where my biggest problems come in...
I'm currently running Gingerbread 2.3.4, S-ON, and ADB is BROKEN on my phone
What I currently have to work with (what works):
Wifi, SD Card (new one of course), 3G, and I'm able to boot
I cannot find any way to root my phone based on my current situation.
I have found plenty of ways to root (I'm used unrevoked plenty of times but it wont help me now because ADB wont work with my phone because it's broken, but I can't fix ADB, because I can't get root, it's really a sad situation)
I've tried HTC's RUU official root method, other RUU's, and Unrevoked, but they all don't work because my ADB is messed up
Also, I don't know if this helps, I can use fastboot, and I was able to flash an image using fastboot commands, but it's been awhile since I've tried that, and I don't know of anything I can flash via fastboot to help my situation.
My main goal is, I just need to get rooted again so that I can re-flash Albinoman's sweet Beta 3 ROM which I've been unable to even try
Any help anybody could offer me would be GREAT! Thanks XDA, you guys are amazing!
Click to expand...
Click to collapse
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
tiny4579 said:
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
Click to expand...
Click to collapse
1st of all, thanks for getting back to me so quickly Tiny, you're amazing, and I appreciate all the work you've done with the Dinc, thanks for being so active!
1. No, mass storage doesn't work (I assume you mean plugging in the phone and having it mount the SD card as a drive on the computer)
However, I am able to now use both my SD card from within Gingerbread, and the recovery, but only after doing the "fastboot oem enableqxdm 0" trick
2. I haven't tried uninstalling and reinstalling the ADB drivers, but only because.... I'm a developer, and sometimes I develop on my home computer, and sometimes I develop at work, and they both exhibit the same behavior, so I don't think it can be that both computers, just happened to get messed up at the exact same time, right when my phone got hosed?
Also, I've used ADB plenty in the past, on both computers, so I'm certain they're set up right, just between having two computers to work with, AND the extensive use I've made of ADB in the past (I'm the office Root-er, I've rooted most of my co-worker's phone for them, so I've had quite a bit of experience (and should have known better than to turn off my phone when I did which got me in this pickle ))
Just to be clear though, basic USB communication works, but only in HBOOT, NOT from Gingerbread, actually, having the phone plugged into USB (whether or not USB debugging is turned on on the phone), WILL lock up my computer until I unplug it, and as soon as I unplug, my computer snaps back to normal So I think somehow something in the phone got hosed so the ADB is broken, however, I can't fix it because I can't get my root back because I'm stuck in the horrible stock gingerbread (no offense to anyone that likes it )
Also, yes, I've tried a ton of times to flash a superuser zip to root and it says it's not allowed/bad signature or whatever, because it's still S-ON
cmlusco said:
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
Click to expand...
Click to collapse
@cmlusco
I didn't even know you could use RUU's through hboot, I'll try that, as well as using the HTC unlocker RUU with hboot.
I'd already tried those things normally, but with by USB being hosed, it didn't help much. :-\
I'll post back when I've given them a try
cmlusco said:
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
Click to expand...
Click to collapse
I'm on HBoot 0.92.0000
and it seems to only allow me to flash newer, or the same version as what I've got (because I've tried downgrading)
I just tried the RUU from HTC to root my phone.
I ran the RUU, put the phone in hboot, and it sat and said "verifying phone information" or something like that and said "error 170, usb connection error"
I also put the phone in "fastboot" and tried again, it didn't seem to make a difference.
Now regarding flashing an RUU through hboot, how would I go about doing that? I'm assuming you're talking about throwing the PB31IMG.zip on my SD and booting into Hboot. Now that DOES work however, I'm still S-ON, so unless it's a factory image, it ain't gonna like it
That is, unless there's some kind of fastboot voodoo that can be done to get something on there to exploit it and get my back my root I once had and loved!
meadowsjared said:
I'm on HBoot 0.92.0000
and it seems to only allow me to flash newer, or the same version as what I've got (because I've tried downgrading)
I just tried the RUU from HTC to root my phone.
I ran the RUU, put the phone in hboot, and it sat and said "verifying phone information" or something like that and said "error 170, usb connection error"
I also put the phone in "fastboot" and tried again, it didn't seem to make a difference.
Now regarding flashing an RUU through hboot, how would I go about doing that? I'm assuming you're talking about throwing the PB31IMG.zip on my SD and booting into Hboot. Now that DOES work however, I'm still S-ON, so unless it's a factory image, it ain't gonna like it
That is, unless there's some kind of fastboot voodoo that can be done to get something on there to exploit it and get my back my root I once had and loved!
Click to expand...
Click to collapse
That PB31IMG.zip i posted is 4.08.605.15, the latest android version for our phone. It is official and signed by htc, so it should flash even if your s-on. Just place it on your sd in no folders and hboot should find it.
cmlusco said:
That PB31IMG.zip i posted is 4.08.605.15, the latest android version for our phone. It is official and signed by htc, so it should flash even if your s-on. Just place it on your sd in no folders and hboot should find it.
Click to expand...
Click to collapse
Yes, you're right, I was able to flash that image using hboot, but sadly... the adb is STILL broken and doing all the same things it was before (it doesn't work, and when I plug it into my computer, it freaks out my computer and the computer freezes until I unplug the phone, then everything is fine again)
It seems that all these images write everything to the phone... BUT what I need. I've found some things that "should" fix my problem, but they are all unsigned, and therefore they require root. Is there a chance that now with this newest RUU you gave me "z4root" will work cmlusco? (the reason I ask is, I'm hoping that an app that roots the phone without the computer will work, since every time I plug into a computer, it doesn't work, and just freaks out the computer)
Also, regarding the official HTC way to root, I tried running their "PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe" file, however, that didn't work in the slightest (because it uses adb commands to talk to the phone). Is it possible that there's a way to extract the PB31IMG.zip file from that exe file and therefore I would be able to flash that using hboot, and the phone would like it because it's signed by HTC (I'm assuming)?
By the way, ever since I flashed that newer PB31IMG.zip ROM, now when I go into hboot, at the top it says "*** LOCKED ***", and it never said that before, I don't know if that matters at all? :-\
Also, if it helps any, here's what the update looked like....
*** LOCKED ***
INCREDIBLE XC SHIP S-ON
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.12.20
Apr 24 2012,22:58:40
HBOOT
Parsing... [SD ZIP]
[1] RADIO_V2 - OK
[2] BOOT - OK
[3] RECOVERY - OK
[4] SYSTEM - OK
[5] SPLASH1 - OK
Update Complete...
Then, after running the update, it asked me if I wanted to reboot, it showed the picture of the phone with the arrows in a circle around it, then when it wen to reboot, it did the usual (for me lately), and gave me the 5-vibrates of death and a black screen, the only way to get out of it is to do a battery pull. Then, after doing that, if I just plug in the cable, I can boot into the new rom just fine, but if the cable isn't plugged in, I just get the 5 vibrates of death, like this guy....
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/show....php?t=1110865
But sadly, in order to completely fix myself, I need root, and I can't seem to even get temporary root? :-\
I'm hoping maybe something there might help y'all to help me? :-\
tiny4579 said:
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
Click to expand...
Click to collapse
@tiny4579
To be more clear, the basic USB communication doesn't work, the only way I can get anything that uses USB to work, is by booting into fastboot, and I have been able to do fastboot commands (like "fastboot oem enableqxdm 0"). So it seems that fastboot's USB works just fine (I've tested this on multiple computers), but anything after that, like trying to use the USB from the operating system, is totally broken. So I'm guessing that internally, the phone's drivers for USB are separate for hboot, and therefore still work, however, the phone's USB drivers for Gingerbread, are completely broken, even though I've been able to flash 2 different versions of signed gingerbread from HTC, they still don't seem to fix my USB problem even though it's writing the entire system all over again. Is it possible that there's a signed HTC zip that will fix my USB, that would fix me... the only question is.... does a signed HTC zip exist that will fix my USB??? :-\
Ok, I've got great news, I was able to finally unlock my bootloader! so now when I go into HBOOT, it says at the top "UNLOCKED", however, it still says S-ON, and I still don't have root, but I think we're getting there!
So now that my bootloader is unlocked, I'm assuming I should be able to either load a custom recovery (like clockworkmod), however, I still can't use ADB to do anything so things like unrevoked wont work for me sadly
Do you guys have any advice on what I can now do that my bootloader is unlocked? (I'm a little unclear about what the whole bootloader thing does for me). I think I understand rooting, at least enough, and I thought I understood the bootloader, and the unlocking. But now that my bootloader is unlocked, it still wont let me load anything like CM7.1, or clockworkmod (I tried both of those by going into recovery and trying to flash the update.zip).
Either way, I'm very encouraged by the fact that my bootloader is unlocked, I'm assuming it should help me to acheive my goal of rooting and eventually gettting Albioman's Jellybean on there?
meadowsjared said:
Ok, I've got great news, I was able to finally unlock my bootloader! so now when I go into HBOOT, it says at the top "UNLOCKED", however, it still says S-ON, and I still don't have root, but I think we're getting there!
So now that my bootloader is unlocked, I'm assuming I should be able to either load a custom recovery (like clockworkmod), however, I still can't use ADB to do anything so things like unrevoked wont work for me sadly
Do you guys have any advice on what I can now do that my bootloader is unlocked? (I'm a little unclear about what the whole bootloader thing does for me). I think I understand rooting, at least enough, and I thought I understood the bootloader, and the unlocking. But now that my bootloader is unlocked, it still wont let me load anything like CM7.1, or clockworkmod (I tried both of those by going into recovery and trying to flash the update.zip).
Either way, I'm very encouraged by the fact that my bootloader is unlocked, I'm assuming it should help me to acheive my goal of rooting and eventually gettting Albioman's Jellybean on there?
Click to expand...
Click to collapse
Now you need to fastboot flash cwm. Download this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, and place it on your pc in the same folder as the fastboot.exe file.
Open a cmd prompt on your pc to where fastboot.exe and recovery.img are. Type the folowing:
Code:
fastboot flash recovery recovery.img
If you get no errors, go to the maim hboot menu and select recovery. You should now be in cwm recovery.
Download superuser http://dinc.does-it.net/Superuser/SuperUser_3.0.7.zip, and place it on your sdcard by going to mounts and storrage and selecting mount usb storrage. If it freezes up the phone or the pc, you will need to take the sd out and use a card reader to put it on the sd with a pc.
Then flash it thru recovery like you would a rom. Now you will be rooted. Then flash a rom of your choosing and hope it boots.
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
tiny4579 said:
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
Click to expand...
Click to collapse
Yeah i guess it is pointless to flash su, then wipe it, then flash a rooted rom.
Thank you both of you, you were a HUGE HELP!!!!! I'm FIIIIIIXED!!!!!!!!!!!!!!
I'm going to update the original post to detail how I got fixed (the short version is, I just did what cmlusco said, and as soon as I had root, I followed this and it worked!!!!)
tiny4579 said:
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
Click to expand...
Click to collapse
I wound up loading superuser like cmlusco suggested, only because I wanted to have everything fixed and perfect before loading Albinoman's new ROM, just in case there were issues, that way I'd know that it was the ROM or my phone, especially since my SD Card freaked out on me and that's how I got into this mess
....But, you are right, the only problem is, I'm super paranoid, and I like to be super-thorough
meadowsjared said:
I wound up loading superuser like cmlusco suggested, only because I wanted to have everything fixed and perfect before loading Albinoman's new ROM, just in case there were issues, that way I'd know that it was the ROM or my phone, especially since my SD Card freaked out on me and that's how I got into this mess
....But, you are right, the only problem is, I'm super paranoid, and I like to be super-thorough
Click to expand...
Click to collapse
Glad its working for you.
Sent from my Galaxy Nexus using Tapatalk 2