[Q] Am I screwed? Anyway to backup userdata via fastboot? - Nexus 7 (2013) Q&A

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)

Related

[Q] bootloop no recovery

Wife's Verizon Galaxy Nexus 4.2.2
Bone stock, completely un-tampered with, stuck in bootloop. If I try to access recovery I just get the Android dude with the red exclamation point sign, and eventually it reboots and back to the bootloop problem.
I need to save the data on the phone (pictures/videos). Flashing factory image erases all data, but could a person use Odin to flash the Verizon 4.2.2 OTA update? Is it possible or will Odin erase everything anyway?
That is stock recovery. Odin flash also wipes user data. Is the bootloader unlocked?
a maguro wrote this.
Oh, sorry for my ignorance, and the bootloader is locked.
You may try this awesome method: http://forum.xda-developers.com/showthread.php?t=2016628
The thread talks about GSM Nexus but may also work on your device (I think they have same CPU and bootloader). No warranties.
My Gnexi said:
You may try this awesome method: http://forum.xda-developers.com/showthread.php?t=2016628
The thread talks about GSM Nexus but may also work on your device (I think they have same CPU and bootloader). No warranties.
Click to expand...
Click to collapse
Exactly, do it at your own risk.
a manta wrote this.
Does seems like the most promising option at this point. Now if I can just find the OMAPFlash, the link is no longer good.
I think I have a copy on my laptop, will check later.
Edit: No need for my copy. The original post from gsmhosting.com by legija has a link that led me to http://d-h.st/XNv it's on dev-host and by efrant so it must be good
My Gnexi said:
I think I have a copy on my laptop, will check later.
Edit: No need for my copy. The original post from gsmhosting.com by legija has a link that led me to http://d-h.st/XNv it's on dev-host and by efrant so it must be good
Click to expand...
Click to collapse
Yes, its the same file.
a manta wrote this.
woohoo, it worked, I now have an unlocked bootloader. If I am correct I should now be able to flash a no-wipe recovery onto her device? I've been searching like crazy, but it seems like every other thread I find contradicts the previous so I'm still pretty lost.
hillbillymo said:
woohoo, it worked, I now have an unlocked bootloader. If I am correct I should now be able to flash a no-wipe recovery onto her device? I've been searching like crazy, but it seems like every other thread I find contradicts the previous so I'm still pretty lost.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1812959
You will be able to flash a custom recovery or even only boot a custom recovery through fastboot ('fastboot flash recovery recovery.img' for the first, 'fastboot boot recovery.img' for the latter). Read that first post on the thread I linked you to. It will teach you what is what and how to interact with the tools.
Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?
hillbillymo said:
Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?
Click to expand...
Click to collapse
USB debugging only has an effect when the OS is booted
Sent from my Galaxy Nexus
hillbillymo said:
Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?
Click to expand...
Click to collapse
While on CWM, ADB/USB debugging is active.
Use 'adb pull /sdcard/' to pull all contents under /sdcard/.
a manta wrote this.
Success...kind of. The "adb pull /sdcard/" command did not work, for some reason it kept freezing on the first file it found. I then navigated to the Camera folder and pulled all the .jpg files, which is what I was primarily after. ADB did not like pulling .mp4 files so I just called it good there.
After that I tried using fastboot to flash boot, system, recovery, and even radio images, but phone was still in bootloop. I then ran the flash all batch file that came with the factory image I downloaded, everything went fine, but still no boot. Also tried Odin to flash factory image, but every time I clicked on "Start" I would get a "program stopped responding" error message(no matter what version of Odin I used).
At this point I believe the phone has a major problem that cannot be repaired with software, time to lock the bootloader and send it in I suppose. If anybody has any other ideas let me know, but I'm not very hopeful.
Thank you to everyone that contributed to my data recovery, this really is an awesome place, guess I'll stick around.

[Q] System wiped, Bootloader not unlockable (freezes), TWRP working. Options?

Hey guys,
I've been messing around with my brand new N7 yesterday and somehow screwed up badly.
Right now, all I have is a working TWRP recovery and a locked bootloader.
When I try to unlock the bootloader, the device just freezes so flashing stock images is not an option.
Can I do something via TWRP to get my N7 working again?
I already opened a RMA with amazon.
Second question: If I am out of options, is there a way to remove TWRP?
Really need your help right now,
thanks in advance,
DrTek
which method did u try to unlock the bootloader?
MoonBlade said:
which method did u try to unlock the bootloader?
Click to expand...
Click to collapse
I tried with "fastboot oem unlock"
The moment I choose yes and push the power button for confirmation - the device freezes.
drtek said:
I tried with "fastboot oem unlock"
The moment I choose yes and push the power button for confirmation - the device freezes.
Click to expand...
Click to collapse
is it freezing for more than 2 mins ? it should not freeze like that unless it is already unlocked ??
It might already be unlocked. Do you have an unlocked symbol when you turn it on? If you do, run the Dead Nexus batch file from here. I was unable to do anything from TWRP or CWM. Just a bunch of errors when it tried to do anything with the drive. Flashing, copying, formatting, etc. This saved my Nexus!
http://forum.xda-developers.com/showthread.php?t=2381582
Do you have access to the internal SD? From a computer or anywhere? Because if you do you can just flash a ROM from twrp
sent from my nex7

