Related
I'm stuck at a nearly 99% brick I think...
I've got an AMOLED Desire from T-Mobile Germany (still branded), with HBOOT 0.80.0000, rooted via Unrevoked and still S-ON.
The phone gets stuck during the boot process when the provider-splashscreen (or HTC-Logo) is shown at the beginning. Only pulling out the battery will shut the phone down.
The same happens when I try to get into Recovery via HBOOT. The only option is to pull the battery.
If I connect the phone via USB and enter Fastboot it is recognized by the computer with the command "fastboot devices".
I can't use ADB, because I can't access the recovery.
I downloaded the right RUU for my provider/amoled/hboot 0.80.0000 Desire (RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed) and extracted the ROM.zip from the installer. I renamed the file to PB99IMG.zip and manually moved it to the SDcard using my computer.
But, when I enter HBOOT the file is recognized and extracted, but then it fails ...due to an "incorrect CID".
The same happens if I manually execute the RUU....exe under Windows with my phone plugged in via USB. (It's error code 131 in the flash program of the RUU....exe).
A very helpful user (cargo) of a german Android forum (www.android-hilfe.de - link to his posting) assumed that my HBOOT is not correctly displayed and I might have a "newer" one than 0.80.0000
This leaves me quite without any option than to flash HTC RUU 2.29.405.5, which brings HBOOT 0.93.0001...(but I may be able to downgrade again.)
But this flash process is only possible if I have a Goldcard, which I actually don't have at the moment
Is there any way to create a Goldcard for my device in my actual position (only fastboot working, no boot to run the system, no adb working, no recovery access)?
Every howto explaining the goldcard crating process requires either working adb or even a running system for apps like "goldcard helper" or being able to use "terminal emulator"
I would be very very thankful for every bit of help
Maybe there is some way
Thanks in advance guys!
I believe that goldcards are specific to the card and not the phone(read it somewere on here) so it should be possible to make one without using your phone.
Sent from my HTC Desire using XDA App
TheGhost1233 said:
I believe that goldcards are specific to the card and not the phone(read it somewere on here) so it should be possible to make one without using your phone.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
As far as I know you need the phone for your goldcard. At least it was said in the tutorial I was following a few months back. You need to connect the phone to get the serial number (through ADB shell) which you will need to hex-reverse and put it on your SD card image.
To be honest, they are more sophisticated methods now (as I read) creating a goldcard, but since unrEVOked, i do not follow that part.
And by the way, why don't you flash the HTC RUU 2.29.405.5? 0.93 HBOOT can be downgraded. But with the latest tools you can S-Off, root & whatever with that HBOOT, too.
I just tried flashing the HTC RUU 2.29.405.5 with the PB99IMG-method.
But I get an error "CID incorrect"
I treid to execute the HTC RUU.exe and I get again error code 131...which means something like "user-ID error"
But I could grab a screenshot of the actual "version" of the RUU...or what is this?
Thanks guys
CID incorrect? Your phone is unbranded or branded? Because I found this:
ERROR [294] : INVALID VENDOR ID
Every device contains a short string that identifies the operator who sold it. Because the same device is sold by different operators, this prevents users from flashing a T-Mobile ROM to a device that was sold by Orange, for example. You probably need to Install a HardSPL or CID Unlock your device.
Click to expand...
Click to collapse
I recommend to find a RUU for your device (e.g Vodafone, T-mobile etc.)
Also:
ERROR [131]: CUSTOMER ID ERROR
One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.
Click to expand...
Click to collapse
If it's saying wrong CID then it's branded, simple as that
1. Boot your phone in fastboot
2. Run the ruu that matches your phone.
You need a T-mobile branded ruu.
You can look here for one that matches. http://shipped-roms.com/index.php?category=android&model=Bravo
I think you can try an UK one, because it is multilingual.
If it is giving you the same errors, then you picked a wrong version.
EddyOS said:
If it's saying wrong CID then it's branded, simple as that
Click to expand...
Click to collapse
well it said "incorrect cid" even with a t-mobile branded ruu :/
If you are rooted, then boot into the bootloader and flash a custom rom. Then create a gold card.
Lennyz1988 said:
If you are rooted, then boot into the bootloader and flash a custom rom. Then create a gold card.
Click to expand...
Click to collapse
Yes, try that too, if you can.
Also use a NOA2SD Rom if you dont have ext partition. Or create one on your PC (if you want to use an A2SD ROM).
How can I flash a Rom using the bootloader?
Simply rename the zipped Image of a custom Rom into "PB99IMG.zip", put in on the SDcard and boot into HBOOT?
Thank you
spaboleo said:
How can I flash a Rom using the bootloader?
Simply rename the zipped Image of a custom Rom into "PB99IMG.zip", put in on the SDcard and boot into HBOOT?
Thank you
Click to expand...
Click to collapse
Yes, if you rooted with unrEVOked. Boot in to recovery (clockworkMOD/AmonRa) wipe all data and flash a CUSTOM rom.
You don't have to rename it, it can be anything as soon as it is .zip
nagypapi said:
Yes, if you rooted with unrEVOked. Boot in to recovery (clockworkMOD/AmonRa) wipe all data and flash a CUSTOM rom.
You don't have to rename it, it can be anything as soon as it is .zip
Click to expand...
Click to collapse
Uhm...flashing a custom rom in general is no problem...but i can't access Recvoery
as described in the initial post of the thread only the bootloader (HBOOT) and fastboot are working.
spaboleo said:
Uhm...flashing a custom rom in general is no problem...but i can't access Recvoery
as described in the initial post of the thread only the bootloader (HBOOT) and fastboot are working.
Click to expand...
Click to collapse
Yeah, sorry, my bad.
Well you can try to falsh it via PB99IMG.zip, but i won't think it work.
your only hope is finding a working RUU. (at least seems to me, if you can access only fastboot).
Hi all, have same trouble with flashing via PB99IMG, but in my case, the device normally loads the firmware and returned to fastbut. When you try to go to recovery device hangs on the logo. Фfter removing the battery and re-attempt to restart the device, it begins to vibrate 7 times and then freezes on the logo. What do these vibration?
PB99IMG.zip will work as you don't need recovery. Just put it on the root of your SD card and boot into HBOOT. It'll find the file and flash it
did renaming rom to pb99img nd flash via hboot work for you?
i have a similar problem, rather same prob, only fastboot available
To let this thread maintain usefullness for future readers:
The solution was to take a goldcard from a friend and flash the right (matching hboot, provider and version) RUU, by using the PB99IMG method.
By this the phone will be set back to it's delivery state! This will include the Rom, all data in the NAND storage the recovery and everything else, which got modified like getting root access or S-OFF etc.
Troubles were caused by USB-Brick or an error on my old ext3 partition or maybe even corrupt data in my Titanium file-backup I restored a few days before the crash :/
I can't clearly say what is the main cause...maybe it was a combination of all.
If you don't have got any chance of getting another goldcard (yes the goldcard creation does NOT depend on the devices! It can be created with ANY android phone ) you are really screwed.
My advice: Always keep a spare microSD card, equipped with it's goldcard image around!
Because I was not able to find any method to echo the CID (Id of the SDcard) in fastboot.
Greetings
And good luck to all of you having comparable issues
Hi,
In an attempt to downgrade from HBOOT 1.03 to Alpharev I followed the tutorial in this forum titled "[S-ON][TUTORIAL] Downgrade from a ROM Hboot 1.03 to a ROM Hboot 0.9". Problem is, when I tried to flash misc, I was not using a gold card and pretty much corrupted the partition. After that my phone is now pretty much useless. No calls can be made, does not pick up my carrier, can't mount SD card. trying to install stock RUU crashes both my PHONE and my COMPUTER.
Things I've tried:
Use stock RUU to flash again ( Crashes computer and phone )
Use fastboot to flash stock ROM.ZIP in RUU ( Says RUU is corrupt )
Use PB99IMG.zip on card, reboot, nothing happens ( says image is corrupt or not found ).
Try restore from nandroid ( can't mount sdcard )
I have the original misc partition on my computer, so if i find a way to restore it I can flash it back.
Anyone have any ideas on how I can fix this? Apart form a walk down to a Telstra dealer and coming back with a new phone?
Thanks =]
link of the forum?
1.03 is htc unlocked you can't downgrade
Tayone said:
Hi,
In an attempt to downgrade from HBOOT 1.03 to Alpharev I followed the tutorial in this forum titled "[S-ON][TUTORIAL] Downgrade from a ROM Hboot 1.03 to a ROM Hboot 0.9". Problem is, when I tried to flash misc, I was not using a gold card and pretty much corrupted the partition. After that my phone is now pretty much useless. No calls can be made, does not pick up my carrier, can't mount SD card. trying to install stock RUU crashes both my PHONE and my COMPUTER.
Things I've tried:
Use stock RUU to flash again ( Crashes computer and phone )
Use fastboot to flash stock ROM.ZIP in RUU ( Says RUU is corrupt )
Use PB99IMG.zip on card, reboot, nothing happens ( says image is corrupt or not found ).
Try restore from nandroid ( can't mount sdcard )
I have the original misc partition on my computer, so if i find a way to restore it I can flash it back.
Anyone have any ideas on how I can fix this? Apart form a walk down to a Telstra dealer and coming back with a new phone?
Thanks =]
Click to expand...
Click to collapse
Sorry, it's unlockable...
I think you got in usb-brick situation.
I'm not sure if you can flash misc with S-ON define?
try "fastboot flash misc mtd0.img" (you can use your misc or donwload from web (keyword: Quick & dirty HTC Desire mtd0.img generator for usb-bricked devices by stevebrush))
What was the file that you named PB99IMG.zip originally? Was it an HBoot .img, ROM...??
Had a USB Brick a week or so ago, when going CM7 > DG > CM7r2...except in haste, I forgot to flash the r2 after DG and tried to flash ROM. OOOPS!!! lol. When I loaded CM7r2.img and renamed PB99..., I must have loaded the wrong file and got the same response you did. Tried again, got it right this time and phone updated and rebooted, all good.
Sorry, I don't recall exactly what I did to cause the corrupt image, but I know that perserverance fixed it...
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
nodnarb said:
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
Click to expand...
Click to collapse
Try this, reformat your sdcard fat32 with a pc. Then place only this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on the sd in no folders (Do not rename). Boot to hboot (vol down + power), it should find the file and prompt you to press vol up to install. I think your issue with the ruu before was that you were trying to flash an older version than you already have installed. If that dosent work try fastboot flashing cwm again, and see if it can mount the sd then.
Thread moved. Please post all questions here in the correct section of the forum.
Thanks
AvRS
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
shivaagarwal1 said:
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
You'll probably get better help in the Incredible S section. This is for just the plain olé Incredible.
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.
htc desire a8181
frig trying to identify no sound through earphone speaker is getting weird
With trying a few different roms, I've also tried flashing a few hboots from the desire custom hboot thread:
Apparently Since flashing the 220/16/200 one I cant flash hboots anymore and recovery keeps (4ext) keeps getting probs with screen distortions etc.
Hboot reports 145 system and massive cache (120 from memory)
When I try to flash replacement standard hboot size via fastboot get a failed message and on phone says 'only blackrose can be flashed'
Not aware of installing 'blackrose' although I've seen the nexus threads with similar problems, and I've never owned a nexus or flashed one.
Managed to get one nandroid to recover with cooldroid v3 on, but 4ext still reports weird partition sizes which cooldroid shouldnt run in.
WTF?
Help
OK tried to replace 4ext with twrp - image update error
Tried to nandroid recovery old backup 'failed to unmount system
Tried PB99IMG - failed
going from bad to worse.
tried
Looking for advice before attempt flash different recovery eg CWM as 4ext is at least still partially working
Clear now
after blackrose trahed it
The rogue 4ext boogered it further
Even got to the stage where it was saying no sd card, despite recognising it at boot.
Cleared data from hboot, after installing MW and it booted.
Ran 4ext updater and it cleared the boot issues
Now back on a relatively normal rooted and unlocked a8181
- ear speaker issues are a failed speaker - may try taking it apart and cleaning contacts, but just bought a cheap replacement and all now working apart from ear speaker.
Might even explore blackrose on this one now I know how to undo.
How to fix when blackrose hboot has been installed
Nexus blackrose (BlackRose_IS_130203.zip) (PC end) will run with the phone installed blackrose
Connect phone up to PC with OS started
Run Nexus Blackrose on PC with command (like fastboot commands)
'Blackrose skip'
You should get blackrose menu on PC
On PC Select option from menu to disable hboot protection and confirm
PC should get confirmation message protection removed until next reboot and the phone should reboot into fastboot
Flash bravo_alphaspl.img hboot.
Restart and check/reinstall if necessary your phones recovery (4ext or whatever)
(dont forget you cant flash ruu's with either blackrose or alpharev hboot protections)