Database Info

Frp locked

Ok, here is the deal, i was being impatient, i flashed nougat yesterday on my phone, after flashing it there was no keyboard to enter my email to login, so i stupidly but unknowingly so changed my gmail password to an easier one cause the only input method i had was voice commands, anyways, i got helped out by another xda member, and i got FRP locked for changing my password, then i attempted to rollback to MM, now my bootloader is relocked and it says FRP LOCKED, the thing is i did a nandroid full backup with twrp of everything on my phone before starting all this and every step along the way when something went wrong i went to twrp to recover but the restore did not appear despite having it on my sd card so idk if it have to be on internal memory or there is something wrong with twrp, currently my phone is bricked and i need help recovering it since i am broke these days and i can't afford another phone and it's out of warranty, if the backup can be restored somehow or any other methods, please guys let me know, any help is greatly appreciated

i flashed rollback package, then b320, then black screen, then flashed b200 failed at 5%, b162 also failed at 5%, then flashed the rollback package one more time, now i am stuck with the huawei logo, can't flash anything else, any long press just shuts the phone for a second then takes me back to the huawei logo, i can only access the bootloader and it is FRP locked

Read here:
https://forum.xda-developers.com/mate-8/help/frp-locked-bootloader-update-to-n-t3524202

Flash latest recovery2.img of nougat and then try dload

Use huawei exrtacor to get recovery.img
And then flash using fastboot
Then dload ur original FW before updating to nougat

h4ni said:
Use huawei exrtacor to get recovery.img
And then flash using fastboot
Then dload ur original FW before updating to nougat
Click to expand...
Click to collapse
and how do i flash this img?

Tavros said:
Read here:
https://forum.xda-developers.com/mate-8/help/frp-locked-bootloader-update-to-n-t3524202
Click to expand...
Click to collapse
i read there and asked and no one replied me back yet, i also tried the method listed in one of the comments about rollback then 320 and that didnt work

Armali said:
and how do i flash this img?
Click to expand...
Click to collapse
"And then flash using fastboot "

Pfeffernuss said:
"And then flash using fastboot "
Click to expand...
Click to collapse
i'm FRP LOCKED, my bootloader is locked, and i can't use ADB commands

I have the same problem. I am on nougat and I cant enter my google account details because I only have google keyboard voice input wich doesnt work... so its dead now?

Manually debrand from C900 to Cxxx

So the easiest way to do this as I understand it is to use @somboons srk tool unfortunately I'm having trouble with adb.
Running the srk tool the process gets stuck on the command waiting for device
I have tried different adb/fastboot installers and when I run the adb devices command I always get returned "device number Offline"
http://cloud.tapatalk.com/s/58a18bc141157/IMG_20170213_113246.jpg
But funny enough running fastboot devices with phone in fastboot mode return correct respond and I can flash file via fastboot so I don't think it's the USB drives.
So I'm now trying to find a manual way to do it, searching for the past few days have lead me to the following, but I would like someone to confirm that this is the way to go:
1. Take oeminfo from srk tool folders and place it at
/dev/blocl/platform/hi_mci.0/by-name/oeminfo
2. Take custom.bin from srk tool folder and place it at
/data
3. Change build.prop file at /System
And changing the line
ro.build.display.id=NextL00C432B011 for C432
Additional questions I have is that currently am on C636B320 and if I restart my phone will it boot up if I change above thing?
Since I need to change the build.prop file I need to use a file browser/Explorer on the phone... Or is it possible to do the changes above from TWRP?
My ultimate goal is to go to C432B560.
System info:
Unlocked bootloader
Rooted
L29C900B320 (belive it was C636 update.img)
Phone was originally AL10
Computer info:
Windows 10
Skickat från min NEXT via Tapatalk

No one? Anyone? [emoji20]
Skickat från min NEXT via Tapatalk

dexz said:
Okay. I will try to guide you. Let's do it one by one. Bare with me. So are you in C432B320 right now? Are you able to load into the system?
Sent from my HUAWEI NXT-L29 using XDA Labs
Click to expand...
Click to collapse
I'll reply to you in this thread since my initially problem is connected to the question I have in this thread.
To answer your question my phone shows C900B320 same as @EGOiST1991 did. My issue is that I can't use adb commands which means I can't use the srk tool to rebrand. I belive that is why I cannot follow the guide stated in the other thread about updating to nougat. If you read op on this thread you see the issue I have, like you said one step at a time. My goal is to upgrade to nougat... I'm wondering if wouldn't be easier to go stock and update via official update and then root once on C432B560. But if I can get it to work with TWRP which always had been easier until now I would rather do that, then I don't need to redo as many steps.
PS. I appreciate if you point me in the correct direction.

