[Q] Android system recovery 3 - HELP - Galaxy S 4 Q&A, Help & Troubleshooting

Hey guys,
**picture attached of my screen***
I'm new to this forum and consider myself a newb in need of quick advice.
This morning i restarted my Samsung galaxy s4 (model: SGH-M919V) and now all it does is goes on the Android System recovery 3 screen, where i see:
Top of the screen:
Android System recovery 3.
kot49h.m919vlufn1
And I have 6 options:
Reboot system now
Apply update from ADb
Apply update from external storage
Wipe data/factory reset
wipe cache partition
apply update from cache
I tried Reboot system now and it closes the phone and starts it right back to the same screen (Android system recovery 3)
*On this screen, there is a Android drone laying sideways and it's written under 'No command'.
I really want to be able to use the phone and specially not lose my contacts, pictures and all.
Can someone PLEASE HELP!!!
(IMPORTANT: My volume key higher is broken but lower works fine. It's been like that over a month)

qcmobile said:
Hey guys,
**picture attached of my screen***
I'm new to this forum and consider myself a newb in need of quick advice.
This morning i restarted my Samsung galaxy s4 (model: SGH-M919V) and now all it does is goes on the Android System recovery 3 screen, where i see:
Top of the screen:
Android System recovery 3.
kot49h.m919vlufn1
And I have 6 options:
Reboot system now
Apply update from ADb
Apply update from external storage
Wipe data/factory reset
wipe cache partition
apply update from cache
I tried Reboot system now and it closes the phone and starts it right back to the same screen (Android system recovery 3)
*On this screen, there is a Android drone laying sideways and it's written under 'No command'.
I really want to be able to use the phone and specially not lose my contacts, pictures and all.
Can someone PLEASE HELP!!!
(IMPORTANT: My volume key higher is broken but lower works fine. It's been like that over a month)
Click to expand...
Click to collapse
Hi ,
Just in case check all the key and make sure none is push in making some strange combination
If not you do not have many options , try first
wipe cache partition ( you will not lose any data)
If does not work next step would be
Factory reset ( you will lose your data)
If does not work you will have to do some flashing.....

MAX 404 said:
Hi ,
Just in case check all the key and make sure none is push in making some strange combination
If not you do not have many options , try first
wipe cache partition ( you will not lose any data)
If does not work next step would be
Factory reset ( you will lose your data)
If does not work you will have to do some flashing.....
Click to expand...
Click to collapse
I did try the Wype cache partition but same results.
Is there a way to make a backup before resetting the phone?
With Kies or Odin?

qcmobile said:
I did try the Wype cache partition but same results.
Is there a way to make a backup before resetting the phone?
With Kies or Odin?
Click to expand...
Click to collapse
Not that i know....sorry
Did you check the key, just in case they are stuck?

Related

Phone Won't Boot I9000M Bell

Hey I've got JH2, rooted and OCLF. It's been working great for a month. Last night I pulled the phone out of my pocket and it was off. I turned it back on and check again in 15 minutes, it was off again. Third time it stayed on all night just fine.
Today I tried to go into the Android Market and it kept force closing so I tried to restart the phone, not it just gets to the "S" on loading and hangs there for a while and then the screen goes back and the two bottom buttons stay lite.
I got into recovery mode and wiped the cache but it still won't restart. I did not to the wipe data/factory reset yet. Should I do that next? Will I lose everything?
I just did the factory reset and it's running again.
glad you got it resolved
hello i am having the same problem tried data /factory reset but it is still doing the same thing... i get an error when entering recovery mode
"E:Can't mount /dev/block/mmcb1k0p1
(NO such file or directory)
E:copy_dbdate_media:Can't mount sdcard:copy default media content failed."
this was coming up before the data/factory rest also
any suggestions on how i can fix this ?
ps this is my first android phone so i dont really now how to do much
hakkers420 said:
hello i am having the same problem tried data /factory reset but it is still doing the same thing... i get an error when entering recovery mode
"E:Can't mount /dev/block/mmcb1k0p1
(NO such file or directory)
E:copy_dbdate_media:Can't mount sdcard:copy default media content failed."
this was coming up before the data/factory rest also
any suggestions on how i can fix this ?
ps this is my first android phone so i dont really now how to do much
Click to expand...
Click to collapse
there are much talk about possible fixes here
http://forum.xda-developers.com/showthread.php?t=793404

S4 Stuck in 'Android Recovery'

I was just casually browsing my FB newsfeed when my S4 suddenly rebooted itself into this Android Recovery Mode.
I've been presented with the following 6 options:
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Now I have no idea what most of those options with mean, so I tried to reboot the system several times but to no avail.
At this point, I was as desperate to wipe data/factory reset but even that failed.
I've no idea what to do as I cannot afford to have this repaired at the shop and I do not have insurance either. I'm not sure if dropping it recently, and breaking the volume UP has contributed to this. However, I can use the volume DOWN.
itskimmy said:
I was just casually browsing my FB newsfeed when my S4 suddenly rebooted itself into this Android Recovery Mode.
I've been presented with the following 6 options:
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Now I have no idea what most of those options with mean, so I tried to reboot the system several times but to no avail.
At this point, I was as desperate to wipe data/factory reset but even that failed.
I've no idea what to do as I cannot afford to have this repaired at the shop and I do not have insurance either. I'm not sure if dropping it recently, and breaking the volume UP has contributed to this. However, I can use the volume DOWN.
Click to expand...
Click to collapse
Try to Choose wipe cache and then factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!) then reboot. If still doesnt Boot Flash the stock rom via odin.
Repulsa said:
Try to Choose wipe cache and then factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!) then reboot. If still doesnt Boot Flash the stock rom via odin.
Click to expand...
Click to collapse
I can't even get back into the android recovery screen now for some strange reason. It just flashes the white Samsung Galaxy real quick and shuts back off straight away. I've tried holding in all power combos (volume, power and home screen) to get in but that isn't working.
Edit: Okay. I managed to did that, then rebooted. It still starts back up into the recovery screen.
Also what does 'Boot Flash the stock rom via odin' mean? How do I do that? It is not an option on my screen.
Hi,
read this ( don't download anything from this post, it's not for S4 ! )
and this
I've checked out those links and it's far too complexed for me to understand. I've rang around a few local phone repair shops, and I've found a cheap quote for £10-15. I'd rather leave it in the hands of someone that knows what they are doing as opposed to risking it myself and cocking it up.
Thanks though.

