Develop Bugs

[Q] Am I screwed? Anyway to backup userdata via fastboot?

Hey all,
I just woke up and decided I was going to update to 5.1.1 since the notification kept bugging me to.
Well doing this while half asleep just screwed me. I forgot to open Boot Unlocker beforehand to unlock the bootloader and then proceeded to wipe recovery, boot, system, cache. I then tried to flash the 5.1.1's and got the message that I wasn't unlocked...:highfive::silly:
I was stock kernal and rooted and HAD twrp. I don't do anything special, I just like to root for the added abilities with some apps.
I've tried searching around but have been unable to find any solutions that work.
Any help is appreciated.

FoRealz said:
Hey all,
I just woke up and decided I was going to update to 5.1.1 since the notification kept bugging me to.
Well doing this while half asleep just screwed me. I forgot to open Boot Unlocker beforehand to unlock the bootloader and then proceeded to wipe recovery, boot, system, cache. I then tried to flash the 5.1.1's and got the message that I wasn't unlocked...:highfive::silly:
I was stock kernal and rooted and HAD twrp. I don't do anything special, I just like to root for the added abilities with some apps.
I've tried searching around but have been unable to find any solutions that work.
Any help is appreciated.
Click to expand...
Click to collapse
Did you relock your boot loader AFTER installing TWRP? If so, why would you do that?

SwoRNLeaDejZ said:
Did you relock your boot loader AFTER installing TWRP? If so, why would you do that?
Click to expand...
Click to collapse
I did. I debated about this for a while and researched a lot. The consensus I received was that some people relocked their phones and tablets if they were going to take them in public places to protect their data. Granted, the chance of the thief being savvy enough or caring is pretty slim.

FoRealz said:
I did. I debated about this for a while and researched a lot. The consensus I received was that some people relocked their phones and tablets if they were going to take them in public places to protect their data. Granted, the chance of the thief being savvy enough or caring is pretty slim.
Click to expand...
Click to collapse
Dude, honestly, with the addition of Android Device Manager sometime ago, relocking after you add recovery and root is trivial. If you're that worried about your device, you can encrypt lock and wipe remotely with the device manager.
So how did you go about flashing stock recovery with a locked boot loader, and do you still have TWRP?
Have you tried fastboot oem unlock?

SwoRNLeaDejZ said:
Dude, honestly, with the addition of Android Device Manager sometime ago, relocking after you add recovery and root is trivial. If you're that worried about your device, you can encrypt lock and wipe remotely with the device manager.
So how did you go about flashing stock recovery with a locked boot loader, and do you still have TWRP?
Have you tried fastboot oem unlock?
Click to expand...
Click to collapse
I can't flash anything at the moment. I was however able to format cache, recovery, boot, and system without being unlocked....so TWRP is gone now.
I haven't done fastboot oem unlock because I'm trying to preserve my userdata or back it up before I do that.

Dude you can pull your user data through ADB, but at the end of the day, screw the user data!! Get your tablet working again!

SwoRNLeaDejZ said:
Dude you can pull your user data through ADB, but at the end of the day, screw the user data!! Get your tablet working again!
Click to expand...
Click to collapse
How can i do it through ADB if i can't boot in to enable usb debugging?

FoRealz said:
How can i do it through ADB if i can't boot in to enable usb debugging?
Click to expand...
Click to collapse
Have you checked in stock recovery to check if you have ADB access?

SwoRNLeaDejZ said:
Have you checked in stock recovery to check if you have ADB access?
Click to expand...
Click to collapse
I can't get to recovery since I blew away the recovery partition. I can only get to fastboot/bootloader, but my bootloader is locked so I can't flash or boot from another recovery.
I think I'm out of luck. :crying:

FoRealz said:
I can't get to recovery since I blew away the recovery partition. I can only get to fastboot/bootloader, but my bootloader is locked so I can't flash or boot from another recovery.
I think I'm out of luck. :crying:
Click to expand...
Click to collapse
Dude, screw your data. Run fastboot oem unlock, and see if you can get it unlocked. That's literally your only option.
Moral of the story: Once you unlock bootloader LEAVE IT UNLOCKED. Your data is not at risk. (as is obvious based on this post, only bad things will end up happening)

How to install Android in Download Mode

Hi everyone,
I'm really sorry, I really tried everything and I tried to look for an answer but it's very hard for me to understand.
My phone "died". I am not sure it's because of a firmware update or not, but now it's on an infinite bootloop.
I can access to recovery mode and download mode, I downloaded the factory image for Android 7 on the official website but then, I don't know how to continue. I open the file flash-all.bat, but in the command prompt it doesn't recognize it. I suppose I missed a step. Should I open the file from another software?
Please help...
Thanks a lot