Leo_83 said:
I'll reply to you in this thread since my initially problem is connected to the question I have in this thread.
To answer your question my phone shows C900B320 same as @EGOiST1991 did. My issue is that I can't use adb commands which means I can't use the srk tool to rebrand. I belive that is why I cannot follow the guide stated in the other thread about updating to nougat. If you read op on this thread you see the issue I have, like you said one step at a time. My goal is to upgrade to nougat... I'm wondering if wouldn't be easier to go stock and update via official update and then root once on C432B560. But if I can get it to work with TWRP which always had been easier until now I would rather do that, then I don't need to redo as many steps.
PS. I appreciate if you point me in the correct direction.
Click to expand...
Click to collapse
Ok. Let's settle your adb first because it's much easier having adb working for now and in the future.
1. Which adb version are you using? SRK tools adb should be fine. Make sure run SRK Tools as administrator.
2. Did you installed latest HiSuite (for latest debug driver)?
3. Did you tried different usb port/usb cable?
Sorry you have to do the checklist. Just bare with me on this.
Edit:
One more thing you can try. Plug in your phone to your computer. Make sure the usb debugging icon showing. In Developer Options, select "Revoke USB debugging authorisation" then press OK. Unplug the usb cable then replug it again. You should get message "Allow USB debugging". Tick Always allow and press OK. After that try the "adb devices" again. Hope this will solve your adb issue.

dexz said:
Ok. Let's settle your adb first because it's much easier having adb working for now and in the future.
1. Which adb version are you using? SRK tools adb should be fine. Make sure run SRK Tools as administrator.
2. Did you installed latest HiSuite (for latest debug driver)?
3. Did you tried different usb port/usb cable?
Sorry you have to do the checklist. Just bare with me on this.
Edit:
One more thing you can try. Plug in your phone to your computer. Make sure the usb debugging icon showing. In Developer Options, select "Revoke USB debugging authorisation" then press OK. Unplug the usb cable then replug it again. You should get message "Allow USB debugging". Tick Always allow and press OK. After that try the "adb devices" again. Hope this will solve your adb issue.
Click to expand...
Click to collapse
1. I have used minimal_adb_fastboot_v1.4 and also tried from the srk commadn folder, in both I have run adb kill-server and adb start-server and then adb devices but I always get respond "Device number Offline".
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."
2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled
I dont have that option in Developer Option
The only Revoke option there is when I search is the following

Leo_83 said:
1. I have used minimal_adb_fastboot_v1.4 and also tried from the srk commadn folder, in both I have run adb kill-server and adb start-server and then adb devices but I always get respond "Device number Offline". 
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."

2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled 
I dont have that option in Developer Option 
The only Revoke option there is when I search is the following
2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled
I dont have that option in Developer Option
Yes I have run the tool as administrator but it always get stuck on "Waiting for device..."

2. HiSuite version: 5.0.1.300_OVE
3. Different cable and port
4. USB debugging enabled 
I dont have that option in Developer Option 
The only Revoke option there is when I search is the following

Click to expand...
Click to collapse
Ok. I think that's the reason why your adb detect offline because of usb debugging authorisation issue. Maybe you can extract boot.img & recovery.img from update.app B320 and then flash it via fastboot. After that do factory reset. Backup if needed. After enter to the system. Enable developer option again then check if revoke usb debugging showing.

dexz said:
Ok. I think that's the reason why your adb detect offline because of usb debugging authorisation issue. Maybe you can extract boot.img & recovery.img from update.app B320 and then flash it via fastboot. After that do factory reset. Backup if needed. After enter to the system. Enable developer option again then check if revoke usb debugging showing.
Click to expand...
Click to collapse
That did the trick!!! Cheers!!!
Now shall we go back to the other thread?
Edit: So I felt adventures (I know I know ) and started trying to debrand, initially didn't get it to work but now I'm half way there...
I managed to flash oeminfo and custom.bin for C432 via srk tool when I look in About Phone the following is stated:
Model Number: NXT-L29
Build Number: NXT-C900B320 I believe it is because I haven't changed the build prop
Now to the "issue" when changing the oeminfo and custom.bin with the srk tool the phone did a factory reset and I now I see that in fastboot it states:
Phone Locked
FRP Locked
So this was what I was trying to avoid initially but since it happened I wonder which is the best way forward. Unlocking bootloader once again, installing TWRP and rooting or with the bootloader locked try to go completely stock and down to C432B192....?

