Question BOOT LOOP - OnePlus 9 Pro

Hello all this night my cellphone got battery depleted and when i started to charged it it entered boot loop . Agents in OP say i need to wipe all my data but i can t afford to do that. Is there any chance i can extract data from the phone? pls i need help

There is no way to recover your data if you can't boot up your phone. That's the whole idea of security, to protect your privacy and data.
Also, make sure to ALWAYS make backups.
And is your battery now still depleted, it can't charge at all, or your phone is just not booting up completely?

ekin_strops said:
There is no way to recover your data if you can't boot up your phone. That's the whole idea of security, to protect your privacy and data.
Also, make sure to ALWAYS make backups.
And is your battery now still depleted, it can't charge at all, or your phone is just not booting up completely?
Click to expand...
Click to collapse
Its just not booting battery is 100 % . My biggest problem is that the recovery is version 1.2 and the only option is to format data and not wipe cache....

ekin_strops said:
There is no way to recover your data if you can't boot up your phone. That's the whole idea of security, to protect your privacy and data.
Also, make sure to ALWAYS make backups.
And is your battery now still depleted, it can't charge at all, or your phone is just not booting up completely?
Click to expand...
Click to collapse
The process is OP logo appears then the red dot with the 2 white dots circling and then black screen auto restarts again

henriquembm said:
The process is OP logo appears then the red dot with the 2 white dots circling and then black screen auto restarts again
Click to expand...
Click to collapse
And how much time passes before the phone goes "black" after it starts loading on the OP logo?
That sounds like a soft brick, and the only way is to either WIPE your phone as suggested by OP or re-Flash it with MSM tool which also wipes your data.
There is no way to recover your information from this stage.

ekin_strops said:
And how much time passes before the phone goes "black" after it starts loading on the OP logo?
That sounds like a soft brick, and the only way is to either WIPE your phone as suggested by OP or re-Flash it with MSM tool which also wipes your data.
There is no way to recover your information from this stage.
Click to expand...
Click to collapse
Apparently google took the wipe cache option on android 12 . so in your opinion i dont have any way of getting my children photos again ?
about 10 to 15 sec

henriquembm said:
Apparently google took the wipe cache option on android 12 . so in your opinion i dont have any way of getting my children photos again ?
about 10 to 15 sec
Click to expand...
Click to collapse
As I said, if there would be an easy way for such, the phone's security would be useless in that case.
Your storage is encrypted, and without booting the ROM (decrypting your data) you can't access it. Not saying it's impossible in the real world, but not for "us".

Why not try booting twrp to see your files? If he's rooted, it might.. Or flashing boot.img...
Or, if you can not do either, when ur phone is trying to boot( red and white dots) try holding power only button after it has been spinning for 5 seconds or so. U might feel a vibrate and then let go of power button.

thats crazy mine is doing the same thing today, i let the battery deplete and now its bootlooping exactly the same

Shooter7889 said:
Why not try booting twrp to see your files? If he's rooted, it might.. Or flashing boot.img...
Or, if you can not do either, when ur phone is trying to boot( red and white dots) try holding power only button after it has been spinning for 5 seconds or so. U might feel a vibrate and then let go of power button.
Click to expand...
Click to collapse
Because you can't boot TWRP on a locked bootloader, and neither is there a TWRP for A12 ROMs.

Hi Guys, i just have the same issue ...
Let me know if there is anything to do or if any OP service center can help before i click wipe data.

Hi all,
My 1P did this too, I ended up shutting it off by holding the power + volume UP button at the same time for some 10 seconds. After that it rebooted and seems to be working okayish. I still moved all my photos and important data to my harddrive after this just in case. Hope this is helpful at all!

henriquembm said:
Hello all this night my cellphone got battery depleted and when i started to charged it it entered boot loop . Agents in OP say i need to wipe all my data but i can t afford to do that. Is there any chance i can extract data from the phone? pls i need help
Click to expand...
Click to collapse
You don't need to wipe your phone, see my other message!

Related

