Develop Bugs

FAILED (remote: The Device must be rooted first)

Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
2/024/2012 01:24:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
12/024/2012 01:24:19 - INFO - Device connected with USB debugging on
12/024/2012 01:24:19 - INFO - Connected device : LT18
12/024/2012 01:24:19 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
12/024/2012 01:24:19 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
12/024/2012 01:24:41 - INFO - Root Access Allowed
12/025/2012 01:25:24 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
12/025/2012 01:25:24 - INFO - Device Status: ADB mode
12/025/2012 01:25:27 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
12/025/2012 01:25:28 - INFO - Device will soon enter fastboot mode
12/025/2012 01:25:29 - INFO - Device disconnected
12/025/2012 01:25:30 - INFO - Device connected in fastboot mode
12/025/2012 01:25:33 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
12/025/2012 01:25:33 - INFO - Device will soon reboot back into fastboot mode
12/025/2012 01:25:34 - INFO - Device disconnected
12/025/2012 01:25:36 - INFO - Device connected in fastboot mode
12/025/2012 01:25:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot.img
12/025/2012 01:25:40 - INFO - Flashing selected kernel
12/025/2012 01:25:40 - INFO - FASTBOOT Output:
sending 'boot' (5850 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Click to expand...
Click to collapse
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?

Rooting doesnt unlock the bootloader.. Is ur bootloader unlocked? how did u do it? SE has given official instructions on how to unlock the bootloader..
http://unlockbootloader.sonymobile.com/
R u trying to flash this Kernel via the Flash tool software? I would suggest you to connect ur cell in the fastboot mode.
Switch it off and connect it to PC via USB by pressing the menu button (A blue LED will be seen)
U need to have working fastboot for that..
http://www.mediafire.com/?b2of5mpqi2bwczt
Extract this file and when u'll connect ur cell to PC as stated above, for the first time, it will ask for drivers... browse to the USB driver folder which is in the .rar file.
Once u r done with the unlocking bootloader, download the kernel img file and save it in the folder where fastboot.exe is.
Now open the command promt (if u r using windows 7, just press shift and do a right click, select open command prompt here from the menu) and go to the fastboot folder in the cmd. once u r on the path of fastboot. Enter following commands :
fastboot flash boot KernelFile.img (ur copied kernel file)
it will start flashing the kernel, once it is done, type following
fastboot reboot
Ur cell be restarted, when u'll c the kernel booting, keep pressing the volume button to go into the recovery mode..
I cant be held responsible if u damage ur device!!!
Hit thanks if I helped u..

same issue
so ive tried everything i can come across to figure out why it gives me the same error. my bootloader is unlocked and phone is rooted. but i still get the phone must be rooted message no matter what i do and its so irritating cuz i want to put miui on it but cant for the life of me flash anything except stock roms. fastboot not working for me at all. any help please
edit
even though store claimed it to be unlocked the bootloader was not phone just wasnt branded to any carrier so had to unlock the bootloader and everything is glorious now:}

iKevinShah said:
I have got the same stuff (but on my xperia neo)
same exact problem.
The is nothing with bootloader or root, i guess
what my experience is, when i open with cmd in windows and type fastboot devices, i get none but in flashtool it recognised the device in fastboot.
Do you also have the same status as this ?
Click to expand...
Click to collapse
Seriously bro.. you're doing something wrong.. once install all the drivers and execute this command..
Fastboot.exe -i 0x0fce getvar version
If u get 0.3 or something its all fine..
Don't forget to hit 'THANKS' if I helped..
Sent from my Xperia Pro using XDA

You need to unlock your bootloader....
unlockbootloader.sonymobile.com/instructions
I has the same problem, after unlock bootloader, its fine!

I solve it
Overdose1986 said:
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Click to expand...
Click to collapse
Hi,after "BootLoader" again,it's OK.I hope it's useful for U.

i have the same problem
it says that you device must be rooted
and i have my xperia ray rooted and unlocked bootloader
please help me to solve this problem:crying:

