Database Develop

How to install GSI ROM on OnePlus n100. - OnePlus Nord N100 Guides, News, & Discussion

Good morning guys.

bentalebnordine said:
Recently I installed lineage os 11 gsi rom on my OnePlus n100 and I wanted to share this experience with you guys :
Click to expand...
Click to collapse
- First you need to download This mini sdk
one_plus_nord_sdk.zip
drive.google.com
It is necessary for the cmd commands to work
- you need also to install the drivers , just go to
Universal ADB Drivers
OnePlus-USB-Drivers.zip
drive.google.com
You need to install both drivers clockworkmod and one plus drivers.
- To unlock the bootloader of your oneplus device just connect it to a Windows computer with USB debugging on and run the following commands from the mini sdk folder that just downloaded
adb devices
Then check your device for confirmation. Then
adb reboot bootloader
Then run the command
fastboot oem unlock
A factory screen will pop-up asking for confirmation, you need to confirm using the volume buttons and the power button.
The phone will reboot into recovery and wipe the data. Please do not interrupt this process or the device will not boot anymore.
So just be patient until the phone finishes booting and set it up and turn the USB debugging on.
bentalebnordine said:
2: after that you need to boot your device on fastboot mode, simply by running the code
adb reboot bootloader
And run the command
fastboot --disable-verity flash vbmeta vbmeta.img
Then this command
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
Note that you need to flash both files only once, unless you returned to stock rom.
bentalebnordine said:
Then run the command
fastboot reboot fastboot
Then flash the system of your choice by visiting
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Note that the file downloaded would be in Xz format, so you need to extract it with 7zip or beanzip and put it on sdk folder.
The file downloaded must end with arm64_bvS.img. Xz and not with arm64_avS.img.xz (bvS not avS) or the phone will stuck on bootloop.
And the file extracted must not exceed 2.6 gB or you will get an error of resizing the system partition.
After flashing the system with the command
fastboot flash system <your system >.img
Run the command
fastboot -w
And finely the command
fastboot reboot
And good luck.
Click to expand...
Click to collapse
If you updated to Android 11 Oxygen OS 11 you need to switch slots by running the command
fastboot --set-active=a
Because android 11 were installed in the b slot.
If you have a problem booting into fastboot mode try extracting the mini sdk provided in the tmp folder on your desktop computer.
The working Android versions are 10,11,12. Now I am running Resurrection Remix ROM android 10 just amazing
NAMING
Some information you should know about knowing what type of gsi it is
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
Z = dynamic superuser included
-lite = for VNDK Lite vendors (also can help with broken camera even on normal VNDK vendors)
so in most common example "arm64_avZ" is ARM64 A-only vanilla with dynamic superuser
you can simply look to the attached text file.

I am unable to flash any of the .bvs.img gsi files on a Metropcs (11) phone -- BE2015 following the guide. Bootloader is unlocked.
Any help is appreciated.

joegib said:
I am unable to flash any of the .bvs.img gsi files on a Metropcs (11) phone -- BE2015 following the guide. Bootloader is unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
Me I have a BE2013 variant and I was able to flash it with gsi roms using just this guide. I should mention that I am not an expert on rom development.

If I am not mistaken, the BE2013 variant is the global factory unlocked. If so, then maybe these carrier devices will not work with your excellent guide. That being said, I was able to get the DSU to work fine -- AOSP 12.

If you're on the Metro firmware it's a bit tricky. You'll most likely have to still be running Android 10 but you can decrypt the data partition and mount system r/w. After you've accomplished that then it's a piece of cake. Follow this thread, I've been able to remount the system partition read/write on both my Google Pixel running Android 11 and Metro Firmware of OnePlus Nord n100. https://forum.xda-developers.com/t/...-superrw-featuring-makerw-read-write.4247311/

Is GSI for nord n100 updated?

VPH20 said:
Is GSI for nord n100 updated?
Click to expand...
Click to collapse
I'm running Project Arcana Android 12 GSI on my n100 without any issues. I've flashed serval different GSI ROMS but it's by far the best. There's a few things you need to know to successfully flash it but if the steps are followed exactly it's not a problem at all. Here are a few screenshots. It passes safety net basically out the gate with Magisk installed. You'll definitely have to flash the Global firmware to the Metro variant If you happen to be on that version. Luckily, if that's the case someone has already created a modified MSM flash tool that works without any other modifications.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks, the link please.

