Database Users

How to boot into Clockwork Mod Recovery from Power Off

I've had a Droid Incredible (AMOLED) for sometime, Unrevoked Forever. Flashed many, many ROMs and kernels, and numerous recovery backups.
Picked up a Droid X yesterday (still have my Dinc). Rooted using Z41, and have permanent root. Paid for and downloaded Bootstrap, and had ROM Manager from my Dinc.
I've spent a good six hours reading the various "how to" threads and Googling, but I'm not finding the solution to my issue.
I can boot into Clockworkmod Recovery from within Bootstrap.
But, I cannot figure how to boot into Clockworkmod Recovery from power off state. When I hold the Home button while powering up, hitting the Search button boots my DX into the stock recovery, NOT Clockworkmod Recovery.
I guess my question is, how / is it possible to make Clockworkmod Recovery the default recovery when booting from power off?
Looking forward to getting to know the DX community on XDA.

To boot into clock work from power off...hold vol down then press power. Hold about 10 seconds. You should be good to go...
Sent from my DROIDX using XDA App

drewbe70 said:
To boot into clock work from power off...hold vol down then press power. Hold about 10 seconds. You should be good to go...
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
That is the method on the Dinc, which I'd tried. But, just now did it and released the power button after the Moto logo appeared and continued to hold the vol down, and there was the familiar Clockworkmod Recovery glowing green.
Old habits.
Thanks!

Cool, glad it worked. Was not sure about the exact timing though!

tbcpn said:
That is the method on the Dinc, which I'd tried. But, just now did it and released the power button after the Moto logo appeared and continued to hold the vol down, and there was the familiar Clockworkmod Recovery glowing green.
Old habits.
Thanks!
Click to expand...
Click to collapse
Well, so I flashed a ROM (ApeX 1.3 which runs well), but once again I can boot into Clockworkmod Recovery via Bootstrap, but cannot (or have not found a way) boot into Clockworkmod Recovery from power down, even using the above method that worked with the rooted stock .340.
Not a biggie unless something bad happens, of course.
Thoughts? The ROM? Me?

tbcpn said:
Well, so I flashed a ROM (ApeX 1.3 which runs well), but once again I can boot into Clockworkmod Recovery via Bootstrap, but cannot (or have not found a way) boot into Clockworkmod Recovery from power down, even using the above method that worked with the rooted stock .340.
Not a biggie unless something bad happens, of course.
Thoughts? The ROM? Me?
Click to expand...
Click to collapse
From Koush's website:
What if my phone won't boot? How do I get into recovery without the app?
When the hijacker runs, it will automatically create the "/data/.recovery_mode" file after it finishes. This tells the system that the next time it boots, it should boot into recovery. But, when the system starts, the Droid X Recovery Bootstrap will then delete that file when Android is fully started, to prevent you from booting into recovery. So what does this mean? If you fail to boot, simply pull your battery, and your next boot will be into recovery (unless your /system is *really* hosed, in which case you need to SBF).
I'd probably just press bootstrap recovery in the app every time you turn your phone on. So just in case you DO need it next time you boot up, it'll be there. Damn moto and their locked phone..

Sheen160 said:
From Koush's website:
What if my phone won't boot? How do I get into recovery without the app?
When the hijacker runs, it will automatically create the "/data/.recovery_mode" file after it finishes. This tells the system that the next time it boots, it should boot into recovery. But, when the system starts, the Droid X Recovery Bootstrap will then delete that file when Android is fully started, to prevent you from booting into recovery. So what does this mean? If you fail to boot, simply pull your battery, and your next boot will be into recovery (unless your /system is *really* hosed, in which case you need to SBF).
I'd probably just press bootstrap recovery in the app every time you turn your phone on. So just in case you DO need it next time you boot up, it'll be there. Damn moto and their locked phone..
Click to expand...
Click to collapse
That doesn't do it either. Must be the custom ROM.
Somewhat OT, but you're right about the "damn Moto and their locked phone." Coming from the Dinc, I'm not accustomed to this sort of hassle. Having said that, altho I've only had the DX for a couple days (and still have my Dinc), I am liking the big screen, albeit not as nice as the AMOLED, and the really solid build of the DX--it's a good phone. Looking forward to the Thunderbolt...

