Related
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
hiveNzin0 said:
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
Click to expand...
Click to collapse
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, thank you very much. I didn't know I had to press the 3 top buttons again after the dead droid screen, I thought it failed loading the Recovery Mode.
I have to setup my account etc again so I guess it is safe to say it worked.
Additionally, I tried this method after the recovery : http://forum.xda-developers.com/showthread.php?t=2015467
and it worked fine. My device has an unlocked bootloader and is rooted.
hey if someone could help me im stuck myself, after i had the dead android in recovery mode i tried to flash software with the toolkit in fastboot and now when i go to recovery its just a blank screen till i hold the bottom combo again and it takes me back to fastboot
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
maximepull said:
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
Click to expand...
Click to collapse
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
sharksfan7 said:
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
Click to expand...
Click to collapse
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Sorry. I don't know enough about these things to give more in depth troubleshooting advice. I just recently got my N10 & unlocked it and based on your original post, I thought that's where you needed help. But it sounds like you got past that and got it unlocked.
Have you tried downloading a factory image directly from Google and installing that? If it's locking up on a fresh install of any ROM, it very well may be a hardware issue. You may have to file a warranty claim if possible.
maximepull said:
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Click to expand...
Click to collapse
sharksfan7 said:
Have you tried downloading a factory image directly from Google and installing that?
Click to expand...
Click to collapse
^ that's your solution. If you dont know how to just pm me
Sent from my Galaxy Nexus using XDA Premium HD app
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
If I'm not mistaken, you would need to un-root your phone prior to installing any OTA Updates from AT&T. Also, you should only install the OTA Updates while using the stock recovery. So, you should re-flash the stock recovery and then attempt to complete the OTA Update. After that, you could re-install TeamWin, re-root and prosper.
Refer to this link on reverting back to stock... http://forum.xda-developers.com/showthread.php?t=2721435
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
Flash factory recovery, take the update, flash twrp back
or..
Titanium backup to freeze att update
an0ther said:
Flash factory recovery, take the update, flash twrp back
or..
Titanium backup to freeze att update
Click to expand...
Click to collapse
Just downloaded titanium back up. How do I freeze the update?
howyodoing said:
Just downloaded titanium back up. How do I freeze the update?
Click to expand...
Click to collapse
Try searching next time.. I see you are new here so i'll at least give you a link this time
http://forum.xda-developers.com/showthread.php?t=2752718
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
Click to expand...
Click to collapse
Good rule of thumb, do not install OTA updates on any modded Android device, without at a minimum doing thorough research on what will happen.
Depending on the device and the update in question, attempt to install an OTA on a modded device will remove root, possibly plug existing exploits (and render the phone unable to be rooted), or put you in a boot loop (as you have experienced).
In particular, OTAs require stock recovery in order to install. So if you have custom recovery installed, this is why the OTA install is failing (and why it keeps booting into TWRP).
Also, there is little (if anything) contained in the OTAs that doesn't get posted in a safe format (flashed from custom recovery) in the Development section soon after the OTAs start to roll out.
Solution for HTC OneM8 (continous restarting after update)
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
Hi, i have a HTC One M8, and when my first update popped, i was very enthuziast.
I accepted to download the update, installed it, and... the problem appeared. The phone made his restart after update... and continued to do so over and over again. (Vibrate/HTC screen on for 30 secs/screen off and so on)
I checked the HTC website for solutions, i entered live chat with a consultant, and he asked me to start the Hard reset procedure. To do that, while turned off, you have to press both volume keys, and press the power button. The phone will enter in the Bootloader menu where you have some options. But... tell me, how to do that if the phone restarts continously? you have about 1-2 seconds to do that, while the screen is off. It gave me a hardtime to do that... Finnally, i managed to enter the Bootloader menu.
There... you have 2 options: (using volume up/down to select, and power button to select) you can select to poweroff(shutdown) the phone - and the phone will shutdown,
or you can turn off the fastboot, and the phone will restart normally.
The thing is that when you restart your phone normaly, while fastboot on, the phone skips some steps, and go directly to to turn it on and show you the startscreen.
When you make a major update, like system upgrade, when the phone restarts, he needs to load all the boot setting. And here is the problem. If you have fastboot on, and make a major update, the phone will enter in this ****ty cicle of continous restarts.
Remember to deactivate this Fastboot before you update!
sergiu.dragan25 said:
I checked the HTC website for solutions, i entered live chat with a consultant, and he asked me to start the Hard reset procedure. To do that, while turned off, you have to press both volume keys, and press the power button.
Click to expand...
Click to collapse
This is not correct. To force a reboot, you hold power and vol up (not both vol buttons). Then, when its restarting (the moment the screen goes dark and before the white boot screen appears) you let go of both those buttons, and only hold vol down.
sergiu.dragan25 said:
But... tell me, how to do that if the phone restarts continously? you have about 1-2 seconds to do that, while the screen is off.
Click to expand...
Click to collapse
In the case of a bootloop (phone keeps restarting), all you need to do is hold vol down during one of the reboot cycles. The timing doesn't matter in this case. Just sit on the vol down button until the bootloader screen appears.
sergiu.dragan25 said:
There... you have 2 options: (using volume up/down to select, and power button to select) you can select to poweroff(shutdown) the phone - and the phone will shutdown,
or you can turn off the fastboot, and the phone will restart normally.
The thing is that when you restart your phone normaly, while fastboot on, the phone skips some steps, and go directly to to turn it on and show you the startscreen.
When you make a major update, like system upgrade, when the phone restarts, he needs to load all the boot setting. And here is the problem. If you have fastboot on, and make a major update, the phone will enter in this ****ty cicle of continous restarts.
Remember to deactivate this Fastboot before you update!
Click to expand...
Click to collapse
First, the FASTBOOT selection in bootloader is not the same as "Fast boot" in Settings>Power. The latter just makes the phone start faster from power OFF. The former is an adb (Android Debug Bridge) special mode that allows you to flash partitions from a computer.
Second, in bootloader, you should have the following selections:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Of course, its the FACTORY RESET option you want if you want to wipe the phone. Scroll down to (using vol keys) and select with power button.
On the bootloader screen, the active selection is the blue box with white text below the green phone info (hboot number, radio number, etc.). FASTBOOT should only be the default "active" selection if your phone is connected to a computer by USB. Otherwise the default selection in bootloader should be HBOOT.
Third, the "Fast boot" option in Settings>Power does not make a restart "faster" by skipping any steps. It just makes a start from power OFF faster. Its kind of a trick, where power OFF is not really off, but just a deeper sleep mode. A restart is always a restart, regardless of whether "Fast boot" is selected or not in Settings>Power.
Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J
I was thinking of a way to block the bootloader, and I came up with something very basic, so please who can try the method, share whether it works or not. (This method was checked and it WORKS !!)
Warning: I am not a super developer, just one more user who wants to help the community
Warning 2: This Process will erase everything in its path, remember to make a backup of your internal memory.
This series of steps is aimed at inexperienced users, if you think you are missing or there are many steps, this guide is not for you.
Without more to say, let's start.
How to re-lock bootloader:
1. Turn off your device.
2. Press Bixby Volume down and connect your device to a PC to start the download mode (now you can release both buttons)
3. Read the text below on the Download Mode screen
to block or unblock the Bootloader.
4.- Long press the vol (- or +) button as best suits you.
LOCK BOOTLOADER:
5. Long press the volume up button ( ) until the computer is restarted (this will erase your data and restart automatically). :fingers-crossed:
Ready! Now you have a device with an OEM lock.
Good luck my friends!!!
chalofito said:
I was thinking of a way to block the bootloader, and I came up with something very basic, so please who can try the method, share whether it works or not. (This method was checked and it WORKS !!)
Warning: I am not a super developer, just one more user who wants to help the community
Warning 2: This Process will erase everything in its path, remember to make a backup of your internal memory.
This series of steps is aimed at inexperienced users, if you think you are missing or there are many steps, this guide is not for you.
Without more to say, let's start.
How to re-lock bootloader:
1. Turn off your device.
2. Press Bixby Volume down and connect your device to a PC to start the download mode (now you can release both buttons)
3. Read the text below on the Download Mode screen
to block or unblock the Bootloader.
4.- Long press the vol (- or +) button as best suits you.
LOCK BOOTLOADER:
5. Long press the volume up button ( ) until the computer is restarted (this will erase your data and restart automatically). :fingers-crossed:
Ready! Now you have a device with an OEM lock.
Good luck my friends!!!
Click to expand...
Click to collapse
Thank you for posting this. I've had this method work once before but i am in a bit of a pickle at the moment.
I no longer get the options to 'long press vol up' which i think is the key to re locking the bootloader. Have you or anyone else got any idea why that would be?
akkaria said:
Thank you for posting this. I've had this method work once before but i am in a bit of a pickle at the moment.
I no longer get the options to 'long press vol up' which i think is the key to re locking the bootloader. Have you or anyone else got any idea why that would be?
Click to expand...
Click to collapse
This was tested once and it worked, it was not tried for the second time .. What version of Compilation do you have?
chalofito said:
This was tested once and it worked, it was not tried for the second time .. What version of Compilation do you have?
Click to expand...
Click to collapse
It has definitely worked before but not having much luck now. Maybe the latest software update has blocked this method?
This is my current version. I'm in Australia.
View attachment 4767541
akkaria said:
It has definitely worked before but not having much luck now. Maybe the latest software update has blocked this method?
his is my current version. I'm in Australia.
View attachment 4767541
Click to expand...
Click to collapse
It's a shame, I'm sorry that this happens to you, we hope that in the future this will be solved, for the moment we have to wait. someone will come who finds a definitive solution.
chalofito said:
It's a shame, I'm sorry that this happens to you, we hope that in the future this will be solved, for the moment we have to wait. someone will come who finds a definitive solution.
Click to expand...
Click to collapse
Thanks for your help. Yes, hopefully soon someone will find a method.
akkaria said:
Thanks for your help. Yes, hopefully soon someone will find a method.
Click to expand...
Click to collapse
Can you tell what exactly you already did with your phone? Did you unlock bootloader, re lock bootloader, then unlocked it again and then actually rooted it? And now after you unrooted your phone you can not re lock bootloader?
I am asking because I suspect that you can not re lock you bootloader again after you actually have rooted your phone once. I am suspecting I only read a post from a guy who managed to re lock is bootloader but he never actually rooted his phone once. So in other words after you tripped knox (which seems to only happen when you install magisk) you may not be able to re lock you bootloader (ever) again.
SakazukiAka said:
Can you tell what exactly you already did with your phone? Did you unlock bootloader, re lock bootloader, then unlocked it again and then actually rooted it? And now after you unrooted your phone you can not re lock bootloader?
I am asking because I suspect that you can not re lock you bootloader again after you actually have rooted your phone once. I am suspecting I only read a post from a guy who managed to re lock is bootloader but he never actually rooted his phone once. So in other words after you tripped knox (which seems to only happen when you install magisk) you may not be able to re lock you bootloader (ever) again.
Click to expand...
Click to collapse
Yes!! You hit the nail on the head!! So i was able to re lock bootloader once before but i wasnt successful in rooting the phone. After i then successfully rooted the phone with Magisk i restored back to normal and no i cannot re lock the bootloader.
It seems as though a few people have said you can't re lock it after successfully rooting! Quite frustrating!!
akkaria said:
Yes!! You hit the nail on the head!! So i was able to re lock bootloader once before but i wasnt successful in rooting the phone. After i then successfully rooted the phone with Magisk i restored back to normal and no i cannot re lock the bootloader.
It seems as though a few people have said you can't re lock it after successfully rooting! Quite frustrating!!
Click to expand...
Click to collapse
I see. There is another method, that seems to work, tested by @robbo1947 that he explained here.
robbo1947 said:
Assuming you had the standard Samsung ROM (you hadn't flashed a custom ROM)
Change OEM switch while rooted, exit settings, no need to flash stock firmware.
Power off phone.
Press and hold Bixby and Volume down, whilst holding connect with USB cable to computer. Release buttons when Download screen appears.
Long press the Volume up.
At this stage, the phone will wipe the data and overwrite the Magisk modification then reboot.
You should now have an S10, standard boot screens, stock ROM and no root.
Click to expand...
Click to collapse
I did not check it myselff yet, but it worked for robbo1947. All credits goes to @robbo1947 !! Please let us know if that worked for you or not.
SakazukiAka said:
I see. There is another method, that seems to work, tested by @robbo1947 that he explained here.
I did not check it myselff yet, but it worked for robbo1947. All credits goes to @robbo1947 !! Please let us know if that worked for you or not.
Click to expand...
Click to collapse
I am going to have a go again in the next few days to prove to myself and others that it is possible to relock the bootloader after rooting. Will let you know.
Watch this space.
robbo1947 said:
I am going to have a go again in the next few days to prove to myself and others that it is possible to relock the bootloader after rooting. Will let you know.
Watch this space.
Click to expand...
Click to collapse
I look forward to your findings. As i am running my phone as my daily driver now i am hesitant to re root it if this method wont work. I have my fingers crossed though
samsung doesn't allow you to unlock and then lock back the device multiple times. It only works once, then your bootloader stay unlocked for ever.
I I had root and twrp on my s10 + but I quietly put the last nobrand ASE7 firmware back and I re-locked the bootloader without any difficulty I no longer have any warning messages at startup and in the developer options I have the oem option working like new.
akkaria said:
I look forward to your findings. As i am running my phone as my daily driver now i am hesitant to re root it if this method wont work. I have my fingers crossed though
Click to expand...
Click to collapse
Lebrun213 said:
samsung doesn't allow you to unlock and then lock back the device multiple times. It only works once, then your bootloader stay unlocked for ever.
Click to expand...
Click to collapse
OK, sorry for delay in getting back to this question of locking and unlocking the bootloader on the Galaxy S10.
During the last few days I have locked, unlocked, locked and unlocked again, probably 15 or 20 times to test various scenarios.
Please remember, each time you lock or unlock the bootloader all of your data is wiped.. any Root will also be gone. You will also be needing your current firmware.
This is for the Galaxy S10 without TWRP.
Scenario 1. Your phone is rooted with Magisk.
Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.
Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).
Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. Then the S10 logo screen will briefly apppear, before it flicks back to the Download screen with the words 'VBMETA: Error verifying vbmeta image etc' at the top, as the image below.
This is all good so far. Leave the phone exactly as it is with this screen showing and make sure the phone is still connected to the computer.
On your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 file parts (BL, AP. CP and CSC) into Odin.
Let Odin finish.
The phone will reboot ready for setup.
The Unlocked bootloader warning screen will be gone.
Scenario 2. Your phone has been rooted but isn't now, and the greyed out OEM switch is ON
Easy, turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Scenario 3 Your phone has been rooted but isn't now, and the greyed out OEM switch is OFF
Sorry, but in this situation, you are going to have to root your phone with Magisk as the OEM switch will only be available when rooted.
When rooted, proceed as Scenario 1.
Scenario 4 Your phone has never been rooted, and the greyed out OEM switch is ON i.e. you unlocked the bootloader but never proceeded to root the phone
Turn off your phone and proceed from the 2nd paragraph of Scenario 1.
If you want proof that I have locked and unlocked time and time again see HERE
:victory:
robbo1947 said:
OK, sorry for delay in getting back to this question of locking and unlocking the bootloader on the Galaxy S10.
During the last few days I have locked, unlocked, locked and unlocked again, probably 15 or 20 times to test various scenarios.
Please remember, each time you lock or unlock the bootloader all of your data is wiped.. any Root will also be gone. You will also be needing your current firmware.
Scenario 1. Your phone is rooted with Magisk.
Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.
Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).
Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. The S10 logo screen will briefly apppear, before it flicks back to the Download screen as the image below.
With the phone still connected to your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 parts into Odin.
Let Odin finish. The phone will reboot and the Unlocked bootloader warning screen will be gone.
Scenario 2. Your phone has been rooted but isn't now, and the greyed out OEM switch is ON
Easy, turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Scenario 3 Your phone has been rooted but isn't now, and the greyed out OEM switch is OFF
Sorry, but in this situation, you are going to have to root your phone with Magisk as the OEM switch will only be available when rooted.
When rooted, proceed as Scenario 1.
Scenario 4 Your phone has never been rooted, and the greyed out OEM switch is ON i.e. you unlocked the bootloader but never proceeded to root the phone
Turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Click to expand...
Click to collapse
No dramas, thanks heaps for your reply.
So it seems I am in scenario 3 meaning I'll need to re root my phone which is fine. However, when I hold down the bixby and volume up and plug in I don't get the option to long hold volume up which I previously did. I only have press volume up or down. Is this because my bootloader is already unlocked? I should still be able to re root my phone in this scenario shouldnt i?
akkaria said:
No dramas, thanks heaps for your reply.
So it seems I am in scenario 3 meaning I'll need to re root my phone which is fine. However, when I hold down the bixby and volume up and plug in I don't get the option to long hold volume up which I previously did. I only have press volume up or down. Is this because my bootloader is already unlocked? I should still be able to re root my phone in this scenario shouldnt i?
Click to expand...
Click to collapse
Yep, your bootloader is unlocked.
When you have re-rooted and you go into Developer options you will be able to control the OEM switch and ensure it is ON.
Then when you get into Download mode you will see that option of LONG press Volume-up.
I've just added video proof to original post.
robbo1947 said:
Yep, your bootloader is unlocked.
When you have re-rooted and you go into Developer options you will be able to control the OEM switch and ensure it is ON.
Then when you get into Download mode you will see that option of LONG press Volume-up.
I've just added video proof to original post.
Click to expand...
Click to collapse
Awesome. Will give it a go in the next day or two and report back but given your success I'm hoping I'll have the same.
Cheers
akkaria said:
Awesome. Will give it a go in the next day or two and report back but given your success I'm hoping I'll have the same.
Cheers
Click to expand...
Click to collapse
Don't forget the :good:
robbo1947 said:
Don't forget the :good:
Click to expand...
Click to collapse
You sir, are my hero. It all worked perfectly and i no longer get the bootloader warning screen and my bootloader is now relocked!!
For anyone else having this problem, i too can confirm that this method works. The only issue i had was that for some reason, i was stuck on the Samsung flashing boot screen for nearly half an hour. A simple reboot into recovery(hold power and volume down for 7 seconds to shut down and then quickly hold power, vol up and bixby) and wipe factory data then system reboot fixed it.
I can also confirm that after doing this and re locking the bootloader, i now have access to all apps that i was previously having issues with and my google play store recognises my devices as certified.
I now have a fully working and functional device. Thank you again.
if i revert to stock rom after root and samsung status says official and relock bootloader will be able to get otas again???
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.