Develop Bugs

[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ClockworkMod Recovery - Modified for Motorola Xoom​
OK, so this recovery will skip /data/media (Internal storage) when performing nandroid backups and also when you perform a factory reset.
This means that we can now perform nandroid backups without backing up our internal media and removing it everytime you want to do a backup.
Thanks to Bigrushdog and MadIndustries for helping out with the concept of the solution for skipping /data/media.
Also thanks to Koush and all the other developers that have contributed to clockworkmod, without you guys the android world would be completely different.
Thanks also to everyone in #xoom that tested this.
The source code for all changes etc are available through the github repository. The two other projects that have been modified to make this recovery possible can also be viewed through my github account.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
==============================================
General Notes
When I refer to /data/media, this is the same as /sdcard when the xoom is booted into honeycomb. So any data that is stored in here should be untouched by this recovery.
If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard. This will revert to the old way of formatting /data. NOTE: by doing this you will lose everything that you have in /data/media.
Versioning of recovery images:
At the moment I don't have a version number as such, instead each recovery image is timestamped in the format of DDMMYY-HHYY. So the file recovery-solarnz-120511-2030.img was produced on 12 May 2011 at 8:30 PM. This versioning is also shown in recovery when it starts.
==============================================
Downloads
SLOW DOWN AND RELAX
Make sure you download the correct version depending on how you want to flash. I have seen at least two xooms bricked now because they have tried to flash the zip file through fastboot.
Recovery Zip (solarnz-R4c-100611-1150) FLASHED THROUGH CWM
MD5: 1ad409db4030635734b27df02b7e7c1a
Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
==============================================
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or any other method
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Sit back and relax while recovery flashes the new recovery and reboots into it.
Click to expand...
Click to collapse
Method 2 Without CWM
Download the recovery image (not the zip file)
Pull up your command prompt, then
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
fastboot reboot
Let your Xoom boot up. Then to check out your shiny new recovery,
Code:
adb reboot recovery
Click to expand...
Click to collapse
Also, you can grab Rom Manager or QuickBoot from the market for easy access to recovery.
==============================================
Changelog
Code:
[url=http://bit.ly/k7cZxJ]3.2.0.0 (R4c-100611-1150)[/url]
- Rebuilt recovery, the previous recovery was built off of bad device files.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4b-060611-1300-cwm.zip]3.2.0.0 (R4b-060611-1300)[/URL]
- Disabled partitioning the sdcard as per request.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4-050611-1515-cwm.zip]3.2.0.0 (R4-050611-1515)[/URL]
- Included changes from koush's sources upto clockworkmod 3.2.0.0
- Implemented Advanced backup. This allows you to choose what partitions you want to backup.
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-120511-2030.zip]3.0.2.8 (120511-2030)[/url]
- Fixed mounting the sdcard for some users
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-080511-1630.img] 3.0.2.8 (080511-1630)[/URL]:
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method.

Great job guys!!!!
Sent from my HTC HD2 using XDA Premium App

You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.

Win
Sent From My Evo

Great job folks!!!
We've gotten used to BRD's awesome formatting of his posts and super clear instructions, would be real nice if we can get this on the new sticky

bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?

jland22 said:
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?
Click to expand...
Click to collapse
Rom manager is still nice as you can quickly reboot to recovery etc from it. It also allows you to select the operation to do in recovery and then restart it will automatically restart and perform the action.
If you flash recovery from Rom Manager, you will end up with the official 3.0.2.5 recovery from Koush that doesn't contain the method of skipping /data/media

bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App

lokko21 said:
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.

What folder do i need to flash this too?

b0ricua said:
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.
Click to expand...
Click to collapse
Gotcha so I'm cool, thanks.

ok just flashed, looks good

Solarnz, thanks for formatting the OP and adding clear instructions!!
You da man!

very cool, but would it be complicated to just make an "exclude" menu before backing up? That way people can just exclude whatever they want ...

thanks to everyone who contributed. We dont always think about how great CWM is and all the wonderful things it does for us until we dont have it anymore I didnt like the feeling of walking around with that stock recovery

running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.

maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?