Google Nexus GSM stuck on google boot loop

My nexus is stuck on the google boot loop since this morning, i am on stock firmware no root or no nothing, can someone suggest me how can i fix this issue. i have mac and does not have access to any windows machine so i will be greatful if the suggestions will be accordingly for mac
switch off your phone . if you cant switch off the phone then take the battery out and put it back in. Press the volume up and down key along with the power key . this will take you into the bootloader. press the volume down button and navigate to the recovery section. press the power button . this will take you to the default recovery on your phone.
At that time you will see an android robot with an exclamation mark. press the volume up and down key along with the power once again. you should now see the option to update your phone , wipe/reset options. wipe the phone and reboot it . you should be ok after that.
I had the same problem with my gsm gnexus.
Hopefully factory reset using recovery works as krunal1981 suggested. If it doesn't then you will have to use Odin or Heimdall for Mac and preform a full restore. If you have a warranty and the first doesn't work, take it back to Verizon and tell them that your phone isn't booting anymore and they'll replace it.
krunal1981 said:
switch off your phone . if you cant switch off the phone then take the battery out and put it back in. Press the volume up and down key along with the power key . this will take you into the bootloader. press the volume down button and navigate to the recovery section. press the power button . this will take you to the default recovery on your phone.
At that time you will see an android robot with an exclamation mark. press the volume up and down key along with the power once again. you should now see the option to update your phone , wipe/reset options. wipe the phone and reboot it . you should be ok after that.
I had the same problem with my gsm gnexus.
Click to expand...
Click to collapse
Thanks Much this solved all my problems with the phone as of now, wonder what caused the phone to go in that ever ending loop
Question: Did wiping from stock recovery also erase your internal storage (/sdcard) or not?
Anyway - I have had this problem too, and all I can say is: A full wipe fixes it but only temporarily. It will happen again most likely. I believe it is a hardware problem with the internal memory. Next time it happens you should seek a warranty replacement.
when i do this all i get is the droid robot with an exclamation mark. my phone seems to go crazy at moments just keeps power cycling and gets soooooo hot and verizon just keeps trying to give my refurbed ones doing the same thing
galaxy nexus stock
Yes.. resetting the phone from the stock recovery erases everything
---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------
when you get the android with an exclamation mark , press all the hardware buttons on your phone i.e volume up , volume down and the power button. this will take you to the stock recovery .
Phone just did this last night, it was on my desk and I saw it reboot to the google logo after which it would continually random reboot.
Did a factory wipe/reset, fixed temporarily, but within minutes, begins to do it again. No sim card in, etc.
Curious if there's been any more progress on this.
sphish said:
Phone just did this last night, it was on my desk and I saw it reboot to the google logo after which it would continually random reboot.
Did a factory wipe/reset, fixed temporarily, but within minutes, begins to do it again. No sim card in, etc.
Curious if there's been any more progress on this.
Click to expand...
Click to collapse
It's a hardware defect. The only permanent fix is a warranty replacement.
Fortunately the units with this defect seem to manifest it within the first few months so that the owner can figure it out and get a swap.
So, a bit more information here. I'll get to the result at the end.
I did the factory reset from recovery, that would allow the phone to boot and stay on for a few minutes, I found, after which it would go into boot loops again.
Once the phone was on, I had USB debugging on, and was looking at the phone files when I noticed that folders that were originally on the phone from before the wipe @ recovery would begin to appear, one by one. Complete with all the original files that I had before the factory reset. Once I noticed this, I performed a full wipe from the phone OS (Settings -> Backup & Reset -> Factory Data Reset).
This actually wiped everything, 100%. Made sure not to restore all apps from my google account, either, and guess what, more than 24 hours of not a single reboot. Heavy use for those 24 hours, as well. Been stressing the phone HARD.
Near as I can tell, there was some file or app that for whatever reason probably went rogue and was causing the phone to encounter something which I can only relate as being similar to a core dump/BSOD if you were on linux/windows. I don't study phone OS culture enough (I'm an auto service technician by trade) and haven't compiled a Linux box in over 10 years, so I'm a bit rusty on it, but it honestly doesn't surprise me that this is a definite possibility given all the different hardware configurations and all the different apps that are out there that are expected to work on everything.
So, there you have it, my experience, my fix, and what worked for me (so far). I'll keep everyone posted if I notice any random reboots or any future reboot loops.
I believe it's a hardware level defect with the eMMC. It keeps working fine again until it attempts to write some important file to that exact sector of the internal memory. Then it corrupts again and back to the boot loop.
When I had a defective unit, the longest it'd last before looping again was 20 days. Sometimes as few as five hours. If it spontaneously starts looping again - it's a hardware problem and there's no fix. You need a replacement.
Sent from my Galaxy Nexus using Tapatalk 2
So, here's an update on the situation with my phone.
The update, is that there is no situation. The phone is operating perfectly fine. Had it's OTA update to Jelly Bean a couple/few weeks back now, and is still running smoothly. Moderate to heavy data/wifi usage (past 10 days has seen 700mb wifi traffic, 1.2gb 3G/HSPA traffic) and phone hasn't been rebooted in over 300 hours.
I'll give periodic updates every month or so.