tbcpn said:
That is the method on the Dinc, which I'd tried. But, just now did it and released the power button after the Moto logo appeared and continued to hold the vol down, and there was the familiar Clockworkmod Recovery glowing green.
Old habits.
Thanks!
Click to expand...
Click to collapse
I am on .605 base running MIUI ICS on my Droid X, and this did not work for me. I need to be able to access clockwork to fix my phone. Somebady plz help me!

Zeklandia said:
I am on .605 base running MIUI ICS on my Droid X, and this did not work for me. I need to be able to access clockwork to fix my phone. Somebady plz help me!
Click to expand...
Click to collapse
Reboot your phone, when it's on the Motorola logo a blue LED will flash, when it does press the volume down button.
From there you can navigate to ClockworkMod Recovery.
Sent from my DROIDX using XDA App

Thank you so much!!!!!
YOU HAVE SAVED ME!!! Now where is that dang thanks button.
Is it possible to set up a MIUI / CM74DX-GB dual-boot with that menu?

Zeklandia said:
YOU HAVE SAVED ME!!! Now where is that dang thanks button.
Is it possible to set up a MIUI / CM74DX-GB dual-boot with that menu?
Click to expand...
Click to collapse
Bootmanager
Sent from my Shooter (CM7 Alpha 3) using xda premium.

Zeklandia said:
YOU HAVE SAVED ME!!! Now where is that dang thanks button.
Is it possible to set up a MIUI / CM74DX-GB dual-boot with that menu?
Click to expand...
Click to collapse
Not through that menu, but using Boot Manager you can dual boot roms. Your base rom must be 2nd init, however.
Sent from my DROIDX using XDA App

infazzdar said:
Reboot your phone, when it's on the Motorola logo a blue LED will flash, when it does press the volume down button.
From there you can navigate to ClockworkMod Recovery.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hello ALL.... I'm not sure what I'm doing wrong but none of these seem to work for me.....I rooted Droid X using D3 one click method it worked and got Droid X to root....I have not installed bootstrap or any type of booting apps but in the past I have and was still unsuccesful at getting into Clockwork recovery from power-off state......oh and I don't see any blue light...... please help

Having same issue as poster above: Can NOT get into CWM recovery. (Also have Rom Toolbox installed, and I can't get into Recovery via that app, either.)
Running Liquid 3.2, and no matter what I try, I can only get into stock recovery.
EDIT: Was able to get into CWM Recovery from ROM Manager: Select Reboot into CWM Recovery, then hold VOL DOWN button while phone reboots. Voila! (Still doesn't solve original issue, but it's progress.)

i rooted using the terminal method on mac. i cant post a link it wont let me but its on droid life. i cant figure out how to reboot into clockwork mod or stock recovery i want to flash this new liquid rom i downloaded. can someone tell me how to do this or provide a link i can use to help me? thanks.

I also have sbf'd liquid 3.2. I've had a terrible time with the radio. Wifi works, it doesn't. 3G works, it doesn't. Market works, it doesn't. So, I just sbf'd the rom again but the phone is stuck in a boot loop. I need to get into Clockwork to try "wiping", but I can't get in. Seems like it's yet another issue with liquid 3.2. Anybody have any ideas?

landmarkaudio said:
I also have sbf'd liquid 3.2. I've had a terrible time with the radio. Wifi works, it doesn't. 3G works, it doesn't. Market works, it doesn't. So, I just sbf'd the rom again but the phone is stuck in a boot loop. I need to get into Clockwork to try "wiping", but I can't get in. Seems like it's yet another issue with liquid 3.2. Anybody have any ideas?
Click to expand...
Click to collapse
After SBFing you won't be able to enter ClockworkMod Recovery. Use stock recovery to format data and cache.
Sent from my DROIDX using XDA App

I'm unable to boot into Clockword mod recovery as well when I choose to do so from the ROM manager... It just reboots my phone back that's all...
I'm on stock 605 and just rooted my phone - no boot strap or bootloader apps I've installed other than the CWM recovery 5.0.2.0 I installed through ROM manager v4.8.0.6
I'm able to boot into Stock recovery (Search button and then volume keys) but not into cwm recovery....
Any suggestions what I'm doing wrong ? I even tried volume down key during power up - doesnt seem to help. I dont see any blue LED either during the moto logo...
Thanks...
EDIT/UPDATE: I installed the Droid X bootstrap apk, Install bootstrap, and Reboot into recovery and that seemed to start up CWM recovery fine I guess ROM manager was not installing the right CWM boostrap... From the ROM manager I was selecting the Droid X, (had tried Droid X 2nd init as well as Droid 2 - didnt seem to make any difference that time)....

On blur roms you always have to use the Droid 2 Bootstrapper app before flashing ClockworkMod Recovery in Rom Manager.
Sent from my DROIDX using XDA App

USB Debugging
I was having a terrible time getting into any kind of recovery, Bootstrap, Rom Manager, etc., that is until I remembered something I read sometime back. I unchecked USB Debugging and then had virtually no problem with getting into recovery mode.
So, having said all that, check to see if your USB Debugging is checked or not. That might make a difference for you.

A500 suddenly died

Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.

Dopius_Fishius said:
Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.
Click to expand...
Click to collapse
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD

Moscow Desire said:
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD
Click to expand...
Click to collapse
Thanks MD. I looked up the threads you suggested, and after a lot of screwing around I have installed the APX drivers and used blackthund3r's APX Flash Util 0.3 (The link is broken to the current version) to attempt a recovery of my tab.
Its now sitting at an Acer screen, "Entering Acer Download Mode" while the flash util is sitting at:
Nvflash started
[resume mode]
It's been there for about 10 minutes now, no progress to report. Is it worth just sitting it out, or now that the damn tab shows SOME signs of life, can I just restart it and reset to factory?

And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...

Dopius_Fishius said:
And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...
Click to expand...
Click to collapse
erm for now i would make sure you have all backups of data, cpud etc,.. just incase. you can just sit em on your computer i always try to keep a nandroid of all 3 of my devices each month or so.:good:
edit: and of course keep the link for the thread MD recommended.

Gee. Sounds exactly like mine....
The only thing I haven't tried is an update .zip, but I don't hold out much hope.
Considering parting out at this point....

Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.

Dopius_Fishius said:
Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.
Click to expand...
Click to collapse
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD

Moscow Desire said:
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD
Click to expand...
Click to collapse
Tried the update.zip - nada
Tried timmiedean yesterday, went into Acer Download mode OK, failed....
If dolps is like mien, the first time he tries to go into recovery, it will crash again...

It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....

tennessee_titan said:
It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....
Click to expand...
Click to collapse
I told you maaaannnn, go see me cousin in Jamaica maaaannnnn. She do some good things you see
Glad it's running again.
MD

First, is this a SOD?
I can kill it by booting into recovery and get it back by using Blackthunder flash tool to go into APX and letting it sit for 20 minutes or so. Close the program, unplug, reboot and it is back. I would like to use timmiedean (td) and go back to square 1, but it fails at the image detect ( displays ICS 4.0.3 Civato as the current image, a red X for the new image). Has td been proven to work reverting from ICS? Will a boot recovery reflash and a new ROM flash solve this? Is there another way to get out of ICS back to HC?
Any suggestions/comments welcome!
EDIT: I flashed FLEXxx V4. Shut it off, problem still there....

Really frustrated. Trying to use the timmiedean tool, but it requires that the unit be shut off in the middle of the process, which kills it. Does anyone know the whereabouts of the blackthund3r revert tool, or the .apx package for his flash tool. I can't find it...

I'm done with this one. On Ebay for parts.... GONE!!!
Have an A100 now, rooted, unlocked,. on Relix
1 more A500 coming next week

A500 wont get past boot logo or CW recovery

I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!

Staples01 said:
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Click to expand...
Click to collapse
That's what happens when you run stuff from Dev's that don't adhere to GPL. Undoubtedly some leftover code from whomever it was taken from and "somebody" didn't bother to clean it out all the way. FYI, Team Rogue did ICS development for the Xoom tablet, and also some early CWM work. Guess we know where "somebody" got some code from
Ok, back to your current issue at hand. For starters, you're probably still on an HC Bootloader and probably running a really old version of CWM recovery. If you are going to run ICS or JB roms, I highly suggest you upgrade your bootloader to the patched ICS Unlocked bootloader. Also, I would update to the latest version of CWM. You can get it at his site.
I believe your next rom may be able to run on an HC bootloader, or so I've heard, but your CWM needs to be updated, and that's what probably threw out the errors.
You can find a guide for the unlocked bootloader installation in the Dev Forum. It's stickied.
Hope this fixes your issue. If not, post back.
MD

Staples01 said:
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Click to expand...
Click to collapse
All I can say is WOW!!

linuxsociety said:
All I can say is WOW!!
Click to expand...
Click to collapse
Yeah, its strange but doesn't surprise me.
OP, your partitions are also undoubtedly messed up as well. I suppose you didn't by chance write down your UID number did you? You may be able to get by with installing an ICS full update zip. Maybe.
MD

Soo...nothing. is it just a piece of junk now?

Staples01 said:
Soo...nothing. is it just a piece of junk now?
Click to expand...
Click to collapse
I wouldn't think it is 100% bricked, but I'd definitely ask on tegraowners.com since it is from one of their recovery/roms. Guess you may have already asked Thor about the issue though?

I have my cpuid but when i run the dotnetdetector to update the usb doesnt stay connected long at all.

Staples01 said:
I have my cpuid but when i run the dotnetdetector to update the usb doesnt stay connected long at all.
Click to expand...
Click to collapse
Are you trying to manipulate the A500 from a Windows PC or Linux? Notice you said Dotnetdetector, sounds like windows, but not familiar with it exactly. Maybe you could try using a live linux distribution (such as Ubuntu or Fedora) to try to get fastboot/adb and reflash the recovery partition with a known working recovery for A500. The teamrogue thing still puzzles me and I'm just curious if bits of Team Rogue's code has been pieced in with the A500 recovery you are trying to use, or if you may have got a hold of a recovery that was for a different device ? I'm not trying to say that you are a nub and flashed a recovery for the wrong device, but there is a possibility depending on where you obtained the rom from, that it could have been mis-labeled for your device ( but been for a different one) If it was for a diff device it would make sense why you can't do anything with it.
Let me get it straight how this happened.
1. You had CWM installed for A500 and recovery was working fine
2. You used CWM to try to flash a Thor ROM, in which the installation failed.
3. After reboot you have nothing but the Acer logo
4. When you boot back into recovery, it is no longer CWM, but a Team Rogue logo is displayed, and that is all you see?
That's the way I interpret the issue you are having anyway. Can you please send me a link to the ROM that you tried to install that triggered all of this. That way I can see exactly what the installer script attempted to do (because it very well could have tried to flash a diff recovery to your device and failed on something else)
Hope we can get things straightened up for you. Good luck again bud

No access to Recovery mode after getting into it once i9505

Hey guys,
i never flashed/rooted/modified my Samsung Galaxy S4 I9505 before. Sitting on my desk, my phone turned off suddenly. At the first moment i thought, that the battery is just empty. After i charged the phone and went away, i got back and saw, that it was rebooting (the whole time?)
As i said, i got never in contact with modding/flashing, so i had to read pretty much about these things. After several days of reading and trying i did this:
Tried to get into Recovery Mode with VOL Up and Power button to wipe - "recovery is not seandroid enforcing set warranty bit recovery" in blue, red and yellow.
Flashed several Stock ROMs by Sammobile. After every flash i flashed TWRP - no change.
I get easily into Download Mode to flash the Stock ROMs, no errors in Odin, didn't check autoboot and repartition
Yesterday i flashed I9505XXUFNA5 - Open Europe - KK 4.4.2 (four-pieced) sucessfully. Then i flashed TWRP and tried to get into Recovery Mode - same results, i thought. But after i put the phone on my desk to think about what to do next, TWRP Recovery Mode was starting. I was totally happy, but didnt want to do something wrong in my euphoria. So i put out the battery to read about what to do, allthough i knew i wanted to do a wipe. After i read i wanted to try it again - no chance! I couldnt get into recovery mode again. I waited, nothing happened. Tried it again and again.. and again. Then i flashed the Stock ROM again, flashed TWRP again - no change. Meanwhile did this 8 times again and i didnt get into recovery mode again. Thats absolutely illogical in my opinion.
Please help me to get out of this, i dont know what to do now... THANKS

Recovery is volume up, home, and power button?

audit13 said:
Recovery is volume up, home, and power button?
Click to expand...
Click to collapse
Yes, home is optional (as i read) but i press this 3 buttons. I pressed it in several variations, for example like one user here in xda: "right after it vibrates release the power button only, keep pressing the volume up and home buttons for another 5-10sec as Whosebat recommended..."

Home button is not necessary, just vol up / down + power button. I also have the same issue as you. I went to a GSM service earlier today and over there was another S4 with exactly the same issue. Looks like lifespan of our phone reached to an end?
http://forum.xda-developers.com/galaxy-s4/help/phone-stuck-boot-loop-flashing-stock-t3398068

alesu69 said:
Home button is not necessary, just vol up / down + power button. I also have the same issue as you. I went to a GSM service earlier today and over there was another S4 with exactly the same issue. Looks like lifespan of our phone reached to an end?
http://forum.xda-developers.com/galaxy-s4/help/phone-stuck-boot-loop-flashing-stock-t3398068
Click to expand...
Click to collapse
Just speculating, but: I didnt update to the firmware version, from which you couldnt get back to the earlier versions. The reason would be some safety reasons. I thought about a relation to that for a short period of time.

#push

harary said:
#push
Click to expand...
Click to collapse
I think "bump" is the word you're looking for
After you flash the stock ROM, does it actually boot into the stock recovery?

GDReaper said:
I think "bump" is the word you're looking for
After you flash the stock ROM, does it actually boot into the stock recovery?
Click to expand...
Click to collapse
No, i have never seen the stock recovery. I was 2 times in TWRP Recovery, but meanwhile i dont get there anymore. I have no clue why i get after doing exactly the same things into TWRP Recovery and 3 minutes later i dont get there anymore.
I came two times into TWRP with flashing I9505XXUFNA5 - Open Europe - KK 4.4.2, then TWRP 2.8.6.0.
With other Stock ROMs i got never into Recovery Mode.
Please help me

harary said:
No, i have never seen the stock recovery. I was 2 times in TWRP Recovery, but meanwhile i dont get there anymore. I have no clue why i get after doing exactly the same things into TWRP Recovery and 3 minutes later i dont get there anymore.
I came two times into TWRP with flashing I9505XXUFNA5 - Open Europe - KK 4.4.2, then TWRP 2.8.6.0.
With other Stock ROMs i got never into Recovery Mode.
Please help me
Click to expand...
Click to collapse
So stock recovery doesn't work either?
It's really weird.
Have you tried flashing TWRP using the app Flashify (requires root)?

GDReaper said:
So stock recovery doesn't work either?
It's really weird.
Have you tried flashing TWRP using the app Flashify (requires root)?
Click to expand...
Click to collapse
Unfortunately i cant start to install apps, because i am caught up in bootloop.
I tried to flash now a GT-I9505-Factory-Firmware-Full-Wipe-DBT with following files, but nothing changes except i get Warranty bit : kernel if i want to start normally without booting into recovery mode.

S5e won't boot

I am at a loss here. After almost 2 years of working flawlessly, my s5e won't boot.
The screen got frozen while using anydesk, and had to force a restart (power button + up and fown volume buttons).
I can see the Samsung logo for less than a second, and then it switches off. Without touching anything, after some seconds the same thing happens.
I tried charching it and similar behaviour: i see charging circle for less than a second, and off again.
I AM AT A LOSS.
I managed to boot it pressing power+volume_up buttons and this is what i see (attached). It can stay like that for a long time so I guess battery and it's connection to the tablet are fine.
PLEASE ANY HELP WOULD BE VERY WELCOME
UPDATE:
I have tried MANY things in the 6 hours since I wrote this post. I am able to put the tablet in download mode and ODIN (and my PC) recognizes it. I am able to flash VBMETA but now TWRP (fail).
At some point the tablet rebooted in normal mode (why?) but got frozen again and had to reboot it.
Anyone can point me to how to recover it? I don't mind right now to loose what is in the internal memory.

Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!

Abd El-Rahman El-Batal said:
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Click to expand...
Click to collapse
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?

iruiz2 said:
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
Click to expand...
Click to collapse
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro

Abd El-Rahman El-Batal said:
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Click to expand...
Click to collapse
It just loads the screen attached in my first post.

Try flash via Odin, it still in download mode with this warning.

The tablet was still covered by warranty so I called the seller and they took it to a Samsung repair store. They replaced the motherboard, so I guess it was not recoverable.
The bad news is that they updated to android 11, I was quite happy with old 9.0 because I had TWRP and Magisk working.
Thank you for all that tried to help.