[UNBRICKED] Data Recovery For Soft-Bricked OnePlus 5T - OnePlus 5T Questions & Answers

I'm really anxious and nervous about this so I'll simplify this as much as I can; recently my phone was turned on on top of my desk and randomly restarted. I thought little of it, as it quickly went through the OnePlus logo (it began to take longer the second time I restarted it) and Android splash screen, but then stopped on the circles animation and remained looping there. I have very important data on it that I'd like to recover and WILL NOT factory reset (flash) my phone.
The battery icon and percentage still show up when I plug in the device. I still have access to Recovery Mode, Fastboot, and Sideload through their key shortcuts. I previously had USB Debugging enabled but can't authorize ADB since I can't check the confirmation dialogue box (shows up as "unauthorized" in command prompt). I had very little storage (less than 250mB) for the last few days. I don't have root access, custom recovery, or an unlocked bootloader.
I already tried clearing my cache; if I restart after doing so it only takes a few seconds to pass the OnePlus logo as opposed to the ~20 seconds it previously took. This delay raises every few restarts. I've tried waiting many hours to see if anything would happen or if ADB would start functioning. I also tried fully draining my battery overnight and nothing happened. My files are not deleted/fully corrupt since I could still see them when flashing through internal storage from Recovery Mode. OnePlus chat support said I have to flash my phone and Twitter support refused to respond. Local data recovery centers said I could get my phone shipped to them for a free diagnostic, should I do so or is there a way to unbrick or recover my data at home?
Is there anything I can do? Thank you very much!... for now I'll just remain depressed...
TL;DR - My phone's stuck at the circles boot animation and I want to recover my files or fix the soft-brick without resetting. I don't have root access, custom recovery, or an unlocked bootloader.

UPDATE: I boot into Recovery Mode and "Reset System Settings"- my phone rebooted with 112 gigabytes of storage already taken up and all of my Android/data folders empty! I lost very little as I set my save folders to other locations! It looks like the error was not having enough storage! OnePlus chat support said that I had to factory reset my phone, DO NOT listen to them! MY PHONE IS UNBRICKED!
Check out other responses:
https://www.reddit.com/r/Oneplus5T/comments/ahfabg/data_recovery_for_softbricked_oneplus_5t/
https://forums.oneplus.com/threads/data-recovery-for-soft-bricked-oneplus-5t.986096

Related

