Hi everyone.
I've been trying to look for a solution for five days now, and I can't find anything over here (or maybe my search skills are bad?)
Anyways, I have a Mate 8 NXT-L29C185B580 with unlocked bootloader, TWRP installed and rooted, however FRP is locked since "Enable OEM unlock" is disabled. It so happened that I accidentally restored default settings in developer options, causing the switch to be disabled again and since it is greyed out I can't turn it back on.
From what I gathered here on XDA, to access this option again I need to relock bootloader, but to do that I need the stock recovery which I can't flash due to the FRP lock.
What I'm trying to do is to go back to full stock. I have the update.zip of B580. Dload fails, so does flashing through TWRP.
I'd appreciate it greatly if anyone can help me out, losing my mind over this, although I'm probably going at it the wrong way
Okay so the problem is solved.
Downloaded B560 using link from firmware finder (since downloading from app itself was problematic), booted into TWRP and performed factory reset + advanced wipe dalvik cache, cache, data and system and flashed the two .zips. Afterwards booted into stock recovery and performed factory reset from there since phone wasn't booting. Finally I re-locked bootloader using fastboot and thus was able to access oem unlock option again.
Posting this here incase anyone else gets stuck in a similar situation.
zxc2.0 said:
Okay so the problem is solved.
Downloaded B560 using link from firmware finder (since downloading from app itself was problematic), booted into TWRP and performed factory reset + advanced wipe dalvik cache, cache, data and system and flashed the two .zips. Afterwards booted into stock recovery and performed factory reset from there since phone wasn't booting. Finally I re-locked bootloader using fastboot and thus was able to access oem unlock option again.
Posting this here incase anyone else gets stuck in a similar situation.
Click to expand...
Click to collapse
im having the same problem but unfortunately i cant flash anything getting error 9 will OEM be enabled by just factory resetting and wiping?
Related
Ihave had my GT-I9020T for a few months but in the last week i had problems with it foreclosing all my apps after i turned it off and back on and now i cant get my phone to unlock bootloader or factory reset at all. I have never unlocked bootloader or rooted my phone before on this phone because i got it with 4.0.3 OTA updated so really no need to root yet. I get this on recovery 3a when i try to factory reset/wipe, what does it mean?
Have you tried reset to factory/erase sd from phone menus ?
The best thing is to :
-unlock bootloader
-fastboot flash recovery cwm.img
do everything from there...(format,reset , etc..etc...)
The stock recovery is crap
Refer to the general section for more details
i already tried
I already tried to unlock bootloader but it wont do it because my phone wont let it factory wipe. i have tried to erase sd in main menus and it successful but factory reseting wont work and that is where the problem is.
Bump. I have this problem now too. Ever since I updated facebook my phone started force closing everything and I cant reset or unlock my bootloader again to wipe. Someone please help
Now it's my turn. Pressed factory reset by accident in boot loader. Can get to TWRP but it says E: Unable to mount storage
e:Unable to mount /sdcard/TWRP/twps. when trying to read settings file. etc...
Advanced File manager in TWRP shows /sdcard/TWRP
Any ideas???? If I try to mount data in TWRP my Mac wants to initialize.
Thanks
TWRP shows internal storage 0 mb
I flashed the stock recovery, then ran it and somehow it booted right into CM11. Everything was lost, but it's working again.
Factory reset wipe everything! Including SD card.
null0seven said:
Factory reset wipe everything! Including SD card.
Click to expand...
Click to collapse
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
808phone said:
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
Click to expand...
Click to collapse
I had the same issue, pressed by mistake factory reset in bootloader some time ago. I was pressing vol down to reach recovery, there was a slight lag and I pressed it a second time the immediately I've pressed power...so cursor has jumped 2 rows then executed. I've solved it only by flashing stock recovery and resetting to factory settings again, then flashed TWRP.
Now why you still had CM11...well not 100% sure but in TWRP when you wipe to factory the system partition is not formatted. I've paid attention once to the messages during a wipe and it was formatting data, cache, dalvik and android secure but not system. A reason can be that while flashing any ROM, the install script formats system at the beginning so theres no need to do that with factory reset.
Now I can only think that the factory reset from bootloader does the same and system is not wiped. Theoretically it is correct...system is read only especially on a stock non rooted device and resetting it to factory practically means that any trace of personal settings/aps and so on should be erased. And those are not stored on the system partition. There is also no hidden place on the phone where a recovery image of the original android OS is kept so this is not like on the laptops where you reset to factory and Windows is reinstalled from the recovery partition. My guess is that the factory reset just wipes all partitions that contain personal data and settings and leave system intact. So after a wipe and reboot is like you first start it.
You still had CM11 cause the wipe didn't format system...If anyone has a better explanation I would be glad to hear it. So From my point of view nothing went wrong and has nothing to do with the Maximus recovery or it's compatibility with CM11. It would have happen the same if you have used any other stock recovery
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
null0seven said:
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
Click to expand...
Click to collapse
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Rapier said:
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Click to expand...
Click to collapse
I don't want to try it again but I wonder if moonshine's factory reset is incompatible with cm11?
Dont understand what do you mean by "incompatible". The factory reset from bootloader is not the same thing as the one from a custom recovery. You shouldn't do a factory reset from bootloader regardless of the ROM you're using
Moonshine is an S-Off method, I didn't used it myself so I don't know what factory reset option is in there
Sent from nowhere over the air...
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
808phone said:
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
Click to expand...
Click to collapse
The reset to factory from bootloader exists because on stock ROM there's no custom recovery that has that option....so it's in bootloader. For it to work properly though, you must have the stock recovery also. If you have a custom recovery like twrp/cwm and use the wipe from bootloader it'll mess your sd cause phone is not able to perform the wipe properly with that custom recovery. That's why, in order to get back to normal you should flash back stock recovery and perform the wipe from bootloader again.
Sent from nowhere over the air...
Thank you for the clarification. It makes sense. Too bad that reset is so close to the recovery command. It's pretty weird that I didn't have to run the wipe from the stock boot loader again. It ran and rebooted the phone into CM11. Anyway, I am glad I am back to running. Thanks.
Basically, my wife's phone was constantly rebooting. I had heard of power button issues so I tried to open the phone to fix that. After fiddling around with the button the problem persisted. I read somewhere that wiping the cache would help so I prepared to do that.
As I was waiting for the cache to wipe... the phone reboot again. It now does not boot (sits on the boot screen after the Google logo goes away) and says invalid argument when I try to wipe the cache.
According to this post, flashing the cache.img will fix the corrupt cache and allow me to wipe it.
Unfortunately my wife's phone has not been backed up, nor has the bootloader been unlocked. Is there ANY way to backup/retrieve files before unlocking the bootloader so I can fix the cache corruption issue? She has stock recovery, running lollipop.
Would really appreciate help in this matter, the pictures on her phone are from a year of travelling (not my best idea to leave them on her phone...but I digress).
If your phone keeps rebooting, and bootloader is LOCKED, its going to be hard to do anything to recover user data.
Having said that,
If you had ADB debug enabled before this disaster, you could try to ADB Sidleoad the Nexus 5 Lollipop OTA zip from stock recovery.
Then you data would remain intact.
Best of luck
Artorias90 said:
Basically, my wife's phone was constantly rebooting. I had heard of power button issues so I tried to open the phone to fix that. After fiddling around with the button the problem persisted. I read somewhere that wiping the cache would help so I prepared to do that.
As I was waiting for the cache to wipe... the phone reboot again. It now does not boot (sits on the boot screen after the Google logo goes away) and says invalid argument when I try to wipe the cache.
According to this post, flashing the cache.img will fix the corrupt cache and allow me to wipe it.
Unfortunately my wife's phone has not been backed up, nor has the bootloader been unlocked. Is there ANY way to backup/retrieve files before unlocking the bootloader so I can fix the cache corruption issue? She has stock recovery, running lollipop.
Would really appreciate help in this matter, the pictures on her phone are from a year of travelling (not my best idea to leave them on her phone...but I digress).
Click to expand...
Click to collapse
Contact me on hangouts/email: [email protected]
I can flash custom recovery without unlocking bootloader or wipe. If the /data partition didnt get corrupted we could recover the files.
Sent from my Nexus 5 using XDA Free mobile app
Has my brain gone broken? I thought you could fastboot stock img files without unlocking the bootloader?
Ben36 said:
Has my brain gone broken? I thought you could fastboot stock img files without unlocking the bootloader?
Click to expand...
Click to collapse
You can try that too.
What version of Android did you have on the phone?
In order to flash factory images, you’ll need to have the Android SDK HERE
Then you need to download the same version of Hammerhead Factory Image
you have been running on her phone HERE
Extract the correct Hammerhead Factory Image using 7zip or other extractor tool.
Then copy the cache.img from the extraction to the SDK/platform-tools folder.
From within your platform-tools folder, open a command prompt.
I'd recommend wiping the partition before flash.
-First type the following command
fastboot erase cache
-Then type the following command
fastboot flash cache cache.img
Plenty of tutorials in the sticky's if you need to learn more .
Best of luck
Okay, I'm not sure if this entirely the right place. Have updated to Viper 2.1.0. Rebooted my phone, as I do each morning. It came up with needing to to enter a decryption key, ie; my password. Did said & it failed saying that data is corrupt. TWRP can no longer read the data portion either. Therefore can't wipe it in TWRP.
Is there a way to format or wipe the data partition through either fastboot or adb?
Factory reset but your data will be gone.
Random Pinenut Joy said:
Okay, I'm not sure if this entirely the right place. Have updated to Viper 2.1.0. Rebooted my phone, as I do each morning. It came up with needing to to enter a decryption key, ie; my password. Did said & it failed saying that data is corrupt. TWRP can no longer read the data portion either. Therefore can't wipe it in TWRP.
Is there a way to format or wipe the data partition through either fastboot or adb?
Click to expand...
Click to collapse
Try this, Venom helped with it a while ago and it worked, you will just have to re activate smart lock in google setting.
TWRP-Advanced-File Browser.
Navigate to /data/system and delete the locksettings.db.
I got my phone back from HTC after repair my phone screen and they wiped my custom rom and recovery but still have unlocked bootloader and restore oreo 8.0.
I managed to re-install twrp and tried to install a customed rom and experienced the same "decryption unsuccessful". But there is no lockingsettiings.db in the folder.
I will later try this method and report.... been a frustrating day....
=https://forum.xda-developers.com/showpost.php?p=59685278&postcount=3
So I flashed the January factory image using android flash tool (back to public). After that I turned off OEM unlocking in the developer settings.
Should I also perform a factory reset before setting everything up; any benefits in doing so? I'm guessing no since the flashing process wiped everything, but because I'm new to this I just wanna be sure.
galan said:
So I flashed the January factory image using android flash tool (back to public). After that I turned off OEM unlocking in the developer settings.
Should I also perform a factory reset before setting everything up; any benefits in doing so? I'm guessing no since the flashing process wiped everything, but because I'm new to this I just wanna be sure.
Click to expand...
Click to collapse
No need for that.