Leo_83 said:
That did the trick!!! Cheers!!!
Now shall we go back to the other thread?
Edit: So I felt adventures (I know I know ) and started trying to debrand, initially didn't get it to work but now I'm half way there...
I managed to flash oeminfo and custom.bin for C432 via srk tool when I look in About Phone the following is stated:
Model Number: NXT-L29
Build Number: NXT-C900B320 I believe it is because I haven't changed the build prop
Now to the "issue" when changing the oeminfo and custom.bin with the srk tool the phone did a factory reset and I now I see that in fastboot it states:
Phone Locked
FRP Locked
So this was what I was trying to avoid initially but since it happened I wonder which is the best way forward. Unlocking bootloader once again, installing TWRP and rooting or with the bootloader locked try to go completely stock and down to C432B192....?
Click to expand...
Click to collapse
Glad you managed to get adb back.
Before you do anything please make sure FRP is unlock first (This step is very important before you go Nougat). In developer option under Enable Oem Unlocked is turn on and once you flashed oeminfo it will lock your phone again. Just unlock your Bootloader using SRK Tools. I assumed you have BL code right? Once you have Unlocked BL, Unlocked FRP, TWRP, Root & Debrand. Now you are ready to go Nougat. Report me back.
Good luck

dexz said:
Glad you managed to get adb back.
Before you do anything please make sure FRP is unlock first (This step is very important before you go Nougat). In developer option under Enable Oem Unlocked is turn on and once you flashed oeminfo it will lock your phone again. Just unlock your Bootloader using SRK Tools. I assumed you have BL code right? Once you have Unlocked BL, Unlocked FRP, TWRP, Root & Debrand. Now you are ready to go Nougat. Report me back.
Good luck
Click to expand...
Click to collapse
Before I do complete rebrand... Shouldn't I go to a C432 rom first otherwise I will get bootloop, because of incompatible rom and "model", right?
Sent from my NX507J using Tapatalk

Leo_83 said:
Before I do complete rebrand... Shouldn't I go to a C432 rom first otherwise I will get bootloop, because of incompatible rom and "model", right?
Click to expand...
Click to collapse
Yes. You should debrand first. I mean debrand should be done before going to Nougat.

dexz said:
Yes. You should debrand first.
Click to expand...
Click to collapse
Sorry I think I need step by step instructions now...
I have unlocked bootloader, TWRP for EMUI 4.1 is installed and I think I'm running C636B320 but it is shown as C900B320.
If I change build.prop to C432 I won't be able to boot up on my current C636B320 update.zip so I will download C432B320. And install it from TWRP 4.1 after changing build.prop or maybe do first hmmm...
An other option could be to change build.prop, get bootloop, go to fastboot flash TWRP 4.0 and then flash C432B192.
Which do you think is the better option going forward and keeping in mind I want to go to L29C432B560?
Sent from my NX507J using Tapatalk

Leo_83 said:
Sorry I think I need step by step instructions now...
I have unlocked bootloader, TWRP for EMUI 4.1 is installed and I think I'm running C636B320 but it is shown as C900B320.
If I change build.prop to C432 I won't be able to boot up on my current C636B320 update.zip so I will download C432B320. And install it from TWRP 4.1 after changing build.prop or maybe do first hmmm...
An other option could be to change build.prop, get bootloop, go to fastboot flash TWRP 4.0 and then flash C432B192.
Which do you think is the better option going forward and keeping in mind I want to go to L29C432B560?
Click to expand...
Click to collapse
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys

dexz said:
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys
Click to expand...
Click to collapse
Check! Here goes nothing... [emoji38] wish me luck [emoji12]
Sent from my NX507J using Tapatalk

Leo_83 said:
Check! Here goes nothing... [emoji38] wish me luck [emoji12]
Click to expand...
Click to collapse
Good luck :laugh:

dexz said:
Good luck [emoji23]
Click to expand...
Click to collapse
Haha to late... The phone won't boot into recovery after flashing TWRP 4.0 which is needed if I'm going to flash C432B180 or C432B192
Sent from my NX507J using Tapatalk