I cannot unlock the bootloader
I do have the same problem, my device is rooted as per doomlord method and I when I try to install a custum kernel I too get the error
failed remote the device must be rooted first.
Also I could not unlock the bootloader when I try the steps mentioned in sony website, I got the unlock code and it says " need a unlocked device" while I try to unlock the bootloader: fastboot -i 0x0fce oem unlock 0x<unlockcode>

mail_venu said:
I do have the same problem, my device is rooted as per doomlord method and I when I try to install a custum kernel I too get the error
failed remote the device must be rooted first.
Also I could not unlock the bootloader when I try the steps mentioned in sony website, I got the unlock code and it says " need a unlocked device" while I try to unlock the bootloader: fastboot -i 0x0fce oem unlock 0x<unlockcode>
Click to expand...
Click to collapse
Put the unlock code in the command, enter it, while having phone in fastboot mode, and bootloader should get unlocked. That is only if you do have SIM-unlocked phone, that is no SIM-lock.

--

same problem
Overdose1986 said:
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Click to expand...
Click to collapse
same problem, who to fix?

joaoandre23 said:
same problem, who to fix?
Click to expand...
Click to collapse
Download the lastest flashtool available, now allows you to flash .img kernels

joaoandre23 said:
same problem, who to fix?
Click to expand...
Click to collapse
Rooting does not unlock your bootloader. They are not even related to each other!
There is a big difference between "Bootloader unlock allowed: Yes" and "Bootloader unlocked: Yes". I think you understand the difference.
Unlock bootloader and then try to flash kernel again.

