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] TF101G bricked??? unable to restore backup!

Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....

Can you still get into clockworkmod recovery touch? If you can try using the ADB from there to 'adb push rom.zip filepath/filepath' to get it onto your Internal SD and then reflash from there. I just use cwm 3.2, it's rock stable and never gives me issues, and after reading all of the issues with new versions and lack of ext SD support I refuse to update.

Darth Valda said:
Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....
Click to expand...
Click to collapse
You 101G is NOT nvflash compatible. You don't have SBK v1.
The only thing you can try is ADB push the necessary files to the internal sd storage.

I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX

Darth Valda said:
I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX
Click to expand...
Click to collapse
Good to hear you got it working. Just a little FYI for the future.
Nandroid restore does not restore the kernel so next time just flash the ROM before or after the nandroid restore. That should put the correct kernel in place for it to boot up.

Did you try reflashing an earlier kernel? Those backups haven't been designed to store/restore kernel data (for us anyway). I think I had a similar experience, back when I was trying early AOSP ICS.

Hey! Thanks for the heads up, everybody!
I always thought that the nandroid backup restores everything (e.g. ROM, settings, base, kernel, etc.). That explains why the restore after the screwed up update to ICS didn't work anymore and why I got stucked in a bootloop again.
So even that seems not to be the last line of defense if you brick your device....

[Q] Is it bricked

I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.

jflynn0 said:
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
Click to expand...
Click to collapse
What instructions did you follow? Is the bootloader unlocked and can you boot into it? Does adb work? Need more info if we're going to help you.

It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
bootloader unlocked
I was looking around in cwm menu before I tried to install the stock asus rom. Just going thru the menu's looking trying to familiarize myself with cwm. I went to backup and restore menu and there was Zip there. I hit to power button instead of the volume and it starting restoring the device. After that i have not been able to get it to do anything after the asus screen. But I can get into the menu of cwm. When i tried following the adb, i go into cmd on my computer and change directory it tells me the device is not ready. I tried putting a zip on a sd card but I cant get it to show on the device to install.

Try a factory reset in CWM, see if that helps.

tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.

jflynn0 said:
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
Click to expand...
Click to collapse
Can you flash a different ROM, maybe the stock one?

Had the same problem. Tried to flash stock from Twrp recovery.
Wipe do a factory reset, wipe system and than flash the aokp rom again.
Then reboot and when you are back in System you can put the rom you like on your internal SD.
Back to Recovery and flash the new rom.

I got adb working and it come up in devices list. How do i flash the aokp rom on the device. I'm learning this as i go along, after this i might get the hang of this . I cant seem to push files using adb either my directory is wrong. I unzip it into a folder (C:\romfolder\aokp_tf201_build-38.zip/sdcard) and all that comes up scrolling page of commands and help for adb when i push

this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image

jflynn0 said:
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
Click to expand...
Click to collapse
Do not flash a 201 rom or image. Thats for the prime. Never flash roms designed for another device no matter how similar they are.

ok I downloaded this on
http://goo.im/devs/termleech/tf300t/aokp_tf300t_unofficial_20120617_2100_build-39.zip
have to go to bed but when i get up this afternoon will try to get it o go to device.
How am I suppose to get it to the device if the sd card does not show up on file list in cwm?

Can you still use ADB? You can always push the files with that.

how do i use adb to push the file on to the device itself. because i can add it to the sdcard by just putting in on there and then placing sdcard in device but the menu as far as install zip from sdcard never shows any zips that are on the card itself. Only thing that shows up are list of directories that look like a standard list from cwm. Also if you choose any of directories from that list it returns no file found. If I choose apply update on sdcard no matter how many time i have called the file update.zip says "no such file or directory install aborted". Or how do i push and image to the restore section of the device and where do i find an image at?

well still no luck. I think I will give it a few more days and if I still cant get it guess will go to best buy and buy another on. Any thoughts on Toshiba excite?

Try this i posted a tutorial on how to fix this http://forum.xda-developers.com/showthread.php?t=1738825 hope it helps

IT WAS THE FINAL STEP... and it did not work. (Stuck on boot loader warning screen)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.

I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you

I have almost the same problem as if the fastboot not install anything despite not display errors

great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.

do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom

Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!

ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors

angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.

ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.

K1 - So I think I may have bricked this thing. Looking for help, if any.

Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?

Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings

kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:

Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery

Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!

OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.

It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.