[Q] stock cant reboot nd recovery plz help - EVO 4G Q&A, Help & Troubleshooting

I did root my evo 4g hboot 2.18 radio 2.15.0012.19 and i try to downgrade but i get stock... cant do anything and i have no backup... icant get into the recovery and i cant reboot onle the htc evo 4g logo plz help to solve this problem. How Ido to fixed plz help..

eddi2004 said:
I did root my evo 4g hboot 2.18 radio 2.15.0012.19 and i try to downgrade but i get stock... cant do anything and i have no backup... icant get into the recovery and i cant reboot onle the htc evo 4g logo plz help to solve this problem. How Ido to fixed plz help..
Click to expand...
Click to collapse
Try this:
1. power down
2. remove battery
3. press and hold power button for 10 sec.
4. reinstall battery
5. press and hold the volume down button
6. press the power button to turn the phone on but DO NOT release the volume button until you can see the boot screen.
when you are in the boot screen one of the options in the list should say recovery. use the volume button to navigate down to that option and press the power button to select it. your phone should then boot into recovery and you will get the recovery screen and choices.

thanks
i did it but when i get into recovery i see the phone with the sing and then i reboot get stock in htc evo 4g logo if u have any idea how to get into the phone to flash any rom would b perfect tnx

Sounds like it could be a USB brick. This has happened to me before. I remember when that happened to me and couldn't get into recovery. For some reason when I plugged in the micro usb to the phone it would let me boot into recovery. Give that a shot and try searching usb brick. Also my sd card could not be recognized once I booted into recovery.

How did you try to downgrade?
Sent from my PC36100 using xda premium

ok well i flash 2 programs 1 flash_image 2 mtd-eng then run the pc36img but nothing happen it says cant roll back hboot n i reboot the phone n i went to the bootloader n it was locked n i try to enter to the recovery n show me the phone w/ the sing...

any idea where can i get an usb brick??

I'm not familiar with a USB brick, but I believe that your computer can still read your phone through USB. I see that you were trying to S-OFF the phone. Looks like something went wrong when you flashed the misc partition, which locked your bootloader once again.
You should try running an RUU file from your computer with your phone connected which can be found here.
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
But first, you will need to install the Fastboot drivers to your computer which can be found here
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
You need to run the RUU from your phone's bootloader from FASTBOOT USB (click on Fastboot then run the RUU from your computer).
If that works, that should at least get your phone back going again (unrooted of course).

i did but w/ the ruu doesnt work too appears error 155 unknow problem n stops i dont know what else to do

Just checking, did you run the RUU in FASTBOOT USB which should have been highlighted in red from your bootloader after clicking FASTBOOT? Also, with your phone connected to your computer while in FASTBOOT USB, check your computer's device manager from the control panel and see do you see anything under Android USB devices.
And too, which PC36IMG file did you try to run?

Sounds like you tryed to downgrade your hboot to the Eng hboot. If that is what you did, then congradulations! You have successfully bricked your device! Hboots are generally NOT downgradable...especially 2.18 to eng

{ParanoiA} said:
Sounds like you tryed to downgrade your hboot to the Eng hboot. If that is what you did, then congradulations! You have successfully bricked your device! Hboots are generally NOT downgradable...especially 2.18 to eng
Click to expand...
Click to collapse
Yea, I was afraid that the wrong PC36IMG file was indeed used. Generally on the newer phones, any downgrade of the Hboot below 2.02 is a guaranteed brick. That's why Captain Throwback only recommends PC36IMG files down to Hboot 2.10 (the 2.02 ones don't work with S-ON phones). On the older hardware however, the Hboot can be downgraded to anything, including 0.76 from 2.18. I've done it on mines. You just have to know which hardware version and partition erasesize your phone has.

the one that i get from evohacks pc36img i think i need one way to flash a rom

the one i get from a post in htcevohacks
is the pc36img
if i brick my phone is there any way to unbrick

eddi2004 said:
the one i get from a post in htcevohacks
is the pc36img
if i brick my phone is there any way to unbrick
Click to expand...
Click to collapse
The best advice that I can give you is to reboot the phone into FASTBOOT USB (connect it to your computer, then go to your bootloader and click on FASTBOOT), then go back to the HTCdev site, start over and try to re-unlock your bootloader. If you can do that, then I may have a workaround for you If not, there might not be much else that you can do.