OPPO Keyboard has stopped working, leading me to stuck on a fastboot loop.

Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
daiichi said:
Please help. This is a serious matter for me.
Started having this problem at February 14th, 02.10 AM.
Have been looking for the answers in the Oppo Forums too but still got no answers.
Okay, I have a habit, which is moving all of my applications from my internal storage to my external SD card, after I let those applications doing their functions and programs and features and so on for a while. It's not a big deal for me to set up my phone again after I restarted it, and usually it works perfectly. Just restart and I would get to operate my phone again. However, this time, I got a bad luck. The worst one, considering the fact that I'm all-around-gadget.
Here's the results I got from reading a lot of threads (not only from this forum and OPPO forums):
OPPO Swype Keyboard has stopped working? Really?
After restarting my un-rooted Find 7 (9076), I cannot type the password on my lock screen. Like any other Android devices, it would always come back to it's system or default applications, I knew that fact. But this time, when I touched the blank space to type my password, nothing came out. No OPPO Keyboard, which happened to be OPPO's default keyboard. No other keyboards. None at all.
So, I cannot do one single thing to my phone except just turn it on and stared at it like a complete idiot.
Then I decided to turn my phone off and turn it on again after a while.
But still, the same thing happened. No keyboards.
That time, I decided to turn off my phone again and pulled out the battery and my external SD card.
After putting the battery back (External SD Card was still outside), and turned it on again, the same thing still happened.
Sliding my fingers up and down, nothing happened. The touchscreen was still there, showing me my date and time even though I was sliding my fingertips up and down.
Not too long after, I felt my phone got warmer and warmer. I tried double-clicking the home button, which I already set to unlock the lock screen, was also useless. The screen was still black and locked. When it got over-heating, automatically I pulled out the battery without even turning off the phone.
That one was my fault. I knew, and well, honestly speaking, this is the first time I'm in this kind of situation. In the past, my Find 7 would just suddenly restarted itself then everything went back to normal, but not this time.
And here's the beginning of my Fastboot Loop.
Fastboot Loop on un-rooted device
After pressing the Power button and the Volume Up button at the same time, it would bring you to the Recovery Mode. When I did that to my Find 7, it brought me to a black backgrounded screen with cute OPPO mascot and some Hanzi (Chinese handwritings). Picture attached.
I tried to wait for 2-3 hours and found nothing happened.
Pulling the batter out and putting the batter back would do the same.
In other words, I am not able to gain access to my Recovery Mode.
Why didn't bring the phone to the service centre?
I thought about this already.
When I tried to connect my phone to my pc, it can detect the phone but cannot access the files because the phone was still locked with the password.
Usually, the service centre requires us to unlock the phone if there's a problem with it, right? In my cases, yes.
I was searching all night to find out the answers.
I found some threads about the Fastboot Loop thing and etc, but they are only for rooted devices.
I'm using:
OPPO Find 7 (9076)
Color OS 2.0.5i Beta
Android KitKat 4.4.2
Device is not rooted, still original.
Still dealing with the same problem until now (the time I post this thread).
Anyone has solved this problem and guide me step by step to finish this?
Click to expand...
Click to collapse
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
treacherous_hawk said:
boot into recovery and format the phone, this should fix it. If you want to backup your data, just boot into fastboot, connect phone to pc, run fastboot command from sdk tool, push custom recovery, flash twrp, make nandroid backup, fomat phone along with all the storage and then flash oppo stock rom (you need to download) or any other custom rom with gapps. To restore use nandroid manager, do not restore system files if you are flashing custom rom.
Click to expand...
Click to collapse
Thank you for your help Sir.
But, my Find 7 already operated normally again since I left it for a few days uncharged and off.
Then I got into Recovery Mode by pressing Power button and Volume Down button (not Volume Up button) while in the middle of my fast-boot loop.
It worked. I could gain access to ColorOS Recovery Mode.
So, I reset my Find 7, then re-installed my applications and everything again.
Thank you for answering!

Backup internal SD on phone that hangs on boot (at Verizon Screen)

I have a non-rooted VS986 (probably 26A).
Recently I ran out the battery and the phone died. When I charged it and turned it back on, it stayed stuck at the Verizon boot screen.
I hadn't really changed anything recently, and I did not take the most recent OTA (27C) so this just seems like a random hardware failure.
I can boot into Recovery, but if I choose "Safe Mode" or "USB Debug Mode" the phone just hangs at the Verizon Screen.
I tried to Wipe Cache and restart, but it just hangs at the Verizon screen.
I *can* boot into Download mode.
I would really like to back up the internal SD card--photos, settings etc. if possible.
Is there anything I can do at this point just to get an ADB prompt or something that might allow me to perform a backup (even if limited)?
Sounds like a motherboard failure. You could try booting into download mode and using adb to pull your files but you'll have to know the exact path to their location. And to do that you would have had to have USB debugging activated.
If that doesn't work then your SOL. Time to use your insurance or warranty if it's still good.

Problem with booting G4

Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market
Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.

T-Mobile S8+ [G955U] -- Factory reset resulted in complete wipe & no longer boots up.

