Database Develop

Retrieving Data on Broke Phone

Need someone with tons of knowledge here to help me out
I'm currently dealing with a Nexus 6, unrooted, stock.
The phone was dropped and the screen was destroyed. During the drop something internally must have been damaged as the phone starts the At&t music up and resets immediately and will keep looping until the power dies or I put it into the fastboot screen to shut it up, in which the phone stays on that screen. (or at least theres where im assuming its going)
The thing is, my computer recognizes the phone as an android device and shows the android device bootloader on my device manager on my cpu. Every time I try to get into recovery (or at least how I recall doing it without a screen to assist) the phone just restarts to the at&t music once again...
Is there any hope here for retrieving my data on this thing? I figured I could do something with adb although im not too savvy with it. Just assuming since the computer does recognize the device in some way, it is possible hopefully.
Btw I dont think debugging is on atm.
Any help would be super appreciated. Even willing to donate to anyone that may be able to assist me in this.

If and when Mobiletechvideos gets back up and running, they can more than likely save the entire device and if not at least get your data. But unfortunately because of the high demand for their services, they have gone into a temporary work hold until all current orders are complete. Either way, I would try to get ahold of them and see if they can assist or can point you in the right direction.

If it is unrooted with stock recovery and not booting up to android, there will be no easy way to get your data off.
It is possible, though very unreliable and extremely difficult to unlock the bootloader, flash a custom recovery, create an image of the data partition and scan that on a computer with data recovery software, but that really isn't worth doing.

hi ... how r u .... i have this problem too .... broken screen ... screen totally black ..... stock rom no root no recovery ...... debuging not enabled
http://forum.xda-developers.com/showthread.php?t=2786395&nocache=1
this guy said in his thread i can access the phone via computer but i need to enable debugging which i donno how to do with screen totally black
any suggestions is really appreciated

OnePlus 3T automatic shutdown after 5-20 seconds in use, no bootloop, data recovery?

Hello to the community,
its my first post here but got a serious problem with my OnePlus 3T and looking for professional help. As the titel says my device performs an automatic shutdown after 5-20 seconds when already in use. Which means I can enter the unlock scheme, enter the PIN and the device is fully startet. But neither any work nor data saving/recovery actions have been successful so far. I try to explain what happened and the issue in detail, hope some professionals have ideas or can help.
Beginning of the issues:
I had a freeze during a Whatsapp call, after rebooting the device worked, network as well as wireless lan got connected, I could even send/receive Whatsapp messages before it would shut down after 5-20 seconds. A quick "wipe cache" or start in safe mode didnt help, the error kept occuring every time so I performed a "reset system setting". Now after booting I can set-up my new OS but the error keps occuring. So within the time I can get max. to the step to connect to the wireless LAN before the device shuts down again.
I have tried a few things and beside the automatic shutdown after a full boot/startup everything seems to work:
-display fingerprint works, I can enter the unlocking pattern as well as enter the PIN, no errors there
-battery seems to work, no fast discharging, Dash charging works, error occurs also during charging.
-device does not produce worrying amount of heat, tried also restarting after having it in a sealed bag for 1h in a freezer in cause its a thermal issue with rapid overheating but no improvement
-vie install from ADB I can load the current 1.5Gb OxygenOS via USB, it unpacks 100% and after rebooting start to set-up the new OS, I get to step with wireless setup maximum before reboot.
-via "install from Internal Storage" I see the full folder structure existent and browse through it for unlimited amount of time which makes me 100% confident all data/apps are basically there.
-unfortunately via ADB Sideload I can only load the OS via USB but the "pull" or "shell" dont work, if I would get that working it would be the solution.
-after rebooting the device is recognized via USB on my PC as the OnePlus phone before it shuts down after a few seconds.
-in fast boot/Recovery the device works for an unlimited amount of time, the automatic shutdown is only performed after the device is fully booted/started and the screen for my unlocking pattern appears. From there on I got between 5-20 seconds to do something. As I now got a new OS I get maximum to the step with connecting to WiFi.
I am in contact with the OP Support Service but if I send in my device for repair the memory is 100% gone. I am open for any ideas on how to either fix the device or at least recover the data. For example if I could get "pull" and "shell" commands working. Are there any known hardware/software issues known to cause such a behaviour?
regards and already a merry christmas,
ManuelW