ok i did everything that u tell me n now i rename the zip (ss_stock_4.67.651) in PC36IMG n then reflash recovery-RA-supersonic-v2.3 now i can get into the recovery menu n i flash the rename (ss_stock_4.67.651) PC36IMG n i have a rom from sprint but now i still cant use adb command so what else shuld i do to recovery to normal n there r many issues that cant load like mail that is forced to sptop unexpected n thank u for all ur help!!

in the command window type:
Code:
fastboot oem enableqxdm 0and then:
Code:
fastboot reboot

eddi2004 said:
in the command window type:
Code:
fastboot oem enableqxdm 0and then:
Code:
fastboot reboot
Click to expand...
Click to collapse
Oh no. I don't know which tutorial you got those instructions from.
I'm also lost with your description of what happened. I hope you unlocked your bootloader, and can now boot into the operating system. If so, you were not suppose to rename the ss_stock_4.67 file to PC36IMG. You were suppose to flash that through RECOVERY as is. If I were you, I would go back to RECOVERY, and wipe All Factory/Reset (or whatever it says) and Dalvik-cache, then reflash the ss_stock file or another ROM.
Second, the adb commands only work from the operating system, not FASTBOOT. You need to be inside the operating system with your phone connected to your computer and USB Debugging enabled under Settings/Applications.

ok here i am
i change the name cos the bootloader let me flash the recovery amon ra 2.3 then i can see the recovery menu n i flash the rom named pc36img n give me the sprint w/ errors now i download another rom that i flash n now my computer can read the sdcard but im still locked n i dont know if im still rooted so the what i think is i have a usb brick so i need to unbrick my usb to use the adb command so i apreciate ur help w/ this thanks all of u for ur help

Related

Unroot with broken power button