need help with axon 7 a2017u semi bricked

Hi
Yesterday I got my axon 7 and it worked perfect.
Now I was wanted to change the language
So I downloaded as file that in my language
And I tried to install him .
And it worked by the adb software when the axon connected to the computer
So I went to the application in my phone and changed it to my language after USB debugging and developer option is worked
Then the phone was changed to my language and crashed
Now the axon just show the start logo and stuck in restart loop. so I tried to do few thing through your forum , but nothing helped ..
I also cleared the cache through recovery mode but it also didn't help
Its like the axon can't upload the operating system
Thanks a lot for who will help me here.
Also if it possible to send money through PayPal
And if it's legal I will send 30$ to the first that will help me solve this problem
Can you share the link to the file you downloaded ?
Is it compatible with the version of your phone ?
If you can enter in recovery it's enough to save it.
billy_boolean said:
Can you share the link to the file you downloaded ?
Is it compatible with the version of your phone ?
If you can enter in recovery it's enough to save it.
Click to expand...
Click to collapse
Yea the reason it happened is because I installed wrong adb language on my axon through USB debugging and external app
Now it possible to get into recovery
I just don't know what to do next
I tried few things but I always keep getting errors
You can try to install TWRP.
You will have a lot of option.
There is no option to restor the phone in the official recovery ?
billy_boolean said:
You can try to install TWRP.
You will have a lot of option.
There is no option to restor the phone in the official recovery ?
Click to expand...
Click to collapse
I tried to use twrp but the computer doesn't recognize My axon
You need to install driver first...
billy_boolean said:
You need to install driver first...
Click to expand...
Click to collapse
I tried but after the install the drivers and cheak them in the device manager in my computer
The name of the driver was London marshesll something
And not what I saw in the guide - adb something
And it didn't recognize my device
I wrote also adb reboot bootloader
And it gives me error massage
I would be more then happy to give someone 30$ now..
Just that my axon will work
Did you root your phone, or just use ADB to sideload a file? If it's wasn't rooted/unlocked, then a factory reset should take care of it, as nothing done via ADB in that setup would impact the system partitions.
If you used the unofficial bootloader unlocking, then you'll have to follow other people's restore guides.
As @TeutonJon78 mention, a factory reset will do the job youan boot to stock recovery using adb
Code:
adb reboot recovery
Or doing it manually,
- Completely Power off your device
- Press and HOLD Volume UP and Power button.
- once you boot to recovery just use your volume buttons to navigate FACTORY RESET.
- Reboot System
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
I will be honest man. I bricked mine too. Everybody has a step by step guide that they say works. I followed them step by step. They did not work. I have an RMA open on my phone and fedex is taking it to ZTE. Use the warranty. Until Zte puts online the full factory images for us to use there is no real way to fix these things.
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
Are you from Israel?
---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------
I know how to help you if you can tell me which bootloader version you have? Did you unlocked it? did you use Tenfar's method to root it?
tabletalker7 said:
I will be honest man. I bricked mine too. Everybody has a step by step guide that they say works. I followed them step by step. They did not work. I have an RMA open on my phone and fedex is taking it to ZTE. Use the warranty. Until Zte puts online the full factory images for us to use there is no real way to fix these things.
Click to expand...
Click to collapse
Were you playing around with the rooting/unofficial bootloader? It should be very hard to actually brick the device without doing those things, and nothing a factory reset shouldn't fix.
If one's playing around with unofficial modifications, then they should take all precautions to make sure to know how to recover the device before hand. There's still a lot of moving pieces between potentially faulty TWRP bugs and no image file.
liron lev said:
holding up and down at the same time. get to fastboot mode it says secure boot: enabled and device state: locked. then i entered to recovery mode, and press on "wipe data/factory reset" (said it was successfully finished). then i pressed on "reboot system now". still its stuck on the zte logo
Click to expand...
Click to collapse
Did you let it sit for awhile? First runs after a factory reset can take up to even 10 minutes to boot fully. If it still doesn't work again, check if the recovery menu has another option like wipe cache/davlik, which maybe also needs to run if they have a bug in the recovery code about resetting data. If you hadn't touch anything using the tools on this forum, and none of the factory reset/wipe data/wipe cache stuff helps, then you probably have a faulty phone. Just sideloading an app shouldn't be able to corrupt a locked system partition.
The OP of this thread hasn't yet clarified if he was just sideloading files on a normal system (which should be totally fixable unless his phone has an actual flash problem) or if he had been tinkering with other things first.
TeutonJon78 said:
Were you playing around with the rooting/unofficial bootloader? It should be very hard to actually brick the device without doing those things, and nothing a factory reset shouldn't fix.
If one's playing around with unofficial modifications, then they should take all precautions to make sure to know how to recover the device before hand. There's still a lot of moving pieces between potentially faulty TWRP bugs and no image file.
Did you let it sit for awhile? First runs after a factory reset can take up to even 10 minutes to boot fully. If it still doesn't work again, check if the recovery menu has another option like wipe cache/davlik, which maybe also needs to run if they have a bug in the recovery code about resetting data. If you hadn't touch anything using the tools on this forum, and none of the factory reset/wipe data/wipe cache stuff helps, then you probably have a faulty phone. Just sideloading an app shouldn't be able to corrupt a locked system partition.
The OP of this thread hasn't yet clarified if he was just sideloading files on a normal system (which should be totally fixable unless his phone has an actual flash problem) or if he had been tinkering with other things first.
Click to expand...
Click to collapse
The factory reset made my phone lose it's IMEI. Everyone said follow this certain guide. After following that guide and getting more help after that I had an AXON 7 that wouldn't turn on at all. Without full factory images from ZTE I won't touch the software. ZTE can fix it.
tabletalker7 said:
The factory reset made my phone lose it's IMEI. Everyone said follow this certain guide. After following that guide and getting more help after that I had an AXON 7 that wouldn't turn on at all. Without full factory images from ZTE I won't touch the software. ZTE can fix it.
Click to expand...
Click to collapse
Which guide did you follow? A Factory reset form within the stock software or stock recovery shouldn't cause that problem at all, as it should only be wiping data, cache, Davlik, and potentially the "media" portion of the internal storage.
TeutonJon78 said:
Which guide did you follow? A Factory reset form within the stock software or stock recovery shouldn't cause that problem at all, as it should only be wiping data, cache, Davlik, and potentially the "media" portion of the internal storage.
Click to expand...
Click to collapse
The factory reset that made it lose the IMEI - it was completely stock then!
liron lev said:
Hi
Yesterday I got my axon 7 and it worked perfect.
Now I was wanted to change the language
So I downloaded as file that in my language
And I tried to install him .
And it worked by the adb software when the axon connected to the computer
So I went to the application in my phone and changed it to my language after USB debugging and developer option is worked
Then the phone was changed to my language and crashed
Now the axon just show the start logo and stuck in restart loop. so I tried to do few thing through your forum , but nothing helped ..
I also cleared the cache through recovery mode but it also didn't help
Its like the axon can't upload the operating system
Thanks a lot for who will help me here.
Also if it possible to send money through PayPal
And if it's legal I will send 30$ to the first that will help me solve this problem
Click to expand...
Click to collapse
I could help you, please pm.
i tried to use the appliction "morelocale2" to chnge my phone language.
i did turn on the usb debugging option through Developer Options.
it all went good until i tried to choose my language from the app (morelocale2) it change to my language got stucked and start looping over and over. (start up and shut dowm).
after that i cleand evrything such as: wipe data/factory and cache data, and then i restart the phone. it is stoped looping but got stucked on logo zte. and after i cleaned the data i waited few houres.
i also think i used an old version of "morelocale2".
and yes im from israel...
liron lev said:
i tried to use the appliction "morelocale2" to chnge my phone language.
i did turn on the usb debugging option through Developer Options.
it all went good until i tried to choose my language from the app (morelocale2) it change to my language got stucked and start looping over and over. (start up and shut dowm).
after that i cleand evrything such as: wipe data/factory and cache data, and then i restart the phone. it is stoped looping but got stucked on logo zte. and after i cleaned the data i waited few houres.
i also think i used an old version of "morelocale2".
and yes im from israel...
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.wanam
download this app
install it
search hebrew in hebrew
choose hebrew (iw)
accept the root prompt
reboot your phone
everything will be fine
If you have bootloop issues these are not related to the app!
if you need help with this contact me!
you have my info in pm.

