[Q] HTC Wildfire problem after root/custom rom - Wildfire Q&A, Help & Troubleshooting

Oke, so i have a problem with my HTC Wildfire. I decided to root it today and put cyanogenmod 7 on it. I found a guide on how to do this, followed it and it all worked fine.
When CM7 was running, I didn't really like the experience. It seemed slow and too buggy for my liking. Therefore i wanted to recover the previous state my phone was in. To do this, i tried to recover the back-up i had made with rom-manager.
However, the recovery didn't work. It said it did, but then the phone just freezed on the standard boot screen (showing the green HTC letters) Since then I haven't been able to get past this.
I tried recovering again from the bootloader; i've tried the factory reset; i've tried an RUU thing i found from froyo, and the result has always been the same. Nothing. The recovery and factory reset were reported to have been successful, but after it i still couldn't get past the boot screen. The RUU thing didn't work, it shows an 'unknown error' ([155])
So, does anyone know how i can fix this? At this point i don't really care what is my UI, whether it's the stock android; sense; or some ROM. As long as i can use my phone again.
Any help would be very much appreciated!

Flash a custom ROM (Any, Cyanogenmod 7 , or Sense) again via Clockworkmod. Follow this post (Ignore the parts where it says to backup apps and stuff)
http://forum.xda-developers.com/showpost.php?p=8926457&postcount=4

Problem is that i would need the CM7 files on my sd card. And right now i wouldn't know how to access it. I can't do it with my phone, since my laptop doesn't recognize the sd card when the phone hasn't powered up. And i don't have card reader for a micro sd card.
The last time i installed the rom, i did it with rom-manager, and didn't download any files myself (only via the app)

Boot into Clockworkmod Recovery (The procedure is given in the post I linked above. Press Vol Down + Power, Navigate to Recovery, Press Power Button..... and so on). Once it's done, connect your Wildfire to your laptop, then browse to "Mounts and Storage" in Clockworkmod, and select "Mount USB Storage". Now, you will be able to access your SDCard normally as it was before.

It's working! Many thanks!

Related

Problems with ROOT, Am I bricked!???

