Develop Bugs

Unlock Bootloader on Android 5.1.1 A5CN701?

I've been trying to unlock the bootloader since the A5CN701 update. Here's how i've tried:
1. Go to developer options -> Tick OEM Unlocking
2. Use the launcher.bat from IntelAndroid-FBRL-05-16-2015.7z from this topic http://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
3. Use the T4 option and the tablet ends up like this (because the bootloader is locked):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Use fastboot and enter this code:
Code:
fastboot oem unlock
Then the cmd console and the tablet should look like this:
5. Select ''Yes: change device state'' using the UI on the N1 but here's all i've received:
The result is :''Fail: couldn't change state''
So that's pretty much about how i've tried to unlock the bootloader. I don't know why i couldn't change the device state! Is there anyone that can help me?
I posted this topic so that everyone can join and make suggestions & solutions to rooting the A5CN701 firmware!
Any help would be much appreciated!
P/s: sorry for the sloppy photos, i didn't have time to crop and edit them

it's no use,I use the same way and i get my device state-unlocked.
C：\Dociments and Settings\fldministrator>cd C:\platform-tools
C：\platform-tools>adb reboot bootloader
C：\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time： 5.844s
C：\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine： 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv：
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine： 0.391s
sorry，can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.

乄Rain丶Man said:
it's no use,I use the same way and i get my device state-unlocked.
C：\Dociments and Settings\fldministrator>cd C:\platform-tools
C：\platform-tools>adb reboot bootloader
C：\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time： 5.844s
C：\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine： 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv：
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine： 0.391s
sorry，can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.
Click to expand...
Click to collapse
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out

When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.

Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
you reboot into the Temporary CWM success?

Xkernels said:
you reboot into the Temporary CWM success?
Click to expand...
Click to collapse
Yes

Drivknuten said:
Yes
Click to expand...
Click to collapse
please, you could post your image?

colorado48 said:
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out
Click to expand...
Click to collapse
No,if you unlock device,only stay in bootloader,no matter what your choice，reboot to recovery or power off or anything else. yesterday，i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
p233 said:
please, you could post your image?
Click to expand...
Click to collapse
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive，if you want it ,i can give you the url.

乄Rain丶Man said:
No,if you unlock device,only stay in bootloader,no matter what your choice，reboot to recovery or power off or anything else. yesterday，i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive，if you want it ,i can give you the url.
Click to expand...
Click to collapse
Here is the original old version download link
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529 #3

p233 said:
please, you could post your image?
Click to expand...
Click to collapse
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
乄Rain丶Man said:
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
Click to expand...
Click to collapse
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.

Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
2.adb reboot bootloader?
can you provide some pic?

Xkernels said:
2.adb reboot bootloader?
can you provide some pic?
Click to expand...
Click to collapse
Yes that should be adb reboot bootloader.
NO pics possible, my device is in a bootloop and i dont have the time to fix the device until the weekend.

Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks

pdt100 said:
Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks
Click to expand...
Click to collapse
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update

Drivknuten said:
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update
Click to expand...
Click to collapse
Hi, i was able to submit the command successfully however no change unfortunately. any other ideas? thanks

Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
Then did you root your device successfully？or did you rollback to old version？

乄Rain丶Man said:
Then did you root your device successfully？or did you rollback to old version？
Click to expand...
Click to collapse
Nah i bricked it,

the same thing to me, after i relock bootloader, it jump into a big problem: bootloop, whenever i turn on devices, it just show "android" screen

It's been a while now, can anybody confirm that a root for A5CN701 is on the way?

Drivknuten said:
Nah i bricked it,
Click to expand...
Click to collapse
Oflyt...

Root + Twrp Recovery Asus Zenfone Selfie (ZD551KL)(Z00T)