KF wont boot properly when battery runs out

My KF gets stuck in cyanogen boot logo when 1. KF suddenly turns off or 2. Battery becomes low. I need to reflash it just for it to work again. PLEASE HELP any idea?
Plug the device into a power source
Hold the power button for 10 seconds to shut it off
Let it charge
soupmagnet said:
Plug the device into a power source
Hold the power button for 10 seconds to shut it off
Let it charge
Click to expand...
Click to collapse
no, the issue is more complicated than that.
Here's a scenario, for example i'm using it still @ 60% battery, then suddenly it will shut-off, when i try to re-start it it won't boot properly, it get stuck in the cyanogen logo, it seems some file gets corrupted, the only for it to work again is to reflash. (which im getting tired off )
vertcam9 said:
no, the issue is more complicated than that.
Here's a scenario, for example i'm using it still @ 60% battery, then suddenly it will shut-off, when i try to re-start it it won't boot properly, it get stuck in the cyanogen logo, it seems some file gets corrupted, the only for it to work again is to reflash. (which im getting tired off )
Click to expand...
Click to collapse
I see.
There was a user a while back that ended up with the eMMC bug and had to repartition his device to skip over the bad blocks. In doing so, he didn't allocate enough space for a proper cache partition (something like 150MB, I believe) and his device would do the exact same thing.
I would suggest clearing your cache and see if that helps. You may have to do a true wipe though, because I don't think a wipe in custom recovery will cut it.
You might want to check the cache, system, and boot partitions for bad blocks while you're at it.
Try other ROM
vertcam9 said:
My KF gets stuck in cyanogen boot logo when 1. KF suddenly turns off or 2. Battery becomes low. I need to reflash it just for it to work again. PLEASE HELP any idea?
Click to expand...
Click to collapse
From my experinces with KF1 for two years, switch to stock ROM 4.3 AOSP from Hashcode and everything became wonderful. better battery life, no freezing

Need some help - possible defective hardware?

First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...
You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...

Useful advice for scenario: Blank TWRP + Bootloop After Rom Flash.