I was rooted and running a 2.2 rom and wanted to install the damagecontrol 3.2 rom, which, as I understand it, requires NAND to be unlocked. I downloaded Simple Root and tried to unlock NAND.
When I turn on the phone I get stuck in a boot loop.
I try the recovery console. It takes a few minutes to load PC36diag.zip, the update for NAND which I already installed.
When I say no to the update and no to restarting I get into the menu, but if I try RECOVERY it loads the phone with the exclamation point, but I am unable to connect using the adb batch file I have always used before.
Also, when I try HBOOT USB the drivers aren't able to be installed. The device is read as "Android 1.0".
Can someone please help me?
devin.slick said:
I was rooted and running a 2.2 rom and wanted to install the damagecontrol 3.2 rom, which, as I understand it, requires NAND to be unlocked. I downloaded Simple Root and tried to unlock NAND.
When I turn on the phone I get stuck in a boot loop.
I try the recovery console. It takes a few minutes to load PC36diag.zip, the update for NAND which I already installed.
When I say no to the update and no to restarting I get into the menu, but if I try RECOVERY it loads the phone with the exclamation point, but I am unable to connect using the adb batch file I have always used before.
Also, when I try HBOOT USB the drivers aren't able to be installed. The device is read as "Android 1.0".
Can someone please help me?
Click to expand...
Click to collapse
Bootloop means you need to do a full wipe.
First thing's first, delete the PC36IMG.zip file from your SD. Then when you get the image of a phone with an exclamation mark, hold down the power and volume up key to get into recovery.
As for the last bit, I'm sorta' confused what you're problem is.
Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.
Something similar happened to me. For me, instead of booting Damage Control, I switched it to Fresh and booted Fresh v3.0 and it worked and booted. Then I unlocked the Nand and made a nandroid. Then whipped everything 2 times and booted DC and it worked fine after that.
devin.slick said:
Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.
Click to expand...
Click to collapse
You can get in to usb and put fresh on there by going to recovery mode and selecting one of the options that says USB, i can't remember the exact wording.
Added: I just checked it's called "USB-MS toggle"
devin.slick said:
Part of my problem is that I can't delete the file from the SD card. Can't get into the OS and can't turn on USB.
Click to expand...
Click to collapse
When you get the exclamation mark screen, hold down the Power and Volume Down key. Once in recovery mode, select the USB-MS Toggle feature, this mounts your SD card yto your PC. You should then be able to access the root of your SD card via the Removable Disk icon on your computer.
It wouldn't let me load USB from the console/whatever either... Another weird driver issue.
But after several more hard battery pulls I let it try again to boot and it showed me the "HTC, quietly brilliant" boot screen, which was different that what it had before.. I let it load and now I'm in android, but it says my SD card is removed.
Is this a part of the process necessary to unlock NAND?... Do I have NAND?
devin.slick said:
It wouldn't let me load USB from the console/whatever either... Another weird driver issue.
But after several more hard battery pulls I let it try again to boot and it showed me the "HTC, quietly brilliant" boot screen, which was different that what it had before.. I let it load and now I'm in android, but it says my SD card is removed.
Is this a part of the process necessary to unlock NAND?... Do I have NAND?
Click to expand...
Click to collapse
Check and see if your USB connection is in Charge Only or Disk Drive mode.
devin.slick said:
Is this a part of the process necessary to unlock NAND?... Do I have NAND?
Click to expand...
Click to collapse
no. You make your nand back up when you are in recovery mode and you select nand back up and it backs up everything. You'll need to follow through with the rest of the Nand unlocking instructions.
Did you download and follow the steps of the flash_image and mtg-eng.img etc etc...? Then the rest of the steps?
That's the first thing I tried to do when android loaded. It's not even an option. It says I removed my SD card.
I restarted, denied the update to get through to recovery, and I still can't connect with adb -it shows "Unknown Device" in the device manager.
devin.slick said:
That's the first thing I tried to do when android loaded. It's not even an option. It says I removed my SD card.
I restarted, denied the update to get through to recovery, and I still can't connect with adb.
Click to expand...
Click to collapse
are you connected with charge only? try hot sync (you need to install the program, which include drivers. this is on the htc website)
Mine worked for hot sync but not charge only
Looks like you may need to run through this. http://forum.xda-developers.com/showthread.php?t=695243
I've been reading that post.
When I select fastboot, it gives me other options.
bootloader
reboot
reboot bootloader
powerdown
If I select bootloader it takes me back to the main menu, if I select reboot, I get back to android and still do not have access to my SD card, so I can't get out of the debugging rom, or whatever it is.
I put another SD card in, so I don't have to wait on the update.zip to be read every single reboot, but that's all it did.
Am I doing something wrong?
Don't know then... sorry. You can try starting over from the beginning?
Best of luck.
FML.
Someone? I'm totally stuck.
And my phone says the the charger isn't delivering sufficient voltage... and I'm down to 8%.
HEEELLLPPP
its always an good idea to have a micro sd to sd adapter
After 3 locations, I found a Sprint store that actually existed... had them copy an update.zip that I brought on a flash drive onto my micro sd card. I tried booting into recovery and it didn't do the update. They suggested another store that does repairs, so I went to my 5th store, where I just dropped off my phone, hoping they'll reflash it fore me. I'm expecting a call back.
What a wonderful birthday this is turning out to be... lol. FML
UPDATE: I called them and they said the phone needs to be exchanged... but I don't know how they're going to react to it having the recovery/debug version of android on it.
Does anyone have ANY advice?
Just tell them to put in a fully charged battery for you. Then when you get it home try the Simple Root Guide you tried at first. This time post your issue (if you have any others) in that thread and myself or Jiqqa will help. Make sure before starting that guide that you have .NET framework and HTC sync installed on your computer. But you should be able to root phone and then be able to flash custom ROM after that.

HTC Desire Stuck on HTC logo - Recovery not Working - NOT SOLVED!!

Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Cyanoid said:
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Click to expand...
Click to collapse
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it says "Android Bootloader Interface" in Windows Device Manager, that it says "HBOOT USB PLUG" on the HBOOT screen when connected via USB, and that I am able to issue FASTBOOT commands from the PC. But I can't issue adb commands, so it appears I can only "partially" communicate with the phone from the PC.
Should I try CLEAR STORAGE, or could that fully brick my phone?
On the HBOOT screen, these are the status messages that load:
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nbh]
No Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99DIMG.nbh]
No Image or wrong image!
waynestir said:
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Click to expand...
Click to collapse
USB Brick
For me, it sounds like a typical usb brick :/ I hope you still have rooted ROM. Search through this forum for unbricking guide.
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
HTC Desire Stuck on HTC logo - Recovery not Working - SOLVED!!
madcr0w said:
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
Click to expand...
Click to collapse
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
sorry for delayed responce. I'm sure you had already found a solution by now but in the off chance you didn't.
you have to load fastboot not hboot.
from a power off state hold back button and power on phone. this will load fastboot and ruu will find device when run.
Cyanoid said:
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it o Image!
Click to expand...
Click to collapse
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
expza said:
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
Click to expand...
Click to collapse
+1 There is a good guide to fastboot commands on the android wiki:
http://android-dls.com/wiki/index.php?title=Fastboot
Should be a case of wiping system, data, cache, then flashing recovery image. Then boot into that and restore a backup or flash a rom.
Cyanoid said:
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
Click to expand...
Click to collapse
can u plz help me frm with post u solved ur probs....i m stuck too
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Does your phone get hot and overheated during the htc logo? It did so to me and it turned out to that my CPU had melted and overheated. Take it to your retailer and they will fix it for free because it's not your fault, it's the phone that overheated.
Try this:
-download this with ur pc and rename it a PB99IMG.zip (not PB99IMG.zip.zip ok?)
-then put it on the root of ur sdcard (not in some folder) through an sd card reader
-ensure the battery is charged much than 30%..better more
-with the phone off (remove battery and put again) press and HOLD the volume down key and press (still holding the volume down key) and hold the power button..hold both and wait to enter in the hboot
-there wait a bit, and it will ask to u if u want apply the update, select yes with the volume keys and confirm with power button
awayra said:
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Click to expand...
Click to collapse
Just go to my troubleshooting guide, you'll probably find an answer there.
Send it back for warranty repair.
Sent from my Motorola Startac running Atari 2600 software!
@nhrsak - you save me, thanks very much!!
Did you try getting s-off with Revolutionary?
I had problems when i was s-on, but when i s-offed, everything went fine.
Have you tried flashing recovery.img via AndroidFlasher(from XDA)?