Pre-Requirement File for Selfie
★ Zenfone Selfie with Unlocked Bootloader ★
★ Zenfone Selfie Recovery ToolKit ★
How to Install TWRP Recovery On Zenfone Selfie
Step 1. Download and Install ADB fastboot tool on PC.
Step 2. Enable USB Debugging mode on ZenFone Selfie (Settings>Developer Options> USB Debugging)
Step 3. Extract Zenfone Selfie Recovery ToolKit
Step 4. Connect ZenFone Selfie with your PC
Step 5. At toolkit Folder Press shift + mouse right click > open command here
Step 6. Type these command in sequence (enter after each line):
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot oem reboot -recovery
Step 9. Wait for the device restart and entered the recovery
Step 10. Done
Asus Zenfone Selfie Easy Root
::::::: Procedure Rooting Asus Zenfone Selfie:::::::
# go to twrp recovery by pressing (power button+ volume up
button)
#select Install from sd card > install zip from SD card > select – Root Zenfone Selfie.zip> yes.
#then a process will occur.
# wait untill it finished.
#then reboot your Asus Zenfone Selfie
Congrats, you have successfully Rooted Asus Zenfone Selfie
:good::highfive:
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE IN THE PROCESS. DO IT AT YOUR OWN RISK.

did u try on prerooted rom zenfone selfie ?

Hey will this work for Z00UD ?

