Related
I have a Sprint Nexus S 4G that I keep in Airplane mode most of the time and rarely use (an hour a week at most, usually). I use it so rarely that it shuts off due to low battery a lot.
The last time it shut off, I wasn't able to boot it up when I turned it back on. It got stuck at the Google logo indefinitely with the bottom buttons lit up. I can boot to CWM Recovery (v6.0.1.9) but when I do, I get the log message "Error mounting /sdcard!" or "E:Can't mount /sdcard/" when I try to search for an update.zip on the phone, or try to mount or format /sdcard. I tried using the "adb sideload" command to install a ROM from CWM, which fails with:
E:Error in /tmp/update.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
I also tried using "adb push cm-10.1.2-crespo4g.zip /sdcard/", which does not fail with any errors but still am unable to mount /sdcard/ through CWM so that obviously isn't any help for me.
I can boot into fastboot and tried flashing back to stock with these commands using the image files from this thread.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash radio radio.img
fastboot erase cache
fastboot reboot
When I flashed using the commands above, I got no errors in the terminal but my phone still would not boot past the Google logo. Afterwards I was able to flash CWM Recovery back onto the phone with no problems but CWM still can't see the /sdcard partition.
I also tried all of the suggestions on this thread with no success.
Nexus S stuck on google boot logo
For an even crazier attempt at a solution, I found a person with a similar problem to mine where they ran a hair dryer over the phone for a few minutes to fix it. That didn't help, either.
I think my nexus died
At this point I'm out of ideas and was hoping someone else might know something I could try. I planned on getting a new phone soon anyway but was hoping to be able to use my old phone for a little while until that happens.
You've tried all sorts of things to recover the SD card portion. Which I think is badly corrupted.
I think your internal memory card has died. I suggest going for a new phone.
One last effort will be to install a different recovery and try formatting the SD card from there. Try Philz Touch or TWRP.
Sent from my Nexus S using Tapatalk 4
danherbert said:
I have a Sprint Nexus S 4G that I keep in Airplane mode most of the time and rarely use (an hour a week at most, usually). I use it so rarely that it shuts off due to low battery a lot.
The last time it shut off, I wasn't able to boot it up when I turned it back on. It got stuck at the Google logo indefinitely with the bottom buttons lit up. I can boot to CWM Recovery (v6.0.1.9) but when I do, I get the log message "Error mounting /sdcard!" or "E:Can't mount /sdcard/" when I try to search for an update.zip on the phone, or try to mount or format /sdcard. I tried using the "adb sideload" command to install a ROM from CWM, which fails with:
I also tried using "adb push cm-10.1.2-crespo4g.zip /sdcard/", which does not fail with any errors but still am unable to mount /sdcard/ through CWM so that obviously isn't any help for me.
I can boot into fastboot and tried flashing back to stock with these commands using the image files from this thread.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash radio radio.img
fastboot erase cache
fastboot reboot
When I flashed using the commands above, I got no errors in the terminal but my phone still would not boot past the Google logo. Afterwards I was able to flash CWM Recovery back onto the phone with no problems but CWM still can't see the /sdcard partition.
I also tried all of the suggestions on this thread with no success.
Nexus S stuck on google boot logo
For an even crazier attempt at a solution, I found a person with a similar problem to mine where they ran a hair dryer over the phone for a few minutes to fix it. That didn't help, either.
I think my nexus died
At this point I'm out of ideas and was hoping someone else might know something I could try. I planned on getting a new phone soon anyway but was hoping to be able to use my old phone for a little while until that happens.
Click to expand...
Click to collapse
I am also having the same situation. OP, were you able to resolve this issue?
Hi everyone, this is the first time i write here. I've been dealing with this problem for some hours now and it seems i can't get out of it alone.
Today i decided to wipe the N5 and install Lollipop. I downloaded the factory image, wiped everything from TWRP (i know it was unnecessary...), started to flash all the stuff from ADB...but i got some error. I tried again, and got the same error again. So i started to mess around...a guide told me to give adb the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I think it was after this that ADB stopped recognizing my phone, and now i can't even get to the recovery. I tried uninstalling and reinstalling sdk and google usb drivers plenty of times, i even tried some alternative solutions like LGUnitedMobileDriver and Universal Naked Driver.
I can see that windows sees the device (which now only works in fastboot mode) from Device Manager, and that ADB is working (if i give the command "adb version" it responds correctly), but there's no way to make adb recognize the Nexus. If i just install the drivers, Device Manager shows it as "Android Bootloader Interface". A guide i found says to manually select "Android ADB Interface" or "Android Composite ADB Interface", and so i have done (i have to untick the "show compatible hardware" box in the installation process to see this options), but no luck.
Does anybody have any idea how to solve this? What may i have missed?
You need fastboot commands to flash images in recovery. ADB will only recognize the device when you have android running
Try "fastboot devices" command without quotes. It should detect your phone and return a serial number. If so, flash the images (see the sticky on how to return to stock and follow the method 2)
Adb and fastboot are two different things. ASB works in android or recovery but is not used for flashing. Fastboot works in bootloader.
I wrote an "adb and fastboot" thread. Use it uninstall your Google drivers and install naked.
Omg, it was that simple! Thank you guys, you were so fast :good:
If you downloaded the factory image, it seems like you just need to flash that with fastboot.
1). Reboot into the boot loader by holding down volume when powering on.
2). Type fastboot devices to make sure your phone is recognized.
3). Untar the image and execute the flash-all.bat script. This will completely factory reset your phone, including stock recovery. Note this will also delete your internal storage files.
If you don't like this approach, you can also flash the recovery partition with fastboot flash recovery recovery.img, where recovery.img is the TWRP image you downloaded. Once you boot into recovery you can restore a nandroid or whatever from there. Good luck.
Sent from my Nexus 5 using Tapatalk
Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.
I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.
Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me
First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!
i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester
did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.
Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.
I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.
rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.
Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help
Moto G XT1032
Hello,
I hope that you understand my English. I am kind of a layman concerning Android, but still wanted to install Cyanogenmod 13. I followed these instructions (can't post them apparently since I am new). Official instructions on the CM website. (Bootloader was already unlocked because I already installed Cyanogenmod 12, went back to Stock ROM and now tried to install CM13). Like alwas there were some minor errors during the first steps, but I handled them alright, I think.
The real problem started when I tried to install the zip-file of CM13 ("Installing CyanogenMod from recovery", step 8). I followed the instructions (wipe etc.), but the installation stopped at "Patching system image unconditionally" and it said something like "missing md5-file" although the file I downloaded on the TWRP website was right next to the recovery .img.
After trying and trying I started to go through the options in TWRP recovery (which was a fault, I know) and wiped some things that probably should not have been wiped. Next error message was: "unable to mount /system". New problem.
Then I thought, I might try the recovery that was right next to the downloadlink of the CM13 firmware. Installed it succesfully and tried again some things, now I have a bootloop and can't shut off the phone. When I shut it off, 1 second later the Google-screen with the open lock appears again". The only help was to manually shut it off with recovery.
I can't even start Android anymore, which means I can't activate USB-debugging, the installation files of CM13 are missing and the main problem: my PC only recognizes the phone in fast boot mode - I can't move files to the phone, it just says in the task bar: "Fastboot falcon S".
As soon as I enter recovery mode, the USB-sign on Windows vanishes.
Tried to move the files to the devices by "adb push cm-13.0-20160703-NIGHTLY-falcon.zip /scard", but it says "* daemon not running. starting it now on port 5037 *
* daemon startet successfully *
adb: error: connect failed: no devices/emulators found"
The device is not recognized by "fastboot devices" in cmd.
I hope that you understood everything. Already tried to get help in German forums, but nobody answered there.
And yeah, I definitely stopped trying to solve it by myself because I might just destroy it more.
Thanks for your help!
seems like we are on the same trolley.
I wanted to have a 100% clean system so I wiped everything.
I reinstall SDK, google drivers, motorola drivers, but no success. In fastboot mode it's written: USB connected, on the computer eject "Fastboot falcon S". I create file adb_usb.ini with id in it, restarted system, killed adb and so on. Tried different USB port, different cables.
Aendroit, if you find a way share.
I'm on W10 if that matters.
Ok. So I managed to go through the problem.
First, I was able to reinstall TWRP with fastboot (fastboot root twrp.....), so fastboot worked for me. Then it seems that on the main screen, where you choose options with volume buttons, fastboot works, but not adb.
I went into recovery and "adb shell" worked, so did "adb devices".
I used push command and so on.
I'm glad you got the solution now. Unfortunately I can't follow the instructions. Could you please take me through it step by step ("fastboot root twrp", I never used a command like this before). Thanks!
Because when I go in recovery and type in "adb shell" or "adb shell" on my computer, it says "no devices/emulators found".
Update: Got it. I can enter TWRP now, but in the installation log it said "Mismatched partition size (recovery)" at the end. If someone knows what that means ...
I meant: fastboot flash recovery twrp-3.0.0.0_2-falcon.img
Mismatched size is just an information, nothing to worry about. Now, when you are in TWRP try to check the device "adb devices", should work.
Thank you, my computer recognizes the device again! I was able to copy the files to my phone. Unfortunately I still can't install a custom rom. I tried Mokee instead of CM13 now and i always get the same messages:
"Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 146758281
Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and so on.
I don't know what that is supposed to mean ...
Well, I'm not very good oriented in all this stuff, so I don't know why you got those problems, far from being a dev.
I copied ressurection ROM + open gapps nano (thou I always used banks, but this time wanted to save more free space) and installed it via TWRP without any issues.
Thank you for the answer. Mokee works now! I'm not happy that I can't use CM13, but I got Mokee working after a while and I'm glad about it.