Restarting Issue

I have a Moto X Style Indian version & for some reason my phone is continuously restarting. The moment I go in settings/developer options I can see the message developer options not available for this user. I want to take a backup of my gallery but the phone just doesn't remain switched on for me to connect & take the backup. I have tried going into recovery mode & wiping the cache but still the issue remains. Can anyone help me get my data back? If I can get the data then I can format the phone.
choosymoron said:
I have a Moto X Style Indian version & for some reason my phone is continuously restarting. The moment I go in settings/developer options I can see the message developer options not available for this user. I want to take a backup of my gallery but the phone just doesn't remain switched on for me to connect & take the backup. I have tried going into recovery mode & wiping the cache but still the issue remains. Can anyone help me get my data back? If I can get the data then I can format the phone.
Click to expand...
Click to collapse
Go into TWRP, put in an SD card en use TWRP File manager to copy your files to the SD card?
Ijspegel said:
Go into TWRP, put in an SD card en use TWRP File manager to copy your files to the SD card?
Click to expand...
Click to collapse
It's not rooted. It's a complete stock phone with stock recovery.
choosymoron said:
I have a Moto X Style Indian version & for some reason my phone is continuously restarting. The moment I go in settings/developer options I can see the message developer options not available for this user. I want to take a backup of my gallery but the phone just doesn't remain switched on for me to connect & take the backup. I have tried going into recovery mode & wiping the cache but still the issue remains. Can anyone help me get my data back? If I can get the data then I can format the phone.
Click to expand...
Click to collapse
Are you backing your photos up on Google Photos? How long do you have in the system until the device reboots? It could be a stuck in power button, like the Nexus 5 is known for. To determine if this is the case, boot the phone into fastboot by holding power and volume down and let it sit for a minute. If it selects an option without you selecting anything, it is most likely a power button issue. In this case, rapidly flick the power button even though it may feel physically fine and tell me if that works.
Thanks for helping out. No backup on Google photos is not done. The phone remains for max 5 to 10secs. I doubt the power button is the issue as I've been to recovery mode to wipe the cache, if power button was pressed I'm sure I would have come across issues while wiping the cache.
If the phone is still under warranty send it back. If the data means that much to you then I think you will need to void the warranty and unlock the bootloader then flash TWRP. From TWRP if it stays up you can connect it to your computer and download your data.
I don't know how much can be done from the bootloader/stock recovery, but I don't think it's much. Maybe try flashing a new system partition from the bootloader and see if it boots?