bentalebnordine said:
Thanks, the link please.
Click to expand...
Click to collapse
There's no verified instructions on this but I took the liberty to upload the necessary files to my Google drive that I used to successfully flash this GSI. First and foremost you'll need to revert back to the global stock firmware 10.5.5 using the msm tool. If you're on the the European firmware then I'm not sure if this will work for you or not and it definitely won't work on the Metropcs version but if you happen to be on the Metro version then you can flash the Global firmware to that device which is what I did. Once you're on stock 10.5.5 enable debugging and oem unlock in developer options and reboot to bootloader. If your bootloader isn't already unlocked enter the command fastboot flashing unlock_critical and use the volume keys to select unlock the bootloader. Your device will be wiped. Wait for the system to reboot then go back into developer options and enable debugging again. Once again reboot to the bootloader. Once there enter the command fastboot -w and wait for it to finish. Once it's complete enter fastboot reboot fastboot and wait to enter fastbootd mode. Use the vendor.img that's included in the zip file I have linked and enter fastboot flash vendor_a (name of vendor).img. Once it's complete enter fastboot reboot bootloader. Once you're back into the bootloader interface enter fastboot -w and wait for it to complete. Then with the twrp file I've supplied enter fastboot boot twrp10.img to boot to recovery (Don't flash only boot!!) When you enter recovery choose wipe, then format data and type yes. Reboot to the bootloader once again. Enter fastboot reboot fastboot and wait to enter fastbootd mode. Once there enter fastboot flash product_a product_gsi.img. Then enter fastboot erase system_a. Next enter fastboot resize-logical-partition system_a 4210000000. Once that's complete enter fastboot reboot bootloader. Once you're in the bootloader enter fastboot -w once again. Once complete boot back to twrp with fastboot boot twrp10.img. This is when you'll flash the GSI and it has to be loaded on your sdcard. Flash it to the system partition and reboot to the bootloader once it's complete. Your next move is important if you want it to boot. Again with the images I've supplied enter fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img then fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img. Now you can reboot to the system. For some reason twrp won't boot anymore once this GSI is flashed so I've also included the stock boot.img you can patch with Magisk and flash via fastboot to root and pass safety net.
Oneplus_files.zip
drive.google.com
https://xiaomemeindex.com/treble/Arcana/20220226/ProjectArcana_v402-arm64-bgS_20220226.img.xz

sdflowers32 said:
There's no verified instructions on this but I took the liberty to upload the necessary files to my Google drive that I used to successfully flash this GSI. First and foremost you'll need to revert back to the global stock firmware 10.5.5 using the msm tool. If you're on the the European firmware then I'm not sure if this will work for you or not and it definitely won't work on the Metropcs version but if you happen to be on the Metro version then you can flash the Global firmware to that device which is what I did. Once you're on stock 10.5.5 enable debugging and oem unlock in developer options and reboot to bootloader. If your bootloader isn't already unlocked enter the command fastboot flashing unlock_critical and use the volume keys to select unlock the bootloader. Your device will be wiped. Wait for the system to reboot then go back into developer options and enable debugging again. Once again reboot to the bootloader. Once there enter the command fastboot -w and wait for it to finish. Once it's complete enter fastboot reboot fastboot and wait to enter fastbootd mode. Use the vendor.img that's included in the zip file I have linked and enter fastboot flash vendor_a (name of vendor).img. Once it's complete enter fastboot reboot bootloader. Once you're back into the bootloader interface enter fastboot -w and wait for it to complete. Then with the twrp file I've supplied enter fastboot boot twrp10.img to boot to recovery (Don't flash only boot!!) When you enter recovery choose wipe, then format data and type yes. Reboot to the bootloader once again. Enter fastboot reboot fastboot and wait to enter fastbootd mode. Once there enter fastboot flash product_a product_gsi.img. Then enter fastboot erase system_a. Next enter fastboot resize-logical-partition system_a 4210000000. Once that's complete enter fastboot reboot bootloader. Once you're in the bootloader enter fastboot -w once again. Once complete boot back to twrp with fastboot boot twrp10.img. This is when you'll flash the GSI and it has to be loaded on your sdcard. Flash it to the system partition and reboot to the bootloader once it's complete. Your next move is important if you want it to boot. Again with the images I've supplied enter fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img then fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img. Now you can reboot to the system. For some reason twrp won't boot anymore once this GSI is flashed so I've also included the stock boot.img you can patch with Magisk and flash via fastboot to root and pass safety net.
Oneplus_files.zip
drive.google.com
https://xiaomemeindex.com/treble/Arcana/20220226/ProjectArcana_v402-arm64-bgS_20220226.img.xz
Click to expand...
Click to collapse
Thank you very much my friend for the help, I have the E2013 and it worked.

Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
I'd also like to mention that if you're into theming your device, the infamous dev kdragOn has developed an app called repainter that's quite amazing and works really well on this device and ROM. I'm in no way affiliated with him or the advertisement of his app but just making an honest recommendation

sdflowers32 said:
Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
Click to expand...
Click to collapse
Exactly.

bentalebnordine said:
Exactly.
Click to expand...
Click to collapse
I sent you a PM if that's okay please and thank you.

sdflowers32 said:
Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
I'd also like to mention that if you're into theming your device, the infamous dev kdragOn has developed an app called repainter that's quite amazing and works really well on this device and ROM. I'm in no way affiliated with him or the advertisement of his app but just making an honest recommendation
Click to expand...
Click to collapse
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol

Markus214 said:
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol
Click to expand...
Click to collapse
Go to this page you will find extra details about how to resize system partition and install larger system files.
https://forum.xda-developers.com/conversations/gsi-roms.14701453/#convMessage-15038845

Okay I just want to say thank you first and foremost to @bentalebnordine and @sdflowers32 because without your both helpful and informative guides I would have taken much longer lol! I can get a guide going completely. With the above guide that sdflowers posted make sure you follow this to a T or you won't boot trust me. Also the GSI images that work best for our device must be the following
system-arm64-ab-img.xz and they will work with no issues I'll put up a cleaned up guide as well to hopefully help others but again this is all only possible with the help of you two first and foremost so thank you!

Markus214 said:
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol
Click to expand...
Click to collapse
DOT (Droid on Time) is another GSI that works beautifully on this device but it's Android 11. I personally haven't tried any 10 GSI'S. If you want to update to 11 through stock firmware I already have a DOT super.img I repacked that I'm pretty sure can be flashed without issues with the Android 11 twrp for this device and I'm certain can be flashed via fastbootd mode. Other than project arcana it's the only one I've been impressed with and I've flashed 7 or 8. At least 3 of them I could never get to completely boot after trying every trick of the trade. Arcana is by far the best but DOT runs a tight race. If interested let me know and I'll upload the super.img. I packed it myself so if I ever get bored and just want to go back it would be a much less painless process to flash and I've tested it and it works perfectly.

sdflowers32 said:
DOT (Droid on Time) is another GSI that works beautifully on this device but it's Android 11. I personally haven't tried any 10 GSI'S. If you want to update to 11 through stock firmware I already have a DOT super.img I repacked that I'm pretty sure can be flashed without issues with the Android 11 twrp for this device and I'm certain can be flashed via fastbootd mode. Other than project arcana it's the only one I've been impressed with and I've flashed 7 or 8. At least 3 of them I could never get to completely boot after trying every trick of the trade. Arcana is by far the best but DOT runs a tight race. If interested let me know and I'll upload the super.img. I packed it myself so if I ever get bored and just want to go back it would be a much less painless process to flash and I've tested it and it works perfectly.
Click to expand...
Click to collapse
Thank you very much that would be great! I just downloaded DOT to try it out. I used it before on my 7T and it's great. I just am stubborn I'll say where I like Android 10 the most and 11 not bad but 12 I just don't like the interface and magisk 24 especially for what I do with the phones. I ideally would love to be able to use lineage but when it came time to flash Gapps I kept getting storage error even with resizing. I just want to again say seriously thank you so much without your guide I'd still be screwed

Instructions for flashing DOT GSI
(Start by flashing to stock 10.5.5 with the MSM tool for the device and follow the previous instructions to unlock the bootloader but only to this point)
I decided to edit this because it's been so long since I've removed encryption on this device I completely left out the steps to do so which are imperative. It's much easier to remove encryption on Android 10 than 11 with this device but as far as I know this is the sure fire way to flash an Android 11 GSI on this device. Maybe it can be flashed from 10 but I can't guarantee it as I can with this so here is the revised instructions.
1. Use the MSM tool to revert back to stock and unlock the bootloader
2. Upgrade OTA as far as you can up until version 11.0.4 (Most likely you'll have to use the file I've included in the attachment and perform a local upgrade by placing the zip file in your internal storage to get on this version) Remember this is only for the global firmware but it can be cross flashed with a modded MSM tool.
3. Once you're on 11.0.4 you'll need to format an SD card to exfat which can be done easily with windows because you're going to have to place the super.img on it to be flashed in TWRP. Android supports exfat but for reasons beyond my understanding when you purchase an SD card for Android it comes formatted as fat32 which has a 4 gig limitation.
4. Unzip the 11.0.4 super.img and load it on the SD card along with Magisk.apk. You can either rename the extension from Magisk.apk to Magisk.zip and keep just the one file on your card or copy it and place them both on but nevertheless you'll need the zip file to flash in TWRP after flashing the super partition. Use the TWRP11.img provided in this devices thread and have it placed in your platform-tools folder on PC. Reboot to the bootloader and enter fastboot boot twrp11.img (Or whatever the name of the image happens to be). Once you're in recovery choose wipe, format data and enter yes. Go back and choose install image then select the super11.0.4.img and flash to the super partition. Go back and flash Magisk.zip.
5. Now boot to the bootloader and with the volume keys enter stock recovery.
6. Wipe Data, Cache and System and reboot. I usually reboot back to the bootloader then boot TWRP again just to make sure I can mount all partitions assuring that the device is decrypted.
7. Now all you have to do is place the DOT_SUPER.img on your SD just as you previously did, wipe and format data, then flash it to the super partition just as you did with the stock 11.0.4 super. The boot image is provided as well but I wouldn't advise uninstalling Magisk. Upgrade if you like but it may not boot if you flash the stock boot.img
DOT Files

Related

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some china OP5 user got it from OnePlus staff, and uploaded it to china cloud drive.
[Driver]
Mega:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=889764386195921378
[Oxygen Version Download]
After you use this tool, your OP5 will be restore into stock Oxygen OS.
Mega 1:
https://mega.nz/#!MPBXkJjK!O2uDD7Xx04KPT_cx9coMHnGtaeSK06t9gwNpUR4KDXE
Mega 2:
https://mega.nz/#!gjRFmB4C!-HN00YSS2tUy5ZQTbJbzwEmZ8VU_iv5lLaTlbXin7Ec
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=745425885120760474
[Hydrogen Version Download]
After you use this tool, your OP5 will be restore into stock Hydrogen OS.
Source :
http://www.oneplusbbs.com/thread-3587805-1-1.html
Baidu pan:
http://pan.baidu.com/s/1qYz7hZu
pwd: 0fb4
Mega (corrupted):
https://mega.nz/#!kyJ1XJ7D!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Mega 2:
https://mega.nz/#!RmQnQKTB!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Google Drive:
https://drive.google.com/file/d/0B9vxnq7dlG4pYVJGaGZOYWNuZzA/view?usp=sharing
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?w=files&flid=204903
[Tutorial]
The steps is the same as 1+3T.
Ref:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Great ! I always prefer a fastboot / edl flash.
Sent from my ONEPLUS A5000 using Tapatalk

Isn't it Oxygen OS?

gonsa said:
Isn't it Oxygen OS?
Click to expand...
Click to collapse
Yes,it isn't.
However you can easily install Oxygen OS by yourself.:laugh:
Ref:
https://forum.xda-developers.com/oneplus-5/how-to/guide-installing-oxygenos-chinese-t3647409

Someone should be able to tweak this to fetch OOS files instead of H2OS. Both the firmwares are the same except userdata
Sent from my ONEPLUS A5000 using Tapatalk

Someone should upload this to androidfilehost so there are other places to download incase the original is taken down.

file in mega is corrupted.
please upload in any uploading site

@snowwolf725 ,since I already "came back" from fastboot-ed github/OOS/MSM8998 build, I like to clarify few tips:
-Unbrick via Qualcomm QFIL tools were well documented here and there (Oneplus 1/2/3/3T) ; but Qualcomm never granted free distribution of QualcommQDLoader9008 DRV or QFIL, AND your WindowsPC has to be disabled with integrity checks or antivirus. So it should be considered as the last extreme ultimate rescue.
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.

@oF2pks if I get your process correctly, for a clean flash, Flash all needs to be done 3 times with the stock recovery followed by OEM lock and post that the last step is to fastboot erase boot/system/user data/cache followed by adb sideload of the stock firmware?
Sent from my ONEPLUS A5000 using Tapatalk

On this subject, we need a return to stock guide for the OP5 :good: Fine writeup oF2pks! :highfive:

oF2pks said:
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.
Click to expand...
Click to collapse
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!

TwinAdk said:
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!
Click to expand...
Click to collapse
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.

File in mega is corrupt please re upload

hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu

Sir link is not visible

Link is not visible

hsareminia said:
file in mega is corrupted.
please upload in any uploading site
Click to expand...
Click to collapse
sanjeevattre said:
File in mega is corrupt please re upload
Click to expand...
Click to collapse
hsareminia said:
hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu
Click to expand...
Click to collapse
I add new mirror links and dirver download link.
Driver:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ

jasonwsc said:
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
I am aware that the process above is HIGHLY complicated - and is often not necessary.
At the time of my post, my phone was in a state where I had been doing crazy things with it (decrypted data, multiple custom ROMs and TWRP versions, including multiboot variants and the chinese one. On top of that I had flashed the am-verity and force decryption patch zip). This is as such not unusual, but my attempts to return to stock had failed (stock ROM zip failed to flash, stock recovery were wierd as well).
Therefore, when the quick layout for COMPLETE STOCK were outlined above, I grabbed them and did the process, while documenting it for future reference for others. Also, I choose to include the oem unlock and lock part - though I am fully and completely aware that it's unnecessary to 99% of the readers, after all this is One Plus phones
I had not been able to find any other sources of the steps outlined, though they may be simple, so I took all the steps how ever overkill they might be, because then there would be a documented process
The steps above would recover a One Plus 5 from a state where only adb works, pretty serious condition indeed....
I'm staying on OOS based custom ROMs as long as the blobs for the camera is undisclosed by One Plus. I haven't had time to reply to this sooner, have a great weekend, and @asonwsc, I agree with you :highfive:
Kind Regards
TwinAdk

jasonwsc said:
...If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.... flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )

oF2pks said:
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )
Click to expand...
Click to collapse
But if the device is considered certified on the play store, then it passed SafetyNet without an issue.
Correct me if I'm wrong, but shouldn't SafetyNet pass under the following conditions?
1. Locked bootloader with no root (stock)
2. Unlocked bootloader with Magisk root.
Is it actually possible for a locked bootloader and unrooted phone to fail SafetyNet? You can't root without the unlocking the bootloader, so how would that trigger SafetyNet?