T-Mobile S8+ [G955U] -- Factory reset resulted in complete wipe & no longer boots up.
I have a Samsung galaxy S8 plus (T-Mobile) [SM-G955U]
Current Firmware:
G955USQU4CRE9
I'm using windows 7 to attempt to repair my phone.
My problem is as follows...
A few weeks ago my phone started giving me the dreaded:
"Unauthorized actions have been detected..."
error code and sending my phone to restart.
This has happened to me in the past on other phones so i thought, ok. restart and it should be fine. However, this kept happening... the next day and on the 3rd day it happened about 3 times in a row. At this point I was cautious and backed up all my files, turned on USB debugging and shut off my wifi & data.
I then proceeded to do a factory reset from the settings. Once it restarted I got a weird error stating something like no such recovery file could be found. When I saw this I knew I messed up because I didn't first take a backup of my system & recovery...
I got a hold of T-Mobile who walked me through their reset steps, none of which worked. They had me contact Samsung and I did but to no avail. Simply stated they mentioned they could fix it if I had warranty, if not I would have to pay for repair.
Either way I sent all information to Samsung and they have not gotten back to me even though they mentioned we'd hear back in 48 hours. (it's been about a week) I've tried to reach out since then but I haven't had a lot of time to sit on the phone with their elevator music...
Ever since then I've tried everything from Samsung Smart Switch to re-flashing through Odin with no luck.
I've tried all of the reset options...
Hard reset
Soft reset
Wipe cache (recovery mode)
Wipe and factory reset (recovery mode)
Simulated battery pull
etc., etc., etc.
Nothing works. Odin flashes correctly (i get "PASS") and the phone turns off but does not turn back on.
I've tried several tricks to get it to turn back on but it won't go past the boot screen (Samsung Galaxy S8+ screen)
I've flashed, re-flashed, wiped, reset, etc.
Now smartswitch doesn't even work on it because it does not recognize the device...
When i connect my phone now it just shows up as the qualcomm chip. I get "Qualcomm HS-USB QDLoader 9008" under devices...
ADB only works when it's in download mode or recovery mode but it doesn't recognize the device either...
Another problem is the increased time it takes to get into the boot menus (download or recovery).
Sometimes when I haven't touched my phone for a whole day I can get into download mode within 10 seconds or less but the more I try it and especially if I successfully flash stock software, the next time booting into recovery or download mode can take up to 5 minutes (holding the button combination). Recovery mode is worse.. even after 24 hours without touching the phone it will come up maybe in 3 minutes but has taken as long as 7 minutes... my fingers are in pain.
Essentially, even after successfully flashing my phone will not boot. and when i hold vol_down + power i can sometimes get the boot screen but it won't go past that.
Also, None of the above boot options work if my phone isn't connected to power--these options only work when it's plugged in. If my phone is not plugged in it will not vibrate, light up, boot up, or do anything other than behave as a paperweight.
I believed it may have been a charging issue so i left it plugged in overnight and even went to download mode and plugged it in for a few hours but that doesn't affect it at all. Even if i'm in download or recovery mode it'll turn off right when i unplug the device.
I'm trying to get it to the best buy that's approved for samsung repair but when I called they said they wouldn't repair it anyways because i didn't buy it there... -_-
Please let me know if I need to provide any other information. I'm trying to get an image of the recovery screen so you can see the error it gives me... Something about no file found. This is increasingly difficult though because some times it takes too long to get into these modes and I leave it alone and come back to it later.
Has this happened to anyone else? Can someone provide some sort of advice or a method to fix this?
thanks in advance.
Can you download the Qualcomm HS-USB QDLoader 9008 driver, and then see if you can fastboot oem-unlock and see if it unlocks your bootloader

Recover files from a Pixel 3 XL that cannot boot anymore