http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow this guide to the letter. You probably haven't installed your fastboot drivers correctly.
Note: if your phone was working correctly and started bootlooping on its own, you might be one of the unlucky users who has a defective motherboard. If it continues bootlooping after flashing stock image RMA the phone.

peltus said:
http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow this guide to the letter. You probably haven't installed your fastboot drivers correctly.
Note: if your phone was working correctly and started bootlooping on its own, you might be one of the unlucky users who has a defective motherboard. If it continues bootlooping after flashing stock image RMA the phone.
Click to expand...
Click to collapse
Hi, thanks a lot for your answer.
I'm stuck at oem unlock. The command prompt tells me
FAILED (remote: oem unlock is not allowed)
And on the internet, they say to unlock it in the dev options... but I can't access to my phone. Am I stuck?
Edit: I tried to skip this and I succeeded in these conclusions: abd works but then I get an error when I try to abd sideload: footer is wrong, aborted.
Then I tried fastboot but fastboot doesn't recognize my device. What to do?

Light_Ben said:
Hi, thanks a lot for your answer.
I'm stuck at oem unlock. The command prompt tells me
FAILED (remote: oem unlock is not allowed)
And on the internet, they say to unlock it in the dev options... but I can't access to my phone. Am I stuck?
Click to expand...
Click to collapse
Pretty much, yes probably. As i said if it started bootlooping running completely stock you probably can't do much about it by flashing anyway.
It's a common fault on the n5x that started popping up recently.

peltus said:
Pretty much, yes probably. As i said if it started bootlooping running completely stock you probably can't do much about it by flashing anyway.
It's a common fault on the n5x that started popping up recently.
Click to expand...
Click to collapse
I tried to skip this and I succeeded in these conclusions: abd works but then I get an error when I try to abd sideload: footer is wrong, aborted.
Then I tried fastboot but fastboot doesn't recognize my device. What to do?

OK I did a lot of research and I think I'm stuck.
fastboot recognized my device, I had to connect the phone on USB 2 instead of USB 3 port.
ADB shows an error on the phone, and fastboot says OEM is forbidden. And because OEM can be activated only from the phone... I'm doomed I suppose.
LG said my warranty expired. And anyway, I would have to pay for shipping and all.
:'(
Thanks for everything. If you find anything, answer here.

I think someone has already started a thread on unbricking bootloader locked phones. You might search for that.
But to me, it just sounds like the hardware has gone belly up just as many others. You might search for that problem also.

Thank you, I contacted the author of the topic!
Just in case for people, here is the topic: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 ([REQ] Need help. Unbrick phones with locked bootloader, oem unlock disabled)

Light_Ben said:
Hi everyone,
I'm really sorry, I really tried everything and I tried to look for an answer but it's very hard for me to understand.
My phone "died". I am not sure it's because of a firmware update or not, but now it's on an infinite bootloop.
I can access to recovery mode and download mode, I downloaded the factory image for Android 7 on the official website but then, I don't know how to continue. I open the file flash-all.bat, but in the command prompt it doesn't recognize it. I suppose I missed a step. Should I open the file from another software?
Please help...
Thanks a lot
Click to expand...
Click to collapse
just sent it to lg ...I iam paying 130 euros for new bootlader because mine stucked on bootloop but I can acces the recovery mode and I tried to flash stock but nothing if you never locked the bootloader try to sent it to lg and say to them you never unlock the bootloader ....sorry for my bad engilsh

I have a big problem and I did not find any solution at xda.
I flashed a custom rom and now after entering pin my phone bootloops. I am not able to enter recovery or download mode.
It feels like the phone is ignoring volume up and volume down buttons. I also tried to press the buttons directly on the motherboard. I cannot immagine that the buttons are broken. Has anybody an advice or me?

Verizon Pixel XL boot-loop after 7.1.2 update -> Looking to recover userdata