Custom ROM Flashing Guide​So after tons and tons of test builds, the good ol' devs managed to get everything working and gave us a super stable ROMs (many more to follow soon ). However, since our device supports A/B scheme, a newbie can find it rather difficult to get used to flashing ROMs, kernels and even GApps! So I decided to prepare a simple guide which should help you get used to flashing ROMs and lots of other stuff.
Disclaimer: If you don't know what bootloader is and/or don't know anything about Custom ROMs, I strongly recommend you to not try this on your own and rather watch some videos about them and the advantages/disadvantages associated with them.
Notes:
1. Prerequisites:
Unlocked Bootloader
ADB, Fastboot and Device Drivers (Google them)
Use Command Prompt instead of PowerShell for ease of use.
STEPS:
1. Boot into Fastboot mode (power+vol up) and run:
Code:
fastboot -w
Note your active slot from here. Mine is 'b' as can be seen from the pic attached. Yours can be 'a' or 'b'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Download vbmeta from View attachment q_vbmeta.img and then do this:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Now run the following command in your fastboot using pc(obviously):
If your active slot was 'a':
Code:
fastboot set_active b
If your active slot was 'b':
Code:
fastboot set_active a
4. Either restart bootloader directly from your phone (using volume and power keys) or do this:
Code:
fastboot reboot bootloader
Your fastboot screen should now look like the following. Notice the change in the active slot (if yours was 'a' in the previous step, it should be 'b' now).
5. It's TWRP time!!
Download TWRP (both boot.img and permanent zip) by @ThE_MarD from here.
Flash TWRP using:
Code:
fastboot flash boot boot.img
Make sure the name of your downloaded twrp image file is boot.img! If not, either rename the file or change the fastboot code to that filename.img
6. Now reboot to recovery using power and vol keys on your phone. You should see TWRP booting up now. If not, you've messed up somewhere, do the entire process again (correctly ).
7. Click on WIPE > ADVANCED WIPE, and choose System, Dalvik (Cache) and Data.
8. Check ROM notes and see if it comes with inbuilt vendor or not. If it does, you can skip this step. If it doesn't, ask for the required vendor from the maintainer.
Note: All A12 ROMs so far have come with inbuilt vendor.
9. Now, if you unlocked your bootloader via official apk (provided by Asus), then flash ABL.zip in TWRP/SHRP. However, if you unlocked unofficially, you can skip this step.
10. Time to flash the ROM of your choice. ! Click on INSTALL and then choose the ROM you want to flash. SWIPE>>>>>>>>>
11. Flash TWRP permanently using this: Permanent TWRP.
12. Flash the same vendor you flashed on the other slot. In other words, repeat Step 8 (no need to flash abl again) (skip flashing vendor if you skipped step 8).
Note (optional): Mount vendor before performing this step just to be safe.
13. Reboot to Recovery (IMPORTANT).
14. After rebooting, twrp would have automatically switched to your active slot (the one you had in Step 1)(check this in reboot section of twrp).
15. Now you can flash GApps, Magisk from the active slot anytime. This step varies from ROM to ROM as some ROMs have GApps pre-installed.
Note: Access TWRP by pressing power+vol down button simultaneously.
16. REBOOT>SYSTEM and you're done! Enjoy the ROM.
Credit Section:
1. Jackeagle -- TWRP and ROM Developer
2. Rohan Purohit -- ROM Developer
3. Sandeep.Sethi -- Kernel Developer
4. Marc Bourgoin -- TWRP and Device Developer
5. All the testers.
Thank you and I hope this guide benefits the community.

