Hi everybody, I've been reading for years but had little reason to post as all my questions were already answered. But I find myself in a rather frightening situation.
Where I'm at: My Samsung Galaxy S2 from Straight Talk Wireless boots to the part where it says "Samsung Galaxy SII" and goes no further.
Without the USB connected, I tried getting into recovery mode by holding volume up and volume down and power, but it gets no further than the "Samsung Galaxy SII" screen. I tried to get into download mode for Odin by holding volume down and power, but it still comes to this screen. I also tried holding volume down and power and the home softkey, to no avail.
With the USB connected it does nothing other than show the empty battery logo with the usually animated logo to show it is loading battery info, but it doesn't animate and never fills up the battery, even though the batter is >80% charged.
How I got here:
I flashed CyanogenMod with success, it was working fine, but my call recording app would not accept the voice uplink as a source saying my hardware didn't support it, even though it supported it just fine under the stock ROM. I flashed back to my stock ROM, all was well. I decided to try to flash another ROM, and Biftor said in the description that it had call record, so I tried it, but my back button didn't work, so I went back to my stock ROM. Only now, I couldn't hear the people I was calling, and they couldn't hear me! Makes a phone rather useless, obviously. I factory reset, cleared the cache, cleared the Davik cache, same result (right now sorta wishing I tried fix permissions, but I didn't).
I panicked, removed my SD Card, and wiped every partition I could see in CWM, figuring I could put my SD Card back in and restore a backup or flash a fresh ROM with no residual problems from previous installs, and at the very least get it into download mode with Odin. I can do none of these things.
This brings us back to the first part of the post "Where I'm At".
This phone is my primary means of communication, I rely on it for business that will begin early in the morning, and I'm not looking forward to buying a new one, so as a guy who has at the very least, tried, to do his homework, and is in desperate need of your help, I beg you to assist me. I have paypal and a little bit of money if that's what it takes to save my skin before morning.
Thank you all in advance for whatever I assistance I might receive on this thread, but more importantly for all the times I never even had to ask the question.
I left the sim card and battery out for about 15 minutes and was able to get back into recovery mode, by holding power + vol up + vol down while inserting battery.
Hey guys-
Was on a long international flight yesterday and decided to put my (unrooted) Galaxy S6 into "ultra power saving" mode for the first time. It was a horrible mistake and I'm not sure how to undo it!
The first issue it had was that it said Ultra Power Saving mode doesn't support the use of themes, so it was reverting to the default theme (I use Material Black).
After a long time of saying it was reverting to the default theme, I'm not sure if it worked - it ended up in the state that it is currently in: if I turn the phone on, the screen is just black - it has the status bar at the top of the screen, but just a blank black screen below it. It does not look like images I've seen on other websites for what Ultra Power Saving mode is supposed to look like (no icons on the screen, no "More" at the top right). If I go to settings by dragging from the top of the screen and hitting the settings button, I get a very limited set of settings: WiFi, Bluetooth, Airplane Mode, Mobile Networks, Location, Sound, and Brightness - nothing that enables me to turn off Ultra Power Saving mode.
I am afraid to reboot the device, because when I did that yesterday, I had major issues. My device is encrypted, and I think this mode doesn't play nicely with encryption; when I rebooted the device, I was asked to sign in to unlock the encryption (as normal), but then the encryption booting screen (an unlock symbol with a circle around it) just idled indefinitely - for an hour or two. I couldn't do anything to get the phone to actually boot. Eventually, many hours later, rebooting the phone and logging in allowed it to boot to the state I described above; I don't know what went differently that time.
I tried various key combinations on restart, one of which seemed to result in the device trying to boot to Safe Mode (it said safe mode in the bottom left corner when asking me to sign in to device encryption), but ended up leaving me in the exact same place - the extremely limited Ultra Power Saving mode black screen I described above.
Anyway - is there anything I can try to get my phone out of Ultra Power Saving mode and back to normal? It is unusable right now and I can't figure out how to get it back. Would like to avoid a factory reset if possible (because I'm overseas with ****ty internet, and don't have access to my office to get it re-set up with enterprise mail etc.).
If I have to factory reset the device - I'm not even sure how to do it from this current UPSM state, so any tips there would be helpful too.
Thanks a ton in advance for the help guys
Go to download mode, reflash original rom with odin. You need your rom file from sammobile or samsung-updates or xda and odin 3.
Sorry, I am no power user although I am not totally tech incompetent. Can you tell me in a little more detail what your instructions mean? It sounds like it is basically a total reset of the OS; is that right? Any implications for my warranty? Any alternatives?
If you had package disabler and disabled any of the packages required to run ultra power saving mode, you get symptoms like this.
com.sec.android.emergencylauncher is one package amongst many.
I have honestly only heard of factory resetting working.
http://www.hardreset.info/devices/samsung/samsung-g920f-galaxy-s6/
Hi!
Very weird situation. Before that everything was stock and OK (no custom ROM or anything).
- If the phone is unplugged, nothing works at all (key combinations,...)
- The battery is charged, at some point, when totally off, it showed the battery charging, 60% at least. But have not been able to go back into this mode.
- When connected, it starts booting, but keeps rebooting very fast (1-2 s after Samsung splash screen).
- Unable to boot into Recovery mode (UP+HOME+PWR, for wiping cache,...). Just does nothing, howerver long I wait
- Unable to boot "directly" into Maintenance Mode (all buttons), more on that later
- Can boot into Download (ODIN) mode (DOWN+HOME+PWR) very easily. I was able to flash stock ROM, but nothing changed.
- From ODIN mode I can boot into Maintenance mode (all buttons). I can navigate the menu, but any choice, even Factory Reset, gets me directly back to the reboot loop...
As I can not even turn it off, I cannot drain the battery (at least not quick). As soon as I disconnect the cable it goes dark (whatever mode I am in).
Anything I missed that I could try before throwing the phone?
Thanks!
SOLVED
Just to leave a trace on what happened:
- Left the phone alone, un plugged, for 8-10 hours.
- Just to see, tried to reboot it normally,
- It booted on a blue/cyan display, with "installing updates".
- At one point before I had that screen, but after 10 seconds it rebooted into the loop cycle. And after playing with the recovery reboots, I had never managed to get this special boot again.
- This time it stayed on "installing updates" for 1-2 mn, then rebooted, and Voilà!!!
So apart from my magic touch of doing nothing, don't really know what happened... So much for the recovery recipe!
A fairly similar thing happened to my girlfriend's g920v yesterday. We haven't been that lucky that it got fixed.
The situation is slightly different though, it boots for about 3 seconds, makes the low battery sound, battery indicator says 0%, then shuts back down.
Tried flashing stock in odin a few times, a few factory resets, nothing.
It seems like an OTA update failed and now the stupid locked bootloader won't let me or the or OS fix it.
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
guimou_qc said:
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
Click to expand...
Click to collapse
There's got to be some connection of some sort, yours is the 4th post I've seen here or on Reddit this month about bootloops probably related to updates
Yesterday I put my phone to charge over night and when I woke up today's morning I was met with a Black Screen with a status bar and Software Back button, that doesn't do anything. Rebooting in recovery doesn't work (TWRP just stuck on loading screen). I can receive notifications, but can't interact with them. I can Turn on and off Wi-Fi, Bluetooth, GPS etc. through status bar. I can't open Settings or any App. I can't reboot with out removing battery, can't hard reset and if I power off phone from Power menu it won't start again, when I hold down Power button, unless I remove battery.
Some Details about phone:
LG Max x155
Android 5.0.2
Custom AOSP (installed long time ago, never faced this problem)
TWRP 3.0.3.
I searched internet and tried some things:
Rebooting (didn't work at all)
Hard Reseting (didn't work at all)
Removing Battery putting it back and then powering on (didn't help)
Entering Safe mode (didn't help, it shows same issue, though it briefly shows my Home screen before going black)
Doing anything with Recovery, like wiping, reinstalling ROM etc. doesn't work, because TWRP won't load
Some other details:
I am using different charger (but I have used it for several days already). Phone was overcharged over night.
Now I am trying to drain the battery to zero and then charging it again, using my old charger. If it won't help I don't know what can be done.
TRI99ER_ said:
Yesterday I put my phone to charge over night and when I woke up today's morning I was met with a Black Screen with a status bar and Software Back button, that doesn't do anything. Rebooting in recovery doesn't work (TWRP just stuck on loading screen). I can receive notifications, but can't interact with them. I can Turn on and off Wi-Fi, Bluetooth, GPS etc. through status bar. I can't open Settings or any App. I can't reboot with out removing battery, can't hard reset and if I power off phone from Power menu it won't start again, when I hold down Power button, unless I remove battery.
Some Details about phone:
LG Max x155
Android 5.0.2
Custom AOSP (installed long time ago, never faced this problem)
TWRP 3.0.3.
I searched internet and tried some things:
Rebooting (didn't work at all)
Hard Reseting (didn't work at all)
Removing Battery putting it back and then powering on (didn't help)
Entering Safe mode (didn't help, it shows same issue, though it briefly shows my Home screen before going black)
Doing anything with Recovery, like wiping, reinstalling ROM etc. doesn't work, because TWRP won't load
Some other details:
I am using different charger (but I have used it for several days already). Phone was overcharged over night.
Now I am trying to drain the battery to zero and then charging it again, using my old charger. If it won't help I don't know what can be done.
Click to expand...
Click to collapse
Do a google search for:
"Return to stock (your model number)"
Then reinstall TWRP, then flash your 5.0ROM and Gapps. Don't forget to factory reset, wipe cache and wipe dalvik cache when you flash the ROM.
Sent from my SM-S767VL using Tapatalk
Sorry for late answer
TRI99ER_ said:
Yesterday I put my phone to charge over night and when I woke up today's morning I was met with a Black Screen with a status bar and Software Back button, that doesn't do anything. Rebooting in recovery doesn't work (TWRP just stuck on loading screen). I can receive notifications, but can't interact with them. I can Turn on and off Wi-Fi, Bluetooth, GPS etc. through status bar. I can't open Settings or any App. I can't reboot with out removing battery, can't hard reset and if I power off phone from Power menu it won't start again, when I hold down Power button, unless I remove battery.
Some Details about phone:
LG Max x155
Android 5.0.2
Custom AOSP (installed long time ago, never faced this problem)
TWRP 3.0.3.
I searched internet and tried some things:
Rebooting (didn't work at all)
Hard Reseting (didn't work at all)
Removing Battery putting it back and then powering on (didn't help)
Entering Safe mode (didn't help, it shows same issue, though it briefly shows my Home screen before going black)
Doing anything with Recovery, like wiping, reinstalling ROM etc. doesn't work, because TWRP won't load
Some other details:
I am using different charger (but I have used it for several days already). Phone was overcharged over night.
Now I am trying to drain the battery to zero and then charging it again, using my old charger. If it won't help I don't know what can be done.
Click to expand...
Click to collapse
I figured it out. My SD Card burnt and caused this issue. I removed it and the phone's fine.
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Also having same issue
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Strongo said:
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Click to expand...
Click to collapse
No, unfortunately my phone is still stuck on that exception red text (not a single green one like the one i found online).
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
The only solution I could find that could help me in the future is that 1. Phone is dead, eMMC and motherboard cannot start. 2. Since the phone could be (difficultly) tore down, the best bet is that you find a data recovery center (not Samsung since as I found out they don't do data recovery, but they simply change everything giving you a new phone basically or they change the motherboard, so deleting everything) or a data recovery specialist so that you could disassemble the phone, remove the memory, and read the content on a chip reader.
In this case maybe there's a chance to recover the simple data you have (photo, video, music, documents and something else that has a recognizable header) but probably everything else is lost.
I would be more than happy to be proven wrong since I'm not an expert but it's been 2 weeks and I received no answers.
Iztooi said:
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Click to expand...
Click to collapse
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes. Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
cooltt said:
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
Click to expand...
Click to collapse
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes.
Click to expand...
Click to collapse
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
Click to expand...
Click to collapse
The fact is that it doesn't power off and on multiple times, but just one time.
Iztooi said:
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
The fact is that it doesn't power off and on multiple times, but just one time.
Click to expand...
Click to collapse
I'm this case you'll need to use ADB and side load to flash a new bootloader.
cooltt said:
I'm this case you'll need to use ADB and side load to flash a new bootloader.
Click to expand...
Click to collapse
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Iztooi said:
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Click to expand...
Click to collapse
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
cooltt said:
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
Click to expand...
Click to collapse
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Iztooi said:
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Click to expand...
Click to collapse
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
cooltt said:
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
Click to expand...
Click to collapse
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Iztooi said:
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Click to expand...
Click to collapse
I assume youre in upload mode. Press only power button for 20 seconds
kpwnApps said:
I assume youre in upload mode. Press only power button for 20 seconds
Click to expand...
Click to collapse
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Iztooi said:
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Click to expand...
Click to collapse
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Iztooi said:
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
Click to expand...
Click to collapse
kpwnApps said:
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Click to expand...
Click to collapse
I already did that, but sadly it didn't work.
Iztooi said:
I already did that, but sadly it didn't work.
Click to expand...
Click to collapse
Then it might be an UFS hardware fault
kpwnApps said:
Then it might be an UFS hardware fault
Click to expand...
Click to collapse
I have the exact same problem. This is the closest thing I could find on the internet I could find regarding diagnosing it. Had to make an account just to reply. I was thinking it was a OS problem for the longest time, but I suspect that it may be a hardware problem after all. My s7 did this to me the morning of Jan 9. Set it down and came back to it, reboot with bootloader error, red text only, no combinations of buttons work etc. I see that two others in the thread had theirs fail around the same time as well.
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
draco18 said:
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
Click to expand...
Click to collapse
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Iztooi said:
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Click to expand...
Click to collapse
I was wondering if you installed any apps recently and how full your internal memory was. I believe my phone was around 90% full of the 32GB, had no warning symbol about how full my memory was though. Friend was saying I should of got a warning if my memory was getting near capacity. I installed F-droid recently and used it to download Adaway app. Deleted F-droid and deleted Adaway since I couldn't get Adaway to work. Never rooted my phone. I was curious if you also did anything similar to what my phone did since we're in the same boat. Otherwise the only things we share in common is we set it down and it reboot with this bootloader error.