Develop Bugs

Booting to recovery with button combination not working

So, after trying out a few firmwares (JM2, JG8, JM5) and kernels (Samset&OC) I can't no longer boot to recovery with Vol UP + Home + power. I can't really say when this problem first occurred, but maybe with JG8 flash. The strange thing is that I can get to recovery with adb reboot recovery and through android console with reboot recovery (when rooted ofc). Also download mode works great.
Things I have tried:
-flash again to JM2 and JM5 with re-partition checked (512 PIT)
-cleared cache+data through recovery
-factory reset through phone code (this also cleared the internal SD)
-took out the battery multiple times
-booted phone without sim
-flashed phone without sim
-changed CSC with phone code
-restore a nandroid backup of JM2. Recovery worked with this one when I took the backup
-there's no external flash card inserted
Soooo..does anyone have any idea about this kind of problem?

i had a similar problem after trying few ROMs. In my case, when i pres the key combi i get the boot logo and then few seconds later the screen goes black and then i see the boot logo again, and this goes forever. and then i tried pressing the same key combination simultaneously and once i see the boot logo i let go the power button and keep the vol up and home pressed, and then only it went into the recovery mode.
hope it works the same for you
Cheers

Agreed, 99.9% chance you are doing it wrong.
Sent from my GT-I9000 using XDA App

mmthabet: I had the exact same experience. Letting go of the power button when the logo appears lets me enter recovery.

or you may need to take out the battery first for a few seconds... after that, you can reinsert it back and try recovery mode...
at least this work for me...

Thanks for replies but none of the solutions work. The recovery mode button combination DID work for a few weeks, but then just stopped working.
I know that I'm doing it right. I have always pressed vol up and home down until the phone loaded recovery and only briefly pressed power button just at the start. I have also tried to remove battery multiple times and once waited 30 mins before re-inserting it.
Trust me, I'm not doing it wrong :s And recovery is working great through adb reboot recovery and shell.

Darkstriker said:
Agreed, 99.9% chance you are doing it wrong.
Click to expand...
Click to collapse
More so a timing issue. Buttons not pressed at the same time.
I get it all the time for all combo's.
Just keep trying.

You might already have this however just in case you dont, check out Quick Boot.
http://www.appbrain.com/app/com.siriusapplications.quickboot
With this app you can boot into recovery mode. Have to be rooted though.

odyssey61 said:
You might already have this however just in case you dont, check out Quick Boot.
http://www.appbrain.com/app/com.siriusapplications.quickboot
With this app you can boot into recovery mode. Have to be rooted though.
Click to expand...
Click to collapse
this wont work, if you bricked the phone in a bad flash situation.
in times when this app works, you can easily do adb reboot recover
so this app still doesn't address the real issue of how to get the 3 buttons press hardware recovery mode