Hello everyone,
I come here because I have a big issue with my Pixel 3 XL.
It's up-to-date regarding the OTA updates i.e. I have the latest firmware installed.
I've never done anything special regarding "tweaking", such as enabling the developer mode i.e. the developer mode is unfortunately not enabled.
I was browsing the Internet and the phone suddenly rebooted unexpectedly. Then it was in a reboot loop. I pressed power and volume down buttons to enter the boot menu.
The boot loop stopped but I was unable to do anything to make my phone boot properly again. In the recovery menu, there is no option to wipe the cache partition.
There should be roughly 400 MB of free space on the phone. I was thinking that maybe this could have been the cause of the issue.
When the phone is off and not plugged to the charger, the percentage of battery decreases. When the charger is plugged, the percentage of battery does not decrease but does not increase either. It seems I cannot charge the phone anymore. Currently remains 13%.
When the phone is off and I press the power button, the Google logo shows up and the progress bar below has just time to appear before the phone vibrates and goes off.
I don't care much saving the phone, but it's extremely important to me to be able to recover the photos it contains (standard DCIM folder).
Most of what I found googleing so far is about wiping the cache partition, but there is no such option on my Pixel 3 XL.
Since the developer mode (USB debugging) was not enabled when the phone was working fine, I cannot use adb to pull files. I can sideload though. As far as I understood, in my situation it is not possible to enable the developer mode.
I've just heard about TeamWin Recovery Project, and still trying to figure out if this can help me.
Could someone please tell me how I can, at least, backup my photos?
Of course the best would be able to boot the phone normally, but really my first goal is to save my photos.
Is there a way to reflash the firmware with the same version, or another version, without losing data, just like what happens on a regular update e.g. when a new Android version is deployed?
Thank you.
magrac said:
Hello everyone,
I come here because I have a big issue with my Pixel 3 XL.
It's up-to-date regarding the OTA updates i.e. I have the latest firmware installed.
I've never done anything special regarding "tweaking", such as enabling the developer mode i.e. the developer mode is unfortunately not enabled.
I was browsing the Internet and the phone suddenly rebooted unexpectedly. Then it was in a reboot loop. I pressed power and volume down buttons to enter the boot menu.
The boot loop stopped but I was unable to do anything to make my phone boot properly again. In the recovery menu, there is no option to wipe the cache partition.
There should be roughly 400 MB of free space on the phone. I was thinking that maybe this could have been the cause of the issue.
When the phone is off and not plugged to the charger, the percentage of battery decreases. When the charger is plugged, the percentage of battery does not decrease but does not increase either. It seems I cannot charge the phone anymore. Currently remains 13%.
When the phone is off and I press the power button, the Google logo shows up and the progress bar below has just time to appear before the phone vibrates and goes off.
I don't care much saving the phone, but it's extremely important to me to be able to recover the photos it contains (standard DCIM folder).
Most of what I found googleing so far is about wiping the cache partition, but there is no such option on my Pixel 3 XL.
Since the developer mode (USB debugging) was not enabled when the phone was working fine, I cannot use adb to pull files. I can sideload though. As far as I understood, in my situation it is not possible to enable the developer mode.
I've just heard about TeamWin Recovery Project, and still trying to figure out if this can help me.
Could someone please tell me how I can, at least, backup my photos?
Of course the best would be able to boot the phone normally, but really my first goal is to save my photos.
Is there a way to reflash the firmware with the same version, or another version, without losing data, just like what happens on a regular update e.g. when a new Android version is deployed?
Thank you.
Click to expand...
Click to collapse
I don't think there is anything you can do without developer mode, but aren't your photos backed up to Google servers at https://photos.google.com?
dcarvil said:
I don't think there is anything you can do without developer mode, but aren't your photos backed up to Google servers at https://photos.google.com?
Click to expand...
Click to collapse
no, I don't synch with the Google cloud.
I've just read that in order to install TWRP, I needed a unlocked bootloader, which is not my case. Unlocking the bootloader would cause my data to be wiped (for security reason it seems). Is that true?
magrac said:
I've just read that in order to install TWRP, I needed a unlocked bootloader, which is not my case. Unlocking the bootloader would cause my data to be wiped (for security reason it seems). Is that true?
Click to expand...
Click to collapse
Unfortunately, that is correct. Unlocking the bootloader wipes the data. I know of nothing you can do.
was your problem resolved?

Categories

Resources