I've been trying to follow
http://forum.xda-developers.com/showthread.php?t=835971
But in order to go into bootloader, i need to hold volume down and power (Which is broke)...
What i tried was, "adb reboot bootloader"
which goes in bootloader but doesn't scan like the guide says... and from there i'm lost.
Any help is appreciated.
oh wow. so you cannot manipulate your power button at all? no tweaking or pushing in with something else (is the button still there or did it break off?
warning -- do not do this -- im just trying to be helpful but I am probably not.... dont do this on my account.
well im looking in TJWorld... please dont do this without a real dev taking a look at this
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess#FastBootRestart (Chain Operating System down 1/4 of the way)
in so many words connect serial-usb-to control Hboot (need linux host)
screen /dev/ttyUSBO
press enter till you see "hboot"
and then basically I guess just like in GOTO language
gotofastboot
or
gotohboot
and then theres OEM Reboot Codes
-reboot=oem-1F Regular reboot
--reboot=oem-42 HBoot menu
--reboot=oem-74 In some indeterminate state, for all intents and purposes powered off or just plain dead
--reboot=oem-76 Wipe data and cache (factory reset) Amber and Green LEDs flash whilst it is doing it, then the device reboots
--reboot=oem-78 ??
I hope this helps at all..
The buttons there, you can press it as hard as you want but nothing. Just no response
I have this exact problem!! It's been sitting in my room collecting dust. If anyone can find a fix.. a cup of coffee on me!
My power button is also in perfect condition, I've compared it to another G2 and the button's "press feel" is exactly the same.
why dont you just remap the keyboard and map the camera button as power
^^ i thought the power button combo is not remappable....
and that Its only mapped within android not for the default system combos
Do you have CWM? If so, the phone should turn on when it is plugged into a power source.
^^ Do have CWM, problem is not the phone turning on... the problem is I have no usable power key to follow the guide to unroot and put a stock rom on so i can send it in for warranty.
Using keyboard I can turn on the screen so thats do-able... but restoring to stock + removing root is what I'm trying to ultimately achieve.
i think theres an app thts called quick boot maybe tht could help...
Could you not flash the zip file from within rom manager. By selecting install rom from SD Card, you avoid needing to use powerbutton to get into bootloader. Correct me if you cant do this.
I tried flashing from CWM and error... rom manager didn't reboot it to CWM to flash, so not sure what to do.
This is what I have tried --
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
on hex editor the version is 1.19.531.1, and it already was so i didn't need to change it. But when i try putting that zip through cwm it doesn't work.
I've tried adb reboot bootloader , but it doesn't scan for PC10IMG which i downloaded from the guides....
Torob said:
I tried flashing from CWM and error... rom manager didn't reboot it to CWM to flash, so not sure what to do.
This is what I have tried --
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
on hex editor the version is 1.19.531.1, and it already was so i didn't need to change it. But when i try putting that zip through cwm it doesn't work.
I've tried adb reboot bootloader , but it doesn't scan for PC10IMG which i downloaded from the guides....
Click to expand...
Click to collapse
Which version CWM have you got on there? If its 3.0 I dont think you can flash a froyo rom with that. You would have to install an earlier version.
You can remap the power button with the button remapper app it cost 1.04$ it works fine for me even if you turn off your phone u can use camera button to turn it on, I got the app for free if u dnt want to spend but I cannot post the apk I'm using my phone right now just search it on google beansoft button remapper
http://forum.xda-developers.com/showthread.php?p=11021708#post11021708
My posted app.. hope this helps
i don't think remapping keys will work. It's a hardcoded thing the power+volume key during boot. What i don't get is the fact that hboot doesn't find the file. did you rename it to PC10IMG.zip?
thats the only filename hboot understands as an update or new rom. (Be shure to follow the original guide)
edit: tried myselve.. it doesn't go to hboot does it.. you have to select with powerkey
how can we just make the phone crash? to leave no trace of root or anything of the sort.
Possible solution
Hi !
While I am still thinking about a solution how you could boot into hboot (by using adb reboot bootloader you boot into fastboot mode and not hboot mode) the following might be a solution.
I can not test it because I don't have windows but this is what might work:
1. You need windows and you need the USB drivers from HTC Sync (You can get that here http://www.htc.com/uk/supportdownloadlist.aspx?p_id=325&act=sd&cat=all
2. You need a Desire Z RUU:
You can get one from here http://shipped-roms.com/index.php?category=android&model=Vision
Select any WWE I would probably use RUU_Vision_HTC_WWE_1.22.405.1_Radio_12.26.60.1301_26.02.00.24_M2_release_151197_signed.exe
3. You need the G2 Stock ROM zip, i.e PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
The procedure is the following:
1. Install the HTC Sync so that you have the USB Drivers installed
2. Start the RUU and let it do it's job until the Welcome Screen apears.
At this moment you should have a directory in C:\C:\Documents and Settings\<your user>\Local Settings\Temp\{some-CLSID}\{another-CLSID} that contains a file called rom.zip.
Delete this file and copy the PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip to the directory and rename it to rom.zip
3. Connect you phone to the USB and on the welcome screen check the checkbox and continue.
If I am right the RUU should update your phone using the G2 rom.
As said, I am blind driving cause I ain't got Windows but this might work.
have fun Guhl
ACMilan07 said:
how can we just make the phone crash? to leave no trace of root or anything of the sort.
Click to expand...
Click to collapse
Well there is an option if you do have the engineering hboot installed.
DO NOT TRY THIS BECAUSE THERE IS NO RECOVERY FROM THIS BRICK
1. boot the phone into fastboot mode by using
Code:
adb boot bootloader
2. use fastboot do completely erase the emmc
Code:
fastboot oem fdisk_emmc
After this the phone will be completely erased and will not even know that it is a phone anymore. You can send it in and have it replaced and no one will ever know how your phone got bricked like this
And again: There is no way to recover from this state !!!
Torob said:
I've been trying to follow
http://forum.xda-developers.com/showthread.php?t=835971
Click to expand...
Click to collapse
Last thing I wanted to add is that the probably better way to unroot and go back S-ON, CID and restore SIM-Lock is described in the wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Returning_to_Stock
guhl99 said:
Well there is an option if you do have the engineering hboot installed.
DO NOT TRY THIS BECAUSE THERE IS NO RECOVERY FROM THIS BRICK
1. boot the phone into fastboot mode by using
Code:
adb boot bootloader
2. use fastboot do completely erase the emmc
Code:
fastboot oem fdisk_emmc
After this the phone will be completely erased and will not even know that it is a phone anymore. You can send it in and have it replaced and no one will ever know how your phone got bricked like this
And again: There is no way to recover from this state !!!
Click to expand...
Click to collapse
SO THIS WILL WORK?? THERES NO WAY FOR THEM TO FIND OUT IT WAS EVER ROOTED??? im in shock, seriously?
***EDIT***
DOES NOT WORK. Anything else specific?
ACMilan07 said:
SO THIS WILL WORK?? THERES NO WAY FOR THEM TO FIND OUT IT WAS EVER ROOTED??? im in shock, seriously?
***EDIT***
DOES NOT WORK. Anything else specific?
Click to expand...
Click to collapse
This does not work?
Do you have the engineering hboot installed? (hboot or fastboot has to say VISION PVT ENG S-OFF)
Does
Code:
fastboot oem ?
show INFOfdisk_emmc ?

Recovery, System, data ... not Allowed

Hello,
First of all I am very null in English, so I use the google friends ... Sorry
Well this is not the first time I flash a phone, but in WinMobile I find myself in the ....
I have a htc desire PVT3 S-OFF that do not boot the system (sense) or on the recovery, .. because I install a rom (supernova) and since I have a white screen htc.
I try to put my recovery and re-flash my boot my system, the adb command fastboot and me but also his brand:
fastboot:
Failed remote: not allowed
ADB:
No devices conected
Install the driver and that of UnRevoked (HBOOT Driver)
I saw you can get it through linux, but I did not and I would really avoid because I do not have my pc at the moment and it was my job that I did everything ... I am admin on the pc ...
....
If it please you help me ... its been 2 days now ...
Any fair to have space and android 2.3 ... heck
Thank you in advance
so ummm
switch your phone off
turn it on holding 'power' + 'back' buttons
this will take you to the bootloader, now using volume up and volume down buttons navigate on 'recovery' and hit power button
this should launch recovery
report back
report:
White screen htc ... Even after 1 hour ..
Already tried last night for a restaurant
AND
I forgot to tell you that the supernova rom I downloaded was corrupted ...
Result: more than clockwork and system ..
ok so here is what i would do:
make sure my ADB is set up correctly @ my PC, then try putting my phone in fastboot mode (back+pwr) and flash a recovery image.
if that wont work, make sure it is not an USB-Brick (if your wall charge starts as soon as you plug phone then its OK)
finally put phone into fastboot mode and run a RUU.exe @ PC ?
this should bring it back to stock, unroot and S-ON again
if your phone is branded, you might need to create a goldcard, also make sure you use a correct RUU.
other than that i got no ideas on how to help you.
I do not think it is a USB-BRICK, because the first driver install is that of htc and then when I go into the same phone with fastboot the only difference is that ... Finally I think I am no longer in ROOT ...
When I try the command "fastboot update file.zip or .img or fastboot recovery .zip or .img or when fastboot boot .zip or .img gives me every time:
Failed remote: not allowed
then the RUU already try but actually I do not know if it's good, (that of XDA)
Finally a Goldcard I do not know what it is nevertheless my phone was already rooted UnRevoked thanks ..
I do not know if it's important
you think that I can one day recover my phone? ....... :'(
In fact there are fastboot that happens to connect to my phone adb do not recognize either the UCP and UnRevoked either ...
and no firewall or antivirus
WOOOOOOOOW I managed to start the RUU thank you very much ... In reality it was a driver problem ....
Today I'm under Win XP and Win in the last 7 64bit and I think it's because of its ...
I would give you the news
Thank you again because I would not continue with the RUU
Good but now that I install the RUU I'm not as root?
runnign a RUU will revert your phone back to stock
no root, S-ON
from there you can root it again, and S-OFF
and you should be fine
ok but I'm still S-OFF ... So it mean anything?
S-ON or S-OFF and what diference?
I know it's safety but his hand?

Stuck in Hboot, pc36 & recov not working

Hello,
I've been rooted for over a year now. Have flashed back and forth roms around hundreds of times now. Unfortunately an hour after flashing synergy godmode and some of the godmode tweaks, my phone rebooted while idling and bootloops.
Now i am stuck in hboot and can not enter recovery. I am using hboot 0.76.2000 (pc3610000) and s-off. I have tried flashing seperate clockwork and amon-ra embedded pc36img.zip, these say that they will complete updating but then will bootloop after i try to enter recovery. I have tried these updates with a different sd card (as my current sd card w/godmode may be an ext2 partition?) but that has not changed anything either.
As i understand, I can only push files with adb through recovery; which i can not get into.
If anyone can please help it would be very much appreciated.
Thank you in advance
try this way? its how i flash my recoveries when im switching or testing...
remove any pc36img.zip files from your sd and boot to your bootloader...
when you bootloader boots up let it scan for the pc36img whatever thing and let it say not found...
now highlight fastboot and click the power button and wait for FASTBOOT USB to show up...
then type in these codes...
Code:
fastboot devices
it should output some info, if you get some serial number then your good
then type in...
Code:
fastboot flash recovery *whatever the name of the recovery your using is*
so like for amon_ra 2.3 (which is what i use is)
Code:
fastboot flash recovery recovery-RA-supersonic-v2.3.img
just make sure that the recovery img file is in the same directory as the fastboot.exe file on your comp (its should be with all your other sdk stuff like adb.exe and such)
if all goes well then itll say
pushing recovery OKAY
writing recovery OKAY
and the amount of time it took...
then click back into your bootloader and go to the newly written recovery
(i apologize in advance if you already tried this with no avail)
I've set up fastboot usb and done this. Everything wrote ok and finished, however i still bootloop when trying to access recovery. I have tried multiple recoveries including clockwork 3, recovery-RA-supersonic-v2.3.img, and doing entire nandroid restores using nandroid recovery batch script. In both cases everything passes and nothing seems to be functional afterwards.
Any other ideas?
dunno man.. im just trying to visualize how it bootloops going to recovery.. it should be the white htc screen (or any other splash you may have set on there) and then boink recovery... does it like just sit there on the splash and thats it?
try letting it boot normal and then when it goes to the rom loading screen type in
Code:
adb reboot recovery
other than that something is totally askew bro
When booting, i'll get the white htc screen for 4-5 seconds, then it'll power off and reboot, unless i boot to hboot. When i hit recovery, it goes black for a second, then reboots to htc screen and repeats.
I've also tried complete wiping recovery and reloading using fastboot commander, and doing full pc36img.zip that include hboot, radio wiimax updates etc http://forum.xda-developers.com/showthread.php?t=830153&highlight=wimax
I may just go into a sprint store today. Was trying to avoid it as I really don't want to be stock again.
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
the only hboot that allows fastboot commands is 0.76 unfortunately
try running an ruu maybe? other than that i havent the slightest idea
I used this RUU - http://forum.xda-developers.com/showthread.php?p=7529500
It passed every step, but still bootloops when booting to ROM and Recovery.
I'm out of ideas....
I'm going to go with hardware problem.
Sent from my PC36100 using XDA Premium App
bad sector on the internal flash memory ?
My brother has the same problem and i have been trying to fix it with no luck. When i boot the phone up its beeps/vibrate 5 times, then sits on a black screen. I can get into hboot and load pc.....whatever files, it says they work but still reboot, 5 beep, ect. I was going to try an RUU next i see that didnt work for op.
i just ran into this problem today. I was at work when it randomly rebooted and now is stuck in a bootloop. i have tried everything even using the latest RUU. it finished but still bootloops. I am also not able to get into recovery. Sucks because im out of warranty.
So let me get this straight...you can't go into recovery because there's no recovery? You've installed drivers and ran RUU and still nothing? That seems weird because i had the same issue when i first rooted my phone with unrevoked, all i did was run the RUU and it restored my phone back to "stock" and i re-rooted again but this time using z4 root. You might just have to take the phone back to Sprint
Same issue but worse
I'm having the same issue as the OP except that my buttons (power and volume up/down) will not respond. I have scoured these and other forums for a situation like mine and have found none.
I have tried flashing recoveries, RUU's and jsut about anything someone says.
First screen says:
supersonic evt3 ship s-off
hboot-2.10.0001
touch panel atmelc03_16ac
oct 15 2010 12:01:00
hboot
fastboot
recovery
clear storage
simlock
hboot usb
then it scans the sd card for the pc36img zip. It will load but will freeze on the next screen:
parsing...... [sd zip]
1. boot loader
2. radio
3. boot
4. recovery
5. system
6. user data
7. splash
8. wimax
it will stick here and I am completely lost. My old Palm Pre will only suffice for a day.... max.
If anyone has come across a situation like this that might help me, would you please point me in the right direction. Thanks!
kdbrown5 said:
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
Click to expand...
Click to collapse
If you look in autoroot thread in my sig the "tools" zip has something that will let you flash different partitions from fastboot. If you use that to flash the PC36IMG from here it will give you the eng hboot back and possibly reflash whatever got corrupted.
Keep in mind, that will only work properly if you are not using one of the 2.xx hboots. Only phones with a 0.9x hboot will let you use it.

Stuck in bootloader, S-ON, clockworkmod can't mount sdcard....bricked?

I've been running CM7 on my phone for quite some time along with SOS and recently the latest CM7 from here. Somehow my phone appears to be bricked. Perhaps from a faulty nandroid that I restored? It goes into bootloader but I can't do much there. When I select recovery I get the 5 vibes of death and black screen. I can get to CWM with USB connected, but CWM can't mount the sdcard. And somehow I noticed I have S-ON. I originally rooted with unrevoked. Can anyone offer any advice on how to proceed?
Flash Amon Ra. CWM is just not a good recovery with the Evo, but even so, with AR, I've had my recovery get corrupted twice with the same error you're having (Both times were after the only 2 times I ran a superwipe) and had to reflash my recovery, which fixed it.
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like here?
ogp said:
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like here?
Click to expand...
Click to collapse
Yes.This is a good site to get what you need.
ogp said:
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like
Click to expand...
Click to collapse
not bricked
Your recovery is corrupted. Just place the PM36IMG in the root of the SD Card and as soon as you PWR+Vol- your phone will rub the update package and you will then be able to enter recovery. If you phone turns on, it's not bricked. There is always a way to fix it. Message me at any step you get to and if your phone won't go any farther I will message you back with the solution.
Ok, so I've copied that file to my sdcard and booted. hboot sees the file and it appears to load with a vertical blue indicator to the right. But I never get any prompts to install. Once the indicator completes, it goes back to the hboot menu. Will this not install because I have S-ON?
Ahh, well, yeah, I didn't know you were S-on. You have to be S-off to flash a custom recovery
Ok. I'm not sure how I got S-ON. I'm pretty sure it was off so I could flash CM7 and CWM, etc. Anyway, can I easily turn it off?
I've got hboot 2.10.0001
Radio 2.15.00.11.19
I can get it to boot into CM7 but it won't recognize the sdcard.
I can't seem to get my phone working with adb. I have adb enabled and when I connect my usb cable to my phone and laptop, the phone says debugging enabled but my laptop can't talk to it via adb. I also tried to ensure hboot drivers are installed and I still show android bootloader interface in device manager. When I boot into bootloader and select hboot usb and then connect my usb cable, it shows hboot usb plug but adb devices still shows nothing connected. So my sdcard and usb seem to not be working properly.
What can I load via hboot with S-ON? I've tried to update the radio as well as loading a rooted stock rom by loading the files on my sdcard as PC36IMG.zip. hboot sees them and loads/checks them, but I never get the option to install. I even tried stock 1.32.651.1 and it loads and checks but I still don't get the option to install.
Nothing. You need to run the RUU, either via pc36img or by the exe on your computer, re-root, and then flash recovery
Could there be something wrong with my bootloader? I tried to run this RUU and it definitely gets loaded and checked, but I never get the option to install. It just goes back to the bootloader menu. Any ideas why I don't get the option to install? Is the RUU version too old for my phone/bootloader version? I don't think I can run the .exe since I'm having a difficult time getting my phone to talk to my pc via USB.
So I was able to get it to show up in adb by booting into bootloader and selecting hboot usb and then going into recovery. When I try to run unrevoked3 I get the error Device "/sbin/sh: getprop: not found" is not supported at this time.
I think you'll need to run Revolutionary, although it's been so long since I rooted, or follwed rooting processes, I'm not sure, based on your Hboot version, but that determines which root process you'll need to use.
Sorry this is dragging on so long.
Also, jump on IRC, Freenode #htc-evo.
Those guys are great at helping people out
My phone is still rooted, it just has S-ON for some reason. I looked at Revolutionary but wasn't sure that applied since my hboot version, 2.10.0001, isn't listed in the options and I'm having trouble talking to my phone via usb/adb.
HipKat said:
I think you'll need to run Revolutionary, although it's been so long since I rooted, or follwed rooting processes, I'm not sure, based on your Hboot version, but that determines which root process you'll need to use.
Sorry this is dragging on so long.
Also, jump on IRC, Freenode #htc-evo.
Those guys are great at helping people out
Click to expand...
Click to collapse
No one on IRC seems to have an input....
ogp said:
No one on IRC seems to have an input....
Click to expand...
Click to collapse
First, you have the wrong drivers installed to run any RUU (not PC36IMG). You need Fastboot drivers, not Hboot drivers from here. (INSTALL IT TO YOUR COMPUTER).
http://www.4shared.com/get/InLGg_UI/HTCDriver300007.html
Second, you have the wrong PC36IMG file (not RUU) for your Hboot 2.10.
Either one of these files should work for you to unroot since they each have the same Hboot 2.10.
http://shipped-roms.com/download.ph...15.00.11.19_NV_1.90_release_161482_signed.exe
http://goo-inside.me/stock/superson...15.00.11.19_NV_1.90_release_161482_signed.zip
Third, you will need those Hboot USB drivers you installed in Hboot USB to run unrevoked (the reflash program) from your computer, not recovery. Make sure when you go to Hboot USB (by clicking on Hboot in the bootloader and observing "Hboot USB" highlighted in blue, not just "Hboot" highlighted) with your phone connected to your computer, that your device manager still reads "Android Bootloader Interface", or you will have to reinstall them (in "Hboot USB").
The unrevoked reflash program (not unrevoked-forever) can be found from this link.
http://downloads.unrevoked.com/recovery/3.32/reflash_package.exe
Reboot back into your phone's operating system, then run the unrevoked program, and you should be OK.
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
ogp said:
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
Click to expand...
Click to collapse
Try pulling the battery. Can you get into the bootloader, and also, can your computer still read the phone after a battery pull and trying to boot into the bootloader or trying to boot into the operating system?
ogp said:
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
Click to expand...
Click to collapse
Uh-oh. You might need to end up doing this:
http://forum.xda-developers.com/showthread.php?p=21765954#post21765954

[Q] Revolutionary Rooted stuck in boot loop no recovery

Help. My phone is stuck in a boot loop. No recovery, won't take one even when I flash multiple ways. Won't take a rom. S-off. Was rooted with Revolutionary, but since it wouldn't take a ROM or recovery I tried to unroot. Was able to remove the "Revolutionary" watermark, change hboot from 6.16 to 2.16.0001. Tried installing ruu which is what removed the Revolutionary and changed back hboot.
Here's what I have now:
Supersonic evt2-3 ship s-off
hboot 2.16.0001
Radio 2.15.00.0808
Any help! Thanks.
Looks you might have to get a PC36IMG.zip on your sdcard and then flash that through bootloader
Ideally, put on a froyo PC36IMG so that rerooting is easier if you want to do it again
So what happens when you try to select Recovery from Hboot?
The advice is free....the bandwidth, not so much
Still boot looping...
CNexus said:
Looks you might have to get a PC36IMG.zip on your sdcard and then flash that through bootloader
Ideally, put on a froyo PC36IMG so that rerooting is easier if you want to do it again
Click to expand...
Click to collapse
Already tried that...
FinZ28 said:
So what happens when you try to select Recovery from Hboot?
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
All I get is the white "HTC EVO 4G" boot screen. When I flash a custom recovery, everything goes as expected, but still can't access recovery.
You will have to go through all the bootloader ruu's till you find the one that works. Good luck I had the same issue and ended up selling it on eBay and the buyer finally got it working.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
You will have to go through all the bootloader ruu's till you find the one that works. Good luck I had the same issue and ended up selling it on eBay and the buyer finally got it working.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Ok. I tried every ruu I could find. Problem remains. Also, s-off never turns to s-on. Tried flashing contents of stock rom separately. Everything appears to flash ok, but same result: no recovery, no rom. Any ideas?
What I think I need is a method to nand unlock via fastboot or hboot. Anyone know of such a thing? Anyone have any other ideas? Besides what I've already done? Thanks...
mabulok said:
What I think I need is a method to nand unlock via fastboot or hboot. Anyone know of such a thing? Anyone have any other ideas? Besides what I've already done? Thanks...
Click to expand...
Click to collapse
S-off is nand-unlocked...run an ruu (any version), as soon as it opens, press windowsKey+R and type "%temp%" then *enter
Now sort the files by date modified and search in the most recent folders for a file called "rom.zip", as soon as you find that copy it to your desktop
Rename the rom.zip to "PC36IMG.zip" and place it on the root of your phones sdcard (you may need to reformat your sdcard to FAT32, make a backup if you need to do this)
Now put the sdcard in your phone, pull out the battery and go into bootloader (VolDown+Power) , the bootloader should find it and commence the update process back to stock unrooted, follow the prompts and press power when necessary
Okay, tried that...
CNexus said:
S-off is nand-unlocked...run an ruu (any version), as soon as it opens, press windowsKey+R and type "%temp%" then *enter
Now sort the files by date modified and search in the most recent folders for a file called "rom.zip", as soon as you find that copy it to your desktop
Rename the rom.zip to "PC36IMG.zip" and place it on the root of your phones sdcard (you may need to reformat your sdcard to FAT32, make a backup if you need to do this)
Now put the sdcard in your phone, pull out the battery and go into bootloader (VolDown+Power) , the bootloader should find it and commence the update process back to stock unrooted, follow the prompts and press power when necessary
Click to expand...
Click to collapse
Tried your method using the rom from an ruu. Still s-off, although everything appeared to have updated. I've done this previously, but not extracting the rom.zip from an ruu. Each time the hboot updates, or downgrades, depending on the ruu, but s-off remains. No rom, no recovery...
Next...
Sometimes the problem is solved by wiping the recovery partition first, and then re-flashing it. To do that, you would need a Hboot where you could run fastboot commands, since you cannot boot into a Rom.
You can try upgrading your Hboot, then unlocking the bootloader using the Htcdev site, so that you can run the fastboot commands. If it fails on the new Hboot, then it can probably be flashed back to whatever Hboot you have, since you're S-OFF.
I've included the Hboot file that you would need for the upgrade. You would first run the PC36IMG file throught the bootloader, then reboot the phone. If the Hboot changes, then you should go to the Htcdev site and try to unlock the bootloader.
There are some other steps that follows, but there's no point of giving them to you now and complicating things unless the initial steps work first.
Update
shortydoggg said:
Sometimes the problem is solved by wiping the recovery partition first, and then re-flashing it. To do that, you would need a Hboot where you could run fastboot commands, since you cannot boot into a Rom.
You can try upgrading your Hboot, then unlocking the bootloader using the Htcdev site, so that you can run the fastboot commands. If it fails on the new Hboot, then it can probably be flashed back to whatever Hboot you have, since you're S-OFF.
I've included the Hboot file that you would need for the upgrade. You would first run the PC36IMG file throught the bootloader, then reboot the phone. If the Hboot changes, then you should go to the Htcdev site and try to unlock the bootloader.
There are some other steps that follows, but there's no point of giving them to you now and complicating things unless the initial steps work first.
Click to expand...
Click to collapse
Ok. This didn't work. I was able to flash the hboot, but fastboot commands did not work. I can unlock, and relock the bootloader, flash any ruu, but s-off remains, and still unable to flash a rom or recovery.
Try this and see what happens: Unzip the fastboot.zip file in side a folder on your computer and place the recovery.img file in that same folder on your computer, then open a command prompt from that folder (shift + right click+"open command window here"). From the FASTBOOT USB menu on the phone (Hboot + click on FASTBOOT): type
fastboot erase recovery <ENTER>
fastboot flash recovery recovery.img <ENTER>
fastboot reboot-bootloader <ENTER>
shortydoggg said:
Try this and see what happens: Unzip the fastboot.zip file in side a folder on your computer and place the recovery.img file in that same folder on your computer, then open a command prompt from that folder (shift + right click+"open command window here"). From the FASTBOOT USB menu on the phone (Hboot + click on FASTBOOT): type
fastboot erase recovery <ENTER>
fastboot flash recovery recovery.img <ENTER>
fastboot reboot-bootloader <ENTER>
Click to expand...
Click to collapse
That didn't work either...

Categories

Resources