Hello XDA!
I have a Verizon Pixel XL that is stuck in a boot-loop after the 7.1.2 firmware update. The boot-loop did not begin immediately after the update which confuses me. I have never attempted to unlock the bootloader, root, or flash the firmware. I have thousands of pictures I am attempting to recover (I did not have coverage to backup the pictures in Google Photos) before I work on the boot-loop issue (or warranty replacement). I can access fastboot & recovery but these modes do not provide a backup option or backup command from ADB. When I boot to safe-mode the phone will stay on for about 10 seconds which has allowed me to disable a LOT of apps and enable USB debug.
As I see it, there are only two options available to me...
1) Find a way to 'halt' the system after start-up or find the mysterious app causing the issue and disable it.
2) Forensic (physical) data recovery for $500-$900
I have tried to research as much as possible (please correct me if I'm wrong): unlocking Verizon bootloader is not currently possible, installing custom recovery is either not possible or will wipe the device, and pushing a firmware update will also wipe the device.
If anyone has any suggestions or would like more information please let me know.
I will keep an eye on this thread to provide timely responses.
Thank you,
Matthew

w144mjb said:
Hello XDA!
I have a Verizon Pixel XL that is stuck in a boot-loop after the 7.1.2 firmware update. The boot-loop did not begin immediately after the update which confuses me. I have never attempted to unlock the bootloader, root, or flash the firmware. I have thousands of pictures I am attempting to recover (I did not have coverage to backup the pictures in Google Photos) before I work on the boot-loop issue (or warranty replacement). I can access fastboot & recovery but these modes do not provide a backup option or backup command from ADB. When I boot to safe-mode the phone will stay on for about 10 seconds which has allowed me to disable a LOT of apps and enable USB debug.
As I see it, there are only two options available to me...
1) Find a way to 'halt' the system after start-up or find the mysterious app causing the issue and disable it.
2) Forensic (physical) data recovery for $500-$900
I have tried to research as much as possible (please correct me if I'm wrong): unlocking Verizon bootloader is not currently possible, installing custom recovery is either not possible or will wipe the device, and pushing a firmware update will also wipe the device.
If anyone has any suggestions or would like more information please let me know.
I will keep an eye on this thread to provide timely responses.
Thank you,
Matthew
Click to expand...
Click to collapse
Flashing updates do not wipe your data. Download firmware of choice. Unzip it, place latest fastboot drivers in where update zip is. Rename it to something easy. fastboot update update.zip
Edit: enclosed fastboot drivers

Tulsadiver said:
Flashing updates do not wipe your data. Download firmware of choice. Unzip it, place latest fastboot drivers in where update zip is. Rename it to something easy. fastboot update update.zip
Edit: enclosed fastboot drivers
Click to expand...
Click to collapse
Thank you Tulsadiver!
Do you think the firmware update will also fix the boot loop?

w144mjb said:
Thank you Tulsadiver!
Do you think the firmware update will also fix the boot loop?
Click to expand...
Click to collapse
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.

Tulsadiver said:
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Click to expand...
Click to collapse
Being the noob that I am, I have a few more questions.
Do I have to unlock the bootloader to update the firmware?
I'm currently on NHG470 firmware, should I choose NHG47N or NHG47K or a different one?
I'd like to keep the phone on a factory image unless you suggest otherwise.
Thank you for your time and patience,
Matthew

w144mjb said:
Being the noob that I am, I have a few more questions.
Do I have to unlock the bootloader to update the firmware?
I'm currently on NHG470 firmware, should I choose NHG47N or NHG47K or a different one?
I'd like to keep the phone on a factory image unless you suggest otherwise.
Thank you for your time and patience,
Matthew
Click to expand...
Click to collapse
Yes, you must unlock the bootloader...you are on Verizon and I am unfamiliar with their procedure and even if the bootloader is unlockable. You had better talk to someone on a Verizon phone.

Tulsadiver said:
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Click to expand...
Click to collapse
Tulsadiver said:
Yes, you must unlock the bootloader...you are on Verizon and I am unfamiliar with their procedure and even if the bootloader is unlockable. You had better talk to someone on a Verizon phone.
Click to expand...
Click to collapse
On Android source I am reading that unlocking the bootloader requires a full wipe.
https://source.android.com/source/running#unlocking-the-bootloader
Please advise.
Thank you,
Matthew

w144mjb said:
On Android source I am reading that unlocking the bootloader requires a full wipe.
https://source.android.com/source/running#unlocking-the-bootloader
Please advise.
Thank you,
Matthew
Click to expand...
Click to collapse
That is true.
If you take it to a Verizon store and explain the situation they might be able to help.

Tulsadiver said:
That is true.
Click to expand...
Click to collapse
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew

w144mjb said:
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
Click to expand...
Click to collapse
I understand but my stepson has worked for every Carrier and they have access to software that might help. You already have a phone coming in so no skin off their nose.

w144mjb said:
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
Click to expand...
Click to collapse
I'm pretty sure you're SOL if you can't get it to boot to system. I don't think you can pull the data off the device without being in system. Even if you can it would be encrypted. So you wouldn't be able to do anything with it. Have you tried to boot in safe mode. If you get it to boot up in safe mode then you can pull the data off with no issues.

Tulsadiver said:
I understand but my stepson has worked for every Carrier and they have access to software that might help. You already have a phone coming in so no skin off their nose.
Click to expand...
Click to collapse
I'll give Verizon technical support a call tonight (or a few, as necessary) and update you after.
Thank you,
Matthew

toknitup420 said:
I'm pretty sure you're SOL if you can't get it to boot to system. I don't think you can pull the data off the device without being in system. Even if you can it would be encrypted. So you wouldn't be able to do anything with it. Have you tried to boot in safe mode. If you get it to boot up in safe mode then you can pull the data off with no issues.
Click to expand...
Click to collapse
It will stay on for about 10 seconds in Safe mode.

w144mjb said:
It will stay on for about 10 seconds in Safe mode.
Click to expand...
Click to collapse
Safe mode only runs stock apps so if you are still boot looping in safe mode it's unlikely an app is causing your problem. I'm not sure what you mean when you say you didn't have coverage to back up your photos in Google Photos --i thought all Pixel phones came with unlimited original quality photo backup as long as the photos were uploaded from your phone. At this point I don't think you can recover your photos unless you find a way to fix the boot loop. Your boot loop where it didn't happen immediately after the update and it allows you into safe mode briefly sounds kind of unusual and might be the result of a hardware problem on your phone rather than a software issue. Have you tried booting the phone up while it is plugged into a wall outlet to see if that makes any difference? Some people with boot loop issues on the Pixels have reported that allowing the battery to completely run down until the phone is dead and then plugging the phone into a wall outlet allowed them to boot up normally. If you try that maybe you will get lucky but your options are very limited at this point.

Question Bootloader Unlocked and You Device Is Corrupt Message

Is it normal to get the "Your device might be corrupt" message if you just unlock your bootloader? I have not flashed a customer kernel or Magisk, just unlocked the bootloader. I was rooted with the fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img, but I did a clean flash of the firmware, but still get this message. When I have verity disabled I don't get the message. Just want to make sure that the message is normal?

Normal if you are unlocked.

Yep, normal.

Ok just making sure. It sucks that you have to push the power button to start your phone with just the bootloader unlocked.

ilatimer1 said:
Ok just making sure. It sucks that you have to push the power button to start your phone with just the bootloader unlocked.
Click to expand...
Click to collapse
You don't. It'll still boot on its own, just give it a few seconds. Actually, I think pressing the power button once causes it to pause booting.

roirraW edor ehT said:
You don't. It'll still boot on its own, just give it a few seconds. Actually, I think pressing the power button once causes it to pause booting.
Click to expand...
Click to collapse
No there are two messages. The first one is that you device might be corrupt. It requires you to press the power button to continue. The second message is the bootloader unlocked message with will just boot if you ignore it.

ilatimer1 said:
No there are two messages. The first one is that you device might be corrupt. It requires you to press the power button to continue. The second message is the bootloader unlocked message with will just boot if you ignore it.
Click to expand...
Click to collapse
Hmmm. You say when you have verity disabled, you don't get the message. If this is accurate, I would consider either keep disabling it each time you flash the stock image, or if you have the energy, do a factory reset, but note of course that a factory reset will cause your phone to require complete setup as if it was new. You'd still get the one message about the bootloader being unlocked - that's the one that's normal.
At this time, it would probably be helpful to know your complete situation.
We know you've unlocked the bootloader, and that at some point you disabled Verity and Verification, and it sounds like you reflashed stock with Verity and Verification not disabled. Correct me if I'm wrong. Can you be more detailed about exactly what's been done since you unlocked the bootloader?

roirraW edor ehT said:
Hmmm. You say when you have verity disabled, you don't get the message. If this is accurate, I would consider either keep disabling it each time you flash the stock image, or if you have the energy, do a factory reset, but note of course that a factory reset will cause your phone to require complete setup as if it was new. You'd still get the one message about the bootloader being unlocked - that's the one that's normal.
At this time, it would probably be helpful to know your complete situation.
We know you've unlocked the bootloader, and that at some point you disabled Verity and Verification, and it sounds like you reflashed stock with Verity and Verification not disabled. Correct me if I'm wrong. Can you be more detailed about exactly what's been done since you unlocked the bootloader?
Click to expand...
Click to collapse
So there is a little more backstory. I was rooted with verity disabled and everything was working fine. When it came out that the new Magisk did not need verity disabled I decided to start from scratch and clean flash my phone.
I used the Google online flashing tool and around 3/4 of the way through the laptop froze and the flash failed. I ended up soft bricking my phone. I was able to get back to fastboot and did a clean flash using the flash-all.bat file. I noticed that I now had the corruption message.
So after that I decide to use the Google online flashing tool one more time and was successful, but I still had the corruption message. I finally decided to relock the bootloader to see if that would help. The corruption message did go away after locking the bootloader.
Now with everything back to clean stock I decide to try an unlock the bootloader again and when I reboot I get the corruption again. I am at kind of a loss now on what to try. Just as a FYI, I did try having the Google flashing tool force partition flashing to see if that would help, but it did not.

ilatimer1 said:
So after that I decide to use the Google online flashing tool one more time and was successful, but I still had the corruption message. I finally decided to relock the bootloader to see if that would help. The corruption message did go away after locking the bootloader.
Now with everything back to clean stock I decide to try an unlock the bootloader again and when I reboot I get the corruption again. I am at kind of a loss now on what to try. Just as a FYI, I did try having the Google flashing tool force partition flashing to see if that would help, but it did not.
Click to expand...
Click to collapse
Try a factory reset without any further flashing and see if that helps. Settings / System / Reset options / Erase all data (factory reset).

First, thank you all for offering advice. I ended up resolving my issue by downgrading to .37 and now the corruption message is gone with the bootloader unlocked .

ilatimer1 said:
First, thank you all for offering advice. I ended up resolving my issue by downgrading to .37 and now the corruption message is gone with the bootloader unlocked .
Click to expand...
Click to collapse
For my small part, you're welcome. Are you going to try to re-upgrade? It's a very unusual problem and there should be a solution - I just don't know what it is, but there are a lot more knowledgeable folks around here.

roirraW edor ehT said:
For my small part, you're welcome. Are you going to try to re-upgrade? It's a very unusual problem and there should be a solution - I just don't know what it is, but there are a lot more knowledgeable folks around here.
Click to expand...
Click to collapse
I just sideloaded the .17 update and everything is good to go!

Xiaomi Stuck in MI logo data backup needed

Hi all;
I writing to ask if I can get support from you in order to recover data from my phone. This is the situation I have a Xiaomi 10T 5G device that 4 days ago suddenly reboot and get stuck on MI logo screen. I have try entering in Recovery mode and test Reboot, Safe Mode and Repair Mode with no luck. I have try also to connect it to MIPC suit but the phone get not detected, only if I put it in fastboot mode I got a message from PC suite telling that I should change to Normal mode and reconnect.
I have installed ADB drivers and my usb drivers of my device.
The issue and before sending it back for reparation I want to backup the photos, all the other data is not relevant. The phone is with the fabric ROM. Is there any way that I can recover the data??
Thanks in advance for your support.

locked bootloader? unlocked?

GizmoTheGreen said:
locked bootloader? unlocked?
Click to expand...
Click to collapse
I assume is blocked as nothing g has been done to it since the purchase.

That happened to me twice. I was pushing it to recovery, fastboot, safemode for over and hour untill it turned on. It was after update last spring. Never happened again. I cant remember what happened (i know i realized it than, but i was on a business trip and pissed, just remember that prior to that it was a problem with unlocking it/power button/sensor, maybe not the same thing as you have, since it was looping),i think it was some bug

Hi thanks for the reply but I assume is not the same case as I have try to fastboot, safe mode and repair mode a lot of times and nothing happened.
Hope to find a way to get the data from the device.

zepo88 said:
Hi thanks for the reply but I assume is not the same case as I have try to fastboot, safe mode and repair mode a lot of times and nothing happened.
Hope to find a way to get the data from the device.
Click to expand...
Click to collapse
it may be stuck in some kind of recovery loop because it crashed and think it couldn't boot. like windows does.
try turn it completely off then start it.
I'm sorry if you did not unlock before hand, there is nothing you can do.
flashing rom requires unlocked bootloader. running TWRP requires unlocked bootloader.
flashing stock rom/ recovery rom from SD will I think wipe your data
unlock bootloader will wipe your data.
if you can't get it to boot you are SoL for the data friend :/

Thanks Sir. Seen that there is no option I have wipe all the data and the phone has come back again to normal operation. Now I will try to root to use some data recovery tool to see what I can get. Any recomendations??