Prod1702 said:
running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.
Click to expand...
Click to collapse
Ok, I'm assuming you are on android 3.1 without a modified kernel.
The issue you are having is that with the default boot image, it flashes back the stock recovery every single time you reboot.
Code:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
(Thanks Berzerker7)
ltracte said:
maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?
Click to expand...
Click to collapse
Ok. on our xooms, /sdcard is actually a symlink (think of a shortcut) to /data/media.
So when I say /data/media, you can think of /sdcard (the internal storage).

random one again - will this be available via ROM Manager? it's still 3.0.2.5 there
thanks!

E: can't mount /sdcard/update.zip
or error mounting /sdcard
anyone has encountered this problem plz?
thks

[Q] Where to start?

Hi,
I just bought a Desire today.
its
S-OFF
rooted
running leedroid v2.3d
thats all I know.
Im downloading the InsertCoin Sense 2.1 1.0.8 CM7 Rom right now.
How do I get things right without messing up my phone?
pls someone guide me how to install this rom propely and what's the required files etc2
Im really confused right now.
read a bunch of stuff here and couldnt find an answer
hopefully someone would help me out
thanks!
edit:what's the MD5sum for?
it says as a requirement on the insercoin thread that its either a
A2SD CM7 HBOOT - cm7 hboot from alpharev.nl - the one with 130 mB for /system
- 1 gB ext2/3/4 partition
A2SD+ STOCK HBOOT - stock hboot - the one with 250 mB for /system
- 1 gB ext2/3/4 partition
Click to expand...
Click to collapse
which one should I use/download?
the ROM that I downloaded has a md5sum of MD5: b7e9f7e7dc60b79874920dfcde50ac76
please please anyone?

MD5 sum is to chceck if your download was uncorrupted. MD5 of downloaded file must be identical to the one provided in ROM thread ALWAYS CHECK MD5 SUMS, if you flash for example corrupted hboot or radio it WILL brick your device
now, what you must do, since you are already rooted and S-OFFed:
1) make sure you have 1GB ext3/4 partition on your SD card, AFTER FAT32
if it is there, you are OK, if not use Gparted (bootable CD) to make one, mount SDcard in recovery and partition your SD
2) since you downloaded CM7 hboot version of insertCoin go to alpharev.nl and download CM7r2 PB99IMG then put it to the root of your SDcard and boot phone into bootloader (vol down+power) then wait until it finds the file and accept the flashing of new hboot >> this will change partition layout. [2nd method possible but you would have to have ADB @ pc correctly set up, which i doubt you have, so do it PB99IMG way CHECK MD5)
3) boot into recovery, wipe all, wipe dalvik and choose to flash downloaded insertcoin.zip
once it ends reboot, and after 15min it should boot up android, if not pull the battery cause smth didnt work out.
what could have gone wrong:
-your sd-ext wasnt done properly (double check or re-do)
-your recovery was outdated (report back here, i will help you updating it)

thanks for the response!
how do i check for the md5 of my downloaded file?
I have a clockworkmod v2.5.0.7
im downloading gparted now and will the files on to a disc after.
or can I use any partition master apps?like minitool or easeus partition?
please guide me how to partition it properly
its a 16gb kingston class 6
and how do i update my recovery just do be sure
edit: sorry for these noobie questions. I was really shocked how hard it is compared to flashing hd2s and defys
and yeah I have adb installed on my pc with the required files in it. the thing is I never used it. not even once sorry :0
anyway will try repartitioning my sd card now

you can check MD5 with program called HashTAB: once you install it, right click on file, choose properties and choose file hashes panel.
updating your recovery: find topic here on desire forums for clockwork mod 4.0.0.5 - if you download a .zip file you can use a fake-flash method which means booting into CWM 2.5.0.7 then choosing to flash CWM4.0.0.5.zip and this will launch new CWM, however you must do it every time you go into recovery.
if you want a permanent install of CWM 4.0.0.5 download its .img file, check MD5, put it into your androidSDK folder, put your phone into fastboot mode (back+power) and in windows command prompt (cmd) type:
cd X:/ANDROIDSDKLOCATION/tools [navigate to your SDK installation folder]
fastboot devices [this should give a serial number]
fastboot flash recovery FILENAME.img [.img file must be inside /tools folder]
and it will flash it permanently
you can find a video tutorial on how to partition SD in Desire Android Development sticky thread, its one of the first 3 or 4 threads, videos for noobs, all is there
also in thread tagged [TUT] you can find video on how to use ADB

