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.
Related
So, I'm in a bad spot with my Nexus S 4g. I had CWR installed on it and flashed a new rom yesterday to try it out, I had been running Deck's rom. I don't remember what the name of the rom was I flashed yesterday, but I didn't care for it so I was going to flash MIUI this morning. When i went to boot into recovery it brought me to the fastboot screen and said no boot or recovery img. From there I rebooted back to the rom I have loaded and tried to search around on the interwebs a little. I went into ROM Manager and tried to reflash the recovery, but that didn't work as upon reboot it did the same thing in returning to fastboot everytime. I did some more searching and I found info on an app called flash image that's in the app store that will flash kernels and recovery's. So I dl'd it and tried to reflash clockwork recovery from there. It gave me an error about not enough free space on the device. I went back to ROM Manager and set it to erase the current recovery before it flashed the new one in hopes that it would resolve the issue. So I reflashed the recovery again and went to boot to recovery. Now I can't get past the bootloader/fastboot screen at all. It won't boot to android, it won't boot to recovery. My pc won't recognize the phone to allow me to install the drivers for adb...I'm at a loss.
Any help would be greatly appreciated as I have no idea what to do next.
Thanks in advance...
Did you try to flash recovery through the computer from the cmd window, Because ROM manager doesn't flash recovery properly sometimes.
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.
Hi guys
I hope you can help. Ive been triying all day yesterday to root another rom to replace my cleanrom 4.1.1.
I run CWM 6.0.2.1 tried to flash several different roms withuot succes. Tried to flash CM10.2 but it hangs duing the boot screen. Tried to flash A newer version of clean rom but it hangs on the startup screen.
I did read on the internet that you need a newer recovery to flash a newer rom. So i tried to flash anther recovery. The problem is that fastboot does not see my tablet. My windows 8.1 PC recognizes the tablet but fastboot says waiting for device
I even tried to flash my tabet on a XP VM, but it wont recognize my tablet at all,
The funny thing is that i can flash my old cleanRom version 4.1.1 without any problems
iaudio87 said:
Hi guys
I hope you can help. Ive been triying all day yesterday to root another rom to replace my cleanrom 4.1.1.
I run CWM 6.0.2.1 tried to flash several different roms withuot succes. Tried to flash CM10.2 but it hangs duing the boot screen. Tried to flash A newer version of clean rom but it hangs on the startup screen.
I did read on the internet that you need a newer recovery to flash a newer rom. So i tried to flash anther recovery. The problem is that fastboot does not see my tablet. My windows 8.1 PC recognizes the tablet but fastboot says waiting for device
I even tried to flash my tabet on a XP VM, but it wont recognize my tablet at all,
The funny thing is that i can flash my old cleanRom version 4.1.1 without any problems
Click to expand...
Click to collapse
What bootloader are you on, you may have to upgrade the bootloader before flashing any current roms. Also try using running fastboot in Windows 8 test mode.
cmendonc2 said:
What bootloader are you on, you may have to upgrade the bootloader before flashing any current roms. Also try using running fastboot in Windows 8 test mode.
Click to expand...
Click to collapse
I cannot find anything about flashing the bootloader, if you mean a recovery, i already tried. In the past i had to flash a boot image using fastboot, but since my pc does not recognize the device in fastboot mode, i cant do anything
iaudio87 said:
I cannot find anything about flashing the bootloader, if you mean a recovery, i already tried. In the past i had to flash a boot image using fastboot, but since my pc does not recognize the device in fastboot mode, i cant do anything
Click to expand...
Click to collapse
upgrading the bootloader involves flashing the stock ROM. That can be done via the TWRP installed on your device, which you said can flash ROMs like CleanRom
cmendonc2 said:
upgrading the bootloader involves flashing the stock ROM. That can be done via the TWRP installed on your device, which you said can flash ROMs like CleanRom
Click to expand...
Click to collapse
This also involves fastboot, witch doesnt recognize my tablet (the pc does, but fastboot does not)
iaudio87 said:
This also involves fastboot, witch doesnt recognize my tablet (the pc does, but fastboot does not)
Click to expand...
Click to collapse
You'll need to get that working then. It's not hard just need to install the drivers from XDA - try the naked universal drivers first.
Hello,
I got this HTC One X from AT&T (->evita) and tried to get CM 10.2.1 running on that.
The steps I made:
Boot into bootloader, go to fastboot, then get the identifier, get unlock token via htcdev and unlocked it with fastboot.
I then flashed CWM 6.0.4.6 for evita via "fastboot flash recovery *filename*". Now I booted into CWM (recovery) and wiped everything instead of first trying to copy the cm.zip onto the sdcard. (I also didnt do this when the stock ROM was still running...)
Now I can access the phone via fastboot in the bootloader but I can not use adb or the USB mount when in CWM. Whenever I plug the phone into my computer (or laptop, doesn't matter. Also tried switching between USB 2 and 3 ports!) Windows keeps making the "unplugged" sound every second.
Reinstalling the latest HTC drivers did not change anything.
Anyone here knows a way how I can stop that or get the zip file on the memory? I also tried flashing the boot.img on boot and tested if I can copy the file then through CWM but that did not work.
Hoping,
NyphoX
Not sure if it'll work but try using TWRP recovery instead:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Installed the most recent version.
I get into the recovry and when I plug it into a computer Windows will keep making the "unplugged"-noise.
I can see the sdcard-directory perfectly when I hit install in both, TWRP and CWM but when I want to mount it via USB it will not change anything and I cannot access it on my PC.
adb doesn't list any device either.
Also, TWRP and CWM keep telling me that my phone is not rooted, when I try to power off or restart. Is that normal?
My other HTC One X (non AT&T) just works fine with cwm 5.*.*.*
It's normal for the recovery to inform you that you're not rooted, it'll suggest that you install superuser but there's no point doing that in your case because you have no working OS installed. Did you at any point perform a factory reset from the bootloader? If so, you've corrupted the internal storage (known bug on modified Evitas) and will need to wipe it with TWRP.
Sent from my Evita
Saw that in your Q&A.
I wiped the internal_sd and tested it after but it still did not work. I also tried a factory reset through TWRP but that did not help either.
Both recovery programs keep telling me "E:Unable to mount '/cache'.
Still not working. Q_Q
Update: I got like the oldest laptop I ever owned and installed the most recent HTC drivers there and tried to mount it. It told me in device manager that the "evita" is not recognized. When I let Windows search automatically it installed the drivers and I am now able to access the memory.
I can only assume what the problem was but it seems like the HTC One X (endeavoru) driver and the evita don't like each other...
TL;DR trying to install now. Will edit.
//EDIT: Windows still screws when I plug the phone to the other computer/laptop, so I just have to use the old machine now. Still thanks for your help, timmaaa!
//EDIT: It does work when I booted CM and enable the USB storage at the other two machines.
Everything was working fine but I haven't updated my ROM (Mokee ROM in my sig) in a long time. I also wanted to just start fresh. So, I rebooted into recovery and wiped absolutely everything. I downloaded the same (but updated) ROM I was using before. I put the files on a microSD and put the microSD into the tablet. I flashed the ROM and then GApps as described in the instructions and then rebooted. Now I am stuck in a boot loop. At first, I thought maybe the downloaded files were corrupt. So I downloaded them again on another computer. It didn't change a thing.
But every time I try getting into recovery mode, it just boots to the ROM. So how do I get things up and running again? I'm comfortable with the command line but right now ADB and Fastboot dont see the device. I've installed the USB drivers and 15 second ADB/fastboot install on Windows. I've never had this problem and haven't found anything online yet that provides a solution. What now?
x000111 said:
Everything was working fine but I haven't updated my ROM (Mokee ROM in my sig) in a long time. I also wanted to just start fresh. So, I rebooted into recovery and wiped absolutely everything. I downloaded the same (but updated) ROM I was using before. I put the files on a microSD and put the microSD into the tablet. I flashed the ROM and then GApps as described in the instructions and then rebooted. Now I am stuck in a boot loop. At first, I thought maybe the downloaded files were corrupt. So I downloaded them again on another computer. It didn't change a thing.
But every time I try getting into recovery mode, it just boots to the ROM. So how do I get things up and running again? I'm comfortable with the command line but right now ADB and Fastboot dont see the device. I've installed the USB drivers and 15 second ADB/fastboot install on Windows. I've never had this problem and haven't found anything online yet that provides a solution. What now?
Click to expand...
Click to collapse
Restore backup or flash some other Rom,
Sent from my GT-P3100 using Tapatalk
Yes, that is what I'd like to do. But how would you suggest doing that since I cannot get into recovery and am stuck in a boot loop?
Whew... I let the tablet sit for a couple of days while I worked on other things. I decided to try, just for the heck of it, to put it into recovery mode (Power+Vol Down) and it worked. I already had a new ROM ready to install on my microSD and did it. It looks like CM10 is going to be my ROM now. It installed and is running! What a relief!
It must not have been shutting down all the way before. Even though I saw the Samsung Galaxy Tab logo, there must have been something it didn't like at the time. No idea besides that.