need to exchange the phone, so i need to revert the phone back to fully stock. phone currently has cyanogenmod 7. just want to make sure i'm doing this right...
so as i understand it, following the g2\desire z wiki, i can just use clockword mod recovery to install the stock image and flash it with CWM right, via the "flash alternate recovery" option?
and more importantly, the wiki says that to install the stock rom, i need to make sure my main version is not higher than 1.19.531.1, but i was not able to find my version. i booted into hboot, which number is that? and regardless, if i use misc_version to set the main version, does it matter what version i have? also, i used gfree to root before, and still have the original partition 7 saved on my pc, if that matters. thanks
Here follow my guide, it describes how to return to stock. Only change you might want to make is use a proper stock rom to flash instead of my modded ones.
-Nipqer
thanks! how do you flash stock recovery???
i did fastboot recovery recovery.img and it said:
"sending 'recovery' (4652 KB)... OKAY [1.021 S]
writing 'recovery'... FAILED <remote: not allowed>
finished. total time : 1.031s
Fastboot flash recovery only works on eng hboots or htcdev unlocked hboots.
-Nipqer
Sent from my HTC Vision using xda premium
so then what can i do? thanks again
Use the xda wiki to get full root. That will give you recovery in the process
-Nipqer
Sent from my HTC Vision using xda premium
Similar-sounding problem
I've attempted to install ClockworkMod and CM7 on my G2 with Gingerbread 2.3.4, and have wound up putting it in a semi-bricked state. (Whole process went fine on my old G2 last year, but had to return that due to a wifi problem). Here's what I've done so far:
1. Started the root/CW process (http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting). Once I got to the psneuter step, I got "Failed to set prot mask (innappropriate ioctl for device)", which I figured meant I needed to do the downgrade, since that was the only difference I could see between my new G2 and the old one (which had Froyo when I went through this process).
2. Downgraded to Froyo (http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Froyo). That seemed to go just fine.
3. Re-did the root/CW process. That also seemed to go just fine, until I rebooted into CW, at which point I got:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
At this point, attempting to select any of the items in the CW menu just showed the hat-with-ring logo, no text. I figured I must have screwed something up, and decided I'd best roll back to stock (I'd just done that on my old G2, so I could send it in, and that process had also worked fine).
4. Rolled back to the original PC10IMG.zip (http://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/ but without the OTA part). When I rebooted, I got the green-on-white "HTC" screen, for at least 10 minutes. Retried several times. Using power-volumedown, I could still get into recovery, which was still Clockwork, but with the same errors as in step 3. I could still connect via ADB (when in Clockwork) and get a root shell with that, at this point.
5. Big goof: I decided I should rollback to stock recovery. Did that using the http://forum.xda-developers.com/showthread.php?t=834545 guide. Rebooted. Phone still sticks at the initial HTC screen, forever. Using power-volumedown, I can get to the screen whose name I do not know, the one that's white with three skateboarding androids at the bottom, and the "Fastboot, Recovery, Factory Reset, Simlock, System Info, Image CRC" menu.
6. Recovery now takes me to what I presume is stock recovery, which has a "E:Can't mount /cache/recovery/command" message at the bottom of the screen. Menu is "Reboot system now, Apply sdcard:update.zip, Wipe data/factory reset, Wipe cache partition." Factory reset and wiping the cache partition, then rebooting, still results in the eternal HTC screen.
7. If I do reboot and do power-volumedown to get back to the three-skateboards screen (someone please tell me the actual name, so that I can sound like less of an idiot), I can select fastboot, and then connect via fastboot-windows. I haven't done anything with that yet, however, as I figured I've gone too far already without stopping to ask for help, and don't want to cut myself from off from fastboot the way I cut myself off from adb.
Right now, I just want to get the phone to a usable state again. Not expecting any hand-holding, but I'd appreciating someone pointing me to the start of the path back.
...the three skateboards screen is called bootloader
is it still s-off and what hboot-number does it show?
At the top of the bootloader (thanks!) screen, I get:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.01.00.17_M2
eMMC-boot
Sep 8 2010, 15:56:38
ok, this looks good.
first i would flash a recovery.img through fastboot (you do have eng hboot so it should work)
download the 3.0.2.4 image from here and put it into your platform tool folder:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
then connect your phone to pc go to your platform tool folder and type:
"fastboot flash recovery recovery.img"
enter recovery and wipe data&cache&dalvik cache afterwards flash a new rom...
if you get the same error as before, have a look here:
http://forum.xda-developers.com/showthread.php?t=1448441
Thanks immensely. Going to try this in the morning (hitting 2am for me). Just one final question: at the "flash a new ROM" step, should that be the stock T-Mobile ROM, or does it matter? My original intent was to install CM, so if it makes no difference I'll go with that, but right now I'd be happy just to have a phone that boots, so if I need to I'll use stock and count my blessings.
emamid said:
Thanks immensely. Going to try this in the morning (hitting 2am for me). Just one final question: at the "flash a new ROM" step, should that be the stock T-Mobile ROM, or does it matter? My original intent was to install CM, so if it makes no difference I'll go with that, but right now I'd be happy just to have a phone that boots, so if I need to I'll use stock and count my blessings.
Click to expand...
Click to collapse
no do not flash a stock rom (you will get in troubles doing this with a rooted phone and s-off)... cm7 is a good way to go
if you don´t mind pls hit the thanks button
damnit... now i can't seem to downgrade the new phone, with the 1.22 firmware. following the cyanogenmod wiki, at the step where you enter:
Code:
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
adb shell
i get a whole bunch of:
Code:
An error occurred while running the exploit (-1) (errno: 25)
Scanning region fffe0000...
An error occurred while running the exploit (-1) (errno: 25)
adb shell
adb: permission denied
$
help, what am i doing wrong?
first of all you do have gingerbread (2.3+)? because you asked this in a different thread...
and you did chmod it as described in the guide?
hoffmas said:
first of all you do have gingerbread (2.3+)? because you asked this in a different thread...
and you did chmod it as described in the guide?
Click to expand...
Click to collapse
nope, it's android version 2.2, but the build number is 1.22.531.8, so that means i have to downgrade it, right?
you need a different guide for a froyo downgrade - try this guide:
http://forum.xda-developers.com/showthread.php?t=905261
i´m not sure if it works... other thing you could do is make a official update to gingerbread and then downgrade with the guide you used before.
hoffmas said:
if you don´t mind pls hit the thanks button
Click to expand...
Click to collapse
Weird, I had to open the page in Firefox rather than Chrome for the "Thanks" button to show up.
---------- Post added at 03:03 PM ---------- Previous post was at 02:43 PM ----------
hoffmas said:
ok, this looks good.
first i would flash a recovery.img through fastboot (you do have eng hboot so it should work)
download the 3.0.2.4 image from here and put it into your platform tool folder:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
then connect your phone to pc go to your platform tool folder and type:
"fastboot flash recovery recovery.img"
enter recovery and wipe data&cache&dalvik cache afterwards flash a new rom...
if you get the same error as before, have a look here:
http://forum.xda-developers.com/showthread.php?t=1448441
Click to expand...
Click to collapse
Installed clockwork, and can get to it through the bootloader. However, when I try to wipe the cache -- or select any of the other menu items -- I just get the hat-and-ring logo, with nothing else. Power button takes me back to the CW menu again. No error messages at any stage, but nothing happens either.
Should I proceed with the steps in the second link you pointed to? Or does this sound like a different problem?
Hm don't know... Maybe try to find out if your cache is corrupted or your emmc chip. So yes follow the link i posted, but before you do the same as the op there (means using your sdcard instead of emmc) try everything else... (i think nipqer posted a link there related to corrupted cache...)
Sent from my HTC Vision using XDA App
Thankfully, I didn't have to go through hardly any of the contortions CollegeBound had to in that thread. Installing 4EXT was enough -- it was able to get past the "E:Can't mount /cache/..." errors (which started again when I used fastboot to erase the cache), whereas Clockwork was stymied by them. Did an update using a CM ROM, and everything seems fine.
Thanks again for your help. I don't think T-Mobile would have let me RMA two phones in two weeks.
Related
So I was trying to root my evo so I could try the fresh rom (please note that this was my first ever root attempt and my phone had the OTA update). I followed the instructions from this guide:
Latest OTA rooted! - Page 2 - Android Central Forums
This is where my problem is:
11. Once back at the Home screen type:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
When I enter the "cat /sdcard/flash_image > /data/flash_image" code I get:
"cannot create /data/flash_image: permission denied"
After some googling I found other people typed "su" prior to typing in the "cat /sdcard/flash_image > /data/flash_image" command. That didn't work for me. I received "su: permission denied" after entering su.
Would going back and starting this tutorial all over cause serious damage? I'm wondering if maybe I messed up earlier.
I'm very worried I really screwed something up. Can anybody please offer up some advice for a newbie?
Weigh the stakes
Man, just try the "SimpleRoot 1.47 OTA update" app for Windows. You save time, money and a lot of feces on your tract by the worries that everything is ok.
Now, I want to remind the stakes. If you haven't looked at my post here at Q&A, I pretty much effed up my phone while being rooted. I don't know if it was too much exposure to heat caused by WiFi Tether, or of mysterious powers regarding the RSA 256 bit encryption update process screwed my phone up. So before trying to crack your phone, please, review the stakes and stay stock.
BTW, you haven't completed the root process, so a simple Factory Reset should do the trick to go back into Stock without any trace of root procedure. That is, if you want to play it safe.
Okay, first things first. Just so I'm clear.
1. Which guide(exactly) did you follow?
2. What software version do you have now?
Yeah i was having problems with my administrator password so I switched from simple root to this method. Maybe I was using the wrong version or something, could you post a link to simple root for ota?
churchwin88 said:
Okay, first things first. Just so I'm clear.
1. Which guide(exactly) did you follow?
2. What software version do you have now?
Click to expand...
Click to collapse
1. http: // forum.androidcentral. com/htc-evo-4g-roms-hacks/ 21043-latest-ota-rooted-2. htm
2. My software number is 1.47.651.1
Thanks for the help
StrummingLevi said:
Yeah i was having problems with my administrator password so I switched from simple root to this method. Maybe I was using the wrong version or something, could you post a link to simple root for ota?
1. http: // forum.androidcentral. com/htc-evo-4g-roms-hacks/ 21043-latest-ota-rooted-2. htm
2. My software number is 1.47.651.1
Thanks for the help
Click to expand...
Click to collapse
For the 1.47 you need to use this version of simple root(if you haven't already) - http://forum.xda-developers.com/showthread.php?t=720565
I'm not sure why it would have problems with the password. Only thing I can think of would be something along the lines of not having administrator privileges.
EDIT: Make sure to have all the requirements and if you successfully run that let me know so we can proceed to the next step(it is really simple).
I did the simple root for 1.47 and it was a success! Although I did not understand what the flash recovery did. I tried the clockwork recovery and it took me to a screen with a bunch of options, but I didn't know what to do so I just rebooted. What's next? I want to try the newest version of the fresh rom.
TO try fresh first download it and place the zip file on your computer, boot into recovery, (power phone off then hold down volume and power untill you get to the white screen) select flash zip fron sd card then select the fresh rom and flas, presto fresh should flash, the recovery is a seperate area which is used to flash a rom, as you cant flash a rom from within a rom.
So do I use the clockwork recovery to flash the fresh rom? I was looking at the guide to flash the new fresh rom and it says that I need to have nand unlocked. How do I do that?
if you did simpleroot nand should be unlocked, and yes clockwork recovery is used to flash the fresh rom. clockwork recovery is what you are in when you boot with the down volume and power button held down. If it doesnt work you may want to try amon ra recovery, find the toast root method and do the last step:
- on your PC open a shell again and do:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
- you should now be in recovery mode
- do a wipe of data and dalvik cache
- navigate to nandroid restore and restore the previous rom setup
- come here to the forum, get and flash the latest radio
- enjoy... you can now reboot into recovery, write to system and other partitions while in Android. Also you now have a Engineering SPL so you can fastboot and much more.
It also wont hurt to do the whole part two of toasts guide if you dont think your nand is unlocked. FYI Nand unlocking allows both a read write option in the recovery which is needed to write the custom roms.
StrummingLevi said:
So do I use the clockwork recovery to flash the fresh rom? I was looking at the guide to flash the new fresh rom and it says that I need to have nand unlocked. How do I do that?
Click to expand...
Click to collapse
Your nand is unlocked. Just download Fresh, boot into recovery, wipe caches, and apply Fresh via zip file.
ifly4vamerica said:
if you did simpleroot nand should be unlocked, and yes clockwork recovery is used to flash the fresh rom. clockwork recovery is what you are in when you boot with the down volume and power button held down. If it doesnt work you may want to try amon ra recovery, find the toast root method and do the last step:
- on your PC open a shell again and do:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
- you should now be in recovery mode
- do a wipe of data and dalvik cache
- navigate to nandroid restore and restore the previous rom setup
- come here to the forum, get and flash the latest radio
- enjoy... you can now reboot into recovery, write to system and other partitions while in Android. Also you now have a Engineering SPL so you can fastboot and much more.
It also wont hurt to do the whole part two of toasts guide if you dont think your nand is unlocked. FYI Nand unlocking allows both a read write option in the recovery which is needed to write the custom roms.
Click to expand...
Click to collapse
Ignore this post, unless you want to flash Fresh with Amon Ra Recovery instead of Clockwork Recovery (what you have now)
Agreed, I was only posting that "if" he had problems using clockwork sorry for the confusion.
jerryparid said:
Your nand is unlocked. Just download Fresh, boot into recovery, wipe caches, and apply Fresh via zip file.
Ignore this post, unless you want to flash Fresh with Amon Ra Recovery instead of Clockwork Recovery (what you have now)
Click to expand...
Click to collapse
So I decided I was going to use Amon Ra's recovery because flipz recommended it. That was going well until "- navigate to nandroid restore and restore the previous rom setup". I selected nandroid restore and it said something like /sdcard/nandroid not found. Aster that I just rebooted , which took a while and had me pretty nervous. It eventually booted up though. This stuff is a lot more confusing than windows mobile was haha. I'm wondering if nandroid was indeed unlocked with simple root. I'm still willing to press forward if the help is still available. By the way, what and how can I make a nandroid backup?
Turn phone off, turn phone on holding down volume and power, when you get to white screen select recovery then scroll through your options, i believe it it backup/restore then creat nandroid backup, FYI you cant restore a nandroid backup if you haven't created one, IE the not found error you got before.
Ok so how exactly would I go about flashing(if that's even the right word) fresh rom from what I already have?
I'm not sure what you actually have, can you get to recovery, then the option to 'flash zip from sd card? if you have that option just place the fresh rom on the root of your sd card (put the zip file there and don't open the zip) then reboot to recovery, ie vilume down and power button when you get to white screen volume down to recovery, then flash zip from sd then select the fresh rom zip, then hit power button to select, hit power button again to confirm and away you go.
Ok that sounds simple enough. I can't thank you guys enough for all your help. What does a nandroid backup do?
it makes a copy of your rom basically, so say you put on fresh do a nandroid backup then flas CM6, you decide you dont like CM6, so you nandroid restore of your fresh and presto right back to where you were before you flashed CM6, also useful if you have screwed something up ... you can go back ... make sense?
I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw
did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.
@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com
Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.
Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...
Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse
Yes your just not rooted anymore. Run whatever process worked for you the first time
Try whitslack's method.
EDIT: Nevermind, no can do.
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first
Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse
latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse
I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
BigEdgar said:
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
Click to expand...
Click to collapse
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
cmlusco said:
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
Click to expand...
Click to collapse
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
BigEdgar said:
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
Click to expand...
Click to collapse
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
cmlusco said:
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
Click to expand...
Click to collapse
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
BigEdgar said:
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
Click to expand...
Click to collapse
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
BigEdgar said:
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
Click to expand...
Click to collapse
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
BigEdgar said:
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
Click to expand...
Click to collapse
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Are you able to use adb now? If you can, i have another sugestion i came across in another thread. A guy said he could not access, format, or use his data partition. He claims he fixed it by adb pulling the file system from a working inc, and adb pushing the files to the borked inc, fixing it. If you can get adb to stay connected long enough to push the files it might be worth a try.
cmlusco said:
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Click to expand...
Click to collapse
Thanks again for the suggestions.
I tried that but it's pretty much the same results.
HBOOT--> Factory Reset --> Screen with green arrows --> Red triangle with Exclamation point --> - Power button + Up Volume to get to the System Recovery menu --> Reboot:
Phone hangs on the black/white "htc Incredible" splash screen
One other odd note - if I do this same factory reset process with the USB cable *unplugged*, the instead of hanging on the black/white splash screen, it just goes into an infinite loop (black/white splash screen --> HTC quietly brilliant screen --> droid eye --> back to the black/white splash screen). FWIW this isn't new behavior, I just forgot to mention it earlier. In fact this is what the phone started doing once Verizon pushed the OTA update that screwed up the phone in the first place (there are a number of threads on this over at HTC and VZW forums, but their solutions aren't working for me).
I think this thing is a brick. If anyone has any recommendations for tools that can be used to analyze the partitions on a phone that won't boot, let me know. Otherwise this thing is getting sold for parts : )
Ok, some more progress. Most importantly, I learned that adb has a shell! I obviously didn't RTFM well enough.
Anyways, with the shell I was able to verify that the partitions on the phone are accessible (at least from a Windows machine) and I can, in fact, write files to the device (using "adb push" to push files to /sdcard, for example). That's great as it proves that the storage on the device *is* accessible, but just not from CWM. I followed some instructions that I followed partially before (http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html) in an attempt to see if I could get S-OFF. This tutorial is nice because most of the actions are via adb and fastboot instead of using the UI on the phone, which I couldn't get to. I was able to do most of the work I needed to get S-OFF via adb instead of using CWM or some other recovery tool, which was key, since CWM always tells me that it can't read or write any partitions.
I was actually able to get Froyo installed and boot into it! That's the first time this POS has booted into anything in almost a month!!
Now to my current problem - the last few steps of the tutorial linked above require that I install superuser and unrevoked, and suggest that this be done via CWM. Unfortunately, CWM can't read any of my data partitions, so this doesn't work for me. Not many others seem to have this problem, so googling it doesn't turn up any help.
Is there any way I can use ADB to install superuser and unrevoked forever? I also have access to the UI via Froyo and could conceivably install apks as well.
Here are the instructions from the tutorial that don't work for me, as they rely on CWM:
******************
use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
******************
Those last two steps - install zip from sd card - are the ones that completely fail for me. CWM just gives me a bunch of "E:can't mount /sdcard/" errors.
If anyone has any ideas on how to install superuser and unrevoked using ADB, I'm all ears : )
Thanks!
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
nschiwy said:
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
BigEdgar said:
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
Click to expand...
Click to collapse
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
cmlusco said:
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a few times and while Unrevoked is reporting success, I'm still S-ON and BusyBox and ROM Manager report that I'm not rooted. Back in CWM, CWM still reports errors mounting all drives and is basically crippled. In addition to the "can't mount SD card" errors, I'm also seeing "E:cant mount /dev/block/mmcblk0p2" and "E:Can't mount /cache/recovery/command". Weird. Can't tell if the mount errors are causing my inability to root or my inability to root is causing the mount errors.
(I also tried using AmonRa and got the same "can't mount" blah blah issues). Time for a drink : )
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
eljean said:
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
Click to expand...
Click to collapse
Eljean - that link's a 404...
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
eljean said:
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
BigEdgar said:
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
Click to expand...
Click to collapse
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
eljean said:
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
I appreciate the thoughts, but I think we're talking about different issues here. One of your issues seemed to be that you couldn't access the device at all via USB. I don't have that problem. My USB connection has always been fine. My problem is that CWM can't mount the SD card (or any other drives, for that matter). Everything mounts fine in Froyo, so I'm guessing it has to do with the way the drives are mounted in Recovery vs. Froyo.
The thread you referenced stated that the fix for not being able to access the SDcard was the fastboot oem enableqxdm 0 fix. I tried that a few times but it didn't make any difference.
Thanks for the thoughts!
Team,
I've consider myself a fairly intermediate android root user. I've been doing this for many years, and have never had an issue that I was able to get out of (with the help of the xda community, of course). I've personally never had to post a question on here because I'm always able to find someone who has a similar issue to me. Today though, I am stumped...
I've been happily running Slimkat: http://forum.xda-developers.com/showthread.php?t=2590649 for the past few weeks.
This morning, I decided to try the ElementaX kernel (http://forum.xda-developers.com/showthread.php?t=2249774). After flashing the Kernel, my phone refused to boot up. Usually, I would just reboot into recovery and re-flash the ROM I've running (which includes the ROM's kernel). Every single time I've flashed an incompatible kernel in the past, this method has worked.
After choosing to flash the ROM, it got stuck while installing. The installation just sat there for at least 20 minutes.
Next step - I decided to wipe data/factory reset and then re-flash the rom. Data was able to be wiped, but then it got stuck on formatting cache....
So I hard reset, and decide to restore my nandroid backup - As soon as I boot up CWM Recovery, I get this message
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
When I tried to restore the backup, it just timed out again...
I reflashed CMW REcovery via fastboot, and even tried TWRP Recovery. Nothing seems to work.
If I try and restore my nondroid backup now, I get an MD5 mismatch.
I'm unable to mount /system, /cache and I'm getting nothing when I try and mount USB storage.
I've soft-bricked devices before (we are all careless sometimes), but I was always able to find a solution somewhere. I think I got myself into a situation that's a bit above my paygrade.
Any help would be greatly appreciated.
Thanks.
Are you sure you reflashed the correct recovery? Try this one just for kicks http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img If it still dosent work, i would try an ruu.
cmlusco,
Thanks for the quick reply. I flashed the recovery - Unable to mount System or Cache and PC is not detecting any devices when activating ADB sideload through TWRP.
To be honest, I never of an RUU before. I can research the topic. If you know of any threads that could help me along the process, I would definitely check them out.
thanks again.
The RUU method worked! Thank you very much for suggesting that.
Here's what I did.
1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/showthread.php?t=2428276)
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
Thanks again,
OMG OMG OMG... you saved me
Pharaohnee said:
The RUU method worked! Thank you very much for suggesting that.
Here's what I did.
1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/showthread.php?t=2428276)
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
Thanks again,
Click to expand...
Click to collapse
Some of the RUU's i found the download was funky but here's the one that finally worked
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I was stuck in this situation... something with my cache got messed up when I tried to let ROM Manager update my CWMR... never again.
Glad you got it worked out, could you put solved in thread title it help others, thanks
Hey there,
I hava a strange situation here.
I rooted my phone a while ago. These days I wanted to sell the phone and therefore getting back the stock rom. Didn't worked like I wanted and for some reason I put a PC10IMG.zip on the sdcard (which is the PC10IMG.zip from one of those guides e.g. shenye.co.uk/files/fya-vision-root/PC10IMG.zip) and it installed this one.
Now all seems to be the stock rom and everything fine but I recognized that I cannot access the recovery mode. Actually there comes only a picture of a phone with a red warning sign where I can only remove battery to restart.
In bootloader it says
Code:
VISION PVT SHIP S-OFF
HBOOT-0.85.0008
MICROP-0425
RADIO-26.04.02.17_M2
eMMC-boot
Nov 17 2010,21:21:39
Trying fastboot flash recovery recovery.img results in writing 'recovery' ... FAILED (remote: not allowed)
Also trying the guide from my first rooting on gaining temp root fails on the fre3vo debug part as no exploit is being found.
I have absolutely no idea here. Could someone help me?
That's stock recovery, all is back yo stock except being s-off
You can't flash through fastboot right now due to shipped bootloader
But in the state it is in sounds nearly stock to me
demkantor said:
That's stock recovery, all is back yo stock except being s-off
You can't flash through fastboot right now due to shipped bootloader
But in the state it is in sounds nearly stock to me
Click to expand...
Click to collapse
Ok but what would be the way to "install" a recovery mode? Because right now there isn't any or at least it isn't accessible.
When I go into recovery, I only see this: (picture can be seen at wornermath.de/pictures/recovery_vision.jpg)
That's stock, just press both volume keys in there and options appear (or a combo of other keys, forget)
Ok, I got it. Thought it is something like an error screen.
Power and volume key up is the combo.
In there I can Reboot, Apply sdcard:update.zip, Wipe data/factory reset, Wipe cache partition.
Below all it says: E:Can't open /cache/recovery/command
Is this normal?
Yeah, that happens, most often its nothing to worry about, just reboot, test everything, if all is good just boot back to recovery and do a factory reset then you can sell it
Ok thanks. Made a factory reset and wiped cache. Error still occurs.
But I'm interested why I cant gain temp root with the fre3vo debug? Maybe the new owner of the phone wants to root it again...
If they do they just need to flash a modified PC10IMG.zip to get an engineering bootloader and then they can do as they please from there