Stuck on "Google" screen

I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.
This happened to me and Google sent a replacement phone. However the replacement phone is a refurbished phone that suffers from ghost touches Now trying to get a replacement for the replacement.
Ocelot584 said:
I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
can u boot into bootloader mode?
dominoeflux said:
can u boot into bootloader mode?
Click to expand...
Click to collapse
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?
Ocelot584 said:
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?
Click to expand...
Click to collapse
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems
dominoeflux said:
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems
Click to expand...
Click to collapse
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.
Ocelot584 said:
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.
Click to expand...
Click to collapse
Oh ok I thought it was sorry if I wasn't of any help
dominoeflux said:
Oh ok I thought it was sorry if I wasn't of any help
Click to expand...
Click to collapse
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?
Ocelot584 said:
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?
Click to expand...
Click to collapse
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?
dominoeflux said:
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?
Click to expand...
Click to collapse
nope...what's a bootloader anyway?
Ocelot584 said:
nope...what's a bootloader anyway?
Click to expand...
Click to collapse
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it
dominoeflux said:
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it
Click to expand...
Click to collapse
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?
Ocelot584 said:
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?
Click to expand...
Click to collapse
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative
dominoeflux said:
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative
Click to expand...
Click to collapse
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?
Ocelot584 said:
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?
Click to expand...
Click to collapse
Of course
Edit: have you tried resetting it in the factory recovery?
dominoeflux said:
Of course
Edit: have you tried resetting it in the factory recovery?
Click to expand...
Click to collapse
Nope...I was waiting to see if I could find a way to recover my data first
Ocelot584 said:
Nope...I was waiting to see if I could find a way to recover my data first
Click to expand...
Click to collapse
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.
dominoeflux said:
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.
Click to expand...
Click to collapse
Alright, but since all my data won't be recovered, is there a way to get access to files on my phone before I factory reset it?
Ocelot584 said:
Alright, but is there a way to get access to files on my phone before I factory reset it?
Click to expand...
Click to collapse
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way
dominoeflux said:
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way
Click to expand...
Click to collapse
oh... wow.
I'll just suck it up and reset it then. I'll let u know how it goes.

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.

XA2 stuck in bootloop

Hy guys, i need your help.
I bought a XA2 off of ebay with a bootloop issue. I thougth that a software recovery with PC companion would solve the issue, but sadly it didn`t. It failed to update the device.
The EMMA tool finds the device with the bootloader locked.
I tried multiple times to flash different stock roms with the flashtool, wiping all data from the phone. Nothing seems to work. When wiping all the data flashtool hangs, but when wiping all but leaving the user data, the flashtool completes but the phone is still in bootloop.
erase:userdata
erase status:fail
Write-TA:2:2311 --- hangs
Please advice further, thanks!
madhogg said:
Hy guys, i need your help.
I bought a XA2 off of ebay with a bootloop issue. I thougth that a software recovery with PC companion would solve the issue, but sadly it didn`t. It failed to update the device.
The EMMA tool finds the device with the bootloader locked.
I tried multiple times to flash different stock roms with the flashtool, wiping all data from the phone. Nothing seems to work. When wiping all the data flashtool hangs, but when wiping all but leaving the user data, the flashtool completes but the phone is still in bootloop.
erase:userdata
erase status:fail
Write-TA:2:2311 --- hangs
Please advice further, thanks!
Click to expand...
Click to collapse
Try 'newflasher'
hamirali said:
Try 'newflasher'
Click to expand...
Click to collapse
Tried, no luck.
It looks like the USERDATA has the issue. Everything hangs when it reaches that part of the flashing process.
madhogg said:
Tried, no luck.
It looks like the USERDATA has the issue. Everything hangs when it reaches that part of the flashing process.
Click to expand...
Click to collapse
Just a very amateur suggestion: load into twrp, change boot slot and try newflasher again.
hamirali said:
Just a very amateur suggestion: load into twrp, change boot slot and try newflasher again.
Click to expand...
Click to collapse
I don't know how to do that, do you have any guide i can follow? I am not shure if i can do that, since the bootloader is locked, and no way to unlock it, because i can't select the option in the system settings like usb debugging and allow oem unlock
madhogg said:
I don't know how to do that, do you have any guide i can follow? I am not shure if i can do that, since the bootloader is locked, and no way to unlock it, because i can't select the option in the system settings like usb debugging and allow oem unlock
Click to expand...
Click to collapse
Right I missed that bit in your first post about the bootloader being locked.
Well if I were in your position, I would assume - since it is in a bootloop - that both the other 2 things could have been already allowed by the previous owner.
It is not necessarily the obvious case, but there's no loss assuming that and try to unlock the bootloader vis usb.
you must know your IMEI though.
Hopefully, someone with real expertise can guide you here. Good luck!

Categories

Resources