Accidentally installed OTA update, now seeing many problems and can't find a fix

Yesterday I accidentally installed the OTA update. I got stuck in TWRP and flashed a new ROM. Phone booted up fine, but now I have no cellular signal, nothing that uses video or sound works. Camera doesn't work, flashlight doesn't work.
I tried several different ROMS and nothing changes. Even the system sounds, ringtones and so on do not work. Anyone have any idea what I can do? Thanks
boot into fastboot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase misc
fastboot erase fota
fastboot erase boot
then pull battery and reboot into twrp by holding power and vol down, when lg logo appears then click the power button and re-hold it down to get into twrp.
once in twrp, check and see if system is mounted, if it wont let you mount, go to wipe and wipe everything (not ur sd of course)
System, cache, dalvik, data, internal, everything... the fastboot should have already done this but let twrp do it too..
once done, use the format option and format data also, some of these may error thats okay, just keep going..
once done reflash the full rom that matches your device.. let it flash and reboot and do its thing. this should fix the issues...
once it boots you may need to let it activate, or re-activate.
Only other suggestion would be if you have a twrp backup and you backed up your efs, its time to restore it also and see if the NV files have been damaged.
I've tried installing several different roms available on xda but that didn't resolve the issue. My phone remains in a boot loop state. Is there a way I can return to stock without compromising my ability to use the current root exploits?
Might help to know what you've got currently, are you able to get to recovery at all, etc?
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
My Solution
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
lanyueng said:
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
Click to expand...
Click to collapse
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
jluca98 said:
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
Click to expand...
Click to collapse
This isn't working for me. Keeps rebooting to TWRP.
I get FAILED (remote: unknown command) with every adb command
Any ideas?
Drkphnxs2k said:
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
Click to expand...
Click to collapse
Don't use Easy Recowvery. Do it manually from the original thread. You can also google it for some sites that have cleaned the instructions up for easier reading.
I just did a H918 10d like this.

Resources