I just partitioned my sd properly w/ gparted
downloaded the Desire_recovery-clockwork-4.0.0.5-j_r0dd_mod.zip
what do you recomend?fake flash or flash it permanently?
and could you please clarify this
2) since you downloaded CM7 hboot version of insertCoin go to alpharev.nl and download CM7r2 PB99IMG then put it to the root of your SDcard and boot phone into bootloader (vol down+power) then wait until it finds the file and accept the flashing of new hboot >> this will change partition layout. [2nd method possible but you would have to have ADB @ pc correctly set up, which i doubt you have, so do it PB99IMG way CHECK MD5)
Click to expand...
Click to collapse
I downloaded the PB99IMG_cm7r2.zip, what should I place on the root of my SD card?the zip file or the .IMG file?then once I press vol+power I just wait then accept then it will install it?
then after that I just copy the nandroid backup onto my SD card and flash?
one more thing.
what's the best or recommended radio?
note:I cant connect to any data connection.either using 2g/wcdma,wdcma only or 2g only.
I dont know if it's the rom or what.hope its not a hardware issue though
My reception is always full by the way
note:here's what I did. placed the PB99IMG.zip on the sd then turned the device off then pressed vol down + power, a prompt asked for a update.I said yes then asked me to reboot. I answered no then went to clockwork recovery then flashed the insercoin rom after wiping cache and dalvik and factory data reset.rebooted the device and now im waiting for my phone to completely boot.
hope I made everything right

you gotta read more carefully dude
as i said, if you downloaded CWM.ZIP (ZIP FILE) FAKE-FLASH is the ONLY thing you can do with it. if you would have .IMG FILE permanent flasing from fastboot would be the only possibility. SOZ BOUT THAT !!! i just looked at this files, it is not flashable ZIP, this is an .img file packed into a .zip (LOL) unpack it, check MD5 Sum provided inside the .zip file and flash it using fastboot !!!
also some instructions taken from alpharev.nl (they are just under the table with hboots): You can also download the corresponding PB99IMG zipfile, put it on your sdcard, and rename it to PB99IMG.zip. Then start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC. It is however still necessary to either restore your nandroid, or reflash your ROM after doing this. The partition LAYOUT has changed, the actual data still needs to be 'moved'.
so rename the cm7r2.zip you have to PB99IMG.zip and put it on your SD (not in any folders) then go to bootloader with VolDown+Power, wait around 10 seconds and confirm flashing new HBOOT
after doing this, you cannot simply restore a NANDROID (if a ROM was made for stock hboot, it will not work on CM7 hboot this should be kinda obvious) you must flash a ROM designed form CM7 hboot so, for example InsertCoin CM7 (it is because on stock hboot system files are 250MB, and then on CM7 you have only 145mb, so restoring a NANDROID that had 250MB/system wont work, wont fit, wont boot)
i suggest you read full info available on www.alpharev.nl
best radio ? well i am an up-to-date geek so i always use the newest though you should be fine with any. if you encounter any problems though (with reception or wifi etc) you should consider upgrading your RADIO. however if you will change your HBOOT to CM7 (which is also treated as data++ by alpharev AND Ultimate Online Kitchen cause of the /cache size) you will be able to flash new radio ONLY from fastboot (it is also said on alpharev.nl :If you downloaded Bravo Data++, please notice the /cache partition is too small to hold Radio flashes from recovery. You can however flash the radio just fine with 'fastboot flash radio radio.img'. Just extract the radio.img from the radio update.zip beforehand.)
about data connection.
go into settings > wireless > acces points (you gotta find it, i dunno how are these named in other laungauges) and set up your APN correctly (you should find correct settings for your mobile provider on thier website, or just google it)
closing remarks:
remember that if ANYONE was helpful to you, hit the 'thanks' button if you got any more questions, i am more than happy to help

