Related
'hey guys/girls.
Im new at installing custom ROMS and all that.
I got my desire rooted with unrevoked 3.0 and it worked fine.
I installed a custom ROM and it worked fine,but i didnt like it so I tried a new one.
I can´t remember the name of it but I didnt like that either. Again i found a new ROM i´d like to try but when I turn off my phone and turn it on again trying to get to Hboot/recovery mode or what its called nothing happens i just stay turn off until i remove my finger from volume down buttom, then it just start then phone normally.
Do any one know what to do?
There are a couple of ways.
Way 1
1) Turn off your phone
2) Hold vol down + power until it loads the bootloader
3) When it's finished checking SD card, move to recovery using volume keys and press power to select recovery
4) It should load into recovery
Way 2
1) Have the Android SDK installed with the platform-tools downloaded and working
2) Make sure you plug your phone cable in your phone and PC
3) Open up command prompt or terminal (depending on your OS)
4) Type "adb reboot recovery" (no quotes) and it will reboot to recovery.
i have similar problem, cant access recovery anymore. that happened after installing a custom rom (leedroid). when i try to access recovery phone just hangs up on that red triangle. to turn it on again i have to pull of the battery. btw, phone works normaly itself only problem is that i cant access recovery to install some other rom :/
Drunk Moose said:
i have similar problem, cant access recovery anymore. that happened after installing a custom rom (leedroid). when i try to access recovery phone just hangs up on that red triangle. to turn it on again i have to pull of the battery. btw, phone works normaly itself only problem is that i cant access recovery to install some other rom :/
Click to expand...
Click to collapse
The red triangle is the stock recovery, so you're actually in recovery there.
Download a recovery and read this. Should get recovery back on your phone again.
but i had normal recovery i installed dozens of custom roms :/ and now phone just stucks in that screen with phone and triangle :/
How the hell can you install custom roms with the stock recovery.
thats the point, i had normal recovery and now i cant access it im using custom roms from the times desire was released and now almost after a year this **** happened :/
Ok... 2 posts ago I linked you to an article that can get the a custom recovery back onto your phone.
can u explain me info in that link a little? what .zip file do i need and where to get it? and WTF is terminal?
1) Download Clockwork Recovery or if you have PVT4 download Amon_RA (GSM)
2) Put it on your SD card
3) Download terminal emulator from the market
4) Type "su" (without quotes) and press allow when it comes up
5) Type "flash_image recovery /sdcard/recovery.img" (without quotes) and it will write the file to your phone.
To check which PVT you have, boot into bootloader. Turn off phone and hold vol down + power.
installed better terminal emulator pro. downloaded img, renamed it to recovery, inserted it to sdcard in terminal typed:
su (enter)
flash_image recovery /sdcard/recovery.img (enter)
and terminal says:
flash_image: not found
Did you put the img into a folder?
no, in the root of sd card
Weird. I don't know. Just tinker around with it. I tried it once and it worked for me. Check spelling, check in a file manager to see if the file is there.
i think i get this. thing is my rom does not have flash_image. now looking how to get it.
yep, there is no flash_image in system.
Are you using the new Sense ROMS/Gingerbread? If so 'Fast Boot' mode will screw with getting into recovery. I have to hold down volume while replacing the battery or turn off fast boot from within settings....
OFC if you have no recovery image anymore this won't help one little bit
KYI
yes im using new leedroid gb. i turned off that fast boot, its not that :/ now trying to push flash_image through adb, but it says "failed to copy....bla bla bla...: out of memmory" getting little desperate
If I was you I would back everything up. Contacts, SMS all that good stuff. I would then use an RUU and get the stock rom back on and just root that. Could of done it by now really.
Ok 2 problems:
1. to the topic starter. The reason you can't access recovery is that your rom uses fast boot up(sleep mode). When this is activated the phone doesn't really shut down when you tell it to, so it also cannot actually enter recovery or fastboot. Just turn it off in the settings menu and you'll be fine.
2. to Drunk Moose.
You have the original htc-recovery installed. I bet that you rooted back before unrevoked, and you probably have been using fakeflash since then. Try making rom manager dl cwm and choose reboot to recovery from rom manager. It should enter clockwork mod. If that is the case, this means that your phone have a modified version of the stock recovery, which allows test-keys. if that is not the case, and you still get the triangle, you somehow overwrote your recovery with a stock one.
Either way to fix this, you need to replace the recovery image with a cwm one. This can only be done in 2 ways for the desire:
1. Use unrevoked even though your phone is rooted and it'll flash it using a known exploit.
2. run alpharev to gain s-off. When you have s-off you will be able to flash the recovery through fastboot or from the system like described by meaple.
The reason it doesn't work for you when you do like meaple descriped, is that the commands tell the phone to use a custom binary called flash_img and passes it the parameters "recovery" and the "recovery.img" file. Then the binary will tell the android system how to write the img file to the recovery partition(it cannot do this entirely by itself). However this bynary is very unlikely to be included on your rom(like you figured out yourself ), so you need to place it somewhere you can access it from the terminal. And even if you had had the file, you wouldn't have been able to do so, as the recovery partition is write-protected doing runtime, when you are s-on.
So I'll recommend that you do one of the 2 mentioned solutions(I'll be glad to provide further help)
edit: and for god sake don't just flash a ruu every time you are in doubt... There are almost certainly an easier solution, and by doing s-off, you can avoid ever having to run a ruu again, as you can restore the system 1 partition at a time if you feel like it.(sorry this was not directed at you but people in general, as meaple just suggested doing so)
in fact i was just trying to use unrevoked bu it stucks on bootloader, tells to check for drivers, despite the drives is installed. :/
p.s. and yes i have rooted my desire almost a year ago there was no unrevoked
any other suggestions? or just try to install ruu?
and about the rom manager, it gets me to the same red triangle. btw the recovery was fine till i installed leedroids rom about a month, and i noticed it only few days ago, when i tryed to update my rom.
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.
okay, well i've done my share of research on these forums and others, and attempted recovery of this phone a few different ways, and nothing is working. i'll tell you everything i know and have tried, and unless i forget something, i'm at a loss for what else to try.
booting the phone regularly, it sticks on the HTC Incredible boot screen.
pressing power and volume down, i can get to hboot. hboot says:
incrediblec xd ship s-on
hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
radio-2.15.10.07.07
Jul 23, 2010, 10:06:51
HBOOT
<VOLUME UP> to previous item
<Volume down> to next item
<power> to select item
Fastboot
recovery
clear storage
simlock
factory reset
all options but fastboot/simlock vibrate once on reboot and return to HTC Incredible screen
simlock, well i'm not needing i reckon
fastboot brongs up the fastboot menu
bootloader
reboot
reboot bootloader
power down
bootloader returns to hboot
reboot reboots phone
reboot bootloader turns screen black and returns to fastboot
power down (obvious)
fastboot can be booted directly with joystick and power as normal.
i have flashed a PB31IMG with the stock gingerbread on it from hbbot, that goes through the upgrade procedure, and asks me to reboot when its done, but it still sticks at the white screen.
ive tried installing CWM's and the stock recovery from pvillecomp*com
phone reads zip, then returns to hboot menu with no action taken
card is formatted fat 32, yes.
Well you wont be able to flash CWM because of it being S-On. If you were stuck at the HTC screen prior to you trying all of this, it may be a hardware related issue.
U havto reroot (s-off) in order to flash a rom. Try rerooting.
Inc
You would need to downgrade to Froyo to be able to root your phone....
jackbtha1 said:
You would need to downgrade to Froyo to be able to root your phone....
Click to expand...
Click to collapse
i'll try the froyo image from pvillecomp and post back my results
Main Version is older!
Update Fail!
Do you want to reboot device?
<vol up> Yes
<vol down> No
cablemirc said:
Main Version is older!
Update Fail!
Do you want to reboot device?
<vol up> Yes
<vol down> No
Click to expand...
Click to collapse
Unfortunately in order to downgrade your phone needs to be bootable I believe.
jackbtha1 said:
Unfortunately in order to downgrade your phone needs to be bootable I believe.
Click to expand...
Click to collapse
expensive brick, if so.
cablemirc said:
expensive brick, if so.
Click to expand...
Click to collapse
Yup. I've seen a few Inc that randomly started rebooting and then it stays stuck at the HTC screen. They all turned out to have hardware issues and they are were AMOLED Inc as well. I hope this isn't the case with yours.
cablemirc said:
okay, well i've done my share of research on these forums and others, and attempted recovery of this phone a few different ways, and nothing is working. i'll tell you everything i know and have tried, and unless i forget something, i'm at a loss for what else to try.
booting the phone regularly, it sticks on the HTC Incredible boot screen.
pressing power and volume down, i can get to hboot. hboot says:
incrediblec xd ship s-on
hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
radio-2.15.10.07.07
Jul 23, 2010, 10:06:51
HBOOT
<VOLUME UP> to previous item
<Volume down> to next item
<power> to select item
Fastboot
recovery
clear storage
simlock
factory reset
all options but fastboot/simlock vibrate once on reboot and return to HTC Incredible screen
simlock, well i'm not needing i reckon
fastboot brongs up the fastboot menu
bootloader
reboot
reboot bootloader
power down
bootloader returns to hboot
reboot reboots phone
reboot bootloader turns screen black and returns to fastboot
power down (obvious)
fastboot can be booted directly with joystick and power as normal.
i have flashed a PB31IMG with the stock gingerbread on it from hbbot, that goes through the upgrade procedure, and asks me to reboot when its done, but it still sticks at the white screen.
ive tried installing CWM's and the stock recovery from pvillecomp*com
phone reads zip, then returns to hboot menu with no action taken
card is formatted fat 32, yes.
Click to expand...
Click to collapse
sounds like the partitions are mess up. try flashing hboot again to get them to set right. then RUU.exe to get the stock GB back on then try to boot. you will loose any data on the phone with RUU.exe but it might get you a working phone again.
jackbtha1 said:
Yup. I've seen a few Inc that randomly started rebooting
Click to expand...
Click to collapse
mine's never done any random reboots.
synisterwolf said:
sounds like the partitions are mess up. try flashing hboot again to get them to set right. then RUU.exe to get the stock GB back on then try to boot. you will loose any data on the phone with RUU.exe but it might get you a working phone again.
Click to expand...
Click to collapse
the hboot reflash reads the PB31IMG.zip and returns to hboot screen without offer to reflash. the hboot is .92, as is the version i'm trying to flash. and again, sd card IS fat32.
i used the ruu sucessfully, got all excited to see the new HTC screen in black with the loading bar, but when the flash finished, rebooted the phone, it's still stuck at the white screen. major downer.
no other ideas? paperweight? parts?
Hmmm I am having the exact same issues you are describing and nothing has worked on my phone so far. My phone is currently s-off though. This all started to occur after I did a backup through Rom manager and then also a backup through MIUI rom. A few hours later while it was charging it randomly started the reboot cycle flashing the htc incredible screen. I'll let you know if I am able to fix mine but at the moment it seems were both SOL.
Did you ever find a solution to this problem?
This is a guide I posted in androidforums about a month ago after i went though a bunch of crap to root my phone, hopefully it can be helpful
So, This is the second time I’ve tried to make this post and I feel like I should have known better than to make a giant post like this and then hit submit before copying it to word or something but anyway…..
I thought that I have been through so much to finally get this rooted and have my ROM installed that I thought I am certainly not the only person to have had this problem and I would organize a full instruction guide to Downgrade, root and flash when you have troubles with unrevoked for people who have had similar troubles.
NOTE: I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU CAUSE TO YOUR DEVICE, THIS GUIDE IS DESIGNED TO HELP DROID INCREDIBLE USERS WHO ARE HAVING TROUBLE ROOTING THEIR PHONES AND I DO NOT KNOW THE EFFECTS A SIMILAR PROCEEDURE WOULD CAUSE TO OTHER PHONES.
First things first, I want to give credit where credit is due. Scotty85 of these forums wrote a large portion of what I am about to tell you and I am simply copying it and I will give you links to his original posts so he gets credit.
Step 1: Downgrade your phone
If your phone already has Android 2.2 on it then you can skip to Step 2
The HTC Incredible cannot be rooted unless it is running android 2.2 froyo, so the first thing you must do is downgrade your phone: I will copy the instructions to here so they are all in one place but here is a link to the original post by Scotty85
http://androidforums.com/incredible...ot-2-3-4-downgrade-get-s-off.html#post3308718
I will provide you with new links because a lot of the ones on Scotty85’s post are dead
First Download These Files:
Hboot Drivers for The droid incredible – from unrevoked
Mini-adb_inc.zip from mediafire
PB31IMG.zip from mediafire
Now, follow the following instructions:
Scotty85 said:
3)prepare to downgrade
-extract the mini-adb_inc .zip. place the extracted folder on the root of your c\ drive. it comtains mtd0,flash_image,and some adb tools.
-extract zergRush.zip. take the image inside,and either copy/paste or drag it into your mini-adb_inc folder
-place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG. now is a good time to verify that your SD card is formatted "FAT32" by right clicking on the drive that is your phones sd card,then click "properties". if you find your card is formated anything else,youll have to re-format it. start by backing up all files to your PC as reformatting WILL wipe it clean. using your PC,do a full format to FAT32. you can then transfer the files back. *this is important-as your phone will not find the downgrade PB31IMG unless your card is formatted to FAT 32,and the file is correctly named.
4)downgrade with adb. make sure your phone is charged to 100% before starting.
-on windows 7,click the start bubble and type "command" in the search box. this should open a small black command window. from this point forward,all code will be in bold so you know what lines to copy and paste(or type,if you really want to type them all in). additional comments will be blue,and should not be copy/pasted. please note that each line is one command. copy/paste it into the prompt in your command window,and push enter. one line at a time.
at the end of the post,is a copy of my session,to show what the outputs of the entered lines should look like. hopefully,its a little less scary when you know that youre getting the right responses to the things you enter.
-make sure phone is plugged in and usb debugging checked on in charge only mode
-at the promt in your command window:
cd c:\mini-adb_inc this should change your command promt to "mini-adb_inc",indicating youre using that directory.
adb devices this should output your phones serial number,indicating its recognized
md5sums mtd0.img it should output a few things.at the end you should see this number 34307be744275f1db1dd16af04c37839
md5sums flash_image again,it will output some things,then you should see this number: 0098a7dd6600b55fac34fc6645be5d7a
md5sums zergRush again,output stuff, then this number:4a32187446c284c2b975845f3ab9ffc4
*all those numbers must match exactly. if they do then you can procede.
adb push zergRush /data/local/
adb shell this will change your promt to a $
chmod 755 /data/local/zergRush
/data/local/zergRush
this will cause zergRush to start,and it shoudl say "found a gingerbread!" followed by a bunch of other funny stuff.
last thing it says will be: Killing ADB and restarting as root... enjoy!
you should then be returned to your "mini-adb_inc>" prompt
adb push flash_image /data/local/
adb push mtd0.img /sdcard/
adb shell your prompt should change to a #
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local
./flash_image misc /sdcard/mtd0.img
you can now downgrade back to 2.2,so you can run "unrevoked forever" to regain s-off
exit to get out of your adb shell,and back to the "mini-adb_inc" prompt
adb reboot bootloader this will boot your phone to "fastboot" select "bootloader" with the power button.
Click to expand...
Click to collapse
Now what you need to do is place PB31IMG.zip onto the root of your sd card and run hboot by when turning on your phone holding down the power and volume-down buttons at the same time. It should automatically find the file and ask if you wish to update and you just need to select “yes”.
Step 2: Flash Clockwork Recovery to your phone
You now need to download a few more files and place them somewhere that will be easy to find.
Unrevoked 3.22 from Mediafire – NOTE: if this link ever becomes broken, you must use version 3.22, 3.32 will NOT work.
Clockwork 5.0.2.0 from PvilleComp.com – make sure you use clockwork 5.0.2.0 with md5: e8ac35ddc1c37000bb0852d1f380b5bb
Next, run unrevoked 3.22, as an administrator if you can. And click file>Custom Recovery… and select the .img file which is inside the Clockwork 5.0.2.0 .zip that you downloaded, you may need to extract the folder first.
Next you can plug in your phone and select charge only and then go to Settings>Applications>development> and enable debugging.
Unrevoked should now recognize your phone and bring up a warning dialogue. Click ok and Unrevoked will run and flash Clockwork 5.0.2.0 to your phone. Do not touch your phone until you see a terminal-like screen on your phone in all blue text on a black background.
At this point just click “reboot system now”- you can navigate clockwork using the up and down volume keys and use the power button for “enter” or you can use the scroll button at the bottom of your droid incredible to navigate and center-click for “enter”.
Step 3: Rooting your phone
You will now need to download a few more files and place them on the root of your sd-card
Superuser.zip – found on androidsu.com – simply select the version of superuser.zip that matches your OS, 2.2 Froyo.
Unrevoked forever – from unrevoked.com – look for the unrevokedforever.zip file download
Like I said, place these files on to the root of your SD card at this time using the mass storage feature of your phone when it is booted into android.
Now, boot your phone into clockwork recovery mode. Simply turn off your phone and hold power + volume-down and it will start the hboot and then select “recovery” using the volume keys to navigate and the power button for “enter”
When booted into clockwork navigate to the “install zip from sd card” option and then find the superuser.zip file that you put onto your sd card. Select yes to install and clockwork will install superuser and root your phone.
At this time your phone is rooted, and if this is all you wanted then congratulations, you’re done! Simply click on “reboot system now” and enjoy your superuser powers responsibly
However, if you want to someday in the future flash a ROM to your phone go ahead and use the same procedure you used to install superuser.zip to install unrevokedforever.zip, this is simple to switch the phone from s-on to s-off, which means that the security is off and it will allow you to install unsigned ROMs to the phone (one’s not signed by HTC)
You may now click “reboot system now” to reboot into android.
Step 4: Installing a ROM
Find a ROM from Cyanogenmod or your favorite developer such as and put it onto the root of your sd card.
At this time you have two options for installing a ROM to your phone: you can either manually go into clockworkmod recovery and wipe the cache, data, and system of your phone and then use the “install zip from sd card” and install the ROM
OR you can install ROM manager to your phone (can be found on Google Play, formally Android Market) and install from there. All you need to do is use the app to reflash Clockwork and then select “Install ROM from SD card” and it will do all of the work for you. You can choose to backup your old ROM or to wipe the cache, but after this runs and completes you will boot into your new ROM.
Note: if you format your sd card before this process and have only the ROM on the card it will run much faster.
You’re done! Congratulations! You may have a ROM that does not have google apps pre-installed but there are many guides online for installing the android market and google apps. For example, for cyanogenmod you can just flash a gapps.zip specific for your version using clockwork and it will push all of the apps for you.
Enjoy your now rooted and flashed phone, and as always, root responsibly.
jackbtha1 said:
You would need to downgrade to Froyo to be able to root your phone....
Click to expand...
Click to collapse
That is incorrect. Using unrevoked 2.3 you can root 2.3.4. And you do not need s-off to flash roms! I can flash roms left and right with no problem,and i can even flash kernels. S-off protects flashing radios.
As far as the stuck in hboot and splash screen,you may be stuck with the bootmode stuck to bootloader.
Google is your friend.
Sent from my VTAB1008 using XDA
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
You're going to need to upgrade your device to the latest available RUU version (4.67.651.3), unlock your bootloader with HTCDev, flash a custom recovery, root your device, and then downgrade your misc partition (again). That should normalize your device (if one of the earlier steps doesn't do it).
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
have you tried running a RUU yet? it should restore your phone back to stock radio hboot system and a few other things
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
echoedge said:
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
Click to expand...
Click to collapse
The RUU is run from the PC while you're in fastboot mode. That'll work fine. Or you can use the PC36IMG from here and flash in HBOOT (bootloader).
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
C:\Android>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
Click to expand...
Click to collapse
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
echoedge said:
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
Click to expand...
Click to collapse
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Captain_Throwback said:
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Click to expand...
Click to collapse
Yes, it did that.. went through all the checkmarks with success down to WiMax I believe was the last one.
It did reset once during the process.. I remember because I was confused, didn't know if it turned off or what, then it turned itself back on, continued with the process and installed the rest of it.
The only thing that changed was the radio version from 2.15.00.08.08 to 2.15.00.11.19 after the RUU/Hboot/PCIMG36 img flash.
Bootloader says... I'll type it all out
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Click to expand...
Click to collapse
Should I try re-flashing again using the .exe file, does everything seem right on the bootloader?
Okay, I think I might have put the wrong PC36IMG file directing towards 11.19
(too many files in my Downloads folder )
Lemme try again.. I see the radio version should be 12.19, which is what Captain's link provided
Okay, I used the proper 12.19 PCIMG36 file this time,
now the bootloader says
*** LOCKED (OOW) ***
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
Dec 21, 2011, 12:50:32
Click to expand...
Click to collapse
Looks like it's back to its original state
I'm assuming it works now, still updating as I type this, will try the token and the other steps to get it back down to 2.10 with s-off and back to where it should be
Thanks for the help guys.
I'll let you know if it works, I'm assuming it will and I know the steps to perform at this stage.
One more question though which got me into this original mess,
do I need to update the kernal/radio/anything in order to get an ICS rom loaded on the Evo 4G?
Or was that issue mute just because I was trying to flash an Evo V 4g/incompatible rom?
Thanks again!!
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
echoedge said:
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
Click to expand...
Click to collapse
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Tried going back into hboot.. plugged it in,
was detected, but had to re-install drivers on my w7 machine I noticed.
after i figured out that hboot usb worked, went to recovery, went to restart now.
went to black screen and noticed it is vibrating 5 times now (before it was 3)
took out battery, turned back on, back to sprint stock. still no usb capabilities within the rom.
btw my bootloader now says
** unlocked **
s-on
hboot-2.18.0001
radio-2.15.00.12.19
also,
tried going back into recovery, and re-flashed the superuser file. installed fine.
this time instead of going to 'reboot now' went to shut down.. it shut down fine. I turned it back on, turned on fine.
It only seems to be doing the black-screen and 5 vibrations when I reboot.
Tried plugging it in again to pc, checked settings - nothing.
Am confused now, not sure what's wrong
EDIT:
okay, just read Capt. Throwback's reply AFTER posting this, will give that ago. Thanks CT
Captain_Throwback said:
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Click to expand...
Click to collapse
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
echoedge said:
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
Click to expand...
Click to collapse
You're going to need to flash a ROM with Wireless ADB enabled, or manually use Terminal Emulator to flash the misc partition, as per the instructions in my "Downgrade HBOOT" thread. If you still have the flash_image and mtd-eng.img on your SD card, Terminal might be the easiest way to do it (hopefully it'll let you). If not, we'll have to go the Wireless ADB route, as I did here.
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Also I booted into the sprint stock rom, plugged in the USB and now that functionality is working fine.. prompts up, charge only, etc.
Seems I'm almost there... :fingers-crossed:
echoedge said:
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Click to expand...
Click to collapse
If you're back to S-OFF, you might be okay. Try flashing the 4.67 PC36IMG.zip in HBOOT again. After you do that, you should still be S-OFF, if everything is working properly, and hopefully everything else will be working too.
It's also possible that the misc partition flash was incomplete. Since you're now S-OFF, and presumably ADB is working, you should be able to run the commands over USB.
Okay, I had to put in a bigger SD card for it to detect the PC36IMG to detect- installed perfectly.
Also had to reflash amonRA recovery.
I was already S-OFF for whatever reason so yup, after that I was good to go! :good:
Booted to recovery, made a backup, wiped data/factory reset, an flashed an ICS rom. Just booted up, everything is working great
Thanks a bunch everyone (esp Capt. Throwback) for getting this resolved quick and painlessly
Am very relieved to get this working once again as normal, wasn't sure if I would be able
Thanks again!!
I've been trying to re-root my phone since late last night, and have had nothing but problems. I've searched all over the internet, and tried anything that I thought would apply to my situation in the slightest.
I originally downgraded from 2.3.4 to 2.3.3 and rooted my phone using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1298990
I ran Revolutionary, ClockworkMod, and SuperUser. Everything worked perfect the first time around. Installed the Cyanogenmod 7.2 ROM and Tiamat v1.1.5 kernel. Then I started having issues with my battery, and Cyanogenmod seemed to be increasing the issues. At that time HTC announced they'd be releasing ICS, yada yada yada. I found a stock ROM online, and installed it, and updated as they were released OTA. Having finally gotten a new extended battery, I'd like to re-root & ROM my phone, but I've hit some road blocks.
I currently have the Android Version of 2.3.4 & Software Number of 5.10.605.9
I tried to re-do the entire process that had previously worked for me, but once I used the command hack-vivow.cmd, the phone would boot to the Revolutionary (of HBOOT ?) screen. Command line shows this, and just hangs:
c:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
Click to expand...
Click to collapse
Phone shows this:
-Revolutionary-
VIVO_W XB SHIP S-OFF RL
HBOOT -6.13.1002
RADIO -1.09.01.1111
eMMC -boot
Click to expand...
Click to collapse
Phone gives me the options of "BOOTLOADER", "REBOOT", "REBOOT BOOTLOADER", & "POWER DOWN". "REBOOT BOOTLOADER" changes "FASTBOOT" briefly to "FASTBOOT USB", but changes back in about 15-20 seconds. When I select "BOOTLOADER", the screen freezes for a few seconds, and it won't let me select any options, "FASTBOOT" changes to "HBOOT", and I get this in green text:
SD Checking
Loading...[PG32DIAG.zip]
No image!
Loading...[PG32DIAG.nbh]
No image or wrong image!
Loading...[PG32IMG.zip]
Click to expand...
Click to collapse
The next screen of green text says "Parsing...[SD ZIP]" followed by 9 things, and I'm only given an option to Update or No/Reboot. No/Reboot reboots my phone into an endless bootloop, until I remove the battery and power back on with Volume Down + Power Button. Update does a reset of my phone, and puts me right back to where I am now. While it is updating there is an error message at the bottom that says "Can not roll back hboot version".
I've tried multiple things to attempt to fix this... I ran the TacoRoot method from here:
http://forum.xda-developers.com/showthread.php?t=1751796
When the 8th line was completed
adb shell /data/local/tacoroot.sh --setup
Click to expand...
Click to collapse
, the phone rebooted, it got stuck in a bootloop.
So that's where I am now. I'm stuck with S-Off, the PG32DIAG/PG32IMG errors, an HBOOT that seems to be far too new of a version, and I haven't found a way to get back to 2.3.3. As you can see I'm a noob. I'm really not sure where I went wrong (other than going back to a stock ROM and allowing it to update). Unfortunately a lot of things are just way over my head, without seeing a step by step process. But I'm just stuck at the moment. If anyone has any ideas on how to fix this, or any ideas of things to try I GREATLY appreciate it.
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Cleanincubus said:
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Click to expand...
Click to collapse
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
gtdtm said:
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
Click to expand...
Click to collapse
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Cleanincubus said:
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Click to expand...
Click to collapse
So with Froyo on there can you get to the stock recovery?
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I think you should be able to do 1B at this little how-to site:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I also just noticed...did you do "fastboot devices" first to make sure it actually recognized your phone? I'm really guessing, but I figured it was worth asking.
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Cleanincubus said:
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Click to expand...
Click to collapse
You shouldn't be flashing romantic zips as PG32IMG. That's what clockwork is for. If get it back to froyo, then go to the HTC recovery and follow the clockwork instructions I linked to. But maybe someone more knowledgeable than I can answer better.
Sent from my ADR6350 using xda app-developers app
After you go onto bootloader and it flashes your IMG you either rename the file on your SD card or delete it from your SD card. You will be able to proceed after that has been done
sent from my incredibly paranoid inc2
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Your s-off so the hard part is done.
sent from my incredibly paranoid inc2
You're right. The PG32IMG.zip was a problem. I removed them from the SD card's root, and it's working as it should.
Now the issue is the instructions in that link. I can't find any update.zip for the phone anywhere. I also can't find any options in the Recovery for "re-install package". I go to "BOOTLOADER" and then "RECOVERY". The Phone then boots to a small image of my phone with a red "!". I press Volume Up + Power button, and it loads the "Android system recovery <3e>". I have a Yellow error at the bottom stating"
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
sjpritch25 said:
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
Click to expand...
Click to collapse
screenshot for you
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Cleanincubus said:
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Click to expand...
Click to collapse
I don't think it's going to work until you get fastboot devices and adb devices to recognize your phone. I wish I could point you in the right direction, but I'm not very experienced with it.
I'm assuming you have the drivers for our phone installed? Some people have to reboot the pc to get those to recognize the device...
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Cleanincubus said:
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Click to expand...
Click to collapse
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
sjpritch25 said:
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Click to expand...
Click to collapse
Yup, it's there.
Did those commands, and it ended in the same result. No errors or "waiting" messages at the flashboot devices command, but it didn't show my device either.
Jasonp0 said:
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
Click to expand...
Click to collapse
Definitely installed driver. I originally tried to install the driver I previously used with my original s-off/root/rom, but it didn't work with Windows 8 (previous PC was WinXP), so I found the correct one for my OS. The "adb devices" command never found my phone, before installing the current driver.
I never installed HTC Sync. Just double checked the "Uninstall or change program" in the Win8 control panel (previously "Add/Remove Programs") to make sure it didn't get installed with out my knowledge, and it's not in there.
If you mean on the phone: "Settings" > "Applications" > "Development" > check box for "USB debugging", then yes. If it's a command of some sort, then no & I don't know how to do it.
I'm also making sure to run these commands by right-clicking the Command Prompt and selecting "Run as administrator", before doing these commands.