Related
For some reason my Nexus S will no longer go into recovery mode ... it only restarts the fastboot mode when selected. I'd like to get as fresh a start as I can here, but can't figure out how to get back into recovery mode to get a new image loaded.
I've got the stock-GRH78.zip which seems like the right place to start, but can't figure out how to reload it.
Thanks!
Moved to general
thanks for the move ... hopefully someone will be able to help!
If the bootloader just reloads itself whenever you try to go into recovery, that means that the phone doesn't detect a recovery image. Check the top of your devices as well. In red colors, it should say something about not finding a recovery.
We don't have a true copy of the stock recovery, so you are going to have to use Clockwork Recovery in order to move forward from here. Google has not released the recovery files/rescue .zip so you're going to have to unlock the bootloader/root to fix this. Once you've flashed that on, then you can do a NAND restore of the stock 2.3.1 image linked in the stickied FAQ or in the development section.
EDIT: Just realized AllGamer made a way better step by step guide stickied at the top of this forum: http://forum.xda-developers.com/showthread.php?t=895545
unremarked said:
If the bootloader just reloads itself whenever you try to go into recovery, that means that the phone doesn't detect a recovery image. Check the top of your devices as well. In red colors, it should say something about not finding a recovery.
We don't have a true copy of the stock recovery, so you are going to have to use Clockwork Recovery in order to move forward from here. Google has not released the recovery files/rescue .zip so you're going to have to unlock the bootloader/root to fix this. Once you've flashed that on, then you can do a NAND restore of the stock 2.3.1 image linked in the stickied FAQ or in the development section.
EDIT: Just realized AllGamer made a way better step by step guide stickied at the top of this forum: http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
will run through this ... thanks. I don't see any mention of not finding a recovery image. Red just says Fastboot Mode and that my lock state is unlocked.
still struggling along here ... in fastboot mode, I can't connect to my device to run commands so fastboot seems pretty impossible. I can connect when the phone is more fully booted, but you can't run (or I can't anyway) the fastboot commands ...
atmasphere said:
still struggling along here ... in fastboot mode, I can't connect to my device to run commands so fastboot seems pretty impossible. I can connect when the phone is more fully booted, but you can't run (or I can't anyway) the fastboot commands ...
Click to expand...
Click to collapse
You need to install the drivers for fastboot to recognize the phone. Should be detailed in the link I gave you. If not, try the method below. It's what I used. not entirely sure if it will work for you, however.
http://forum.xda-developers.com/showthread.php?t=878786&highlight=pdanet
I'm on a Mac ... No drivers required as I can tell. It worked pre-root.
atmasphere said:
I'm on a Mac ... No drivers required as I can tell. It worked pre-root.
Click to expand...
Click to collapse
Eh, sorry, don't think I can suggest anything else. :/
What worked pre-root? ADB or Fastboot? They're different. Nothing happens when you type in "fastboot devices?" If fastboot doesn't work, I'm pretty sure you're toast. :/
Both commands work but not once I am booted in fastboot mode. Then I lose my connection from the desktop ...
... once rebooted, I am still unable to do anything from fastboot mode. ./adb devices shows nothing listed. added the cable once there, rather than with it connected to switch over. sigh.
atmasphere said:
Both commands work but not once I am booted in fastboot mode. Then I lose my connection from the desktop ...
Click to expand...
Click to collapse
I often don't get a connection on the Mac unless I unplug it from USB and re-plug it in after I've entered fastboot.
Yeah thanks I have tried that multiple times as well as used multiple ports and a USB hub. Maybe rebooting my Mac a few times will do something
unremarked said:
Eh, sorry, don't think I can suggest anything else. :/
What worked pre-root? ADB or Fastboot? They're different. Nothing happens when you type in "fastboot devices?" If fastboot doesn't work, I'm pretty sure you're toast. :/
Click to expand...
Click to collapse
when I do ./fastboot-mac devices I can actually see something ... that's got to be good! adb shows nothing in fastboot mode.
resolved ...
courtesy of my waking up and of course the guidance here, I was able to sort this out by flashing over a recovery image via fastboot. I then used the GRH78 Nandroid backup to get my S back in order. whew!
thanks everyone!
atmasphere said:
when I do ./fastboot-mac devices I can actually see something ... that's got to be good! adb shows nothing in fastboot mode.
Click to expand...
Click to collapse
that is correct, ADB is more for when you are already BOOTed up on the phone
fastboot / fastboot-mac is for when you are in the BOOTloader screen
Just a suggestion, since you have a MAC
it'll be best if you set up a VMware WinXP machine set aside with USB enabled
you'll come across a lot of GUIDEs, HOWTOs and other references written for PC users.
LOL just saying that reminded me of the MAC & PC commercials
AllGamer said:
Just a suggestion, since you have a MAC
it'll be best if you set up a VMware WinXP machine set aside with USB enabled
you'll come across a lot of GUIDEs, HOWTOs and other references written for PC users.
Click to expand...
Click to collapse
Kind of ironic that a linux/unix based phone doesn't have the best support for it on unix based computers like the Mac.
At least fastboot plays nicely with Androids on the Mac. The Galaxy S phones I've had forced me to find an old windows laptop to be able to use Odin.
Been modding android devices since the G1 but never got stuck like this before. Already spent hours of searching and googling but couldn't find any definite answer.
My B70 got bricked when using a program to boot into recovery.
Is there any way out or should I just throw it away?
I have a feeling that the device is looking for a recovery on internal SD card and fails. I can see the unit as ADB unit but when trying to connect it says device is offline both in normal boot or in recovery boot.
Been trying putting stock roms on external SD but it never runs it.
Has anyone solved this problem?
Check your SBK version and try to NVFlash
Try to boot recovery/apx wipe permissions /data if possible
post questions in Q&A not Dev
After a lot of examination it has been decided that you have posted this in the wrong section and we shall place it where it should be. Please make sure you post correctly next time.
Like mentioned already, some B70 are SBKv1 meaning nvflashable.
What app did you use to get into recovery causing the "brick"
Can you still get into cwm recovery, ect.
you still have hope if ADB can see it, try to update your driver.
If it work use ADB to push the file you need.
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
The app I used to get into recovery was just a random boot into recovery app. It worked many times before. I don't think taht app caused this, maybe the recovery files where deleted?
df9517 said:
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
Click to expand...
Click to collapse
You can use SBKdetect to check your SBK version (linux)
Did you have CWM before? Are you rooted?
What is your tablet doing right now? Stuck at the start up screen?
My tablet was previously running rooted ICS WW .11 with CWM.
Now its just stuck at the first boot image. I can go into same image where it tries to run recovery image by holding vol down. I guess it is standard brick.
Not getting anywhere with ADB, device is offline
hmm.. can you cold boot? just hold vol-down and wait?
df9517 said:
Not getting anywhere with ADB, device is offline
Click to expand...
Click to collapse
Search on here for the universal naked driver. Try that or sometime if you can try a different usb port.
Can you get into CWM Manually?
Hold VOL DOWN and POWER for about 10-12 seconds until some small text appears.
Quickly (within 5 seconds) release both buttons and hit VOL UP to enter RCK (Recovery).
If you can get into CWM this way you should be able to clear some caches and see if it will boot. If need be, you may be able to flash a new ROM if need be.
I only got the naked ADB drivers to work. The real ASUS ones does not work. Only tries 64 bit though.
Of course I tried to go into recovery manually.
Actually I now remember that just before this happened I updated CWM through the clockwork app. Probably updated to a version that does not work.
Since you have ADB working, download a CWM flashable .zip from your favorite recovery thread and extract the recoveryblob.
adb push it to /temp/dd or something similar, then run adb shell, su, and (you will need root/busybox on here) dd if=/your/blob/here of=/dev/block/mmcblk0p4.
after running that, run reboot, you should see a blue line and be able to get into a good CWM recovery. never use rom manager.
Thing O doom.
It always says my device is offline using ADB. I have only got naked driver to work.
But now I saw the NVflash for B70+ devices in your post. I will try that tonight.
I have not given up.
Yes, that is probably your only hope if you can't get ADB working, and it just came out! Lucky day
Yes, thank you all!! Finally NVflash for B70+ devices saved my day. Reflashed original ROM.
A long time ago I rooted my phone and put CM9 on it. I decided I wanted to go back and try Jelly Bean (from factory then go outwards).
I had a difficult time with the CM flash and found one that worked, and thought I was good to go.
My phone: gt-i9020a nexus s
Product name: Herring
HW version 16
boot loader: i 9020xxkl
carrier att
fastboot enabled
unlocked state.
I can launch the official 2.3.6 (Build GRK39F), from google
then the OTA updated kicks in and the phone is stuck at 'boot' Google logo on the screen.
I have done the information below and the same keeps happening...
link: http://forum.xda-developers.com/showthread.php?t=1586845
first of all, the VQ8PQk is a patch file, not a full rom. So flashing that on something else than 2.3.6 will never work. Get into clockworkmod recovery wipe wverything from the mounts and storage menu, and then flash this file : http://android.clients.google.com/pa...o/ZD3PyN0t.zip and THEN this : http://android.clients.google.com/pa...o/hR7QFEtn.zip
and other steps I could try to work around, none of them seem to work.
Am I missing anything?
Thanks!
Use the full factory rom images (sojuaxxxx) from Google.
https://developers.google.com/android/nexus/images#sojua
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Edit: install CYGWIN to have linux-like commands (works with tar, adb, fastboot) in windows.
Do you have a backup (preferrably CWM backup) that you have prior to trying to get JB working? If so keep that handy, and preferrably store it on the PC. Titanium backup can ease migrating apps after a wipe and is highly recommended, so do one of these too if you havn't already.
After you make sure you have a solid backup with the information that you want/need on the phone, i would just start fresh. The best way to do this is to do a factory image flash (note: you want sojua if you have the 850MHz variant which is from AT&T). Flashing these will wipe all user data and the /system partition, the sdcard won't be touched. Basically you download it, extract it, then hook up your phone in fastboot mode and do the commands as written in the text file (or run it as a script if you know how). I've described it in more detail elsewhere as have others, doing a search should give results pretty quickly
This will become a factory install of android as given by google, in your chosen version. I'd go straight ot JB and then you can see how much you like it. CWM backup data can be extracted if you lost some crucial information in the flashing and all your apps and their data can be easily restored with titanium backup.
morning update
_android_ said:
Use the full factory rom images (sojuaxxxx) from Google.
Follow the instruction on that page (scroll up). If using Windows, use 7zip (or similar util) to expand the .tgz file, open content of "flashall.sh" and execute the commands one at a time.
Code:
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-jro03e.zip
The last command will wipe all data and install new 4.1.1 rom.
Click to expand...
Click to collapse
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
lost_man said:
running linux, no cygwin needed
did this again this morning..and i'm stuck on the google boot screen with the unlocked padlock on the bottom.
how long should this run (20 minutes now)
I have tried the roms from that page, the 2.3.6 is the only rom that I was able to get working..
Click to expand...
Click to collapse
Make sure you use the sojua versions.
Do you mean you finish all the steps and upon reboot, it's stuck on Google boot screen?
What do you mean by you can only get 2.3.6 working? It went past Google boot screen?
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
lost_man said:
** ran 'flash-all.sh" see if that changes anything, nothing like a script to rule out human error.***
**** that was a mistake...now phone is not turning on, the screen is dead...when i plug in USB chord, nothing is detected no state change on the phone. When I press buttons no state change nothing changes on the screen. I actually think my phone is a true brick, not a software glitch that is fixable....any suggestions now? ****
Click to expand...
Click to collapse
Some (quite a few) Nexus S seemed to be vulnerable to Jelly Bean/CM10 update in that the mainboard is toast. I think the only option is to send back for warranty repair. There are some threads on rigging some kind of adapter cable but that will definitely void your warranty (physical mod).
Doesn't sound good, there have been instances where the flash storage has given up and ends up needing a new SoC (the whole mainboard) and similar issues. Some more information would be good to diagnose this better though.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
-Take the battery out for 5 minutes, place back in, can you get into fastboot?
-Can you flash recovery and radio? Can you enter recovery?
-After the "fastboot -w update ...." command, what messages do you see on the phone (at the bottom)?
If you can't get the phone to turn on at all after a good 5 minutes without the battery inserted, give AdamOutlers resurrector a shot. A nice phone call to samsung might be a good idea if you're still within 12 months of purchasing. Hopefully it all turns out okay.
Click to expand...
Click to collapse
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
lost_man said:
Did all of the above, nothing. adamoutliers does not see a device connected.
lsusb shows nothing
dmesg shows my device disconnect, after the failed boot, no reconnect.
I'm headed out for a few hours, I will leave battery out, and phone disconnected but i'm thinking it's toast. Att will send an RMA phone to me, they gave me a choice of samsung focus (I asked how a windows phone was similar to an android?) or a samsung galaxcy II skyrocket...I'll try samsung next..
Thanks for all the help!
Click to expand...
Click to collapse
How do i close this thread? It's done, the phone is dead...rma...
NS4G
Will boot to fastboot and recovery
CWMR Touch 6.0.1.0
Situation:
My device started bootlooping after about a week of random restarts and freezes. I had just flashed BlackBean and now this, so I decided I was just going to flash a new ROM/Kernel combo. I remembered someone saying I should format /system to install the specific ROM, but I'm fairly sure I formatted /boot along with it, like an idiot. FYI - Fast Charge and a build.prop tweak to set permissions on boot was enabled when this happened. So then I try and flash a new ROM/Kernel combo to fix my bootloop and it wouldn't read the sdcard afterwards. Now it boots straight to fastboot everytime. Toolkit seems to be able to do some things via USB control like reboot the bootloader, but it does not detect an ADB device when I run the driver check or try to restore my CWM backup. I ran the stock+unroot option in Toolkit (was going to send it in thinking the sdcard thing was hardware at first) and it seemed to have went through the whole process correctly... Until the end when it did not reboot automatically like it should have. After doing this, I now get "STANDARD_SET_CONFIGURATION" on the phone when I insert the USB cord while in fastboot. It did not do this before, whether it is the new cord or the flash I do not know. My old cord WAS having problems with data though.
Problem:
I now have no USB debug or SDcard functionality. I assume because of missing files on /boot. I can mount nothing (except cache, but the PC doesn't recognize) without getting a "can't mount" error. This puts a serious dent in my novice ability to fix it. Anything in Toolkit that runs via ADB commands doesn't seem to work properly because it says the device is not in debug mode. PDAnet USB Drivers seemed to install without a hitch and device is recognized on my PC.
Errors:
When trying to mount ANYTHING except the cache while in CWM, I only get: "E:/ Can't mount /sdcard/".
If I try to mount USB storage I get: "E:/ Unable to write to ums lunfile (No such file or directory)Error mounting /sdcard!"
If I try to run any one click methods that use ADB I get: "Daemon not running* No ADB device detected. Make sure you have debugging enabled on your phone"
The log in CWM recovery always shows: "I: Set boot command "" failed to open /sys/class/android_usb/android0/state: No such file or directory" over and over (as many times as I tried to mount something while in recovery for that session)
Questions:
Do you think USB Fast Charge or having the build.prop tweaks enabled could have done something to USB debug? Is there a way to at least just fix the USB Debug problem? Am I correct in assuming that wiping the /system along with the /boot folder is what caused me to not be able to mount the /sdcard to flash another ROM? Is there a way to push the files I need onto the device to restore sdcard function and flash another zip?
Also, what fastboot do I need to be in to do the StockROM+Unroot method in the Toolkit? I have two. Only hold Vol Up/Power takes me to "FASTBOOT". Holding both Volumes+Power puts me into "FASTBOOT - NO BOOT OR RECOVERY IMG"
What is the difference?
I only ask because the Toolkit wants me to hold both volumes and up to get into bootloader mode, but they describe a big green "Start" with an android lying on it's back, mine does not look like that. It simply looks like regular fastboot, but says "FASTBOOT - NO BOOT OR RECOVERY IMG" instead.
It seems you messed with the ROM zip with some tool. Sorry could read your lengthy post completely.
I just want to know one thing clearly, what is the problem basically? where are you stuck?
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
DizturbedOne said:
Edit - Made it as concise as I could, hope it helps. Sorry for length.
Basically, the phone has a formatted /boot, /data, /sdcard, /system, dalvik cache, and I can't seem to use any of the flashing tools via Toolkit in Fastboot mode because the Toolkit says it "cannot find ADB device" please enable "debug" mode. Even when I run the driver check, it says ADB Device Not Found. Though I do have some control of the device via USB (I can use Toolkit to soft reboot from the bootloader) telling me my drivers are probably OK? I couldn't flash any ROM zips (or anything, even backups on the device) because I lost /sdcard functionality.
After a bunch of reading last night, it seems I want to Push a backup of /system and /boot onto the device, which should then restore USB functionality and allow me to flash a ROM... Right?
Click to expand...
Click to collapse
Your storage memory is completely inaccessible?
Yes, no way to access it via CWM. ADB stuff does not work either. It seems Fastboot stuff DOES. I would like to find a boot.img and system.img to flash via Toolkit (I believe toolkit uses fastboot or odin for these) to see if that would work for me. Any ideas?
It seems like the easy nature of unlocking, rooting, and customizing this phone leads to less of these kind of discussions, I can usually find many files and discussions pertaining to this for HTC phones, but never for this phone.
My bootloader version is KE1, but my baseband version is LF2, makes no sense to me.
The KE1 bootloader was when I was on ICS, but the LF2 baseband was from Jellybean... wth?
Do you think the time I flashed "stock+unroot" on the toolkit that it only partially took? (I did try to back it up to ICS because the Jellybean download didn't work). It seemed as if it flashed everything via fastboot, but never restarted at the end and still won't boot when done.
same problem kinda
i am having the same problem as this with my nexus. mine started after i downloaded Jellybean.it worked fine for about 1 month. i had changed nothing but when i would change my battery or restart my phone it would get stuck at the google screen every now and then, then it started more often. i could normally pull the battery and restart it and it would work after a couple of times doing that. but now this last time i tried that the phone wouldnt go past google screen at all. i can access my clockwork mods recovery but when i try to install zip from sd i get the error cant load sd i have tried everything i know and cant get nothing to work. please help. i miss my nexus this prevail is too slow and small...
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
polobunny said:
Your drivers don't seem to be installed properly.
Get that right, then you can reflash your recovery via fastboot, then you can mount your usb and transfer anything (rom kernel gapps etc etc)
Edit: oh and Bamamac82, that's not the same problem at all. Create a topic of your own.
Click to expand...
Click to collapse
@ polobunny - There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and manually reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such. I've tried it with PDAnet drivers and the Samsung drivers and have followed every driver install guide on the web... Any other suggestions on how to do this properly? I was even thinking of installing a Google SDK just to see if the drivers would work better...
@ Bamamac82 - Yes, that is pretty much the exact same problem, with the exception of the fact that you didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up. Not having a working USB cord at the time botched me, because I couldn't get my drivers reliably installed before anything happened, I was using AirDroid because my OEM cable wasn't working with data reliably.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
DizturbedOne said:
There is no way for me to install them more properly if I can't go into debug mode to install them though... I wiped out ALL drivers and reinstalled the drivers from PDAnet that had previously worked perfectly on my device. But now it never installs as Nexus S, only as Samsung ADB Interface or some such.
And Bamamac82 has the exact same problem, with the exception of the fact that he didn't wipe the /boot partition as I did. But yeah, I installed a JB ROM, it got a few random restarts, froze up twice, then one morning got stuck in a bootloop after I pulled the battery on a freeze up.
I totally thought the sdcard problem was because I formatted /boot in a hasty ROM flash though. Could I be wrong here?
Click to expand...
Click to collapse
When you're in fastboot mode on your phone, on your windows PC point the unknown device or the device with an exclamation/question mark to the path where the .inf for the drivers are located. If it still doesn't detect it, you can always try and force it to install a certain device (adb debug bridge or something of the sort).
Once that is done as I said you won't have any problem fastboot'ing to your phone and doing the other steps. Windows drivers and especially the adb drivers can be finnicky.
Your SDcard problem has nothing to do with the fact your formatted boot partition though, those are not linked.
Edit: Oh and I know there is some people, namely with NS4Gs, that had issues with the drivers. I believe for some reason there's some missing IDs in the inf making it impossible to install automatically. Forcing it should work though.
Polobunny thank you so much for your help so far. My device has been softbricked for a week and I'm using a HTC Hero for now! It's atrocious. I'm going to try as you said when I get home tonight and will update if fastboot allows me to flash after that.
Any idea where I can get all the .img's I need? I can only find the complete .tgz for IMM76D (which is fine for now just want it back to working state) and don't know how to extract .img's from it. Can't even find the complete .tgz for JRO03R though, the link is always down. At this point, all I want is a factory img to start from so I can upgrade to JRO03R, root it, and then make a fresh NAND backup from there.
If I were you, I would download Odin, a factory image from Google (just search nexus s factory image), the SDK tools (Google it) and would "reset" the phone.
You will easily find a guide for Odin. Then you'll just have to follow it and your nexus should be fine (but it will be factory reseted and you will have lost all your data )
Sent from my Nexus S using xda premium
Sorry guys, have been putting late hours in at work and haven't had much time until this weekend.
@BenHeng, that's what I am about to look into tonight. I didn't want to learn an entirely new aspect to restore this, I have been limited on free time and am starting to think it will be less hassle than dealing with this.
Only caveat to that, is that I definitely would like to know what happened to cause the SDCARD problem, because that was the main problem that got to me here, would like to prevent that from happening again.
ADB
Make sure ADB debuging is checked under Developer options
localpagefirst said:
Make sure ADB debuging is checked under Developer options
Click to expand...
Click to collapse
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Hi, I don't understand why you want to use ODIN, fastboot commands still don't work after you installed correctly your driver?
Anyway you can find all (new and old) originals google image here:
http://www.randomphantasmagoria.com/firmware/nexus-s/
Listen mate, the best way would be to flash the factory image via fastboot in bootloader mode. Follow this simple step to step guide.
If you have any issues. post them there on the blog post itself :good:
DizturbedOne said:
Please read the thread before replying.
@polobunny - I did a complete manual install of the RAW drivers, and got it to recognize properly as a Nexus S, as it did when USB Debug and everything worked correctly... But it still does not recognize it as an ADB device when running a driver check.
Is it safe to continue forward with a flash via ODIN in this state?
Click to expand...
Click to collapse
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
polobunny said:
Please, please don't use a shi**y 1-click package thing. There's no driver check to be done other than using adb and typing "adb devices". Do it manually and report the results. It should show your adb device ID, a long string of number and letters.
Click to expand...
Click to collapse
I get nothing when I do that. It says "List of devices attached" and a blank line underneath. When I plug the USB in during fastboot I get "STANDARD_SET_CONFIGURATION" at the bottom, which I never get until I install the drivers.
It seems as if the computer must recognize the device in debug mode in some way to properly install the drivers.
Why is my sdcard partition unable to be written to? This never would have been a problem as I always keep a couple backup ROM's on the phone. Either way, it seems as if all of this is for nothing if the phone will not allow me to read/write to the memory in the device.
I'm still somewhat new to all this but after buying my tf700 last December I've been trying out a few things, unlocked/rooted and I have been happily using TWRP and various versions of Cromi X for months without any problem. Suddenly one day it didn't want to boot the ROM anymore and I have no idea the cuase (didn't just flash some kernel or drop the tablet, etc). I have TWRP 2.5.0.0 and CROMI-X 5.0.2.
I've dug through the forums and there doesn't seem to be anyone I can find who's having exactly the same problems. There was no special data I particuarlly needed on the tablet and I have backups on saved elsewhere so I am totally happy to wipe everything and start from scratch. I just want my tablet back. I'm just looking for the easist way to fix this (and I hope there is a way!) so any help is greatly appreciated.
Info is as follows:
Cromi x won't load stuck on ASUS logo. Same goes for cold booting
When I boot into recovery it says "Key driver not found.. Booting OS" at the top left
[when I enter TWRP it asks for password and says it can't mount E as below
when i "cancel" the password request i am taken to the usual home screen but installing from internal storage shows no files and a size of "0"
strangely I can get into the Micro SD card and load CROMI X from there which all goes through normally but at the finish when I'm going to reboot it says "No OS Installed!" and after restarting i'm back to same problem
I'm not getting the Fastboot USB logo I think I'm supposed to get in recovery when it is plugged it into my PC and ADB sideload in TWRP also not working (not so experienced with these though)
When I try to wipe data in TWRP I get "Failed" the message about being unable to mount E below
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Unable to find partition size for '/data'
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
strangestribu said:
E: Unable to mount '/system'
E: Unable to mount '/cache'
Click to expand...
Click to collapse
Looks like some issue with the internal eMMC. Reboot your tablet into TWRP, connect it to your PC and run on the PC:
Code:
adb shell dmesg > dmesg.txt
adb shell ls -l /dev/block/mmc* > mmc.txt
Post the 2 resulting files.
can't seem to connect through PC
_that said:
Looks like some issue with the internal eMMC. Reboot your tablet into TWRP, connect it to your PC and run on the PC:
Code:
adb shell dmesg > dmesg.txt
adb shell ls -l /dev/block/mmc* > mmc.txt
Post the 2 resulting files.
Click to expand...
Click to collapse
Thanks very much for this. The problem I am having is I can't past the "error: device not found" message I get in the CMD on my (windows 7) PC. (yes I am opening the command line window on my android ADB folder). In fact the tablet doesn't appear in the Device Manager either. I'll admit I'm not so experienced working on the tablet through the PC (though I'm guessing I'm about to learn a lot), but I think the fact I get "Failed" when trying to ADB sideload in TWRP and nothing in the Device Manager is a big part of my problem though I'm stumped how to fix it.
Any ideas?
strangestribu said:
In fact the tablet doesn't appear in the Device Manager either.
Click to expand...
Click to collapse
You may not have the correct drivers, but even then it should at least appear as unknown device.
I don't know which drivers you need for Windows (it's easier under Linux) but maybe someone else can help you here. I remember sbdags once posted which drivers worked for him, maybe you find it using the search function.
Try these drivers:
PC doesn't recognize tablet is plugged in
sbdags said:
Try these drivers:
Click to expand...
Click to collapse
_that said:
You may not have the correct drivers, but even then it should at least appear as unknown device.
I don't know which drivers you need for Windows (it's easier under Linux) but maybe someone else can help you here. I remember sbdags once posted which drivers worked for him, maybe you find it using the search function.
Click to expand...
Click to collapse
Thanks both for this, but the problem that I'm facing is I can't seem to get my PC to recognize the existence of the tablet (connected via USB with TWRP running) even as an unknown device. Because of this I'm not sure how to get the drivers loaded. Also have loaded Android SDK Build-Tools and Google USB Driver through the Android SDK Manager. That doesn't seem to solve it either.
Not surprisingly when I run fastboot from a cmd line window and look for adb devices the list is blank.
Not sure what else to do. Would be willing to create a second Ubuntu boot on my machine if using linux would help me get this fixed. Just at a loss about what to do.
Any further insights are welcome!!!
strangestribu said:
Thanks both for this, but the problem that I'm facing is I can't seem to get my PC to recognize the existence of the tablet (connected via USB with TWRP running) even as an unknown device.
Click to expand...
Click to collapse
Is the tablet connected directly to the PC? No dock, no USB hub?
To check if your USB cable works, you can boot your tablet into APX mode (hold volume-up while turning on). The screen will stay black but the backlight should be on. You can only do something useful in this mode if you have previously created your blob file for wheelie/nvflash, but at least your PC should recognize the Tegra APX device (vendor 0x0955, device 0x7030).
If that also doesn't work, boot any live Linux distribution and run "lsusb". If that also shows no trace of the tablet (vendor ID should be 0b05 for normal operation or recovery, or 0955 for APX mode), then either your cable or your tablet's USB connection is broken.
Am I bricked?
_that said:
Is the tablet connected directly to the PC? No dock, no USB hub?
To check if your USB cable works, you can boot your tablet into APX mode (hold volume-up while turning on). The screen will stay black but the backlight should be on. You can only do something useful in this mode if you have previously created your blob file for wheelie/nvflash, but at least your PC should recognize the Tegra APX device (vendor 0x0955, device 0x7030).
If that also doesn't work, boot any live Linux distribution and run "lsusb". If that also shows no trace of the tablet (vendor ID should be 0b05 for normal operation or recovery, or 0955 for APX mode), then either your cable or your tablet's USB connection is broken.
Click to expand...
Click to collapse
Well you gave some great advice...I hadn't thought that the cable (which charges the tablet perfectly) could be the issue. I borrowed a cable from a friend who has the same machine and voila, recognized and could get into fastboot.
...and then with that problem solved, things got really bad.
I attempted to reflash TWRP on the tablet by pushing via fastboot as described on TeamWin's website. All was going perfectly until the tablet froze partway through the flash. Now when i power on, whether or not I hold vol down, I get a brief .5 seconds of the "Asus Inspiring innovation..." logo with a blue bar that goes up to about 75%, with "The device is unlocked" in the corner. After this brief 1/2 second it goes directly into APX -- black screen (though possibly back-lit) but, with the working Asus cable, Windows 7 recognizes the tablet as "Unknown Device"
I fear the device is now bricked as all the forums I've read seem to imply this. No, I didn't really know about creating a blob file for wheelie/nvflash before so don't have one (sure have read plenty about it now).
So...is this the end? Can I create a working blob file from my friend's device (I'm guessing not or it would have been thought of before)? or any other solution?
Or if not I've heard you can replace the motherboard though this is really unknown territory for me...I'm a bit curious so would be up for having a go but don't want to sink money into a helpless situation. Plus I don't know why any of this has happened in the first place so i fear there may be other parts that are not working properly.
Any useful insights on how to solve this problem I've created for myself would be greatly appreciated.
Sounds like it is bricked if you can't get into the bootloader.
What was the exact command you used to 'push' TWRP and which file did you use?
strangestribu said:
Well you gave some great advice...I hadn't thought that the cable (which charges the tablet perfectly) could be the issue. I borrowed a cable from a friend who has the same machine and voila, recognized and could get into fastboot.
...and then with that problem solved, things got really bad.
I attempted to reflash TWRP on the tablet by pushing via fastboot as described on TeamWin's website. All was going perfectly until the tablet froze partway through the flash. Now when i power on, whether or not I hold vol down, I get a brief .5 seconds of the "Asus Inspiring innovation..." logo with a blue bar that goes up to about 75%, with "The device is unlocked" in the corner. After this brief 1/2 second it goes directly into APX -- black screen (though possibly back-lit) but, with the working Asus cable, Windows 7 recognizes the tablet as "Unknown Device"
I fear the device is now bricked as all the forums I've read seem to imply this. No, I didn't really know about creating a blob file for wheelie/nvflash before so don't have one (sure have read plenty about it now).
So...is this the end? Can I create a working blob file from my friend's device (I'm guessing not or it would have been thought of before)? or any other solution?
Or if not I've heard you can replace the motherboard though this is really unknown territory for me...I'm a bit curious so would be up for having a go but don't want to sink money into a helpless situation. Plus I don't know why any of this has happened in the first place so i fear there may be other parts that are not working properly.
Any useful insights on how to solve this problem I've created for myself would be greatly appreciated.
Click to expand...
Click to collapse
If you cannot get into the bootloader and APX mode is your only access .... without nvFlash - sorry, it's a brick :crying:
The blobs for nvFlash are device specific, so somebody elses would not help you.
Your only option is to sell it for parts or have the main board replaced.
I don't have experience with that (thank God), but there are tear-down videos and instructions on iFixit.com. Maybe that'll help you decide if it would be something you can do yourself.
Otherwise sending it to Asus and have them fix it would be your only option. It is expensive....
My condolences....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
TF300T help
I've worked on this now for about 12 hours. I cannot figure it out. I run into the same roadblocks. I know this is an old thread, hopefully by now there's a solution for this kind of issue.
Can this be fixed in Odin or platform tools or something?
I've got TF300T where I believe I bungled the process by format/wiping from bootloader menu instead of TWRP. It's technically not bricked at all. But it's screwed up in the following ways (I was trying to get it to be a Clean Rom tablet, and there were so many sets of instructions, had them all open, and was trying to be careful about this, I've rooted and ROMed so many times and this is the first time I haven't been able to solve the issue in a reasonable amount of time)
-TWRP 2.5.0.0 asks for password, no pw ever set anywhere, tried all possibles that could feasibly be, but nothing works. This TWRP issue causes all cards to be invisible, it wiped by external SD, shows internal SD as having nothing in it but this is false as the OS boots ok (see below).
-cold boot or reboot leads to going straight into TWRP 2.5.0.0
-issuing command 'adb reboot bootloader' while in TWRP does take me into (bootloader?) 3 iconed menu, this menu is the only way I can boot the tablet into the normal Android system
-cannot factory restore the tablet from normal Android as it goes straight into TWRP following this action
-in the bootloader 3 iconed screen it is not seen by issuing that 'devices' command,
-thus cannot do 'fastboot -i 0x0b05 flash staging blob', TWRP disallows this also as the damn thing is locked down by a non-existent password.
I issued your commands:
DMESG.TXT (output too long to post here, exceeds xda allowable) &
MMC.TXT
brw------- 1 root root 179, 0 Jul 12 00:32 /dev/block/mmcblk0
brw------- 1 root root 179, 1 Jul 12 00:32 /dev/block/mmcblk0p1
Without a working fastboot connection you are one or two steps away from a hard brick. Proceed with caution!
chickenmusket said:
Can this be fixed in Odin or platform tools or something?
Click to expand...
Click to collapse
Odin is for Samsung devices only, the platform tools give you adb and fastboot, see below
TWRP 2.5.0.0 asks for password, no pw ever set anywhere, tried all possibles that could feasibly be, but nothing works. This TWRP issue causes all cards to be invisible, it wiped by external SD, shows internal SD as having nothing in it but this is false as the OS boots ok (see below).
Click to expand...
Click to collapse
Usually the reason if TWRP is asking for a password is a corrupted data partition. The recovery cannot read /data, so it assumes that it's encrypted and it asks for the password. Surprising is that you can boot into Android if your data partition is corrupted!!
-cold boot or reboot leads to going straight into TWRP 2.5.0.0
-issuing command 'adb reboot bootloader' while in TWRP does take me into (bootloader?) 3 iconed menu, this menu is the only way I can boot the tablet into the normal Android system
Click to expand...
Click to collapse
That's what stumps me... Most of the time, if you use the "Wipe Data" option in the bootloader or do a factory reset from within the stock rom with TWRP installed, you end up in a forced reboot to recovery loop - no boot to rom, no boot into the bootloader. So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom??
cannot factory restore the tablet from normal Android as it goes straight into TWRP following this action
Click to expand...
Click to collapse
That's totally normal because the factory reset command calls the recovery to perform a wipe of data. Since you don't have the stock recovery it calls TWRP - but TWRP cannot resolve the command. Read this for background, but you probably don't need bootit.ko since you can boot into the bootloader anyway.. http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
in the bootloader 3 iconed screen it is not seen by issuing that 'devices' command,
-thus cannot do 'fastboot -i 0x0b05 flash staging blob', TWRP disallows this also as the damn thing is locked down by a non-existent password.
Click to expand...
Click to collapse
This is the part that worries me. Without a fastboot connection you could be dead in the water pretty quickly. And that's the problem you should tackle first.
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem. Read this to get fastboot working:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
And again - if that goes wrong and you don't have fastboot working, you could end up with a paperweight. Be careful!
Thanks for taking the time to answer. Understanding more of this is helpful (doesn't drive me as mad when I know that I don't need to keep trying passwords in TWRP). I'd like to be in a position where I knew knew all this stuff & could be helping others instead.
I thought the reason for all the lock ups was my wiping data from the 3 iconed menu rather than from twrp (the latter was supposed to do)
YES >>>So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom?? >>>YES
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem.
>>I got TWRP into the tablet by issuing this command
fastboot -i 0x0b05 flash recovery twrp.blob
>>Tablet is already unlocked via the Asus way. Am I supposed to go through a procedure to re-do fastboot somehow?
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
>>Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
and when I boot into this OS,
>>Android version 4.2.1
Kernel 3.1.10-g215ae8bf / [email protected]#1
Build: JOP40D.US_epad-10.6.1.27.5-20130902
Pad EC version PAD-EC20T-0216 (too much info?)
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
>>Cannot format data in TWRP, after entering yes to confirm
E: unable to find partition size for '/misc'
E: ...a bunch of unable to finds, unable to mount, unable to wipe, unable to cache
everything unable to ...
I had tried that already.
Do you think I should try this:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page7
chickenmusket said:
Thanks for taking the time to answer. Understanding more of this is helpful (doesn't drive me as mad when I know that I don't need to keep trying passwords in TWRP). I'd like to be in a position where I knew knew all this stuff & could be helping others instead.
Click to expand...
Click to collapse
Stick around enough long enough, read a ton and you will be
I thought the reason for all the lock ups was my wiping data from the 3 iconed menu rather than from twrp (the latter was supposed to do)
Click to expand...
Click to collapse
It probably was. Although with a different effect than usual...
YES >>>So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom?? >>>YES
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem.
>>I got TWRP into the tablet by issuing this command
fastboot -i 0x0b05 flash recovery twrp.blob
>>Tablet is already unlocked via the Asus way. Am I supposed to go through a procedure to re-do fastboot somehow?
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
>>Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
and when I boot into this OS,
>>Android version 4.2.1
Kernel 3.1.10-g215ae8bf / [email protected]#1
Build: JOP40D.US_epad-10.6.1.27.5-20130902
Pad EC version PAD-EC20T-0216 (too much info?)
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
>>Cannot format data in TWRP, after entering yes to confirm
E: unable to find partition size for '/misc'
E: ...a bunch of unable to finds, unable to mount, unable to wipe, unable to cache
everything unable to ...
I had tried that already.
Do you think I should try this:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page7
Click to expand...
Click to collapse
Yes. That would be the safest way to go, but you need fastboot for it. I thought you don't get the device ID returned when issuing 'fastboot devices' while in the bootloader??
As long as you can boot into the BL you don't need bootit.ko so follow that guide from the "fastboot devices" input
Correct, I do not have a fastboot ID.
chickenmusket said:
Correct, I do not have a fastboot ID.
Click to expand...
Click to collapse
That's what i mean: Probably a driver problem. Open Device Manager on the PC. then connect/disconnect the tablet while in the bootloader. Check if anything changes, check for yellow triangle next to the driver if it shows as Fastboot interface.
You can also try this in adb shell in recovery since you do have that working. This will also format your data partition:
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
The issue was resolved with the help of Joshua Lynch. He saw my post and PMed me. For those that are losing hope like I was, if you're coming back to this old tablet, all is not lost. I will post how this resolved as soon as I have time. Thanks for the answers. Bounty has been claimed.
the issue was a driver. the computer would only have one driver installed at a time and installing fastboot driver again fixed the not seen issue. I had installed another driver (as part of this process, and it eliminated the presence of fastboot driver), and was racking my brains because I didn't think to reinstall the original fastboot driver.
I had help from Joshua Lynch a couple months back on this. It turns out that the reason the tablet wasn't seen was indeed a driver issue. What had confused it with me is that I did physically install both drivers fastboot & adb. However, my system only allowed one to be active at a time. So when I was trying to, if I'm remembering this correctly, fastboot into the tablet to console, it wasn't seen because adb was the active driver. All that needed to be done was remove adb & put in fastboot.
Just to let you all know, I did a full one & zero wipe of the tablet & installed Zombi-Pop rom with Joshua's help. The tablet was still slower than hell. Slower than any device I've ever used. I'm talking 5 to 15 second delay time from when touching something & getting a response. I found that disabling everything google (except play store & play services) helped a great deal.
But the tablet has never returned to its former speed prior to the asus update. Tinfoil hat: I have this feeling that they sent out an update that permanently screwed up the hardware on purpose.
berndblb said:
That's what i mean: Probably a driver problem. Open Device Manager on the PC. then connect/disconnect the tablet while in the bootloader. Check if anything changes, check for yellow triangle next to the driver if it shows as Fastboot interface.
You can also try this in adb shell in recovery since you do have that working. This will also format your data partition:
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
Click to expand...
Click to collapse
Question: do you know if the original stock software that the tablet came with (before the update) can be installed? Is there a full set of instruction on this (and the stock rom)? I've got a ton of files (some roms, some files from asus website) downloaded for this tablet. I've taken a break from this thing, returning to it now... Ready to take another crack at it.
If someone wants to make some money and help me out with this, I'll pay them a total of 50 if all goes well. First 20 for their service to get the thing back on stock, original out of box software and updates disabled, another 30 when I've seen after a few days, that indeed it was done right and fast like it originally was.
Reason for this is that I already gave someone 50 for their help with this and the outcome wasn't acceptable. I've invested a ton of time in this and the $$ put in so far exceeds the value of the tablet.