Hello, I have a problem with an ALE-L21 the bootlader is marked as unlocked when I check with fastboot, but in reality I can not flasher anything: for the twrp I get a message: failed (image verification error). But I have to try to flash several other firmwares, the flash runs correctly but I remain blocked in balong version C52B311.aurte thing the serial number of the phone has to change instead of W3D7N15919016836 I have stuff like 0123456789ABCDEF! So this number does not allow me to retrieve a code to unlock the bootloader (I had noted the old but it no longer passes with fastboot I get "bad password" when I try to re-unlocked) voila I am completely blocked with phone and also imei disappeared I have already tried a lot of thing with dc-phoenix, I can flush android 5 or 6 but nothing changes in the phone. thanks for your advices sorry for my english.
oldgamer-72 said:
Hello, I have a problem with an ALE-L21 the bootlader is marked as unlocked when I check with fastboot, but in reality I can not flasher anything: for the twrp I get a message: failed (image verification error). But I have to try to flash several other firmwares, the flash runs correctly but I remain blocked in balong version C52B311.aurte thing the serial number of the phone has to change instead of W3D7N15919016836 I have stuff like 0123456789ABCDEF! So this number does not allow me to retrieve a code to unlock the bootloader (I had noted the old but it no longer passes with fastboot I get "bad password" when I try to re-unlocked) voila I am completely blocked with phone and also imei disappeared I have already tried a lot of thing with dc-phoenix, I can flush android 5 or 6 but nothing changes in the phone. thanks for your advices sorry for my english.
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/showpost.php?p=65226774&postcount=4
Ok I just tried to flash the rom b052 to unlock, but nothing is wrong, I am still stuck on this damned balong version V100R001C50B311 and the imeis are always marked as "unknown", stuffing the flash goes without message, Error I do not understand, I already work on many phones of all brands without problems but I am blocked !
oldgamer-72 said:
Ok I just tried to flash the rom b052 to unlock, but nothing is wrong, I am still stuck on this damned balong version V100R001C50B311 and the imeis are always marked as "unknown", stuffing the flash goes without message, Error I do not understand, I already work on many phones of all brands without problems but I am blocked !
Click to expand...
Click to collapse
downgrade to b052, and then update the smaller UPDATE.APP file.. that should get rid of balong bug problem..
Update process:
Put the smaller UPDATE.APP file inside a dload folder
copy that folder to the root of the internal storage
Dial *#*#2846579#*#* and choose SD Card Upgrade
After successful upgrade, you must back your Build Number
Ok, I finally came out of the balong bug and am in version B052, the model number is also returned (ALE-L21) but the 2 imei are always marked as "null". So I would like to avoid the error, it can come from what?
oldgamer-72 said:
Ok, I finally came out of the balong bug and am in version B052, the model number is also returned (ALE-L21) but the 2 imei are always marked as "null". So I would like to avoid the error, it can come from what?
Click to expand...
Click to collapse
Did what sokkoban wrote.
Make a wipe then update via OTA
I did the update via OTA in version B070 with full wipe still not recovered the numbers imei..the installation of recovery TWRP always fails with a message (remote: image verification error) .. how to recover its imei?
oldgamer-72 said:
I did the update via OTA in version B070 with full wipe still not recovered the numbers imei..the installation of recovery TWRP always fails with a message (remote: image verification error) .. how to recover its imei?
Click to expand...
Click to collapse
One more try:
Flash 052, wipe, OTA and then check imei.
I have just tried this and I followed the procedure to the letter: flash to b052, reboot and wipe, reboot, update of version b070 by OTA and still no imei ..
oldgamer-72 said:
I have just tried this and I followed the procedure to the letter: flash to b052, reboot and wipe, reboot, update of version b070 by OTA and still no imei ..
Click to expand...
Click to collapse
When you update via OTA you was with or without balong error?
Second round
Even with bootloader locked you have to root your device, can you do it while you're in b052?
Delete internal storage, And os, and then flash Your Firmware
No I no longer the balong bug since my donwgrade successfully in B052 so the updates are done on a "clean" version. Since i'm not re-trying to root the tel.but ok i will try this . I might have a non-permanent root because of the blocked bootloader?. I am saying that the bootloader is marked as unlocked in fastboot and rescue mode! ... ok i root
oldgamer-72 said:
No I no longer the balong bug since my donwgrade successfully in B052 so the updates are done on a "clean" version. Since i'm not re-trying to root the tel.but ok i will try this . I might have a non-permanent root because of the blocked bootloader?. I am saying that the bootloader is marked as unlocked in fastboot and rescue mode! ... ok i root
Click to expand...
Click to collapse
If you are root now, try this:
http://huaweip8lite.blogspot.pt/2016/03/bootloader-huawei-p8-lite-14-huawei.html?view=classic
I just re-try this method with a root access but it does not work with me, I get nothing, no unlock code ... I'm still in version b052
oldgamer-72 said:
I just re-try this method with a root access but it does not work with me, I get nothing, no unlock code ... I'm still in version b052
Click to expand...
Click to collapse
Follow the path /mnvm2:0/SC/Pers
How many files do you see with ImeiFile_xx.bin or hash?
Good ok it is always the same the I passed in b70 and always imei marked as: 0000000000 exists there a method to recover imei? In addition I root the phone with kingo root, I check with root checker it tells me ok this is root and a few moments later I reverify with root checker and it tells me that I no longer root rights I understand nothing more And does not know what to do !! Please help
oldgamer-72 said:
Good ok it is always the same the I passed in b70 and always imei marked as: 0000000000 exists there a method to recover imei? In addition I root the phone with kingo root, I check with root checker it tells me ok this is root and a few moments later I reverify with root checker and it tells me that I no longer root rights I understand nothing more And does not know what to do !! Please help
Click to expand...
Click to collapse
Hello did you solved it? I have a similar problem.
My P8 lite had a CUSTOM rom and was rooted (ALE-L21C432B574-Deodex)
It was going well , it worked for months, then all of a sudden it bootlooping every 90 seconds
So I tried to flash Nougat but it didn't solved then I think I deleted for mistake /mnvm2:0/ folder all alone.
In someway I managed to stop it bootlooping but after that my imei was gone.
I tried all kind of guides on the related forums and I tried flashing the following roms and checked the imei after
b041c imei1:null imei2:null (hcu-client shows imei1:correct imei2:0000000000000000)
b046 imei1:null imei2:null (hcu-client shows imei1:correct imei2:0000000000000000)
b052 imei1:null imei2:null (hcu-client shows imei1:correct imei2:0000000000000000)
b132 imei:0000000000000000 (hcu-client shows imei1:correct imei2:0000000000000000)
b170 imei:0000000000000000 (hcu-client shows imei1:correct imei2:0000000000000000)
b574 imei:0000000000000000 (hcu-client shows imei1:correct imei2:0000000000000000)
b598 imei:0000000000000000 (hcu-client shows imei1:correct imei2:0000000000000000)
b604 imei:0000000000000000 (hcu-client shows imei1:correct imei2:0000000000000000)
Please Help me! I am desperate because I love this phone!
Ciao!
Related
Changing thread to become updates on trying to 7.0 to work on L29
IGNORE:Has anyone tested the leaked Android N on an L29. It was confirmed that dload is not working. Has anyone tried fastboot
UPDATE:Tried flashing Boot Cust System and Recovery images from the new update.app. It flashed successfully with no errors. However, the device is currently stuck on "Device is booting"
Any Suggestions?
UPDATE 2:Went ahead and flashed the boot recovery and cust images from the update.app from L29C636B320 and i went through the device is booting screen. Currently on a black screen without a boot animation, waiting for something to happen. Tried a factory reset through the recovery and it failed. I'll let you know if it boots up
UPDATE 3: Noticed HiSuite being recognized, not sure how long its been there. Its been 15 minutes on black screen losing hope
UPDATE 4: Flashed back to B320 for now, @nakul has instructions to getting Nougat. Please refer to those. As of now I did not try it, I will when I have the time. Basically it's using dload after rebranding L29 as AL 10
UnchartedRd said:
Has anyone tested the leaked Android N on an L29. It was confirmed that dload is not working. Has anyone tried fastboot
Click to expand...
Click to collapse
Dload not working on my NXT-L29 bootloader Locked
Not tested by Bootloader
streetbike55 said:
Dload not working on my NXT-L29 bootloader Locked
Not tested by Bootloader
Click to expand...
Click to collapse
OK I'll try it with fastboot, as mine is unlocked. I guess I'll take the risk, however I believe that it should work.
UnchartedRd said:
OK I'll try it with fastboot, as mine is unlocked. I guess I'll take the risk, however I believe that it should work.
Click to expand...
Click to collapse
Ok, but if I understand it will pass the phone in AL-10. Because this leak is for AL-10
streetbike55 said:
Ok, but if I understand it will pass the phone in AL-10. Because this leak is for AL-10
Click to expand...
Click to collapse
Yeah, but the hardware is identical to the AL10.
UnchartedRd said:
Yeah, but the hardware is identical to the AL10.
Click to expand...
Click to collapse
Be carreful with related "Google play services" bug. Like contact synchronisation for example .
streetbike55 said:
Be carreful with related "Google play services" bug. Like contact synchronisation for example .
Click to expand...
Click to collapse
OK I'll keep that in mind. Thanks
UnchartedRd said:
OK I'll keep that in mind. Thanks
Click to expand...
Click to collapse
Good Luck !
we want the news ! :good:
streetbike55 said:
Good Luck !
we want the news ! :good:
Click to expand...
Click to collapse
I will let you know in a few hours or in the morning. It's late where I live
So how did it work out?
Skickat från min HUAWEI NXT-L29 via Tapatalk
Tried flashing Boot Cust System and Recovery images from the new update.app. It flashed successfully with no errors. However, the device is currently stuck on "Device is booting"
Any Suggestions?
Went ahead and flashed the boot recovery and cust images from the update.app from L29C636B320 and i went through the device is booting screen. Currently on a black screen without a boot animation, waiting for something to happen. Tried a factory reset through the recovery and it failed. I'll let you know if it boots up
UnchartedRd said:
Changing thread to become updates on trying to 7.0 to work on L29
IGNORE:Has anyone tested the leaked Android N on an L29. It was confirmed that dload is not working. Has anyone tried fastboot
UPDATE:Tried flashing Boot Cust System and Recovery images from the new update.app. It flashed successfully with no errors. However, the device is currently stuck on "Device is booting"
Any Suggestions?
UPDATE 2:Went ahead and flashed the boot recovery and cust images from the update.app from L29C636B320 and i went through the device is booting screen. Currently on a black screen without a boot animation, waiting for something to happen. Tried a factory reset through the recovery and it failed. I'll let you know if it boots up
Click to expand...
Click to collapse
UPDATE 3: Noticed HiSuite being recognized, not sure how long its been there. Its been 15 minutes on black screen losing hope
Bad news :crying:
Originally Posted by UnchartedRd
Changing thread to become updates on trying to 7.0 to work on L29
IGNORE:Has anyone tested the leaked Android N on an L29. It was confirmed that dload is not working. Has anyone tried fastboot
UPDATE:Tried flashing Boot Cust System and Recovery images from the new update.app. It flashed successfully with no errors. However, the device is currently stuck on "Device is booting"
Any Suggestions?
UPDATE 2:Went ahead and flashed the boot recovery and cust images from the update.app from L29C636B320 and i went through the device is booting screen. Currently on a black screen without a boot animation, waiting for something to happen. Tried a factory reset through the recovery and it failed. I'll let you know if it boots up
UPDATE 3: Noticed HiSuite being recognized, not sure how long its been there. Its been 15 minutes on black screen losing hope
Click to expand...
Click to collapse
do you try with dload via sd card L29C636320
UnchartedRd said:
UPDATE 3: Noticed HiSuite being recognized, not sure how long its been there. Its been 15 minutes on black screen losing hope
Click to expand...
Click to collapse
You doesn't flash Cache.img and userdata.img ?
streetbike55 said:
You doesn't flash Cache.img and userdata.img ?
Click to expand...
Click to collapse
I had the same issue on Saturday. Flash the recovery from the Android N zip file. Then downgraded to B172 using the dload method. Upgraded again to B320 and stopped there. Try it... Good Luck
This Tips only for L29C636xxx for upgrade to nouget 7 beta for L10 cn chinese only
uses Srk tool
1 root and unlock bootloader
2 use srktool Menu 7 utility /9:Changing oeminfo and custom.bin after that phone will reboot and reset factory
i have problem with phone show unlock in ADB but can not flash stock recovery via srk tool unlock once again
3 phone must open usb debug use srk tool flash stock recovery choose you have rom 4.0or 4.1
4 now phone on deban with L10 with usb debug make dload folder only sd card which copy file nouget update.app
5 at phone call *#*#2446578#*#* at 4: software upgrade phone will reboot to update with dload wait
6 until restart again ****f volum up with power go to menu reformat factory
end
now phone must on nouget 7
good thing this rom fast smooth and save bat can login huawei id install app
bad thing sim slot 1 lock only for cn chinese mobile only sim slot 2 only 2g internet
phone show lock ADB error can not flash anything
i can rool back by dload again with rom 4.1 AL 10 only
after unlock bootloader and root deban Changing oeminfo and custom.bin to L29C636320
laster dload with rom L29C636320
now phone with lock rom L29
someone wants to testing this rom nouget 7 ?
@nakul Are you sure turned on OEM unlock in developer options
nakul said:
do you try with dload via sd card L29C636320
Click to expand...
Click to collapse
Dload is not working with L29 but as @nakul said rebranding your phone seems to work. He also mentioned that International Sims are only receiving 2g internet
hey
i flashed emui 5 on my VNS-L21
i did a mistake though
i flashed VNS-L31 firmware on my VNS-L21
now the phone model is changed to generic-a15
now i cant flash any roms using dload to this device..
i flashed twrp using fastboot but i cant boot into twrp....the bootloader unlocked screen says 'phone is booting" forever when i try to get into twrp
what do i do
please help
the rom is working fine on my VNS-L21 except for the camera...i need it a lot
please help me
edit:1
i tried to revert back to mm
it still says firmware incompatible
now my bootloader got locked...in the boot i got a msg that data partition is damaged and i need to format it....so i formatted it
now my phone is only booting to erecovery and bootloader
i cant flash twrp or revolution recovery because the bootloader is locked
i cant unlock bootloader now because i cant boot up my phone
Guys help us about the camera. I am in the same exact situation. @BadWolfYe and your product_V3 doesnt fix the camera for me, VNS-L21.
And for the recovery - http://forum.xda-developers.com/hua...ecovery-twrp-3-0-2-android-nougat-03-t3511937 - use adb flash it.
dancress said:
You'll have to go the hard route. You'll find all the required files in the ROM section.
Download any Nougat.zip (329 worked for me, 336 did not). Unzip. You'll get the update.app.
Download the second file with all the missing apps. Do not unzip. Maybe rename to something shorter like data.zip.
Download Revolution Recovery for Nougat. Unzip. You get the recovery.img. RENAME to something like revolution.img.
Open update.app in Huawei Update Extracor. Extract recovery.img, boot.img and system.img to wherever your fastboot.exe is. It's practical to put it all in one directory so you don't have to type long paths.
Now, careful...
Go into Fastboot. If Vol- + Power doesn't work, let it boot into eRecovery, press Vol- and tap Reboot. There you are.
Open a command window in the dir with fastboot.exe and the .img files (right click, Open Command Window)
fastboot flash boot boot.img
.... OK
fastboot flash system system.img
.... sparse 1/5 or something, this takes a bit of time.
fastboot flash revolution.img
.... OK
Now DO NOT REBOOT into System. Hold Vol+ + Power while still in Fastboot. It'll boot into Revolution eventually. Tap Advanced, ADB Sideload. Swipe.
Back in your command window, type:
adb sideload second_file.zip
... working... this'll take a bit. There might be an error message like 'could not mount /data'. Doesn't matter at this point.
When done, type
fastboot flash recovery recovery.img (this is the stock recovery you extracted from update.app)
... OK
Reboot to recovery from Revolution.
Do factory reset. Note: If you don't do this last step, there will be a bootloop.
Reboot. The system should now boot up normally. At least it did for me... good luck.
Click to expand...
Click to collapse
But maybe you installes twrp for mm
Laurisss said:
Guys help us about the camera. I am in the same exact situation. @BadWolfYe and your product_V3 doesnt fix the camera for me, VNS-L21.
And for the recovery - http://forum.xda-developers.com/hua...ecovery-twrp-3-0-2-android-nougat-03-t3511937 - use adb flash it.
Click to expand...
Click to collapse
I did this too. Only way to fix it is to downgrade to MM (instructions are in the N install thread). I then unlocked the bootloader, booted to fastboot, flashed Meticulus recovery. Once you're here, the important thing is to flash the update.zip and appropriate .Zip file for your device. Took me a while to find it but Meticulus has a post in Spanish with all of them for each type of P9 lite - there's one for the VNS-L23 there. Flash the update.zip and then device zip (in that order) and reboot. It'll work.
This phone is harder to flash Roms than others I've had in the past... It's important to do things in the right order.
Here's the link I was referring to: http://www.htcmania.com/showthread.php?t=1265029
ALAN JO K said:
hey
i flashed emui 5 on my VNS-L21
i did a mistake though
i flashed VNS-L31 firmware on my VNS-L21
now the phone model is changed to generic-a15
now i cant flash any roms using dload to this device..
i flashed twrp using fastboot but i cant boot into twrp....the bootloader unlocked screen says 'phone is booting" forever when i try to get into twrp
what do i do
please help
the rom is working fine on my VNS-L21 except for the camera...i need it a lot
please help me
Click to expand...
Click to collapse
Like me today.. I´ve installed Emui 5 on my VNS-L21, but after installation bootloader seems to be locked and TWRP won´t load.. What can I do now? I´ve tried flash some recovery, or MM but with locked bootloader it´s hard Is here somebody who know how to repair it ??
DiXiDeR said:
Like me today.. I´ve installed Emui 5 on my VNS-L21, but after installation bootloader seems to be locked and TWRP won´t load.. What can I do now? I´ve tried flash some recovery, or MM but with locked bootloader it´s hard Is here somebody who know how to repair it ??
Click to expand...
Click to collapse
First thing when you want to do something (TWRP, root, custom ROM etc.) with your phone is: UNLOCK BOOTLOADER!
Without unlocked bootloader is not hard to do, you not even try, because it is impossible...
gtdaniel said:
First thing when you want to do something (TWRP, root, custom ROM etc.) with your phone is: UNLOCK BOOTLOADER!
Without unlocked bootloader is not hard to do, you not even try, because it is impossible...
Click to expand...
Click to collapse
You didn't understand me.. I've unlocked it. Installed TWRP, EMUI 5 and after reboot unlocked bootloader gone.. How is this possible ?
DiXiDeR said:
You didn't understand me.. I've unlocked it. Installed TWRP, EMUI 5 and after reboot unlocked bootloader gone.. How is this possible ?
Click to expand...
Click to collapse
Simply! At any install of stock firmware you loose: unlocked bootloader, twrp and root.
gtdaniel said:
Simply! At any install of stock firmware you loose: unlocked bootloader, twrp and root.
Click to expand...
Click to collapse
Oh okey. So.. Maybe this will be retarded question, but how can I unlock bootloader now, when my phone model is generic_a15? When I'm trying to put it on Huawei website it is wrong..
DiXiDeR said:
Oh okey. So.. Maybe this will be retarded question, but how can I unlock bootloader now, when my phone model is generic_a15? When I'm trying to put it on Huawei website it is wrong..
Click to expand...
Click to collapse
With same procedure that you unlocked before.
You must have the unlock code.
gtdaniel said:
With same procedure that you unlocked before.
You must have the unlock code.
Click to expand...
Click to collapse
Okey, second retarded question.. I didn't save my first code.. is here some way to reach it again ? Or can I somehow use generic_a15 phone model?
If you do not have the initial unlock code you have a big problem...
gtdaniel said:
If you do not have the initial unlock code you are a big problem...
Click to expand...
Click to collapse
Oh god, I'm so retarded, but thank you for your patience
Now, when you dial code for Device ID you will get a differend ID and when you make procedure for another unlock code on Huawei site you get ERROR...
gtdaniel said:
Now, when you dial code for Device ID you will get a differend ID and when you make procedure for another unlock code on Huawei site you get ERROR...
Click to expand...
Click to collapse
Yes..
diorenzo said:
But maybe you installes twrp for mm
Click to expand...
Click to collapse
i tried to revert back to mm
it still says firmware incompatible
now my bootloader got locked...in the boot i got a msg that data partition is damaged and i need to format it....so i formatted it
now my phone is only booting to erecovery and bootloader
i cant flash twrp or revolution recovery because the bootloader is locked
i cant unlock bootloader now because i cant boot up my phone
ALAN JO K said:
i tried to revert back to mm
it still says firmware incompatible
now my bootloader got locked...in the boot i got a msg that data partition is damaged and i need to format it....so i formatted it
now my phone is only booting to erecovery and bootloader
i cant flash twrp or revolution recovery because the bootloader is locked
i cant unlock bootloader now because i cant boot up my phone
Click to expand...
Click to collapse
For unlock bootloader you only need you phone to boot into bootloader...
You say "now my phone is only booting to erecovery and bootloader"
So?
gtdaniel said:
For unlock bootloader you only need you phone to boot into bootloader...
You say "now my phone is only booting to erecovery and bootloader"
So?
Click to expand...
Click to collapse
how do i get the ids required for unlocking bootloader if i cant look it up in settings
ALAN JO K said:
how do i get the ids required for unlocking bootloader if i cant look it up in settings
Click to expand...
Click to collapse
You have to saved anywhere first time you have'it!
That is the first rule!
Once you debranded your phone that Device ID is change,
so even your phone boot ok and you obtain a Device ID is not the same
with the one saved in the Huawei databases...
So, procedure to obtain the bootloader unlock code is ended in error...
My wife got a P9 Lite L31. I wanted to upgrade to Nougat. I finally succeeded, but after that I messed things up. I tried to do a clean intall with a update that wasn't ment for this.
In the beginning I could still enter the Nougat recovery, but I wasn't able to reinstall the update.zip. The device wouldn't boot, etc.
I tried to do many different things, but at this moment I cant enter TWRP anymore, I can enter fastboot and is says:
PHONE Unlocked
FRP Unlocked
But flashing an other TWRP recovery doesn's work because I get an error:
(Remote: Command not allowed).
Also relocking the bootloader doesn't work because is gives the same error as the one above.
I can't flash a OEM file through fastboot because it gives the same error as the one above.
I can't use HiSuite because it says it does not support the phone.
I don't know what else I can do right now.
I tried the 3 button method, but I can't get in the official recovery. The phone reboots to some kind of recovery where it wants to update the recovery through wifi, but it ends up with an error that it can't fails to get the package info. But there is no option to do a factory reset (I've put the MM update.app file in sdcard/dload folder).
Any ideas what else I can do to recover the phone?
Unlock the bootloader again.
Johnny TDN said:
Unlock the bootloader again.
Click to expand...
Click to collapse
Ok, did not expect to do that again, but I did it.
What's the next step? flash a nougat recovery? flash a oem recovery?
Fastboot now says:
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
Looks like fastboot isn't recognized by the computer anymore after the re-unlocking of the bootloader.
Windows device management also doesn't see the device. Not even as an unknown device.... Looks like the bootloader unlock completely bricked the device.
Well.
You must change your motherboard.
Johnny TDN said:
Well.
You must change your motherboard.
Click to expand...
Click to collapse
As per usual, your comment was of no help at all.
Take a look to this thread, it seems similar to your problem https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
What are you able to do with the phone?
igreja94 said:
As per usual, your comment was of no help at all.
Click to expand...
Click to collapse
-_-
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
Try to discharge your battery by leaving it on Fastboot mode.
Charget the batery and let it boot itself.
If it boots in the software, it will be very easy to fix. If no, then changing the motherboard is required
Potato997 said:
Take a look to this thread, it seems similar to your problem https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
What are you able to do with the phone?
Click to expand...
Click to collapse
To be honest, nothing.
It can do two things, you can let it boot and then it says it's booting, and that's it (after the warning that the bootloader is unlocked), or I can boot into fastboot but the phone is not detected by the computer. Device manager doesn't see the device at all not even as an unknown device. Nothing. So no way to flash anything using fastboot. KI also can't get into the fastboot&repair.
So yeah, I decided to send it in for repair.
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
NikkoVicedo said:
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
Click to expand...
Click to collapse
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
daner[email protected] said:
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
Click to expand...
Click to collapse
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
NikkoVicedo said:
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
Click to expand...
Click to collapse
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
[email protected] said:
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
Click to expand...
Click to collapse
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
Hi guys, i Got the SAAAAAME Problem, this is all about what i PMd to you danerrickcuba FRP lock and bootloader unlocked. can't go to recovery, but has access to fastboot and wasn't able to do anything to fastboot.
Already fixed my phone. Had to pay 15 euros for DC Phoenix (this software saved me from bringing my phone to huawei service center to have it fix. Thank god!) so I can fix my phone. Recovery, eRecovery, Dload method working, and relocked bootloader. Currently updating my phone through OTA. Tnx danerrickcuba for suggesting methods to fix my phone....
NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
i have the same problem
bootloader unlock and frp lock ,bootlooping,rec&e-rec destoryed
if you do not log out google /shut down "find my phone"/check oem-unlock in developer mode before downgrading or flashing ,you will get "frp lock" warning
bootlooping may come from wrong update.app. eg. i use dload method to flash rollback(5.0-B300) pkg in EMUI4.1 , my rec and e-rec are destoryed
however, i think fastboot command could do nothing to "bootloader unlock ,frp lock,rec and e-rec destoryed ". i do not know how DC-phoenix fix this and i pay a new motherboard for my mistake
try https://forum.xda-developers.com/showpost.php?p=71338813&postcount=29
This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M
Reserved for future use
can i follow this step for ZE520KL ?
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.
DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me
Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP
Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.
I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!