Leo_83 said:
Haha to late... The phone won't boot into recovery after flashing TWRP 4.0 which is needed if I'm going to flash C432B180 or C432B190
Click to expand...
Click to collapse
You can't used TWRP 4.0 because you are still in EMUI 4.1 . Try flashing TWRP 4.1 then install C432B180/B192

dexz said:
You can't used TWRP 4.0 because you are still in EMUI 4.1 . Try flashing TWRP 4.1 then install C432B180/B192
Click to expand...
Click to collapse
It's either C432B180 or C432B192?
Or both in sequence i.e first B180 and then B192?
Sent from my NX507J using Tapatalk

Leo_83 said:
It's either C432B180 or C432B192?
Or both in sequence i.e first B180 and then B192?
Click to expand...
Click to collapse
It's either one. If you can flash B192 then B192 it is.

dexz said:
I would suggest use C432B180/192 then in TWRP do format data, wipe (cache, dalvik, system and data) After that flash C432B180/192.zip then reboot to system. You can do debrand from here before going to b560. Once debrand. Go to https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/ follow the steps.
PS: Remember build number must not be C900**** before proceed to B560 or else you end up become test-keys
Click to expand...
Click to collapse
Success!!!
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/
I goes it will be harder to get rooted if I first go to B560 instead of following sillanwali guide

Leo_83 said:
Success!!! 
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/
I ddidn't need to change build.prop via srk tool after flashing B192 it already showed C432!!
I checked the updater and it shows B560, should I still do it via https://forum.xda-developers.com/mate-8/general/how-to-install-nxt-l29c432b560-official-t3540042/

I goes it will be harder to get rooted if I first go to B560 instead of following sillanwali guide
Click to expand...
Click to collapse
Thats great. :good:
It's depend what method you want to try. you can try to follow some of the thread here
Good luck

SOLVED....Can´t get to TWRP because of my fault