thanks a lot bro!
Im now running on insertcoin w/o any probs.
many many thanks for your help.
PS:gave you a couple of thanks

[Q] Cannot flash other ROMs after installing CM 7.2

HI,
Ever since installing CM 7.2 I cannot flash any other roms, I get constant HTC screen or staying on Android logo. I am not new to flashing custom roms .
I have done all wipes before an installation and after to see if that makes any difference (sadly not) The only rom that works is CM 7.2!
Anyone got any ideas what to do
thanx pp

Try removing Battery and then again switch on the phone
then same
vol dwn + power
recovery
then flash new rom

Try installing an official ruu then after that try another custom rom.

still no joy ! unrooted back to stock then rerooted and still the same

Perhaps you need a GoldCard to install a ruu official ROM.

seems my device cannot handle OC roms! any ideas why??

I had the same problem, and even CM7 stopped working....don't think my phone likes overclocking either, even if i install the overclocking kernel on stock rom, the phone goes mad!
to get back to stock:-
-if you are able to get to CWM recovery, go to that first and clear all cashes, format all drives, just basically choose EVERY "clean", "clear" and "format" option to wipe everything from the phone.
-use the same directory you used for the htcdev unlock (usually c:\android)
-search this forum for a thread called "s-on gsm how to upgrade to 2.3.5" or something like that, and download the file "Gingerbread 2.3.5 (v2.13.401.2).zip".
-extract this file and find within it "rom.zip"
-extract rom.zip to the same folder you're using (e.g. c:\android)
-you should now have files called C:\android\boot.img, c:\android\recovery.img, and c:android\system.img.
-open up a command prompt window and navigate to c:\android\
-turn your phone on while holding down the -vol key to get to hboot menu
-choose "fastboot"
-connect your phone to your pc via usb, you should see it say on your phone screen "FASTBOOT USB" or something like that, in red letters.
-now, on your pc, use the following commands to flash everything back to stock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
after this is done (usually only a few minutes), exit the command prompt, power off the phone and restart.
you should now have a fully restored back to stock and working ROM (although you will have to set up all your contacts, all your home srceens, options, settings, and re-download all your apps etc.
-if it's confirmed working, i reccommend then IMMEDIATELY installing CWM recovery, and making a full backup, then next time things go drastically wrong, you should be able to wipe everything then just install this backup (remember to store the backup on your pc, don't just keep it on your mem card).
good luck, this method worked for me, so hopefully you will at least get a working phone again, and if you then want to try other custom roms, you can....but i think some phones are more picky when it comes to overclocking.....i can't run anything that overclocks without the phone freezing/crashing/needing battery pull and reset.

thanks. i will give it a try

Bootloop After Trying to Unroot

Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
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
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.

That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.

Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!

So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?

double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...

I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?

double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.

Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.

double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe

Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.

RUU fail

Hello, My HTC desire is unstable (hard reboot so many time) and i d like to back to full stock rom, radio, hboot, unrooted etc.
But when i try to run a RUU, my phone reboot into HBOOT and the RUU fail (no connection)
This is picture of my HBOOT where RUU fail:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My down volume bouton is down. So i'm limited.
I can use adb command line and reboot in recovery with rom manager.
Any idea how can i restore my phone to stock
Thx

Use bortak's troubleshooting guide stickied to the top of Q&A
Find and flash the 2.3.3 RUU, nothing else.
If you can't run it from a computer, use the PB99IMG.zip method

I'm looking some help in bortak's topic but nothing works for now.
As i say, RUU start, reboot my phone into HBOOT and the RUU process stop.
I try too the PB99IMG.zip copy in my root of my SDcard but that doesnt work.

Strange
I don't think I've seen that screen either.
Things to try:
- Flash the alpharev downgrader.img from alpharev.nl, then reboot bootloader. I think it should say Alpharev Unlock at the top of the bootloader screen. Then try running RUU again.
- Backup and format your sdcard to a single FAT32 partition. Then put the PB99IMG.zip on there only. Does it detect it and ask if you want to flash it?
- The same thing on a different sdcard just to be sure.