[Q] Also stuck on white boot screen with HTC logo.

Problem is:
Few months ago i rooted my unbranded DHD, installed CyanogenMod 7.1, it worked perfectly fine for a couple of months, but a few days ago, my phone was on but did not respond anymore. I tried to reboot it, but it got stuck at the white screen with the HTC logo (sometimes it bootloops, other times it freezes)
I rebooted the phone with the volume down key pressed, so it would give me that menu,
scrolled down to "Recovery", i get the recovery menu from ClockworkMod (5.0.2.0), but then my volume key does not work ! i can not do whipe or anything else, the phone freezes.
I mounted the SD card in my PC, cleared it, put a rom in root of SD card and call the rom "PD98IMG.zip" and put the SD card back in my phone. I start the phone with the volume key down pressed, i get that
white screen with the menu and it then finds the .zip file.
It then reads the image, parses the image and then tries to load "NV.img" on which my phone freezes again.
I tried CyanogenMod and LeeDroid, and a stock rom. They all do the same thing, as written above.
When i connect my phone to my PC, my pc tries to install the driver, but gives me an error, saying the device is not known. I have installed both HTC Sync and the SDK. Tried it when i had only HTC Sync
installed, did not work either.
I also tried a RUU (.exe file) but this program tells me there is no device connected...
My phone is over a year old, so i have no warenty anymore, that's why i rooted it.
Phone is in S-Off Mode
HBoot-0.85.2007
Radio-26.03.02.26_M
OS version 1.72.405.3
Tried to boot with SIM and SD, just the SIM, just the SD and with none of them. Outcome is still the same.
i've read a few things about abd and such, never used it before, so please, speak noob
ok...
got it sorta running, but, whatever rom i install, it comes back like its chinese, it wont see my SIM and im in some sort of set up. I can do the setup, but when i come at the Wifi menu where i have to choose my wifi, it freezes..
Tried stock rom, CyanogenMod 7.1 (on which it ran perfectly before it crashed) and LeeDroid.. they all come to this..
Now when i try to load a rom (cyanogenmod 7.1 again) and go into hboot then choose recovery, the phone shows an image of a phone with a red triangle with a ! in it.. and wont install..
Delete PD98IMG from sd card. Reboot the phone as you did before (volume down + power button) plug the usb to pc (It should now read fastboot usb) and try to run an official RUU.exe
Just to see if it works with the stock rom.
The red triangle could be the stock recovery. From stock recovery you cannot flash any custom rom. From red triangle screen push volume up and power button. It should go through a menu where you can try to do a factory reset, just in case...
Ignore the wifi setting, if this is causing freeze. You can set it later.
Here is a list of official RUUs. Download the appropriate and run (colud be the 12 from the top). I know you tried already but just an idea.
Also, you may need the driver. Uninstall HtcSync and download and install this Driver. Better to reboot pc after you installed the right driver.
Good luck!
Thank you vey much !
Downloading a RUU at the moment. I also wanted to download that driver, but that is not a correct link. (the link says http:/ /htcdriver.3.00.700.exe which ofcourse wont let me download anything.
Could you please give the correct link ? For now i'll try the SDK one, downloading that RUU is going to take another hour, i'll be trying this RUU when its downloaded.
Thnx again !
TijnS said:
Thank you vey much !
Downloading a RUU at the moment. I also wanted to download that driver, but that is not a correct link. (the link says http:/ /htcdriver.3.00.700.exe which ofcourse wont let me download anything.
Could you please give the correct link ? For now i'll try the SDK one, downloading that RUU is going to take another hour, i'll be trying this RUU when its downloaded.
Thnx again !
Click to expand...
Click to collapse
Uninstall current driver and use this one >>>>Download driver here

[Q] Help! Accidentally deleted system and can't restore or install

Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent
Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed
Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent
You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.
Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent

Samsung S3 (tmo) soft bricked, encrypted, USB debugging off

Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt
[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.
Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.

Categories

Resources