SOLVED!......
So hello guys, I am 17 year old, amateur in this mobile topic . My mobile is honor 8 with android 7.0
I unlocked my boot loader and then I tried to flash the TWRP thorugh the fastboot. It didn´t work. Everytime when the mobile was starting I finished on the screen that told me :"your device is unlocked...., your device is starting..." just the normal window when you have bootloader unlocked. I couln´t get into anything. I tried multiple twrps and then I found one called like twrp-3.1.1-1-frd.img https://forum.xda-developers.com/honor-8/development/twrp-t3566563 that worked for me and everything was ok.
But yesterday I wanted to unroot the phone. I read here how to do that: https://forum.xda-developers.com/honor-8/help/honor-8-to-stock-locked-t3509004
But everytime I wanted to start through stock recovery.img (that was downloaded in update.app from https://forum.xda-developers.com/honor-8/development/models-stock-firmware-packages-honor-8-t3501942) nothing happen.
Still the window with the message your device is starting. I coun´t get elwhere then bootloader mode. When I flashed the twrp-3.1.1-1-frd again, it worked normal. But I still wanted to get stock.
I didn´t know what to do so I scrolled down the same site and found this:
"Extract the update.app use this attachment
take Boot , Recovery , Data , System .
Go to ur Fast-boot Folder move this Files inside it .
Open Terminal or CMD throw Admin Rights inside the folder
make sure ur device with fast-boot mode before connecting ur cable to ur device
and make sure u have drivers installed
Type in CMD
Fastboot flash Boot boot.img
Fastboot flash Recovery Recovery.img
Etc .. flash all .imgs
Last type fastboot oem lock <YourPersonalUnlockCodeHere> ( THIS ONLY IF U LIKE TO LOCK AGAIN !)
fastboot Reboot . unplug cable and hope Work Fine ."
So I did what is written there I extracted those img files from update.app and flashed them ...... Now even if I put twrp-3.1.1-1-frd.img nothing happen I am stuck there only thing I can do is to boot to bootloader mode or be in the windew that is telling me device is starting....
And what would I want is to unstuck and go stock again.
Thank you in advance for your reply and sorry for the english.
How did I solve. I flashed twrp in recovery2 too, this solved it and mobile booted. THX for help guys.

https://forum.xda-developers.com/honor-8/how-to/discussion-t3591964/post72056001and#post72056001

deadko said:
https://forum.xda-developers.com/honor-8/how-to/discussion-t3591964/post72056001and#post72056001
Click to expand...
Click to collapse
I dont understand what you meant. the twrp-3.1.1-1frd.img doesn´t work for me at the moment it worked but since I did what I wrote it stopped working.
I cant get even in recovery mod.

Rommco05 said:
I always prefer clean start. Is a longest way but for performace and battery is the best!! So u can make downgrade to Marshmalow and your bootloader will locked (relocked) auto. If don't know how (xda search) leave a post here
Click to expand...
Click to collapse
But I don´t know how and where to start the only 2 screens I get is bootloader boot and your device is starting...
and I dont know why all of the TWRPs stoped working for me

Rommco05 said:
If u can boot to os. Please check in fastboot and in developer section >> frp is locked or unlocked? oem is...?
Click to expand...
Click to collapse
I can´t boot at all not even in recovery mode. "Phone onlocked, FRP unlock"

Rommco05 said:
Your last fw was?
edit: unroot phone? I see first time thx
Click to expand...
Click to collapse
When I rooted I installed how I wrote twrp, then flashed super su
I dont have unrooted phone I just wanted to unroot the way that I would install update.app throught stock recovery mode.

Markus37CZ said:
When I rooted I installed how I wrote twrp, then flashed super su
I dont have unrooted phone I just wanted to unroot the way that I would install update.app throught stock recovery mode.
Click to expand...
Click to collapse
U can install even with root . It will bring back all the files to stock .dont worry about current system. It will be updated with the file in update.app and all ur changes to system will be erased

I messed up with Huawei Mate 9. Please Help.

Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?

Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone

up

You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition

shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.

cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware

ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.

cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.

ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.

Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse

AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.

Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?

LOSQ/LiR - LineageOS 17.1/18.1-UNOFFICIAL-GSI

For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver.
LOSQ/LiR is not developed nor maintained by me!
Credits: @eremitein
Requirements: basically full stock EMUI 9.1, with stock recovery_ramdisk.
Note: I prefer to install in fastboot mode, it's quick, easy and most importantly, safe.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Install arm64-b.. only!
1. LOSQ - LineageOS 17.1-[10]-unofficial-GSI
with the GAPPS
GAPPS
without GAPPS
Vanilla
-----------------------
LiR- LineageOS 18.1-unofficial-[11]-GSI
Download
2. Extract the ROM .img file from the compressed file.
3. Flash extracted losq/lir... .img from fastboot , use command
fastboot flash system (file_name).img
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot .
NFC patch:
https://forum.xda-developers.com/t/losq-lineageos-17-1-unofficial-gsi.4219291/post-84394147
Magisk root (23.0):
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ),
- download and install Magisk manager-23.apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
- Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1):
- copy TWRP file to the SD card, and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
- flash TWRP - run command
fastboot flash recovery_ramdisk (TWRP's_name).img
- boot into TWRP, select storage - SD Card, select "Install image", find TWRP-9.1.img file and mark eRecovery, swipe. Go back, find magisk_patched-23.img file, mark Recovery, swipe. Go back to the TWRP's main menu, select Reboot > Recovery. Done.
Note: you then need to boot your phone every time via Recovery. It'll boot into android as normal but with root.
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
To remove Magisk reinstall stock recovery_ramdisk via TWRP or fastboot , download Here
How to boot into TWRP:
- Turn off your phone, connect to the PC (or charger), then press and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset).
Tips:
https://forum.xda-developers.com/t/treble-gsi-favorite-gallery-camera-and-file-manager.4246019/

I have tried this rom - but without the magisk as I don't really care for root.. However.. This rom still has one big missing feature.. Fingerprint unlock. I can go to register fingerprint. Add the finger multible times to complete the circle.. however.. every time it misses just the last part - it will fail. If anyone has a fix for this I would be happy to use this as my daily driver as it works just fine.

whitetigerdk said:
This rom still has one big missing feature.. Fingerprint unlock
Click to expand...
Click to collapse
I'm afraid you're wrong... It works perfectly for me.

Can confirm that so far everything works flawless. Fingerprint sensor is working on the phone too.
Thank you Alf.
Just two additional questions:
How will updates be perform in future?
How to switch from LOS 16 to this rom - the other P20 lite we have is still on v.16?
Cheers
Horqai

horqai said:
How will updates be perform in future?
Click to expand...
Click to collapse
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
horqai said:
How to switch from LOS 16 to this rom
Click to expand...
Click to collapse
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!

-Alf- said:
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
Click to expand...
Click to collapse
Ugh, is there a way to install emui 9 without it locking my bootloader? I unlocked my bootloader via the @huaweihax method.