pls help me , its stuck on
D:\DwnlData\asus_zenfone_selfie_recovery_toolkit>adb reboot bootloader
D:\DwnlData\asus_zenfone_selfie_recovery_toolkit>fastboot flash recovery recover
y.img
< waiting for device >
and on my Asus selfie just saw
Fastboot Mode!!!
and stuck on asus logo (

TWRP ?
Hi everyone !
So I tryed to install CM on my Asus zenfone (Z00UD) and everything worked with no problems until the fastboo oem reboot-recovery.
So I tryed to reboot while pressing the VOLUME DOWN key and i get to the original recovery mode.
My phone is still booting to the usual android when I boot without going in recovery.
So I guess TWRP flash didn't worked as excepted, but i remember it showing completed.
Is there a way to verify that TWRP isn't installed so i can re install it ?
Or is it another problem ?

Hiroyt01 said:
Hi everyone !
So I tryed to install CM on my Asus zenfone (Z00UD) and everything worked with no problems until the fastboo oem reboot-recovery.
So I tryed to reboot while pressing the VOLUME DOWN key and i get to the original recovery mode.
My phone is still booting to the usual android when I boot without going in recovery.
So I guess TWRP flash didn't worked as excepted, but i remember it showing completed.
Is there a way to verify that TWRP isn't installed so i can re install it ?
Or is it another problem ?
Click to expand...
Click to collapse
Hi,
Did you use all this three Codes???
"
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot oem reboot -recovery
"

reddyarunm46 said:
Hi,
Did you use all this three Codes???
"
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot oem reboot -recovery
"
Click to expand...
Click to collapse
Yes that is exactly what i used (Except replacing the recovery.img by the twrp.img name)
I also tryed fastboot oem reboot-recovery (without the space)

Hiroyt01 said:
Yes that is exactly what i used (Except replacing the recovery.img by the twrp.img name)
I also tryed fastboot oem reboot-recovery (without the space)
Click to expand...
Click to collapse
Instead of replacing the recovery.img by the twrp.img name jus replace "recovery" with the file name that you have downloaded!!!!
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
Hiroyt01 said:
Yes that is exactly what i used (Except replacing the recovery.img by the twrp.img name)
I also tryed fastboot oem reboot-recovery (without the space)
Click to expand...
Click to collapse
If you have downloaded from the above link in the thread then dont replace anything just use the codes.

reddyarunm46 said:
Instead of replacing the recovery.img by the twrp.img name jus replace "recovery" with the file name that you have downloaded!!!!
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
If you have downloaded from the above link in the thread then dont replace anything just use the codes.
Click to expand...
Click to collapse
I used dl.twrp.me/Z00T/ recovery (to get the latest), and I replaced "recovery.img" by "twrp-3.0.2-5-Z00T.img" in the fastboot comand line. I also put "twrp-3.0.2-5-Z00T.img" in the same folder as "recovery.img".
Should I try again the process with the recovery.img ?
Is it safe to try again to flash the recovery ? (I didn't try again the process because I don't know if it's safe)

Hiroyt01 said:
I used dl.twrp.me/Z00T/ recovery (to get the latest), and I replaced "recovery.img" by "twrp-3.0.2-5-Z00T.img" in the fastboot comand line. I also put "twrp-3.0.2-5-Z00T.img" in the same folder as "recovery.img".
Should I try again the process with the recovery.img ?
Is it safe to try again to flash the recovery ? (I didn't try again the process because I don't know if it's safe)
Click to expand...
Click to collapse
its all right....it worked for me..

Ok thanks, I'll try to flash again when getting home tonight.
Which of those 2 recovery do you recommend using ?

Hiroyt01 said:
Ok thanks, I'll try to flash again when getting home tonight.
Which of those 2 recovery do you recommend using ?
Click to expand...
Click to collapse
1st try with the recovery you downloaded for the thread . Then if you want to update you can do it as well using an TWRP App from play store ...

Can't install Twrp
I did as said above.
But I'm getting Failed to send data (Unknown error)
Please help me to install twrp

Asus zenfone selfie Z00UD android Marshmallow
Hello sir good afernoon,
Im Jon from Philippines and my problem is can you help me how to root my Asus zenfone selfie Z00UD running android marshmallow and install TWRP, because I dont know what to do. PLEASE help me sir.. GODBLESS

Stuck at "fastboot oem reboot -recovery"
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>adb devices
List of devices attached
FAAZCY041912 device
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>adb reboot bootloader
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (29436 KB)...
OKAY [ 0.924s]
writing 'recovery'...
OKAY [ 1.136s]
finished. total time: 2.061s
This is where I got problem:
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>fastboot oem reboot -recovery
...
FAILED (remote: unknown command)
finished. total time: 0.001s
how to resolve?
Please help me. Thanks.

ash_zairy said:
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>adb devices
List of devices attached
FAAZCY041912 device
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>adb reboot bootloader
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (29436 KB)...
OKAY [ 0.924s]
writing 'recovery'...
OKAY [ 1.136s]
finished. total time: 2.061s
This is where I got problem:
C:\Users\StreetLuck\Desktop\Asus ZenFie\asus_zenfone_selfie_recovery_toolkit>fastboot oem reboot -recovery
...
FAILED (remote: unknown command)
finished. total time: 0.001s
how to resolve?
Please help me. Thanks.
Click to expand...
Click to collapse
Same problem for me, did you solved it?

Elmengardo said:
Same problem for me, did you solved it?
Click to expand...
Click to collapse
at that point try this command: fastboot boot recovery.img
it worked for me

does it work in Asus Zenfone Selfie ZD551KL Z00UD android 6.0.1?

fastboot oem reboot -recovery faild how i solve it ?
C:\Users\acer\Desktop\New folder\asus_zenfone_selfie_recovery_toolkit>fastboot oem reboot -recovery
...
FAILED (remote: unknown command)
finished. total time: 0.002s
how to resolve my phone is asus zenfone selfie
android version : 6.0.1
how i solve it ?

Hiroyt01 said:
Hi everyone !
So I tryed to install CM on my Asus zenfone (Z00UD) and everything worked with no problems until the fastboo oem reboot-recovery.
So I tryed to reboot while pressing the VOLUME DOWN key and i get to the original recovery mode.
My phone is still booting to the usual android when I boot without going in recovery.
So I guess TWRP flash didn't worked as excepted, but i remember it showing completed.
Is there a way to verify that TWRP isn't installed so i can re install it ?
Or is it another problem ?
Click to expand...
Click to collapse
I have the same phone Hiroyte but I cant unlock bootloader because the system does not boot to OS >> any help to do this without boot into the system ?
thanks

i want to go back stock recovery and relock the bootloader

Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10

moinkazi said:
Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10
Click to expand...
Click to collapse
delete

allrockedout said:
This is stock recovery. Flash in twrp as image. Select recovery ramdisk as partition.
After flash. Reboot to recovery from twrp. That should take you to stock recovery. There you can do a factory reset.
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=sharing
If you also flashed magisk or root. You will need to flash kernel as well. I was able to flash in fastboot mode. https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=sharing
Click to expand...
Click to collapse
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step

moinkazi said:
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step
Click to expand...
Click to collapse
The recovery I posted before was for bl24 usa version ORRRREEEEEOOOOO ONNNNLLYYY. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.

allrockedout said:
The recovery I posted before was for bl24 usa version. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.
Click to expand...
Click to collapse
Thnks bro

Perfect time to find this post. I am getting the OTA update notification but it won't install on TWRP. My strategy is to return to stock (unrooted and stock recovery) to get the OTA. Once I am on that, get TWRP and Resurrection Remix.

allrockedout said:
The recovery I posted before was for bl24 usa version...
Click to expand...
Click to collapse
BND-L24 you mean?

duckredbeard said:
BND-L24 you mean?
Click to expand...
Click to collapse
Si

allrockedout said:
Si
Click to expand...
Click to collapse
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?

duckredbeard said:
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?
Click to expand...
Click to collapse
I tried flash recover ramdisk than kernel in twrp, rebooted to stock recovery and factory reset. But wouldn't boot, than booted to fastboot and flashed kernel, fastboot flash kernel kernel.img and it rebooted and was all good. Just my experience.

Just trying to avoid using adb.

duckredbeard said:
Just trying to avoid using adb.
Click to expand...
Click to collapse
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure

allrockedout said:
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure
Click to expand...
Click to collapse
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?

duckredbeard said:
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?
Click to expand...
Click to collapse
Fastboot flash recovery_ramdisk recovery_ramdis.img

allrockedout said:
Fastboot flash recovery_ramdisk recovery_ramdis.img
Click to expand...
Click to collapse
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?

duckredbeard said:
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?
Click to expand...
Click to collapse
You can boot to fastboot from twrp than start flashing

allrockedout said:
You can boot to fastboot from twrp than start flashing
Click to expand...
Click to collapse
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.

duckredbeard said:
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.
Click to expand...
Click to collapse
Yeah bootloader is correct. Good luck.

allrockedout said:
Yeah bootloader is correct. Good luck.
Click to expand...
Click to collapse
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!

duckredbeard said:
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!
Click to expand...
Click to collapse
Is frp and bootloader unlocked when rebooting to fastboot both are red?

[GUIDE] How to root your Asus Zenfone 6 without TWRP | Info about A/B

Hey guys and girls,
This is a bit of copy and paste for from my guide for the HTC U12+. I thought it might be helpful to people here too.
If you find mentions of the HTC U12+ please notify me and I will correct them.
I couldn´t find any guide on how to root the Asus Zenfone 6 without twrp yet, so I thought maybe it´s good to have one. It´s also useful for people who don´t like to boot/flash the recovery but want root access.
I also decided now to do a little write up about the A/B slot partition system.
General Information about the A/B slot partition system and seamless updates
Google firstly introduced seamless updates on the Pixel Phones and with it the A/B partition system.
So this means, contrary to non A/B devices, there are two copys of most partitions except userdata.
We have two system (system_a and system_b), two boot (boot_a and boot_b) and two vendor (vendor_a and vendor_b) partitions, amongst others (can be found further down in the partition list but let´s concentrate on these).
When booted in the OS, one slot is actively used and the other is "inactive".
The main advantage that emerges now is, that in case an OTA arrives the "inactive" partitions get updated, while the OS is running. That means while the actual OTA is happening you can use your phone just like you always do.
The following reboot will boot into the former "inactive" slot and use the seamless updated partitions. This happens seamless and just with a reboot. So OTAs are much faster!
If you are interested further here are some links:
https://www.xda-developers.com/list-android-devices-seamless-updates/
https://source.android.com/devices/tech/ota/ab/
https://source.android.com/devices/tech/ota/ab/ab_faqs
Here’s another writeup from the XDA portal!
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But here are a few tips and tricks:
How to reboot to bootloader to be able to use fastboot:
From booted OS with buttons: Press and hold power down until the screen goes black, then press and hold power and vol up to enter bootloader
non responding and the phone isn´t booting: press and hold power plus volume up to enter bootloader
From the OS or recovery via ADB (requires USB Debugging enabled in dev options):
Code:
adb reboot bootloader
How to get the active slot:
Code:
fastboot getvar current-slot
How to set the active slot:
A word of advice. If you don´t know what you´re doing you should probably not change slots. Because my U12+ only has a working A Slot. The B slot is without the first OTA or flashing a RUU unbootable.
Set active slot to a:
Code:
fastboot --set-active=a
Set active slot to b:
Code:
fastboot --set-active=b
How to extract the boot.img from a firmware.zip
1. Download the firmware zip from here : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
2. Follow the steps described here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
3. Obtain your boot.img
How to root your phone without TWRP
Prerequisites:
- unlocked bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries (can always be found here
- working adb and fastboot environment
- magisk-patched boot.img
How to:
1. Download the latest magisk manager from here and install it on your phone: https://github.com/topjohnwu/MagiskManager/releases
2. Get a boot.img that fits your current firmware. Look at the point above, how to extract it from an Asus firmware zip.
Important: if you decide to use a pre-patched boot.img (available below), download it and place it in your fastboot folder, then skip to step 11!
3. Copy the extracted boot.img to your phone
4. Open the magisk manager app and tap two times on install
5. Now choose patch boot.img file and select the previously extracted boot.img you copied to your phone in the upcoming file chooser
6. Wait for the boot.img to be patched
7. Now connect your phone to your pc and make sure usb debugging is enabled in developer options
8. Open up a terminal in your fastboot folder and make sure adb is working by typing
Code:
adb devices
into terminal which should return your serial number
9. Pull the patches boot.img to your fastboot folder via:
Code:
adb pull /sdcard/Download/magisk_patched.img
10. Reboot to bootloader:
Code:
adb reboot bootloader
11. Flash the magisk patched boot.img:
Code:
fastboot flash boot magisk_patched.img
12. Congratulations you´re now rooted.
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609

Is it possible to do this and still get OTA updates from ASUS?

sidamos77 said:
Is it possible to do this and still get OTA updates from ASUS?
Click to expand...
Click to collapse
You need to unlock the bootloader for this which will prevent you from getting ota updates automatically from asus. But you can install updates manually.

Ok, great, thank you.

Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.

Any way to unofficially unlock the Bootloader?

vasra said:
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Click to expand...
Click to collapse
In Europe unlocking the bootloader and rooting doesn't legally void warranty. It was ruled this way a few years ago.

Freak07 said:
[...]
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Click to expand...
Click to collapse
The folder WW_PHONE-16.1210.1904.75-0 which is the firmware my device has, is empty. Do you still have the prepatched boot.img of that version ? ASUS doesn't have that version for download anymore.
Thanks in advance.
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?

GRöder said:
how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-26#post-2433773
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-37#post-2442236
Use Translator.

I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .

GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
the getvar command returns the following output:
Do you have any advice for me ?
Edit:
After being curious and trying which worked, I tried to flash it at the active slot b explicitly: which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.

Freak07 said:
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Click to expand...
Click to collapse
That might have been the the point. In fact, I did download them, but I used (definately outdated, because on my pc since literally years) a minimal adb and fastboot installation.
I didn't think about it, as this is my first A/B device.
I won't try it now with the latest ones, because it worked and I don't want to destroy something (since we still dont have a working TWRP for backup & recovery) but I guess you're right, and the problem were the outdated binaries.
Thank you.

GRöder said:
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.

isthisadagger said:
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
Click to expand...
Click to collapse
In fact, I tried that before I tried the stock-recovery-method (found it at the ASUS FAQ-pages), but it didn't work, even after a reboot, no notification showed up.

GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks

Ya how do we unlock the bootloader without asus knowing it

MirkoMirko9 said:
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Click to expand...
Click to collapse
nikhil18 said:
Ya how do we unlock the bootloader without asus knowing it
Click to expand...
Click to collapse
I used the official app, while the device was connected to the internet. So yes, ASUS knows that I unlocked the device.
The device was still at the -75 firmware, when I did it.
 @MirkoMirko9 If you can live with asus knowing that you unlocked the device, try it again with active internet connection.
As far as I know, there is no other method yet.

unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?

QuazIqbal said:
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79817571&postcount=31

magisk_patched boot.img for .156 firmware is uploaded to the patched boot.imgs folder

Question about rooting with Magisk

I have successfully unlocked the Pixel 2 XL and installed the official release 8.0.0 / OPD1.170816.010 from Sep 2017. I downloaded Magisk and transfered the image to the phone and extracted the files on the phone.
According to the official guide, I have to patch the boot.img, but the image only contains a bootloader.img. When I use the "fastboot flash boot boot.img" command, it also tells me "No such partition".
How do I properly patch the official file and root the Pixel 2 XL without bricking it? Am I doing something wrong?

Venomiz said:
I have successfully unlocked the Pixel 2 XL and installed the official release 8.0.0 / OPD1.170816.010 from Sep 2017. I downloaded Magisk and transfered the image to the phone and extracted the files on the phone.
According to the official guide, I have to patch the boot.img, but the image only contains a bootloader.img. When I use the "fastboot flash boot boot.img" command, it also tells me "No such partition".
How do I properly patch the official file and root the Pixel 2 XL without bricking it? Am I doing something wrong?
Click to expand...
Click to collapse
Are you unzipping the second folder as well?
Factory Image .zip > unzip to factory image folder > unzip to 2nd factory image folder > boot.img
Curious as to why you're flashing 8x instead of android 10?
If you still hit a wall, check out the step by step instructions linked in my sig, near the bottom is an upgrade from os to os section ( 9x to android 10).

Az Biker said:
Are you unzipping the second folder as well?
Factory Image .zip > unzip to factory image folder > unzip to 2nd factory image folder > boot.img
Curious as to why you're flashing 8x instead of android 10?
If you still hit a wall, check out the step by step instructions linked in my sig, near the bottom is an upgrade from os to os section ( 9x to android 10).
Click to expand...
Click to collapse
Thanks for the reply. In the folder are the following files:
bootloader-taimen-tmz10n.img
flash-all.bat & .sh
flash-base.sh
radio-taimen-g8998-.....
And I overlooked the image-taimen-opd1.170816.010.zip
So, I patched with magisk the wrong file but it was successful (at least if I trust the onscreen text). I will now transfer the boot.img to the pixel, patch it, transfer it back, and flash. I will reply after doing so
PS: Android 8 is easier to use if you do something you should not in Pokemon Go... :silly:
And the

Why patch the boot image manually, flashing magisk via TWRP as it works fine. Ive never used the patch boot image method ever on any of the devices ive owned.
1) Flash ROM
2) Boot TWRP
3) Flash TWRP (optional)
4) Flash Magisk
5) Reboot

