Related
Ok, guys im in a bit of a pickle and I'm looking for a genius to help me fix the problem.
Firstly I just got my Evo4g yesterday, im no stranger to rooting and or unlocking but this time i'm stuck. I came straight here to get the root started. My evo is running 2.2 firmware stock. I went here and started the ball rollinghttp://www.thedroiddemos.com/2010/08/27/how-to-root-the-htc-evo-4g-with-froyo-2-2-video-walkthrough/
The first video went off without a hitch and I was feeling really good about everything, then tragedy struck. I followed the second video and during the PC36IMG.zip update I got a weird error.
First line it bypassed the bootloader and on the second line it said:
[2] Raidio_V2 FAIL-PU
everything else updated fine but after the reboot i can only access the bootloader or it goes straight to the red triangle. I've been up for 3 hours trying to correct this problem before I give up and try to get a new device.
A little more information in my bootloader it reads:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02.0000
MICROP-041F
TOUCH PANEL-ATMELC03_16ac
RAIDIO-2.15.00.09.01
I've tried several things and none of them worked, I've even tried to flash the stock RUU.
If you've run into the same problem, please post here and maybe some of the genius's at XDA can brainstorm and keep this from happening to anyone else.
You have the new HBOOT here is a guide on how to root it http://forum.xda-developers.com/showthread.php?t=829045
My computer wont communicate with the phone because im in bootloader mode. How can I fix this?
Have you tried pulling the battery and restarting?
Sent from my PC36100 using XDA App
Surf Burger said:
Have you tried pulling the battery and restarting?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I did and it gave me the same error. I even tried different PC36IMG PACKAGES, still nothing.
Sent from my SGH-T959 using XDA App
You should be able to access recovery from booyloader screen on your phone. Use that to mount what you need and probably get the PC36IMG you need!
Sent from my Snapified Evo
I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
luck has been wished
Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?
still won't not into any rom? did you get errors?
NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.
what happens when you reboot the phone not going into bootloader?
Just the HTC EVO 4G splash screen. Over and over and over...
does it show the boot animation or just stuck on splash?
Just the splash. No animation.
pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Wrong button..
xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?
never do OTA when rooted, use unrevoked to root, unrevoked.com
NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?
Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
run the ruu to s-on then trade for another
NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.
Yes, I am a noob. Yes, I saw the video and followed the steps. Yes, I most definitely appreciate your help and realize it may take some time for a reply.
I do not have the know-how required to deal with a rooted phone. A friend of mine was the one who originally rooted my phone roughly a year ago. I decided to unroot it. I used the unroot method provided at androidforums.com
Everything happened as it was described. However, I still have SuperUser as well as access to ClockWork Recovery and bootloader. I can also see in Software Information the kernel version. It is my understanding that if your phone is rooted, you should not be able to access these. I feel like I shouldn't be able to access these and that my phone shouldn't be displaying the kernel versionSo these are my questions:
1. Will bootloader still show up, when you hold the down volume and on-off button, even if your phone is unrooted?
2. Should you be able to access Clockwork Recovery and SuperUser if your phone is unrooted?
3. How do I know with 100% that my phone is unrooted? Is there some kind of test or method of testing?
4. Do I need any of the ROOTING/UNROOTING zip files on my phone after it's been unrooted?
I simply want my phone to be stock, like it was when I bought it. I have read on these forums that if the bootloader displays s-on then the phone is unrooted; I have s-on but can still access these programs.
Once again, I just want to go back to stock. No SuperUser, no Clockwork, nothing, regular stock HBOOT#. How do I go about this?
I want to thank you ahead of time. I know you guys have tons of questions thrown at you. Thank you.
Current Phone Information:
SUPERSONIC EVT3 SHIP S-ON
HBOOT-6.17.0001
TOUCH PANEL ATMEL224_16ab
RADIO-2.15.00.0000
Mar 8 2001
Android Version 2.3.3
Baseband Version
2.15.00.0808
Kernel Version
2.6.35.10-gc0a661b
[email protected]#
Tue Jun 14...etc.
Build Number
4.24.651.1 CL61076 release-keys
Software number
4.24.651.1
MannyA said:
Yes, I am a noob. Yes, I saw the video and followed the steps. Yes, I most definitely appreciate your help and realize it may take some time for a reply.
I do not have the know-how required to deal with a rooted phone. A friend of mine was the one who originally rooted my phone roughly a year ago. I decided to unroot it. I used the unroot method provided at androidforums.com
Everything happened as it was described. However, I still have SuperUser as well as access to ClockWork Recovery and bootloader. I can also see in Software Information the kernel version. It is my understanding that if your phone is rooted, you should not be able to access these. I feel like I shouldn't be able to access these and that my phone shouldn't be displaying the kernel versionSo these are my questions:
1. Will bootloader still show up, when you hold the down volume and on-off button, even if your phone is unrooted?
2. Should you be able to access Clockwork Recovery and SuperUser if your phone is unrooted?
3. How do I know with 100% that my phone is unrooted? Is there some kind of test or method of testing?
4. Do I need any of the ROOTING/UNROOTING zip files on my phone after it's been unrooted?
I simply want my phone to be stock, like it was when I bought it. I have read on these forums that if the bootloader displays s-on then the phone is unrooted; I have s-on but can still access these programs.
Once again, I just want to go back to stock. No SuperUser, no Clockwork, nothing, regular stock HBOOT#. How do I go about this?
I want to thank you ahead of time. I know you guys have tons of questions thrown at you. Thank you.
Current Phone Information:
SUPERSONIC EVT3 SHIP S-ON
HBOOT-6.17.0001
TOUCH PANEL ATMEL224_16ab
RADIO-2.15.00.0000
Mar 8 2001
Android Version 2.3.3
Baseband Version
2.15.00.0808
Kernel Version
2.6.35.10-gc0a661b
[email protected]#
Tue Jun 14...etc.
Build Number
4.24.651.1 CL61076 release-keys
Software number
4.24.651.1
Click to expand...
Click to collapse
Your unrooted you just have to run a ruu to get rid of superuser.clockwork, and your hboot back to normal
Sent from my PC36100 using XDA App
---------- Post added at 07:03 PM ---------- Previous post was at 06:58 PM ----------
http://www.fileserve.com/file/3rVYVfd download the ruu rename it to PC36IMG.zip put it on the root of your sd card (not in any folders) power down to the bootloader accept the update reboot and youll be 100% stock
Thank you, evo4gnoob.
When I unrooted my phone, I downloaded that file, transferred it to my sd and let the bootloader update. However, I still have superuser, clockwork, hboot like I mentioned.
I don't know if this will tell you anything, but whenever I restart my phone, it goes into a continuous restart cycle.
MannyA said:
Thank you, evo4gnoob.
Where would I find said RUU? Is this "RUU" specific to my software?
Click to expand...
Click to collapse
i posted the download llink
I edited my post once I saw your link. Thank you for adding that on to your post. Once I saw the name of the file, I recognized it. Yesterday, when I unrooted my phone, I downloaded that file renamed it to PC36IMG.zip and transferred it to the root of my SD. The bootloader updated and I proceeded. However, I still have all the previously mentioned conditions. Including the bootloop.
In order to be thorough, I have downloaded the file you linked. I renamed it to PC36IMG.zip, transferred it to the root of my SD and brought up the bootloader. I accepted the update. It updated a few of the things on the list, and then rebooted into bootloader and it continued to update. Afterwards, I turned it off, and try to get into bootloader but it would just start up normally. I did a battery pull and then it let me into bootloader. The HBOOT is now 2.16.
Should I proceed to delete all the zip files associated with rooting and unrooting?
THANK YOU.
MannyA said:
I edited my post once I saw your link. Thank you for adding that on to your post. Once I saw the name of the file, I recognized it. Yesterday, when I unrooted my phone, I downloaded that file renamed it to PC36IMG.zip and transferred it to the root of my SD. The bootloader updated and I proceeded. However, I still have all the previously mentioned conditions. Including the bootloop.
In order to be thorough, I have downloaded the file you linked. I renamed it to PC36IMG.zip, transferred it to the root of my SD and brought up the bootloader. I accepted the update. It updated a few of the things on the list, and then rebooted into bootloader and it continued to update. Afterwards, I turned it off, and try to get into bootloader but it would just start up normally. I did a battery pull and then it let me into bootloader. The HBOOT is now 2.16.
Should I proceed to delete all the zip files associated with rooting and unrooting?
THANK YOU.
Click to expand...
Click to collapse
It's up to.you
Sent from my PC36100 using XDA App
What made it go into a.continues
Sent from my PC36100 using bootloop
XDA App
Just out of curiosity, why did you unroot in the first place? Just to have it stock??
just had this conversation with a friend of mine, who wants to root his Prevail for the first time. Being S-off, itself, doesn't change anything on your phone, as far as how it runs, looks, etc.
It's like having the keys to a car you don't drive. Just because you don't drive it, doesn't mean you throw the keys away.
I have a fairly strange problem. My wife got tired of the Verizon bloatware on her Dinc2 so I offered to root and flash it to a nice rom. Her only requirements were that it work both as a phone and as a camera. After an uneventful downgrade, s-off, root and CWM, we tried aeroevan's unofficial CM9. We found that the camcorder was broken. Next we tried the MikRoms Incredible 2 HD Rls1. This worked beautifully in every respect except one: when I rebooted the phone, it went into a loop. The phone would boot to the opening lock screen.. in some cases I could even unlock it.. and then either turn off or reboot (which one seemed random). After getting back into the bootloader, I tried all the obvious things:
Wiping all partitions
Reloading the ROM
Trying a different ROM
Flashing back to a Stock ROM + root
Flashing back to stock 2.3.3.
In every case, the phone works perfectly with the new ROM up until it is rebooted, after which it goes into a loop at the lockscreen. The only ROM that DOES work is aeroevan's unofficial CM9. It reboots without any issues, but of course the camcorder and camera flash are busted there. At least it's usable as a phone again.
I've looked and looked, and either my google-fu is failing me utterly or this is a fairly unusual problem. Does anyone have the faintest idea what's going on here and how I can work at fixing it?
This is a well known issue with 605.05 software phones (and several other threads already about this). There is a PSA in Development warning this issue exists. Only guaranteed ROMs without issue are AOSP ROMs. If you want working camera, flash CM7.
I have also heard that flashing the radio packaged with the latest software may fix the issue, you can give that a try. You could also try flashing Condemned Soul's 6.xx ROM in development section.
Sent from my ADR6425LVW using Tapatalk 2
Yah, right after I posted this I saw this:
http://forum.xda-developers.com/showthread.php?t=1746490
Sorry about that. Thanks for the info!
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
I bet the biggest plus is the happy wife part huh?
Sent from my Incredible 2 using xda app-developers app
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
Glad flashing the new radio got it sorted out!
fsiddique said:
Glad flashing the new radio got it sorted out!
Click to expand...
Click to collapse
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
wexx2504 said:
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
Click to expand...
Click to collapse
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
prototype7 said:
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
Click to expand...
Click to collapse
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
wexx2504 said:
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
Click to expand...
Click to collapse
You can check the md5sum from the phone, just use terminal emulator (might need busybox installed). To check if you are S-OFF, boot into the bootloader and it should say S-OFF.
Sent from my Incredible 2 using Tapatalk 2
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
wexx2504 said:
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
Click to expand...
Click to collapse
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
wexx2504 said:
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
Click to expand...
Click to collapse
\
I am at this exact same radio, firmware version, hboot version and situation too any help would be greatly appreciated. Trying to help a co-worker fix his wife's device.
I need some guidance on trying to resurrect an HTC Incredible 2 (Verizon) that is currently a stock unit, S-ON (never rooted or unlocked) that will not boot - gets stuck on white HTC screen. The person using it, went and upgraded to another device and was about to throw the unit out until I decided to take one crack at a rebuild.
I can get into the HBoot screen and have attempted numerous factory resets to no avail... system will simply show a progress bar that never moves.
I've been searching this board and can't seem to get a clear way to get a full image back onto the phone. I've tried some of the moves to copy a RUU file to P32IMG.zip but keep getting "main version is older" messages from numerous different versions that I've tried. (So, the unit is reading the SD card correctly)
Can anyone point me to a guide to simply blast a new image onto the phone that is currently S-ON and cannot boot to the OS? (preferably via the SD Card, since I'm not able to get onto the phone via a USB cable - even after I've installed HTC Sync). All of the rooting/unlocking/S-OFF guides on this board seem to assume you can boot to Android as a first step - which i cannot do.
Here are the version numbers from my HBOOT screen:
*** LOCKED ***
VIVO_W_XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-BOOT
Jul 18 2011, 12:39:36
Thanks in advance for any assistance.
I would try to root it first. I think you can push files to your phone while in hboot through adb. After you root it, you can always go back to stock. Check prototype's guide in either general or development section.
Sent from my Oney Bone.
Go soff
Sent from my ADR6350 using xda app-developers app
ever have any luc? I have 2 htc droid incredible 2's that have corrupt boot loaders.... yeah big mistake there. they aren't a primary phone just kinda gathering dust on my shelve and I thought I'd try and fix it again.
Sent from my VS980 4G using XDA Premium 4 mobile app