eddiehk6 said:
Strange
I don't think I've seen that screen either.
Things to try:
- Flash the alpharev downgrader.img from alpharev.nl, then reboot bootloader. I think it should say Alpharev Unlock at the top of the bootloader screen. Then try running RUU again.
- Backup and format your sdcard to a single FAT32 partition. Then put the PB99IMG.zip on there only. Does it detect it and ask if you want to flash it?
- The same thing on a different sdcard just to be sure.
Click to expand...
Click to collapse
I flashed the downgrader and now i have that when i try to run RUU it's still block after reboot the device
It's like if when i'm in hboot or fastboot, my computer can't communicate whith the device.

Try the PB99IMG.zip method, it removes any possibilty of USB or driver issue. You can run it while not connected to PC at all, just make sure you have enough battery or connect direct to charger (not computer)
When you put the PB99IMG.zip on the sd card, go straight to bootloader (vol down + power). Does it scan for the file? Does it ask if you want to flash?
Have you formatted your sdcard or tried a different sdcard as suggested?

eddiehk6 said:
Try the PB99IMG.zip method, it removes any possibilty of USB or driver issue. You can run it while not connected to PC at all, just make sure you have enough battery or connect direct to charger (not computer)
When you put the PB99IMG.zip on the sd card, go straight to bootloader (vol down + power). Does it scan for the file? Does it ask if you want to flash?
Have you formatted your sdcard or tried a different sdcard as suggested?
Click to expand...
Click to collapse
I can flash no problem for that.
Look pic now it's write Alpharev Unlock in top in place of --Revolutionary--
But even after flash i can't run the RUU.

SiX-P4cK said:
I can flash no problem for that.
Look pic now it's write Alpharev Unlock in top in place of --Revolutionary--
But even after flash i can't run the RUU.
Click to expand...
Click to collapse
Sorry think I may have missed a step
Flash the stock hboot.img, then try again.
Be specific and say exactly what you have tried so far. I've asked several times, and "I can flash no problem for that" doesnt' make sense
- Are you trying to flash the PB99IMG.zip method as in bortak's guide?
- Does the bootloader scan for the PB99IMG.zip at all? You should see green text flash briefly when you boot to bootloader.
- Have you formatted your sdcard to a single FAT32 partition? Have you tried a different sdcard?

eddiehk6 said:
Sorry think I may have missed a step
Flash the stock hboot.img, then try again.
Be specific and say exactly what you have tried so far. I've asked several times, and "I can flash no problem for that" doesnt' make sense
- Are you trying to flash the PB99IMG.zip method as in bortak's guide?
- Does the bootloader scan for the PB99IMG.zip at all? You should see green text flash briefly when you boot to bootloader.
- Have you formatted your sdcard to a single FAT32 partition? Have you tried a different sdcard?
Click to expand...
Click to collapse
I'm sorry i will try to be more precise:
- Yes i try to flash the PB99IMG.zip as in bortak guide (i copy file in root of sd and reboot in fastboot)
- Yes the bootloader scan and ask me if i want flash. Volume up to yes and down for no. After that my HBoot change like show on the pictures
- No I don't format my SD because i don't think i need it to flash RUU.
Thx u for your help.

SiX-P4cK said:
I'm sorry i will try to be more precise:
- Yes i try to flash the PB99IMG.zip as in bortak guide (i copy file in root of sd and reboot in fastboot)
- Yes the bootloader scan and ask me if i want flash. Volume up to yes and down for no. After that my HBoot change like show on the pictures
- No I don't format my SD because i don't think i need it to flash RUU.
Thx u for your help.
Click to expand...
Click to collapse
So good news is at least the bootloader detects the PB99IMG.zip. So you press volume up, and then just says RUU? Very odd.
- Have you also flashed the stock hboot.img from alpharev?
- Please try to backup and format the sdcard to a single FAT32 partition. I know you don't necessarily need to for an RUU, but you should try it as the RUU is running from the sdcard. I have seen it work before as it rules out card corruption.
- If above doesn't work, try PB99IMG.zip on a different formatted sdcard. Again, the RUU is running from the sdcard, so just in case your current sdcard is corrupt in any way even after formatting. I have also seen this work.
Trying to explore all options here...

