Database Info

[Q] Nexus S Bootlooped and not detect by adb

Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?

I had that once when I installed stock. I fixed it by going into recovery and clearing cache and dalvik
Sent from my Nexus S using XDA App

I can't boot into recovery though - It's missing.

theadb said:
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
Click to expand...
Click to collapse
you need to install the proper nexus s drivers.easiest way is to go to the pdanet website http://junefabrics.com/android/ , download their free product, and let it install the drivers for you. did you flash the recovery through rom manager originally? anyways, then wipe(data. factory reset) and reflash the stock rom. you always have to wipe before flashing a DIFFERENT rom, or youll get stuck in a bootloop.

I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)

theadb said:
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
Click to expand...
Click to collapse
maybe?????

Will adb still work even though I can't boot my phone and turn usb debugging on?
Unfortunately I have 64-bit windows at work, but I'll try on my Win7 or Mac at home.

Still can't get adb to or fastboot to recognize the device...maybe I'm missing something...
I have no recovery and can't boot - what can I do?

Bump. In the exact same mess.
I was on MIUI ICS and tried to go to a stock GB rom, ended up stuck at the boot animation in the fresh rom (which kept looping). Recovery was a no-go too. I tried using adb to push another stock rom which again, installed but got stuck at the boot animation. After that even adb stopped detecting the phone.
What do I do now? theadb how did you fix it?
ADB is working as I plugged in my HD2, which was detected immediately.

Er bump?

Use fastboot to flash a new recovery, then boot into recovery and do what is needed. Recovery will probably be replaced by stock each time you attempt to boot into android while the stock ROM is installed.

I'm in the exact same situation and I don't really think there's anything we can do. We can't enter fastboot. We can't go into download mode. We can't boot into recovery there is literally zilch that we can do to fix the phone.

[Q] Did a factory restore and now my system only reboots in CWM

Hello guys...
I was using Thundersnap GB and "noobly" did a factory restore through system... Well, I lost everything including my rom, and my system only boots into CWM. I have managed to re-add some ROMs into sd, have installed them with CWM with no errors, wiped everything as usual, but the system insists to reboot into cwm, I cant run the rom.
Did anyone have an idea of what Im missing? :crying:

acpesreplays said:
Hello guys...
I was using Thundersnap GB and "noobly" did a factory restore through system... Well, I lost everything including my rom, and my system only boots into CWM. I have managed to re-add some ROMs into sd, have installed them with CWM with no errors, wiped everything as usual, but the system insists to reboot into cwm, I cant run the rom.
Did anyone have an idea of what Im missing? :crying:
Click to expand...
Click to collapse
I think you have corrupted boot loader sequence. Search XD for universal_recoveryloop_breaker.zip. Copy it to your sd card.and install it in recovery. It seems that you cannot use the systems factory reset options once you have installed a custom[wkparks] recovery and bootloader. only use twrp or cwm to reset to factory. Hope this helps.

keith210350 said:
I think you have corrupted boot loader sequence. Search XD for universal_recoveryloop_breaker.zip. Copy it to your sd card.and install it in recovery. It seems that you cannot use the systems factory reset options once you have installed a custom[wkparks] recovery and bootloader. only use twrp or cwm to reset to factory. Hope this helps.
Click to expand...
Click to collapse
Thank you for your help, man, but it didnt work. Actually I lost access to recovery, went stucked in LG logo now. I cant even recover with LG Tool... The program recognizes when I connect in download mode, but when upgrading the process stops at 10% due to bad communication or something else. I saw a video about reinstalling the drivers via device manager to get properly recognized, but I couldnt get it to work. Run Windowns 8/64, with LG p720h.
I think only way now is to unbrick, right? P920 method works with my P720?
Thanks in advance anyway.

It is likely a driver issue. Windows 8 tips at the top here
http://forum.xda-developers.com/showthread.php?p=39269819
I think drivers are the same for P720 but not certain. Roms are not the same so you will need to find firmware to flash.

[Q] Stuck in recovery restart limbo

