Related
So today, I was upgrading from modaco 2.7 to 2.7.1,
after the upgrade (using recover mode and the signed zip file (core chinese)), I did a system wipe and reboot the device with the USB still plugged in my PC, and everything seems to be normal until my pc's tray notification pops up with the "unknown device found" message - i thought it was a little bit odd, so then I waited for the hero to boot up completely - it reboots after showing the HTC logo once, and then it boots normally to the setup wizard (select language, etc);
I then followed the normal procedure of typing all the wifi, flickr, gmail stuff in, and when i got into Rosie, it shows a notification icon on the hero saying "SD Card removed". I can't access the SD card, nor my pc can recognize the hero. I ejected the SDCard and re-insert it but it's not detected either. HTC Sync on the device does not give a notification nor the mass storage notification shows up either.
I tried rebooting into recovery mode, (Hero 1.2.3) and i can see the menus just fine; however, when i try to mount SD card as usb, or flash update.zip or any zip, or fix ext3, or clear dalvik-cache or wipe the sdcard's ext partition, it keeps giving me errors saying
error: run 'whateverprogram' in terminal
when i try to set 'USB Mass storage on', it says "Error enabling USB mass storage! Run ums_enable manually from console.
I then try to login the device using adb shell through window's command prompt, it says device not found as well.
giving up, i tried to reboot teh device into fastboot mode, the PC recognizes the USB device just fine. it's really odd.
Anyway I can do a recovery on this to make these device work again?
p.s. when i try to choose zip file in recovery mode, it says
Code:
"E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
Can't mount sdcard, aborting".
after every reboot (shutdown, start), the setup wizard shows up again as if I have not written anything on my device after any setup.
I can't download anything to run on the Hero as it requires the SD card. I can't flash any recovery images either as again it requires the SD card.
Any ideas??? I'm left with a half-brick now
Update1: using ConnectBot I can login my own device using root,
it shows the following when i run df -h:
Code:
/dev/block/mtdblock3 1700M 157.3M 12.7M 93% /system
/dev/block/mtdblock5 165.8MB 12.8M 152.9M 8% /data
/dev/block/mtdblock4 130.0M 1.2M 128.8M 1% /cache
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Al936 said:
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Click to expand...
Click to collapse
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
kazuni said:
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
Click to expand...
Click to collapse
Update2: the only way that my pc can detect my device as "My HTC" is when i boot it into fastboot mode; unfortuantely there are no way for me to update the device in this mode, so i can't do anything to modify the rom, or to check it using dropbear or any shell client. =\
C:\Documents and Settings\user>fastboot devices
HT97RL900725 fastboot
it sees it just fine.
I wonder if the goldcard method + fastboot update will work or not; let me give it a shot and try to flash it back to 405.5 first ;\
update3: can't. fastboot update is still locked for any rom type.
damn man. its freaking. i am not going to update to 2.7.1 untill this issue is resolved.
still no go.
im left with a half-bricked device that:
1) clean wiped, normal boot, cannot detect SD card nor the Hero is detectable by XP.
2) clean wiped, recovery mode, can't run any of the script except :
Reboot System Now
Wipe data/factory reset
Fix apk uid mismatches
Fix rotate
3) can't download anythign from browser as it needs to save onto sd card.
4) android market doesn't have flashrec so i can't reinstall the recovery image.
wget ftp://myhost/system.img /data/
flash_image system /data/system.img
hope this works
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
packetlss said:
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
Click to expand...
Click to collapse
can't. It doesn't even boot into normal mode, nor boot loop. it just holds at the HERO logo.
I think I have the same problem, i can charge my phone but trying to mount my phone to either my pc or mac it just won't be picked up
tried using RUU with a goldcard, no go. remote not allowed (fastboot flash system system_rel.img, nor fastboot boot boot.img or fastboot flash boot boot.img. no go. sigh.)
now i have a brick :\
wonder if there is any way to go into fastboot mode and flash ANY part of the blocks (device, recovery, or system, if at all).
Some progress: using hboot mode, i placed HEROIMG.zip into the sdcard and it loads successfully. it works! and im now rolled back to official 2.7.405.5; however, the USB and the sd card is still dead ;\
I guess I'll be bringing it back to HTC to see if they would do anything about it (fortunately It's now back to stock recovery and 2.74.405.5)
I managed to do the same thing, i'm hoping the tmobile will replace my phone
hi all,
I am having the same issue... what I don't understand is: it has to be a software problem, because, from what I've read, everyone of us have been installing radio and firmware updates to the htc hero, and since some of these updates the USB and sdcard mounting is not properly working... I believe it's not possible to break a USB port just by installing software...
so there should be a way to fix this other than sending the phones back... If anyone has any suggestion I can try it on my phone
cheers : )
I know it's weird! Funny thing is, official updates includes radio + recovery + pretty much every part of the rom is being re-flashed (including hboot, from what i understand); how ever, ONLY in hboot mode, the device is recognized properly as "Android USB" by windows.
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
dennis333 said:
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
Click to expand...
Click to collapse
I tried this but it didn't seem to work for me, so I just put the official rom update and sent the phone back to my network saying that it was broken, now i've gotta wait for another 2-3 weeks to get my phone back , but i'm hoping they'll give me a new phone as i did kinda drop it and there two scuff marks on it
hello dennis333,
today I tried going from 2.8 to the HTC generic ROM you told, and then to 2.5. no results.
I also installed the official HTC / Orange Rom update, which I have now. It has improved a bit because now when I plug the USB cable the PC detects something, but it does'nt work... it says 'unknown device' (tried this on two computers)
when I boot to fastboot ( BACK + POWER BTN ) my computer detects Hero ok (My Htc)
I really don't know what else to try...
I saw another post from someone who had the exact same problem and got it fixed by installing SPL and ROM from fastboot menu
http://forum.xda-developers.com/showthread.php?t=556038
I tried it too, but when trying to use the SPL zip file he says I get an error ( I guess it's because he has a T-Mobile and I have an Orange Hero)
[update]: I finally got the SPL to flash correctly and then installed a modaco 2.8 ROM, but I still cannot connect the Htc Hero to the PC via USB.
regards
Hi guys, i am a newbie here.
Last night i was trying to root my desire using unrevoked. I followed the guide from XDA step by step and everything seemed fine until word "done" appear in unrevoked.
After that, desire supposed to enter recovery mode and clockworkdmod but there was nothing appear in the screen. My desire suddenly shut down.
Can you tell me what am i suppose to do then because i want to put custom rom in my desire and now there's nothing i can do because it can't enter recovery mode (it only able to enter bootloader or Android OS itself).
Thanks
kyosiro said:
Hi guys, i am a newbie here.
Last night i was trying to root my desire using unrevoked. I followed the guide from XDA step by step and everything seemed fine until word "done" appear in unrevoked.
After that, desire supposed to enter recovery mode and clockworkdmod but there was nothing appear in the screen. My desire suddenly shut down.
Can you tell me what am i suppose to do then because i want to put custom rom in my desire and now there's nothing i can do because it can't enter recovery mode (it only able to enter bootloader or Android OS itself).
Thanks
Click to expand...
Click to collapse
when you are in boot loader, use the volume down key and goto recovery and git power button. you should then be taken to clockwork recovery. this is where you can select your rom from SD card and flash
I've tried to do that and now it stuck in HTC Logo. Doest it mean i've to try unrevoked again or simply unroot it?
try rebooting by taking battery off. i'm not an expert but you might have to do it manually using the guide http://forum.xda-developers.com/showthread.php?t=696189
did you install the unrevoked drivers?
Okay i will try. Btw, in case i want to unroot, can you tell me where i can get "RUU_Bravo_hTC_Asia_WWE_1.19.707.7_Radio_32.36.00.2 8U_4.06.00.02_2_release_126179" ? The link from XDA seems down and i can download any.
Me and another member have encountered the same issue, seems there's some bug in HBOOT or something.
Boot into Android, go to Settings > Privacy > Factory data reset. Once you confirm it, it will reboot your phone into Recovery.
BUT, unless you re-format (partition) your SD Card, you won't be able to get back in again (unless you do the Factory data reset again).
This seems to happen randomly. Right now I can get into Recovery just fine. But once the bug occurs, the only way to get it to stop is to format your SD card.
Now i am thinking to unroot it than trying to do the whole rooting step all over again. Can you tell me where i can get the RUU for HTC Desire Asia
kyosiro said:
Now i am thinking to unroot it than trying to do the whole rooting step all over again. Can you tell me where i can get the RUU for HTC Desire Asia
Click to expand...
Click to collapse
Here you go:
http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126179_signed.exe
Okay, i've done unrooting with HTC Desire RUU Asi and what happen now my SLCD is brick. I am really hopeless right now because guide for "SLCD Brick" doesn't even work in my phone because once again my htc can't enter recovery mode ><
"I am trying to use the guide from sprinker right now. Hopefully it will work"
when you are in hboot the volume down/up button work?
Hi all,
I also have the problem that I can no longer enter the recovery mode on my desire.
Basically, whenever I am in the bootloader menu (either by pressing vol-down+power, return+power, or via ROMManager) and then select "recovery" I get right back to the "fastboot" screen.
I tried uninstalling/installing/upgrading ROMManager and also tried flashing clockwork via the newest version of Unrevoked (downloaded yesterday).
Nothing helps :-(
What I didn't try, yet, is reformatting my SDCard or resetting my device via "Settings > Privacy > Factory data reset". (I don't want to install all my apps >again<; I'm also a bit afraid that I break something an then cannot even reflash using recovery).
Here is some more info about my device:
- Flashed rom: Leedroid 2.1a
- HBOOT 0.83.0001
- RADIO 5.10.05.23
I would be really greatful if anyone had a solution for this problem.
P.s.: in case I HAVE to reset/format: can I somehow make a backup of all my apps&settings?
Hi all, I have the same problem now.
Everything works, after s-off, except I can no longer enter Recovery - any solution?
I didn't find an easy solution. I had to do the following (some steps might be optional but I wanted to be sure):
- Formated SD card (ext3 and fat partition)
- Complete reset via RUU (RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe)
- Using unrevoked to reinstall recovery rom
- Reinstalled my custom rom (Leedroid)
Now everything works.
BTW: via TitaniumBackup I could backup all my apps and data quite easily. Didn't expect it to work that well
thanks- what about s-off - is it working now for you?
"s-off" = ?
I Have a similar problem... I can't enter recovery. When i press "recovery mode", I just get a black screen with a phone and a "!" in it.
Have to pull battery to reboot desire.
I have formatted sd.
Quite annoying, cause I need to wipe my battery stats, and I don't know any other way to do it, than going to recovery.
I tried to update ROM to Cyanogenrom which was unsuccessful - just get boot loop.
I also get the same 'red triangle with exclamation mark on phone' icon when trying to go to recovery mode.
So now I have a Desire which boot loops and cant enter recovery mode ...
anyone know how to get out of this one?
This might work for you
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck
This should bring back your phone to stock. Root your phone again after it is done
i have the same issue. but i got stuck when trying to partition my sd card. Now i can't enter Android itself only the bootloader. But i also lost my clockwork recovery...
it keeps looping the HTC Quitly brilliant bootscreen... Forever!
i am now formatting my sd card with my pc. will i then be able to go into recovery again using a zip file from clockwork i found? using this:
fake-flash
Fake-flash is only possible with root access, you need to be rooted to use it. Basically, its a way to have recovery running on the phone without using a PC (making it safer as you are less likely to brick using no USB cable to push files, instead, you push directly from your phone). You can use "ROM Manager" from the marketplace to do this. Simply place the downloaded test recovery image on the phone and the downloaded rom zip (renamed to update.zip) and flash using ROM Manager.
Preperation
Download the fake-flash update zip from one of the links below
Copy the update.zip to the root of your SD card (the name MUST remain as update.zip)
When you want to launch the recovery image
Turn on your device with 'volume down' pressed and select 'Recovery'
When the exclamation mark appears, press and hold 'volume up' then press 'power'
Select the second option, 'Apply sdcard:update.zip
That's it, ClockworkMod recovery should launch!
Click to expand...
Click to collapse
and then installing a ROM with it?
(sry for bad english)
i'm having the exact same problem. i've tried fake flash and it does nothing for me, so does flashing the clockwork recovery image. the only one i haven't used yet is the downgrade...hope that will help
Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work
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.
Hello,
I have done days worth of research in my spare time, before finally caving in and asking for help. I'm still kinda new to the custom rom scene, and somewhere I must've messed up.
I was updating my ViperX rom to a newer version, but got an error code during the install, which rendered the OS useless. So decided to wipe and reinstall the older version again, which failed. So I tried to install CM 11, which also failed... Somewhere a long the line my SD Card stopped being detected by the phone AND my PC. So now I don't know how to get an OS on it.
Here's some info I might need to share.:
**** UNLOCKED ***
ENDEAVOUR PVT / S-ON
HBOOT - 1.39.0000
(Bought in Sweden, before moving to the UK)
I have access to bootloader
I have access to recovery which is CWM 6.0.4.8.
My SD card WONT MOUNT (I think), so I don't think I could do "side loading", since it's not recognized in ADB . If I reboot the system, it bootloops at the CM update logo forever. I've tried reinstalling it several times, but it only installs for a few seconds, then restarts. (I'm guessing it's corrupt?)
(Edit: Earlier today it ran out of battery, and despite charging it for hours, it's not turning on and the little LED on the top is blinking RED... What's that all about?)
Is there ANYTHING I've missed, or can do to fix this? I don't care what kind of ROM I have to use at this point, I just want a WORKING phone.
Cheers // Vic
Vicarate said:
Hello,
I have done days worth of research in my spare time, before finally caving in and asking for help. I'm still kinda new to the custom rom scene, and somewhere I must've messed up.
I was updating my ViperX rom to a newer version, but got an error code during the install, which rendered the OS useless. So decided to wipe and reinstall the older version again, which failed. So I tried to install CM 11, which also failed... Somewhere a long the line my SD Card stopped being detected by the phone AND my PC. So now I don't know how to get an OS on it.
Here's some info I might need to share.:
**** UNLOCKED ***
ENDEAVOUR PVT / S-ON
HBOOT - 1.39.0000
(Bought in Sweden, before moving to the UK)
I have access to bootloader
I have access to recovery which is CWM 6.0.4.8.
My SD card WONT MOUNT (I think), so I don't think I could do "side loading", since it's not recognized in ADB . If I reboot the system, it bootloops at the CM update logo forever. I've tried reinstalling it several times, but it only installs for a few seconds, then restarts. (I'm guessing it's corrupt?)
(Edit: Earlier today it ran out of battery, and despite charging it for hours, it's not turning on and the little LED on the top is blinking RED... What's that all about?)
Is there ANYTHING I've missed, or can do to fix this? I don't care what kind of ROM I have to use at this point, I just want a WORKING phone.
Cheers // Vic
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery and you have working sd card mount there copy what you want to your sd card and if you want to install kitkat rom flash lates CWM or TWRP or Philz and inatall it
Thant said:
Flash Philz 5.15.9 recovery and you have working sd card mount there copy what you want to your sd card and if you want to install kitkat rom flash lates CWM or TWRP or Philz and inatall it
Click to expand...
Click to collapse
You must've missed the part where I said neither my Phone nor my PC can detect the SD card, so can't put anything on it. :/
Vicarate said:
You must've missed the part where I said neither my Phone nor my PC can detect the SD card, so can't put anything on it. :/
Click to expand...
Click to collapse
NO I not missed nothing you don't listen me. flash Philz 5.15.9 recovery after this go in recovery connect the phone to computer and choice mount sd card after 1-2 min you will see your sd card and if you think not do this I will stop help you. It is your choice to flash revovery you dont need sd card only fastboot commands, use exactly the same recovery where I write you not newer not older have shears from me on googledrive use search function and download it take the recovery.img from zip archive then place in your fastboot folder the connect the phone in fastboot and run the command fastboot flash recovery recovery.img. Simple thing to do