OSS Vendor Flashing Guide​Note: This guide is deprecated now, kindly refer to the guide above for latest ROM builds.
So after tons and tons of test builds, the good ol' devs managed to get everything working and gave us a super stable ROMs (many more to follow soon ). However, since our device supports A/B scheme, a newbie can find it rather difficult to get used to flashing ROMs, kernels and even GApps! So I decided to prepare a simple guide which should help you get used to flashing ROMs and lots of other stuff.
Disclaimer: If you don't know what bootloader is and/or don't know anything about Custom ROMs, I strongly recommend you to not try this on your own and rather watch some videos about them and the advantages/disadvantages associated with them.
Notes:
1. Prerequisites:
Unlocked Bootloader
ADB, Fastboot and Device Drivers (Google them)
Use Command Prompt instead of PowerShell for ease of use.
STEPS:
1. Boot into Fastboot mode (power+vol up) and run:
Code:
fastboot -w
Note your active slot from here. Mine is 'b' as can be seen from the pic attached. Yours can be 'a' or 'b'.
View attachment 4785824
2. Download vbmeta from View attachment 4961371 and then do this:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Now run the following command in your fastboot using pc(obviously):
If your active slot was 'a':
Code:
fastboot set_active b
If your active slot was 'b':
Code:
fastboot set_active a
4. Either restart bootloader directly from your phone (using volume and power keys) or do this:
Code:
fastboot reboot bootloader
Your fastboot screen should now look like the following. Notice the change in the active slot (if yours was 'a' in the previous step, it should be 'b' now).
View attachment 4785825
5. It's TWRP time!!
Download TWRP (both boot.img and permanent zip) by Jackeagle from here.
Flash TWRP using:
Code:
fastboot flash boot boot.img
Make sure the name of your downloaded twrp image file is boot.img! If not, either rename the file or change the fastboot code to that filename.img
6. Now reboot to recovery using power and vol keys on your phone. You should see TWRP booting up now. If not, you've messed up somewhere, do the entire process again (correctly ).
7. Click on WIPE > ADVANCED WIPE, and choose System, Dalvik (Cache) and Data.
8. Flash OSS Vendor. You can flash via fastboot by downloading and extracting OSS_Fastboot.7z. Navigate cmd to OSS folder and run:
Code:
fastboot flash vendor vendor.img
Alternatively, you can simply flash OSS_Recovery.zip in TWRP/SHRP.
9. Now, if you unlocked your bootloader via official apk (provided by Asus), then flash ABL.zip in TWRP/SHRP. However, if you unlocked unofficially, you can skip this step.
10. Now, flash permanent twrp from here, change to the inactive slot and reboot to recovery again. Flash the same vendor you flashed on the other slot. In other words, repeat Step 8 (no need to flash abl again).
11. Time to flash the ROM of your choice. ! Click on INSTALL and then choose the ROM you want to flash. SWIPE>>>>>>>>>
12. Flash TWRP permanently using this: Permanent TWRP. Flash this simply in twrp.
Note (optional): Mount vendor before performing this step just to be safe.
13. Reboot to Recovery (IMPORTANT)
14. After rebooting, twrp would have automatically switched to your active slot (the one you had in Step 1)(check this in reboot section of twrp).
15. Now you can flash GApps, Magisk from the active slot anytime. This step varies from ROM to ROM as some ROMs have GApps pre-installed.
Note: Access TWRP by pressing power+vol down button simultaneously.
16. REBOOT>SYSTEM and you're done! Enjoy the ROM.
Credit Section:
1. Jackeagle -- TWRP and ROM Developer
2. Rohan Purohit -- ROM Developer
3. Sandeep.Sethi -- Kernel Developer
4. All the testers.
Thank you and I hope this guide benefits the community.