Someguyfromhell said:
Put the unlock code in the command, enter it, while having phone in fastboot mode, and bootloader should get unlocked. That is only if you do have SIM-unlocked phone, that is no SIM-lock.
Click to expand...
Click to collapse
That's right.
The whole process look like (with my phone:
Code:
E:\Download\Mobile\Xperia>fastboot devices
CB5121CFWR&ZLP fastboot
E:\Download\Mobile\Xperia>fastboot.exe -i 0x0fce getvar version
version: 0.5
finished. total time: 0.001s
E:\Download\Mobile\Xperia>fastboot flash boot boot.img
sending 'boot' (8617 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.005s
E:\Download\Mobile\Xperia>fastboot.exe -i 0x0fce oem unlock 0xUNLOCK-KEY
...
(bootloader) Unlock phone requested
OKAY [ 0.500s]
finished. total time: 0.501s
E:\Download\Mobile\Xperia>fastboot flash boot boot.img
sending 'boot' (8617 KB)...
(bootloader) USB download speed was 20960kB/s
OKAY [ 0.438s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.482s]
finished. total time: 0.922s
E:\Download\Mobile\Xperia>

mandarjoshiin said:
Rooting doesnt unlock the bootloader.. Is ur bootloader unlocked? how did u do it? SE has given official instructions on how to unlock the bootloader..
http://unlockbootloader.sonymobile.com/
R u trying to flash this Kernel via the Flash tool software? I would suggest you to connect ur cell in the fastboot mode.
Switch it off and connect it to PC via USB by pressing the menu button (A blue LED will be seen)
U need to have working fastboot for that..
http://www.mediafire.com/?b2of5mpqi2bwczt
Extract this file and when u'll connect ur cell to PC as stated above, for the first time, it will ask for drivers... browse to the USB driver folder which is in the .rar file.
Once u r done with the unlocking bootloader, download the kernel img file and save it in the folder where fastboot.exe is.
Now open the command promt (if u r using windows 7, just press shift and do a right click, select open command prompt here from the menu) and go to the fastboot folder in the cmd. once u r on the path of fastboot. Enter following commands :
fastboot flash boot KernelFile.img (ur copied kernel file)
it will start flashing the kernel, once it is done, type following
fastboot reboot
Ur cell be restarted, when u'll c the kernel booting, keep pressing the volume button to go into the recovery mode..
I cant be held responsible if u damage ur device!!!
Hit thanks if I helped u..
Click to expand...
Click to collapse
can you re-upload the files you uploaded on mediafire please?

isko95 said:
can you re-upload the files you uploaded on mediafire please?
Click to expand...
Click to collapse
Can you use the search button please?
僕のINO2から送られてきた

Solved
I was having the same problem and it was due locked bootloader
then i unlocked the bootloader and every thing goes fine

so, dudes, I had the same problem... beyond others
the situation is: YOUR BOOTLOADER LOOKS LIKE UNLOCKED,
BUT IT ISN'T!!
When you rooted your phone, the rooting method modificated this notification. But the true story is that you need to go to Sony website and claim your BOOTLOADER UNLOCK CODE.
Unless you do this, you'll never flash any thing on your smartphone.
Hugs and kisses!!

Can't flash TWRP - rollback warning. Please advise

I have Chinese 6gb 128gb Mi Max 3 with latest China stable ROM. Finally i decided to get root but i can't flash TWRP over fastboot as in all instructions. My bootloader is unlocked. I get following warning
J:\Xiaomi Mi Max 3 - root>fastboot flash recovery twrpteamwin.img
target reported max download size of 536870912 bytes
sending 'recovery' (61164 KB)...
OKAY [ 1.333s]
writing 'recovery'...
(bootloader) Security Warning: rollback version downgrading,
(bootloader) which may make your device enter to EDL state!!!
(bootloader) Warning: If you want force flashing, try do
(bootloader) 'fastboot oem ignore_anti' before!
FAILED (remote: Please check your package anti version!!!)
finished. total time: 1.353s
I tried 3 versions of TWRP. I also installed latest global stable ROM. Same error. What should i do? Please help...

Same for me. Tried
Code:
C:\platform-tools>fastboot flash recovery twrp-3.3.0-0-nitrogen.img
Sending 'recovery' (61164 KB) OKAY [ 1.325s]
Writing 'recovery' (bootloader) Security Warning: rollback version downgrading,
(bootloader) which may make your device enter to EDL state!!!
(bootloader) Warning: If you want force flashing, try do
(bootloader) 'fastboot oem ignore_anti' before!
FAILED (remote: 'Please check your package anti version!!!')
fastboot: error: Command failed
Is it safe to do the oem ignore_anti thing and force it or would it brik my device?
Device should be official global 64gb 4 gb RAM bootloader unlocked official with 720h waiting periode. Currently MIUI Global 10.2.1.0 installed.

That's what I'm trying to figure out, if it's safe to override it. I don't want to brick my phone. Right now i had installed China beta ROM which has a root built in. But Android Auto refuses to work with this ROM. So i have to either go back to China stable without root, or flash TWRP somehow

So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.

bigScreenUser said:
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
Click to expand...
Click to collapse
PLease let me know if you were able to flash ROM after that! I'm waiting for your reply and biting my nails

Try
fastboot boot twrp.img
And then flash twrp.img through booted recovery.

bigScreenUser said:
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
Click to expand...
Click to collapse
So, did it work? Were you able to flash ROM after overriging ARB warning during TWRP install?

If anyone is interested in overcoming this error: I have done the following, here are my steps:
My phone: China Stable ROM, 6Gb/128Gb Mi Max 3
- Make sure oyu have unlocked bootloader
- I flashed Global Stable ROM first, with the chinese software tool: essentially just automated flashing via fastboot, but any method works. Custom ROMs would be flashed after TWRP.
- Copy TWRP image on a flash drive, make sure it's accessible from the phone
- Phone in fastboot mode, conenct to PC "fastboot boot twrp-tw3300.img" (renamed latest teamwin TWRP image for Mi Max 3)
- Phone boots in TWRP
- Select flash - image - and flash TWRP from inside TWRP (no wiping, nothing else, flash image to recovery partition)
- If root is desired, flash Magisk.
- Reboot to recovery, to see that it sticks
- Reboot to system
- Install Magisk apk, check root.

Sorry for late reply, was bussy getting RR GSI up and running. But sadly it was stuck in bootloop. So i flashed a room from mi-glob roombuilder. This worked so far succesfully, but the chines dialoges do not go well with me.
From my understanding, the warning from the Booloader ist just a warning. In this case may be triggered by ARB, wich means that fastboot or the BL can not guarantee that the room or recovery will work on that phone or may even brick it or is at least not from the vendor.
After you type in :
Code:
fastboot oem ignore_anti
basically this compatibillity check is disabled. After that you can flash any room or recovery you like. If you do flash an older firmware on an ARB activated device you will produce a nice paperwight. But that is another topic.
I do not know, which part (bootloader or fastboot) is responsible for the warning, as i am a total noob regarding flashing android devices.

[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

[HELP NEEDED] Can't unlock Lenovo Z2 Plus bootloader

I'm trying to unlock lenovo z2 plus bootloader using adb and fastboot on fedora. I'm using platform tools version 29. I'm trying
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
but this command won't work. I get this error message
fastboot: invalid option -- 'i'.
Apparently fastboot --help also doesn't shows -i as an argument.
So how can I unlock the bootloader?

Ignore that i part,
Just use fastboot flash unlock unlcok_bootloader.img

According to my experience, under Qualcomm's EDL mode (9008), it can actually flash TWRP without unlocking the bootloader.
"fastboot oem reboot-edl" or "adb reboot edl" will reboot the phone into 9008 mode. You may try special EDL USB cable as well, especially under tricky situations.
You need to download (and install) qpst 2.7.474 and stock ROM (for prog_emmc_firehose_8996_ddr.elf). QFIL has a nice partition manager feature, which allows you to flash anything you want - of course, this will introduce risk of data loss/bricking etc, if improperly operated.

fun_jack said:
I'm trying to unlock lenovo z2 plus bootloader using adb and fastboot on fedora. I'm using platform tools version 29. I'm trying
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
but this command won't work. I get this error message
fastboot: invalid option -- 'i'.
Apparently fastboot --help also doesn't shows -i as an argument.
So how can I unlock the bootloader?
Click to expand...
Click to collapse
These are for older version adb commands so you are facing issues either use older adb files or use new commands

No longer receiving unlock files
I bought an Indian version of Z2 plus on @mazon.ae. after 2 weeks of trying and waiting for the bootloader .IMG file to unlock the phone from official zuk developer site and with different Email including [email protected] CN (aliyun) I gave up and got the device 100% refunded. The latest possible patch date is Nov 1st 2016... Anyone got better results recently (Oct Nov 2019)?

Ludo56510 said:
I bought an Indian version of Z2 plus on @mazon.ae. after 2 weeks of trying and waiting for the bootloader .IMG file to unlock the phone from official zuk developer site and with different Email including [email protected] CN (aliyun) I gave up and got the device 100% refunded. The latest possible patch date is Nov 1st 2016... Anyone got better results recently (Oct Nov 2019)?
Click to expand...
Click to collapse
Ohhh no that seems bad I just received my z2 yesterday for sake of custom rom and rooting.If this does not work out, I have to refund it ASAP.
Please follow this thread and reply if anyone got the unlock file

Finally this thread https://forum.xda-developers.com/le...-receive-unlock-bootloader-img-t3731061/page4 Post Number 40 helped me unlock my bootloader as of 16th November 2019 and now I am on custom ROM

didn't need the file at all
Phone: ZUK Z2 Plus (Z2131)
After having tried many times following this tutorial and never receiving any E-Mail, I found a rather simple solution that worked:
I didn't really expect it to work, so this is from memory, wordings may differ a bit.
First: make backup of your data!
Make sure you have updated ZUI to the latest available version.
Enable developer options ( From your device go to " About -> ZUI version" , scroll down and click " build number " continuously until you see "You are now a developer")
Go to developer Options and look for the toggle "Allow OEM Unlock" (or similar) and set it to enable. Confirm.
Reboot.
The phone automatically performs a factory reset (All Data lost!).
Now you can continue with flashing custom recovery (TWRP) and ROM.
For example use Lineage OS. Instructions: (Sorry, can't post the link) go to lineageos.org and look for the decive and go to install instructions.
Finally I can enjoy the phone with custom ROM and up-to-date Android 10.
You may have to be on ZUI 3.5 (Chinese Version) - It may not work with the Indian Version.
Follow this hints to deep flash ZUI Chinese Stock firmware: https://forum.xda-developers.com/showpost.php?p=83808887&postcount=2
Also read this:
https://forum.xda-developers.com/showpost.php?p=80890653&postcount=40
Quote:
From ZUI 3.5.xxx on you don't need unlock_bootloader.img anymore.
You need to allow OEM unlock in developer options first, then just unlock by "fastboot -i 0x2b4c oem unlock-go" .
If you did not allow OEM unlock option in developer setting then you get error message.
Click to expand...
Click to collapse

can you help me ASAP
E:\Minimal ADB and Fastboot>fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (5 KB)...
OKAY [ 0.032s]
writing 'unlock'...
FAILED (remote: Invalid data)
finished. total time: 0.072s
always like that , i've tried to get new img but still like that.

Development [RECOVERY][OFFICIAL] TWRP for ASUS ROG Phone 6/6 Pro (Qualcomm ONLY)

Official TWRP is now available: https://twrp.me/asus/rogphone6.html
IMPORTANT NOTES:
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2201

It doesn't work! Either flashing or just booting via fastboot gives an error message. Tried to install twrp app...it crashes all the time, couldn't even flash the zip...
I also had to reflash the raw because the phone was stuck in bootloader mode.

I can't flash the img either. I'm on tencent version, is it the difference?
Code:
fastboot flash recovery_a twrp.img
Sending 'recovery_a' (102400 KB) OKAY [ 2.319s]
Writing 'recovery_a' FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
fastboot: error: Command failed

minazukix said:
I can't flash the img either. I'm on tencent version, is it the difference?
Code:
fastboot flash recovery_a twrp.img
Sending 'recovery_a' (102400 KB) OKAY [ 2.319s]
Writing 'recovery_a' FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
fastboot: error: Command failed
Click to expand...
Click to collapse
The message seems to indicate that your device bootloader isn't unlocked...

Captain_Throwback said:
The message seems to indicate that your device bootloader isn't unlocked...
Click to expand...
Click to collapse
I have unlocked the bootloader already.
I can flash to WW by flashall_AFT.cmd, like here https://androplus.org/en/entry/rog-phone-6-china-to-global-conversion/

minazukix said:
I have unlocked the bootloader already.
I can flash to WW by flashall_AFT.cmd, like here https://androplus.org/en/entry/rog-phone-6-china-to-global-conversion/
Click to expand...
Click to collapse
Flashing RAW doesn't require an unlocked bootloader.
I'm just telling you what the message from the bootloader is saying. I don't control that, sorry.

Captain_Throwback said:
Flashing RAW doesn't require an unlocked bootloader.
I'm just telling you what the message from the bootloader is saying. I don't control that, sorry.
Click to expand...
Click to collapse
I've already unlocked my phone with the official unlock device app.
I have the boot loader is unlocked warning screen when my phone power on.
Also, I can flash the patched boot.img to get root.
Code:
fastboot flash boot magisk_patched-25200-boot.img
Sending 'boot_a' (98304 KB) OKAY [ 0.301s]
Writing 'boot_a' OKAY [ 0.240s]
I think my bootloader should be unlocked.

minazukix said:
I've already unlocked my phone with the official unlock device app.
I have the boot loader is unlocked warning screen when my phone power on.
Also, I can flash the patched boot.img to get root.
Code:
fastboot flash boot magisk_patched-25200-boot.img
Sending 'boot_a' (98304 KB) OKAY [ 0.301s]
Writing 'boot_a' OKAY [ 0.240s]
I think my bootloader should be unlocked.
Click to expand...
Click to collapse
Then try just
Code:
fastboot flash recovery twrp.img
without the slot suffix and see if that works. That'll just flash TWRP to the active slot.

Just read carefully on the page that you've downloaded the twrp.img. I saw a short brief guide on how to flash TWRP recovery as below: (using termux or any terminal on your phone)
1. Copy downloaded file and Place it in the root of your /sdcard folder and rename it to twrp.img.
2. Type following command on termux or any terminal (on your phone).
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_a
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_b
Ps_1: it works for me, after failed to flash via fastboot due to locked state. (my phone is rooted with Magisk)
All credit to: Captain_Throwback.
I take no credit at all.
Ps_2: your phone must rooted.

tuannghia1985 said:
Just read carefully on the page that you've downloaded the twrp.img. I saw a short brief guide on how to flash TWRP recovery as below: (using termux or any terminal on your phone)
1. Copy downloaded file and Place it in the root of your /sdcard folder and rename it to twrp.img.
2. Type following command on termux or any terminal (on your phone).
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_a
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_b
Ps_1: it works for me, after failed to flash via fastboot due to locked state. (my phone is rooted with Magisk)
All credit to: Captain_Throwback.
I take no credit at all.
Ps_2: your phone must rooted.
Click to expand...
Click to collapse
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.

fux1976 said:
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
Click to expand...
Click to collapse
Yes, it works for me too.
You can use adb push/pull to transfer files in TWRP.

fux1976 said:
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
Click to expand...
Click to collapse
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.

minazukix said:
Yes, it works for me too.
You can use adb push/pull to transfer files in TWRP.
Click to expand...
Click to collapse
Thanks, that's the best option to push file directly via abd push.

tuannghia1985 said:
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
Click to expand...
Click to collapse
I just flashed the latest raw zip(WW-AI2201-32.2810.2210.220-REL-2210-M2.13.33.24-ASUS_1.1.1-Phone-user-20221109.raw), then everything is working well (e.g. /vendor/factory/COUNTRY is already WW).
I don't use voice typing, Android auto, google pay and fingerprint either, but I just tested the fingerprint features, there is no problems. I pass safetynet and hide root by this Method 2: https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/

tuannghia1985 said:
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
Click to expand...
Click to collapse
Everything is working fine, except these 2 features. Voice typing at first is working but after downloading my configuration (google backup) and my apps, it stops. I can live without it. I've tried several ways: no way of making it work. So I gave up..Maybe with Android 13... as everything was fine on Android 11 on my deceased Rog2. I have Magisk props (safetynet: passed, banking apps ok). But Android auto keeps crashing..Never mind. I have a spare phone to use when I'm driving.

So if you try to fastboot Boot the twrp Image you end up with a destroyed device with no return? Or do i misunderstand that?

Einheit-101 said:
So if you try to fastboot Boot the twrp Image you end up with a destroyed device with no return? Or do i misunderstand that?
Click to expand...
Click to collapse
It says unbootable, not destroyed. RAW should fix it without a problem. It's just a long road to take, including having to wipe the device, for not following a simple instruction.

Hi guys, I want to flash this but I have 2 quick questions:
1. Can I FOTA after install TWRP ?
2. Do I need to reflash it every FOTA ?

fux1976 said:
It doesn't work! Either flashing or just booting via fastboot gives an error message. Tried to install twrp app...it crashes all the time, couldn't even flash the zip...
I also had to reflash the raw because the phone was stuck in bootloader mode.
Click to expand...
Click to collapse
hi how to reflash raw rom , i cant run flashh aft my phone stuck stock recovery help

Captain_Throwback said:
It says unbootable, not destroyed. RAW should fix it without a problem. It's just a long road to take, including having to wipe the device, for not following a simple instruction.
Click to expand...
Click to collapse
how to flash raw ? my laptop cant run flash all AFT pls help