Hello all,
Last night I was trying to install the latest Gummy release on my Verizon Galaxy S3. This was the first time I have tried to flash a rom on this phone. It failed, and I rebooted my phone, and now it will only boot into the clockwork recovery.
I thought it may have been damaged as i was transferring the file to the device. I had an SD card in my droid X, So I put it in my Galaxy and formatted it with clockwork. Then I transferred the gummy release (that I also re-downloaded) from my computer to the SD card via a memory card reader. I put it in my Galaxy and tried to install the release, and it gave me a different error
Code:
E: Can't Open /external_sd/Gummy-2.1-01-09-14-NIGHTLY-d2vzw.zip
(bad)
Installation aborted.
Edit: Tried a few other roms and they had the same issue, but Cyanogen Mod 10.2 worked. Anybody have any guesses why?
Edit2: Further developments, Trying to do the latest nightly fir the CM yields the same issue that Gummy's release gave me initially. It reports as follows:
Code:
E: Error in /external_sd/cm-11-20140110NIGHTLY-d2vzw.zip
(Status 7)
Installation aborted
Is there possibly a firmware issue at play?

Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery

I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536

twistedillutions said:
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
Click to expand...
Click to collapse
Sorry, forgot to mention, I did unlock with EZunlock. Would the clockwork on the play store be the latest one, or is there another place with more up to date versions?
Cappurnikus said:
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
Click to expand...
Click to collapse
Do you get the same error on install that I'm getting, ro are the installs finishing, but not booting?

Try goo manager or ez-recovery to install the latest recovery
right now i can think of
factory reset format data. Make sure u backup ur internal
Wen changing from rom to rom is a good thing to do a clean install
get the right gapps.
The 1st boot always takes time at least on me.
Sorry i cant think of more helpful things.. Been drinking

Looks like my recovery just needed an update. Thanks everyone.
Sent from my Nexus 7 using Tapatalk

Confirmed also an old recovery for me as well. Thank you very much!

[Q] Stuck in recovery mode boot loop

Tried installing a custom rom and apparently it didn't install completely. Unfortunately not my note 10.1 is stuck in recovery mode. It will reboot and always enters recovery mode. I can't seem to mount the internal sd card so I can add a new image to try and reflash. The original ROM i tried to flash it with was the 4.4.4 Omni Rom. My note is a 8013 by the way. Any ideas on how to fix this?

You can flash a new ROM using Odin or Heimdall . Download your ROM from Sammobile. Worked for me.

nyichiban said:
Tried installing a custom rom and apparently it didn't install completely. Unfortunately not my note 10.1 is stuck in recovery mode. It will reboot and always enters recovery mode. I can't seem to mount the internal sd card so I can add a new image to try and reflash. The original ROM i tried to flash it with was the 4.4.4 Omni Rom. My note is a 8013 by the way. Any ideas on how to fix this?
Click to expand...
Click to collapse
I guess the best option to do is a full wipe. Then download the rom again and flash via odin. Remember to check that USB debugging is enabled.

[Completed] CM13 + CWM + Gapps = Brick

Ok. I have a Samsung S4 mini. Yesterday I installed CM13. Dumb thing to do.
It was an automatic update from CMUpdater, so not through the Recovery menu.
For my surprise, I noticed that this update also updated the ClockWorkMod Recovery to the latest version available.
The CM13 installation went well actually .The phone booted fine. Then of course I needed the new Gapps installed. I downloaded the correct Gapps. Boot into CWM recovery. Choose the Gapps ZIP file. And... Error! I went back to phone to enable root acess (ADB & Apps), and enabled USB debugging also. And...Error! No way to install Gapps with CWM recovery.
After some search I realize that the new Gapps for CM13 is somehow not compatible with the CWM recovery that was instaled. So I downloaded ROM MANAGER to change the recovery to TWRP, which everybody said would perfectly flash the Gapps smoothly. Nothing happened. No TWPR. Only CWM still on. Then I downloaded Flashify and went back and forth on installing and unistalling TWPR and CWM. On and On.
Conclusion: somewhere along the process not only I couldn´t install TWRP recovery, but also have wrecked the CWM recovery. Now, no matter what I do, I cannot enter recovery mode at all, hence i cannot neither install Gapps or Reinstall another ROM to "start from scratch"....
I can boot the phone normally.
I can boot into donwload mode normally.
I tried installing TWRP .tar with ODIN3 but it keeps saying "cant open USB port", so it fails.
I have also installed KIES. It sucessfully install drivers, but fails to connect with my device.
Is there anyway to install a Recovery or a fresh new ROM without having to boot recovery?!
Some help? Please.

Hello,
Welcome to XDA.
Do you have USB debugging enabled in system settings to allow flashing via Odin? You may not even need to use Odin.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s4-mini/help
The experts there may be able to help.
Register an XDA account to post and reply in the forums. Good luck.