Related
I have searched all over and am still coming up empty on this one. Phone was working with Cyanogen earlier today, then rebooted itself and never stopped. When I try to boot into recovery it simply goes to the white evo splash screen and reboots again.
The only thing I can do is hboot/flashboot. I could not get adb shell to load at all connected to my mac. Under windows when I select flashboot it does appear on device manager under Android USB Devices->HTC Bootloader.
I have tried RUU, connection error.
I have access to both a PC and a Mac and am open to any suggestions.
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-0.93.000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Jul 23 2010, 16:41:47
carlbeck said:
I have searched all over and am still coming up empty on this one. Phone was working with Cyanogen earlier today, then rebooted itself and never stopped. When I try to boot into recovery it simply goes to the white evo splash screen and reboots again.
The only thing I can do is hboot/flashboot. I could not get adb shell to load at all connected to my mac. Under windows when I select flashboot it does appear on device manager under Android USB Devices->HTC Bootloader.
I have tried RUU, connection error.
I have access to both a PC and a Mac and am open to any suggestions.
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-0.93.000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Jul 23 2010, 16:41:47
Click to expand...
Click to collapse
Sounds like you wish to unroot to solve your problems? If that is the case I can promise you that with patience you can get the RUU to work. If your computer is seeing your phone then you probably have all the drivers. Try to reboot your computer and then plug your phone in, go into bootloader and select the fastboot option I believe it is, whichever one lets you make connection to your computer. I would say to use the reboot bootloader option a few times to refresh then connection then trying to run the RUU.
I've tried doing hboot usb (it changes to hboot usb plug, shows in device manager) and fastboot (it shows fastboot usb and also recognizes in device manager). Cannot get RUU to work at all, period.
Do I want to RUU? No, not really. Just trying to find any way I can get the phone back up and working.
I've never done anything in hboot except by following the recovery instructions, so I am not expert.
If I was stuck in your situation I would follow the root instructions HERE. You will have copy the files to the SD card with your windows computer if that is working. If not find one of the micro SD card adapters and use a computer to put the files on the card and use hboot to flash the new recovery.
Actually go to THIS thread and follow the instruction for via bootloader. Again, if you can't connect to the SD card through usb, take it out and put it in a computer.
Flashed that new Recovery you linked via the bootloader using the PC36IMG method, still bootloops over and over again. Can't get into recovery nor anything other than the boot loader.
Seems like it is something more serious? Bad hardware perhaps? Anything I can do from here to make it seem like the device was not rooted and swap it out at a sprint store?
Is it boot looping at the Cyanogen boot screen or at the white screen that says HTC EVO 4g? Does the hboot screen still say s-off?
If the new recovery flashed successfully it should work.
If you are highlighting recovery and then hitting power and it is bootlooping you have a problem that is over my head.
White EVO screen. Still showing S-OFF, yes. If I highlight recovery and hit power, yes.. still bootloops.
Do what fazulka reccomends and put your sd card in an adapter . Sounds like your recovery got borked,
Search for your recovery of choice
Put on root of sd card and try again
You can find a .img recovery to load up and update/flash a new one thru hboot
Swyped from a galaxy far far away......
Got the RUU to recognize the phone now. When updating it starts by rebooting to bootloader, where I get a darker screen with HTC in the middle. Then not so long after it gives me another connection error 170 and quits.
Edit: Jimdog, I have flashed a new recovery using hboot. Still gives me a bootloop.
Ran the RUU, it finally finished updating this time. Guess what? Still bootloops. Gets to the white evo screen when booting regular or to the recovery, then reboots. Every time.
Still showing S-OFF, is there any way to get this to S-ON so I can take this into a Sprint store for a swap out?
Try sprintlovers.
This may fix it.
go HERE.
The first link that says download it the one you want. When you download it it will be named PC36IMG.zip put that on the root of your sd card. Boot into recovery. Recovery will find the file and ask if you want to use it. I believe volume up is yes. There is long waits then it will ask you if you want to reboot, press up for yes
Should boot (note, first boot is LONG)
Also, it may seem like it is freezing in recovery a few time, look to the top righ and there will be a small loading bar. Some of the actions are pretty slow.
I cannot boot into recovery. It reboots over and over no matter if I try to boot normally or boot into recovery. The ONLY thing I can do is anything in hboot, i.e. flash things using a PC36IMG.
I tried flashing a new recovery, I tried flashing sprintlovers. I successfully ran a RUU even. It still bootloops during the white evo screen.
I think something is physically wrong with the phone at this point, but I am affraid since I cannot get S-ON back without flashing unrevoked in recovery that I will not be able to swap out the phone at sprint under warranty.
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
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:47:02
---------------------------
Currently, Phone is stuck on HBOOT whenever the phone is turned on. I've tried removing the battery for long periods of time, removing the SD Card and so forth with no success.
With the SD Card inserted, it does the SD Checking! Sequence where it looks for images I'm guessing, being unable to connect the SD Card directly with an adapter I was hoping if anyone could tell me whether if theres anyway to transfer files via HBOOT mode or any advice on how to recover phone (Perhaps if theres a method to force it into the CWR mode.)
Thank you for any help.
ittekimasu said:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:47:02
---------------------------
Currently, Phone is stuck on HBOOT whenever the phone is turned on. I've tried removing the battery for long periods of time, removing the SD Card and so forth with no success.
With the SD Card inserted, it does the SD Checking! Sequence where it looks for images I'm guessing, being unable to connect the SD Card directly with an adapter I was hoping if anyone could tell me whether if theres anyway to transfer files via HBOOT mode or any advice on how to recover phone (Perhaps if theres a method to force it into the CWR mode.)
Thank you for any help.
Click to expand...
Click to collapse
Are u able to navigate to recovery just through hboot with the volume buttons?
If not, if you've used adb before use the command
Code:
adb reboot recovery
Then from there, since you're S-OFF you can do a full wipe and restore a backup or flash a ROM, if you have those things on your sd
Let me know if there are any other problems
Select bootloader option in hboot and then you will see recovery and just hit the power button when you want to enter recovery.
Sent from my HTC Inspire 4G using xda premium
maatsby said:
Are u able to navigate to recovery just through hboot with the volume buttons?
Click to expand...
Click to collapse
Thanks for the replies, and No, I'm unable to navigate the HBOOT with the volume controls at this point.
Would the ADB allow me to reset and set it into recovery mode whilst its in HBOOT mode? This might be something I'll look into once I get home.
ittekimasu said:
Would the ADB allow me to reset and set it into recovery mode whilst its in HBOOT mode?
Click to expand...
Click to collapse
Yes it would
The easiest way to use adb that I've found is to look for leith51's guide to flashing a radio, they have an easy flash guide that includes a zip with adb and all drivers included, and a .bat file for an easy start.
Click start here.bat, then type "adb devices" to see if the phone is recognised (it will print your phone's serial number) then go ahead with "adb reboot recovery"
If you can't find it I'll send it to you when i'm home from work
Format your whole phone and try again
here you go, i had it bookmarked on my laptop
http://forum.xda-developers.com/showthread.php?t=896597
download the Radio flash.zip
double click the Start Here.bat
away you go
I'm in need of some expert help for my wifes Droid Incredible. It is rooted, s-off running Cyanogen 7.xxx
She woke me in a pannic this morning saying her phone wasn't working. When I took a look, it keeps booting to the white screen with the "htc Incredible" words. I can press volume down and power to get into hboot, but when I select recovery or factory reset, it just boots back to the white screen with "htc Incredible"
I can't seem to get anywhere from here and the search I did seems to bring up other issues with people at least able to get into the recovery.
Any help or advice on where to go from here would be greatly appreciated.
Thank you.
Droinc said:
I'm in need of some expert help for my wifes Droid Incredible. It is rooted, s-off running Cyanogen 7.xxx
She woke me in a pannic this morning saying her phone wasn't working. When I took a look, it keeps booting to the white screen with the "htc Incredible" words. I can press volume down and power to get into hboot, but when I select recovery or factory reset, it just boots back to the white screen with "htc Incredible"
I can't seem to get anywhere from here and the search I did seems to bring up other issues with people at least able to get into the recovery.
Any help or advice on where to go from here would be greatly appreciated.
Thank you.
Click to expand...
Click to collapse
You need to try to reflash recovery thru hboot. Download CWM 5.0.2.0 http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and place the file on your sdcard in no folders. Boot into hboot (vol down and power) and it should find the file after a couple secs and prompt you to press vol up to update. Do so and then when prompted to reboot do so. Now remove or rename the PB31IMG.zip on your sdcard and then pull the battery and boot to hboot and see if you can access recovery.
cmlusco said:
You need to try to reflash recovery thru hboot. Download CWM 5.0.2.0, and place the file on your sdcard in no folders. Boot into hboot (vol down and power) and it should find the file after a couple secs and prompt you to press vol up to update. Do so and then when prompted to reboot do so. Now remove or rename the PB31IMG.zip on your sdcard and then pull the battery and boot to hboot and see if you can access recovery.
Click to expand...
Click to collapse
I got the message to hit volume up to update and then after that it asked if I wanted to reboot the device. I selected yes (volume up) and it still loops the white screen with the "htc Incredible" words. I never got to the point where it rebooted fully.
SHOOT!!! Was hoping this would have done it. Thank you for the help though. I appreciate it.
Anything else I might be able to do?
As a side not, the phone does not get recognized when I connect it to my computer. I had to use another phone to place the PB31IMG file on the SD card.
Droinc said:
I got the message to hit volume up to update and then after that it asked if I wanted to reboot the device. I selected yes (volume up) and it still loops the white screen with the "htc Incredible" words. I never got to the point where it rebooted fully.
SHOOT!!! Was hoping this would have done it. Thank you for the help though. I appreciate it.
Anything else I might be able to do?
As a side not, the phone does not get recognized when I connect it to my computer. I had to use another phone to place the PB31IMG file on the SD card.
Click to expand...
Click to collapse
No you misunderstood, it will still boot loop at this point, that was just the first step. Boot to hboot and see if you can access recovery now.
If you can access recovery, either restore a backup or flash a new rom.
cmlusco said:
No you misunderstood, it will still boot loop at this point, that was just the first step. Boot to hboot and see if you can access recovery now.
If you can access recovery, either restore a backup or flash a new rom.
Click to expand...
Click to collapse
Oh, gottcha. Sorry about that, my fault.
After hitting volume up to reboot, I took out the SD card and placed it in the other phone to remove the file. After that I put it back in the Incredible and booted it into hboot, but when I selected recovery, it did the same thing and just loops the "htc Incredible" screen.
Ok the next step to try would be to do an ruu. It will restore the phone to stock, but you will still have s-off.
Download this file http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip and place it on the sdcard in no folders, boot to hboot, vol up to install. This time though when prompted to reboot select no, and then select factory reset. Hopefully when its done it will boot normaly.
cmlusco said:
Ok the next step to try would be to do an ruu. It will restore the phone to stock, but you will still have s-off.
Download this file and place it on the sdcard in no folders, boot to hboot, vol up to install. This time though when prompted to reboot select no, and then select factory reset. Hopefully when its done it will boot normaly.
Click to expand...
Click to collapse
OK, going to give it a shot. Will be back soon with good news hopefully
Question...... After selecting "no" to the reboot option after it's been updated with the file, do I delete or rename the file and THEN try to get into recovery?
Droinc said:
Question...... After selecting "no" to the reboot option after it's been updated with the file, do I delete or rename the file and THEN try to get into recovery?
Click to expand...
Click to collapse
After selecting no to reboot, select factory reset from the hboot menu. When the factory reset is done it should automaticly reboot and boot up like normal.
Then you can delete the file and reflash cwm recovery as the ruu left you with the stock recovery.
OK, I must be doing something wrong. Here are the steps I have done:
* I put the SD card into a phone recognized by my computer
* I then place the RUU file onto that SD card
* I then take the SD card out and place it in the DInc
* I then hold the volume down button and power button to get into hboot
* The phone recognizes the file and starts the update (takes a bit)
* Once the update is done it asks if I want to reboot and I select no
* It then goes to a screen with a few options (bootloader, reboot bootloader etc...) I don't select anything and then pull the battery
* I then take the SD card out of the DInc and place it in the other phone so I can remove the file
* Once the file is deleted I take the SD card out of that phone and place it back into the DInc
* I go into hboot and select recovery and it just boot loops again with the "htc Incredible" screen
Am I missing something?? I know it can be recovered. Even it's back to stock, it would be great. My wife just wants her phone back.
cmlusco said:
After selecting no to reboot, select factory reset from the hboot menu. When the factory reset is done it should automaticly reboot and boot up like normal.
Then you can delete the file and reflash cwm recovery as the ruu left you with the stock recovery.
Click to expand...
Click to collapse
Damn, you're fast cmlusco.
When I select no to the reboot, it does not present me with the screen that has the recovery option. It's a different screen with, I think, 4 options: bootloader, reboot bootloader, and 2 others I can't recall
Just notice this thread is on page 2 now. Check the last post on page one for steps on what I did.
When you boot to hboot there should be an option to do a factory reset, do that, you may have to select bootloader first. Then see if it boots normaly.
cmlusco said:
When you boot to hboot there should be an option to do a factory reset, do that, you may have to select bootloader first. Then see if it boots normaly.
Click to expand...
Click to collapse
no go.
I assume once I apply the RUU I don't need to do it every time?
I went back into hboot and selected factory reset and it just did the same boot loop. Should I try wiping the SD card 100% clean and then try the RUU file?
Droinc said:
no go.
I assume once I apply the RUU I don't need to do it every time?
I went back into hboot and selected factory reset and it just did the same boot loop. Should I try wiping the SD card 100% clean and then try the RUU file?
Click to expand...
Click to collapse
You could try it, but it sounds like the recovery partition may be messed up. The stock recovery dosent work, cwm recovery dosent work, but ruus and recoverys flash fine without error. Sounds like a messed up partition table. Do you have ADB setup on your pc?
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Droinc said:
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Click to expand...
Click to collapse
gotta download android sdk
http://developer.android.com/sdk/index.html
this should help http://androidforums.com/faqs/443072-adb-guide-updated-12-05-2011-a.html
Droinc said:
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Click to expand...
Click to collapse
Download this http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip, and extract the contents to C:\ADB.
Connect the phone to the pc and on the pc go to device manager and look for an entry called unknown or android 1.0. Right click on it and select update driver. Select browse for driver and navigate to C:\ADB\drivers and select the adb folder. It should find the driver and update it.
Then open a cmd prompt on your pc and navigate to the C:\ADB folder. At tje prompt type adb devices , it should return a string of numbers and letters.
From there if it finds the phone you need to fastboo flash your misc partition.
Its gonna get a little complicated and require a bunch of steps. It sucks but it may fix it. I know there are already threads out there on how to fix this issue but i cant seem to find one.
When I plug the phone into the computer and power the phone on it just boot loops and the computer doesn't acknowledge it at all. In device manager there is not entry under any of the categories that says "Android..." or "unknown"
Droinc said:
When I plug the phone into the computer and power the phone on it just boot loops and the computer doesn't acknowledge it at all. In device manager there is not entry under any of the categories that says "Android..." or "unknown"
Click to expand...
Click to collapse
Crap i forgot you need to be able to boot the phone to enable usb debuging for the pc to see it. Um now im not sure what to do. Mabey format the sdcard fat32 and try the ruu again. I need to think about it, it will come to me.
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!!