I need help with booting into recovery mode on E5803 with 7.1.1 firmware. Phone is stock, not rooted, locked bootloader.
The problem is that "adb reboot recovery" simply reboots the phone to OS.
Turning it off, pressing Volume Down and connecting to computer while holding volume down has the same result.
Any advice would be appreciated.
voland66 said:
I need help with booting into recovery mode on E5803 with 7.1.1 firmware. Phone is stock, not rooted, locked bootloader.
The problem is that "adb reboot recovery" simply reboots the phone to OS.
Turning it off, pressing Volume Down and connecting to computer while holding volume down has the same result.
Any advice would be appreciated.
Click to expand...
Click to collapse
there isn't a recovery for stock.. well.. there is.. but not like a normal ui recovery but it's only used as the OTA loader to upgrade for OEM
NeoBeum said:
there isn't a recovery for stock.. well.. there is.. but not like a normal ui recovery but it's only used as the OTA loader to upgrade for OEM
Click to expand...
Click to collapse
Thanks.
My reason for trying to get into recovery was to erase cache in the hope this could resolve some of the sluggish behavior that I noticed after 7.1.1 update. Is there an easy way to do that?
I also got worried that my inability to get into recovery could prevent me from flashing a different stock rom with xperifirm/flashtool. I guess, I should not have a problem.
(I am thinking of flashing a stock rom for a different country in the hope of getting fingerprint working though I did not see confirmations of this working on nougat.)
voland66 said:
Thanks.
My reason for trying to get into recovery was to erase cache in the hope this could resolve some of the sluggish behavior that I noticed after 7.1.1 update. Is there an easy way to do that?
I also got worried that my inability to get into recovery could prevent me from flashing a different stock rom with xperifirm/flashtool. I guess, I should not have a problem.
(I am thinking of flashing a stock rom for a different country in the hope of getting fingerprint working though I did not see confirmations of this working on nougat.)
Click to expand...
Click to collapse
mmmm try vol up+power
clear the play caches and services
and then try another vol up+ power cycle
edit: the volume up + power button, needs to be done while the device is on... the device will vibrate 3 times and the display turns off to indicate it did it's clear
also - quickly check the app settings page and scan to look for any system apps that appear as 0.0KB / 0Bytes
mentioned it @ the sonyforum https://talk.sonymobile.com/t5/Xper...of-clean-upgrades-amp-boot/m-p/1243574#M38418
Related
A few weeks a go I dropped my phone in some water. It appeared to be dead, so I left it off. After a day I turned it back on and everything was fine again except the volume up key was not working. Anyway I could live with that, in fact I lived with it so much that I all but forgot about it. That was until today...
I tried to flash a new ROM and something went wrong and I got stuck in a bootloop, no problem just boot into recovery right.... oh yeah requires volume up key :crying: Then I thought oh ok no problem I will boot into Custom OS flash mode and reflash a stock ROM with ODIN.... oh **** first stage is 'Volume up: Continue'. So I am stuck.
I have taken the phone apart to clean out the buttons but it all seems OK.
I think I know the answer to this ("No" or "Get your volume key fixed") but is there any other way I can solve this issue and flash any ROM without sending it back to my network or manufacturer?
use adb dude :highfive::highfive: when u stuck just type adb reboot recovery
u need to have android sdk on ur pc
yahyoh said:
use adb dude :highfive::highfive: when u stuck just type adb reboot recovery
u need to have android sdk on ur pc
Click to expand...
Click to collapse
Thanks for the reply. Is adb accessible from this situation? I did try it but when I did "adb devices" it didn't list my phone which lead me to believe that adb was not accessible in this situation (i.e. the phone must be booted up.
I think I have sorted it now, I went in to ODIN mode and hammered the volume up key about 100 times in quick succession, eventually one of them registered and it went into Download Mode, I have just followed the instructions here http://forum.xda-developers.com/showthread.php?t=1457458 and it looks like I have my phone back
I think until the volume key is sorted I might have to flash via ODIN.
Bojanglez said:
Thanks for the reply. Is adb accessible from this situation? I did try it but when I did "adb devices" it didn't list my phone which lead me to believe that adb was not accessible in this situation (i.e. the phone must be booted up.
I think I have sorted it now, I went in to ODIN mode and hammered the volume up key about 100 times in quick succession, eventually one of them registered and it went into Download Mode, I have just followed the instructions here http://forum.xda-developers.com/showthread.php?t=1457458 and it looks like I have my phone back
I think until the volume key is sorted I might have to flash via ODIN.
Click to expand...
Click to collapse
i think stock kernel dont support adb on boot or in recovery
u can go into recovery from device in terminal just type : reboot recovery or i think rom manager has option to reboot into recovery or adb
and 99% from roms on xda have option to reboot into recovery when u press power button
JIG?
Bojanglez said:
A few weeks a go I dropped my phone in some water. It appeared to be dead, so I left it off. After a day I turned it back on and everything was fine again except the volume up key was not working. Anyway I could live with that, in fact I lived with it so much that I all but forgot about it. That was until today...
I tried to flash a new ROM and something went wrong and I got stuck in a bootloop, no problem just boot into recovery right.... oh yeah requires volume up key :crying: Then I thought oh ok no problem I will boot into Custom OS flash mode and reflash a stock ROM with ODIN.... oh **** first stage is 'Volume up: Continue'. So I am stuck.
I have taken the phone apart to clean out the buttons but it all seems OK.
I think I know the answer to this ("No" or "Get your volume key fixed") but is there any other way I can solve this issue and flash any ROM without sending it back to my network or manufacturer?
Click to expand...
Click to collapse
i hope this one helps http://samsunggalaxysforums.com/showthread.php/1237-3-Ways-of-getting-to-Recovery-Mode
Hello guys i am pretty stuck on bootloop after flashing a new custom rom to my device, and my volume + (up) is no longer working, meaning i can get into recovery mode. Please is there anyway to fix this issue. I need this urgently
Started out with Z4, updated to Z8. I tried this with TWRP installed after making both EFS backup and regular nandroid backup, installed fine. I made sure to use the recommended partition zips. Here's the ROM I used. However after turning my phone off it will turn on into safe mode (lollipop) in limited, seemingly random instances. I have yet to access recovery. However, the one part I know that I screwed up is I installed xposed (forgot to install the xposed helper), so I receive unlimited errors for that and can't do anything.
I've tried rebooting my phone normally, rebooting into recovery, and cutting all of my losses and flashing back to stock. Any advice? I'm trying to follow the directions here to revert back to stock, but my computer will only recognize an unrecognized device.
Thanks for the help!
Flash the rom labeled "BarePop_TE_V1 " it has the files need to fix your issues (make sure to thank @engine95). Heres the link to the rom it is pretty much a debloated version of that lollipop rom you were running:http://forum.xda-developers.com/sprint-lg-g3/development/barepop-zv8-t3035551
That reboot problem you are having is because of a bug with the stock rom so just flash that one to fix everything.
I appreciate the help, however my main problem still lies with the fact that I can't access recovery. I've gotten it to where I can reboot normally (albeit I still can't do anything due to the constant errors), but holding pwr+vol down and then letting go and reclicking those once the lg sign comes up won't let me into recovery. Do you have any advice for that? Thanks again for the help!
1619415 said:
Flash the rom labeled "BarePop_TE_V1 " it has the files need to fix your issues (make sure to thank @engine95). Heres the link to the rom it is pretty much a debloated version of that lollipop rom you were running:http://forum.xda-developers.com/sprint-lg-g3/development/barepop-zv8-t3035551
That reboot problem you are having is because of a bug with the stock rom so just flash that one to fix everything.
Click to expand...
Click to collapse
I appreciate the help, however my main problem still lies with the fact that I can't access recovery. I've gotten it to where I can reboot normally (albeit I still can't do anything due to the constant errors), but holding pwr+vol down and then letting go and reclicking those once the lg sign comes up won't let me into recovery. Do you have any advice for that? Thanks again for the help!
I've had similar issues in the past trying to boot into recovery and the method you said (vol down+power then let go and press again when LG logo comes up) also wouldn't work for me. Have you tried just holding it down and not letting it go until you see "Recovery Mode"? That actually worked for me.
death_muffins said:
I've had similar issues in the past trying to boot into recovery and the method you said (vol down+power then let go and press again when LG logo comes up) also wouldn't work for me. Have you tried just holding it down and not letting it go until you see "Recovery Mode"? That actually worked for me.
Click to expand...
Click to collapse
I've tried doing that a few times as well, it just boots up as normal at that point. I'm welcome to trying anything though so if you have any other ideas, please let me know.
bdpope88 said:
I've tried doing that a few times as well, it just boots up as normal at that point. I'm welcome to trying anything though so if you have any other ideas, please let me know.
Click to expand...
Click to collapse
death_muffins said:
I've had similar issues in the past trying to boot into recovery and the method you said (vol down+power then let go and press again when LG logo comes up) also wouldn't work for me. Have you tried just holding it down and not letting it go until you see "Recovery Mode"? That actually worked for me.
Click to expand...
Click to collapse
I don't know why it worked this time... but it worked on my second attempt! I have access! Only issue is the touchscreen is messed up on the ROM, but it works!
With all of these issues you may want to flashtool back to ZV4 and reroot or ZV8 your call.
bdpope88 said:
I don't know why it worked this time... but it worked on my second attempt! I have access! Only issue is the touchscreen is messed up on the ROM, but it works!
Click to expand...
Click to collapse
That's a step in the right direction!
death_muffins said:
I've had similar issues in the past trying to boot into recovery and the method you said (vol down+power then let go and press again when LG logo comes up) also wouldn't work for me. Have you tried just holding it down and not letting it go until you see "Recovery Mode"? That actually worked for me.
Click to expand...
Click to collapse
Not to be redundant, but my understanding is the only way it will go into recovery from full off is to keep holding power+vol down until you see "recovery mode", if you let up on the buttons before you see recovery mode it will simply reboot.
When rooting an ATT G3 I could not for the life of me get it to boot into recovery using the button combo, instead I just used adb reboot recovery instead, worked every time, to this day the guy can only reboot to recovery from within rom, gonna suck if he gets soft bricked.. My Sprint G# holding the buttons works like a charm
When I want to boot into recpvery I always have to do volume + power up until the lg logo comes up then let go and press them again. Then I have to press the factory reset button and click yes. For me and I guess others when you hold volume + powerdown you just end up going into safe mode. If you end up always having problem just download a app that can make your phone reboot itself or download terminal and run:
su
reboot recovery
That always works because it is built into the phone.
1619415 said:
When I want to boot into recpvery I always have to do volume + power up until the lg logo comes up then let go and press them again. Then I have to press the factory reset button and click yes. For me and I guess others when you hold volume + powerdown you just end up going into safe mode. If you end up always having problem just download a app that can make your phone reboot itself or download terminal and run:
su
reboot recovery
That always works because it is built into the phone.
Click to expand...
Click to collapse
For me if I go into recovery by volume down + power. It just goes into recovery.
If I'm using phone, i use terminal command. su -c reboot revovery
I'm using ls990 gold edition.
Ok guys so I have a Sony Xperia Z Ultra and I decided to install Marshmallow 6.0 on it (which wasn't released for my phone). I downloaded the boot, cache, system and userdata imgs of Marshmallow 6.0 and installed them using fastboot, then I was supposed to boot in recovery mode and wipe the caches and do a reset, before installing the G-apps zip file and completing the entire process. So I tried to start recovery mode which I had previously installed already and it failed, starting in safe mode instead. Then I re-installed the recovery using a batch file in a directory downloaded from NUT's XDA Developers download site, which failed on the first try. So I tried again and it was installed, meaning my phone will automatically reboot into recovery right after it was done. My phone rebooted but my screen remained black and nothing happened. I tried holding down the power button and it vibrated but nothing happened again. I tried holding down the power and volume down button for 30sec and more, tried it with the volume up button too and it didn't work. I tried connecting my phone to the pc but it won't recognize it (of course) and I tried holding the volume up button upon connecting to enter fastboot but that failed as well. Now it's stuck like this and I'm hoping its battery drains out and it powers off. Help.
Update: I went to sleep and now that I've woken up, the screen is still going with the low battery red light. I don't know for how long it will continue, but the problem remains.
Update: Now my pc recognizes it but all adb commands have no effect.
Jissatsu said:
Ok guys so I have a Sony Xperia Z Ultra and I decided to install Marshmallow 6.0 on it (which wasn't released for my phone). I downloaded the boot, cache, system and userdata imgs of Marshmallow 6.0 and installed them using fastboot, then I was supposed to boot in recovery mode and wipe the caches and do a reset, before installing the G-apps zip file and completing the entire process. So I tried to start recovery mode which I had previously installed already and it failed, starting in safe mode instead. Then I re-installed the recovery using a batch file in a directory downloaded from NUT's XDA Developers download site, which failed on the first try. So I tried again and it was installed, meaning my phone will automatically reboot into recovery right after it was done. My phone rebooted but my screen remained black and nothing happened. I tried holding down the power button and it vibrated but nothing happened again. I tried holding down the power and volume down button for 30sec and more, tried it with the volume up button too and it didn't work. I tried connecting my phone to the pc but it won't recognize it (of course) and I tried holding the volume up button upon connecting to enter fastboot but that failed as well. Now it's stuck like this and I'm hoping its battery drains out and it powers off. Help.
Update: I went to sleep and now that I've woken up, the screen is still going with the low battery red light. I don't know for how long it will continue, but the problem remains.
Update: Now my pc recognizes it but all adb commands have no effect.
Click to expand...
Click to collapse
you should give some info... like what rom youre using. also use twrp 3.x with mm
you cant expect help without telling the error messages you get...
you can always power off your phone with holding vol down + power for 30sec
MusterMaxMueller said:
you should give some info... like what rom youre using. also use twrp 3.x with mm
you cant expect help without telling the error messages you get...
you can always power off your phone with holding vol down + power for 30sec
Click to expand...
Click to collapse
YEAH ok here's my issue. NO MATTER WHAT recovery I install (through the app or fastboot) IT DOES NOT WORK. Any earlier version of TWRP, it will boot into, but the screen is unresponsive, while the latest version of TWRP simply acts like it isn't there as the phone never boots into recovery, this has been happening on MM and now it's happening on my latest stock. After the failed MM attempts I've downloaded the latest C6833 stock and everything is fine, but I'd like to be able to install custom roms like everyone else. It took me a day or two to learn how to actually do that, but I still have no idea why NO recovery works for me. My device is rooted, bootloader unlocked, all that crap. I tried many kernel links on your site, especially that main one that the mod posted, but the links are dead. Help.
Jissatsu said:
YEAH ok here's my issue. NO MATTER WHAT recovery I install (through the app or fastboot) IT DOES NOT WORK. Any earlier version of TWRP, it will boot into, but the screen is unresponsive, while the latest version of TWRP simply acts like it isn't there as the phone never boots into recovery, this has been happening on MM and now it's happening on my latest stock. After the failed MM attempts I've downloaded the latest C6833 stock and everything is fine, but I'd like to be able to install custom roms like everyone else. It took me a day or two to learn how to actually do that, but I still have no idea why NO recovery works for me. My device is rooted, bootloader unlocked, all that crap. I tried many kernel links on your site, especially that main one that the mod posted, but the links are dead. Help.
Click to expand...
Click to collapse
there is other way to enter twrp 3.0.2 with new bootloader, power + vol down (instead of up!)
read op of twrp thread and follow instructions carefully and it'll work. also for the twrp i build you must be on a rom which uses sony aosp device tree (like aicp). otherwise i wont guarantee that it will work.
MusterMaxMueller said:
there is other way to enter twrp 3.0.2 with new bootloader, power + vol down (instead of up!)
read op of twrp thread and follow instructions carefully and it'll work. also for the twrp i build you must be on a rom which uses sony aosp device tree (like aicp). otherwise i wont guarantee that it will work.
Click to expand...
Click to collapse
I tried holding the button down like you said, tried rebooting to recovery from TWRP manager itself, with root access granted of course. Nothing. Can you link the post or something? However I don't think anything in it will fix my issue.
Sounds like you flashed a recovery for another model. I had this issue with a ROM awhile back.
Didn't read the walls of text.
I recommend using you flashtool and flashing a stock ftf. Re-root, recovery and flash again.
---------- Post added at 06:16 AM ---------- Previous post was at 06:11 AM ----------
Edit. Read somethings. There are plenty of ROMs on xda do not flash the old way which is part by part. Flash the most recent Sony firmware, and you should be able to flash MM ROMs.
I have copy's of the recovery if needed.
I did flash the latest FTF using the flash tool, but I need a working recovery in order to install the gapps and still no recovery works on my device.
check here
http://forum.xda-developers.com/xpe...2-0-togari-t3452968/post68481255#post68481255
I'm having an issue with my phone volume down button. Even though I can physically press it without any problem ,the phone itself won't detect keypress. So I cant even go to download mode.
At first I have tried to clean the cache,dalvic and tried the same rom - not working
Tried that volume up+ power thing while it turn on ... not working
cleaned the phone physically but there were no dust or anything -not working
Installed original rom after formatting my partitions still not working
Still my phone stuck with safe mode. If this issue cant be fixed can anyone suggest me to disable safe mode in this phone or suggest me a rom which is not having safemode function . I know it's really dumb question to ask. But I have no other option to left .
please help me out !
@SLDarKprince, step out of safemode by hard reset:
press Power for ≈5s.
Reboot into downloadmode via TerminalEmulator:
su
reboot download
or into recovery:
reboot recovery
rp158 said:
@SLDarKprince, step out of safemode by hard reset:
press Power for ≈5s.
Reboot into downloadmode via TerminalEmulator:
su
reboot download
or into recovery:
reboot recovery
Click to expand...
Click to collapse
I have already tried it many times. But whenever i restart after app installing - it will change back to safemode.
btw thanks for the reply mate. can you please suggest any other way ...
How can you flash firmware and following factory reset without working volume switch?
rp158 said:
How can you flash firmware and following factory reset without working volume switch?
Click to expand...
Click to collapse
the rom which i used , had power option menu which include "recovery,download,power off,restart". So i hadnt any issue with it. Also at that time it detect vol.down button sometimes. But now.. it dosent work at all
...so it wasn't firmware. And flashing firmware by Odin would be the way to repair any software-bug. But unlikely, that you manage it without power buttons.
A new phone?
rp158 said:
...so it wasn't firmware. And flashing firmware by Odin would be the way to repair any software-bug. But unlikely, that you manage it without power buttons.
A new phone?
Click to expand...
Click to collapse
oops are you sure? aren't there any other way to force-disable safe mode in OS.
also i found many TWRP recovery for the same SoC (https://unofficialtwrp.com/download-twrp-3-3-1-mediatek-mt6765/ (Mediatek Helio P35 (MT6765))), will it work if I flash it with it?
thanks
horasmichael said:
also i found many TWRP recovery for the same SoC (https://unofficialtwrp.com/download-twrp-3-3-1-mediatek-mt6765/ (Mediatek Helio P35 (MT6765))), will it work if I flash it with it?
thanks
Click to expand...
Click to collapse
You will not no unless you try it
hi does yours work?
totalnewbielinux said:
hi does yours work?
Click to expand...
Click to collapse
do you have the same phone as him if so yes it will work as it is the same chipset t your phone mine is unofficial more like ported twrp
I am newbie but flashed samsung j7 before, yes I have oppo A15S, however the chipset I am not sure since the phone is come with the maxis/hotlink package that addon a few RM get free phone.
if possible I want official but asked chat GPT and google sadly no result+dead link.
totalnewbielinux said:
I am newbie but flashed samsung j7 before, yes I have oppo A15S, however the chipset I am not sure since the phone is come with the maxis/hotlink package that addon a few RM get free phone.
Click to expand...
Click to collapse
Mediatek MT6765 Helio P35 (12nm) is the chipset of your phone and also if you want an official version youcan compile your own twrp for your self
totalnewbielinux said:
if possible I want official but asked chat GPT and google sadly no result+dead link.
Click to expand...
Click to collapse
here there is an unofficial twrp for your chipset ---------> https://unofficialtwrp.com/download-twrp-3-3-1-mediatek-mt6765/
Hi my experience flash 1 phone before and that phone at least can boot into (normal mode) > now my oppo can only boot into recovery mode. Is there any way to enable developer mode?
totalnewbielinux said:
Hi my experience flash 1 phone before and that phone at least can boot into (normal mode) > now my oppo can only boot into recovery mode. Is there any way to enable developer mode?
Click to expand...
Click to collapse
what do you mean that your phone is stuck at recovery mode? if not you can enable the developers option this is the steps
1.) Go to setting
2.) Go to About phone
3.) tap the build number 7 times
4.) now quit the setting then open it again
5.) scroll down then choose the developers option
thats how you open developers option
basically when I reboot turn off> it will "never" boot into normal mode. My phone is so broken that pressing power button only still boot into recovery mode, wipe data and reboot still into recovery mode.
totalnewbielinux said:
basically when I reboot turn off> it will "never" boot into normal mode. My phone is so broken that pressing power button only still boot into recovery mode, wipe data and reboot still into recovery mode.
Click to expand...
Click to collapse
can you give a picture of your phone or video while doing it so i know what s the problem?
Sorry for late reply basically my volume key stuck and a week later it can use so I JUST IGNORE NOW WORSE. just now I power off my phone and now I cannot power on my phone (just now charging no problem) now charging does not show anything and my phone bricked...
totalnewbielinux said:
Sorry for late reply basically my volume key stuck and a week later it can use so I JUST IGNORE NOW WORSE. just now I power off my phone and now I cannot power on my phone (just now charging no problem) now charging does not show anything and my phone bricked...
Click to expand...
Click to collapse
your phone seems to be new which means that your volume keys are still new and good so thats not our problem here your phone didin't boot right? did you do something to your system phone like flashing or something? because if you do there is a big chance that you screw up something in your phone resulting it to be like that. now your phone can still be charge right there might be still a hope we just need to reflash your whole firmware ( if the problem is really a firmware) you said before you cant boot right then there must be a problem in the booting process, i tested this on my phone before i clean wipe my whole phone and that include system partition so when i tried to boot my phone it wont and when i charge it no logo would appear just like yours so im guessing that you phone partition is gone and like you said to its bricked now. if thats the case we need to flash the whole firmware
Anonymous V said:
your phone seems to be new which means that your volume keys are still new and good so thats not our problem here your phone didin't boot right? did you do something to your system phone like flashing or something? because if you do there is a big chance that you screw up something in your phone resulting it to be like that. now your phone can still be charge right there might be still a hope we just need to reflash your whole firmware ( if the problem is really a firmware) you said before you cant boot right then there must be a problem in the booting process, i tested this on my phone before i clean wipe my whole phone and that include system partition so when i tried to boot my phone it wont and when i charge it no logo would appear just like yours so im guessing that you phone partition is gone and like you said to its bricked now. if thats the case we need to flash the whole firmware
Click to expand...
Click to collapse
Thanks for reply>to avoid confusion no I did not do anything/flashing/even enable usb debugging to my OPPO A15S. I am total newbie that I flash Samsung J7 once only. The Oppo A15S yes it is 1-2 years only, volume key clicking works fine but after system update via setting>Official Oppo coloros things. My phone kinda messed up volume key not working<google results say because a lot of phone cannot boot up because of volume key. So should I pry open my phone to see the volume key? Or just wait until 1 day scheduled power up happens?
Logs:
Wednesday 5am my phone auto boot up in recovery mode.I press restart and the screen black nothing happens.
Thursday 5am no boot up
Friday no boot up too.
So I assume it is my phone power is low and somehow my auto scheduled power on force my phone to boot up? and that time system auto update causes my phone die in midway?
totalnewbielinux said:
So I assume it is my phone power is low and somehow my auto scheduled power on force my phone to boot up? and that time system auto update causes my phone die in midway?
Click to expand...
Click to collapse
hmm i see you didnt do anything in your phone but you did say that you updated it right? while updating you phone did something happen? like rebooting? if so there might be a chance that it became corrupted because of ,that while in the case of your power button what kind of problem does it have? does it work correctly? or you cant click it like its stuck or something? or maybe the button is working correctly and your phone just doesnt boot up? if the button is really problem like google stated ----->
Why is my OPPO always in Recovery mode?
One of the most common causes is that [B]one of the buttons used to access android system recovery is defective or malfunctioning[/B]. Now, you should first check if the physical buttons are responding properly, especially the volume buttons, before trying to get rid of the Android Recovery Mode.
you should probably check you physical button because that might be a problem and i just remembered i have the same problem in my sisters phone vivo y53 its always stuck in recovery mode and we are confused why did it happen so we bring it to our technician friend and let him fix it and he really fix it he he told me that if something happen like this again check all the buttons correctly. Now there is really problem in you button and you cant just pry in you phone you might break something you should let the professional do it like technician after you fix your button try to boot up again and if its still black screen or recovery then the problem is in the phone system and you can comeback here so we can help you fix it.