eddiehk6 said:
So good news is at least the bootloader detects the PB99IMG.zip. So you press volume up, and then just says RUU? Very odd.
- Have you also flashed the stock hboot.img from alpharev?
- Please try to backup and format the sdcard to a single FAT32 partition. I know you don't necessarily need to for an RUU, but you should try it as the RUU is running from the sdcard. I have seen it work before as it rules out card corruption.
- If above doesn't work, try PB99IMG.zip on a different formatted sdcard. Again, the RUU is running from the sdcard, so just in case your current sdcard is corrupt in any way even after formatting. I have also seen this work.
Trying to explore all options here...
Click to expand...
Click to collapse
I press up and it's flash normaly.
The RUU you see in picture is when i try to flash with RUU. Not when i flash with PB99IMG.zip.
I have flash Downgrader from alpharev. Now i will flash stock.

Same probleme with stock HBoot.
I launch RUU, he found my device, ask me a few stuff (agree-next), reboot my device in hboot, wait and never found it.
I think probleme come from my pc. He can't connect with desire when he is in hboot. May be driver issu of stuff like that.
But when the phone run normaly, i can use ADB command line tool.

You are mixing methods which is confusing...
- Do not run the RUU from PC
- Use the PB99IMG.zip method only. Run it when the phone is not connected to anything. This removes all possibility of driver issues.
- Accept the file once found in bootloader (volume up). What happens next, does it actually or try to install? It should give you progress on screen with [OK] or [FAIL] messages at each stage. Can you reboot normally afterwards into the stock ROM?
- The PB99IMG.zip is definitely from the 2.3.3 GB RUU?

eddiehk6 said:
You are mixing methods which is confusing...
- Do not run the RUU from PC
- Use the PB99IMG.zip method only. Run it when the phone is not connected to anything. This removes all possibility of driver issues.
- Accept the file once found in bootloader (volume up). What happens next, does it actually or try to install? It should give you progress on screen with [OK] or [FAIL] messages at each stage. Can you reboot normally afterwards into the stock ROM?
- The PB99IMG.zip is definitely from the 2.3.3 GB RUU?
Click to expand...
Click to collapse
I don't think I mix.
I flash PB99IMG.zip normaly. Phone not connected and it's look like it's work.
When it's finish i reboot my phone normaly
After all that i try to run RUU and it's doesn't work.
I try with PB99IMG.zip from alpharev.nl. Downgrader and stock.

I think i found my mistake...
I only use the PB99IMG.zip file from alpharev.
And i don't extract the rom.zip from RUU.
Work in progress.

SiX-P4cK said:
I don't think I mix.
When it's finish i reboot my phone normaly
After all that i try to run RUU and it's doesn't work.
I try with PB99IMG.zip from alpharev.nl. Downgrader and stock.
Click to expand...
Click to collapse
You're only changing hboots with PB99IMG.zip method.
I want you to extract the ROM.zip from the 2.3.3 GB RUU, and run that as a PB99IMG.zip.
The methods are similar, but they accomplish entirely different things.
- Look at bortak's guide again, step [7]. You said you had looked at the guide....
- Delete all other PB99IMG.zips from your sdcard
- Then put the PB99IMG.zip of the RUU on root of the sdcard (it should be a lot bigger in size)
- Try again

eddiehk6 said:
You're only changing hboots with PB99IMG.zip method.
I want you to extract the ROM.zip from the 2.3.3 GB RUU, and run that as a PB99IMG.zip.
The methods are similar, but they accomplish entirely different things.
- Look at bortak's guide again, step [7]. You said you had looked at the guide....
- Delete all other PB99IMG.zips from your sdcard
- Then put the PB99IMG.zip of the RUU on root of the sdcard (it should be a lot bigger in size)
- Try again
Click to expand...
Click to collapse
Yeah you are right!
I think PB99IMG.zip can only flash hboot and after RUU was suppose work from PC.
But you can too flash the RUU without use the application, just extract rom.zip and flash it.
It's working now.
I'm dumb. Many thx for you help :victory:

Haha no worries. The main thing is you got there in the end :good: