[Q] Failed root, usb/sdcard unrecognized on phone - EVO 4G Q&A, Help & Troubleshooting

Ok, I was running a stock (rooted) 2.1 rom on my Evo until someone using my phone updated me to 2.2 via an OTA update. I didn't really mind, just meant a re-root and a data wipe. Or so I thought.
Everything was going swimmingly until I came to the recovery flash portion of the root (unrevoked reflash). It recognized my phone, proceeded to flash it, but it failed about 3/4 of the way through. Again, I thought no problem I'd just boot into recovery and start over. When I try and boot into recovery, I get the exclamation point error and try to update by holding volume up and pressing power, but the recovery can't mount my sdcard. Well, now recovery is out of the question and I can't use adb to remote into it; phone doesn't recognize my sdcard or any usb connection (even to charge, unless I take the battery out and plug it in after I re-seat the battery). Computer recognizes the card just fine from a card reader, loaded up things onto it with no problem.
How the am I supposed to fix this? Phone boots into stock 2.1 (unrooted), but I can't adb in, load an image off my sdcard (bootloader recognizes the card, but won't let me flash from the pc36img present on the card), or use recovery to load my backup.
I'm screwed, aren't I? If so, think Sprint will replace it if I act like the OTA update trashed it?

Related

Unrooting from SD card

Hey everyone! So the USB port on my friend's evo stopped working and wont charge, plug into a PC, etc. She is returning the phone tomorrow so i told her she should come over and we could Unroot it. Of course i didn't even think about the USB not working. So once she got here I downloaded the stock RUU and extracted the rom.zip image from it. I read somewhere that this would work if you had to Unroot from an SD card.
I renamed rom.zip to PC36IMG.zip and loaded it onto her SD card and booted into recovery. The first time it seemed to work like a charm but then it rebooted...and it started boot looping. So now when I reboot into HBOOT and it tries to load PC36IMG.zip it says "main version is older" and just fails to flash. After that I booted into the Clockwork recovery and tried loading the nandroid backup that I made, but when it restarts it just goes back into the boot loop.
I also tried flashing another rom (damage control 3.1.2) and wiping everything... multiple times. I've racked my brain for everything but at this point i think the only other way to get it back is to run the RUU which is impossible since the USB port doesn't work. Is there anything I can do?

