Related
The phone seems to be stuck in an infinite battery loop.
1) With the battery in, not using the charger.
It first boots into a grey battery for a couple of seconds and then it gets to a green charging battery. I can hear a short vibration, and it boots again into the grey battery and then into the green one. The phone is stuck into that loop until the battery drains.
2) With the battery in and the USB cable plugged in.
The phone boots into the grey battery and then into the green one. It stays there forever. No vibration sound and no rebooting. It keeps charging until hitting the 100% message.
Now, a few days ago I was able to hold the power button down and the phone would reboot normally. I could use the phone for a few hours until, all of a sudden, it would turn off and boot again into the battery loop. Holding the power button and rebooting normally would ONLY work with the USB cable in. If I unplugged the USB cable, the phone would be stuck in the battery loop.
A couple of days ago, I noticed that when I managed to reboot normally and pressed the power button, the phone would ask me if I wanted to restart, and a couple of seconds after that it would reboot into the battery loop.
Now holding the power button down with the USB cable in won't do the trick anymore. It is as if the power button is disabled or something.
Is there a fix for this? If I hold the volume button down I can get to the download mode (Odin Mode). THe info I get is as follows:
Product name: SGH-i777
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung Official
The only way to get out of the download mode is by removing the battery.
Any ideas as to what's going on here?
thanks!
Looks like the culprit is the power button.
I flashed the newest Samsung firmware using Odin in download mode, and I could reboot normally after flashing. I'm using Auto Screen On/Off to wake up the phone, and it does a good job. The Power Off Button apps didn't seem to work, though.
Thing is, if I power off the phone or restart it, it goes into the battery loop again, and the only way to reboot normally that I know is by flashing the stock firmware again.
Is there any easier, faster way to reboot normally with a broken power button?
thanks!
cirerita said:
Is there any easier, faster way to reboot normally with a broken power button?
Click to expand...
Click to collapse
You could try this (it's another power button app https://play.google.com/store/apps/details?id=com.painless.pc). I've used it in the past with great success.
If it doesn't work for you you're currently not rooted - I know your stats show you've downloaded a custom binary, so you shouldn't have any problems.
Post back if you do, and also give us more information regarding which rom you're on.
Thanks, that app is really useful.
I used a custom rom a while ago but then I switched back to stock. I'm using the latest one from Kies (4.1.2, I think to recall). I use Framaroot to root the phone so I can use some apps I like.
Phone still reboots randomly. Maybe I need to clean the cache. Is there an app for doing that while running Android?
Alternatively, is there a kernel/rom that allows me to reboot normally, bypassing the battery loop? The Odin download mode takes too long because I have to flash the stock firmware, and the stock Recovery mode is useless to me because my power button is broken.
IS it possible to access Recovery mode with a broken power button?
thanks!
Sure, but the app I linked allows you to boot to recovery also.
A good custom kernel for a rooted 4.1.2 would be AJK 4.9, the No Swap version I believe. You'd be better off reading the op in the AJK thread.
Thanks, I'll take a good look at the AJK thread. Is it any better than the Siyah kernel?
Problem is, if the phone reboots randomly, then I'm stuck in the battery loop again and I need to flash the stock firmware yet again to be able to reboot normally and bypass the battery loop. I would need some sort of custom boot which I could access pressing the volume button, and which would allow me to reboot bypassing the battery loop.
SteveMurphy said:
Sure, but the app I linked allows you to boot to recovery also.
A good custom kernel for a rooted 4.1.2 would be AJK 4.9, the No Swap version I believe. You'd be better off reading the op in the AJK thread.
Click to expand...
Click to collapse
Just flashed AJK 4.9 and no more random rebootings as of now... Plus, if I reboot manually, it does not get into the dreaded battery loop. So far so good. Thanks a lot for the tip.
cirerita said:
Thanks, I'll take a good look at the AJK thread. Is it any better than the Siyah kernel?
Problem is, if the phone reboots randomly, then I'm stuck in the battery loop again and I need to flash the stock firmware yet again to be able to reboot normally and bypass the battery loop. I would need some sort of custom boot which I could access pressing the volume button, and which would allow me to reboot bypassing the battery loop.
Click to expand...
Click to collapse
AJK's Kernel is based off Siyah.
Ok, so I was preparing to update to 5.02 now that the UK version is out, but it seems my phone has completely lost recovery.
I'm sure I installed TWRP recovery previously, and I'm currently still on 4.4.4 Rooted with SuperSU installed and I installed TWRP as part of setting that up. However, my phone now will not boot into recovery at all. When I power on the phone, there is no notification LED for me to start pressing Volume Up or Down, it just boots normally into Android. If I just hold down the power button until it turns on, then hold the Volume Down button, the phone vibrates a few times, then just boots normally.
The only thing I can think that's changed is that the phone doesn't have the original MicroSD card in it that I used to have (and that one I no longer have access to).
I have tried re-installing TWRP using this thread, http://forum.xda-developers.com/showthread.php?t=2785598, and running the install.bat on the Z2-lockeddualrecovery2.8.10-RELEASE version, and this seemed to go through the process successfully, but no luck. The phone just rebooted to normal Android rather than recovery, and I'm still only able to boot to normal Android, so it seems I've lost recovery entirely.
So is there any way I can get TWRP recovery back on the phone so I can proceed with installing a pre-rooted FTF of 5.02?
EDIT/UPDATE - Ok, I went into SuperSU on the phone and had it forget all of the current Superuser access for Busybox and ADB, then re-ran the installer. This time when the phone rebooted it booted into PhilTouchZ recovery rather than TWRP that I was expecting...? Or is it the same thing?
EDIT/UPDATE 2 - Ok, powered off the phone, then powered back on holding the Volume Down button. Now in TWRP. I have to re-learn Android every time I update/re-root
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
Here are the steps to follow that worked for me to obtain Root on my Samsung SM-J120W Android 6.0.1 which I bought outright from Wind Mobile Canada. This method seems to work for other providers as well, but has not been tested by me. However, others in this thread have since rooted with Chatr (Rogers) and Koodo (Telus). This is great news!
Proceed at your OWN RISK. If you are successful, or successful rooting the SM-J120W that is with a provider other than Wind Mobile Canada, please post it here so others know!
In preparation for this process I performed a Software Update within Android, prior to rooting to ensure that I had the most up to date Android version available. From previous experience, I would suggest that you do not perform a Software update after rooting as it may remove root.
With respect to compatibility, on my phone under Settings > About device > Software info, the Baseband version of my phone, after ensuring the most recent update, was J120WVLU2AQA1 with Build number MMB29K.J120WVLU2AQA1 and Android security patch level January 1, 2017. These versions should match before you continue. To perform an OTA Software Update, on your phone Enable Wi-Fi then navigate to Settings > About Device > Download updates manually, then follow the instructions.
I used a Windows PC to interface with my Android. I have included a link below to a zip of all the files you will need in my Google Drive.
You should have some experience with Android recovery environments / flashing prior to proceeding at your OWN RISK. I will not be held liable for any damages related to this method.
Having said that, let's begin!
1. Download this zip archive from my Google Drive to your PC https://drive.google.com/open?id=0B1iPMyk4G2_-a0ZENXVETjNPT1E.
2. Extract Samsung SM-J120W Rooting Files.zip to your PC, then follow the instructions below on file usage for the files extracted from within.
3. Copy SR1-SuperSU-v2.78-SR1-20160915123031.zip from your PC to your phones internal storage.
4. Install Samsung USB Drivers SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.61.0.exe on your PC.
5. Extract Odin_3.12.3.zip to your PC.
6. On your phone, Open Settings > Developer options > Enable OEM unlock and Enable USB debugging.
* If under Settings there is no Developer options menu, tap About device > Software info > then tap Build number 7 times which will enable Developer options in the Settings menu.
* I was asked for a PIN for OEM unlock, it was my lock screen PIN.
7. Power off your phone. Remove the back cover from your phone. Connect your phone to your PC with a USB data cable. Power on your phone in Download Mode. (Press and hold Vol Down + Home + Power until you are presented with a warning regarding a custom OS). Press Vol Up to continue. You should now see ODIN MODE in red text at the top of the screen and a "Downloading... Do no turn off target" message.
8. On your PC, run Odin by opening Odin3_v3.12.3.exe. Under ID:COM the background should have turned blue. Under Log it should say Added!! Under Options, uncheck Auto Reboot and check F. Reset Time if it is not already checked. Click AP and select the twrp-3.0.2-0-b2-j1xlte.tar.md5 file in the Open dialog. Click Start.
9. Once Odin indicates PASS! in green at the top, flashing is complete. Now remove the battery from your phone. Unplug the USB data cable from your phone. Your phone will now be completely off. Click Exit to close the Odin program.
10. Replace the battery and back cover. Power on your phone in Recovery Mode. (Press and hold Vol Up + Home + Power until you see the blue TEAMWIN logo splash screen).
11. Now that you're in the TWRP Recovery environment, it should say Unmodified System Partition at the top. Tap Never show this screen during boot again, then Swipe at the bottom to Allow Modifications.
12. Tap Install, browse to & select the SR1-SuperSU-v2.78-SR1-20160915123031.zip file you copied to the Internal Storage in Step 3. Tap Reboot after installation is complete, then Swipe at the bottom to confirm Flash.
13. Your phone should boot normally into Android with SuperSU installed in your apps. Configure SuperSU to your liking and test for root by installing a Root Checker app if you wish.
* First boot after rooting may take a few minutes. It can also boot loop a few times. When I performed this on my phone, it did take a little while longer to boot than usual, but I didn't experience any boot loops and all went well.
* I have noticed that some "older" apps that require root, complain I am not rooted. For example, in the past on other phones, with earlier Android Versions, I have used ROM Toolbox Pro to overclock my CPU when rooted; and it no longer works with Android 6 MM. I suspect that the behaviour of Rooted Android 6 MM is a bit different than previous builds. I now use Kernel Adiutor (ROOT) and that works fine for overclocking and doesn't complain about not being rooted. Other newer apps that require root like Root Explorer, AdAway, Busybox Installer, Trimmer (fstrim) all work great!
Please share your experience or comments and suggestions related to this guide!
Updated Sep 13 2017 - Thank you to everyone for your feedback and suggestions.
Please provide a link
Hi, please provide a link of the file twrp-3.0.2-0-b2-j1xlte.tar.tar, I can't find it in google, thank you
https://drive.google.com/open?id=0B1iPMyk4G2_-a0ZENXVETjNPT1E
I rooted it successfully, thank you!
However, I am now having some issues installing xposed framework, have you tried install xposed framework in this phone model?
I installed this custom version of Xposed: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 because with the original one, the phone doesn't startup (it stays in the samsung screen).
That custom xposed version was installed good, and phone started up good, but when I install and activate an xposed module and reboot the phone, I get the same problem, phone stays in the samsung screen.
I hope it's possible to use xposed framework in this phone model, I will open a thread soon about this issue, thanks for the help!
lilandroid said:
I rooted it successfully, thank you!
However, I am now having some issues installing xposed framework, have you tried install xposed framework in this phone model?
I installed this custom version of Xposed: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 because with the original one, the phone doesn't startup (it stays in the samsung screen).
That custom xposed version was installed good, and phone started up good, but when I install and activate an xposed module and reboot the phone, I get the same problem, phone stays in the samsung screen.
I hope it's possible to use xposed framework in this phone model, I will open a thread soon about this issue, thanks for the help!
Click to expand...
Click to collapse
No problem, your welcome. I have not tried to install xposed yet. I don't have a use for it right now. If I attempt and am successful, I will let you know!
lilandroid said:
I rooted it successfully, thank you!
However, I am now having some issues installing xposed framework, have you tried install xposed framework in this phone model?
I installed this custom version of Xposed: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 because with the original one, the phone doesn't startup (it stays in the samsung screen).
That custom xposed version was installed good, and phone started up good, but when I install and activate an xposed module and reboot the phone, I get the same problem, phone stays in the samsung screen.
I hope it's possible to use xposed framework in this phone model, I will open a thread soon about this issue, thanks for the help!
Click to expand...
Click to collapse
I got it working on mine just now. I followed the procedure at this site: https://devs-lab.com/download-install-xposed-for-samsung-devices.html.
I was following that tutorial method, I retried just a few minutes ago with a different approach, and it worked, I will share it here maybe someone finds it useful:
I got rid of everything (root and xposed) with a firmware and odin.
Then I installed supersu and xposed at one time in twrp, then I installed xposed apk, I activated a different module this time, then I turned off instead of rebooting. I waited a few mins and then I turned my phone on and it worked!
I don't know what exactly was the problem, but most likely it was just a module issue.
As always, thanks for the help!
Just posting to confirm that OP's instructions worked flawlessly for me. I had already soft bricked it once using another method, recovered from that, and then found this thread. Thanks a bunch for the tutorial!
4o4 said:
Just posting to confirm that OP's instructions worked flawlessly for me. I had already soft bricked it once using another method, recovered from that, and then found this thread. Thanks a bunch for the tutorial!
Click to expand...
Click to collapse
Awesome! Thanks for the reply
Not working for me, Everything goes great right up to reboot after flashing TWRP. Reboots from Odin into system I wait for complete boot, Power off reboot with Power Volume up and home.
10. Power on your phone in Recovery Mode. (Press and hold Vol Up + Home + Power until you see the blue TEAMWIN logo splash screen).
Click to expand...
Click to collapse
It boots to Andriod Robot saying installing update, Which fails, I try to get it to boot into bootloader via the menu after the install fails but reboots directly to system. Any ideas?
Unit is from Chatr not wind.
is it better, more wise to download the latest version of Supersu from the google play store and use that one, as I notice the one in the zip has a 2008 date
At Step 10 when I try to reboot the phone into recovery mode I don't get the Teamwin splash screen, it just says "Installing System Update" then "No Command" and goes straight to the normal recovery mode. Am I doing something wrong?
---------- Post added at 06:40 AM ---------- Previous post was at 06:03 AM ----------
fubar121 said:
Not working for me, Everything goes great right up to reboot after flashing TWRP. Reboots from Odin into system I wait for complete boot, Power off reboot with Power Volume up and home.
It boots to Andriod Robot saying installing update, Which fails, I try to get it to boot into bootloader via the menu after the install fails but reboots directly to system. Any ideas?
Unit is from Chatr not wind.
Click to expand...
Click to collapse
Exact same happnened to me, did you get it to work after?
Kevinthemew said:
At Step 10 when I try to reboot the phone into recovery mode I don't get the Teamwin splash screen, it just says "Installing System Update" then "No Command" and goes straight to the normal recovery mode. Am I doing something wrong?
---------- Post added at 06:40 AM ---------- Previous post was at 06:03 AM ----------
Exact same happnened to me, did you get it to work after?
Click to expand...
Click to collapse
No sir I did not I will let you know if I can get it to work. Please do the same for me.
fubar121 said:
Not working for me, Everything goes great right up to reboot after flashing TWRP. Reboots from Odin into system I wait for complete boot, Power off reboot with Power Volume up and home.
It boots to Andriod Robot saying installing update, Which fails, I try to get it to boot into bootloader via the menu after the install fails but reboots directly to system. Any ideas?
Unit is from Chatr not wind.
Click to expand...
Click to collapse
Did you Enable OEM unlock in Developer Options? Sounds like the FRP lock is active.
adamwestca said:
Did you Enable OEM unlock in Developer Options? Sounds like the FRP lock is active.
Click to expand...
Click to collapse
If you do get it to work after Enabling OEM Unlock, please let us know as your with Chatr, would be beneficial information knowing that another provider works also other than Wind (Freedom Mobile).
Thanks and Good Luck!
VonLigenstein said:
is it better, more wise to download the latest version of Supersu from the google play store and use that one, as I notice the one in the zip has a 2008 date
Click to expand...
Click to collapse
I would agree to update SuperSU from the Play Store after install. The version I included in the zip is 2.78 SR1, dated Sep 15 2016. Due to the complexity of the process, I have not tested an updated version, therfore have not included it in the guide.
4o4 said:
Just posting to confirm that OP's instructions worked flawlessly for me. I had already soft bricked it once using another method, recovered from that, and then found this thread. Thanks a bunch for the tutorial!
Click to expand...
Click to collapse
Your welcome, glad to help
Just wanted to say this worked for me, except I was having trouble booting into the Teamwin screen.
What I did was skip the end of step 9 where it says to let your phone reboot fully, instead I pulled the battery and the usb cord and forced it off, then went straight into recovery mode, never letting the phone reboot properly. Was able to get to the Teamwin screen just fine after. Everything else worked like a charm.
(Bought phone at Costco in Canada for use on Koodo.)
Mr Minister
[email protected] said:
Just wanted to say this worked for me, except I was having trouble booting into the Teamwin screen.
What I did was skip the end of step 9 where it says to let your phone reboot fully, instead I pulled the battery and the usb cord and forced it off, then went straight into recovery mode, never letting the phone reboot properly. Was able to get to the Teamwin screen just fine after. Everything else worked like a charm.
(Bought phone at Costco in Canada for use on Koodo.)
Click to expand...
Click to collapse
Yeeesss!!! That worked for me as well!
I've got my SM-J120W at Costco and I'm with Chatr
Yeeesss!!! That worked for me with pulling the battery at end of step 9 before reboot
My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
It will display the "Samsung Galaxy Tab S6 | Secured By Knox" logo screen for a few seconds, then switch to the blue "Installing System Update" screen (with the android logo). Installing System Update gets to 28% and stops. Then the rotating icon on the android freezes. Then the device reboots and starts all over again.
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Fedge7 said:
My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
It will display the "Samsung Galaxy Tab S6 | Secured By Knox" logo screen for a few seconds, then switch to the blue "Installing System Update" screen (with the android logo). Installing System Update gets to 28% and stops. Then the rotating icon on the android freezes. Then the device reboots and starts all over again.
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Click to expand...
Click to collapse
can you shut it down? try volume down and power button ? if it don't shut down, do this soon as it reboots, hold volume up and down and plug in usb cable to desktop/laptop usb port! it will boot into download mode!
N1NJATH3ORY said:
can you shut it down? try volume down and power button ? if it don't shut down, do this soon as it reboots, hold volume up and down and plug in usb cable to desktop/laptop usb port! it will boot into download mode!
Click to expand...
Click to collapse
I can't actually shut it down. If I start holding power+voldown right after it boots, the tablet does reboot before getting stuck at 28%. But it reboots--it doesn't power off.
I tried download mode and that actually seemed to work! Specifically, I left the tablet overnight in the reboot loop until the battery drained. Just now, I held down volup+voldown and plugged it into my laptop. I got the green "Warning/Custom OS" screen and then pressed volup to continue. The tablet rebooted pretty quickly after that (I'm guessing due to low battery) so I didn't get a good look at the download mode options.
Once I'm in download mode, can I factory reset the tablet? I don't need to preserve any data/apps/settings.
Fedge7 said:
I can't actually shut it down. If I start holding power+voldown right after it boots, the tablet does reboot before getting stuck at 28%. But it reboots--it doesn't power off.
I tried download mode and that actually seemed to work! Specifically, I left the tablet overnight in the reboot loop until the battery drained. Just now, I held down volup+voldown and plugged it into my laptop. I got the green "Warning/Custom OS" screen and then pressed volup to continue. The tablet rebooted pretty quickly after that (I'm guessing due to low battery) so I didn't get a good look at the download mode options.
Once I'm in download mode, can I factory reset the tablet? I don't need to preserve any data/apps/settings.
Click to expand...
Click to collapse
You cannot reset the tablet from Download mode afaik- You need to enter Recovery Mode to do that.
You can however, flash stock from Download mode using Odin (3.13.3 is best). If you're not confident with doing that, your best option is Factory Reset in Recovery Mode. Hold Volume Up and Power when the Tablet is booting, let go when you see the Samsung logo. The timing can be tricky, but you should be able to do it. Also, you can force a reboot with Volume Down and Power.
Alternatively, if factory reset doesn't work, since you're completely stock, you will still be covered under warrenty.
bartleby999 said:
your best option is Factory Reset in Recovery Mode. Hold Volume Up and Power when the Tablet is booting, let go when you see the Samsung logo.
Click to expand...
Click to collapse
Thanks for the suggestion. I have tried this many many times. I've tried letting go of the buttons at different times. I've tried holding volup while letting go of power. I've tried this a ton of different ways, and no matter what, the tablet always shows the "Installing system update" screen. Some googling has led me to believe that sometimes, when performing a factory reset, the "Installing system update" screen shows up right before the normal recovery screen. Is it possible that the tablet is trying to get to recovery mode, but can't get past this first step?
Fedge7 said:
Is it possible that the tablet is trying to get to recovery mode, but can't get past this first step?
Click to expand...
Click to collapse
Honestly, I don't know - I'm not an expert but I guess it's possible that the update failed and corrupted both System and Recovery.
You'll be covered under warrenty, so maybe just return the Tablet from where you purchased or direct to Samsung, could take a while given the current situation though I guess. If you have a PC, then I think the best option would be to just flash stock yourself, since that's probably all Samsung will do. Even if that doesn't work you'd still be covered under warrenty, as far as I'm aware attempting to flash stock doesn't trip Knox.
Here is solution to unbrick your device!!!
Fedge7 said:
My Tab S6 tried to auto-install an update yesterday (it is rarely connected to Wifi/internet). It then rebooted. Since then, it's been stuck in a boot loop.
...
Edit: the tablet is 100% stock. It's not been rooted or had any custom ROMs loaded.
I have tried getting to recovery mode, by holding power+volup while it boots. This doesn't seem to change the behavior at all. Any advice is much appreciated.
Click to expand...
Click to collapse
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
FYI, I got in this situation, and the previous post did work for me, just takes good timing! Thanks!!!!
Same issue today for me. My tablet showed different screen with green and red text, it allowed me to delete app data, then booted into safe mode, then i had to do factory reset and now i am screwed, as it is refusing to restore any apps and their settings. I will try to flash it back to Android 9, maybe then it will do the restore. I forgot to do any manual backup to SD or so.
Edit: the device upgraded to 10, but reset itself after about 10 minutes of use.
Edit2: i found what caused it. It is caused by Nova Launcher, if i try to set wallpaper.
Just found a news article that there is a RGB/sRGB problem with wallpapers. It might be the problem i had.
I am adding a screenshot of the result.
Yeah, I had that kind of reboot loop from a wallpaper that I downloaded
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Bravo!!
Works for me.
Many thanks
I can get into download mode. But it kicks me out within a few seconds. Any help please
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Hi,
Really need your help, after I updated my firmware using Odin, updated BL, AP, CP, CSC, my tab cannot boot up stuck in logo. Doing the Power + volume up leads me to different screen now. I cannot access recovery mode or download page anymore,
What must I do? Pleasssee help. Added the pic, after doing hard reset (power + vol up)
I cannot connect back to Odin also. Always setup connection failed.
Please help. Really messed up big time
Just a thought... Can this be restored from service center?
Thank you in advance.
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Genpis said:
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Click to expand...
Click to collapse
Did you use HOME CSC or the non HOME CSC when flashing?
Genpis said:
I have the same problem with a Tab S6 Lite, it is in bootloop and does not let me enter the recovery mode, I can go into download mode and I flashed the latest original firmware Android11, Android10 etc., . I tried them all but always goes in bootloop, and also the bootloop occurs only if I connect the usb cable to the PC, without any sign of life. Do I still have hopes or have I compromised the motherboard?
The reason for all this is because I had followed a guide to give root permissions with magisk, I did everything right, only that the guide was with Android10, while I had Android11 and I was deceived by the fact that in the title of the guide there was written "guide 2021"
, so I did not check the compatibility of operating systems, I was a fool, I know, I hope so much that I did nothing irretrievable, it's my son's tablet!
Click to expand...
Click to collapse
Try to install a castom rooted rom which has pre installed also Twrp.
[MAGISK Rom / Firmware base convertor) 420rom-T860/5 - V13.3- CUE1 - ANDROID 10 - OneUI 3.1 - Sec Patch 05/2021 - Released 06/07/2021
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY TAB S6 WiFi/4G (T860/5)! 420rom Telegram-Group: Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means...
forum.xda-developers.com
Download the android 11 last rooted rom from there. You install it with odin as as a normal original rom.
Disable in odin auto reboot. After rom install, restart manually and press the correct buttons immediately to boot in Twrp and not to system. Format (not wipe) data from there and reboot to system. If you are lucky it will work..
(I hope you unlocked bootloader before try to root. If you haven't unlocked bootloader this won't work also).
Moe5508 said:
Here is solution to unbrick your device!!!
Despair not...I have just come from resolving this exact situation not 30 minutes ago. I'd been trying to flash (using Odin as I decided to stay on Stock and not root this device, for a change) the latest OneUI2.1 releases for my device (SM-T865 - LTE version) and boom in the middle of the Odin update, the flash just failed...I then couldn't reboot and get into neither Recovery, nor Download Mode because it appears my bootloader and recovery both got corrupted.
Here's what you need....
1. Odin app for PC (am on Windows)
2. Your device's Stock firmware (sammobile firmware archive)
3. You will need someone to help you boot the device directly into Download mode (and this is the tricky part because for most of us we are used to get into Bootloader by using the key combination (from Powered Off device) Vol+ and Power On at the same time to get into stock recovery and then scrolling down to option 2 in this menu, "Reboot to Bootloader". Well now you are going to boot directly into Bootloader mode. Here's how you do it...
4. Get your friend to line up the USB-C cable into the port of the device, but DO NOT press it in...yet
5. Press Power off and Vol- buttons at the same time to turn off the device
6. And now you have to to be super fast: if device starts to turn on on its own, YOU press and hold Vol+ and Vol- both at the same time while YOUR FRIEND pushes the USB cable fully into the port - you should now have booted directly into Download mode. (if not repeat this, and remember to be super fast and sync with your friend pushing in the USB cable)...
7. When you get into Download mode, then you are home and dry...
8. Select ONLY the Bootloader file (BL...XX...) in Odin, make sure only "reset time" and "reboot" are ticked, and flash
9. When device reboots, press Vol+ and Power combo to get back into Bootloader mode again...but I think device will reboot into Download mode on its own
10. Now select all the files from your Stock file into the various tabs (BL, CP, CSC, AP...) do not select HOME_CSC as we want to flush this device clean...
11. Flash, and voila...success - you will have lost all your data but rather that than losing the device...
12. Feedback here and let us know if this works? For reference for others in the future...
Click to expand...
Click to collapse
Why flashing only the bootloader first? At the moment I'm trying to recover my s20 fe from a bootloop without losing my data
sosimple said:
Try to install a castom rooted rom which has pre installed also Twrp.
[MAGISK Rom / Firmware base convertor) 420rom-T860/5 - V13.3- CUE1 - ANDROID 10 - OneUI 3.1 - Sec Patch 05/2021 - Released 06/07/2021
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY TAB S6 WiFi/4G (T860/5)! 420rom Telegram-Group: Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means...
forum.xda-developers.com
Download the android 11 last rooted rom from there. You install it with odin as as a normal original rom.
Disable in odin auto reboot. After rom install, restart manually and press the correct buttons immediately to boot in Twrp and not to system. Format (not wipe) data from there and reboot to system. If you are lucky it will work..
(I hope you unlocked bootloader before try to root. If you haven't unlocked bootloader this won't work also).
Click to expand...
Click to collapse
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
jointer said:
Same issue today for me. My tablet showed different screen with green and red text, it allowed me to delete app data, then booted into safe mode, then i had to do factory reset and now i am screwed, as it is refusing to restore any apps and their settings. I will try to flash it back to Android 9, maybe then it will do the restore. I forgot to do any manual backup to SD or so.
Edit: the device upgraded to 10, but reset itself after about 10 minutes of use.
Edit2: i found what caused it. It is caused by Nova Launcher, if i try to set wallpaper.
Click to expand...
Click to collapse
did you managed to not lose your data?
jrdef said:
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
Click to expand...
Click to collapse
Wiping cache partition in Recovery and reflashing the firmware are basically your only 2 options
jrdef said:
Any tips in recovering my stock s20 fe from a bootloop without losing data? already tried Odin but without success the first try
Click to expand...
Click to collapse
Flash in odin the same rom you had. There are 2 csc files in rom, which you use 1 in odin one. Try use the "home csc". Home csc keep KEEPS your data. If you're lucky it may work. (It would work in keeping your data 100% if your rom was ok. Because it isn't you have some changes to work.).
You must try with same rom or newer.
CSC – If you flash the CSC file, it’ll perform a factory reset of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same state as it was when you purchased it. Go with CSC if you want a clean installation.
HOME_CSC – On the other hand, if you want to keep your Samsung phone’s data and settings even flashing the stock firmware, you can select the HOME_CSC file.