Since i flashed TWRP "2.3.1.1 grouper" for my Nexus 7, on the Recovery partition (for some reasons it didn't had a Recovery software installed anymore), it seem like i have to hold the Power button for 10-15 seconds before the Google logo show up on the screen. Before that, i only had to hold Power button for about 2-3 seconds (default Power button holding time).
At first i was freaking out, thinking i corrupted something by flashing this and the device just refused to boot up. But then i thought "let's see if the tablet boot up if i hold the Power button long enough"
Why is it doing that suddenly? Is there a way i can shorten this?
infos:
-i have Glazed Jelly Bean 2.1 installed
-i used WugFresh's tools to flash TWRP, while i selected "Custom ROM - JB" in the Android version.
-i changed my boot animation using ROM Toolbox Pro (i don't think it cause the problem, as it was booting just fine before)
strange, when i enable Debugging, i just have to hold it for 3-4 seconds (normal). When Debugging is off, i have to hold it for about 15 seconds. Any idea why?
Do you always leave your Debugging feature on? it seem like it only give access to other hidden folders you wouldn't see normally, on your PC.
I tried flashing the bootloader from here.
Then it went crazy or something, and got stuck on the powered by android logo, however i was still able to boot into download mode the first time by holding power + volume down button
to simulate a battery pull then quickly holding the volume down + home + power again. Then I tried flashing TWRP immediately in an attempt to make it work because i have a flash drive to microUSB adapter that allows me to read flash drives from my phone ( so that I can flash the rom properly ). The last time I was in TWRP there was 0 things in my storage everything was wiped after I flashed TWRP the first time
Now im trying to go back into download mode but it just wont let me after the battery pull.
1.) After simulating the battery pull, I immediately let go when the screen is dark.
2.) I immediately attempt to go into download. It shows the powered by android for a second, then flickers then it's back to the powered by android again.
3.) I think my recovery and download is screwed. Or something is going on
=== EDIT ===
I managed to get into download mode and flash back my stock rom.
I think the phone must have read my Power & Volume Down & Home button as the battery pull because I let go of all buttons completely before doing it.
Steps to get out of bricked hell:
• Hold Power & Volume Down until the phone turns off
• Immediately without letting go of the Power & Volume Down button, press the home button as well.
• If the timing is not correct just retry.
I recently updated my Samsung Galaxy Tab A T280 to the latest firmware and I lost my root. So this afternoon I re-rooted it. Or I attempted to, anyway. Everything seemingly went fine, and I booted into TWRP just fine. I went to flash the ROM and I also selected wipe cache/davlik cache to be done as well, and tapped reboot. My device then turned off and when it started the reboot, it got stuck on the Samsung Galaxy Tab A logo screen and would not move or power off by holding the power button (I tried for a LONG time by using a rubber band to hold it down so I didn't have to, with no luck), and every other combination of buttons wouldn't do a thing, except for holding power + vol down, which made it turn off and back on, but it wouldn't finish rebooting and it just got stuck at the Samsung Galaxy Tab A logo again. So then I thought that maybe plugging it into a charger might not be a bad idea, and after holding down power + vol down again, it turned off and turned on and showed a battery with a charging symbol. I've had it plugged in for an hour and it does not show a charge or do anything except for go back to that boot logo if I unplug it from the charger and again hold down power and volume down separately.
I know it's not hard bricked because it is somewhat responsive so I think there's a chance to fix it, hopefully. I just want it to turn on and fully reboot into anything or in any way that will allow me to be able to fix the issue. My computer will not recognize the device so ADB is not an option right now unless I'm wrong.
Thanks a lot guys, I am so confused and could really use some advice.
What firmware did you install
Try to install original firmware via software "Samsung Smart Switch" on your PC with connected tablet.
I too recommend that you try installing the last firmware that you were on via Odin. Also, when you hit that screen lock issue after a firmware flash, where only the Samsung logo appears do this:
1. press and hold Home + volume up and volume down along with power button (that's all 4 buttons). Hold it there for at least 20 seconds and it should power off.
2. Once the device powers off keep holding the buttons but let go of the volume down button.
3. Once the tablet starts to power back up again release the power button and then in about 1 to 2 second release the rest of the buttons.
This should get you back into recovery. You should at least be able to restore any backup, that you should have already, on your external micro SD.
Good luck.. : )
"Chance Favors the Prepared"
the above post is 100% right. Reboot back into recovery and you'll be good to go. Also twrp has a option to reboot back to recovery so this doesn't happen, just a fyi for future knowledge. Best of luck..
You tried to flash a rom with twrp?
You need to flash stock firmware with odin.
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Dharmost said:
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Click to expand...
Click to collapse
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
D4ND310 said:
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
Click to expand...
Click to collapse
I didn't dip the smartphone into a cup of liquid, i just took a piece of cotton, poured a bit of nail pain remover (don't know the exact name in english, sorry) on it and then scratched the part where the chewing gum was on (on the soft touch back key, which works 100% fine).
I am trying using the method you described, but it seems i can't go into recovery. Maybe i'm not quick enough! will keep trying. If you have any other suggestions i will be glad to hear that!
You could try to make a USB jig, or buy one off of eBay. They're really cheap. Its basicly just a resistens that force the phone to download mode. It have worked fine for all my Sammy's including A310 so it probably works for A (15) series as well.
Just put it in USB connector and press power for a few secs and you should be in download mode.
Just an idea if everything else fails
Sent from my Honor 5X using Tapatalk
go to samsung
A hardware problem could NEVER be fixed by software ways... Unfortunatelly...
It seems that liquid made some changes on your PCB (maybe dissolved some isolators inside??)...
Anyway, go to service or replace it!
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Dharmost said:
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Click to expand...
Click to collapse
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
babyyeobo14 said:
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, but still couldn't get into recovery. I think the home button is really broken, therefore i need to access recovery in another way.
Cause i flashed the stock samsung firmware twice with odin and i can't still start the phone properly, every guide says that a wipe of cache and dalvik solves the situation. But i need to get into recovery for that.
I can't go into recovery with normal procedure probably because the home button is not working, and all the guides about adb commands say that you need to plug in your phone when it has fully started. So i either need a way to force the device into recovery with my computer, or a firmware that once flashed doesn't give me bootloop
I have Samsung Galaxy A20 phone, stock firmware started lagging terribly after upgrading to One UI 3.1, so I decided to install Lineage OS (I've tried some custom roms like Sakura Project previously so I'm familiar with the process) and Gapps Pico (Arm64) for Android 11 which I have on my phone. I already had TWRP installed, with its help I performed data formatting and formatting of the Dalvik Cache, Cache, Data, Internal Storage and System partitions, after which I installed an archive with Lineageos 18.1 and Gapps to install, the installation went without errors and I pressed the reboot button, after which my phone, after a message from Samsung that I lost my warranty (already a common message, had it since rooting my device) and pressing the Power button to continue booting, just either turns off, or does not show the image.
I tried to force restart the phone (if it is still on) by pressing both the Volume Down and Power buttons for ~20 seconds and the phone indeed rebooted, showed the same warning again and the image is black again. I can't get into recovery by pressing the power button and volume up, nothing happens (or the screen is just black, I'm unsure about it), just the usual pressing/holding of the power button does nothing. I'm not sure if there is an image or if the phone just refuses to turn on, I don't have a suitable cable to bring the image to the computer screen. When the screen is black and I plug in the power cable, there is no vibration, which usually indicates that charging has started, also the screen does not show a charging indication (a circle with a lightning and a percentage usually), but if I perform hard reboot (I believe that's what it's called when you hold Power + Volume Down buttons) it shows me white circle and just a lightning icon which usually indicates bad connection, I guess, so when the cable is plugged in I cannot reboot using Power and Volume Down at all for some reason, it just shows me bad power connection indicator. Also, I cannot perform hard reboot when the cable is plugged in, it shows me that circle with a lightning for a split second and that's it.
I can assume that it's an unofficial Lineageos rom specifically for the Galaxy A20, which I downloaded from Sourceforge. What can I do to check the operability and preferably fix this failure?
Lmao, solved it by doing some kungfu, with the cable unplugged did the Volume Down + Power thing and then plugged the cable in and as quick as human being can be I held Volume Up + Power to get into TWRP and from there I was able to reboot into download mode and flask stock firmware using Odin (v 3.14 in my case)