Develop Bugs

[Q] Cannot access recovery

Guys,
I am lost. I thought I am not stupied, but it seems I am.
Here's the problem:
After flashing a couple of different ROMs somehow I wasn't able to access recovery any more - I always used a batch to load the recovery, I never flashed in permanently. Now I only see the white HTC screen.
So I unrevoked, a new RUU plus rerevoked but both scenarios give the same result: unrevoked it stopping when it should boot in recovery.
Also I used some batch scripts flying around. and the problem should be that it is not possible to write the recovery.
my phone:
BRAVO DVT1 SHIP S-OFF
HBOOT-0.75.0000
MICORP-031d
TOUCH PANEL SYNT0101
Radio 0-4.05.00.11
Any clue how I can restore recovery???
Thanks in advance.
M

Can you get into fastboot? If you can, go to shipped-roms.com and find your original stock RUU. Connect your phone and place it in Fastboot mode (select Fastboot and wait until it says FASTBOOT USB and run the RUU your phone came with originally). You may need to insert a Gold Card into your phone if you are running a generic one).
I;m just thinking... it could also be a USB brick, see this guide here for a possible fix:
http://forum.xda-developers.com/showthread.php?t=691187
If i were you, i would steer away from manually accessing recovery using batch scripts/pushfiles, especially when connected via USB, as this can always potentially brick your phone. As you were saying, use unrEVOked with a permanent custom recovery like Amon-Ra, or use ClockworkMod. This will make it virtually impossible to brick your phone.
Hope you get it fixed soon.

You could also try running unroked from a linux live cd. People have less problem running it true linux.

Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M

tameike said:
Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M
Click to expand...
Click to collapse
Try placing the 'recovery-clockwork-2.5.0.7-bravo.img' in the tools folder of the android sdk folder, and then drag the tools folder into terminal and type:
./fastboot-mac boot recovery recovery-clockwork-2.5.0.7-bravo.img (to boot the clockwork recovery through fastboot)
or this:
./fastboot-mac flash recovery recovery-clockwork-2.5.0.7-bravo.img (to flash the clockwork recovery through fastboot)
Hope this helps some.

