Develop Bugs

Phone screwed ? Can't mount SD / emergency calls only

Ok, where to begin:
I Rooted this weekend and have been installing a few roms, all has been fine. This afternoon I tried to partition a fresh SDcard using the windows-recover.bat method to allow apps2sd and that (I believe) is where it all went wrong.
When I rebooted the phone it went into a boot loop, never getting past the HTC logo.
So I factory reset from the HBOOT menu and it still looped, until I put a new SD card in - then it loads ok (I'm using Defrost 2.41d) but after the initial set up it says emergency calls only - I manually select Orange (the phone is a factory unbranded/unlocked CPW handset) - it says it's not allowed to connect - won't connect using my T-Mobile sim either.
It also says the SDcard isn't mounted no matter what SDcard I try (tried 4x).
I've tried booting into recovery and installing a zip from the SDcard so try and install a new ROM and it fails saying unable to mount SDcard.
I have also done a cache wipe, and basically any other option that sounds like a wipe type option from within the Recovery menu on HBOOT/Clockword MOD.
I'm lost, if I can't access the SDcard in any way then I'm screwed and can't reflash.
Any ideas gratefully received...

have you tried pushing a rom to the phone from your computer? or unrooting with an official HTC RUU ROM and starting again?
also search the "USB bricked" stuff on the desire android development forum...

Thanks for the advice
I'm trying to push a std Official ROM but the PC just doesn't see there is a phone attached when the phone is in normal use mode, it starts to see it in HBOOT mode but then says the driver has failed etc.
Someone elsewhere has mentioned the USB brick possibility but from what little I've read it requies SDcard functionality and my phone just doesn't see ANY SDcard - even in HBOOT / Clockword MOD recovery mode.

any feedback?
could you solve the problem?

[Q] Rooted Desire stuck between ROMs!!! HELP!!!

Hi guys, I've had my Desire rooted for around 2 months and have used loads of
ROMs/Mods etc. It's fair to say I know the procedure. At the moment though I'm
puzzled and worried because I have lost my previous ROM and can't get a new one
on!
I was flashing a new version of Pinky Desire over the previous one (without wiping)
and it never got to the reboot screen. So I took out the battery and put it back in
to reboot it. It got to the custom boot screen and no further so I then booted into
recovery and wiped data and cache and re-flashed the ROM, but the result was
the same...
So I tried this a couple more times until suddenly the recovery-windows.bat file
would no longer put me into a recovery menu. I've tried everything I can think of
(using my original Goldcard etc) but nothing is fixing it- it's like I've lost root access.
How can I make my phone useable again? PLEASE HELP!!!
EDIT: In case it makes a difference I did delete what I thought were some old .zips from my SD shortly before this.

Install an official RUU, then re-root it? I guess some of the pro's got some better answers though

Download the ClockworkMod recovery, rename it in update.zip, put it in the sd, enter recovery, when you get the red triangle press vol up+power, select to flash update.zip.

Yep, flash an ruu, then re-root, only this time use unrEVOked and for future when flashing roms use the newer recoveries like clockworkmod or amonra.
The old recoverywindows.bat file leaves you at risk of the usb brick. You may well already have that now if you pulled the battery mid flash.

Thanks all. Haven't had a chance to do this yet but will. I did manage to flash an update.zip but it won't detect the sd. will try with clockwork mod.

DomFel said:
Download the ClockworkMod recovery, rename it in update.zip, put it in the sd, enter recovery, when you get the red triangle press vol up+power, select to flash update.zip.
Click to expand...
Click to collapse
Tried this but all I'm getting is cannot find directory. It retries about 12 times then
reboots. Just won't work.

When trying to flash an RUU it comes up with 'Error 170: USB connection error'.
This is weird because the device's bootloader recognises that there's a usb
connection. Any ideas?
EDIT: Seems like the phone in it's current state simply can't mount an sd card.
Gotta try some alternative methods for getting the RUU to run...

Doogleman said:
When trying to flash an RUU it comes up with 'Error 170: USB connection error'.
This is weird because the device's bootloader recognises that there's a usb
connection. Any ideas?
EDIT: Seems like the phone in it's current state simply can't mount an sd card.
Gotta try some alternative methods for getting the RUU to run...
Click to expand...
Click to collapse
Check out the USB brick thread.

prove said:
Check out the USB brick thread.
Click to expand...
Click to collapse
I will. That's so sh*t though
Thanks guys

Had almost same problem.
I even couldn't flash update.zip
the problem was in SD. it was working OK in windows, but phone couldn't mount it. soved problem with reformating using SDFormater, when formated with clockworkmod.

mendozinas said:
Had almost same problem.
I even couldn't flash update.zip
the problem was in SD. it was working OK in windows, but phone couldn't mount it. soved problem with reformating using SDFormater, when formated with clockworkmod.
Click to expand...
Click to collapse
I've two SDs and neither is working though so...

two things
the windows unlockerthing.bat was only supposed to be run one time, after that you could access the menu pressing vol up and power...
Why would you pull the batt on a Flash??

Pulled the battery because the device said flash completed but didn't do anything for over 5 mins. Won't make that mistake again. I've actually bricked the USB so this thread is a little pointless now
Oh and I did fix the SD issue

[Q] Help with SD problems

So Ive been having problems with my SD card as posted here http://forum.xda-developers.com/showpost.php?p=16689682&postcount=286, and my question is, can someone explain to me how to flash back to stock without the use of my SD card ? Or am I screwed ? Thanks.

What you can do is download the RUU exe for the hboot you are on, if 2.10, its the 3.70, if 3.16, its 4.24 [the new ota], then connect the phone to the pc via usb, boot into the bootloader, select fastboot, then run the exe on the pc.

Thanks for the reply, and sorry for the noob question but how do you determine what hboot you are on ? Cause if I boot to the white Revolutionary screen (volume down + power) the third line down says "HBOOT-6.16.1002", is this right ?
----------
*EDIT*
Also dont know if this will help but when I am in recovery, if I try to mount my SD card it says "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (I/O error)"

Well I don't know if it was changed, but since you were on 2.3.3, you had to be on the 2.16, so for ruu purposes, look for that.

Alright, got stock back on. Thanks a lot.
I didn't know which one to use so I decided that since I have only had my evo for less than a month then I would use the latest version and it seems to have worked. So again, thanks a lot.

Okay, so I guess that I have a hardware problem and I will have to have it replaced. While my phone was just sitting there a notification came up that said "SD card unexpectedly removed"
Do I have to change the phone back to S-On before I get it replaced or can I keep it S-Off ?

Glad that you got it working, and you need to be s-on.
If you're s-off, re-root, then download the unrevoked s-on tool, flash the zip in recovery, make sure the bootloader reads s-on, the unroot again.

okay, so when I try to use the unrevoked s-on tool it fails and says unsupported radio type. any fix for this ?

BioBot said:
okay, so when I try to use the unrevoked s-on tool it fails and says unsupported radio type. any fix for this ?
Click to expand...
Click to collapse
try the 3.70 radio

You need to go to the development thread, then download the 2.1...11.19 radio and flash that.

Thanks for all the help guys. I've ran into another problem now. Before this new problem, if I wanted to put a new file on my SD card I had to flash to stock which gave me a 30-45 second window to mount the card to my pc and copy any files I needed to and power off before it unmounted it. Then I had to reboot, run revolutionary and get a recovery before it unmounted. Then I could flash a zip from my SD. BUT NOW, even if I reflash stock, it auto unmounts the SD at bootup.
Frustrated but still trying to problem solve.... Will update if anything changes.

Okay. I think I got it fixed now. After spending all day trying and flashing my phone at least 12-15 times it seems to be doing okay.
Solution : New SD card
Thanks for your help everyone !

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.

[Q] MIUI Rom gone wrong

okay so heres what happened.
I have an international htc one x that is indeed rooted with no roms installed.
I did create a back up and then tried to install the MIUI rom (but I dont really know where that is on my phone. I know I made one with rom manager. I dont have any backups on my computer though)
It worked, however, it didnt have wifi or data signals so i went back to try again.
I opened my bootloader screen. For the record, it is unlocked and hboot is version 1.73 if that helps.
I wiped cashe/data/delvic everything and even factory reset and installed the MIUI RD rom now hoping it would have a difference.
The darn thing got stuck on the MIUI bootloader for hours.
I did the same thing again a few times, sometimes in different orders and then it passed on and another screen came saying 'starting apps'. That got stuck for hours too.
Now I don't have any other roms on my phone, just the MIUI RD. The original miui just vanished too, i dont see it anymore. Also, when I put my USB wire to the phone and connect it to the pc, I cant transfer newer files into it. So this is all I have access to on my phone apparently.
I tried flashing a boot.img and a couple kernels but no luck. I've been trying to do this for all day and this is my first time so I don't know much about it.
I've been googling and somethings say to open cmd and type but i keep getting 'fastboot is not recognized as an internal or external command'
Currently, its not stuck at either the MIUI screen or the Starting Apps. but just the HTC logo screen and not going past.
I don't really want to install any new roms considering i've worked really hard to get this to work and I really want it now more so.
How do i fix this? I want to use this rom.

flash philz recovery (http://forum.xda-developers.com/showthread.php?t=2240646), usb mounting should work on that, then:
steps to install ROM
1. bootloader version should be 1.3x
2. copy ROM to SD Card
3. copy boot.img INCLUDED in the ROM zip to fastboot folder
4. flash the boot.img in fastboot
5. in recovery, wipe system/data/cache/everything
6. flash rom
7. restart

but how exactly do i put it on my phone? my computer isnt detecting my phone when i connect it? im sorry im not exactly an expert on this.

Go to recovery - mounts and storage - hook up the usb cable - tap the last option in the mounts and storage list and wait a few minutes. It won't be mounted instantly

ok i flashed the philtz recovery but when i flash the boot.img it says:
Finding update package
Opening update package
Installing update
installation aborted
for reference: http://forum.xda-developers.com/showthread.php?t=1957490
thats the rom i used and i flashed the boot.img flasher thats right above the download link
edit: also i tried just flashing the rom again and im still stuck on the HTC screen.
its not even going to the miui screen or starting apps anymore. :[

Boot.img must be flashed via fastboot. Not via recovery !

ok, i looked up how to fastboot, downloaded sdk files and i moved the boot.img into the fastboot folder and i opened command prompt there and wrote fastboot flash boot boot.img but i keep getting:
'fastboot is not recognized as an internal or external command'
what did i miss?
EDIT: ok, so the fastboot folder i got from the page didnt work so i used a different fastboot folder, dragged the .boot there and now it worked! finally passed the screen and wifi is connecting!
thank you!

Good, thanks to @tomascus. He summed it up real nice
Cheers