Hey there,
Out of nowhere my phone started bootlooping right in the middle of everyday use. It'll get to the animated startup screen and then will freeze and try booting up again. Sometimes it will just stop and say "Your device is corrupt. It can't be trusted and may not work properly."
My phone is completely stock other than the updates that Razer sends out to the phone and my bootloader is locked, but I can get to the bootloader screen where I've tried to recovery mode and wipe user data options to no effect.
If anyone can help me get this phone back up and running, I'd really appreciate it!
If it will let you do a factory reset.
Many times that's all you need to do with a stock phone*.
If that can't be done reflash it to the same version.
It was likely a 3red party apk that caused to boot loop. If you were using a 3rd party launcher... don't use it on the new load! Otherwise any app that seemed unstable don't reload it.
*lol, my 10+ was boot looped twice, back to back factory resets. Last reload I left out the 3rd party launcher. Been running strong for close to a year now
MOD ACTION:
Guys, you have completely hijacked the OP's thread and had gone on an Off-Topic spree. Not a single post answers or attempts to answer the OP's issue.
Those having different issues, please search the forum for a similar thread or answers. If not found, please post a new thread at the appropriate forum.
Thank you for understanding!
I'll try this again... for a stock Android NOT Rooted see if you can do a factory reset*.
It may let you go into safe mode to recover data but consider that load toast.
It was likely a 3rd party app that boot looped it.
It may have been an update.
Beware of what you install and let update on the new load.
A 3rd party launcher boot looped my stock Note 10+ twice back to back. The factory reset restored the OS and after not loading that launcher again it's been running fine.
* If you can't do a factory reset it will need its firmware reflashed.
This deep level of corruption could indicate either a trojan or a hardware failure. It's not a normal event.
Boot the phone into fastboot mode. Connect the phone via USB cable and Open a command prompt or powershell as admin and run the following commands:
fastboot getvar all >(enter)
Note the output and determine which slot is active. You should see "active slot_a" or "active slot_b".
Next issue the command:
fastboot --set-active=a (if slot_b was the active slot)
OR
fastboot --set-active=b (if slot_a was the active slot)
Next, issue the following command:
fastboot reboot.
Does the phone boot normally? If so, then the now inactive slot is corrupt and will need to be reflashed.
Once you can boot normally, you then enable developer options and OEM unlocking, unlock the bootloader from fastboot mode and reflash the corrupt partition.
MoPhoMike said:
Boot the phone into fastboot mode. Open a command prompt or powershell as admin and run the following commands:
fastboot getvar all (enter)
Note the output and determine which slot is active. You should see "active slot_a" or "active slot_b".
Next issue the command:
fastboot --set-active=a (if slot_b was the active slot)
OR
fastboot --set-active=b (if slot_a was the active slot)
Next, issue the following command:
fastboot reboot.
Does the phone boot normally? If so, then the now inactive slot is corrupt and will need to be reflashed.
Once you can boot normally, you then enable developer options and OEM unlocking, unlock the bootloader from fastboot mode and reflash the corrupt partition.
Click to expand...
Click to collapse
If their data is backed up a factory reset probably best. No reason to beat a dead horse unless you want to autopsy it.
>If it's a virus a factory reset will likely be the end of it and is the best way to deal with it*<
Ether way fresh load is a no brains needed fresh start.
* virus, trojan etc infections are rare on Adroids unless you do something stupid, but they can happen. A boot loop is a possible symptom of an infection.
The full nuke reload option is the best one as a trojan can do a lot of damage in a short amount of time including hardware damage.
Best to error on the side of caution whenever there are signs a device has been compromised.
blackhawk said:
If their data is backed up a factory reset probably best. No reason to beat a dead horse unless you want to autopsy it.
>If it's a virus a factory reset will likely be the end of it and is the best way to deal with it*<
Ether way fresh load is a no brains needed fresh start.
* virus, trojan etc infections are rare on Adroids unless you do something stupid, but they can happen. A boot loop is a possible symptom of an infection.
The full nuke reload option is the best one as a trojan can do a lot of damage in a short amount of time including hardware damage.
Best to error on the side of caution whenever there are signs a device has been compromised.
Click to expand...
Click to collapse
The OP indicated that he was able to get to FB mode and attempted a Factory reset to no avail, so the only option is the nuclear option at this point.
MoPhoMike said:
The OP indicated that he was able to get to FB mode and attempted a Factory reset to no avail, so the only option is the nuclear option at this point.
Click to expand...
Click to collapse
My bad.
That sounds like a hardware failure.
A reflash is worth a try though.
Related
History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.
Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!
Hello XDA,
Ok, so I'm going to try to explain the best I can. My roommate has a Nexus 6 (Project Fi if that matters). She went to install an update, although I'm not sure which one. She said she thinks it was "7 something". I'm assuming it was 7.1.1 since that is the one that I was last notified about on my phone and she said the notification appeared only a few days ago. After she installed it the phone was stuck in a bootloop (the spinning colored balls screen).
I Googled solutions and tried wiping system cache from recovery mode. That didn't work, so I asked if she had anything important on the phone and if I could do a factory reset. She said I could go ahead and do it, however that did not work either. So then I plugged the phone into my computer and fired up a terminal session to flash a factory image to the phone. I entered "fastboot oem unlock" so I could proceed . It came back with the "see developer options" message. Ok, cool, but I can't get into the settings app to enable OEM unlocking.
So since I did the factory reset and can't boot into the OS, is there any way to enable OEM unlocking from the bootloader? I'll keep looking for answers in the mean time.
Thanks in advanced.
EDIT:
Found a thread with the OP having similar issues. I tried "fastboot format cache" and "fastboot format userdata" which both failed with "Not allowed in locked state!". Even though I got the errors I tried (out of desperation) to boot to TWRP with "fastboot boot ~/Downloads/twrp-3.1.0-0-shamu.img" which failed with "FAILED (remote failure)".
EDIT2:
Tried downloading 7.1.1 OTA image and sideloading via "adb sideload shamu-ota.zip" from the bootloader recovery mode. Failed with "error: no devices/emulators found".
Sideload an OTA image. That should resolve the bootloop so you can enter Android to unlock the bootloader.
Strephon Alkhalikoi said:
Sideload an OTA image. That should resolve the bootloop so you can enter Android to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the reply. I tried it and it failed with "no device found". The command "adb devices" gives me an empty list. Not even ????????.
If ADB isn't seeing the device you potentially have a hardware issue.
i got same problem.
no oem unlock cuz is in bootloop
locked
erasing
@luisq93: Yours is a different issue. The solution for you is to do...nothing.
The erase part of the factory reset MUST complete, or you may end up with unusable internal storage until an uninterrupted factory reset is completed. So all you can do is be patient.
Strephon Alkhalikoi said:
@luisq93: Yours is a different issue. The solution for you is to do...nothing.
The erase part of the factory reset MUST complete, or you may end up with unusable internal storage until an uninterrupted factory reset is completed. So all you can do is be patient.
Click to expand...
Click to collapse
like 2 month and half patient?
cuz the erasing changed language 2 months ago and nothing more... from italian to English, maybe i should just wait... thanks for the advice.
@luisq93: How long did you leave the N6 running the very first time the device started erasing? I'm willing to bet you only gave it a few minutes, became impatient, shut the device down to restart it and upon restarting encountered the erase mode again. Consequently you thought it bootlooped and put it in your drawer.
Until you let erase mode complete, every time the device boots it will immediately enter erase mode, because the erase must complete to avoid corrupting the internal storage. Erase mode, especially on an encrypted phone, may take a while. I had one instance on another of my devices take an hour.
So the solution to the erasing "bootloop" is to do nothing except plug the N6 into its charger and leave it alone.
Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video
Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again
blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again
I hope this is the right place to post this, I'm offering $250 to the person that can assist me in getting my phone to boot again so I can extract the data I need from it. Here are the quick facts:
-Verizon Pixel 5 (locked bootloader, fastboot commands don't work)
-Woke up and phone was in Android Recovery mode (was working fine when I put it on the charger)
-adb sideload OTA hasn't worked so far (tried most recent OTA package and it loaded successfully with status 0 but still leaves me in a bootloop, older Verizon specific OTAs will not load due to being outdated)
-Even tried sideloading Android 12 dev preview, no success
-Safe mode does not work
-Verified that my backups do not contain the data I am trying to recover
I've tried pretty much everything I could find by searching here and other forums/resources and I'm pretty much at the point where I'm thinking this data may be gone forever but I'm hoping someone can prove me wrong. Willing to do a remote session with the phone connected if needed.
bsmack said:
I hope this is the right place to post this, I'm offering $250 to the person that can assist me in getting my phone to boot again so I can extract the data I need from it. Here are the quick facts:
-Verizon Pixel 5 (locked bootloader, fastboot commands don't work)
-Woke up and phone was in Android Recovery mode (was working fine when I put it on the charger)
-adb sideload OTA hasn't worked so far (tried most recent OTA package and it loaded successfully with status 0 but still leaves me in a bootloop, older Verizon specific OTAs will not load due to being outdated)
-Even tried sideloading Android 12 dev preview, no success
-Safe mode does not work
-Verified that my backups do not contain the data I am trying to recover
I've tried pretty much everything I could find by searching here and other forums/resources and I'm pretty much at the point where I'm thinking this data may be gone forever but I'm hoping someone can prove me wrong. Willing to do a remote session with the phone connected if needed.
Click to expand...
Click to collapse
Try the latest factory image for Verizon
rbouza1 said:
Try the latest factory image for Verizon
Click to expand...
Click to collapse
I appreciate the reply, unfortunately I can't flash factory images via fastboot due to the bootloader being locked. I tried both the latest factory image from April '21 and the latest Verizon labeled factory image from Feb '21.
Bounty is still out FYI, I plan on tossing the phone in a drawer for a few months to see if anyone comes up with anything. I'll be taking it out to continue trying out adb sideload of the monthly OTAs that get posted, definitely anxiously awaiting the May '21 update!
Not sure if this information helps, but I just tried sideloading the May '21 OTA and I'm still stuck in the same spot. After the sideload finished successfully (code 0, no errors) it tried to boot but I got the Android Recovery screen again. It still references RQ2A.210405.005 (May '21 OTA is RQ2A.210505.003).
Try changing the active boot slot with fastboot?
How to Change the Current Active Partition Slot? - KrispiTech
Modern Android smartphones ship with partition slots A and B and we can use a Fastboot command to manually change from one active slot to the other.
krispitech.com
bsmack said:
Not sure if this information helps, but I just tried sideloading the May '21 OTA and I'm still stuck in the same spot. After the sideload finished successfully (code 0, no errors) it tried to boot but I got the Android Recovery screen again. It still references RQ2A.210405.005 (May '21 OTA is RQ2A.210505.003).
Click to expand...
Click to collapse
Yes, that makes sense on a/b-partitioned devices. The update is always applied to the inactive slot.
So you would have to change the current slot as suggested:
l7777 said:
Try changing the active boot slot with fastboot?
How to Change the Current Active Partition Slot? - KrispiTech
Modern Android smartphones ship with partition slots A and B and we can use a Fastboot command to manually change from one active slot to the other.
krispitech.com
Click to expand...
Click to collapse
However, I don't think you can do that without unlocking your bootloader.
If you could boot into system, however, we might do it without the bootloader. But here comes the next problem: You cannot boot into system.
bsmack said:
-Woke up and phone was in Android Recovery mode (was working fine when I put it on the charger)
Click to expand...
Click to collapse
What do you even get? A screen saying "Your data may be corrupted" (known as "rescue party")?
Or your normal recovery screen?
If it actually is rescue party, hit the "try again" button – it would reboot, fail and go back to rescue party.
Do that 7-10 times without interruption (e.g. turning of the device). Your device should automatically change the slot to the 'other' slot, and then boot just fine.
bsmack said:
I hope this is the right place to post this, I'm offering $250 to the person that can assist me in getting my phone to boot again so I can extract the data I need from it.
Click to expand...
Click to collapse
Since you offer $250, you may want to invest in "chip off". Your phone will be disassembled and your chip (which holds all of your data) will be removed from the phone.
Using special hard- and software, you should be able to recovery your data.
Only thing I don't know: How do these tools handle encryption? I'm pretty sure they can offer something to insert your password etc., but you may want to research a bit further before buying those tools or paying someone to do it for you.
User699 said:
Since you offer $250, you may want to invest in "chip off". Your phone will be disassembled and your chip (which holds all of your data) will be removed from the phone.
Using special hard- and software, you should be able to recovery your data.
Only thing I don't know: How do these tools handle encryption? I'm pretty sure they can offer something to insert your password etc., but you may want to research a bit further before buying those tools or paying someone to do it for you.
Click to expand...
Click to collapse
I suspect this will be much more than $250 if they can get past the encryption. It's not just a matter of the password it's knowing how to combine the password with the devices unique hardware encryption key to ultimately decrypt the file system.
l7777 said:
Try changing the active boot slot with fastboot?
How to Change the Current Active Partition Slot? - KrispiTech
Modern Android smartphones ship with partition slots A and B and we can use a Fastboot command to manually change from one active slot to the other.
krispitech.com
Click to expand...
Click to collapse
I appreciate the response, this is something I hadn't tried before. Unfortunately it seems Verizon blocks this functionality as well.
User699 said:
What do you even get? A screen saying "Your data may be corrupted" (known as "rescue party")?
Or your normal recovery screen?
If it actually is rescue party, hit the "try again" button – it would reboot, fail and go back to rescue party.
Do that 7-10 times without interruption (e.g. turning of the device). Your device should automatically change the slot to the 'other' slot, and then boot just fine.
Click to expand...
Click to collapse
I believe it is rescue party as that is the first screen I see (data corrupt with two options; try again or wipe phone). Currently trying this now to see if I can get it to switch to slot b (fastboot currently indicates that the active slot is slot a).
Another thought, if I flash an OTA (let's say to slot b since slot a is the active one), after a successful flash wouldn't recovery flag slot b as the slot to attempt to boot into next? And on that next boot, is slot b simply failing to boot and reverting to slot a, which is why I'm seeing the "old" android version in rescue party?
*$250 BOUNTY IS STILL ACTIVE!*
Hopefully replying to myself doesn't get too annoying for everyone, just wanted to give an update and hopefully give some insight to lurkers that might be experiencing something similar.
Based on what I'm seeing, slot a contains the corrupted OS and when I do an "adb sideload" successfully it installs to slot b. Immediately after a successful adb sideload, if I don't "reboot now" and instead "reboot to bootloader" it will show at the bottom of the fastboot screen that the active boot slot is b.
After I press "start" from the bootloader menu, the phone booting takes longer than normal, will restart once, takes a long time again, then restarts again and quickly brings me to the "rescue party" screen with RQ2A.210405.005 as the active OTA version. If I go back to the bootloader after this it will show that the active boot slot is now a.
I am truly thankful for all the replies and suggestions so far and I would love nothing more than to send this $250 bounty to a forum member.
bsmack said:
*$250 BOUNTY IS STILL ACTIVE!*
Hopefully replying to myself doesn't get too annoying for everyone, just wanted to give an update and hopefully give some insight to lurkers that might be experiencing something similar.
Based on what I'm seeing, slot a contains the corrupted OS and when I do an "adb sideload" successfully it installs to slot b. Immediately after a successful adb sideload, if I don't "reboot now" and instead "reboot to bootloader" it will show at the bottom of the fastboot screen that the active boot slot is b.
After I press "start" from the bootloader menu, the phone booting takes longer than normal, will restart once, takes a long time again, then restarts again and quickly brings me to the "rescue party" screen with RQ2A.210405.005 as the active OTA version. If I go back to the bootloader after this it will show that the active boot slot is now a.
I am truly thankful for all the replies and suggestions so far and I would love nothing more than to send this $250 bounty to a forum member.
Click to expand...
Click to collapse
Have you tried to flash to both slots using fastboot --slot=all flash
rbouza1 said:
Try the latest factory image for Verizon
Click to expand...
Click to collapse
There is no factory image for Verizon. You can't unlock the bootloader on it
MOD ACTION:
Thread cleaned.
Friends, please be civil to each other and observe Rule 2 always. Be cool!
thatsupnow said:
Have you tried to flash to both slots using fastboot --slot=all flash
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately this won't work because my bootloader is locked, so no fastboot flashing for me
Have you tried the RQ2A.210405.005 OTA?
Does
Code:
fastboot boot <extracted kernel image>
work? Not sure about this with locked bootloader.
l7777 said:
Have you tried the RQ2A.210405.005 OTA?
Does
Code:
fastboot boot <extracted kernel image>
work? Not sure about this with locked bootloader.
Click to expand...
Click to collapse
Unfortunately this did not work. Never buying a Verizon locked Pixel again!
bsmack said:
Unfortunately this did not work. Never buying a Verizon locked Pixel again!
Click to expand...
Click to collapse
How about:
Apply latest OTA
Reboot to bootloader/recovery
Apply latest OTA again
In theory that should update both slots A and B. Though it sounds like it attempts to boot slot B, then falls back to slot A, then to recovery. Which means something is really unhappy but we're pretty limited with the bootloader lock.
Was ADB enabled? Can you get a logcat while it tries to boot?
l7777 said:
How about:
Apply latest OTA
Reboot to bootloader/recovery
Apply latest OTA again
In theory that should update both slots A and B. Though it sounds like it attempts to boot slot B, then falls back to slot A, then to recovery. Which means something is really unhappy but we're pretty limited with the bootloader lock.
Was ADB enabled? Can you get a logcat while it tries to boot?
Click to expand...
Click to collapse
This was a great idea, unfortunately I think there's a failsafe in place for this. When I went back into recovery to apply the latest OTA again, as expected, the recovery mode menu showed the latest OTA which I have not yet successfully booted into (RQ2A.210505.003).
When running adb sideload to flash slot a, the package seems to transfer but instantly stops (I assume there's some flag that slot a has to not be overwritten because a successful boot to slot b hasn't happened yet). An interesting thing to note is that my phone seems to be regularly trying to boot slot b now instead of slot a, when the rescue party screen shows up I now see RQ2A.210505.003 as opposed to RQ2A.210405.005.
Tried this yet?
Google Pixel - Update and Software Repair
It isn't really clear whether it will wipe data or not.
Someone noted that the fastboot in rescue mode is different from the normal fastboot. I don't know if it will behave any differently when told to fastboot flash or other things not typically allowed with a locked bootloader.
l7777 said:
Tried this yet?
Google Pixel - Update and Software Repair
It isn't really clear whether it will wipe data or not.
Someone noted that the fastboot in rescue mode is different from the normal fastboot. I don't know if it will behave any differently when told to fastboot flash or other things not typically allowed with a locked bootloader.
Click to expand...
Click to collapse
Really appreciate you trying to walk me through this. This was something I had tried (neglected to mention in the OP, my bad!) and I do remember it recommended/prompted me to wipe and restore my phone.
Here's the interesting thing; when I select Verizon as my carrier now it says that it's NOT the carrier for my phone's current software. This was not the case before.
It doesn't seem like rescue mode can take fastboot commands, it is listed when I do "adb devices" though. Instead of "sideload" it says "rescue".
EDIT: And I did try some basic stuff like "adb shell" and "adb pull" in rescue mode, I get an instant "connection closed" error.
I charged my Mi A2 overnight and woke this morning to find that it won't boot past the Mi A2 splash screen; it shows the splash screen for a few of seconds and then dies. I read advice to hold down power and 'up' keys, this just resulted in the same. I tried power and 'down' key and that got me as far as the Fast Boot splash screen, but no further (phone just continued to display that splash screen). I've tried taking the SIM out and turning it on - no change. I tried opening it up and disconnecting the battery for 3 minutes - no change. I'd be very grateful if anyone could suggest a fix. I know this is hugely unhelpful, but I can't remember what I did to the phone in terms of unlocking the bootloader and/or rooting, but I have a feeling I left it stock (I've owned the phone for a couple of years and haven't changed anything material since initial setup).
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Martinocom said:
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Click to expand...
Click to collapse
Thank you very much for your help.
Executing fastboot reboot via adb just brought me back to the Android One splash screen for a few seconds before the screen went black.
Changing the active slot to both A and B gave me the following error message:
FAILED (remote: 'Slot Change is not allowed in Lock State')
Pressing up + power when turning on just brought me to the Android One splash screen for a few seconds before the screen went black. I held those two buttons down for several minutes and the same thing kept happening: splash screen followed by black, repeatedly.
Is there anything else I can try?
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Martinocom said:
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Click to expand...
Click to collapse
Thank you.
If anyone reading knows of a way to get my phone to boot without losing my data I'd be very grateful for your help.