Have you got an unlocked bootloader? This would make stuff a lot easier, because you could boot an alternative recovery and from there use MTP mode, but if it's locked, then unlocking it would unfortunately erase everything.
The issue is strange, it sounds like either kernel panicking or physical damage (maybe bad soldering on CPU? but that would be even more strange, I haven't heard of such an issue on SD820/821), I had a problem with Nexus 5X, when it bootlooped out of the blue and the solution was to disable "big" cores

I think the status is locked. I cant have the phone turned on long enough to be able to retrieve the status via keyboard entry. When I reboot to fastboot I see:
-Secure Boot: Enabled
-Device state: locked
If I use minimal ADB/fastboot I see the device with USB connection via "fastboot devices" and if I check via "fastboot oem device-info" I retrieve:
-Device tampered: false
-Device unlocked: false
-Device critical unlocked: false
-charger screen enabled: false
-Have console: false
-Boot_mode: normal
EDIT: "fastboot oem unlock" returns "FAILED (remote: oem unlock is not allowed)"
regards,
Manuel

Hi
I am also facing the exact same issue on my OnePlus 3..did you get any solution for it?
Any leads will be helpful, thanks

Can anyone please reply on this?

I am also facing the same issue in my OnePlus 3
Can anyone please help me

Unfortunately no, the OP 3T is still laying around as "half-brick". The OnePlus Customer Service was completely worthless, quite certainly one of the worst service experiences so far I have ever had - after more than 8 weeks of contact no help or any hint for resolution. Now got a Mi 9T Pro and still looking for a service where I could send my 3T.
regards,
Manuel

ManuelWenny said:
Unfortunately no, the OP 3T is still laying around as "half-brick". The OnePlus Customer Service was completely worthless, quite certainly one of the worst service experiences so far I have ever had - after more than 8 weeks of contact no help or any hint for resolution. Now got a Mi 9T Pro and still looking for a service where I could send my 3T.
regards,
Manuel
Click to expand...
Click to collapse
Okay, thanks for the reply.
I dont thinks it's hardware problem though bcz my phone works perfectly in fastboot/recovery mode, might think something related to system ui crash.
Does any experts help us to revive our phone.
btw i also got redmi k20 pro.

Though not a solution but my OP3 also behaved similarly few times in last year. Initially, I thought its overheating as my screen was not sticking to bezels perfectly and can see a gap and spongy action too. What I recall I was able to make the device work among other things by switching off and/or restarting my device within the 10-15 sec of usable time quite a few time. Naturally, I usually cleared cache also. If my memory served right then this issue didn't occur after I pasted my screen tightly with the back (used feviquick and masking tape).
Right now I'm at this page coz the issue occurred again and the screen appears to be bulging in the center too (though this may not be the cause). I'll try to use the above method and post.
---------- Post added at 03:08 PM ---------- Previous post was at 02:14 PM ----------
So I was able to get my phone working again
I think doing reboot before the device itself powered off did the trick. Through I noticed one more thing is my auto recording for phone calls got disabled and earlier also I had a lingering feeling this loop bug has to do something with phone call and recording. Though as earlier this issue may present itself again if I receive a call when my phone is loaded with tasks. Does call recording also try to access conflicting resources ?? This is not absolutely clear but similar to my experience last year the device is working normally as of now.

News from my side: After the phone laying around for a couple of months I gave it another try last week by charging and then booting it. Issue seems removed, device worked flawless for a couple of hours and I could retrieve all the data I wanted - USB connection was stable for hours to transfer over 60Gb of data.
As an engineer I do not have a real explanation, maybe its somewhat derived with power supply as after a couple of months it was certainly ensured the device was drained to zero?

Question HELP - Bootloop into Recovery without any attempt to flash

Hey, everybody!
I got a problem and hope to find help in here:
I recently got my Mi 11 Ultra (12GB / 512GB) from Tradingshenzhen. I bought an unmodified chinese version. After setting up my phone a few days ago the only things I did was changing the language of the Play Store using Morelocale 2 and deleting 2-3 (really unnecessary) apps using ADB. I didn't flash anything, didn't unlock the bootloader or didn't even start the unlocking process.
Everything worked fine for a 2-3 days now. Tonight I realized that the phone was off. As I was thinking that the battery was empty (there was a message a while before that the battery was low) I connected the phone to the charging cable and did a long press on the power button trying to turn it on. I put the phone aside and went to bed.
Today in the morning I took the phone and saw that it was obviously in some kind of menu I hadn't seen before. It says " Main Menu MIUI Recovery 5.0". There are three options: reboot, wipe data and connect to MiAssistant. When I am choosing "reboot" the phone tries to reboot but ends up in Recovery Mode again. And again. And again.
How is this possible? Anyone knows what happened here? As I said...I didn't flash any ROM or opened the bootloader.
Unfortunately there is one photo on the device that I need and haven't uploaded to any cloud yet.
Thanks in advance!

Can't see any other options that will work without losing that photo.....
Maybe an expert could help you but I'm not sure you will be able to reflash yourself without Data wipe....

Thanks!
I actually wiped the data and reset the phone. Works now again but the photo is lost.

There is a way to retrieve data from a board but it involves taking the whole phone apart , which is risky, and connecting a couple of wires to some points on the circuit board....
Not for the feint of heart and I haven't seen it done yet on this model but there's a YouTube video of it being done on an older xiaomi phone....

Mi 9 Touchscreen does not work (likely software issue), is there a way to get my data?

Hello,
my Mi 9 (stock rom, locked bootloader, never touched anything) recently got into a boot-loop apparently for no reason. After some tinkering it turned on again. Sadly the touch screen does not respond for some reason. The problem is the last backup of the phone is not so recent and I would really like to get all the photos of that phone.
What I already tried:
Connect Mouse and Keyboard via an OTG cable => not recogniced
Letting the battery drain completeley hoping it would reset itself
Fully charging the battery
Connect ADB => cannot authorize without touch
Connect Xiaomi PC Sync software => does not connect probably needs authorization as well
Stock Recovery does not allow to wipe caches
Last resort was to open up the phone and disconnect the battery and reconnect after a couple of minutes (touch did not work before that)
What is not working:
Touch
Face Unlock
USB OTG Peripherals
USB connection to download photos to PC
What had happened:
Phone randomly went into a boot-loop aparently for no reason
At first booting into Safe Mode worked but not for long
Draing the battery completely did not and fully recharging it => Now the phone turns on again in normal mode as well as Safe Mode
Assuming the initial issue was related to a very weak battery
Battery was already weak before everything happened
Now battery only holds charge for a couple of hours in standby
Sadly after booting the things mentioned above did not work anymore
Maybe failing to boot so often has done anything to the software or the cache on the device
Also storage was already pretty full before everything happened, might play into it
Tried many things, last resort was to open the phone and disconnect the battery for a few minutes => did not work
Touch malfunctioned already before that, so it is unlikely that I caused any hardware damage
What i am looking for:
To get my pictures back, I know if I had done a proper backup we would not be in that situation.
Have not yet tried:
I don't know if there is a way to flash the stock ROM via fastboot or if this could help
Could this help?
Can it be done when the bootloader is locked?
Can it be done without loosing data, screen lock pattern is enabled on the phone.
If you have any more ideas please let me know, I already tried everything I could think of and nothing worked.
Thank you a lot

Also I read something about EDL and EDL Pins, would this help me to download the data partition or clear the cache? Would clearing the cache help? Could the data partition be somehow decrypted outside of the phone?

Question Black screen of death / GrapheneOS Pixel 5a

Tl;Dr - my pixel 5a5g got the black screen of death a few months ago. Last night, I tried using the flash tool to try to flash it back to Android from GrapheneOS - so that Google would be willing to fix it maybe. Flashing seemed to fail. Unsure what to try or do next.
---------------
My Pixel has had the black screen of death for a few months now. I'm assuming it is from falling a few feet to the ground. It had a custom ROM - GrapheneOS - on it. Unless I can reflash to stock Android, it sounds like Google/ubreakifix won't look at it, and thus - no chance of repairing it for free or a smaller charge.
The other night, I tried attaching an OTG keyboard to the phone to log in to it. Since the display is black, I'm not sure it worked. I also tried several times to press where I thought the numbers for logging in would be - on my completely black screen. Somehow, I was eventually able to get my PC and Google's flash tool to recognize the phone. However, I might have messed up on some steps - because I think it might be bricked now.
I think I forgot to remove the grapheneOS key via their Web installer before trying to flash android. I used minimal abd tools to unlock the bootloader (and it still says it is unlocked)... When I tried flashing back to stock android using the android web tool, it went through the motions, but then said something like it needs to detect the phone again after flashing. And it wouldn't detect the phone again. Even if I unplugged then replugged the phone. The directions said I shouldn't/wouldn't need to press any keys on the phone for this step, but it just wasn't progressing further... So, I ended up holding the power button and volume down button - and it went into fastboot(?) again - or whatever that does.
I can repeat the steps of going thru the motions of flashing the device now, but now it gives an error saying something like it can't lock the device.
Being that the 5a screen is completely black, I have no idea what is going on - or what to do from here. I've reached out to some local repair places, but honestly, if I can't flash it myself to stock so that Google/ubreakifix would look at it, then it probably isn't worth sinking money into.... There's decent condition used ones around $120 or something out there... And ubreakifix would probably charge between $160 and $200 for screen replacement + labor - and I'm assuming that's not including a motherboard replacement - if necessary.
Ubreakifix said that they would be willing to look at it, but they can't actually do any repairs to it if it isn't running stock Android. They'd charge for the labor, and they'd temporarily use a screen to look at what it is doing/not doing... But wouldn't actually do the screen repair. I'm assuming the phone never flashed completely, but I'm hoping they can tell me if their diagnostic tools work on it - since I imagine it should work -- IF stock Android is actually installed again on it.
I've also looked into doing something like getting a displaylink adapter + display link app so that I can see the screen on the computer... But even after my multiple attempts of logging in to the phone, I can't send app downloads to the phone. Google Play store shows that the phone was "last seen" months ago... And even if I could push the app download, GrapheneOS still requires manual approval from the user to accept/finalize install of the app... Which would be pretty hard to do without seeing the screen. And obviously since I've tried flashing the phone several times last night, i have no idea what the phone is looking like. Probably app downloads are out of the question now.
Apparently you can't normally do display out of any sort with Pixel phones. The rumor I've seen on here and/or reddit is that Google got rid of it years ago, maybe so that they can sell more Chromecasts...
Does anyone have any further suggestions? I could try using scrcpy or whatever it's called, but I probably should have tried to use that before attempting to flash the phone... It's sure hard to give up on something that I spent good money on. I'd like to think there's something I haven't tried yet that I can do to save it...

You could probably try these steps:
1. Open up Device Manager on PC
2. Connect your phone
3. Hold Power + Volume Down
If you have new device in Device Manager, you can do everything with your device like flashing or try "to remove the grapheneOS key".
Edit: I'm dumb and didn't notice that part where you tried this. You should just boot into fastboot and remove that custom AVB key with fastboot erase avb_custom_key, and then reflash the phone on flash.android.com. Hope that helps!