Related
There's a bunch of threads about the bootloader unlock tool existing, not any real place to aggregate reports of problems with it. So, if you've attempted to unlock your bootloader using the official ASUS tool and are having problems, please post your situation.
Reported instances:
myself
DeathStolas
ASUS_Khang
Rattraps123
m3t4lw01f
creison
both are experiencing bootloader unlock limbo. The tool seems to have worked, but going into fastboot shows two progressive screens:
1) Unlock Successfully reboot in 5 seconds
2) FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Clearing the cache goes through the loop again. Mind you, this loop only happens when you're trying to get to the bootloader. If you go to recovery or normally boot, you won't have any issues.
However, any commands sent via fastboot fail, so the bootloader is still locked. Attached is an image of the second bootloader screen.
ASUS_Khang is already getting in touch with technical folks to investigate as well, but I figure it best to see if anyone else is having issues with the official tool.
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
I have to laugh at the fact that someone on XDA unlocked the bootloader successfully with none of these problems and then ASUS give an "Official Unlock Tool" that screws up the phone of any who uses it... In the words of Alanis Morrisett - "Isn't it Ironic"...
m3t4lw01f said:
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
Click to expand...
Click to collapse
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Same problem here. I used the official unlocker tool and it did what it said it was going to do, but... I got the mythical "Bootloader 5 sec reboot".
asus is working on a fix.
playingmax said:
asus is working on a fix.
Click to expand...
Click to collapse
I'm sure that they are, but it would be interesting to see a source for that claim.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
m3t4lw01f said:
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
Click to expand...
Click to collapse
Sounds good. Can't wait till this is all sorted out and I can continue on with installing Cyanogenmod for my SO. She is really excited since it's her first Android phone.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
here you go
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
look at Khang Thai (ASUS REP) reply. they are working on a fix.
Kona67 said:
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Click to expand...
Click to collapse
Same issue ... I tried without a pin .. now added a pin and it asked me for it when trying to run the app again ... but that didn't help !
Help Ausus!!!
Mine says unlock failed rebooting in 5,4,3,2,1.
any way to relock bootloader as zenfone 6,5,and 4 have
When the 5 second bootloader issue is fixed you should hear about it here first, we have an Asus employee helping us: http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
https://fsfe.org/news/2012/news-20121106-01.en.html
Enviado do meu iPhone usando o Tapatalk
Looks like a user has solved the 5 second reboot issue. Check out the rather convoluted method here: http://forum.xda-developers.com/showthread.php?p=63498472
Hi
Since Friday my Nexus 6P freezes on boot animation logo.
I never tried to root my phone, neither force an updated on it (First time I went in recovery/fastboot mode was this weekend).
Friday morning I received a notification for an OTA update, so I clicked on it to install it and from this point my phone never started up again.
I tried many solutions but none of them worked, so I deciced to ask here finally as my last resort..
What I've tried :
Fastboot flash fails "device is locked" (and fastboot flashing unlock fails aswell because "oem unlock is not allowed" in dev options)
Recovery wipe data/factory reset works but my phone won't boot either (waited for ~1h)
Adb sideload OTA.zip (MMB29P → MMB29Q) fails "Verifying current system... System partition has unexpected content"
Nexus Root Toolkit (Flash Stock + Unroot with options Soft-Bricked/Bootloop) doesn't work
I run out of options, does anyone have another solution ?
Thank you
sorry I don't have ansewer except call google play support 855 836 3987
benrospars said:
Hi
Since Friday my Nexus 6P freezes on boot animation logo.
I never tried to root my phone, neither force an updated on it (First time I went in recovery/fastboot mode was this weekend).
Friday morning I received a notification for an OTA update, so I clicked on it to install it and from this point my phone never started up again.
I tried many solutions but none of them worked, so I deciced to ask here finally as my last resort..
What I've tried :
Fastboot flash fails "device is locked" (and fastboot flashing unlock fails aswell because "oem unlock is not allowed" in dev options)
Recovery wipe data/factory reset works but my phone won't boot either (waited for ~1h)
Adb sideload OTA.zip (MMB29P → MMB29Q) fails "Verifying current system... System partition has unexpected content"
Nexus Root Toolkit (Flash Stock + Unroot with options Soft-Bricked/Bootloop) doesn't work
I run out of options, does anyone have another solution ?
Thank you
Click to expand...
Click to collapse
Get to stock recovery using this guide, once there wipe cache partition then wipe data/factory reset. If that doesn't work call Google or RMA like error629 said.
http://www.androidexplained.com/nexus-6p-recovery-mode/
Read this thread. If I didn't know better, Id say it was yours.
http://forum.xda-developers.com/nexus-6p/help/command-t3308390
if your bootloader is locked and you didnt enable ADB in developer settings, you're out of luck
Contact google.
Soulfly3 said:
Read this thread. If I didn't know better, Id say it was yours.
http://forum.xda-developers.com/nexus-6p/help/command-t3308390
if your bootloader is locked and you didnt enable ADB in developer settings, you're out of luck
Contact google.
Click to expand...
Click to collapse
Yes exact same problem. I'll try to contact Google or Huawei then..
So I contacted Huawei Support (since I didn't buy it from the Google Store) and they told me to bring my phone to a PSM. PSM took my phone in charge and now I have to wait ~2 weeks (they send it back to Huawei). I'll update the thread when I get it back, this might be useful to somebody.
were on the same boat..
i remember a mate of mine uncheck the oem unlocking in the dev option.. then an OTA update came out and i updated it.. now the phone is stock only in bootloader. i wish i could enable the oem unlock.. but the problem is the phone wont boot normal.. pls help
im getting frustrated with my phone.. im thinking of overvolting the usb port with 12V so the dealership wont know about the reflashing
jeremmie said:
were on the same boat..
i remember a mate of mine uncheck the oem unlocking in the dev option.. then an OTA update came out and i updated it.. now the phone is stock only in bootloader. i wish i could enable the oem unlock.. but the problem is the phone wont boot normal.. pls help
im getting frustrated with my phone.. im thinking of overvolting the usb port with 12V so the dealership wont know about the reflashing
Click to expand...
Click to collapse
That would be fraud. Have you tried adb sideload?
No not yet.. i tried researching about sideload.. but i cant seem to understand it.. perhaps do you have any guide on how to do it? Would be really happy if someone post a guide.
---------- Post added at 08:29 AM ---------- Previous post was at 08:16 AM ----------
Also my nexus 6p wont enter recovery mode. It can only access the bootloader
So i cant make adb sideload to work because i cant access my recovery mode. It can only enter bootloader and barcodes and thats it.. pls help.. sigh..
jeremmie said:
No not yet.. i tried researching about sideload.. but i cant seem to understand it.. perhaps do you have any guide on how to do it? Would be really happy if someone post a guide.
---------- Post added at 08:29 AM ---------- Previous post was at 08:16 AM ----------
Also my nexus 6p wont enter recovery mode. It can only access the bootloader
So i cant make adb sideload to work because i cant access my recovery mode. It can only enter bootloader and barcodes and thats it.. pls help.. sigh..
Click to expand...
Click to collapse
If that's the case there's nothing anyone here can do or say to help you, your only option is sending it back for repair. Hopefully a lesson has been learned here.
Good morning
We should make group called nexus 6p bricked devices since we all got same problem .
I read in Google forum that March update released and some users got same problem after flashing it
So we have to make topic also called ( warning read before flash your ota ) at least to help new n6p users .
Ok so i got my phone fixed by my dealer.. So far so good. And they knew that i fcuked up my nexus so they've told me not to reflash the system again.
My nexus 6p is now bonestocked
Sent from my Nexus 6P using Tapatalk
jeremmie said:
Ok so i got my phone fixed by my dealer.. So far so good. And they knew that i fcuked up my nexus so they've told me not to reflash the system again.
My nexus 6p is now bonestocked
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I am happy to hear that hope mine fixed too , I think first thing you have to do is to unlock your bootloader and that's enough ATM .
jeremmie said:
Ok so i got my phone fixed by my dealer.. So far so good. And they knew that i fcuked up my nexus so they've told me not to reflash the system again.
My nexus 6p is now bonestocked
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
atef79 said:
I am happy to hear that hope mine fixed too , I think first thing you have to do is to unlock your bootloader and that's enough ATM .
Click to expand...
Click to collapse
I agree with this. Having an unlocked bootloader is insurance in case anything goes wrong in future.
hi, i have a problem with my N6P. it was unlocked, twrp flashed and running newest version of this ROM http://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600.
then, out of the blue, phone refused to work. when i'm trying to restart it, only option is boot to bootloader. i was trying to flash newest radio, bootloader, vendor and recovery - all failed with message "(remote: flash write failure)"
when i'm in bootloader mode, Andy Android is lying on his back, with no red exclamation point.
also there is written below Andy:
BL: K
Baseband: (empty)
Product/Variant: Angler-VN2
Serialn Number: (is present, but i think there is no need to write it)
CPU: MSM8994 0x20001
eMMC: 32GB Samsung
DRAM: 3072MB HYNIX LPDDR4
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-Mode-charge: ENABLED
Download Mode: DISABLED
Connect USB Data Cable
strange thing is, that there is written "Device is LOCKED", because when wrote command "fastboot flashing unlock", there was a message:
...
(bootloader) Device already unlocked!
FAILED (remote failure)
I was able to fastboot boot boot.img, but it hanged on "Google" screen.
device is not visible after writing "adb devices", but is visible after writing "fastboot devices".
any ideas?
Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?
i'm downloading GFI, but 3 more hours left to finish download (unless there is a mirror server to download them). i'll probably try to do it, but i would like to avoid it because my backup is 2 months old :/
Fe Mike said:
Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?
Click to expand...
Click to collapse
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.
Fe Mike said:
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.
Click to expand...
Click to collapse
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?
miguelm75 said:
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?
Click to expand...
Click to collapse
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google
Fe Mike said:
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google
Click to expand...
Click to collapse
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.
Did you try to format data partition then flash the google image?
Iceburn1 said:
Did you try to format data partition then flash the google image?
Click to expand...
Click to collapse
i just did and received (remote: failed to erase partition) error.
miguelm75 said:
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.
Click to expand...
Click to collapse
The op has an LG device but in second post there is a link (the one I'm posting now) for Qualcomm chipsets.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
Same thing just happened to me except I was just using my phone then it crashed and never came back tried for days to recover was able to re-lock bootloader but no other commands took. Had to RMA it back to Huawei took 3 weeks but it was covered by 12 month warranty so that's a plus
did you switch on find my phone in administer options before unlocking and flashing errors ?
rowihel2012 said:
did you switch on find my phone in administer options before unlocking and flashing errors ?
Click to expand...
Click to collapse
no, i didn't touch it.
Happened to me too while using it. I am still trying to save my data, but no luck for now.
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse
laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse
laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.
dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks
Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.
Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..