[/QUOTE]
XRealX said:
Ugh, is there a way to install emui 9 without it locking my bootloader?
Click to expand...
Click to collapse
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
XRealX said:
I unlock my bootloader via the @huaweihax method.
Click to expand...
Click to collapse
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method

OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
Click to expand...
Click to collapse
There's no way I'm paying for unlocking!
The huaweihax method works this way: you give some information about your device and you flash a slock file to the ramdisk. It unlocks your phone.
To prevent EMUI 9 from re-locking your device, you can flash a zip file to have a custom bootloader unlock code.
Btw, I have hyperlinked the thread that describes this in the "thingy" word.
I guess that custom code should work even if my device is re-locked.

I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone

I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone

How can I repair the factory erecovery I am using the phenix program but it gives me recovery error

itrisev said:
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
Click to expand...
Click to collapse
Sorry, this is not the DC-Phoenix support chat, let's please remember to keep conversations and comments in this thread about LOSQ - LineageOS 17.1, thanks...

Thanks @-Alf-
I followed all your advice in the LOS 16 thread to get 16 installed, but couldn't get gapps to work. So I thought lemme give LOS 17 a shot since it includes gapps, and it works great! However I get the same issue with fingerprint as @whitetigerdk. During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work. Try again or use a different finger". I can provide a screenshot but it's literally just that text.
Apart from that everything seems to work fine. Haven't installed magisk yet, will do that next.

An3skmbi said:
During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work.
Click to expand...
Click to collapse
-Alf- said:
Tested on 9.1.0.132.
Click to expand...
Click to collapse
-Alf- said:
Clean OS
Click to expand...
Click to collapse
-Alf- said:
Install Service ROM using dload method (9.1.0.132 recomm.)
Click to expand...
Click to collapse
Most of custom ROMs require lower build number, on latest build number may or may not work correctly.
If you have followed this guide to the letter and it didn't work, i'm afraid I cant help you .
I've not had any major issue with this LineageOS.
P.S.:
If all this has worked on my device, it does not mean that it goes with everyone else, and vice versa (we are talking about Huawei devices ).

@-Alf- Thanks, that might be it. I'm on firmware 9.1.0.200(C185E4R1P8T8) as that was the recommended one for LOS 16. Let me give it a shot with 132, will update with results.
Edit: With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.

An3skmbi said:
With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
Click to expand...
Click to collapse
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
IMO you can get it via paid service only, for 17euros , hm...look here
.132
The difference between .132 and .200 is google patch - may 2019 vs. july 2019.

-Alf- said:
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
Click to expand...
Click to collapse
What about this one? http://huawei-firmware.com/rom/huawei-p20-lite/ane-lx1/42056
It doesn't have a dload folder, it's just the update.zip basically, so I'm not sure how to flash it only unlocked my phone yesterday, not used to huawei roms yet.
Edit: they explain how here, you create the dload folder manually.

An3skmbi said:
they explain how here, you create the dload folder manually.
Click to expand...
Click to collapse
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .

-Alf- said:
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
Click to expand...
Click to collapse
What do you mean really reliable when the guide is for Android 6? Is there a way to flash the 132 ROM from huawei-firmware?
Also, magisk installation worked perfectly by following your instructions. I can pass safety net with the universal safetynet fix module and got google play certification with the props module.
Is there a way to now boot into TWRP (erecovery)? Currently when booting it doesn't show the option to hold volume up to enter erecovery, it immediately says your phone is booting now. The only way to get into TWRP is to fastboot flash recovery twrp, do stuff there, then flash magisk_patched-ane-v21 over recovery and reboot.
Edit: I captured a logcat while getting the fingerprint enrollment error, there are some exceptions about the enrollment, not sure if that could mean something to the devs to help fix it?

An3skmbi said:
Is there a way to flash the 132 ROM from huawei-firmware?
Click to expand...
Click to collapse
Nope.
An3skmbi said:
Is there a way to now boot into TWRP (erecovery)?
Click to expand...
Click to collapse
Oops I thought I mentioned it in my post, mea culpa.
You have two options:
1. Turn off phone, connect to PC (or charger), then pres and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
2. Restart phone, when appears the yellow warning on screen, press Volume up, hold for ~ 2 sec,
release the button and immediately press and hold again for 2 sec, repeat it 6-7 times, the device will reboot into Stock Recovery , then you can do normal restart - Reboot system now.