Related
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
hatemelectr said:
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
Click to expand...
Click to collapse
Some images simply do not work, so you will need to check for other images simply.
Just install this one : https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
root&gapps&backlight working
of course you'll need Device+ID.apk and register ID with Google but that's easy and simple
Device: Huawei 8x Max AR00
The Quack version works but sadly it is Android 10. I have found many Android 12L GSI roms that I would like to use but the brightness is an issue on all of them. Anyone know how to copy the Quack backlight vendor display and patch it to the newer GSI roms? Tried buildprop GSI wont boot (Crdroid, Lineage 19) Tried Dirty flashing, obviously didn't work. Can't seem to find the file containing the slider brightness limitations. Phherson gives rom backlight options and tried several combinations, and yes rebooted everytime none of them work. Any ideas?
riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
After trying many different gai variants and versions I found they all have an issue with browsers. Both chrome and edge freeze after scrolling a bit. I'm wondering if this because the GSI uses too much storage space and cannot buffer? Tried to port GSI onto other partitions such as cust, prod didn't work. Even Magisk flashes successfully but does not appear in the rom. The a and b is confusing like EMUI uses both and the TWRP does not decrypt and no Verity commands don't work either. The havoc rom seems to work the best with gapps pico flashed.
~ Android 12 backlight issues had to revert to android 10
~ All GSI have the common browsers freezing. Have to use VIA browser (basic)
~ Magisk won't install have to port to ramdisk, but isn't that the TWRP recovery?
Hello, which one is the Qualcomm driver to be installed for sdm660?
EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!
I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?
abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.
~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?
vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.
Since this device tends to bootloop easily and because I've seen lots of questions about it and information is spread across many threads and posts, I'm writing this guide to help you guys troubleshoot bootloops before asking generic "help me" questions.
I) Terminology
1) BROM - A readonly memory on the SoC that runs right when the device boots. Loads the preloader. SPFT talks to it after authentication.
2) Preloader - MTK firmware that resides on flash. It is loaded on the chip's SRAM. It is responsible for initializing DRAM, and is one way of authenticating SPFT (the other is authenticating directly with the BROM, but I believe the way thi is done is known only to MTK and OEM engineers, and not even to authorized service centers). It also loads LK. Its source is distributed to OEMs, but is otherwise unavailable. Plenty of leaks for other devices can be found on the internet (some from the OEMs themselves).
3) LK - Little Kernel. This seems to be the most common platform for Android bootloaders. Mediatek has its own proprietary branch. Same source status as preloader. As an android bootloader, it is responsible for loading recovery or usual kernel image, as well as fastboot flashing.
4) Kernel - If you're on these forums, you should know what it is. You can find it in boot.img
5) DTBO - The device tree for the linux kernel. It specifies which hardware is available on the device. On usual (x86) PC platforms, the BIOS and Option ROMs store device information and offer it to the kernel (through UEFI/ACPI). As arm boards do not have such those, the linux kernel uses dtbos which play the same role.
II) Boot process
1) The ARM cores on the SoC start and jump to the address of the BROM.
2) (I'm not very sure of this, there's too little information) BROM puts the cores into a known state, should listen on the in-build UART for some time (half a decade ago, some leaks said something about 150ms), and if it doesn't receive anything, it loads the preloader.
3) The preloader initializes basic stuff like DRAM (phone's ram), watchdog, USB, etc. If the phone is connected to SPFT, it talks to it and authenticates it (the (in)famous "Account not authorized for this operation" should come from a check in here). I believe it also turns on the charging light. On a normal boot, it further loads lk. I belive that it also shows the chinese menu on pressing the Vol- button on factory preloader, but I did not check this.
4) LK (the one that comes with factory preloader) checks if Vol+ is pressed, and displays the bootloader menu (the one with the 4 english entries). When selecting recovery, it loads recovery. If normal boot is selected, it loads boot.img and dtbo.img and I believe it makes some checks on them (possibly of signatures, see the kernel trees). It then loads the proper image from the logo.bin partition and displays it (note: I've checked Logo Builder; rebuilding the logo.bin partition with it makes LK reboot before showing any image - this is done after the boot menu); examples are the one where it shows "Unlocked" or the Fastboot background. It also checks vbmeta for verified boot. Then it boots the selected entry.
5) The linux kernel does some hardware init, mounts system and starts Android's init.
6) Android does its usual init, mounting vendor, loading modules and firmware, turning on stuff like wifi, bluetooth, gnss, etc.
III) Tips for diagnosing bootloops
1) When bootlooping, plug your phone in a computer and check for the following (this is from my experience):
a) Charging light turning on
b) Vol+ menu showing up
c) Redmi logo showing up
d) Charging light turning off
e) Boot animation showing up
2) Things to do based on where things didn't work as in (1):
If (a) doesn't turn on, you're most likely in deep ****, and I'm not sure who can help you. Edit: Try pressing Vol+ and see if a device with VIDID 0x0e8d:0x0003 shows up. That would be the BROM. If it shows up, try using SPFT (most likely won't work, but you have nothing to lose anyway).
If (b), try SPFT. If it shows "Account not authorized", you have the stock preloader. There's a couple threads here with some methods that may or may not work. Otherwise, ATM you'll quite literally have to pay for your mistake. Grab your wallet and your Windows VM. You'll need them. Be prepared to search for the least shady guy that can help you and have your usb passthrough (on the upstream hub) ready.
If (c) - i.e. you have the menu but no logo, this means you've got LK. Since the Redmi logo doesn't show up, it means something is not quite how lk likes it (and lk is very picky on this phone). If you can, you'll probably want to use fastboot and flash a known good image for whatever you changed. If not, use SPFT.
If (d) - i.e. you have the logo but the charging light doesn't turn off, this means LK didn't boot the linux kernel. Flash a different (working) kernel.
If (e) - the charging light turns off, but you have no boot animation, this means either the kernel panics before it can start Android or that Android failed to boot properly.
From here on, you can use /sys/fs/pstore/console-ramoops to diagnose the problem.
If you do get a boot animation or are close to it, you might also want to try using adb logcat (especially if you've turned on adb debugging, and your ROM can do it on boot).
3) /sys/fs/pstore/console-ramoops
You can access it on a normal boot on some roms (or mount it manually if you've got root), or it's usually mounted automatically on TWRP. This is the kernel log from the last boot and is theoretically stored in RAM (I have reasons to doubt that). Basically, it works like dmesg, but for the last boot.
While it is polluted by zealous MTK debugging info, scrolling through it can often show where the problem is. If you can figure it out yourself, great. If not, post it here, and I (or somebody else) might try to figure out what went wrong and put it on a list of known bootloop reasons and fixes below.
4) Recommendations on posting about bootloop problems:
I think it would help a lot specifying which step from above fails. Also, if the charging light turns off, please, please provide /sys/fs/pstore/console-ramoops. You can easily get it with adb pull from TWRP and it helps *a lot* in figuring out what went wrong.
Hope this info will help you guys getting your devices working again faster (and provide more accurate info when asking for help).
P.S.: Another reference on MTK boot, also around 5 years old.
Reserved for List of bootloop problems:
Reserved
i have:
dm-verity error
Android system on your device is corrupted.
Device will boot in 5s
Click to expand...
Click to collapse
can't boot to my mobile in past week
just i can see my device with "fastboot devices" but not found with adb devices
and in device manager "Android ADB Interface" it's not recognize ( yellow question marks).
also have "adb server version (41) doesn't match this client (39); killing"
hello..
So... /sys/fs/pstore/dmesg-ramoops .. is not there .... /pstore do not exist :-\
and /proc/last_kmsg.. neither :-(
i have.. lineage-14.1-20190213-nightly-asanti-signed install it....
He will be generating them elsewhere???
OP, please add the infamous soft brick symptoms in detail, this maybe help someone in the future.
It shows redmi logo, it can enter vol + menu with some messages (I forgot the message), and it can enter vol - (bootloader), and it will ask for authorization when hooked to SPFT. And also link to that telegram post for work around.
And also, this is crucial info I found. Anything prior global 12.0.7 can be dirty flashed to anything prior that (even A10 to A9). 12.0.7 onward, 12.0.7 is the lowest you can get for dirty flash. I don't know for clean flash. Maybe work, maybe not.
fla5 said:
i have:
can't boot to my mobile in past week
just i can see my device with "fastboot devices" but not found with adb devices
and in device manager "Android ADB Interface" it's not recognize ( yellow question marks).
also have "adb server version (41) doesn't match this client (39); killing"
Click to expand...
Click to collapse
What have you done prior brick? Do you do something like flashing global rom in a locked bootloader chinese flavor phone? If yes, do the unbrick with SPFT. If not, and you have unlocked your bootloader and access to fastboot, I think dirty flash will do the trick.
Sorry for being a lil' off-topic but I would love to ask how to prevent a bootloop after flashing back to stock recovery or/and boot. It happened twice - I used magisk+twrp, an update rolled out, I flashed the stock recovery for my official from (extracted from the official package) and ended up with a loop, did the mi authorized acc unbrick and it worked perfectly, now with the 12.5 rolling out I am preety sure i'll end with a loop again when I'll flash the stock boot or/and recovery.
luq90 said:
Sorry for being a lil' off-topic but I would love to ask how to prevent a bootloop after flashing back to stock recovery or/and boot. It happened twice - I used magisk+twrp, an update rolled out, I flashed the stock recovery for my official from (extracted from the official package) and ended up with a loop, did the mi authorized acc unbrick and it worked perfectly, now with the 12.5 rolling out I am preety sure i'll end with a loop again when I'll flash the stock boot or/and recovery.
Click to expand...
Click to collapse
you need to restore stock recovery and boot. and you can't install the update via updater nor twrp. install full rom via fastboot update or via mi flash (dirty flash is ok). but for 12.5 update, do it in twrp
from 12.0.7 onwards, downgrade without erasing data will lead to bootloop (just flash the correct build for remedy)
Thank you for your answer kekesed97.
Sorry, I made a small mistake. By saying that I used twrp means I had it installed not used for the flash. When the update came out, I thought that installing via ADB the stock recovery and boot will let me update the device like a completly unmodded model. Tried this Twice and always ended with a loop. Afterwards the only solution was updating via flashtools (it's bricked anyway so let's update manually hehe).
This is a guide how I flashed Android 10 to my Cubot Power.
Preparation:
HINT:
Make a Backup! You will definitely loose all your data on the phone due to several factory resets!
First make sure your Device can use treble and also which one you need with this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
(according to this post https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559)
note down:
Architecture: (Cubot Power: arm64)
System as Root: (Cubot Power: A-only)
then you will need fastboot and adb:
Windows:
https://forum.xda-developers.com/showthread.php?t=2588979
Linux:
Code:
sudo apt-get install android-tools-adb
Code:
sudo apt-get install android-tools-fastboot
Then you need twrp Recovery or something similar. Cubot Power is not supported by the official twrp project, but there is this unofficial version:
https://unofficialtwrp.com/twrp-3-2-3-recovery-cubot-power/
And you will probably need gapps:
https://opengapps.org/
For cubot power you will need "arm64" and "anrdoid 10" of course.
For the variant version I went with "nano" but you can probably choose what you like.
If you have a external sd card you want to copy the gapps, supersu and no-verty-opt-encrypt ZIP onto it.
Now download the android 10 treble image from:
https://github.com/phhusson/treble_experimentations/releases?after=v211
For the Cubot Power i went for the system-quack-arm64-aonly-vanilla.img.xz. But you should select the right one according to the treble app.
I went for vanilla because with gapps it did not seem to work.
Optional:
From this site:
https://romprovider.com/cubot-power-root-twrp/
Download SuperSu (https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip)
and no-verty-op-encrypt (https://romprovider.com/download-no-verity-opt-encrypt-version/)
this prevents bootloops.
In case something goes wrong have your stock rom and sp flash tool ready:
Cubot Power: http://forum.cubot.net/viewtopic.php?f=21&t=2419
Flashing
Make sure your phone is charged probably. Booting might take up to an hour. At least 70% is recommended.
Go to developer settings and enable usb -debugging and disable oem.
now type:
Code:
adb reboot bootloader
the device should now restart and boot into fastboot
now disable oem in fastboot and unlock flashing: (WARNING: this will factory reset your phone)
Code:
fastboot oem unlock
Code:
fastboot flashing unlock
now we want to "install" twrp:
Code:
fastboot flash recovery TWRP_cubot_power-030918.img
--(Optional) check if twrp is working:
Code:
fastboot reboot
and restart with the volume up button
in twrp go to mount and check if you can mount data. If not: https://appuals . com/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/.
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Then go to install and install no-verty-op-encrypt.
then got to reboot and select bootloader.
--
continue with flashing android 10:
unzip the xz file
Code:
fastboot flash system system-quack-arm64-aonly-vanilla.img
this might take a while.
Then reboot
Code:
fastboot reboot
now your phone should boot into android 10. This can take very long for me it took about 30 minutes. If it takes longer then one hour you can probably start troubleshooting.
Install google apps(playstore)
once it has booted you either can start the login process and enable usb debugging again and reboot into recovery:
Code:
adb reboot recovery
or turn it off and restart into twrp (power button and volume up).
In twrp again check if you can mount data (see the optional step).
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Install super su and gapps.
Now reboot to system.
Now again the phone will boot a very long time (up to a hour).
Conclusion:
For me it is pretty stable but sometimes the fingerprint sensor does not work or the sim card is not recognized. But a reboot fixes it (sometimes).
But rebooting always takes time. At least 5 minutes sometimes up to 30 minutes. Once the system is booted there are no feel-able performance issues.
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Click to expand...
Click to collapse
Probably it will work, but I can give you no guarantee for that.
Thank you!
Hi Johanno,
Thank you for this great tutorial! I think I already downloaded the treble check tool in March and I also found the github page, but I didn't find any experience on the net related to Cubot Power, so I didn't dare to upgrade.
Did you try later releases?
Should I go with latest release v222 or do you know about any change in v211 that prevents us from upgrading to a later version? ( your link in the tutorial shows only older versions: https://github.com/phhusson/treble_experimentations/releases?after=v211 )
Did you use windows or linux?
Did you experiment with V25 ROM?
https://www.cubot.net/platform/Support/detail/id/192/cid/23.html
Br,
taarzaan
I'm trying the latest release v222. I'm after the last reboot. It's not fast, but I would say it's less than 30 minutes. It should boot in 5 or 10 minutes.
Br,
taarzaan
Results of my experiments
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports legacy Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
regards
Al
Click to expand...
Click to collapse
hi
i just want to understand what is legacy version? and vndk27 ? i googled but few info
my phone say same info here
i ll post the results but if one could explain those 2 things
thank u in advance
taarzaan said:
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Click to expand...
Click to collapse
notes for the next experiment (we should open a proper ticket for phhusson):
"What does "can't be used" mean? Does the pone vibrate? Does screen lights on? If you go in Fingerprint settings, do you see the enrolled fingerprint? Can you enroll a second one? If you press your fingerprint sensor when you're on that screen, what happens?"
I've tried with both v211 and v222 - but I don't seem to get past boot screen.
After using fastboot flash (and I've also tried SP flash tool flash) the phone shows cubot boot screen (with a warning about "orange mode" not being trusted) and can boot into TWRP but when booting system it shows a black screen with white slowly flashing "android" for a long time. More than one hour. I lose faith and re-install stock each time.
Any ideas how to debug and see what's happening?
Any improvements to this? I am having a P20/cubot and had same problems. AOSP v222 does not boot but I tried lineage-17.1-20201215-UNOFFICIAL-treble_arm64_avS.img.xz from https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
Surprise. it works but a bit slowly. Due to large battery I am thinking of cubot power?
I have 2 questions:
1. Can you please try the lineage-17.1 rom?
2. BTW, did AOSP8 work OK in cubot power? (i like oreo more than android 10)
Thanks for your replies.
htorsten2020 said:
1. Can you please try the lineage-17.1 rom?
Click to expand...
Click to collapse
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
htorsten2020 said:
2. BTW, did AOSP8 work OK in cubot power?
Click to expand...
Click to collapse
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
taarzaan said:
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
Click to expand...
Click to collapse
Call/SMS/data stability. A lot of devices that came with oreo (vendor) have lots of issues with signal (mobile SIM) dropping after some hours. Thanks
taarzaan said:
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
Click to expand...
Click to collapse
Cubot Power ships with Android 8.1 (oreo). So I asked if you tried the old AOSP from phhusson (v32 - this is AOSP8 equivalent treble ROM). I found the AOSP from the same version (oreo as the device) is faster than installing newer ROM.
Hi guys, as you may have noticed I am not very active here ;-)
I actually went back to stock firmware after a few weeks because I couldn't get the phone working again. And since I want to use my smart phone and not tinker on it every few days I gave up. But now I am thinking about using Lineage os.
But first I need to back up everything and that's probably the thing that will hinder me the most.
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
kezyr said:
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
Click to expand...
Click to collapse
hi, how exactly did you install the lineageos 18.1 with the twrp 3.2.3? thank you in advance for your help
i just get boot loop on every rom i try on cubot power
I had the same problem and gave up
This will not work if your phone bricked after updating to Android 12. You should use the MSM in this case. This guide details downgrading to an earlier version of Android 11 FROM a newer Android 11. You have been warned.
This evening after updating my phone (installing to inactive slot + flashing with Magisk as I have done many times before), I restarted only to receive a Qualcomm CrashDump.
Unlike what I've read online, my one seemed to be a bit more severe. I could not boot into recovery mode (black screen; had to power phone off) and entering Fastboot did not fix the issue. After spending several hours reading through XDA, Stack Overflow, various other sites etc I finally managed to get it fixed. Not only that, but I kept ALL my data AND my root. It's like nothing ever happened.
The issues I faced:
- Mistakenly had USB debugging off (which cannot be enabled when your phone is soft bricked). This made using ADB for initial diagnostics virtually impossible
- Recovery mode showed a black screen; not accessible.
- Installing TWRP, only to find my device passcode (PIN) wasn't allowing me to decrypt my phone data so I could make a backup
- My phone was buggered
How I solved it: Given recovery mode was blank, I flashed TWRP to my recovery drive via Fastboot to bring it back. Because USB debugging was OFF and TWRP wasn't decrypting my data (meaning I couldn't back up any data or download the ROM to my internal storage without wiping it), I activated ADB Sideload within TWRP and then used this to downgrade my version of OxygenOS! After a reboot I received the Qualcomm error one more time, before it continued to boot into OxygenOS with all my data intact.
Your bootloader should already be unlocked. If it isn't, chances are you will be saying goodbye to your data
These steps may not work for everybody, but I wanted to give back what I learned from this, and it was rather unconventional and against the grain of what others have suggested. With that said, do so at your own risk.
This is a simple guide. I will explain the tools you will need and how to fix the issue. Anything beyond that (i.e. installing SDK platform tools) can be researched.
This is written assuming you are on Windows, although the steps are generally quite similar.
Tools Needed:
A computer to download and install:
- SDK Platform Tools/ADB (https://developer.android.com/studio/releases/platform-tools)
- TWRP for OnePlus 8 Pro (https://forum.xda-developers.com/t/...wrp-for-oneplus-8-8pro-official-beta.4341707/)
- OnePlus 8 Pro Drivers (You will need this installed if it isn't already for your phone to appear in SDK Platform Tools. You may need to disable driver signature enforcement on Windows 10)
- The version of OxygenOS you were running before the CrashDump occurred (https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/)
Steps to take - Initial Setup and Installation of TWRP:
1. Download everything above and then install SDK Platform Tools + OnePlus 8 Pro Drivers if you don't already have them.
2. Enter Fastboot mode on your phone and then connect it to the computer.
3. Ensure the TWRP .img file is in the same directory as your SDK Platform Tools install
4. Open up command prompt with SDK Platform Tools installed and type in
Code:
fastboot devices
Confirm your device ID appears along with "fastboot" beside it.
4. If the device is being recognised, we're ready to install TWRP. Note: Remember your Bootloader must be unlocked for the next steps. While in Fastboot mode, your phone will tell you if your bootloader is locked or unlocked. Now that we've confirmed it is unlocked, Type in:
Code:
fastboot flash recovery_a twrpname.img
followed by:
Code:
fastboot flash recovery_b twrpname.img
5. You can now boot into recovery mode! On your phone, use the volume keys to navigate and choose Recovery so you can enter TWRP
Downgrading to an older version:
When I installed TWRP, I was horrified to see that I couldn't decrypt my phone with my pin code. Apparently this is an ongoing problem with TWRP and the ability to decrypt your phone data varies between devices and builds of TWRP.
1. Now that you have entered TWRP, enter the "Advanced" settings and enable "ADB Sideload".
2. On the computer, type in
Code:
adb devices
. You should see your device appear.
3. Ensure the OxygenOS file is in the same directory as your SDK Platform Tools install
4. Type in
Code:
adb sideload updatename.zip
and let it flash to your phone.
And that's it! Reboot your phone. You may receive the Qualcomm error one last time, so kiss that sucker goodbye with a final reboot (I pressed power + volume up but then it continued to boot as normal; much to my surprise) and you should be good to go.
Hope this helps. This is my first ever guide, but my phone bricked itself this afternoon and it took me 3-4 hours of research to figure out what to do. This community played its role in helping me, and I'm sure someone out there will appreciate this information - definitely wanted to give back. I didn't see any information like this outside of wiping the phone entirely... I'm pretty stubborn and didn't want to do that.
This is definitely a "dirty flash", although given I couldn't even boot into the updated version, I would say a downgrade is definitely just fine in this instance.
I assume that you where using Android 11?
Because in the current situation with android 12 and hard bricking your phone with fastboot flashing this guide is potentially dangerous. As far as i know you should not flash twrp to android 12 right now.
Please correct me if i mixed things up here or if i am wrong. Its better to loose data and use MSM if you are concerned.
You might wanna include this guide in case someone needs to read it before doing anything.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anyway thanks for your effort here.
xtcislove said:
I assume that you where using Android 11?
Because in the current situation with android 12 and hard bricking your phone with fastboot flashing this guide is potentially dangerous. As far as i know you should not flash twrp to android 12 right now.
Please correct me if i mixed things up here or if i am wrong. Its better to loose data and use MSM if you are concerned.
You might wanna include this guide in case someone needs to read it before doing anything.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anyway thanks for your effort here.
Click to expand...
Click to collapse
Thank you and you're right. I've added this warning to the top of the post!