What is vbmeta zip doing?

If I'm on .58 flashing just vendor.img of .72 before all the steps helps?

bordi21 said:
What is vbmeta zip doing?
Click to expand...
Click to collapse
It disables the verified boot, so that you can flash gsi and custom roms. Without it, nothing other than zenui will boot.
jayd4321 said:
If I'm on .58 flashing just vendor.img of .72 before all the steps helps?
Click to expand...
Click to collapse
Yep flash vendor image and stock boot image of 72, and you'll be good to go!

I have performed step 8 and now I am in twrp. How to perform Step 9. Please suggest
Edit- Thanks did it by copying the files to my otg and flashing through twrp.

Thanks a lot for your comprehensive guide, got to unlock the bootloader and flash twrp as per the guide.
However, I have a problem booting the ROM; the ROM installs perfectly well and I can reboot into recovery but can't get past the "ASUS" screen upon actually trying to boot the ROM.
Am I missing something? I followed everything down precisely and I honestly don't know what am I messing up.
A little help would be appreciated.

viveknaudiyal said:
I have performed step 8 and now I am in twrp. How to perform Step 9. Please suggest
Edit- Thanks did it by copying the files to my otg and flashing through twrp.
Click to expand...
Click to collapse
Glad you were able to succeed
Xadus said:
Thanks a lot for your comprehensive guide, got to unlock the bootloader and flash twrp as per the guide.
However, I have a problem booting the ROM; the ROM installs perfectly well and I can reboot into recovery but can't get past the "ASUS" screen upon actually trying to boot the ROM.
Am I missing something? I followed everything down precisely and I honestly don't know what am I messing up.
A little help would be appreciated.
Click to expand...
Click to collapse
Okay! Can you provide your bootloader version and slots on which you have stock rom and twrp?

