Related
Hey Guys I need your help.
I think I bricked my OnePlus 3. (BTW yes its unlocked)
What still works:
1. Fastboot
2. TWRP and Stock recovery
3. ADB Sideload
I use twrp 3.1.0-0
Fastboot looks like this:
FASTBOOT MODE
PRODUCT_NAME: msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMER - [censored]
SECURE BOOT - enabled
DEVICE STATE - unlocked
But I cant boot into any system. I think I corrupted the /data partition or sth.
What I tried:
1. Flashing boot.img and system.img via fastboot -> Result: Still won't boot. I get the Oneplus and android logo and a blackscreen after this.
2. Flashing stock rom / lineage rom / newest stock rom via TWRP Sideload or Stock-recovery Sideload -> TWRP gives me this error: Updater process ended with ERROR: 7
Any Ideas?
Premaider said:
Hey Guys I need your help.
I think I bricked my OnePlus 3. (BTW yes its unlocked)
What still works:
1. Fastboot
2. TWRP and Stock recovery
3. ADB Sideload
I use twrp 3.1.0-0
Fastboot looks like this:
FASTBOOT MODE
PRODUCT_NAME: msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMER - [censored]
SECURE BOOT - enabled
DEVICE STATE - unlocked
But I cant boot into any system. I think I corrupted the /data partition or sth.
What I tried:
1. Flashing boot.img and system.img via fastboot -> Result: Still won't boot. I get the Oneplus and android logo and a blackscreen after this.
2. Flashing stock rom / lineage rom / newest stock rom via TWRP Sideload or Stock-recovery Sideload -> TWRP gives me this error: Updater process ended with ERROR: 7
Any Ideas?
Click to expand...
Click to collapse
Flash stock recovery and flash stock oos
v.konvict said:
Flash stock recovery and flash stock oos
Click to expand...
Click to collapse
says "installation failed" when I try to install stock oos on stock recovery via adb sideload
edit: If I manually flash (via fastboot) boot.img and system.img and then twrp recovery twrp says I do not have a system installed. why that?
edit2: while flashing system.img it first says "Invalid sparse file format at header magi" but then continues normally. does this help?
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
try this
save all your data before
Spector_Prophet said:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
try this
save all your data before
Click to expand...
Click to collapse
He could also try the one that flashes OxygenOS 4.0.3: Newer unbrick tool
I was trying to flash LineageOS but didn't work. I then attempted to fix my mistake. My attempts only made the problem worse as now I can only use fastboot. There is no recovery or OS.
I do have the latest ADB and Fastboot drivers on my computer.
I have unlocked the bootloader.
Code:
fastboot oem unlock
...
FAILED (remote: Device already unlocked)
When I flash the factory image, I get this message:
Code:
writing 'bootloader'...
FAILED (remote:unsupported command)
This happens when I try to flash the other images found in the factory images file from Google individually. This also happens when I try to flash the latest TWRP recovery image.
The following commands also return a "remote: unsupported command" error:
Code:
fastboot erase [partition]
fastboot format [partition]
I have also locked and reunlocked the bootloader but doing this does not change anything when flashing again.
When the bootloader is locked and I return to the screen after pressing lock and volume down, there is a red box that reads:
Code:
OS on your tablet is damaged. Needs recovery.
This goes away when unlocking again.
I have tried Unified Android Toolkit but have run into the same "remote: unsupported command" response.
This highlights all my attempts to fix my tablet. Thanks for reading up to this point.
I've seen suggestions to use fwtool but I can't wrap my head around how to use it. If that is the only way to fix my tablet, can someone show me how to use it to solve my problem? Keep in mind I can only use fastboot. No recovery or OS.
Is there a flashall file in the image from Google?
sabrdawg said:
Is there a flashall file in the image from Google?
Click to expand...
Click to collapse
Yes. When I run it, get into the same message.
Code:
writing 'bootloader'
FAILED (remote: unsupported command)
I was just reading about someone else who had a similar issue, and it was recommended for them to update their ADB and fastboot. Hope this helps!
viii_xvi said:
I was trying to flash LineageOS but didn't work. I then attempted to fix my mistake. My attempts only made the problem worse as now I can only use fastboot. There is no recovery or OS.
I do have the latest ADB and Fastboot drivers on my computer.
I have unlocked the bootloader.
Code:
fastboot oem unlock
...
FAILED (remote: Device already unlocked)
When I flash the factory image, I get this message:
Code:
writing 'bootloader'...
FAILED (remote:unsupported command)
This happens when I try to flash the other images found in the factory images file from Google individually. This also happens when I try to flash the latest TWRP recovery image.
The following commands also return a "remote: unsupported command" error:
Code:
fastboot erase [partition]
fastboot format [partition]
I have also locked and reunlocked the bootloader but doing this does not change anything when flashing again.
When the bootloader is locked and I return to the screen after pressing lock and volume down, there is a red box that reads:
Code:
OS on your tablet is damaged. Needs recovery.
This goes away when unlocking again.
I have tried Unified Android Toolkit but have run into the same "remote: unsupported command" response.
This highlights all my attempts to fix my tablet. Thanks for reading up to this point.
I've seen suggestions to use fwtool but I can't wrap my head around how to use it. If that is the only way to fix my tablet, can someone show me how to use it to solve my problem? Keep in mind I can only use fastboot. No recovery or OS.
Click to expand...
Click to collapse
Hi, did you tried to lock fastboot then unlock it again. Try also to change the bootloader or the kernel with fastboot or boot directly twrp without installing it
rhmanoa said:
Hi, did you tried to lock fastboot then unlock it again. Try also to change the bootloader or the kernel with fastboot
Click to expand...
Click to collapse
I have locked and unlocked the bootloader. I have also flashed bootloader and kernel images from the factory images and I get the same "Remote: unsupported command" message.
rhmanoa said:
Boot directly twrp without installing it.
Click to expand...
Click to collapse
I don't think I understand this. By "twrp" you mean boot straight into recovery mode, I can't. Every time I try to, I am stuck on the Google screen. I left it on that for an hour with no change.
sabrdawg said:
I was just reading about someone else who had a similar issue, and it was recommended for them to update their ADB and fastboot. Hope this helps!
Click to expand...
Click to collapse
Can you direct me to where to download the latest drivers? You look like you're more familiar with this than I am and me being new to using fastboot, I may have gotten an older version.
This should help
https://developer.android.com/studio/run/win-usb.html
sabrdawg said:
This should help
https://developer.android.com/studio/run/win-usb.html
Click to expand...
Click to collapse
It appears I have the latest drivers. To make sure nothing's changed, I flashed the factory image again and it gives the same response as before.
viii_xvi said:
I don't think I understand this. By "twrp" you mean boot straight into recovery mode, I can't. Every time I try to, I am stuck on the Google screen. I left it on that for an hour with no change.
Click to expand...
Click to collapse
fastboot boot twrp-3.1.1-1-dragon.img
Vartom said:
fastboot boot twrp-3.1.1-1-dragon.img
Click to expand...
Click to collapse
I am greeted with "remote: image verification failed".
viii_xvi said:
I am greeted with "remote: image verification failed".
Click to expand...
Click to collapse
Is the boot loader unlocked before this command is executed?
Vartom said:
Is the boot loader unlocked before this command is executed?
Click to expand...
Click to collapse
Yes, it was unlocked. I tried relocking, reunlocking, and executing the same command but it still gave me the same message.
I got exactly the same problem. Any solution for this?
Bolemichel said:
I got exactly the same problem. Any solution for this?
Click to expand...
Click to collapse
I've read relocking and unlocking the bootloader fixes it so that you can flash through fastboot. This didn't work for me, unfortunately , and haven't been able to fix my Pixel C.
Are you sure you no recovery? I was not able to fix my tablet because I foolishly deleted my recovery and was stuck in dev mode but unable to flash anything. As long as you have a recovery, you can fix it. I don't remember exactly how but you'll be able to find it.
viii_xvi said:
I've read relocking and unlocking the bootloader fixes it so that you can flash through fastboot. This didn't work for me, unfortunately , and haven't been able to fix my Pixel C.
Are you sure you no recovery? I was not able to fix my tablet because I foolishly deleted my recovery and was stuck in dev mode but unable to flash anything. As long as you have a recovery, you can fix it. I don't remember exactly how but you'll be able to find it.
Click to expand...
Click to collapse
lock/relock has no effect. Unfortunatelly recovery is broken, tab will reboot when I try to enter recovery.
I'm in contact with google and try to get a new unit now
I also have the same problem and I am so disappointed that I cannot figure it out....#pls forgive my poor English#who can help me ..it is same to me that I have no idea to use so called"fwtool"tool.
Guys I have been trying to fix this for the past week and found these two posts.
[RECOVERY][TWRP][dragon]
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now ! https://twrp.me/google/googlepixelc.html I would like to continue this thread for publishing test builds and other troubleshooting. Once the changes...
forum.xda-developers.com
XCEED :: [KERNEL] :: [AOSP/Stock/PureNexus] :: [v9.xx / Android 7.1.2]
Exceed the limitations /// XCEED kernel Only for Pixel C If this technology provides value to you a donation for the time spent creating it is very welcome! NOTE: The screenshots are actual screenshots from my Pixel C, though your...
forum.xda-developers.com
It explains how to use fwtool, it's actually pretty straightforward. The second link above has the download link for fwtool. Once you download it, start your pixel in fastboot mode while connected to your laptop. In the command line:
Code:
adb push <path to fwtool>/fwtool /sdcard/Download/fwtool
You should get a message like this below:
fwtool: 1 file pushed, 0 skipped. 4.7 MB/s (43880 bytes in 0.009s)
Then open the shell in adb using:
Code:
adb shell
then go to your download directory and check the dev_boot_fastboot_full_cap flag using the commands below:
Code:
cd /sdcard/Download/
fwtool vbnv read dev_boot_fastboot_full_cap
The output for me was:
Code:
127|dragon:/ # cd /sdcard/Download/
dragon:/sdcard/Download # fwtool vbnv read dev_boot_fastboot_full_cap
Firmware debug Tool
dev_boot_fastboot_full_cap = 0
I then set the flag to 1 using fwtool as below.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
After running this, check the flag again using fwtool vbnv read dev_boot_fastboot_full_cap again. It should now display 1. After doing this, I was able flash using fastboot
I hope this helps everyone and good luck...
Evren Tekin said:
Guys I have been trying to fix this for the past week and found these two posts.
[RECOVERY][TWRP][dragon]
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now ! https://twrp.me/google/googlepixelc.html I would like to continue this thread for publishing test builds and other troubleshooting. Once the changes...
forum.xda-developers.com
XCEED :: [KERNEL] :: [AOSP/Stock/PureNexus] :: [v9.xx / Android 7.1.2]
Exceed the limitations /// XCEED kernel Only for Pixel C If this technology provides value to you a donation for the time spent creating it is very welcome! NOTE: The screenshots are actual screenshots from my Pixel C, though your...
forum.xda-developers.com
It explains how to use fwtool, it's actually pretty straightforward. The second link above has the download link for fwtool. Once you download it, start your pixel in fastboot mode while connected to your laptop. In the command line:
Code:
adb push <path to fwtool>/fwtool /sdcard/Download/fwtool
You should get a message like this below:
fwtool: 1 file pushed, 0 skipped. 4.7 MB/s (43880 bytes in 0.009s)
Then open the shell in adb using:
Code:
adb shell
then go to your download directory and check the dev_boot_fastboot_full_cap flag using the commands below:
Code:
cd /sdcard/Download/
fwtool vbnv read dev_boot_fastboot_full_cap
The output for me was:
Code:
127|dragon:/ # cd /sdcard/Download/
dragon:/sdcard/Download # fwtool vbnv read dev_boot_fastboot_full_cap
Firmware debug Tool
dev_boot_fastboot_full_cap = 0
I then set the flag to 1 using fwtool as below.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
After running this, check the flag again using fwtool vbnv read dev_boot_fastboot_full_cap again. It should now display 1. After doing this, I was able flash using fastboot
I hope this helps everyone and good luck...
Click to expand...
Click to collapse
Yes, but no adb without recovery
Is your Pixel C stuck in a never-ending bootloop after flashing TWRP? Meaning, you're in TWRP, you choose Reboot ===> System and instead of booting into Android, it just keeps booting back into TWRP?
Please reference the following thread/post:
https://forum.xda-developers.com/showpost.php?p=78028560&postcount=27
Hope this helps someone.
BJ
I am very beginner in these tweakings. Incidently I have also asked a question with similar problem. With my Google Pixel C only booting into twrp. I think I need to install stock rom/ factory image from https://developers.google.com/android/images according to method provided there. Is it okay to flasing "flash-all.bat" with twrp already installed? Because now my concern is avoiding a 'hard bricked' device.
I ended my boot looping by installing stock rom (ryu-opm8.190605.005-factory-25b457f3) downloaded from google website. For me flash-all.bat or flash-all.sh were not working and throwing multiple kind of errors. I did two things. First I used this guide from xda to set PATH variable "How to Use ADB or Fastboot From Any Directory on your Windows/Linux PC". Then I copied the .zip ROM file into "platform-tools" folder. Importantly I also extracted the .zip file within the .zip to same platform-tool folder. I manually installed each .img file one by one:
sudo fastboot flash bootloader bootloader_dragon-google-smug.img
sudo fastboot reboot bootloder
sudo fastboot devices
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash vendor vendor.img
System now working fine with stock ROM and recovery.
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
Hi guys,
I'm trying to install LineageOS to XZ2 Compact but I have some issues. I was following this guide. (NOTE: Bootloader unlock was done by owner of phone, not sure if he did something wrong)
As said in guide, I should connect phone to PC and reboot to bootloader using command
Code:
adb reboot bootloader
This works. However, when trying to flash boot partition with LineageOS recovery I'm getting fastboot errors. Here are commands and their verbose output (output is same for all these partitions - boot, boot_a, boot_b, boot__a, boot__b):
Code:
fastboot flash boot lineage-17.1-20201225-nightly-xz2c-recovery.img
fastboot: error: cannot get boot partition size
fastboot version is 30.0.5
Any ideas?
Have you tried fastboot devices to see if your device shows up? If that does work, can you try "boot a" with no underscore(s)?
I managed to install Lineage OS to phone. Problem was (strangely) with linux fastboot. It detected device normally but something was not right. Done same steps on windows pc and it worked.
I forgot to update thread.