Related
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
niaboc79 said:
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
Click to expand...
Click to collapse
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Miustone said:
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Click to expand...
Click to collapse
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations ?
niaboc79 said:
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations
Click to expand...
Click to collapse
Nice to know! Fingerprints are the worst on Xperia 1 and 5. Hope it will be better on the Mark 2...
Just made an Overlay over Night for GSIs, after experimenting around with them again. Finally got some essential Features working like AoD. Still missing is VoLTE and wifi calling which is a common Android 10 GSI bug i think. Double Touch to work does also not work on My Xperia 5 (Dunno why).
Thread; https://forum.xda-developers.com/xp...eriment-mars-vendor-overlay-gsi-roms-t4128449
which AOSP Vendor Package from Sony can be use on xperia 1 ii
I was wondering, is this device Xperia 1ii is able to recieved GSI 13?
I have the previous model Xperia 1 running GSI 13 really well, and was wondering if this device is similar to do the same?
Kind of a dumb question, because I would assume yes?... But would like to know just the same, as I saw a bargain price for a new Xperia 1ii, and hoping it to be similar.
Had an 11.2.3.3 Global rooted via Magisk OP9 Pro that I wanted to update via OTA to 11.2.4.4, which was offered via system update. I used Magisk to restore images before update, did the update, and then went back to install to inactive slot. Rebooted and it was still on 11.2.3.3 so I tried again. Upon trying again, my phone got to a Qualcomm debug/error mode. I experienced this before when on a different boot slot for some other diagnosis of another issue in the past so I switched boot slots.
The other boot slot is stuck in fastboot mode I come to find so I check what it shows if I reverted back to the other boot slot, which was the Qualcomm error. Now instead of a Qualcomm error, it shows language options, one of which is English, and then gives me "boot reason", "wipe data and cache" and "advanced". I believe this is the OnePlus recovery menu, which I have not needed to use before and in the past, used TWRP on other devices.
Can't I just reflash a whole system image for 11.2.4.4 (it'd have to be the European one right now since Global isn't available) via fastboot and it should be fixed, albeit unrooted and I can just re-root? I'd like to try this, but there's no "flash-all.bat" and I don't know the proper flash order for the Euro images within payload.bin as there's no xml file (I looked up a guide for directions on how to flash without flash-all.bat that I have used on other devices). Oh, and I tried to fastboot a known good boot.img and on one of the slots, it works fine, but still wont boot. The other gives error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". I'm stumped.
Wondering if this has been experienced by anyone else before. Wiping my device is the last resort and shall be avoided at all costs after how much I have configured it to my liking.
I saw the following on another guide:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
Followed this guide here after extracting the Europe full system image via Payload-dumper and it now boots somewhat, but after it looks like it's loading into OOS and boot is complete, I get a black screen instead of the lock screen. I get charging sounds when plugged into the computer, but just a black screen.
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Wondering if this has to do with the Europe 11.2.4.4 on my Global device. Going to try reverting to 11.2.2.2 Global full image now.
Geez, good luck
vibrantliker said:
Geez, good luck
Click to expand...
Click to collapse
Just tried flashing the older 11.2.2.2 images one at a time and now it's stuck in recovery...
The closest I can get it to full booting is with 11.2.4.4 Europe full image and I get a black screen only, after it boots up with the OnePlus logo. When plugged in, I get a charging sound every 10-20 seconds or so. Too bad there's no 11.2.4.4 full image for Global or I'd try that.
Also just tried fastboot boot 11.2.4.4_global_boot.img on this 11.2.4.4 Europe image and still no go. Boots and makes sounds, but black screen still.
Have you tried the MSM tool?
hadesflames said:
Have you tried the MSM tool?
Click to expand...
Click to collapse
I was considering it, but don't want to lose any data. Next step is to contact OnePlus technical support during normal hours and see if they can work with me to resolve this one. I believe I read here on XDA that people have contacted them and usually are able to resolve the issue. Trying to avoid clearing data as the device is fine as it boots, but I think the Europe image is conflicting somewhere and not allowing me into the system since it boots all the way to the lock screen, but I don't see a lock screen, just a blank screen with sounds after boot seemingly working, along with charging sounds (albeit, sounding every 10-20s like its periodically charging).
This is so odd though because I did everything as I should've and update seemingly occurred, but system version still showed 11.2.3.3. So I go back to system update and it said there was an issue and to restart again. Did that two times with magisk revert image and restore to inactive and it then stopped booting.
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
djsubterrain said:
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
Click to expand...
Click to collapse
Does stock recovery support ADB? At 8 pro you needed modified one..
pyry666 said:
Does stock recovery support ADB? At 8 pro you needed modified one..
Click to expand...
Click to collapse
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
Click to expand...
Click to collapse
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
pyry666 said:
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
Click to expand...
Click to collapse
Yeah I'm working at the moment so not on my own PC, can't really test it out
djsubterrain said:
Yeah I'm working at the moment so not on my own PC, can't really test it out
Click to expand...
Click to collapse
Just tried. ADB with stock recovery is "unauthorized"..So modified is needed if one wants to use stock recovery with adb
djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
Click to expand...
Click to collapse
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
bulletbling said:
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
Click to expand...
Click to collapse
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
djsubterrain said:
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
Click to expand...
Click to collapse
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
Are there actual hw differences between AA and BA?
bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
There's a pinned post at the top of the forum with all the available latest roms. Not sure they've added Global yet tho. Best going there or Oxygen Updater (when the phone is working) than the download page tbh, OnePlus ALWAYS takes ages to add builds there
pyry666 said:
Are there actual hw differences between AA and BA?
Click to expand...
Click to collapse
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
bulletbling said:
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
Click to expand...
Click to collapse
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
pyry666 said:
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
Click to expand...
Click to collapse
I wish I could go without my phone for weeks until they post the latest firmware to see if that even works, but I can't so I guess I'll have to use the msm tool and wipe all of my internal storage of documents, including taxes, and various files and downloads I've amassed over the past half decade. This really sucks. All because of a simple OTA that should've never caused this. They really should prevent this from being possible with the OTA update tool built-in to their system.
Hey guys,
I have Lineage OS installed on my Poco F3. I have (at least not really) never experienced any issues with Lineage so far. Everything has worked really smoothly up until I updated the latest version of Lineage OS. The update took ages for some reason and now my Lineage is incredibly unstable.
It doesn't show any of my contacts anymore, play services and the app store crash all the time, giving me notifications non stop.
I tried manually updating the firmware as I figured something went wrong (obviously) but my device does not talk to my computer over a usb. I went to the settings and those showed me that the file transfer option is unclicked, I can't seem to change it either.. Really annoying.
Does anyone know what to do? I don't want to factory reset because of my authenticator. Shall I just wait for the next update and hope it's fixed?
Kind regards, pls halp!!
You could try going into Fastboot mode (https://www.hardreset.info/devices/xiaomi/xiaomi-poco-f3/fastboot-mode/), boot TWRP (fastboot boot TWRP.img) and then change boot partition (e.g. from a to b).
You get the twrp image here:
Xiaomi Poco F3
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I recommend using minimal ADB and Fastboot if you're using windows:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Make sure you don't accidentally flash the twrp.img but use the "fastboot boot twrp.img" command!
Edit: just realized you can change active boot slot with just fastboot, i.e. no need to flash twrp):
Just boot into Fastboot, find out active boot partition:
fastboot getvar current-slot
And then change accordingly, i.e. if above command returns "a" choose "b" and vice versa wit this command: fastboot set_active b
This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro.
This message was removed on OOS 12 which was one great thing by OP other than the other broken parts.
So this guide is for OOS 13 not 12 as the message was removed on 12.
But OnePlus brought the message back on OOS 13.
IMPORTANT:
*I am not responsible for bricked devices, damage to your device*
I am here to post my method for anyone who is interested.
The methods have been tested
Prerequisities:
You need a unlocked bootloader
YOU NEED TO HAVE THE STOCK RECOVERY INSTALLED
If you're on a custom ROM that'll be the ROM recovery
This is XDA thread and abl.img is only for the OnePlus 8 Pro, but this method has worked for 8 series devices.
You need to be on OOS 13 and have your bootloader unlocked.
The abl.img doesn't rely on the region so it can be used on any OP8 Pro
The abl.img can be extracted using payload dumper, but download the full zip version.
I have added abl.img from OOS 13 F.10 as this is the newest abl.img that has the message removed and is from @bowow
It is recommended to backup your data before modifying anything on your system
Follow one method and stick to that method
Each method is different where one is for Stock OOS 13 and the other is for OOS 13 based Custom ROMs
Method:
Download the abl.img
Copy and paste the abl.img to platform-tools
If u don't have platform-tools, download the .zip file from download links and extract it
For Stock OOS 13
This method was tested and is from @MeHigh.G
This is for on Stock OOS 13 users
Reboot to bootloader
Type " fastboot devices " to check if your device is connected
Type " fastboot reboot fastboot "
Once booted into Fastbootd Mode, type " fastboot devices " to check if your device is connected
Then type " fastboot flash --slot=all abl abl_filename.img "
Now reboot device and done
For OOS 13 based Custom ROMs
This method was tested by me and it does work
This is for OOS 13 based ROM users
Reboot to recovery
Enter advanced
Enter fastboot
The recovery should now show fastbootd
Type " fastboot devices " to check if your device is connected
Type " fastboot flash --slot=all abl abl_filename.img
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
MSMDownloadTool for OP8Pro Here
Bowow's OnePlus Firmware Updates abl section Here
OrangeFox Recovery for OP8+OP8 Pro ext4 erofs
OFox Install instructions Here
OrangeFox Community Telegram
Credits:
@HELLBOY017 For the method and using abl.img to remove the bootloader unlocked message
@MeHigh.G For his method on flashing abl.img on stock OOS 13
@bowow For this F.10 abl.img for OP8 and 8 Pro
reserved
Updates
21/11/22 - Released the XDA thread as a guide to remove the ugly "Your device has been unlocked" message for the OP8 Pro
Not sure if this method does work, but I have contacted ROM developers and they say this is the way...
I'm currently not on OOS 13 based ROM, so I can't try and hopefully this does work
21/12/22 - It has been a month and after checking with devs + testers the method does work!
I have tested the method myself
I have updated the method as there's new steps you need like flashing abl.img in both slots
But the method does work on OOS 13 based ROMS! The message can be removed!
22/12/22 - I have found the method that works on Stock OOS 13 thanks to @MeHigh.G
Stock OOS 13 users should be able to remove the bootloader unlocked message
Added new OOS 13 F.10 abl.img file and removed OOS 12 C36 abl.img due to F.10 being newer to ensure users have a newer bootloader
Credited Bowow for giving the F.10 abl.img file for OP8/8 Pro
5/1/23 - Updated methods to flash abl.img in both slots easily instead of flashing abl.img in one slot
Changed "fastboot flash abl abl.img" to " fastboot flash --slot=all abl abl_filename.img " which will flash abl.img in both slots.
For custom ROM method, you will no longer need to reboot and switch slots with the new command
Nice!
Hello!
Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?
Thank you
Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?
gregpilot said:
Hello!
Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?
Thank you
Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?
Click to expand...
Click to collapse
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.
Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.
EDIT: i found this topic here
Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.
ShadoV90 said:
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.
Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.
EDIT: i found this topic here
Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.
Click to expand...
Click to collapse
That's for the OP9 Pro not the OP8 Pro...
I only learned about this from the dev @HELLBOY017 and it worked for him. He never stated u needed a data wipe.
So I did check that it was working otherwise I would never post something that wouldn't work and wasn't tested.
And I did say.... *I am not responsible for bricked devices, damage to your device* I am here to post my method for anyone who is interested.
I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.
It was from EU OOS 12 C36 full zip
We'll see how it goes as this is new for 8 Pro users and hopefully it does work
Thanks for the reminder of the missing info to include
Extreme_Ninja2099 said:
That's for the OP9 Pro not 8 Pro...
I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.
It was from EU OOS 12 C36 full zip
Click to expand...
Click to collapse
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.
Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.
We don't even know possible bad outcome. That's all.
And to be clear...
I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.
ShadoV90 said:
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.
Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.
We don't even know possible bad outcome. That's all.
And to be clear...
I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.
Click to expand...
Click to collapse
Never considered it as an attack, just posting to clarify where I got this info and everything from.
I only found out about this yesterday from Hellboy017 and it worked for him.
I would recommend this only for users on OOS 13 just to be safe
If something does go wrong, follow the link by @ShadoV90
Do a factory reset or use MSMDownload Tool
thanks for the tip, i'll check it out asap
Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')
we might have to use the --force argument in the fastboot command
try at your own risk
Neil_Armstrong_ said:
thanks for the tip, i'll check it out asap
Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')
we might have to use the --force argument in the fastboot command
try at your own risk
Click to expand...
Click to collapse
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
ShadoV90 said:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
Click to expand...
Click to collapse
the flashing unlock_critical output is the fastboot help, i guess it's not working
I will try again saturday on Linux to see if it helps
ShadoV90 said:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
Click to expand...
Click to collapse
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!
But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.
I talk from experience! And BTW just did that a minute ago.
MeHigh.G said:
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!
But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.
I talk from experience! And BTW just did that a minute ago.
Click to expand...
Click to collapse
Nice feedback, can you share what custom recovery you use on OOS 13 ?
so this work or not?
Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
There's no custom recovery currently for OOS 13... Only for custom ROMs
Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
I use oFox or the one provided with Flamingo OS or Pixel Blaster
so the steps are :
1- extracting the abl file from the rom we are running using paylaod.bin.
2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.
3- booting from there to fastboot
4- flashing the abl file.
right .?
STALKER18 said:
so the steps are :
1- extracting the abl file from the rom we are running using paylaod.bin.
2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.
3- booting from there to fastboot
4- flashing the abl file.
right .?
Click to expand...
Click to collapse
I've already extracted it for the 8 pro... Up to u
For step 4 it's fastboot flash abl abl.img
i'm unable to unlock bootloader says command not supported in default implementation.
IN2021 One plus 8 pro.
I have a LE 2125, didn't like what OOs12 did ( no Android Auto, worse battery life), so I replaced the ROM with Lineage OS 18.1. THAT broke even more things, especially banking apps, ( and still no Android Auto) due to it needing to be unlocked ( but not rooted). Tried factory reset and flashing the OEM recovery. Now I have that in slot b and the Lineage recovery in slot A. Now the phone cannot go into EDL, by pushing the volume buttons I can bring it into Lineage recovery, OR the stock Recovery if I go to Fastboot. I am so confused with how to install TWRP to regain control of my phone.
All the instructions for installing Magisk, or TWRP ( twrp used to be easy to install, either flashing or from the OS) or using MSM seem to be written by programmers talking to other programmers, ie too much knowledge is assumed when giving steps or making references to other things.
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
When I connect my phone to the USB cable ( stock Oneplus red one connected to USB2.0 port) it brings up the Oneplus logo for about 10 seconds, then blinks, then after 10 more seconds goes blank, then after 5 seconds the pattern repeats.
I am not exactly a noob at this, I installed many OSes on my previous Oneplus ( One, X, 3T, 6T) phones, but none with this slot a/b thing. Admittedly my last OS replacement was on my 6T so it has been a few years, and my how things have changed!
coolvan170 said:
I have a LE 2125, didn't like what OOs12 did ( no Android Auto, worse battery life), so I replaced the ROM with Lineage OS 18.1. THAT broke even more things, especially banking apps, ( and still no Android Auto) due to it needing to be unlocked ( but not rooted). Tried factory reset and flashing the OEM recovery. Now I have that in slot b and the Lineage recovery in slot A. Now the phone cannot go into EDL, by pushing the volume buttons I can bring it into Lineage recovery, OR the stock Recovery if I go to Fastboot. I am so confused with how to install TWRP to regain control of my phone.
All the instructions for installing Magisk, or TWRP ( twrp used to be easy to install, either flashing or from the OS) or using MSM seem to be written by programmers talking to other programs, ie too much knowledge is assumed when giving steps or making reverences to other things.
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
When I connect my phone to the USB cable ( stock Oneplus red one connected to USB2.0 port) it brings up the Oneplus logo for about 10 seconds, then blinks, then after 10 more seconds goes blank, then after 5 seconds the pattern repeats.
I am not exactly a noob at this, I installed many OSes on my previous Oneplus ( One, X, 3T, 6T) phones, but none with this slot a/b thing. Admittedly my last OS replacement was on my 6T so it has been a few years, and my how things have changed!
Click to expand...
Click to collapse
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
TheGhost1951 said:
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
Click to expand...
Click to collapse
That is one of my problems – I cannot find the image file for my device. All the links I followed lead me to source code which I must compile myself. The TWRP installer 3.6.2_11-0-lemonadep zip RAMdisk-twrp.cpio, magisk boot file which is only 300 K bites and a meta-info folder. But it is a zip file not an image file.
Post in thread '[RECOVERY] [3.7.0-12.1] [UNOFFICIAL] TWRP with A12/A13 encryption support' https://forum.xda-developers.com/t/...-a13-encryption-support.4523857/post-87793789
Thus is the latest twrp(unofficial, but decrypts and all functions work) by @der_akinator. U must flash vendor_boot.img 1st, then BOOT boot.img. Then once u get in twrp u can go to advanced and install "latest twrp" permantly if you please. However after that u are suppose to go back to fastboot and flash your stock vendor_boot, for your system to work. However, since you're isn't and you are going to use twrp to install rom/OS I think you can skip last part(stock vendor_boot flashing)
TheGhost1951 said:
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
Click to expand...
Click to collapse
cant get fastboot to work, but ADB sideload does.
coolvan170 said:
cant get fastboot to work, but ADB sideload does.
Click to expand...
Click to collapse
Then for the sake of giving yourself all options possible, I would work on getting fastboot working first.
TheGhost1951 said:
Then for the sake of giving yourself all options possible, I would work on getting fastboot working first.
Click to expand...
Click to collapse
Found the QPST tool so I will try with that.
Shooter7889 said:
Post in thread '[RECOVERY] [3.7.0-12.1] [UNOFFICIAL] TWRP with A12/A13 encryption support' https://forum.xda-developers.com/t/...-a13-encryption-support.4523857/post-87793789
Thus is the latest twrp(unofficial, but decrypts and all functions work) by @der_akinator. U must flash vendor_boot.img 1st, then BOOT boot.img. Then once u get in twrp u can go to advanced and install "latest twrp" permantly if you please. However after that u are suppose to go back to fastboot and flash your stock vendor_boot, for your system to work. However, since you're isn't and you are going to use twrp to install rom/OS I think you can skip last part(stock vendor_boot flashing)
Click to expand...
Click to collapse
I found the QPST tool I will try working with that.
coolvan170 said:
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
Click to expand...
Click to collapse
The PC running MSM should be in "test mode" with driver signing disabled. Then MSM will see your phone.
Skynet30 said:
The PC running MSM should be in "test mode" with driver signing disabled. Then MSM will see your phone.
Click to expand...
Click to collapse
Also you can try to side load TWRP img then use TWRP to boot into EDL mode...
The problem with the new A/B Slot solution is (2) things need to match in order to initiate a correct OS boot:
A Stock or (Working) Custom recovery.img
A Stock boot.img
This need to exist in both slots (A & B)
When in a Bootloop, your device is responding to a mismatch of at least one of these, causing corruption and a looping response.
I've made the same mistake and accidentally soft-bricked (what you're currently experiencing) on both my Oneplus 8 Pro and Oneplus 10 Pro
e.g.
Once in Fastboot mode, try flashing a clean boot and recovery to BOTH slots like this :
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Try following my guide here to get things on track via Fastboot Mode:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713
TheGhost1951 said:
Also you can try to side load TWRP img then use TWRP to boot into EDL mode...
Click to expand...
Click to collapse
Also, be sure you have the correct Qualcomm drivers typically packaged with an MSMTool+Stock ROM
Fwiw. Android auto has worked fine on a11, a12, and a13. Wired and wireless. Multiple head units. Wired is picky with cable however. Bluetooth and wifi both need to be on for wireless.