AryanAA said:
Glad you were able to succeed
Okay! Can you provide your bootloader version and slots on which you have stock rom and twrp?
Click to expand...
Click to collapse
my bootloader version was the latest one .72 and my stock ROM was on slot b, which I switched to a for flashing twrp and then booted into twrp and switched back to b to clear data, system and cache; flashed the ROM in the same slot and then flashed the permanent twrp as well.
Following all this i could reeboot back into twrp but couldn't get the ROM to boot.

Xadus said:
my bootloader version was the latest one .72 and my stock ROM was on slot b, which I switched to a for flashing twrp and then booted into twrp and switched back to b to clear data, system and cache; flashed the ROM in the same slot and then flashed the permanent twrp as well.
Following all this i could reeboot back into twrp but couldn't get the ROM to boot.
Click to expand...
Click to collapse
After wiping system,data,cache, you had to go back to slot A and then reboot to recovery and after that flash the rom (read point 10 of post).

@AryanAA can you please extend this guide on how to install magisk

AryanAA said:
After wiping system,data,cache, you had to go back to slot A and then reboot to recovery and after that flash the rom (read point 10 of post).
Click to expand...
Click to collapse
I tried that as well.
I must have repeated the process numerous times, i tired flashing it on the slot where my twrp is and i tired flashing it on the slot where was stock was as well in the next try; both incidences gave bootloop.

