Database Info

Nexus S won't boot to OS

I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.

Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...

I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.

Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2

Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!

[Q] Numerous issues: Boots straight to recovery, won't flash new roms...

I sent my transformer in to Asus because the screen did not turn on anymore. I just received it back and am having an assortment of issues:
1. If I boot it up normally, it books straight into clockworkmod recovery. The only way to boot into the normal system is to go into Asus recovery and cancel wiping data.
2. If I try to flash a new rom in recovery, it just resets the aokp rom that I currently have on there. I also tried flashing new recoveries from Rom Manager, and it says they were successfully flashed, but it is always the same recovery when it restarts.
I have tried fixing permissions, doing a wipe in Asus recovery, doing a complete wipe in CWM recovery, putting the update.zip on the root of the SD card (it doesn't detect it)...I am really at a loss here. The tablet is definitely rooted and I confirmed busybox was installed. Any ideas?

if you can NVFlash something. And try using gnufabio's recovery installer instead of rom manager

mrevankyle said:
if you can NVFlash something. And try using gnufabio's recovery installer instead of rom manager
Click to expand...
Click to collapse
Good call, I am going to try the NVFlash method.

Here's How I Bricked My TF300T

Hello Forum! I've come here for a little help! Here's My Story.
After running Cyanogen 10.1 Nightlies on 4.2.2 for quite some time, I decided to do a factory reset because my TF300T seemed to be running a little slugish. I DID NOT back it up (mistake #1), DID NOT have USB Debugging on (mistake #2), and, while CWM was wiping /data, I shut off the tablet (STRIKE THREE). Prior to my bonehead move, I had everything else squared away. The unit was fully functional. Now, I'm stuck in this infernal boot loop on the ASUS screen.
I can reboot into recovery, so CWM is not compromised. I have tried to push a new ZIP of the ROM via ADB (unsuccessful, thinking the drivers are nerfed) and through CWM (also unsuccessful).
If anyone has any ideas, please feel free to comment.
P.S. Please don't kill me Mods, I'll be good after this

Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?

Kazman101 said:
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Click to expand...
Click to collapse
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik

ricco333 said:
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
Click to expand...
Click to collapse
It Unbricked!
Step 1: Flashed TWRP 2.4.4.0 blob file to overwrite CWM (Check)
Step 2: Factory Reset and Wipe Entire Device (CHECK!?!?!)
Step 3: Flash CM.zip!?!?! (Not So Check ... PLAN B!)
Downloaded Chinese Stock system blob (don't ask, I know it was stupid, but go with me here)
Flashed the system blob (after 3 minutes ... SUCCESS!)
No more boot loop and back to stock ... now to root it again to get my sweet CyanogenMod back ...
Thank you Erik, your help was much appreciated!

Infinity bootlooping, seems unfixable

First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.

greydelta38 said:
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
Click to expand...
Click to collapse
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?

greydelta38 said:
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
Click to expand...
Click to collapse
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"

JoinTheRealms said:
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
Click to expand...
Click to collapse
Yeah - I'm also wondering what bootloader you are running with it.
If you are not current on either flash the bootloader/TWRP package from CROMi-X OP, boot back into system, let it bootloop if it does, boot back into TWRP and reflash the rom.

That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.

greydelta38 said:
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
Click to expand...
Click to collapse
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925

I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.

berndblb said:
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
Click to expand...
Click to collapse
sbdags said:
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
Click to expand...
Click to collapse
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.

greydelta38 said:
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
Click to expand...
Click to collapse
You need to specifically format data in twrp not just wipe data. Only formatting will restore the device now once data corruption has occurred.

Oneplus One TWRP Bootloop

Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.

Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?

This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?