[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

Help, please!

I have been rooted for a while and I installed a new rom, all went good. Rebooted my phone and can't access anything. So i booted into recovery wiped data/cache and tried to re-install. That froze and locked up.
Now i can't load into Clockworkmod Recovery, it stays at my HTC Incredible white screen and never loads.
I cant access the device through ADB or Shell.....
How can I reflash the recovery, and install a backup from Clockworkmod?
Thanks!
Roger
Me personally I would go back to stock, re-root and then start over. It might take longer than just reflashing a recovery, but to me also makes sure that nothing else is corrupting the phone, just my $.02.
If you want to go about it that way you can follow this thread, gets you back to stock and then you can root it and go about regular business
http://forum.xda-developers.com/showthread.php?t=786436 - you just need to follow part 2
That sounds like a plan to me.
The link you provided wants me to push files to my sdcard and flash with clockworkmod. I can't access clockworkmod and cant push any files to /sdcard.....
So how can I get back to stock without being able to access clockworkmod?
You don't have a flash card reader/USB card reader? If not then i don't know how to help.
If you do, these are the only steps you need to follow. just put the file on the root of your SD card. You don't need s-on because you aren't taking it back to verizon for repairs. Even if you need to after you root it again you can use s-on.
2. Download this zip file: http://www.fourty.net/~berzerker/sto....605.1_RUU.zip
3. Push PB31IMG-3.21.605.1_RUU.zip to your SDCard, renaming it to "PB31IMG.zip" (no quotes)(delete any other PB31IMG.zip you might have on there before pushing).
4. Boot into HBOOT, and it should recognize the PB31IMG.zip. Start the update and go get a drink (it might reboot once or twice, don't worry about it).
5. When that's done, reboot and you're at 2.2 stock!
Click to expand...
Click to collapse
OK, so i got a card reader, put the file on there and booted into HBOOT.
Nothing happened. So i powered down the phone and now the phone won't turn back on.
If i plug it into a power supply the led flashes orange....
Now what? Is this phone toasted??
Finally got it working. After a few hours of trying to load the image it took and booted stock rom up.
Thanks for the help!

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] softbricked my phone! keeps sending me to recovery screen :(

Hello!
I have a SGH-T889V Samsung Galaxy Note 2. I've had it rooted and running custom ROMs for more than 6 months, and I've never had an issue until now. I've tried flashing CM, pacman, and omnirom. All of them worked just fine (loaded ROM onto external SD, booted into recovery mode, factory reset, flashed ROM, flashed gapps, reboot phone and everything was peachy). I use Rom manager.
Yesterday, I tried flashing an update to omnirom (the 11/17 update) the same way as before. I got an error message, telling me the update failed. So I tried to reboot my phone again, but it told me that I had lost root access, and asked me if I wanted to fix that. When I picked yes, it went back to the Samsung load screen, and then the recovery screen appeared again. When I tried to "reboot phone now", it just flashed the samsung logo and then back to the recovery screen.
I tried loading the stock rom back on the eternal sd. That didn't work. Basically, when I took the external sd card out and stuck it in my computer, it told me that I had to format it to use it. It gave me exfat and ntfs as the write options. I tried it both ways, but neither of them were registering when i stuck the external sd back onto my phone and tried to mount it, so I can't flash anything from my external sd. To get my phone to register the external sd, I have to format it through rom manager / recovery screen. That works, and after that, my phone registers the SD card, but obviously I still can't flash anything off the external sd once I've formatted it on the phone.
I tried using the toolkit posted in the android development section to load the stock rom. I tried sideloading and also pushing the file to the phone. Both times, I got a messaging saying that it was waiting for USB debugging to be enabled. As far as I know, I can't do that from the recovery mode of ROM manager. So no dice there.
Essentially, I've softbricked my phone. Whenever i boot it up, it goes straight to recovery mode (and I only hold down the power button, not the typical power + home key + volume up key to bring up recovery). I can't flash the stock rom back on the phone, since my external sd does not register after i format it on my computer. When I try to plug my phone into my pc to load stuff on there directly, I can see it registers as MGH, but it does not show up in Windows Explorer to allow me to put any files on there. When I select "reboot phone now" in recovery, it shows the Samsung logo screen briefly before going back to the recovery screen.
I'm really stuck Does anyone have suggestions on what I can do. please?
Have you tried ODIN to flash stock image back on device? Another thing u could try is use another microsd card and format it as FAT32, load your ROM on there via PC and then flash whatever.
Sent from my Nexus 5 using Tapatalk 4
funkstylez said:
Have you tried ODIN to flash stock image back on device? Another thing u could try is use another microsd card and format it as FAT32, load your ROM on there via PC and then flash whatever.
Sent from my Nexus 5 using Tapatalk 4
Click to expand...
Click to collapse
thanks! reading up on Odin now, I'll let you know what happens after I try that.
funkstylez said:
Have you tried ODIN to flash stock image back on device? Another thing u could try is use another microsd card and format it as FAT32, load your ROM on there via PC and then flash whatever.
Sent from my Nexus 5 using Tapatalk 4
Click to expand...
Click to collapse
So I have Odin up and running, I have the stock rom and it's been converted to a TAR file. However, I can't get Odin to work properly because it does not register that my phone is connected to my PC (presumably it should show up in one of the rectangles at the top of Odin once I plug my phone into my laptop via USB). Since my pc (and thus odin) does not detect my phone, I can't flash anything onto it
At this point, I have the appropriate stock roms, I have odin, and my phone still boots up to the recovery screen (with rom manager), but I can't manage to get it connected to my computer, though I have the Samsung drivers installed and working (up until i softbricked my phone).
ETA: google is my friend! Found clear instructions on using odin to flash the stock rom, and yes, it worked. Thanks!!
Google is everyone's friend and I'm glad you figured it out.
Sent from my GT-N7105 using Tapatalk 4

Categories

Resources