Laum said:
I know that I'm doing it right. I have always pressed vol up and home down until the phone loaded recovery and only briefly pressed power button just at the start.
Click to expand...
Click to collapse
I release the buttons right when the first Samsung texts comes on the screen. It will take it to Recovery mode. I also had a "boot loop" few times, if I keep pressing the buttons all the time.
Have you tried release your fingers right in the first texts? I really don`t know what is exactly the right way to press the buttons, but this always have took it to Recovery.

Looks like my latest full wipe with *2767*3855# cured it. Flashed JM5-->full wipe-->samset1.9b-->samset kernel and now it works. It must've got stuck somehow in my previous JM5 installation.

I cant get into the download- or recovery-mode by using these keys... so i am not able to flash a new firmware! can anybody help me please? is there a chance to get into the download mode by using an adb-command?
please help i just cant get into the download mode!

Igor02 said:
I cant get into the download- or recovery-mode by using these keys... so i am not able to flash a new firmware! can anybody help me please? is there a chance to get into the download mode by using an adb-command?
please help i just cant get into the download mode!
Click to expand...
Click to collapse
yes
adb reboot download
but it is dangerous, as you can not recover from a bricked state, if your flash is not compatible or if something went wrong with odin, etc.

I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.

arch3rm said:
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
Click to expand...
Click to collapse
AHHHHHHHHH OMG, WHY DIDN'T YOU SAY THIS SOONER, like 5 hours ago...
i could have tried that, and not had to send my phone back for "repair"
well i'm sure i'll see that screen again in the future, i'll try that next time

AllGamer said:
AHHHHHHHHH OMG, WHY DIDN'T YOU SAY THIS SOONER, like 5 hours ago...
i could have tried that, and not had to send my phone back for "repair"
well i'm sure i'll see that screen again in the future, i'll try that next time
Click to expand...
Click to collapse
Well I did just get the phone 2 days ago,
Had that problem the same day, discovered the fix two hrs of horror later

Same Problem here i contact samsung here in mexico and a technical aggent tell me if we make a repair our phones we need a jtag and this is so bad alllready contact many people jtag manufacturers in china and honkong trow alibaba.com and no luck don't have other source i try is contact to nspro and z3x and no support for this repairand only hope still have is a reply from the people in the forum SMTi Jtag Repair Tool
Its hard to me go to UK Samsung Service Center i'm in mexico like i said
and i'm waith for a solve this i;m so very sad
http://www.youtube.com/watch?v=g8AIvalzBvY

Darkstriker said:
Agreed, 99.9% chance you are doing it wrong.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I usually release the power button on the boot screen first and then the other two buttons

arch3rm said:
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
Click to expand...
Click to collapse
Any idea how long you waited? Been waiting 5 minutes, hasn't shut off. Mine's a Bell though so I'm guessing I won't have any luck.

The way i do it (no chance of doing it wrong and timing):
hold down+home and then also press the power button for a little more then 10 seconds (so all 3 buttons for 10 seconds). The phone will reset into download mode, never fails in whatever mode the phone originaly was..

[Q] Hard brick

Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?

Just unplugged it and it turned on but is again stuck on the X. Is QHSUSB_DLOAD no longer indicative of a hard brick?

I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.

opticaldh said:
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
Click to expand...
Click to collapse
once I turn it off the whole cycle starts over again. It's sporadically deciding whether or not it wants to boot but I'll keep trying to get into fastboot

herculesgs said:
Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Click to expand...
Click to collapse
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?

uprightbass360 said:
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
Click to expand...
Click to collapse
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset

herculesgs said:
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
Click to expand...
Click to collapse
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.

uprightbass360 said:
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
Click to expand...
Click to collapse
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.

herculesgs said:
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
Click to expand...
Click to collapse
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?

uprightbass360 said:
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
Click to expand...
Click to collapse
Wally world. afaik they're pretty lax on returns

update
Got into the bootloader and did a factory reset. Everything seems to be working again now

herculesgs said:
Got into the bootloader and did a factory reset. Everything seems to be working again now
Click to expand...
Click to collapse
Awesome! Love a happy ending.

Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app

AnarchoXen said:
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.

What happens when you do vol down and power to try and get into the bootloader? Nothing at all?
Sent from my Nexus 7 using xda app-developers app

kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Follow hercules advice. Vol Down + Power to get to bootloader. Then you should be able to get to recovery. Let us know.
Sent from my Nexus 7 using Tapatalk 4

kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Stuck at Google means /system is corrupted or erased (fastboot to restore system.img)
Stuck at X means something wrong with userdata/cache (factory restore from recovery)
Won't start at all with USB identifying as QHSUSB_DLOAD means either bootloader corrupted or raw partitions corrupted
I suggest you reflash again.

Delete update

When i try to boot into recovery, my phone tries to install the update and it won't go into recovery. is there any way to delete the update file ?

bump

Do you have an MOFD_UPDATE file on the root of your phone or SD card?
If it's an OTA, it should delete after the update runs.

wipe cache

Harfainx said:
Do you have an MOFD_UPDATE file on the root of your phone or SD card?
If it's an OTA, it should delete after the update runs.
Click to expand...
Click to collapse
thats what i thought. but when i try to boot into recovery it trys to run the update. when i try to run the update it always returns an error( the android on his back with the red triangle )

pjames said:
thats what i thought. but when i try to boot into recovery it trys to run the update. when i try to run the update it always returns an error( the android on his back with the red triangle )
Click to expand...
Click to collapse
Hold power button and press volume up key a few times or until you get to recovery menu. I got stuck like this for a little while too until I realised I'd skipped a step to get to recovery...

Oh, I was thinking that it actually started an update, then errored out or actually ran an update.
Yeah if it's just the dead Android icon, that's normal. That's what happens when you boot into stock recovery on these phones for some reason.
As stated above this post, just hold the power button for a second, then press the Vol-Up key. Once you get the timing down, it'll be really easy to do, but you might have to try a few times to get it to actually kick into recovery.
Don't hold the power for 5 seconds or it will reboot. Make sure you let go of the power button after you press the Vol-Up key.
This will happen every time you boot into recovery when you have stock recovery.

Harfainx said:
Oh, I was thinking that it actually started an update, then errored out or actually ran an update.
Yeah if it's just the dead Android icon, that's normal. That's what happens when you boot into stock recovery on these phones for some reason.
As stated above this post, just hold the power button for a second, then press the Vol-Up key. Once you get the timing down, it'll be really easy to do, but you might have to try a few times to get it to actually kick into recovery.
Don't hold the power for 5 seconds or it will reboot. Make sure you let go of the power button after you press the Vol-Up key.
This will happen every time you boot into recovery when you have stock recovery.
Click to expand...
Click to collapse
It actaully starts an update. thats the problem. i get the fastboot menu, select recovery and it trys to install update and fails

It's not actually updating. That's just what it does.
When the dead android shows up, hold power for a second and press Vol-Up while still holding the power button. Then release power when the recovery menu shows up.

Please see the following for assistance: http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_Support
[email protected]

Harfainx said:
It's not actually updating. That's just what it does.
When the dead android shows up, hold power for a second and press Vol-Up while still holding the power button. Then release power when the recovery menu shows up.
Click to expand...
Click to collapse
you are still not grasping what im saying lol it actually starts the update. i get the progress bar and everything. but it doesnt complete and it gives the error message

another bump do to issue still not fixed

pjames said:
another bump do to issue still not fixed
Click to expand...
Click to collapse
Try flashing pre rooted 2.19 following all the steps given in 3.1 method 1
That should clear you're update
http://forum.xda-developers.com/showthread.php?p=60442527
Sent from my ASUS_Z00AD using Tapatalk 2

chubby65 said:
Try flashing pre rooted 2.19 following all the steps given in 3.1 method 1
That should clear you're update
http://forum.xda-developers.com/showthread.php?p=60442527
Sent from my ASUS_Z00AD using Tapatalk 2
Click to expand...
Click to collapse
you sir are awesome. that did the trick. I was able to install the update and unlock bootloader

pjames said:
you sir are awesome. that did the trick. I was able to install the update and unlock bootloader
Click to expand...
Click to collapse
Your welcome mate glad you got it sorted
Sent from my ASUS_Z00AD using Tapatalk 2

I just installed Android 7.0 and it went into a boot loop.

Can anyone help?
I have stock unlocked HTC 10 I got directly from HTC. All I did was plugging the power in and hit install.
Now it just buzzes, shows HTC splash and repeats every few seconds

TheFlyingPig said:
Can anyone help?
I have stock unlocked HTC 10 I got directly from HTC. All I did was plugging the power in and hit install.
Now it just buzzes, shows HTC splash and repeats every few seconds
Click to expand...
Click to collapse
Can you get into download mode? Hold power and volume down for a few seconds until it reboots into that mode.
Not sure what you did but from there you could recover the phone with a ruu.

TheFlyingPig said:
Can anyone help?
I have stock unlocked HTC 10 I got directly from HTC. All I did was plugging the power in and hit install.
Now it just buzzes, shows HTC splash and repeats every few seconds
Click to expand...
Click to collapse
Go into recovery do a factory reset

Tarima said:
Can you get into download mode? Hold power and volume down for a few seconds until it reboots into that mode.
Not sure what you did but from there you could recover the phone with a ruu.
Click to expand...
Click to collapse
Nop.......I tried that already....it just kept on rebooting while I was holding them down. The phone is getting pretty hot now rebooting so fast over and over.

gillim74 said:
Go into recovery do a factory reset
Click to expand...
Click to collapse
How do you do a factory reset? I will play around for another 10 minutes before I do such a thing. I'd hate to reinstall all my stuff if I can avoid it. But it'd be nice to have this option in my back pocket.
Thanks

TheFlyingPig said:
Nop.......I tried that already....it just kept on rebooting while I was holding them down. The phone is getting pretty hot now rebooting so fast over and over.
Click to expand...
Click to collapse
Just to make sure you're doing it properly, hold both until the phone resets, then let go of power while keeping volume down pressed. You've done this right?
Also try removing your sd card if you have one inserted.

Tarima said:
Just to make sure you're doing it properly, hold both until the phone resets, then let go of power while keeping volume down pressed. You've done this right?
Also try removing your sd card if you have one inserted.
Click to expand...
Click to collapse
I held it for a min, no go
But I am actually reporting back because I removed my sim and sd card and it finish booting and updating.
I stuck the cards back in and reboot. It's working fine.
Thanks all

TheFlyingPig said:
I held it for a min, no go
But I am actually reporting back because I removed my sim and sd card and it finish booting and updating.
I stuck the cards back in and reboot. It's working fine.
Thanks all
Click to expand...
Click to collapse
Good glad to hear you got it

Flashed wrong Recovery :(

I accidentally flashed wrong Recovery for my A3 2017. I now get a message that i need Samsung Smart Switch from Samsung for emergency recovery.
But this f**cking program doesnt even install. On Samsung site its a dead link. I found another one, program doesnt install...
Any ideas? Is my phone bricked?

http://www.samsung.com/global/download/smartswitchwin/

kasa ssg said:
http://www.samsung.com/global/download/smartswitchwin/
Click to expand...
Click to collapse
i have it already...smartswitch doesnt help too :crying:

Is the phone recognized in ADB/Fastboot?

kasa ssg said:
Is the phone recognized in ADB/Fastboot?
Click to expand...
Click to collapse
i installed ADB. For first time. Using this site.
https://www.xda-developers.com/install-adb-windows-macos-linux/
im in a command line area with ADB now...but i dont know what to do
https://gyazo.com/e1d3b6dcce3a18211bbcb85fd9467e28

How to switch off my phone? I tried a lot of key combo's, but it keeps coming back to a blue/green screen with this warning message....

Anyone?

wogooo said:
How to switch off my phone? I tried a lot of key combo's, but it keeps coming back to a blue/green screen with this warning message....
Click to expand...
Click to collapse
I don't think there is one to force it to power off, I think there's only one to force it to reboot which is POWER + VOL DOWN (held down for a few seconds) on the A5, it's probably the same on the A3. Then immediately as the screen turns off you have to switch to the key combination for download mode or recovery. If if you just release the keys it will try and boot normally.

makeyourself said:
I don't think there is one to force it to power off, I think there's only one to force it to reboot which is POWER + VOL DOWN (held down for a few seconds) on the A5, it's probably the same on the A3. Then immediately as the screen turns off you have to switch to the key combination for download mode or recovery. If if you just release the keys it will try and boot normally.
Click to expand...
Click to collapse
thx!! im in download mode now

Im in Recovery now. When i try to wipe it says it cant mount /data, /cache, etc.
Also Restore doesnt work because of this. I tried to Repair. System seems to be repaired, but /data fails to repair. Also unable to repair cache.
What to do?
(needless to say i first flashed the correct Recovery )
In Windows Explorer i see only external sd

Somehow i seemed to fix /data en /system. But not cache and dalvik.
I restored a nandroid backup and it boots until LOS animation now. But there its stuck. (but at least i passed Android logo now)
Installation passed pretty good, only in the end it said cache wasnt mounted.
Any ideas?

alright no clue how but its fixed now lol