Develop Bugs

Critical BootLoop (No CWM Access/USB Unrecognized)

My Salutations, I am asking a question in regards to a serious bootloop I have managed to pull myself into.
Most bootloops I usually just enter CWM and flash another rom or restore. This problem however is much more serious.
Every time I attempt to enter CWM it goes directly to download mode. It's as if CWM doesn't exist on my phone anymore or something.
Download mode is the only thing I can access. I have tried multiple attempts to enter any other recovery mode but they all end up getting me to download mode.
This isn't the only problem. I thought this wouldn't be a big deal until I realized my PC can't recognize my phone at all anymore. Even before I got into the bootloop, my phone would only charge but any other recognition from the PC was absent. I have all the correct drivers installed including numerous attempts at re-installing, re-configuring, and restarting my PC.
I think I may have reached an irrecoverable error.
Any ideas would be much appreciated. Thanks.
FYI, The ROM I flashed when my Phone started acting like a bundle of ninnyhammerness was AOKP milestone 6. It's not the ROMs fault of course, seeing as how this ROM is very good. I also had the Darkside kernel. This is when I couldn't manually enter CWM. In stead, I had to let the phone boot up and utilizing the power menu, restart in recovery mode. I thought this was strange at first. I then wiped, and decided to flash the 20th Nightly of AOKP Jellybean just to try it. It booted fine, but then when I had to restart to enter CWM again I chose to flash another Darkside kernel. After this, my phone went into a bootloop. That is where everything else fell apart.

Sounds like either the recovery isn't sitting in the system correctly or its gone. When your phone is in download mode you said that you can't connect to pc. Are you running odin as admin and/or connecting the device to pc previous to putting the battery back?
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!

Yes I did run Odin as an administrator. I also tried connecting the device prior to putting the battery in, and also after.

I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!

kmcclry said:
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
Click to expand...
Click to collapse
Thanks but, it still hasn't worked. It keep saying "USB device not recognized, Device driver software was not successfully installed."

I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.

i3lackDawn said:
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
Click to expand...
Click to collapse
also it may be because of a faulty data cable !

Htc low battery, no recovery, script not working fastboot fail

hey there!
Ok so I got this problem. My phone felt to the floor like 2 weeks ago and the screen got crashed, everything else works normally, touch is ok, screen is ok, just glass is broken, after 2 days I downloaded some dota apps and it suddenly started rebooting and crashing:
By this I mean, apps stopped working and lots of pop-up messages appeared, after some reboots It stopped turning on, so I decided to root it and installed a custom ROM the one from mike, Android Revolution, this was last week, this weekend it worked fine until sunday when it got bricked because of an outdated recovery from clockwork. I managed to solve this with some help from you guys, but now again.
I flashed the android monday again with same version, it was working well until yesterday at night, it started showing some whatsapp stopped working stuff again, i rebooted it and now a bunch of window errors... reboot it again and well... no luck it stayed in the Android loading window.
After this I was trying to install the stock version ROM from mike also, and that's when it got worse.
Flashed boot and recovery OK, then rebooted and when I tried to install the ROM it just won't let me, failed unknown error, failed remote : 00030000, and other messages, now when I try to flash the recovery again it says low battery, and when I try the script to charge it it won't work, FAILED remote: unknown reason.
What can I do guys? =S (Sorry for the long post, I just don't know what could it be, and I wish by giving that much information someone can find out the reason, contacted HTC and they said it has no guarantee since I rooted and the glass is broken)

can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.

faiz02 said:
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
Click to expand...
Click to collapse
I can but there is some weird reason that won't let me do any flash, either low battery and when it gets charged a bit (because it may charge enough sometimes) it says FAILED remote:00030000 or unknown reason.
Don't know what it could be.

I ran into the exact same problem, the charger script does not help me too (low power on usb port of pc).
Thats how I fix this:
1) disconnect original charger, let's phone die. or use shutdown in fastboot.
2) connect original charger, and wait while phone powered up (He himself off as he does not have enough battery power.). disconnect charger.
3) vol.down and hold power,choose fastboot
4) connect charger
5) choose reboot bootloader (phone will reboot in fastboot)
6) choose reboot bootloader (phone will reboot in fastboot)
7) choose reboot bootloader (phone will reboot in fastboot)
....(do it fast)
249) choose reboot bootloader (phone will reboot in fastboot)
250) choose reboot bootloader (phone will reboot in fastboot)
251) disconnect charger, choose shutdown.
252) go to PC
253) vol down, power up
254) choose fastboot
255) flash the custom recovery with power supply support
256) flash custom kernel
257) don't disconnect USB!
258) fastboot / reboot bootloader / hboot
259) recovery
260) mount USB storage
261) drop zip of custom flash to the phone
262) unmount
263) advanced / restart recovery
264) flash the zip of rom
265) restart phone and dont disturb it, at 30 minute, let hi charge.
266) disconnect USB and connect original charger (1A)
267) Have fun!

It worked but bad news... now as always I am getting the message windows, with some weird apps.
First it was htc.com.bgp or something which I found it was the weather, then whatsapp, then Personalize, pretty much everything I open stops working after a while, what can I do? This was the exact reason that brought me here in the first place. It started showing these messages and I decided to install a custom ROM, it was first stock and locked and happened, now with this Android HD ROM it is still the same.

Thanks man... i was scared like hell when i realised that by script my battery voltage didnt raise up... even worse... it became less... i was reboting bootloader for 1h, but finally it worked... now im charging it to max... then ill flash stock rom
Thanks again.

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.

[Q] galaxy nexus stuck in bootloader, not recognized by pc

hi guys,
tragedy started like that: today i decided to give miui another shot. downloaded latest miui developer rom to sd card of my galaxy nexus, rebooted into recovery and flashed miui zip and tiny kernel afterwards. stupid me i forgot to wipe cache before installing the new rom. hit reboot in cwm, which kindly told me that the new rom could make recovery unusable. here i accidentally selected the obvious wrong choice, which said "dont fix problem" or sth like that. dont know if recovery is gone now... after reboot miui was trying to boot without success (mi logo shown until you turn the phone off). so i went to fastboot by pressing volume down (my volume up is broken!). fastboot acts pretty dead: cant scroll through options by pressing volume down, cant do "normal" start by pressing power, absolute no reaction of the phone. also the phone is not recognized when connecting to pc via usb (tried the samsung original driver). phone is recognized when miui is trying to boot, but i cant send any commands via fastboot.
im thankful for any advice that lets me install a new recovery/boot into recovery/make it boot again!
fastboot mode details:
product name - tuna
variant - maguro 16gb
bootloader version - primemd04
baseband version - i9250xxlj1
carrier info - none
serial number - irrelevant
signing - production
lock state - unlocked

anyone?

[Q] Gnex Brick Mount Fastbood Write Fail help :'(

Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked

BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!

can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?

Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.

I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?

Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems

Anyone?

does erase work?

yes

can you get into recovery?

oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka

how do you know that erase works, I mean that what you erased has really been erased?

One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.

still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?