Hi folks, this is the current status.
I patched the boot.img and tried the following:
fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boota' (25632 KB)...
OKAY [ 0.542s]
writing 'boota'...
FAILED (remote: No such partition.)
finished. total time: 0.548s
What did I miss here?

Venomiz said:
Hi folks, this is the current status.
I patched the boot.img and tried the following:
fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boota' (25632 KB)...
OKAY [ 0.542s]
writing 'boota'...
FAILED (remote: No such partition.)
finished. total time: 0.548s
What did I miss here?
Click to expand...
Click to collapse
Let's start over from scratch because you're not following the instruction being posted, so maybe you are trying to accomplish something else.
What state is your device currently in and what are you trying to accomplish? I was under the impression you simply want to flash the last 8x factory image to your device, is that correct?

Az Biker said:
Let's start over from scratch because you're not following the instruction being posted, so maybe you are trying to accomplish something else.
What state is your device currently in and what are you trying to accomplish? I was under the impression you simply want to flash the last 8x factory image to your device, is that correct?
Click to expand...
Click to collapse
Uhm not really. As I said in the title, I want to root the Pixel 2 XL with Android 8 and Magisk.
So what I did so far is:
- Unlocked the bootloader and applied the Android 8 image
- Downloaded and installed magisk
- Unzipped the original rom wice to get the boot.img, transfer it to the phone, patched it with magisk and transfered it back to the PC.
When now trying to flash it with fastboot, the output above showed up.