I had almost given up on my phone and was coming here to get some help.
As I was writing up this thread I had left my phone on the blank screen I'm about to describe.
then i noticed out of the corner of my eye the screen light up.
So my advice is, if you ever have this scenario happen it may take over 20 minutes for TWRP to even load.
This may not be something that can be duplicated, but hopefully it can be useful for someone who would panic about this like myself and keep trying things.
(I have a sneaky suspicion about my SD card now, I believe it may have become corrupted during the install.. breaking the rom.. and then making the phone hang while loading twrp.)
Mate - mt1-u06
(Ab)using TWRP v2.8.1.0
Thanks
So today I wanted to try out this:
http://forum.xda-developers.com/ascend-p6/ascend-mate/rom-omnirom-t3092487
and when I flashed it through twrp I did the install it was all successful but I forgot to wipe before rebooting (woops) So i thought hmm maybe it didn't need it,
so left it for a few minutes, realized this is a bootloop and needed to be done again.
So I was like okay I'll just shut it off and go back into recovery.
Did it like I normally would (power and the volume) and my heart kinda sank when I got a black screen (back-lit so you could tell it was still on).
weird usually it loads...
powered it off and let it load normally again to see if it was just taking a while to setup maybe to just get into the OS.
Nope 1 hour later nothing.
Have tried getting into recovery a million times but its still blank.
and to get the nooby stuff out of the way:
Fully charged before I did it and It wouldn't even turn on if it wasn't so that's kind obvious.
Mate - mt1-u06
using TWRP v2.8.1.0
Click to expand...
Click to collapse

Question What'll happen if phone shut down due to low battery in fastboot/recovery and is there any fix? (POCO F3)

I know flashing roms are easy. But it might be difficult for newcomers like me. I have always a question in mind what'll happen if my phone shut down due to low battery in fastboot/recovery. If I format the OS before shutdown, is it possible to charge the phone offline without no OS then continue flashing roms?
##Following things happened with me.
I was in MIUI 12.5. I installed Pixel Recovery to flash PE12 via adb sideload. Then I cleared all data/cache. When I tried to update the rom by sideload, it didn't work. I wanted to search the internet and as it would take time, I tried to turn the phone off. I couldn't even shut the phone to save battery. Whenever I pressed power button, instead of shutting down, it always took me to the bootloader menu. Thats when I thought about this question.
that question is so out of the box, i doubt anyone can give you an answer with proof
but yes, i believe it is possible to charge even without OS and no, i dont have any proof to back this up
That's why you need to charge phone first at least until 50% up before flashing any rom.. otherwise if still happen phone shutdown while flashing, yes you still can recover as long your phone bootloader still at unlocked stats also phone still can go into fastboot
If it shuts down when in fastboot/recovery because the battery is empty, you simply charge it and reboot, that should cause no harm. Shutting down while flashing a ROM however is a totally different story. You might get lucky and be able to boot the phone back into fastboot/recovery or you could end up with a paperweight.
jadephyre said:
If it shuts down when in fastboot/recovery because the battery is empty, you simply charge it and reboot, that should cause no harm. Shutting down while flashing a ROM however is a totally different story. You might get lucky and be able to boot the phone back into fastboot/recovery or you could end up with a paperweight.
Click to expand...
Click to collapse
I did shutdown the phone within fastboot to cancel flash all and lock....then booted in forced fastboot end flashed with flash all to not lock the bootloader....and had no prob....! I think those partitions are protected against those scenarios....
Following things happened with me.
I was in MIUI 12.5. I installed Pixel Recovery to flash PE12 via adb sideload. Then I cleared all data/cache. When I tried to update the rom by sideload, it didn't work. I wanted to search the internet and as it would take time, I tried to turn the phone off. I couldn't even shut the phone to save battery. Whenever I pressed power button, instead of shutting down, it always took me to the bootloader menu. Thats when I thought about this question.
Addymore said:
I did shutdown the phone within fastboot to cancel flash all and lock....then booted in forced fastboot end flashed with flash all to not lock the bootloader....and had no prob....! I think those partitions are protected against those scenarios....
Click to expand...
Click to collapse
No. NO NO NO and NO.
You were lucky. This can totally brick your phone. Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
dreamytom said:
No. NO NO NO and NO.
You were lucky. This can totally brick your phone. Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
Click to expand...
Click to collapse
I think it is because I forced fastboot mode after few seconds of starting flashing....by the way I was avoid the flash and lock option that I selected by error while I wanted flash and clean...
I think, there is no ptoblem, fastboot Mode is Read Only Memory, no one can write/edit this think.
No matter you abort the flashing prosses , or the device loss power from battery, didn't affect the fastboot sector/bios on PC
*IMO

Categories

Resources