HELP
Encryption Unsuccessful!
Tried everything multiple times like mentioned in OP.

I was able to flash elementalX using this guide. Thanks for detailed info,i found this guide more understandable than the 1 we have in how to flash gsi thread.

milindmavadia said:
Encryption Unsuccessful!
Tried everything multiple times like mentioned in OP.
Click to expand...
Click to collapse
1. Flash DFE on both slots.
2. Go to fastboot and do fastboot -w on your rom slot

Xadus said:
I tried that as well.
I must have repeated the process numerous times, i tired flashing it on the slot where my twrp is and i tired flashing it on the slot where was stock was as well in the next try; both incidences gave bootloop.
Click to expand...
Click to collapse
Interesting. I think you should restart the whole process and flash rom only on inactive slot rather than both the slots!

viveknaudiyal said:
@AryanAA can you please extend this guide on how to install magisk
Click to expand...
Click to collapse
Process of flashing magisk is exactly same as gapps. Infact you can install gapps and magisk in one go.

AryanAA said:
Interesting. I think you should restart the whole process and flash rom only on inactive slot rather than both the slots!
Click to expand...
Click to collapse
Maybe i will give try in the future, for now i flashed the stock as i was frustrated by the whole thing.
Thanks a lot for your help though.

Fastboot -w ..it's says "waiting for device" can any one help?

Aruss5 said:
Fastboot -w ..it's says "waiting for device" can any one help?
Click to expand...
Click to collapse
You have to first install adb and fastboot drivers to your computer.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!

View attachment 5273685View attachment 5273649View attachment 5273651View attachment 5273653View attachment 5273655
View attachment 5273657View attachment 5273659View attachment 5273661View attachment 5273669View attachment 5273671View attachment 5273673View attachment 5273675View attachment 5273677View attachment 5273679

Agh, plain AOSP. I miss Havoc already.

Testing it out and everything thing seems smooth. I did find one minor issue for the people that like their temperatures in imperial units. You can change the lockscreen temp to imperial and it displays an F for farenheit but the temperature value is still Cecius.

Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?

jonshmorg said:
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
Click to expand...
Click to collapse
You will need to go back to rooted stock, and copy your apn_conf.xml file from product/etc to your sd card, amd replace it on arrow (or another rom)

Quantumstate said:
Agh, plain AOSP. I miss Havoc already.
Click to expand...
Click to collapse
Closest thing to havoc is crDroid ATM mate, it's on the forums here

This ROM is marked as only being compatible with sofiar, but I can confirm that everything seems to work on my sofia device.

Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Edit: It turns out I was using the wrong build of TWRP. Use the one linked in the original post, not the one elsewhere on the forums.