Venomiz said:
Uhm not really. As I said in the title, I want to root the Pixel 2 XL with Android 8 and Magisk.
So what I did so far is:
- Unlocked the bootloader and applied the Android 8 image
- Downloaded and installed magisk
- Unzipped the original rom wice to get the boot.img, transfer it to the phone, patched it with magisk and transfered it back to the PC.
When now trying to flash it with fastboot, the output above showed up.
Click to expand...
Click to collapse
In fastboot do the following:
flash your factory 8 image (leave the -w intact to wipe your device, remove the -w to keep your data)
after your device boots up, get back to bootloader and fastboot the TWRP img from platform folder
once booted into TWRP, flash TWRP.ZIP to install cust recovery
in twrp flash cust kernel (optional)
reboot and allow the OS to fully settle in ( 1-2 minutes after bootup)
boot into TWRP and install magisk
reboot
These same instructions are found in much more detail in the link in my sig. I use this method every month for the latest update, and it's never failed. No patching images, no booting to diff slots, just follow the simple steps.

Az Biker said:
In fastboot do the following:
flash your factory 8 image (leave the -w intact to wipe your device, remove the -w to keep your data)
after your device boots up, get back to bootloader and fastboot the TWRP img from platform folder
once booted into TWRP, flash TWRP.ZIP to install cust recovery
in twrp flash cust kernel (optional)
reboot and allow the OS to fully settle in ( 1-2 minutes after bootup)
boot into TWRP and install magisk
reboot
These same instructions are found in much more detail in the link in my sig. I use this method every month for the latest update, and it's never failed. No patching images, no booting to diff slots, just follow the simple steps.
Click to expand...
Click to collapse
It worked perfectly, thank you!