ok guys.. used the new revolutionary s-off tutorial to obtain s-off with my new replacement Evo from Asurion. In the past i have had no problems with the rom i've used after rooting with unrevoked and such.. but now im in some **** idk what to do about..
obtained s-off with new revolutionary tutorial
wiped everything..
flashed miui 1.92.0 on [newest as of 8sept11]
phone rebooted
now stuck in boot loo
cant get into recovery
cant 'mount as disk drive' to try different rom
dumbfounded on WTF to do
Asurion has dropped me from insurance after 3 phone claims this year from stolen/lost/dropped cases [actual cases]
HELP! :[
some tech
2.3.3 gingerbread
2.15 hboot
1.92.0 miui rom flashed
AF_EVO said:
ok guys.. used the new revolutionary s-off tutorial to obtain s-off with my new replacement Evo from Asurion. In the past i have had no problems with the rom i've used after rooting with unrevoked and such.. but now im in some **** idk what to do about..
obtained s-off with new revolutionary tutorial
wiped everything..
flashed miui 1.92.0 on [newest as of 8sept11]
phone rebooted
now stuck in boot loo
cant get into recovery
cant 'mount as disk drive' to try different rom
dumbfounded on WTF to do
Asurion has dropped me from insurance after 3 phone claims this year from stolen/lost/dropped cases [actual cases]
HELP! :[
Click to expand...
Click to collapse
i dont know if this will help,but,i did the rev. s off tool.got s off and did something wrong and got a big bowl of boot loops!i couldnt get it to stop.so i took my sd card out and put it into a card reader,and downloaded the pc36img file straight to the sd card,booted into recovery and installed it.but now i have no revovery,but still have s off.i have no clue how to re-install a custom recovery.but i hope that i somewhat helped.
If you used revolutionary, you should have a 6.16 hboot, not 2.16 (you said 2.15, but I think only Japanese Evos have that). If you're s-off but don't have a recovery, you can put a PC36IMG of a recovery on your SD card. Just use a card reader to do so. If you can get into recovery but your rom is bootlooping, try wiping cache and dalvik and rebooting.
If none of those are options, try running an RUU from your computer. You should be able to boot at that point so you can put whatever you need on your SD card.
When you select recovery from hboot, what happens? Do you get the stock recovery (red triangle), or does it hang on the splashscreen? Or can you get into recovery?
Sent from my PC36100 using Tapatalk
Related
Recently my phone was working fine until today. I was on mikfroyo 4.4 everything was fine until i decided to flash an unimportant file, when i reboot it my phone was doing boot loops, so i decided to wipe everything and flash a clean mikfroyo 4.4 again. it worked for a couple hours, later my phone started to freeze, i took the battery out and i got stuck on the white screen logo.. i tried to take battery out for a couple times and nothing.. i tired to go into recovery mode(amon-ra 2.2.1) and i could not get into recovery, it kept on freezing i was like WTF!! then i tried to go into bootloader and that worked fine, but when i choose to boot into recovery via bootloader it did boot into recovery but then it froze again in recovery.. So at the end nothing worked but bootloader.. then i decided to flash a ROM via bootloader (PC36IMG.zip) and that fixed all the problems temporarily (it did not freeze).. but then I notice that that was a stock unrooted PC36IMG file so i lost root and it put back the HTC stock recovery (NOT AMON-RA nor CLOCKWORK).. then the problems started again (the same from above).. but since i rooted my phone via unrevoked forever i had S-OFF.. so i flashed AMON_RA recovery via bootloader to see if I could flash unrevoked-forever-son (that way i could have S-ON and send it to sprint for a replacement) but again it kept on freezing on recovery mode.... so my question is is there anyway i can flash unrevoked-forever-son via bootloader.... that way i can send it to sprint and tell them that my phone keeps on freezing.
Nothing works but bootloader, everything else freezes (recovery mode and while trying to boot the phone)
I will apreciate your time and help.
Did you try running unrevoked son as PC36img.zip?, then the stock RUU. (doesn't sound like it could hurt, lol)
but what kind of files would i put inside pc36img?
You don't put anything inside the PC36IMG.zip file. It comes ready to go from the unrevoked team:
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
Click to expand...
Click to collapse
- So go here: http://unrevoked.com/rootwiki/doku.php/public/forever
- Find the section I quoted above
- Download the PC36IMG.zip file
- Put it on the root of your SD card
- Power off
- Hold vol down + power
- Once in HBOOT it will automatically find/ask to run the PC36IMG.zip file
- volia! s-on
I know, i understand that process but my problem is that i cant go into recovery AT ALL it frezzes each time neither to boot my phone normally... the only thing that works fine is bootloader.. so what i am trying to look for is a way to flash the s-on tool via botloader bc i can not go into recovery.
the pc36img contains the stock unrooted ROM - supposed to be flashed via bootloader (i have already done this process so i lost root)
and when you download the S-on tool it comes in a zip file that is suppose to be flash thru recovery not bootloader (and this will be my final step which is not done yet)
yoboii23 said:
I know, i understand that process but my problem is that i cant go into recovery AT ALL it frezzes each time neither to boot my phone normally... the only thing that works fine is bootloader.. so what i am trying to look for is a way to flash the s-on tool via botloader bc i can not go into recovery.
Click to expand...
Click to collapse
Edit: one sec -- I am looking for a PC36IMG.zip that did s-on.
spiicytuna said:
I am looking for a PC36IMG.zip that did s-on; I've used it recently on a friends evo
Click to expand...
Click to collapse
This is what i was looking for i hope you can find it!! !!!
I was looking for a way to have the s-on tool inside a PC36IMG.zip.. i didnt think it was possible
But isn't that process (PC36IMG.zip) only for things that suppose to be flash thru bootloader? like slpash screens, recoverys, boot.img? so in what category does the s-on tool fits?
I'm sorry for all this questions but i dont wanna make my phone worse then what already is.
I think your best bet is to hop on freenode and join channel #unrevokedtest
Easiest way to do this is here: http://webchat.freenode.net/
They'll be able to help you for sure. LazyDog and joshua_ are two good people to look for.
thank you man.. but nope is confirmed you can not put put the S-on tool into a PC36IMG.zip ima have to tell sprint that i lost it.
yoboii23 said:
thank you man.. but nope is confirmed you can not put put the S-on tool into a PC36IMG.zip ima have to tell sprint that i lost it.
Click to expand...
Click to collapse
Did you talk to the guys on irc? Seriously, I've seen them preform some miracles.
PS. The chances of Sprint checking s-on/off is highly unlikely.
You can use the pc36img from amon ra's thread to flash the recovery and then use it to lock your nand. Afterward all you have to do is run the ruu one more time and you will be good to go
I agree with what was said before. The likelihood that they'll look at S-On is VERY small. I would just take it in, tell them its freezing all the time, and ask for a replacement. If by some crazy chance they do look at S-On, just play dumb and pretend you don't even know what it is. If you've got a cute lookin girl to help you that'd be willing to take it in, all the better
Otherwise, try running the RUU for your build number. We'll go from there if you still have problems.
I fixed it, it was all due to a ripped cable inside my evo I don't knw how that happened but it happened lol all I had to do was replace my screen.
And yea I did talk to guys from unrevoked.. they r pretty smart and understood my problem quick but were unable to help me.
I was running unrevoked3 in order to full root my phone (I think it was rooted, but not nand unlocked before - I was running the Fresh Rom and want to switch to cyannogen)
After unrevoked went through two root processes, and stated "this is a triumph," the phone rebooted again and got stuck at the HTC EVO 4G white screen.
Unrevoked states ""Flashing recovery. Do not touch your phone!" So, uh, I don't want to touch my phone.
What do? Should I just pull the battery and try again? or am I going to brick the freaking thing?
It's been on the white screen for a half hour now.
Just so you know, all you had to do was flash unrevoked forever through recovery.
I think it's fine to unplug or pull the battery. Afterwards, you may need to flash recovery, but other than that you should be fine.
(from... Evo/MIUI/Tapatalk)
Hmmm. Flashing the recovery should take next to el zilcho in time.
You stated that you possibly already had root user access on your evo, but you were not sure if you had unlocked nand. Then you tried to run unrevoked again to fully root.
I believe it's a bad idea to perform a root method which is designed to perform a full root operation as if your device was fully stock, on a partial root device.
As long as the process is only trying to flash a recovery you should be OK to pull the battery.
Here are my suggestions to continue:
- Find the AmonRa PC36IMG in his thread in the dev section. Place on root of SD card. Poweroff device - Reboot into bootloader and let the recovery flash.
- If this does not work, I would recommend running a 3.70 RUU (ONLY if you are on a 3.70 ROM) and retry the root process.
Hope everything works out.
If anyone else has something to add, please do!
The first time I rooted mine, the same thing happened. I was on the IRC Channel and a few guys were talking me through it, and one guy said just pull the battery nad reboot to Hboot and reflash recovery using Amon Ra (PC36IMG Version), which I did and it was no problem.
After going to unrevoked's IRC channel, and being directed to pull the battery and then follow these instructions (since i was already S-OFF): h.ttp://noobgui.de/wiki/index.php?title=What_to_do_if_you're_S-OFF_but_can't_get_root (sorry for the broken link I'm not at the point where I can post them).
Everything seems fixed. Pretty sure that's about the same thing as what you said. Thanks.
do you have S-off or the NEWEST 2.3.3 OS?
If you are S-on and on 2.3.3 why the hell are you trying to run UNREVOKED AGAIN, you cannot gain root throught that method because it doesn't work with the NEW HBOOT.
If you have S-off DOWNLOAD AMON RA NEWEST RECOVERY and put it on your SD CARD
Pull the battery from your phone put the battery back in, HOLD VOLUME DOWN and POWER on the PHONE you will be in the RECOVERY screen now let the PC36IMG.zip install and you will regain THE FULL RECOVERY and be able to flash any rom you desire, if you need ROOT all you have to do is INSTALL the SUPER USER & BUSY BOX from recovery to have a fully rooted 2.3.3
OR After installing Amon Ra's Recovery Image, just flash the Deoexed 2.3.3 over your current 2.3.3 you will be deoxed and full rooted and you wont have to reinstall any apps or change your current arrangement
RMelyon said:
After going to unrevoked's IRC channel, and being directed to pull the battery and then follow these instructions (since i was already S-OFF): h.ttp://noobgui.de/wiki/index.php?title=What_to_do_if_you're_S-OFF_but_can't_get_root (sorry for the broken link I'm not at the point where I can post them).
Everything seems fixed. Pretty sure that's about the same thing as what you said. Thanks.
Click to expand...
Click to collapse
My dumb-ass should have told you to go to their IRC channel. Those guys are real quick to be helpful. Good deal getting it working.
Hello everybody. I bought an Incredible with the SLCD screen. Droid Incredibles come with either amoled or slcd screen types. The newer Incredibles have slcd screens. Not knowing this Incredible had the slcd screen, I went ahead and rooted it with Kinsellea2's rooting tutorial vie a Mac here: [How To] Root 2.3.4/downgrade and Get S-off
Anyway, Clockwork Mod recovery does NOT work afterwards as this tutorial was meant for the amoled screen type Incredibles only. Now when I go into Clockwork mod recovery on my phone, I do see HBOOT but as for recovery, I'm seeing is a black screen with two white lines on both sides of the screen. No recovery, no backup, no restore, no nothing. To top it off, the phone does not read the internal or external micro SD memory cards anymore. It's saying both are unavailable with no space information.
Again, the phone is rooted with no S-OFF as I could not get Unrevoked 3.32 to work.
I need help to flash or restore a SLCD type screen Clockwork Mod onto this phone. Could someone give me advice how to accomplish this PLEASE ?
What android version, hboot, and baseband are you on at the moment? Could you also post a link to the thread you were folowing.
Your best bet probably is to just do an ruu and then start from scratch with rooting.
EDIT: Nevermind you said it wont see the sdcard. How are you trying to access the sdcard, with the phone booted? I would still try an ruu, its possible hboot will still be able to read from the sdcard.
I've used Unrevoked method 3.22 and then 3.32 along with Clockwork Mod 5.0.2.0 to root the phone. No go as Clockwork Mod 5.0.2 is only for AMOLED sctreen types.
I can't post outside links yet. But can someone post a link to the RUU method for this phone ?
joot said:
I've used Unrevoked method 3.22 and then 3.32 along with Clockwork Mod 5.0.2.0 to root the phone. No go as Clockwork Mod 5.0.2 is only for AMOLED sctreen types.
I can't post outside links yet. But can someone post a link to the RUU method for this phone ?
Click to expand...
Click to collapse
Cwm 5.0.2.0 should be compatible with both slcd and amoled. Its only the earlier versions that were screen type specific. If im not mistaken if its an incompatible cwm you will not be able to see anything, even hboot or the os when booted. Sounds like your cwm img file may be corrupt, i would not use that one again.
Are you downgraded to 2.2 yet or are you still on 2.3.4?
You can get the ruu here http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and here is how to flash it http://pvillecomp.com/?page_id=79.
Unrevoked 3.32 was not able to downgrade me to 2.2 I'm still at 2.3.4 I can boot to HBoot but I can't get to recovery, backup, restore screen. My screen is black with two white lines on the sides.
joot said:
Unrevoked 3.32 was not able to downgrade me to 2.2 I'm still at 2.3.4 I can boot to HBoot but I can't get to recovery, backup, restore screen. My screen is black with two white lines on the sides.
Click to expand...
Click to collapse
If your on hboot 0.92 i would use this guide and try again. http://forum.xda-developers.com/showthread.php?t=1306400
If you are on hboot 1.02 i would try with this guide. http://forum.xda-developers.com/showthread.php?t=1506258
cmlusco, I'm on HBOOT 0.92.0000. The guide you linked to was the exact tutorial I followed which got me to this predicament. Again, when I got to HBOOT and I scroll down to recovery, all I'm seeing is a black screen with two white lines on the sides. No menu selection like a normal recovery screen.
I did used Unrevoked 3.22 initially then the tutorial said to use Unrevoked 3.32 afterwards, which I did. During Unrevoked 3.32's operation, it gave me some sort of error and the operation stopped. That's when I tried to go into HBOOT and realize the black screen with white sides. What's weird is that the phone will not mount the internal and external memory cards anymore. That's the reason I can't use ROM MANAGER as it needs the SD card to be mounted. I can mount the cards thru recovery in HBOOT but I can't even get to that screen
Have you tried to ruu yet? Sounds like your best option at this point.
Thanks a lot for the advice and suggestions. After trying three days to root this phone, I finally got it rooted. Issue #1, during the rooting process the phone somehow lost connection, lost ability to detect or read both the external and internal SD card memory. I was able to solve this problem with the this procedure:
SD Card Fix
Press & hold vol down and power on the phone
Select fastboot by pressing the power button
ADB commands (from the command line in Terminal)
fastboot oem enableqxdm 0
fastboot reboot
Issue #2: I follow the tutorial exactly but somehow the phone never was able to turn s-OFF. I had to run Unrevoked 3.32 like five, six times before it finally was able to. During this whole rooting process, I've learned quite a bit.
I have a bricked evo 4g that currently only boots to bootloader, The evo says " s-off ".......I have tried flashing RA recovery thats fails, Also tried running official Sprint 2.3.3 ruu, that also fails with usb error 17. I posted some screen shoots of the bootloader and what error i get after trying to flash custom reovery.. does anyone know of a fix... any help is always much appreciated thanks!
Hey,
well I can give you the new that your phone isnt bricked if it was it would not turn on and would pretty much be a "brick" hence the name. I am not good with this but captain throwback is the man on fixing borked devices. so you might want to look to some higher ups in the forum and ask for help!
kevo3000 said:
I have a bricked evo 4g that currently only boots to bootloader, The evo says " s-off ".......I have tried flashing RA recovery thats fails, Also tried running official Sprint 2.3.3 ruu, that also fails with usb error 17. I posted some screen shoots of the bootloader and what error i get after trying to flash custom reovery.. does anyone know of a fix... any help is always much appreciated thanks!
Click to expand...
Click to collapse
Rather than running an RUU from the computer, have you tried flashing a PC36IMG.zip through HBOOT? Try this one - it's the 4.54 Gingerbread stock ROM. If that flashes successfully (you might have to do it twice), then you can try flashing a custom recovery again.
Do you happen to know what hardware version you have? I notice you appear to have flashed my 0.76 ENG HBOOT modded to read 2.10 - if you did that on a newer hardware model, that would be bad. The block sizes on the newer hardware models are different than on the older versions, so you really can't use an HBOOT version prior to 2.10 on them (the one you have is actually 0.76).
Captain_Throwback said:
Rather than running an RUU from the computer, have you tried flashing a PC36IMG.zip through HBOOT? Try this one - it's the 4.54 Gingerbread stock ROM. If that flashes successfully (you might have to do it twice), then you can try flashing a custom recovery again.
Do you happen to know what hardware version you have? I notice you appear to have flashed my 0.76 ENG HBOOT modded to read 2.10 - if you did that on a newer hardware model, that would be bad. The block sizes on the newer hardware models are different than on the older versions, so you really can't use an HBOOT version prior to 2.10 on them (the one you have is actually 0.76).
Click to expand...
Click to collapse
Yeah I think the hardware version was 003 or 004, yeah even when i use the Pc36img in your post 1. Radio_v2 ok then 2-8 Fail-PU.
Kinda the same situation, but I think easier to fix
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.
I had the same thong happen to me when I first unlocked my phone all you have to do is get a computer with a card reader and put that PCI36.img
On the root of your SD card and put it back in the phone and boot into the bootloader... And if the card still cannot mount then keep pulling it and turning the phone on and let it come on in bootloader everytime and adventully the bootloader will reconigze the SD card and install the recover.. this method has worked for me a fee times
Sent from my PC36100 using XDA
Other option is sometimes I do a factory reset and reboot my phone and the very first ROM I ever flashed reinstalls... Without going into the bootloader ofcourse
Sent from my PC36100 using XDA
Oh wait I just read that you said you CAN get into recovery.. well there is a option to mount SD card.. do that and then restart
Sent from my PC36100 using XDA
monty_python said:
Oh wait I just read that you said you CAN get into recovery.. well there is a option to mount SD card.. do that and then restart
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Thanks man, but here's th thing, it KEEPS saying "E: cant mount sd card" and "No such directory found". thats my proble that I am having. If only I can get the phone to pick up the sd card, my situation would be handled.
I bricked my evo 4g while attempting to flash to metro (on my own, couldnt find a exact guide). I had written a metro prl, donor flashed, and I was changing the NAM settings. All this went fine and then I was attempting to write the NVRAM file from whiterabbit site exactly as it told me. It wrote successfully but when I turned on my phone it was bricked.
I can access boot loader but it wont load into recovery. I get the white htc screen over and over again when I normally turn it on or when I attempt to access recovery.
Any help would be appreciated Im super frustrated .
Here are my bootloader specs
Unlocked
supersonic evt2-3 ship S-ON
HBOOT-2.16.0001
MICROP-041F
TOUCH PANEL-ATMEL224_16ab
tenfour1 said:
I bricked my evo 4g while attempting to flash to metro (on my own, couldnt find a exact guide). I had written a metro prl, donor flashed, and I was changing the NAM settings. All this went fine and then I was attempting to write the NVRAM file from whiterabbit site exactly as it told me. It wrote successfully but when I turned on my phone it was bricked.
I can access boot loader but it wont load into recovery. I get the white htc screen over and over again when I normally turn it on or when I attempt to access recovery.
Any help would be appreciated Im super frustrated .
Here are my bootloader specs
Unlocked
supersonic evt2-3 ship S-ON
HBOOT-2.16.0001
MICROP-041F
TOUCH PANEL-ATMEL224_16ab
Click to expand...
Click to collapse
Lol duude calm yooouur nips duude...
Now on to your thing......first your not hard brick which is good and look up how to unroot EVO 4G and reroot it where its HBOOT 2.16 S=OFF then try your method of going to metro or somthing lol
Sent from my PC36100 using xda premium
You can try and take your SD card out of the phone stick it on your computer and download a recovery place it on your of the SD card rename it to PC36IMG.zip ,place the card back on the phone and go to your bootloader and see if it finds the update
Sent from my PC36100 using xda app-developers app
Will unrooting unbrick my phone? And i have a recovery I just cant reach it because when i press recovery it boots to the white screen again. I tryed reflashing my recovery and same thing keeps happening.
A little update at where Im stuck. I reflashed my recovery in hope that it will work but nothing and now it will not let me flash using Cmd prompt anymore. I cannot flash using cmd because it says waiting for device. Putting roms or recoverys in my sd card and renaming as PC36IMG comes out the same, it stops at Parsing zip and never moves forward. I cannot reach recovery because when I click it I just get the white splash screen again.
Apparently my messed up NV items are not as simple to fix as other bricks. There was a solution posted here by cutthroat but the file is no longer downloadable. Here is the link.
http://forum.xda-developers.com/show...6&postcount=54
Any further help on how to fix my NV files or stop this bootloop/brick would be appreciated. Thanks
Well I looked through all those old links and trying to get those files now looks *really* hard.
You could try what someone did in this post:
http://forum.xda-developers.com/showpost.php?p=31931866&postcount=49
And hope that it works.
Maybe afterwards flash a stock rom like nitrous rom and ##3282# reset and ##786# reset
**edit**
This one looks interesting too:
http://forum.xda-developers.com/showthread.php?t=1885208
If you could actually manage to find the nv.img file that would restore your evo, all you need to do is load the engineering hboot aka eng hboot,
then "fastboot flash nv nv.img" ( Without the quotes )
**edit #2**
Supposedly you can get a nv.img file from a PC36IMG.ZIP file, ruu maybe?
Anyways, this thread looks helpful too:
http://cdmagurus.com/archive/index.php/t-4567.html
Thanks for the advice. I'll look into these. I gave up for a few weeks cause Ive gotten too busy lately but hopefully it will be fixed soon
tenfour1 said:
Thanks for the advice. I'll look into these. I gave up for a few weeks cause Ive gotten too busy lately but hopefully it will be fixed soon
Click to expand...
Click to collapse
No problem. I actually had to fix a friend's evo a week ago that had this same problem. It already had S-OFF so I found an eng hboot that was inside a PC36IMG.zip file
After it had flashed, I put it back in bootloader and executed the fastboot command in my post above with the nv.img file you can find by searching google for "mik mik evo radio"
You want the one that says: Baseband 2.15.00.12.19, PRI 2.33_003, WiMax 27243 & NV 2.15_003
After I flashed the nvitems, it worked fine afterwards. Reflashed back to the carrier and all was well.
So Ive tryed a few things and Im stumped. I tryed to fastboot flash my nv.img and it never works. I tryed to put an original signed ruu into my sd card and it never flashes. I looked at trying to s-off but i cant seem to find a guide where I can do it with a bricked phone. Dont really know what to try next.