RaspberryPiBen said:
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Click to expand...
Click to collapse
While in twrp, if you select reboot to fastboot, that is fastboot d

Beetle84 said:
While in twrp, if you select reboot to fastboot, that is fastboot d
Click to expand...
Click to collapse
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.

RaspberryPiBen said:
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
Click to expand...
Click to collapse
Using the twrp linked here or another?

Beetle84 said:
Using the twrp linked here or another?
Click to expand...
Click to collapse
I just noticed that. I was using the TWRP build from https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ because I assumed that was what the link was for. Thank you.

Apps aren't able to see registered fingerprints. Fingerprint auth is grayed out and the apps complain "register fingerprints on the device settings".
I have tried:
Deleting and redoing fingerprints (just one and multiple) with and without rebooting.
Confirmed the fingerprints work for screen unlock and gestures.
Re-installed 08-04-21 Vanilla build with full format, issue persists.
Anything I missed to check? I do not have my phone rooted, so cannot see system logs using the logging app.
Using sofiar (moto g8 power). Tested the apps themselves on my second phone klte (Samsung S5 Lineageos 16) and fingerprints work just fine there.

Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?

jdude520 said:
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
Click to expand...
Click to collapse
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.

ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?

Carl-Robert said:
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
Click to expand...
Click to collapse
I'm not the person with the problem, but thank you for the explanation. I installed my ROMs before Android 11 came out for this phone and I was planning to test the stock Android 11 ROM, so this information will be very useful.

jdude520 said:
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Click to expand...
Click to collapse
I believe you have to roll back to Android 10. Custom Android 11 ROMs may work, but you can't install custom ROMs so that doesn't help.

actually it is rescuing me to android 11 no matter what i do

I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!

This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
yedashare said:
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
Click to expand...
Click to collapse

Savio Dantes said:
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
Click to expand...
Click to collapse
Thank you Savio, but this is my main issue, I cannot enter fastbootD.
Whether using the tool "fastboot enhance" or using the command line. I cannot reach FastboodD.
When I try to reach this using the tool, it's looping with no error log.
And when I try from CMS:
C:\Users\me\Downloads\from dumper> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

It also still sounds like your recovery.img and/r boot.img still may be corrupted.
this needs to MATCH in BOTH slots A & B
Try this:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713

Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery

yedashare said:
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Click to expand...
Click to collapse
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers

u can try to fix sms mms problem using this thread
xiaomi 12/moto edge x30(or any device with sm8450) sms＆ims error · Issue #2246 · phhusson/treble_experimentations
Now gsi is able to boot on devices with sm8450.But sms doesn't work.And ims settings shows "not supported" .I tried to install q-ims.apk or ims.apk from the stock rom.Still ,ims does work at all. A...
github.com
@yedashare
@dladz maybe we can share it groups ?

beatbreakee said:
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
Click to expand...
Click to collapse
Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
I thought that as long as I reach the recovery mode, I can still fix it.
If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
Many thanks for your efforts.

Damn. Nice to know Lineage works well on this phone with extensive tweaking. GSI's can be pretty unstable from what I've seen, missing cell reception and the like.
Yeah, flashing that image killed the phone. I've seen some people recover by flipping their boot slot to the other one and forcing the phone to boot the stock boot there. But if you've flashed to both slots, you're most likely SOL and need a MSM flash. In which case, you could try flashing the complete stock boot image for your OOS version you were on before moving to GSI to both slots as sort of a last resort, but even then I've only seen minimal success.

Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use MSM.
I understand that MSM is no longer available.
Any other direction how I can just fix the booting process?
And this is another error I received which gets closer to the source of the problem:
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer

I’m assuming Adb does not work?

why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.

Arealhooman said:
I’m assuming Adb does not work?
Click to expand...
Click to collapse
Yes right, adb doesn't work, only fastboot is still alive

TuLy2702 said:
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Click to expand...
Click to collapse
Thanks for taking time to answer.
Could you be more specific?

I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.

yedashare said:
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
Click to expand...
Click to collapse
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS

yedashare said:
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
Click to expand...
Click to collapse
you make me laugh

yedashare said:
EoS
Click to expand...
Click to collapse
Damn. I think what happened is you lost your persist.img when initially flashing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.

Prant said:
Damn. I think what happened is you lost your persist.img when initially flaahing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Click to expand...
Click to collapse
It's okay to spend a little money. It's very risky to do it yourself

Did you managed to get fingerprint working on gsi ?

Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation

WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.

starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot

WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible

kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing

I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?

stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218

stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.

lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.

kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.

stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.

stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?

Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.

mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.

No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).

mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully

The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?

mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.