Hi all,
I wanted to unroot and factory reset the phone. I forgot to flick that "enable oem unlocking" button, I tried "flash-all" directly on bootloader and it didn't work and after reboot it got stuck on Google screen. I waited for a while but nothing happened. I wiped system, vendor, cache... Nothing.
I have this message for every parts of the factory image:
Code:
FAILED (remote: device is locked. Cannot flash images)
As i said, the same error appear for boot.img, recovery.img and system.img.
Now, I can still use my "old" TWRP and push files through adb, i tried to flash a ROM (to check that "enable oem unlocking slider") trough ADB sideload, but the flash fails because recovery can't mount "boot", "system" and "vendor".
Any ideas?
If can help anytime I run the recovery, i got a "enter password" option to decrypt data.
Hitting cancel, TWRP ask me if i want to keep system read only or not, what do i have to do?
I tried to perform a full wipe, but i got this error in the terminal:
Code:
E:Failed to decrypt data.
E:Unable to decrypt with default password.
E:You may need to perform a Format Data.
Updating partition details...
E:Unable to mount '/vendor'
...done
E:Unable to mount storage.
Full SELinux is present.
E:Unable to mount setting storage during GUI startup.
E:Failed to wipe dalvik
Updating partition details...
E:Unable to mount '/vendor'
...done
E:Unable to mount storage.
Did i damaged something?
There's basically nothing you can do. You can't flash anything with a locked bootloader, and you can't unlock your bootloader because you can't boot into the OS. There's one thing you can try, try using adb sideload in TWRP to flash a ROM, any ROM, just to get it booting again. That's your only option at this point. If you don't know to use adb sideload just search on Google.
Heisenberg said:
There's basically nothing you can do. You can't flash anything with a locked bootloader, and you can't unlock your bootloader because you can't boot into the OS. There's one thing you can try, try using adb sideload in TWRP to flash a ROM, any ROM, just to get it booting again. That's your only option at this point. If you don't know to use adb sideload just search on Google.
Click to expand...
Click to collapse
Thanks for your kind answer mate, but i have a little problem: when i try to sideload something, i get stuck at 45 %, then the sideload fails and i can hear a "disconnected" sound from Windows 10...
Keep trying different ROM files and hope for the best. I really hope it works out for you
Monster_Joe said:
Thanks for your kind answer mate, but i have a little problem: when i try to sideload something, i get stuck at 45 %, then the sideload fails and i can hear a "disconnected" sound from Windows 10...
Click to expand...
Click to collapse
Like the other guy said, you gotta keep trying, this is the only thing that's going to save your phone.
If your device is based on MTK chipset you can use SP flash tool
Tapan98 said:
If your device is based on MTK chipset you can use SP flash tool
Click to expand...
Click to collapse
Hi, thanks for your answer, can you be more specific?
How can I check if my phone has this chipset?
Heisenberg said:
Like the other guy said, you gotta keep trying, this is the only thing that's going to save your phone.
Click to expand...
Click to collapse
So basically i have two options:
- adb push
- adb sideload
It's correct?
Monster_Joe said:
How can I check if my phone has this chipset?
Click to expand...
Click to collapse
It doesn't
Tapan98 said:
If your device is based on MTK chipset you can use SP flash tool
Click to expand...
Click to collapse
Why would you even post this? Probably best not to give advice if you know nothing about the device.
Monster_Joe said:
Hi, thanks for your answer, can you be more specific?
How can I check if my phone has this chipset?
Click to expand...
Click to collapse
It doesn't, you can ignore that post.
Monster_Joe said:
So basically i have two options:
- adb push
- adb sideload
It's correct?
Click to expand...
Click to collapse
From I can tell, you can't access the internal storage while in TWRP, which would render adb push useless. I believe all you can do is adb sideload, if that doesn't work you'd need to get it repaired.
Heisenberg said:
From I can tell, you can't access the internal storage while in TWRP, which would render adb push useless. I believe all you can do is adb sideload, if that doesn't work you'd need to get it repaired.
Click to expand...
Click to collapse
Hi Heisenberg, thanks for your help, is really appreciated.
As far as i know, i can mount /sdcard partition and adb push files there... Or i'm wrong?
By the way I will try when back at home!
Monster_Joe said:
Hi Heisenberg, thanks for your help, is really appreciated.
As far as i know, i can mount /sdcard partition and adb push files there... Or i'm wrong?
By the way I will try when back at home!
Click to expand...
Click to collapse
Thinking about it more, of TWRP can't mount system then it won't be able to flash a ROM. It's worth a try though.
Heisenberg said:
Why would you even post this? Probably best not to give advice if you know nothing about the device.
Click to expand...
Click to collapse
Hey, sorry for that, i'm newbie to this forum (probably first post on this forum), I didn't saw which device it was. And don't be so mean
Tapan98 said:
Hey, sorry for that, i'm newbie to this forum (probably first post on this forum), I didn't saw which device it was. And don't be so mean
Click to expand...
Click to collapse
well... while you're trying to help, you can make matters worse for some if you arent giving device specific instructions.
tho in the this case, odds are more damage can't be done... fortunately/unfortunately.
Don't take it personally. We all make mistakes. You meant well!
Tapan98 said:
Hey, sorry for that, i'm newbie to this forum (probably first post on this forum), I didn't saw which device it was. And don't be so mean
Click to expand...
Click to collapse
With a little search on Google i found this thread ---->http://forum.xda-developers.com/nexus-6/help/unlock-bootloader-os-installed-t3070473
This guy had the (sort of) same issue with the Nexus 6.
Maybe it's totally useless to your situation, but i guess it never hurts to see how he fixed it.
I'm not entirely sure i understand how he did it.
You'll need a backup though.
Tapan98 said:
Hey, sorry for that, i'm newbie to this forum (probably first post on this forum), I didn't saw which device it was. And don't be so mean
Click to expand...
Click to collapse
My intention wasn't to be mean, but what I said is true. If you give incorrect advice for a device that you have no experience with, the user could end up with a bricked phone. I doubt you want to be responsible for that. Your intentions were good, but stick to what you know, accuracy is of utmost importance here on XDA.
Very interested in seeing the outcome to this situation. Best of luck @Monster_Joe!!!
Related
Hi all,
As mentioned in the title, an update from LG came for my 802 and suddenly, it booted and entered TWRP.
Now, it always goes back to TWRP. Anyone knows how I can solve this or boot normally again?
Thx,
Xiribi
TWRP, that's the problem.
Custom recovery and OTA will be end like this.
Easy fix here
Xenovias said:
TWRP, that's the problem.
Custom recovery and OTA will be end like this.
Easy fix here
Click to expand...
Click to collapse
Will this reset the phone?
Don't want to lose all the data
Xenovias said:
TWRP, that's the problem.
Custom recovery and OTA will be end like this.
Easy fix here
Click to expand...
Click to collapse
but when i do this fix is the ota update then installed?
Edit: the update is not installed but how do i get that update installed whit cwm or other recovery?
Xenovias said:
TWRP, that's the problem.
Custom recovery and OTA will be end like this.
Easy fix here
Click to expand...
Click to collapse
Unfortunatelly this did not solve the problem.
Keeps in a bootloop now and nothing happen.
Anyone remenbers where I can find the ADB thread to restore the phone?
When I try now I get an error that the ADB shell is is error: closed.
I'm looking for a way to put an image back on the phone.
THX guys.
Xiribi said:
Unfortunatelly this did not solve the problem.
Keeps in a bootloop now and nothing happen.
Anyone remenbers where I can find the ADB thread to restore the phone?
When I try now I get an error that the ADB shell is is error: closed.
I'm looking for a way to put an image back on the phone.
THX guys.
Click to expand...
Click to collapse
Use the terminal command if you can't use ADB... might work?
That's what I did, because AT&T stops giving you the option to not update after a couple times, and then I got stuck like you.
http://forum.xda-developers.com/showthread.php?t=2582142
please learn to search and read before doing stuff on your precious phone
FiendFyre said:
Use the terminal command if you can't use ADB... might work?
That's what I did, because AT&T stops giving you the option to not update after a couple times, and then I got stuck like you.
Click to expand...
Click to collapse
i did use the terminal and got into the boot loop.
Cannot perform any operation trough command because it gives me an error saying that the adb shell is error closed.
I'm now trying something else with some LG tools I found here. Hope it works, if it does, I'll repost the link here.
Xiribi said:
i did use the terminal and got into the boot loop.
Cannot perform any operation trough command because it gives me an error saying that the adb shell is error closed.
I'm now trying something else with some LG tools I found here. Hope it works, if it does, I'll repost the link here.
Click to expand...
Click to collapse
I'm not sure what happened for you, because the terminal command worked for me... maybe you mistyped it, or maybe you had a slightly different problem or something. Not sure.
Guys,
I finnaly managed to have my device working.
Trough ADB shell and then trough ADB I was able to copy a downloaded ROM (FLEX rom) to the device and installed it.
After a couple of hours, all is OK.
THANK YOU ALL FOR THE HELP AND INFO!!! (PS: sorry for the caps)
Hello guys !
I got a Nexus 10 looping up at start after displaying "Google".
Looking on the web, I know how to reset the firmware, but I don't want my datas to be wiped, I need to backup my files first.
Does anybody has a solution in order to get datas back?
Thanks in advance for you help
akaii78 said:
Hello guys !
I got a Nexus 10 looping up at start after displaying "Google".
Looking on the web, I know how to reset the firmware, but I don't want my datas to be wiped, I need to backup my files first.
Does anybody has a solution in order to get datas back?
Thanks in advance for you help
Click to expand...
Click to collapse
More information would be nice. Did it just start doing that randomly or were you flashing something? Are you using a ROM or stock? If a ROM, which one?
jsgraphicart said:
More information would be nice. Did it just start doing that randomly or were you flashing something? Are you using a ROM or stock? If a ROM, which one?
Click to expand...
Click to collapse
Hello
What do you mean by "using a ROM or stock?"
I just rebooted the device and then could never boot again normally.
thanks
akaii78 said:
Hello
What do you mean by "using a ROM or stock?"
I just rebooted the device and then could never boot again normally.
thanks
Click to expand...
Click to collapse
Then I'm going to assume you haven't installed a ROM on it and are running the Stock OS that came with the device. What method did you use for rooting?
jsgraphicart said:
Then I'm going to assume you haven't installed a ROM on it and are running the Stock OS that came with the device. What method did you use for rooting?
Click to expand...
Click to collapse
"rooting" ? you meant rebooting? if yes was the normal use with the OS rebooting button.
akaii78 said:
"rooting" ? you meant rebooting? if yes was the normal use with the OS rebooting button.
Click to expand...
Click to collapse
I misread your issue. I thought you said you rooted it and had issues. I have no idea why it would do that if you haven't even done anything to it. Devices just don't not boot unless you did something to mess it up or the device is broken. If anything try just booting into recovery and wipe cache. If that doesn't work try flashing the system.img found in the factory images using fastboot. Or flash all but userdata.img. There are tutorials around the web. But again, if you haven't rooted the device or done anything to the system files, I don't know why it's not booting. Hopefully the internals didn't go out on you.
jsgraphicart said:
I misread your issue. I thought you said you rooted it and had issues. I have no idea why it would do that if you haven't even done anything to it. Devices just don't not boot unless you did something to mess it up or the device is broken. If anything try just booting into recovery and wipe cache. If that doesn't work try flashing the system.img found in the factory images using fastboot. Or flash all but userdata.img. There are tutorials around the web. But again, if you haven't rooted the device or done anything to the system files, I don't know why it's not booting. Hopefully the internals didn't go out on you.
Click to expand...
Click to collapse
Yeah maybe my English is not good.
Actually I didn't recover the original firmware because I won't first to backup my datas, any idea on how to do this?
Thanks for your help !
akaii78 said:
Yeah maybe my English is not good.
Actually I didn't recover the original firmware because I won't first to backup my datas, any idea on how to do this?
Thanks for your help !
Click to expand...
Click to collapse
I have never personally used this method, so I can't tell you what to do with 100% confidence. But if you can boot into the bootloader and then use fastboot to install TWRP recovery, there may be a way to pull files from your device using commands on your computer. You may have to do some research on that. Sorry I can't be more helpful. It's hard to know what's going on with your device when you haven't done anything to cause it.
jsgraphicart said:
I have never personally used this method, so I can't tell you what to do with 100% confidence. But if you can boot into the bootloader and then use fastboot to install TWRP recovery, there may be a way to pull files from your device using commands on your computer. You may have to do some research on that. Sorry I can't be more helpful. It's hard to know what's going on with your device when you haven't done anything to cause it.
Click to expand...
Click to collapse
Do you have tutorial link on how to install TWRP recovery ?
Thanks it's going further and not going back so it's good !
akaii78 said:
Do you have tutorial link on how to install TWRP recovery ?
Thanks it's going further and not going back so it's good !
Click to expand...
Click to collapse
Here's a link to their website for a download and instructions. But you need to have the android SDK installed. Do you have that at least?
https://twrp.me/devices/samsungnexus10.html
Please don't rush into anything and start flashing stuff. It will just mess up things even more.
jsgraphicart said:
Here's a link to their website for a download and instructions. But you need to have the android SDK installed. Do you have that at least?
https://twrp.me/devices/samsungnexus10.html
Please don't rush into anything and start flashing stuff. It will just mess up things even more.
Click to expand...
Click to collapse
But doesn't he need to unlock the bootloader before he can install a custom recovery? And if he does that, his data is gone.
[email protected] said:
But doesn't he need to unlock the bootloader before he can install a custom recovery? And if he does that, his data is gone.
Click to expand...
Click to collapse
I forgot all about that part.
@akaii78, I guess forget what I said. I don't know how you can get your data from your tablet now.
Hi,
You can try going to stock recovery and check if you have adb access with it. Then if you have, you can just pull the files using adb pull command. If you manage to connect to adb I can provide further help.
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Xperia Z1
XxLordxX said:
Hi,
You can try going to stock recovery and check if you have adb access with it. Then if you have, you can just pull the files using adb pull command. If you manage to connect to adb I can provide further help.
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Xperia Z1
Click to expand...
Click to collapse
Hello
Ok I can try but what is adb?
Thanks
akaii78 said:
Hello
Ok I can try but what is adb?
Thanks
Click to expand...
Click to collapse
Hi,
Android Debugging Bridge (better known as ADB) is a way that the computer can communicate with the android device. I suggest you giving a read at the following pages to get a better understanding:
http://forum.xda-developers.com/wiki/Android_Debug_Bridge
http://developer.android.com/tools/help/adb.html
http://www.geek.com/mobile/what-is-adb-and-how-do-i-use-it-1461697/
All the best,
~Lord
Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
My problem is that it does not unlock OEM and I was not active debugging, the phone just let me enter Fastboot but at the time of choosing RECOVERY it restarts
emmafer44 said:
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
Click to expand...
Click to collapse
Dude try Nexus toolkit my Wugfresh (NRT Toolkit) you have to boot to bootloader and use the application to clean install
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Alot of users are facing this bootloop issue. So far no one has been able to figure out a pattern that will give us insight into what kind of devices might be affected by this issue. I have created this survey on GoogleForums so far there are very few responses. Please participate to help the community figure out the probable cause for this bootloop
https://docs.google.com/forms/d/1nGAVdnjbkOE1ohvZvqbntb_7afT4p2OzbFIJjJWiy9Q/edit?c=0&w=1
BTW what's your phone's manufacturing date? were you using Magisk or SuHide?
Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
v12xke said:
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Ive tried literally every fix, its dead jim.
Dadud said:
Ive tried literally every fix, its dead jim.
Click to expand...
Click to collapse
Have you tried FORMATTING boot, system, data & vendor and then reflash? Format, not erase/wipe. Move your TWRP backup off to PC and try that. If you are rusty in ADB/Fastboot, then use NRT to do same in advanced tools. If you have a working recovery and your bootloader is unlocked, I would not give up yet. Good luck!
Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
rchtk said:
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
Click to expand...
Click to collapse
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
You never know the level of the person you're talking about eh. Just tought you hadn't tried the dd.
So dd shutting down before completing wasn't expected but now if I read again your posts, you said doing a photo shuts down the phone and that's quite typical of power related problems. Sh*t.
Could be the battery not holding discharge. Can the device stay in twrp with screen off? Did you try to let it fully discharge and charge it with a slow charge?
There are a lot of information in /sys/ or dmesg but it won't solve your issue.
Still under warranty?
Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
Forget restoring your backup for now. You're not a noob, so transfer your TWRP backup to PC, then FORMAT each partition first, including userdata and then reflash using a Google Imagehere. Ensure you are using the latest version of ADB/Fastboot. You didn't mention you have already attempted to Fastboot flash the NMF26F image. What was your result then? The reason I'm asking is that the Google script erases the partitions- does not format, but running the script will tell you which partition failed during writing.
Huawei Customer Service!!
Had the exact same problem creep up on me this past weekend. I ended up calling Huawei and they are doing a free warranty repair on my phone even though I'm almost two months out of warranty.
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Tylog said:
Make sure you are on SDK 25...
Click to expand...
Click to collapse
Yes, the latest ADB / Fastboot is required. The rest of the SDK is not mandatory. You can get a minimalist ADB-Fastboot-Driver install from an XDA dev here.
Also, TWRP updated for Angler recently here. This update solved a persistent backup problem I had with the previous v3.0.2-2
bought it second hand, and the previous owner bought it at launch, so im just a month or so out of warranty. im trying to get the original receipt to attempt to RMA it. Huawei's IMEI lookup says its under warranty till april 4th next year.
Tylog said:
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Click to expand...
Click to collapse
Was your phone stuck in Bootloop of death as well? How did you fix it? What do think causes this issue and how can it be avoided?
Hi all, I really messed up my 6T today, after messing with the new update and root, I ran the flash_all.bat file (from https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516) to restore images but didn't realize it would clear all my data, I stopped the process after it ran for a few seconds in a panic but now my phone only has the fastboot screen and fastboot.exe from my cmd shell is unable to do anything (just errors out for most commands), is there a way for me to at least retrieve my photos from my phone? I've tried 3rd party software and they all require usb debugging which I can't activate due to my phone not having a boot image. Any help would be a miracle, thanks.
I would try fastbooting a TWRP image. From there you may get access to your internal storage. You can then copy it off to a PC. I say may because you could encounter encryption issues when trying to first boot into TWRP.
If you do hit encryption issues, you could modify the "flash all" batch file to remove the -w command so it doesnt format. However, I thought that it gave you an option to wipe or not?
If it did wipe first, your a gonner my friend. You are too late.
Hope this gives you some insight on where to go from here.
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
christmasdesparation said:
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
Click to expand...
Click to collapse
THe -w command does a very fast wipe. So if it was at the beginning of the scrip that more than likely like your files are gone.
Run the script again, this time delete the -w command. This will be your best chance of finding any data.
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Anyway, I took it to a shop today since I couldn't do much else my self, we'll see what happens. Lesson learned to always back up before messing with the boot.
Thanks
christmasdesparation said:
Lesson learned to always back up before messing with the boot.
Click to expand...
Click to collapse
And to properly read and understand what it is you're attempting to do.
sssarg said:
And to properly read and understand what it is you're attempting to do.
Click to expand...
Click to collapse
lol yes but in my defense I was already kind of freaking out since the fastboot wasn't working like it did previous times and messed up my normal boot
christmasdesparation said:
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Click to expand...
Click to collapse
Probably not possible as user data are stored in a virtual filesystem, mounted over an encrypted partition.
That's the reason why police forces regularly ask phone makers to put a backdoor, it's very hard even for a high tech forensic specialist to find data on a phone
So I actually re-ran the flash_all.bat script without the -w flag and I was able to fast boot flash into twrp (twrp-3.3.1-30-fajita-Q-mauronofrio to be specific). I can see what i believe are my files in the internal storage, but encrypted, however twrp never prompted me for a password, also going to the twrp terminal and entering twrp decrypt <passcode> did not work. Anybody know how to get twrp to decrypt? For some reason flash_all.bat did not restore my original boot or anything so I am only able to boot into recovery mode or twrp from the fastboot on my PC. doing fastboot getvar all shows that my slot-unbootable:a is "yes" if anyone knows how to make sense of this, it would be appreciated, even if I just need to copy my phones internal storage on to my computer and run 3rd party software to decrypt it that is fine
Thank you
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Could have used msm tool. You would have lost everything but at least phone would have worked
jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Yeah, he was trying hard to avoid that.
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Scott said:
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Click to expand...
Click to collapse
Thanks, I owe it to you, your original advice was spot on and all I failed to do was check the version number
jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Well to me "everything" on my phone was worth more to me than the phone itself