Tried this just now:
./fastboot-mac flash recovery ../recovery-clockwork-2.5.0.7-bravo.img
sending 'recovery' (4216 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
./fastboot-mac boot recovery ../recovery-clockwork-2.5.0.7-bravo.img
cannot load 'recovery'
Does this mean anything to anyone?
Thanks guys...

You are S-on, maybe running alpharev so that you are S-off can help you. But I have no experience with that. If you are S-Off you can use the fastboot commands to push the recovery.

It's possible that the stock RUU you ran earlier may have had an HBOOT update in it forcing s-off to change to s-on, causing the HBOOT to be overwritten.
I s-off'ed not too long ago (i know... i know... it does sound dirty ) and it is a risky procedure as it could end up bricking your phonr entirely if not done correctly. I'm am not certain on what exact procedure to follow on Mac, running Windows 7 here...
If you want to give it a try yourself, you can follow what is suggested in the following guide:
http://forum.xda-developers.com/showthread.php?t=805811
This is what i did to security unlock my phone:
I ensured USB Debugging was enabled.
Downloaded this AlphaRev 1.5 HBOOT reflash utility (.iso file)
Important: Before starting this procedure, it is very important that you do not have your phone sync'd to your PC, as you should only connect the phone to the computer when prompted after the .iso is booted.
I burned the .iso to a bootable CD (you can also boot from a DVD disc or USB key).
Note: You may need to change the boot order in your computer BIOS to either boot from a CD/DVD or external device, like a USB key.
I rebooted my computer and booted from the CD I created, and pressed enter at the flashing cursor - you will know that you have successfully booted the .iso as the screen will display some Tiny Core Linux logos. While I waited, I powered on your phone but I made sure that I had not connected it to my PC via USB. After the initial loading, the screen will prompt you to press any key to continue. After this, I was prompted to connect the phone via USB.
Make sure you wait and only connect your phone via USB when prompted on your Mac. When you are ready, connect the phone via USB (while you are doing this, check the status of your phone as you may be prompted to allow super user permissions to continue). During this process, do not interact with your phone and just let it run it's course. Your phone will automatically reboot a few times during the 3 stages, so do not stop the procedure at any cost.
When it is done, go back into the Bootlader and at the top of the screen, it should show the AlphaRev text and s-off.
Next, you will need to flash the custom clockwork recovery here - http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Then, simply follow and enter the command I posted above (make sure you place the recovery image in the tools folder of the android sdk folder, and execute the fastboot command via the Terminal) to flash the custom clockwork recovery from fastboot, and it should then hopefully get you back on track.
Let us know how you get on with this. I will keep my fingers crossed for you
Regards,
Mas.

Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!

EddyOS said:
Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!
Click to expand...
Click to collapse
I think these s-off supplied devices are supplied specifically for developers as developer phones... i think

[Q] Image Unzipping Fail!!!

Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.

Freesoft64 said:
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Click to expand...
Click to collapse
Try to go into recovery mode. What exactly is the problem. If it is not booting in...go to recovery and select fix permissions... this will solve any problems. If not try to install a rom with full wipe and reboot. If you flash a PD98IMG.zip then once again you need to root, S OFF, etc etc....

Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.

JagDave said:
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
Click to expand...
Click to collapse
Well, actualy, i can`t get into Recovery, it reboots and the screen turns black, the only thing what the phone admits is PD98IMG.zip.
Thank you very much for responding!

Delete that file from your SD card, and check if you can get into recovery. If yes, download superWIPE for ARHD, and ARHD rom and install it ( it's different base i think, so you have to superWipe it )

PD98IMG.zip is the radio, if that's what you need they can all be found here:
http://forum.xda-developers.com/showthread.php?t=996630
Might be worth flashing the latest and seeing if your phone behaves enough afterwards to let you get into recovery.

I take it you are trying from bootloader?
Also does your computer recognize the phone on usb?
Sent from The App that Time Forgot.

Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.

JagDave said:
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
Click to expand...
Click to collapse
I am trying all this and i think it will work, the problem is my phone is "SHIP S-OFF"
But i don`t know hot to change from Ship to ENG...
Thank you very much for the answer, from now in one week i think my DHD will work again

If memory serves, you only need Eng to change the radio.
But don't quote me on that
Sent from The App that Time Forgot.

I have tried this http://forum.xda-developers.com/showthread.php?t=1396253
The PD98IMG.zip worked, so i am glad my desire is not bricked yet.
I still not having access to recovery, my phone is SHIP S-OFF not ENG S-OFF and i can`t change the Recovery, i can`t install the SDK drivers for bootloader.
I tried too with Android Flasher, and there doesn`t work because my phone is not ENG S-OFF.
My questions are this: how i can change now to ENG S-OFF?
What else i can do for revive the Desire HD?
Thank a lot for responding this post, i don`t know what i`ll do without all of you!

Personally I see no reason to Eng soff. You can still flash radios and recoveries with just regular soff. Just its done in a different way.
In that thread you posted their is a link for cwr in a pd98img. Just follow the directions I wrote.(its the first section)
But if you are set on getting Eng soff in the dev section you can use jkoljo tool.
Your second question confuses me. You said your phone is now working so what do you mean by reviving your phone?

Well, i tried ADB, the problem now is when i installed the drivers, in the command prompt i cant find my phone.
I was trying with this:
C:\adb devices
List of devices attached
In Device Manager it appairs like: Android Phone>Android ADB Interface
What i can do now?
I know I'm a little annoying, but I will really appreciate your help if we make it work!

Anyone can help with ADB with desire hd?

Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.

earthbrother said:
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
Click to expand...
Click to collapse
I did that, it doesn`t work because it says "error: device not found" i tried reinstalling many times the ADB drivers and another few with the path file, no results. With "adb devices" it says "list of devices attached" then, nothing.
I am really gratefull with all your answers, i hope we can made it work
I have a question more, it`s posible to put it in "debugging mode" from HBOOT?
Thanks a lot!

So, nobody can help me? that who help me will be rewarded!

You said only the recovery pd98 works. Reflash it. After it reboot and hangs take out battery and SD card. Reinsert battery and enter boot. Wait for it to scan, then reinsert sdcard and enter recovery. Wipe and reflash a rom or backup
Edit - still confused, from your pm you suggested that your dhd doesn't work? I need a simple yes it boots or doesn't, before we can go anywhere
Sent from my Desire HD using XDA App

[Q] Help! Can't go into recovery mode with Desire Z hboot‏ (G2)

I have a Tmobile G2 rooted running Gingervillian (gingerbread 2.3.1) and I tried to install the Desire z hboot to get the Sense ui.
I followed the steps here, "http://www.youtube.com/watch?v=ogZfSWLlvPg"
HERES THE PROCEDURE OF WHAT I DID:
After updating the PC10IMG.zip (Desire Z hboot) folder to the root of my G2, I was stuck on the HTC logo screen after updating. So I followed what the guy said in the video, deleted the PC10IMG file in my SD card then rebooted my phone.
After rebooting my phone, I was booted back same rom. So I flash/recovery my phone through Rom Manager and tried rebooting my phone to clockwork mod recovery mode.
After rebooting, I didn't go to Clockwork Mod but to FASTBOOT screen? I select "bootloader" and it goes to a quick load that says something like "SD loading, no image or wrong image". I select "Recovery" then it goes to the HTC logo for a split second then I'm back to FASTBOOT screen again.
This is the info on the fasboot screen? don't know if that'll help:
Vision pvt eng S-off
Hboot-0.84.2000 (pc1010000)
Microp-0425
Radio-26.02.15_m2
eMMC-boot
Sep 8 2010, 15:65:38
So now, I don't know what to do and my questions are:
1.) Is there a way to go back to the G2 hboot?
2. Can I still fix this and procedure on and install new roms on recovery clockwork mode, using Desire Z hboot? (as the video did)
Please help a brother out I'm still a noob and still learning. If this is in the wrong place, please move it to the correct place.

Anyone? if it seems confusing, please ask questions or if I need to provide more information. I really need help with this. Any suggestions will help.

Zedomax's guide are outdated, he never updated them when new methods surfaced.
Try a downgrade
http://www.youtube.com/watch?v=VdWt65tUBVc

tarroyo said:
Zedomax's guide are outdated, he never updated them when new methods surfaced.
Try a downgrade
http://www.youtube.com/watch?v=VdWt65tUBVc
Click to expand...
Click to collapse
would any PP99IMG.zip file work? And do I basically put it in the SD's root and put it into the boot menu to update the file?
Thanks

by the way, is this compatible with G2s?

don´t put the pp99img.zip on your sd !
do something different:
download a recovery.img (3.0.2.4 for vision):
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
be sure to remove any pc10img.zip or so from your sdcard. then put your phone in fastboot mode (power & tp-wake) connect it to pc and flash the recovery through fastboot by typing: fastboot flash recovery recovery.img
after that you should be able to enter recovery. be sure to wipe before installing a new rom...

hoffmas said:
don´t put the pp99img.zip on your sd !
do something different:
download a recovery.img (3.0.2.4 for vision):
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
be sure to remove any pc10img.zip or so from your sdcard. then put your phone in fastboot mode (power & tp-wake) connect it to pc and flash the recovery through fastboot by typing: fastboot flash recovery recovery.img
after that you should be able to enter recovery. be sure to wipe before installing a new rom...
Click to expand...
Click to collapse
I'm assuming I need to do ADB? If so, Is there a way for Mac ios

prototype2 said:
I'm assuming I need to do ADB? If so, Is there a way for Mac ios
Click to expand...
Click to collapse
Yes, you can run adb on a Mac. See the link to my adb guide in my signature (assuming you're not viewing from the XDA app, which doesn't show the full sig).
Sent from my Desire Z running CM7.

Okay, just to make it clear (I am a "step by step" guy when it comes to technical computer/phone stuff.), from my understanding:
1. Download the recovery.img (3.0.2.4 for vision) and put it in the root of my SD card.
2. Delete any pc10img.zip files from SD card.
3. Turn phone off and then turn phone onto FASTBOOT mode by holding power/volume down/camera or power and tp-wake? (Btw what's tp-wake? and during this process, is the phone in fastboot screen mode while I'm about to type the "flashboot flash recovery recovery.img"?
4. Connect to computer, open up terminal (Mac) and do the ADB process and type in "fastboot flash recovery recovery.img"
5. Wipe clean and install new rom in recovery mode? (Clockwork Mod recovery mode?)
PLEASE correct my steps or add in any steps that I'm missing. I bought my phone rooted so I never went through these steps before. Anyways please correct me, I don't want to ruin my phone anymore than it is already.

anyone can review my steps?

good morning
ad step 1: don´t put it onto your sd; put it into the adb tool folder on your pc !
ad step 3: tp-wake = the square button at the bottom of your phone (the one that acts like a mouse); to enter fastboot mode press power & tp-wake
...the phone should be in fastboot mode while typing the command.
before you type "fastboot flash recovery recovery.img" type "fastboot devices" and look if your phone shows up... if so go ahead with flashig the recovery (by the way, you may have to rename the recovery file)
step 4 and 5 look fine...
good luck

okay, I will try it in a little bit here.

In FASTBOOT USB mode, it wont recognize my device but when my device is fully on, adb works.
I get when I type "flashboot devices" (while the phone is on FASTBOOT) in terminal and get:
"-bash: fastboot: command not found"
By the way, I renamed the downloaded flash to "recovery.img" and put that file in the "platform-tools". Don't know if that'll work.

The "fastboot" command should be on your PC in the same folder as the "adb" command. Where did you get adb from, did you install the SDK and platform tools, or something cut-down ?
Sent from my Desire Z running CM7.

hm... that means that you do not have fastboot installed. maybe google for fastboot on mac, because i have a linux system... so i can´t help you in that point.
other thing you could do is following this guide (it´s a pc10img.zip with dz hboot and clockwork recovery):
http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html
but first i would try the fastboot method - it´s safer.

Okay, I got the fastboot devices to read my phone. But it cannot load my recovery.img?
This is what got when I typed in "fastboot flash recovery recovery.img" :
error: cannot load 'recovery.img'

rename it to recovery and try again...

It's not loading the img file for some reason..

prototype2 said:
It's not loading the img file for some reason..
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/wiki/Fastboot
or use the virtuous link...

hoffmas said:
http://wiki.cyanogenmod.com/wiki/Fastboot
or use the virtuous link...
Click to expand...
Click to collapse
that link isn't working

Can't format /data & /cache

Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.

Leshy01 said:
Hi!
I think my /data partition is corrupt. Anytime I flash a new ROM, a handlful of apps I've previously installed are preloaded when then ROM first boots up. I've wiped my dalvik cache, superwiped multiple times, and did a factory reset multiple times, but no matter what ROM i install (JB, CM7, MIUI, Original Sense [Liberation]), those apps are still there, and causes forces closes.
So I went into CWM, and tried to manually format the /data partition and I get the "Error formatting /data" For that matter, this same error happens when I try to format /cache.
I've trired multile ROMs, multiple kernels. I've triend Amon Ra, (I couldn't install TWRP because of a status 7 error). I've deleted the /data folder through adb/fastboot (and it reappears afterwards).Like I said, I've done factory resets, tried formatting each partition (both with the partitions mounted and unmounted), superwipe, fixed permissions..I'm at a complete loss on what to do next. I'm willing to erase everything entirely from the phone and start from scratch if I have to, but I have no access to do anything. Did I brick my phone? I had previously used the EXT4 mod, but I've ran the zips to revert to normal already.
Click to expand...
Click to collapse
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?

cmlusco said:
First off, i am unaware of a script that reverts the ext4 mods, where did you get it from? First i would try an ruu, if that dosent fix it, i would try fastboot flashing the misc partition, and then do the froyo ruu and reroot. Are you s-off? What radio and hboot version?
Click to expand...
Click to collapse
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.

Leshy01 said:
Thanks for the quick reply! I guess I should clarify regarding ext4. I used the "no_data_limit_dalvik_moved" mod to move the unused datadata partition for my /data/dalvik-cache folder. Seeing as how the ext4 modifies the /data AND /cache partitions, and those are the only two that are giving me trouble, I'm thinking that might be the cause of my troubles.
Haven't tried an ruu yet so that'll be my next step. But what do you mean by flashing the "misc" partition? I'm at work so I'll have to try that when I get home. Might have to look up how to flash the ruu too. It's been a while. lol
Am I s-off? Yes.
Radio? 2.15.10.07.07
hboot: 0.92.0000
Edit: So I tried flashing both RUUs (PB31IMG version) Gingerbread AND froyo found here. With both instances, the phone would freeze on the boot image. (Where is says DROID, then those little red dots circle the middle camera twice).It reset and continues to bootloop over and over.
Click to expand...
Click to collapse
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.

cmlusco said:
Ok do you have adb and fastboot setup on a pc, you will need it to flash the misc partition? It sounds like your partition tables may have gotten messed up. The misc partition is where this info is stored. If or when you have adb fastboot and their drivers installed, i will tell you how to flash misc. Also in the meantime, try flashing this ruu just for kicks http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.
Click to expand...
Click to collapse
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.

Leshy01 said:
Thanks! I have adb/fastboot on my home pc, yea. So you can tell me what to do, then I'll get home and try it, and then post results. I'll try that ruu as well and let you know. I tried following some direction online usin parted, but I couldn't make heads or tails of which partition was which.
Click to expand...
Click to collapse
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc, and select fastboot from the hboot menu, so that it says fastboot plug in red at the top. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
fastboot devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.

cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.

tiny4579 said:
cmlusco, you get thanks for being so willing to help other members with their issues. I think you deserve more than I gave you today but I think it's cool how you're always trying to help people with potential bricks and when you tested out kernels and such for me.
Click to expand...
Click to collapse
Thanks tiny, you do great work yourself. I like helping people and i love technical stuff. Knowledge is everything, and its good to pass it on.

cmlusco said:
After you run that ruu i posted, your hboot version should be updated to 1.07. You will then need to go to http://www.htcdev.com/bootloader, and follow the steps to unlock your bootloader. Skip the first couple parts where it has you set up fastboot and skip the bootloader update part (ruu) and start where it has you get a code from your phone (Unlock token). Finish the rest, of the unlock steps and you will see at the top of hboot it now says unlocked.
Once unlocked download this file http://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, and place it on your pc in the same folder as the fastboot.exe file. Then boot the phone to hboot, and connect it to the pc. Open a cmd prompt on your pc to where fastboot.exe is, and type the folowing:
Code:
adb devices
It should show a string of numbers. If it says no devices found, something is wrong with the connection between the phone and pc, or the adb drivers are not setup right on the pc.
If the connections fine and it found your device then type :
Code:
fastboot flash misc mtd0.img
Now download this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip, and flash it thru hboot. Once it compleets reboot, and hopefully it boots up like it should.
If it does boot and all is well, then reroot by flashing cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot, and then flash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip, thru recovery. From there you can flash a rom of your choosing.
Click to expand...
Click to collapse
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?

Leshy01 said:
Curiously, I've only gotten as far as "adb devices" Although I can perform "fastboot reboot" and "fastboot devices" I try "adb devices" and the list is blank. I've used the drivers included in the android sdk. I've also used the drivers from htc sync. I don't know why I can't find my device in adb though. To be clear, my phone says "HBOOT USB PLUG" while I'm trying this.
thank you so much by the way for all your help. And you too tiny. I feel like I'm standing on the shoulders of giants here!
Also, is there some irc channel or something with a bit less idle time between forum posts?
Click to expand...
Click to collapse
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
I do not know of an irc channel, and i like to keep the conversation here so that the instructions and common issues and fixes can be seen and learned from by others.

cmlusco said:
Oops, i ment to put for you to type fastboot devices not adb devices in those instructions, that was just a mistake on my part. I dont think you can even access adb from hboot. As long as fastboot devices works your good to go. Also you will want to select fastboot from the bootloader menu after connecting the phone. So it should say fastboot plug in red not usb plug in blue when entering the commands.
Click to expand...
Click to collapse
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.

Leshy01 said:
Oh well in that case I get an entirely different issue. "Fastboot devices" works but when I try the flash command you suggested:
Code:
sending 'misc' (640 KB)...
OKAY [ 0.119s]
writing 'misc'...
FAILED (remote: not allowed)
finished. total time: 0.129s
Man, talk about frustrating.
Click to expand...
Click to collapse
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?

cmlusco said:
Did you unlock the bootloader with htc dev? Does it say unlocked at the top of hboot?
Click to expand...
Click to collapse
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.

Leshy01 said:
Yep. *** Unlocked *** in pink at the top.
HBOOT 1.07.000
And my screen says FASTBOOT USB in red. When I enter "fastboot devices" I get HT0B2HJ05729 fastboot, so I know that works. As does commans like reboot.
Click to expand...
Click to collapse
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.

cmlusco said:
Hmm thats strange having the boooader unlocked should allow remote. Mabey thats not allowed, i thought it was. Sorry let me dig up some info i believe there is another way.
---------- Post added at 12:44 AM ---------- Previous post was at 12:17 AM ----------
Ok download this http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img and place it on your pc where fastboot.exe is and open the cmd prompt and type:
Code:
fastboot flash recovery recovery.img
And then reboot the phone to the bootloader again and go to recovery and flash this http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip. Just for kicks see if you can mount data or cache from the mounts and storage menu. If you can your issue is probably fixed, if not try this. Download and unzip these files http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip and place both of them in the same folder on your pc as adb.exe. Then while in recovery with the phone connected open a cmd promt to where adb is and type the following hitting enter after each line:
Code:
adb push flash_image /system/
adb push mtd0.img /sdcard/
adb shell (you should get a prompt with a # sign)
cd /system
chmod 0755 /systeml/flash_image
cd /system
./flash_image misc /sdcard/mtd0.img
exit
adb reboot recovery
In recovery go to mounts and storage and mount usb storrage and place this ruu http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip on the sdcard. Then in your cmd prompt type:
Code:
adb reboot bootloader
Once in hboot, select bootloader from the menu amd wait a few secs for it to find the ruu and pronpt you to flash it.
Click to expand...
Click to collapse
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/

Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?

Leshy01 said:
So I was able to complete all your steps without getting any errors. After flashing superuser, I still couldn't format /data or /cache (mounting was never an issue - or at least I wasn't given any errors about it before) However however after flashing the stock ROM, I am still getting the bootloop. I can't check the /data and /cache partition since its no longer running CWM though, but this is the same scenario I was in previously. I'm sure I'm giving you a challange here. Is there a way to manually re-partition everything manually, instead of just formatting?
So like I said, I ran the steps provided above, and still got the bootloop. So I flashed CWM and same as before, I am unable to format the /data and /cache partitions.:/
Click to expand...
Click to collapse
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2

cmlusco said:
Im not sure. If there is a program or a way to manually fix the partitions, i am unaware and it is probably over my head.
Flashing the misc partition should have fixed any errors with the partition table. The fact that it didnt fix it leads me to believe that the partitions are fubar.
One thing bugs me though, you said earlier that you never had an issue mounting the partitions, just formating them. So can you mount data in recovery, and then view its contents or pull and push with adb?
Click to expand...
Click to collapse
Well... I'm sketchy on the exact terms here, but In CWM, I can mount the drives without getting any errors, but whenI try to format I get errors. I haven't actually "done" anything with those partition besides that.
However. I ran through ALL the steps you had me to. Flash the stock ROM w/ recovery, unlocked bootloader from HTC, pushed all the filies you had me through adb. After all that, I flashed CWM, then I flashed CM7, and then I booted up my device. As if my /data partition was not touched, all my apps were still there (titanium backup, my google accounts were still setup, app data and settings were untouched). So on a whim, I ran titanium backup, and uninstalled every single user app (since the android native uninstaller force closes). I ran it successfully, rebooted, and every other app was still there.
So it can READ the /data partition, but I have no abilities to MODIFY that partition. Through any recovery or formatting.
tiny4579 said:
Parted. It already exists in recovery and can be run in adb in recovery. Try that. I can't give directions but be careful. I think I tried to help someone before with this but can't recall the thread. It'd b a good starting point.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm willing to try anything because at this point nother else works, but I don't know where to start. And even if I find some documentation about other devices' partition table setup, I'm assuming the Incredible is different. Way I see it, I can't mess it up any more than it already is.
I'm hoping you guys have some sort of answer, but I'm looking around elsewhere, and I really appreciate everything you guys have contributed to this thread, and the community. Thanks!!!!!

Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?

megosu said:
Hi guys,
I have the same issue (with a galaxy s2 though), anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?
Click to expand...
Click to collapse
I don't think the mmc bug has anything to do with the Droid Incredible or even affects it. I thought the mmc bug led to a fully bricked phone.
This isn't really the thread for this but have you tried the full Odin Factory reset for your device which includes the /data partition? I think the method that uses a PIT file is the most thorough but most risky. I recommend posting any questions in your device's thread but I've had a few samsungs and am somewhat familiar with that process.

[Q] Red Triangle and Exclamation point - won't boot and PC won't recognize

I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you

Look at the following thread, may be this can help
http://forum.xda-developers.com/showthread.php?t=2662787
Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse

Dugoutdog said:
I was S-Off and rooted with Roadrunner. I went ahead and accepted 4.4 OTA fully expecting to lose S-Off and Root.
What I got was a phone that can't recognize the SD card, and won't boot past the white HTC screen (does it twice then shuts down to red triangle and exclamation point. I've tried to get to the main white admin. screen (vol. up and power) but no luck. I have go to a blue screen offering:
a reboot system - doesn't work
apply from SD card - phone can't find it
apply from phone storage - can find no files
apoply from cache - can't find any files
wipe data factory reset - did that and still nothing
wipe cache partition - didn't know what this would end up doing so I haven't tried it.
At the bottom of the screen in green it states :
Mount SDCARD Failed 1 time through 5 times.
Cannon mount SD Card (no such file or directory)
Write host_mode: 0 Done
I only wanted to get to 4.4, S-Off, unlocked, and rooted to get rid of bloatware. I've rooted before but i'm pretty much a noob (I've been reading here for 2+ years) but am lost understanding programmer language.
Can anyone help me? I'm lost as this is my only phone (I don't have a land line)
Thank you
Click to expand...
Click to collapse
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2

Just a little more info Gizmoe please
Gizmoe said:
Did you try and update while having a custom recovery and/or Rom installed? Also bootloader is power+volume down. The ota won't effect s off or locked status. Just get to fastboot and boot to RUU mode and run stock RUU. Then take updates to 4.4.2
Click to expand...
Click to collapse
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.

Dugoutdog said:
I wrote of my problem in middle of night and blanked on getting to bootloader. I am there now. Fastboot takes me to Fastboot USB. RUU mode isn't an option under fastboot just bootloader, reboot, reboot bootloader, and power down. My PC is not recognizing the phone. I was running stock ROM. I don't recall doing anything special as far as recovery since that would be beyond my learning curve.
Click to expand...
Click to collapse
Can you send fastboot commands like
Code:
Fastboot devices
And see your device listed?

PS: to above
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).

Dugoutdog said:
Also just noticed my phone is now saying UNLOCKED which it wasn't before. Just S-Off through roadrunner (and still S-Off). . My contract was up on Friday and called Verizon to get unlock info but they said they didn't supply that info. I needed to go to a third party (figures).
Click to expand...
Click to collapse
Did you read my other post. Can you confirm if you have fastboot connectivity? RUU mode is a command not a list option.

gizmoe
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.

Dugoutdog said:
I can get to the FASTBOOT USB command with bootloader, reboot, reboot bootloader, and power down. My PC made a nolise as if it recognized and connected to the phone but it is not listed.
Click to expand...
Click to collapse
You have connectivity then. It's not going to list it in " my computer" unless its booted into Rom. Just use this thread
http://forum.xda-developers.com/showthread.php?p=46286588
To flash RUU. Don't do relock or s on just flash the stock RUU.

This is where I'm lost again
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.

Dugoutdog said:
If I can't see it in my computer then where do I type the codes? I'm very appreciative of your help but I'm in uncharted waters here.
Click to expand...
Click to collapse
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.

my sub-directory
Gizmoe said:
Use cmd prompt. Did you setup adb/fastboot when you used rumrunners? In command prompt with phone plugged in while on boot loader screen type fastboot devices. If you see a serial number returned you are connected. Typing fastboot oem rebootRUU will put the phone into RUU mode where you can flash the decrypted RUU.
Click to expand...
Click to collapse
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.

Dugoutdog said:
So far so good. It returned FA37GS912166 fastboot.
Typing as directed it returned
<bootloader> Start Verify: 0
OKAY [0.050s]
finished. total time 0.050s
I have a black screen on my device with a white htc showing. Now I just don't know where to get the stock RUU. I went to nosroms.com but page is gone. Went to htc1guru.com and found this one there.
RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted
File Size: 1.1 GiB - Downloads: 1170
MD5: 2704d492d580887e2741c8a6b7fd620e
Comments: modelid: PN0731000
cidnum: VZW__001
It's downloading but REAL slow. Might be done by the time I hear back from you regarding folder.
Click to expand...
Click to collapse
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621

now waiting
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Waiting for download to finish and getting ready for work. It will be close to see if I get it done before I have to leave. If not will finish at 3:00am when I get home and get back to you either way.

almost home
Gizmoe said:
In santods thread at bottom of post #2 look for the decrypted ones. You can download whichever one. I would use the most current and then let it update to kit Kat from software update on phone.
http://forum.xda-developers.com/showthread.php?p=46506621
Click to expand...
Click to collapse
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.

Dugoutdog said:
Ok. Have santods file "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted". I can't remember....do I leave it zipped? If unzipped what file do I use??? recovery_signed.img? If left zipped where must the directory be located? if unzipped where do the files have to be?
I won't forget a big thanks when this is done but thanks for getting me this far. Awaiting your reply.
Click to expand...
Click to collapse
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.

Command Error
Gizmoe said:
Just leave it zipped. Rename to RUU. Then put it in same directory you are in while using cmd prompt. Then type fastboot oem rebootRUU. Once phone is on black screen with silver letters type fastboot flash zip RUU.zip it will do some stuff and then fail saying to flush the image. Just repeat the fastboot flash zip RUU.zip again and it will succeed. You then will be complete stock. Then you should have no problems updating to kitkat either.
Click to expand...
Click to collapse
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.

Dugoutdog said:
I'm getting a {ERR} command error.
entered " fastboot oem rebootRUU.zip" also tried fastboot oem rebootRUU", "fastboot oem reboot RUU", and "fastboot oem reboot RUU.zip" in case you forgot the space between reboot and RUU.
It is in the directory where the fastboot.exe is located. It is a zipped folder called RUU.zip.
I called in SL for tonight as I really want to get this done tonight. Too much at stake.
Click to expand...
Click to collapse
First type fastboot devices and make sure its connected. Phone needs to be in fast boot mode. Screen should read fastboot usb in red letters. Then type exactly
Fastboot oem rebootRUU
Then
Fastboot flash zip RUU.zip
RUU.zip needs to be in the same directory cmd is reading.

Something is happening . . . . . "sending zip"

resent as failed like you said.
failed as you stated . . . resent. It also said failed resend immediately. something is gyrating.
OK. at bottom of command prompt it says "Successful OKAY 249.248s" Finished total time 312.192 sec.
My phone has HTC in white small letters and a solid green bar below it.
Before I screw anything from this point, what do I do now? Just press the power button?