Database Info

[Q] - Nexus S 4G Unable to boot past Google logo and CWM can't mount /sdcard

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?

[Q] Moto g custom recovery not working

Hello Everyone,
My moto g phone suddenly started giving errors saying "unfortunately "xxxxx" not working. xxxx is like google play and many more system services. I cannot do anything as it gives the error continuously.
I was trying to factory reset the mobile and I got the error of "boot up failed". I searched for this and found out that I need to go for custom recovery(I'm new to this) to avoid this error and get my phone back to normal.
I found that I need to unlock boot loader to for custom recovery. After trying and searching a lot I managed to do that finally with the help of a thread in this forum.
From that time I tried with many img files like TWRP, CWM and philz. But, still I could not manage to get my phone back to work.
Last 3 days I was fully in to this searching and finding solution and finally thought to write here(I'm not feeling to give up on this). I can provide you with any information needed.
I read in some guidance of CWM recovery that I need to get CWM model to process further after the below command.
Code:
fastboot flash recovery recoveryimage.img
Instead my screen stays with the below content for whatever .img file I pass for the above command
"Android system recovery <3e>
LXB22. 46-28. 1"
Appreciate any help or support on this to get my phone back to work. Thanks in advance

Nazneen said:
Hello Everyone,
My moto g phone suddenly started giving errors saying "unfortunately "xxxxx" not working. xxxx is like google play and many more system services. I cannot do anything as it gives the error continuously.
I was trying to factory reset the mobile and I got the error of "boot up failed". I searched for this and found out that I need to go for custom recovery(I'm new to this) to avoid this error and get my phone back to normal.
I found that I need to unlock boot loader to for custom recovery. After trying and searching a lot I managed to do that finally with the help of a thread in this forum.
From that time I tried with many img files like TWRP, CWM and philz. But, still I could not manage to get my phone back to work.
Last 3 days I was fully in to this searching and finding solution and finally thought to write here(I'm not feeling to give up on this). I can provide you with any information needed.
I read in some guidance of CWM recovery that I need to get CWM model to process further after the below command.
Code:
fastboot flash recovery recoveryimage.img
Instead my screen stays with the below content for whatever .img file I pass for the above command
"Android system recovery
LXB22. 46-28. 1"
Appreciate any help or support on this to get my phone back to work. Thanks in advance
Click to expand...
Click to collapse
Rename the twrp or cwrecovery as recovery and copy to adb folder. Fastboot command is
fastboot flash recovery recovery.img, (not fastboot flash recovery recovery image .img)

pradeeppk said:
Rename the twrp or cwrecovery as recovery and copy to adb folder. Fastboot command is
fastboot flash recovery recovery.img, (not fastboot flash recovery recovery image .img)
Click to expand...
Click to collapse
it is not "recoveryimage". I just used it for this question. I tried with many files. So, I gave the name of the file and used the command and I got the success message also in CLI saying "Okay" and finished. But no file made any difference to device.
I had a pass code to unlock my screen. Two times I was able to get the screen (Other times it become dark after loading M) and it required the authentication code I gave to enter unlock screen. and I was filled with errors showing continuously "unfortunately not loaded 'system files' ". I suspect that whether the flash worked properly because it was asking for the screen unlock code.

nexus 5 softbrick

Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)

You must use fastboot commands while being into the bootloader, not adb.

mworley1991 said:
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Click to expand...
Click to collapse
Yeah, exactly what primokorn says...
Primokorn said:
You must use fastboot commands while being into the bootloader, not adb.
Click to expand...
Click to collapse
If you use the command "fastboot devices" and your phone with a code appears in the command prompt then there's no problem with your drivers.
Just reflash the factory image, you can use the automatic process if you run "flash all". You can also flash the images manually but if you go for that option make sure you don't forget to flash the cache image, that will fix your problem with mounting the cache partition.

ADB commands are used when the phone is booted into the ROM.
Flash the latest stock ROM from here to see if it solves the issue: https://developers.google.com/android/nexus/images
If the phone still bootloops, flash the userdata.img in fastboot. After flashing the userdata.img file in fastboot, boot directly into stock recovery using the power/volume buttons, perform a factory wipe, and reboot.

Can't go after twrp

Hi,
I have a problem with my r7plusf.
I tried to install lineageOs, with the CM recovery I just got a "zip signature verification" problem. To avoid this problem i flashed TWRP and tried installing it without checking the zip signature. When doing that i got a "table error".
I try to reflash back the rom I had and now I am in trouble :
when i flash it it boots on TWRP instead of the rom.
I tried installing the colorOs recovery and it did not work (I just saw a message telling me "formating data and cache")
/*And now twrp is always telling me "can't mount /data".*/
I resolved this problem by formating the data partition
Does anyone know what i can do to reuse my phone?
Thank you by advance for all the help you could give me.

Little update :
I tried to build lineageOS by hand with this link : https://wiki.lineageos.org/r7plus_build.html to see if there was the cyanogenmod/lineage recovery included but when I try to brunch, I just get this error :
Code:
"ninja: error: '/home/user/android/system/out/target/product/r7plus/obj_arm/SHARED_LIBRARIES/libtime_genoff_intermediates/export_includes', needed by '/home/user/android/system/out/target/product/r7plus/obj_arm/SHARED_LIBRARIES/libandroid_servers_intermediates/import_includes', missing and no known rule to make it"
After looking at the files I just saw that the folder named "obj_arm" does not exists. For info Iam on archlinux whith linux kernel version 4.9.6-1 and I have GCC 6.3.1 .
Does anyone know how to solve this bug or has anyone got the cyanogenmod recovery?
UPDATE : I tried with the cyanogenmod recovery that someone gave to me and it didn't work either, the phone still boots on the recovery. I don't have anymore ideas anymore

Some one oppo forum just gave me the way to save my phone, i just had to boot in fastboot mode, plug the phone in my computer, open a command prompt and type the command "fastboot continue", everything just work fine now.

f22217 said:
Some one oppo forum just gave me the way to save my phone, i just had to boot in fastboot mode, plug the phone in my computer, open a command prompt and type the command "fastboot continue", everything just work fine now.
Click to expand...
Click to collapse
That just helped med A LOT

Phone boots into fastboot, system files corrupted

Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?

Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.

Both failed. I attached the errors I recieved.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com

I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.

crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/

It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.

Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?

Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.

That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .

crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!