Related
My phone is working right now.
I read tons of forums and info about rooting - doesn't mean I know much about it.
If it helps in your replies, please note I am a linux expert and I don't need help understanding file systems, files, busybox commands, etc.
I followed jonsuh dot com's guide entitled /2010/11/ "root-your-droid-incredible-how-to" [I've heard I can't leave links, hence I obfuscated it]
phone is new, nothing installed (well actually, just ConnectBot for ssh, and the verizon&htc bloatware)
specs
htc incredible with SLCD
hboot 0.92.0000
radio 2.15.00.07.28
installed the modified android usb driver for my windows 7 32bit machine
started the reflash_package.exe from unrevoked
selected the cwm slcd recovery image
set my phone to usb debug
plugged in phone to pc
clicked ok in unrevoked to begin flash
6 minutes pass with reboots
hboot shows S-OFF and cwm boot
phone starts up, applications show superuser permission
ok fun, everything i read says to make backups before i do anything. note that all i want to do is remove the bloatware, that's the only reason i'm here!
so, i install rom manager from the market
i allow unknown sources at this point
i try to choose "Backup Current ROM" - error message says I need cwm recovery
so, first option in rom mgr, "Flash ClockworkMod Recovery", i select that one
I give it root access
Next, I select "Backup Current ROM"
phone reboots, screen bricked (black with white bars)
I freak out here ... bad (swore a couple times, not my style)
So, I go to hboot (cwm), select recovery, screen goes white with black lines on side and one at the bottom...I let it sit for 10 minutes
Pull battery
Reboot, phone works again
This time I return to ROM Manager, ROM Manager now things cwm recovery is installed
I select "Backup Current ROM"
Phone reboots
screen black with white bars on side
I reboot to cwm, select recovery, wait 6 minutes
Pull battery
Reboot, phone works again
And that's where I am right now. I'm not going to even touch ROM Manager until I feel confident I'm not going to jack up the slcd drivers again.
Thanks to everyone in advance!
-Payo
ok have 2 things for you to try
1: make sure you have enough room to create a nandroid backup on your SD, as this has cause problems for people in the past.
2: find amon RA recovery .img in that allows you to flash in h-boot
Being computer savvy like you say i would think you wouldnt pull the battery while its making a back up, i know it feels like its a long time when your screen is black but trust me its doing its thing u just cant see. But above all i honestly reccomend AMON RA recovery for the droid incredible as it fixes the issue with the slcd...hope this helps
http://forum.xda-developers.com/showthread.php?t=758874 heres the link for AMON RA just follow the flashing directions and remeber wont be able to use rom manager with this other than just to simply boot into recovery, but honestly I think rom manager isnt that useful anyway IMO
I'm amazed how much I see this advise I don't remember where I read it but there is a version of cwm that you can use when using unrEVOked, I am running it on my phone as I type this. I don't have it with me atm but ill post it and how to get unrEVOked.to use it.instead of the one it is installing.
putting it back together again
Austin:
I enjoy your jab at me for claiming to be savvy and yet careless for removing the battery during such a critical operation. I knew making such claims would surely invite the least of comments like yours . As you point out, it is difficult to wait patiently in high stress situations.
1. Make sure there is sufficient space on the SD card.
> There is 1.61 GB free of 1.81GB
> The SD is FAT formatted
2. Get AmonRa
> Roger. Download completed.
Should I use unrevoked to 'push' amonra to my phone? Oh, you say that site has flashing instructions. I'll review them.
I now have strong objections to using ROM Manager - I have been burned. So, if you say it is not that useful, well, I'm an easy sell. How do you recommend I create a backup?
jmc:
I used the version of cwm that was specifically built for SLCD screens. It was (to my best guess) ROM Manager's fault (perhaps it ships with a bad cwm that it flashed over my good one). Had I used a bad cwm initially with unrevoked (note, I did not run the default option with unrevoked, but selected a custom recovery image - as per jonsuh's guide that I linked) I would have had a screen-brick from the very beginning.
Austin:
I assumed that my new stock phone would not have HTC Sync (read somewhere to remove it if you've added it, which I haven't), but when I browsed the phone on my pc with a usb link, I saw that the phone's drive has HTC_Sync_2.0.40.exe. I would guess that this exe would be presented to my windows machine if I were to choose 'htc sync' on the phone when connecting (as opposed to charge only or removable drive). Am I wrong? Should I be concerned about this?
So my next step is to start reading about amonra - and then prepare to flash the drive.
Thank you very much,
Payo
yea just download the AMON RA recovery boot into H-BOOT (volume down+power) and it will automatically pick up the file and promt you to update simply click yes and after its done select recovery from H-BOOT menu and boom you will now see AMON RA then procede to complete your nandroid back up
http://www.incredibleforum.com/forum/htc-incredible-hacks/5721-i-rooted-now-i-only-see-black-screen-white-bars-recovery.html
In the crosshairs
"download the AmonR RA recovery boot into H-BOOT"
I think what you're saying is to copy the amonra to the sd card's root dir (named PB31IMG.zip) and allow update, then select recovery. My only concern -- what if something goes wrong? Heh, I just feel there is no safety net. Does a stock version PB31IMG.zip for my incredible+slcd exist out there for download? Or can I always depend on the 'revert to stock' option in h-boot?
"then procede to complete your nandroid back up"
With what tool? How? I've not found anything on this that makes sense to me.
Appreciated
-Payo
Yea creating a nandroid back up is an option within the custom recovery read up a little bit more so you understand vital parts or gaining root and flashing custom roms I suggest you scour the wiki
Sent from my ADR6300 using XDA App
payonel said:
"download the AmonR RA recovery boot into H-BOOT"
I think what you're saying is to copy the amonra to the sd card's root dir (named PB31IMG.zip) and allow update, then select recovery. My only concern -- what if something goes wrong? Heh, I just feel there is no safety net. Does a stock version PB31IMG.zip for my incredible+slcd exist out there for download? Or can I always depend on the 'revert to stock' option in h-boot?
"then procede to complete your nandroid back up"
With what tool? How? I've not found anything on this that makes sense to me.
Appreciated
-Payo
Click to expand...
Click to collapse
Ok you PM'ed me, so here's what I'll do:
Get fastboot, make sure it is in /yoursdk/tools
- fastboot oem rebootRUU
- fastboot flash recovery recovery-RA-2.0.img
- fastboot reboot
- done
Note that AmonRA and CWM are not compatible.
A side note: Without pointing a finger, I'd still think about whether you really need S-OFF or not, it's ment for developers and people that are ready to brick the phone for the sake of it.
Hope this helps
no s-off needed
1. Why fastboot and not an update drop on the sdcard/PB31IMG.zip? A lot of people opine the update method is preferred.
2. I'm nervous about ruu bc I've not read anything about it (and it takes me hours of reading before I feel safe to procede with these things).
3. In this thread I was pointed to RA 1.8.1, and you suggest 2.0. I saw 2.0 was the latest, but was concerned it was for the HTC GSM Desire only. (according the post I saw about 2.0 by amon_ra himself).
4. I don't care to test roms, only remove bloatware and have su -- I can see why I don't need s-off for this (but unrevoked just seemed the most reliable method at the time). Can I turn s-on without reverting to factory? How would you recommend I do this? [note, i am a developer, but anything to protect me from bricking!]
5. I've installed the CWM recovery...but (oh noob i am) does that mean i'm running cwm? I don't think I am. I don't want a custom mod. Clockwork is the boot level tool, and there is a mod, clockworkmod as well, right? Oof..given how much I've read, I would think this would be clear to me by now.
Again, much thanks to everyone,
Payo
If I am following what you are saying you are seeing the issues with the cwm that is suppose to work with SLCD screens then thats odd, I havent had any issues with it, besides rom manager not being able to reboot into recovery 9dont know if thats the recovery's fault though.) Just in case you havent tried it try this one though, its the one I was talking about.
For any future browsers, and just fyi, in order to change the recovery that is installed using UnrEVOked once the program is loaded up you click file in the top left corner and then select custom recovery, then browse to where you downloaded the recovery.img to.
you CANNOT use the clockwork mod recovery that comes with unrevoked for SLCD inc. results in black screen with white bars.
tylerwagler said:
you CANNOT use the clockwork mod recovery that comes with unrevoked for SLCD inc. results in black screen with white bars.
Click to expand...
Click to collapse
That's been established a while ago. If you read my post you will see that I have provided instructions on how to make it use the version that does work, that I included. Read before you post.
My phone is stuck at the white Evo splash screen. This happenned after I performed the autoroot procedure located at: http://forum.xda-developers.com/showthread.php?t=838448
I have tried all kinds of ways to bring it back with no success. I downloaded shipped roms 3.30 and 3.70 (3.70) is what my phone originally was. The RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe will not run on my windows 7 machine I assume it's corrupted and I have downloaded it from two different sources. The RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe runs but it always tells me that my battery is below 30% even though I plug the phone in to the charger and after a few minutes the LED turns green. Then I tried downloading the 3.70 rom as a zip file, named it pc36100.zip, put it in the root of my sd card, then I went into recovery mode and I told it to start the update. It looks like it works but I get a message at the end that says "partition update fail!" and then it asks me to reboot and I'm right back at the endless white evo splash screen. I even tried to load several times using the evo-recovery where I was able to pick which image I wanted to phone to update but it fails with a symlink error of some sort.
I'm stuck. Any help would be appreciated here.
Thanks
Try PC36IMG from here http://forum.xda-developers.com/showpost.php?p=8097472&postcount=1
deeztech said:
My phone is stuck at the white Evo splash screen. This happenned after I performed the autoroot procedure located at: http://forum.xda-developers.com/showthread.php?t=838448
I have tried all kinds of ways to bring it back with no success. I downloaded shipped roms 3.30 and 3.70 (3.70) is what my phone originally was. The RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe will not run on my windows 7 machine I assume it's corrupted and I have downloaded it from two different sources. The RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe runs but it always tells me that my battery is below 30% even though I plug the phone in to the charger and after a few minutes the LED turns green. Then I tried downloading the 3.70 rom as a zip file, named it pc36100.zip, put it in the root of my sd card, then I went into recovery mode and I told it to start the update. It looks like it works but I get a message at the end that says "partition update fail!" and then it asks me to reboot and I'm right back at the endless white evo splash screen. I even tried to load several times using the evo-recovery where I was able to pick which image I wanted to phone to update but it fails with a symlink error of some sort.
I'm stuck. Any help would be appreciated here.
Thanks
Click to expand...
Click to collapse
I would also try running the RUU and PC36IMG a couple more times, maybe download them from a different source. Do you have HTC sync installed on your computer? I believe it's needed to use the RUU. So if you pull your battery out, reinsert it, then plug your Evo into a wall charger, the light goes steady green after a few minutes? Strange, I'd try a different RUU. Did you download from here? http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu . I haven't experienced problems like this before (fortunately) but I've also read about people needing to format their SD card before it would work, using the PC36IMG. Not sure why, but possibly something corrupted on the SD card? Did the auto root give you any sort of errors or anything? Or did it just appear to work, and then this happened?
Also, you could try running the RUU from fastboot mode. Boot to the bootloader, select 'fastboot', and then try the RUU
HTC Sync is indeed needed for the RUU in .exe form.
Boot into hboot by holding down the volume down button while turning on your phone. I believe you choose hboot USB and then run the RUU exe.
k2buckley said:
I would also try running the RUU and PC36IMG a couple more times, maybe download them from a different source. Do you have HTC sync installed on your computer? I believe it's needed to use the RUU. So if you pull your battery out, reinsert it, then plug your Evo into a wall charger, the light goes steady green after a few minutes? Strange, I'd try a different RUU. Did you download from here? http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu . I haven't experienced problems like this before (fortunately) but I've also read about people needing to format their SD card before it would work, using the PC36IMG. Not sure why, but possibly something corrupted on the SD card? Did the auto root give you any sort of errors or anything? Or did it just appear to work, and then this happened?
Also, you could try running the RUU from fastboot mode. Boot to the bootloader, select 'fastboot', and then try the RUU
Click to expand...
Click to collapse
The fastboot method worked! Awesome. So, in the hboot menu, it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?
deeztech said:
it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?
Click to expand...
Click to collapse
Correct. You can copy any ROM (suggesting nandroid backup first) to SD card and flash it
deeztech said:
The fastboot method worked! Awesome. So, in the hboot menu, it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?
Click to expand...
Click to collapse
Sweet, I'm glad it worked for you. So it says you're S off, even after running the RUU? I've never used the Autoroot method, but it must flash unrevoked forever, somewhere in the process. Well, if it says you're S off, I believe the only thing you're missing before you can flash anything is a custom recovery, which you most likely do not have, after running RUU. I believe that since you're s off, you can just flash a custom recovery from the bootloader, and then flash a rom. You could also use ROM manager to flash a recovery, you'd just need to download and install the Super User app, I believe. I think that should work for you? I've never tried to just flash a recovery from a stock ROM, right after an RUU, but if you're s off, i dont see why you can't do that. Download the PC36IMG I attatch here, make sure its named PC36IMG, put it on the main directory of your sd card, boot to the bootloader. Let it scan and ask you to update. Select volume up for yes. After that's done, you should have custom Amon Ra V2.3 recovery. From there, you 'should' be able to flash ROMs. good luck.
Edit: wouldn't let me upload the PC36IMG for some reason. Instead, click this link to download. http://db.tt/7jGH2CA
erik077 said:
Try PC36IMG from here http://forum.xda-developers.com/showpost.php?p=8097472&postcount=1
Click to expand...
Click to collapse
Uhh no. That PC36IMG.zip is waaay outdated. You know they are all different, right? Just because it's a PC36IMG.zip does NOT mean it's the same file as the next one.
I used that one in two situations...
1. when my friend phone was bricked
2. when did unroot
both times that file worked for me
erik077 said:
I used that one in two situations...
1. when my friend phone was bricked
2. when did unroot
both times that file worked for me
Click to expand...
Click to collapse
I did as you suggested and installed the custom recovery. Worked beautifully! I was able to install the MIUI rom and it's a beautiful thing. Thanks a lot for all your help.
Np, that's why we here
Sent from my PC36100 using XDA App
help!!!!
im stuck on step 8 my phone is showing the red triangle with the ! the DOS promt says...
waiting for the phone...
found the phone connected as 'recovery'
setting up a temporary recovery...
**daemon still not runningerror: cannot connect to daemon
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
**daemon still not runningerror: cannot connect to daemon
what do i do?
After running the Universal Auto Update v2.4, my phone almost makes it almost all the way. It gets stuck on the screen with the red triangle exclamation mark. On my computer screen, I kept getting the same repeating error messages..."ADB server didn't ACK", "Failed to start daemon" etc, until eventually it gives up. I pulled the battery out to turn the phone off. Turned it on into bootloader and selected recovery. All that does is take me back to the red triangle exclamation mark screen. And also, since the phone was fairly new to me, I went ahead and reset it to factory defaults before I started any of this.
Any help? any other useful information I could give?
Do you have S-ON or S-OFF in bootloader? If you connect phone to a pc does it recognize the device? Do you know how to use adb commands?
The red triangle is you trying to boot into recovery, but no recovery is there. Flash the file I attached, leaving it exactly as it is, no name changing, or extracting, boot into the bootloader, apply update, reboot, reboot into recovery, and you'll be on amon_ra 2.3
Heaterz16 said:
Do you have S-ON or S-OFF in bootloader? If you connect phone to a pc does it recognize the device? Do you know how to use adb commands?
Click to expand...
Click to collapse
It is S-ON. Yes, my computer will recognize the device. And, No, I am not familiar with abd commands.
teh roxxorz said:
The red triangle is you trying to boot into recovery, but no recovery is there. Flash the file I attached, leaving it exactly as it is, no name changing, or extracting, boot into the bootloader, apply update, reboot, reboot into recovery, and you'll be on amon_ra 2.3
Click to expand...
Click to collapse
I didn't think you could flash anything if your phone is not already rooted. Since my phone is not rooted, I'm lost.
golopogas said:
It is S-ON. Yes, my computer will recognize the device. And, No, I am not familiar with abd commands.
I didn't think you could flash anything if your phone is not already rooted. Since my phone is not rooted, I'm lost.
Click to expand...
Click to collapse
If your phone was S off, I'd say you could flash a custom recovery using your bootloader, and you'd be good to go. However, since the autoroot seemed to fail, and you're s on, I don't think you can just flash the recovery...I'm not sure though. If you could get the custom recovery flashed, in theory you could then flash the Unrevoked S-off tool, and you'd be S off with recovery. But I've never tried doing anything like that. If I were you, I'd run the latest RUU, or flash the latest PC36IMG (from here: http://unrevoked.com/rootwiki/doku.php/public/unrevoked3 ). Then once you're back to stock, I personally would run Unrevoked. I've used unrevoked probably a dozen times, and never had a hiccup with it.
Follow these instructions (but don't use the files linked in this post, they're out of date. Use these instructions, but use the files from the actual unrevoked site, as they're up do date) http://forum.xda-developers.com/showthread.php?t=787304
Download Unrevoked 3 from here: http://unrevoked.com/recovery/
Download Hboot drivers here : http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Sounds like a process, but I think it's your best bet, just flashing back to stock and then starting the process again. Good luck, and let me know if you run into any issues.
EDIT: oops, instead of linking you to RUU's, I somehow copied the wrong URL and sent you to unrevoked. Sorry. Here's the right one.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
golopogas said:
I didn't think you could flash anything if your phone is not already rooted. Since my phone is not rooted, I'm lost.
Click to expand...
Click to collapse
Ah, I misunderstood you, but use the links k2buckley sent and you'll be good.
I agree with K2buckley, when auto root's error who knows exactly when and what went wrong in the process. I would RUU as he suggested, here is a link to all RUU's: http://forum.xda-developers.com/showthread.php?t=884060
Select the RUU that matches your phone's SW Version, Radio etc. that you were last running.
Then, I would personally recommend the long method of rooting, that way in case something goes wrong, it is easy to help you along: http://forum.xda-developers.com/showthread.php?t=829045
Heaterz16 said:
I agree with K2buckley, when auto root's error who knows exactly when and what went wrong in the process. I would RUU as he suggested, here is a link to all RUU's: http://forum.xda-developers.com/showthread.php?t=884060
Select the RUU that matches your phone's SW Version, Radio etc. that you were last running.
Then, I would personally recommend the long method of rooting, that way in case something goes wrong, it is easy to help you along: http://forum.xda-developers.com/showthread.php?t=829045
Click to expand...
Click to collapse
I agree that rooting manually, using the 'longer method' is the best way to go, but the OP stated in a previous post that he wasn't familiar with ADB. I would suggest being at least a little familiar with adb, and be somewhat comfortable with it before trying to root a manual way. I guess ya gotta learn somewhere though, why not just dive right on in? I used unrevoked to root first, and then gradually learned ADB, which I use frequently now, and am comfortable with. I always did kind of wish that I learned ADB first, and learned things in the proper order. I learned backwards though.
k2buckley said:
I agree that rooting manually, using the 'longer method' is the best way to go, but the OP stated in a previous post that he wasn't familiar with ADB. I would suggest being at least a little familiar with adb, and be somewhat comfortable with it before trying to root a manual way. I guess ya gotta learn somewhere though, why not just dive right on in? I used unrevoked to root first, and then gradually learned ADB, which I use frequently now, and am comfortable with. I always did kind of wish that I learned ADB first, and learned things in the proper order. I learned backwards though.
Click to expand...
Click to collapse
That's a good point, whichever way he goes is up to him. As long as he figures it out, doesn't really matter to me. I rooted my Hero through adb and had no clue what I was doing which was scary, and then learned adb afterwards along the way like you.
k2buckley said:
I agree that rooting manually, using the 'longer method' is the best way to go, but the OP stated in a previous post that he wasn't familiar with ADB. I would suggest being at least a little familiar with adb, and be somewhat comfortable with it before trying to root a manual way. I guess ya gotta learn somewhere though, why not just dive right on in? I used unrevoked to root first, and then gradually learned ADB, which I use frequently now, and am comfortable with. I always did kind of wish that I learned ADB first, and learned things in the proper order. I learned backwards though.
Click to expand...
Click to collapse
Don't feel bad, I used unrevoked, but that was because I got my evo in november shortly after 2.2 was released and the adb commands wouldn't work. But I feel just as comfortable with adb as the people that used it originally. I originally started using it, but had system errors do the the firmware.
Here's an update. Ran the RUU and it got my phone back to the state it was in before I ran the factory reset, so I made a little progress. I went with the easier method and ran unrevoked. However, I again had an issue with recovery. I got the error msg, "Failed to push recovery. Terminating"
What about this? I read about z4root, which does a temporary root. If I can give it a temp root, and flash with the pc36img, would that get my recovery working? That seems to be the problem. I'd like to hear what you guys think before I try anything else. I feel like the more I do to my phone, the more complicated I'm making the solution.
golopogas said:
Here's an update. Ran the RUU and it got my phone back to the state it was in before I ran the factory reset, so I made a little progress. I went with the easier method and ran unrevoked. However, I again had an issue with recovery. I got the error msg, "Failed to push recovery. Terminating"
What about this? I read about z4root, which does a temporary root. If I can give it a temp root, and flash with the pc36img, would that get my recovery working? That seems to be the problem. I'd like to hear what you guys think before I try anything else. I feel like the more I do to my phone, the more complicated I'm making the solution.
Click to expand...
Click to collapse
hey man glad you got your phone back up and running for one. now as to using z4root to give yourself temp root than flash the PC36IMG.zip, that won't work because as soon as you turn off your phone you lose root. try this method, it takes a little work but you won't have any problems afterward
http://forum.xda-developers.com/showthread.php?t=829045
golopogas said:
Here's an update. Ran the RUU and it got my phone back to the state it was in before I ran the factory reset, so I made a little progress. I went with the easier method and ran unrevoked. However, I again had an issue with recovery. I got the error msg, "Failed to push recovery. Terminating"
What about this? I read about z4root, which does a temporary root. If I can give it a temp root, and flash with the pc36img, would that get my recovery working? That seems to be the problem. I'd like to hear what you guys think before I try anything else. I feel like the more I do to my phone, the more complicated I'm making the solution.
Click to expand...
Click to collapse
After running unrevoked, are you now S on or S off? I've seen a few times where unrevoked succesffully rooted, but failed to push the recovery image to the device. You need to power the phone down, then boot into the bootloader, and see if it says S off. If it does, you're almost done. We can manually flash the recovery image. Again, if you're s off, then download the PC36IMG i attatch. Be sure it's named exactly PC36IMG. Place the file on the main directory of your sd card. Power down the phone. Boot to the bootloader. It will find the PC36IMG, and then ask you to update. Press volume up, to say yes. Once it's done, from the bootloader, select recovery. At that point you should then boot into Amon Ra V2.3. If all that's successful, youll be fully rooted, s off, with a custom recovery.
Now if you check the bootloader, and you're still s on, I would try running Unrevoked a second time, and see if that works. Hope that helps, and again, if you're currently s off, you're almost there, just one more step. Good luck.
Also, when running unrevoked, you need to make 100% sure that there's no programs on your computer that could potentiall talk to your phone. You need to disable your anti virus as well. Some examples would be things like pdanet, htc sync, dropbox, any music syncing/sharing programs you may have. Basically be sure that the only program on your computer that can communicate with your Evo is Unrevoked.
k2buckley, spot on as usual. Also op, a quick way to help resolve issues is if you just restart your pc really quick.
I ran unrevoked a few more times. Still nothing. I decided to uninstall all htc drivers and reboot the pc, and restart the phone again. Ran unrevoked and it finally worked, sorta. Its on S-OFF now, I still need to flash pc36img, but I think I've pretty much got it. Damn I don't what I would have done without you guys. You have all been thanked!
golopogas said:
I ran unrevoked a few more times. Still nothing. I decided to uninstall all htc drivers and reboot the pc, and restart the phone again. Ran unrevoked and it finally worked, sorta. Its on S-OFF now, I still need to flash pc36img, but I think I've pretty much got it. Damn I don't what I would have done without you guys. You have all been thanked!
Click to expand...
Click to collapse
That's good that you're s off now. Flash the pc36img (although unrevoked should push recovery, but that's ok that it didn't, for whatever reason) and you'll be good. That's a better recovery than what unrevoked wouldve provided anyways. Report back, let us know how you make out.
Sent from my PC36100 using XDA App
I downloaded an and flashed an Incredible Rom and I have an HTC Evo.
It is now stuck at the HTC screen, and when I boot into recovery mode, and go to "recovery" it just takes me to Fastboot USB."
Usually it would take me to I believe Clockwork recovery?
Is there any chance you guys can help me or point me in the right direction =/
I really hope I didn't brick me phone. I've been searching online for hours and can't find anything that works. Even downloading the android-usb-driver.zip
I figure as long as I can get into Clockwork recovery or somehow read my SD card from my Phone I can just flash something else to fix it? I can't seem to find a way to do that though =/
Thank you for helping this moron in advance
First off you are not bricked ( take a deep breath) now since you can go into the bootloader you are going to flash clockworkmod from the bootloader look for his thread and download it
evo on cm7
Thank you for your prompt reply.
The thing is, I don't know how to Flash clockword mod from Bootloader. I know I have all the files on my SD card, since I've been rooted for a while and have flashed other roms, I just don't know how to access and flash it. Even if I did not have the file (which I believe I do,) I wouldn't know how to get it onto the SD card and flash it.
Thanks for all your help
PS, it has S -OFF.
Please someone help i'm freaking out here.
Calm down, are you holding volume down and power when you turn the phone on?
Sent from my PC36100 using Tapatalk
pull your card, if you have a card reader, put the pc36img for Amon Ra on the root of yo sdcard, put it in the phone, boot up by holding power and vol down at the same time, you'll go to bootloader. it'll scan, find the pc36img (which must be named PC36IMG.ZIP) and ask if you want to update, select yes, then it'll install recovery.
You can do a search for dougjamal. he has a link to the Amon Ra file in his signature, so find one of his posts
Thanks HipKat!
My friend is coming with his Galaxy S. I'll just put my USB in his phone, download the file to the SD card, pop it back into mine, and it should work, right?
THank you so much.
Can I message you for further help?
LMK how I can use the "Thanks" button. Still somewhat new to this.
I'm at work, so I can't stay on here. That dougjamal guy is really good and has links in his sig for a lot of important files.
IF the AR ps36img file doesn't work, you may have to run the RUU and start over fro mstock, and he has a link to the RUU files in his signature, too. just make sure you use the one for your device in the same way as I described the Amon Ra file, then you'll have to re-root.
ALSO, if you used unrEVOked to root your phone, go to their site and get the s-off tool and run that from recovery, if you're able to get to recovery before you run RUU (I doubt you have to run RUU though. I'm thinking recovery should work for you)
If you still need help you can pm me for it.
Sent from my PC36100 using XDA Premium App
All good now. Thanks so much guys!!
I think I may have bricked my Incredible...I pulled it out to put some games on it for my daughter to play. It had the latest OTA (2.3.4) and I wanted to root it. Played around with various methods to root and nothing worked. Downgraded to 2.2, and now it boot loops. If I have it plugged in, it will boot, but if unplugged it just loops. It won't install recovery from HBOOT, so I don't know what to do. Any suggestions? Thanks!
riot1031 said:
I think I may have bricked my Incredible...I pulled it out to put some games on it for my daughter to play. It had the latest OTA (2.3.4) and I wanted to root it. Played around with various methods to root and nothing worked. Downgraded to 2.2, and now it boot loops. If I have it plugged in, it will boot, but if unplugged it just loops. It won't install recovery from HBOOT, so I don't know what to do. Any suggestions? Thanks!
Click to expand...
Click to collapse
Ok so your definitley on 2.2 now?
S-on or off?
Radio version?
Hboot version?
Does the phone vibrate 5 times when trying to power on?
Software version shows 2.2
S-ON
Radio Version not sure how to check
HBOOT .92
Does not vibrate 5 times.
Thank you very much for the help!!
I had the same issue with not booting unless plugged in. I also had 5 vibes though with it.
Just from hearing that, read through the 5 vibes sticky and see what you can do.
Sent from my ADR6300 using XDA App
Tried the 5 vibrates fix, can't flash the stock rom in HBOOT and the RUU says there is a USB connection error.
Radio (baseband) version is at the top of hboot. If you have the 2.15.00.07.28 radio i would plug the phone into the pc so it boots, and then try using unrevoked to get root and s-off.
The ruu exe probably gave that error because you dont have htc sync installed which gives you the right drivers for the ruu. Im not sure why you cant get a PB31IMG.zip ruu to flash thru hboot. Does it give any errors?
cmlusco said:
Radio (baseband) version is at the top of hboot. If you have the 2.15.00.07.28 radio i would plug the phone into the pc so it boots, and then try using unrevoked to get root and s-off.
The ruu exe probably gave that error because you dont have htc sync installed which gives you the right drivers for the ruu. Im not sure why you cant get a PB31IMG.zip ruu to flash thru hboot. Does it give any errors?
Click to expand...
Click to collapse
I do have the 2.15.00.07.28 radio, but the USB doesn't seem to be working because unrevoked doesn't see the phone. I tried with HTC Sync installed and it still didn't work. I don't get any errors, it just won't install the PB31IMG file. I really do appreciate the help, I want to get this thing working again!!
riot1031 said:
I do have the 2.15.00.07.28 radio, but the USB doesn't seem to be working because unrevoked doesn't see the phone. I tried with HTC Sync installed and it still didn't work. I don't get any errors, it just won't install the PB31IMG file. I really do appreciate the help, I want to get this thing working again!!
Click to expand...
Click to collapse
In the phones settings do you have usb debuging checked (on) and fastboot unchecked (off). If your on 2.2 there will not be a fastboot option.
Also the drivers for unrevoked are different than the drivers for the ruu. You can get the unrevoked drivers from the unrevoked site, and the ruu drivers from htc sync. Note that to install one set of drivers, you need to uninstall the other ones first.
Also when trying the ruu thru hboot, the file must be named exactly PB31IMG.zip, and be on the root of your sdcard (in no folders).
Does hboot find the file, parse it (progress bar on the right) and then abort, or does it not find it at all?
Yes and yes.
Installed the Unrevoked drivers, but still no luck.
It finds the file and ignores it.
riot1031 said:
Yes and yes.
Installed the Unrevoked drivers, but still no luck.
It finds the file and ignores it.
Click to expand...
Click to collapse
I would copy all the files of your sd to your pc, and then format the sdcard fat32 with windows. Then copy your files back to the sdcard and download a fresh copy of the PB31IMG.zip you can get it here http://pvillecomp.com/?page_id=22, you will want the froyo one not the gingerbread. Then try flashing it thru hboot again. You said you also couldnt flash cwm thru hboot. This makes me think there is an error on your sdcard, or your doing something wrong with the PB31IMG files. If your s-off you should be able to flash an ruu or recovery thru hboot.
Not trying to call you a noob or anything but you might want to check this out http://pvillecomp.com/?page_id=79.
cmlusco said:
I would copy all the files of your sd to your pc, and then format the sdcard fat32 with windows. Then copy your files back to the sdcard and download a fresh copy of the PB31IMG.zip you can get it here http://pvillecomp.com/?page_id=22, you will want the froyo one not the gingerbread. Then try flashing it thru hboot again. You said you also couldnt flash cwm thru hboot. This makes me think there is an error on your sdcard, or your doing something wrong with the PB31IMG files. If your s-off you should be able to flash an ruu or recovery thru hboot.
Not trying to call you a noob or anything but you might want to check this out http://pvillecomp.com/?page_id=79.
Click to expand...
Click to collapse
LOL, no offense taken! This is the only phone I've had trouble with. I've owned 2 Incredibles, a DROID 3, a BIONIC, and now two Rezounds. Never had an issue rooting/flashing/etc. til now. I've formatted the sdcard a few times now, and I've tried three different sdcards. I think this phone just hates me. I have two other Incredibles sitting here, I may bite the bullet and give her one of those. I'm not s-off, could that be the problem?
Edit: It let me flash the stock froyo image in HBOOT, but I'm still in the same place. Unrevoked doesn't see the phone.
riot1031 said:
LOL, no offense taken! This is the only phone I've had trouble with. I've owned 2 Incredibles, a DROID 3, a BIONIC, and now two Rezounds. Never had an issue rooting/flashing/etc. til now. I've formatted the sdcard a few times now, and I've tried three different sdcards. I think this phone just hates me. I have two other Incredibles sitting here, I may bite the bullet and give her one of those. I'm not s-off, could that be the problem?
Edit: It let me flash the stock froyo image in HBOOT, but I'm still in the same place. Unrevoked doesn't see the phone.
Click to expand...
Click to collapse
On your pc with the phone plugged in go to device manager. At the top does it say android phone, and when you expand it android adb interface or composite interface?
Other than that im not sure what the issue could be. Now that the 2.2 ruu flashed, does it still bootloop? Mabey the cable or the usb port? Do other phones work with the cable, both charging and data?
I had the issue with not booting unless plugged in also. However, I was getting the 5 vibes.
Follow the 5 vibes of death tutorial up until it says your USB should be fixed and go from there. Which is a problem you're having if I'm understanding correctly.
That's my suggestion.
Sent from my ADR6300 using XDA App
I finally threw in the towel and grabbed another Incredible from my drawer of phones. This one rooted just fine and she's playing with it as I write this. Is there a way to take a nandroid backup from the working phone and get it onto the non-working phone somehow?