Moderator Information
This project is not under active development, take precautions when you are installing it.
Click to expand...
Click to collapse
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 8 Pro in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 8 Pro
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Can you please do this for OnePlus 8 (non pro)
This is awesome, my OP8P is not even here yet and development is moving forward nicely.
Tx mauronofrio, donation sent!
---------- Post added at 09:44 AM ---------- Previous post was at 09:39 AM ----------
As I understand this, this is for the European version so far and not the US version, correct?
Poloasis said:
This is awesome, my OP8P is not even here yet and development is moving forward nicely.
Tx mauronofrio, donation sent!
---------- Post added at 09:44 AM ---------- Previous post was at 09:39 AM ----------
As I understand this, this is for the European version so far and not the US version, correct?
Click to expand...
Click to collapse
desiresiscool said:
Can you please do this for OnePlus 8 (non pro)
Click to expand...
Click to collapse
For now yes, I need of the others normal roms to make the fastboot roms and for sure this will come also for OnePlus 8
Hey! Nice to see you again. I just got my 8 pro today. Nice work!! Is there a telegram group I can join to help with development?
mauronofrio said:
For now yes, I need of the others normal roms to make the fastboot roms and for sure this will come also for OnePlus 8
Click to expand...
Click to collapse
@mauronofrio , you might want to head to my mirrors thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233 https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315/
Some_Random_Username said:
@mauronofrio , you might want to head to my mirrors thread https://forum.xda-developers.com/oneplus-8/how-to/oneplus-8-repo-oxygen-os-builds-t4084233 https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315/
Click to expand...
Click to collapse
Thanks, i'm downloading the others roms just now
This might be a stupid question, but will twrp recovery ever be available to flash custom ROMs down the road, or is it just not possible on the OP8Pro?
Gordietm said:
This might be a stupid question, but will twrp recovery ever be available to flash custom ROMs down the road, or is it just not possible on the OP8Pro?
Click to expand...
Click to collapse
I think that will be needed a bit of time
If I substituted a magisk patched boot.img in the fastboot rom and flashed it via flash-all command, will it flash the stock rom and root it at the same time?
Sent from my OnePlus 8 Pro using XDA Labs
Where is this flash all.bat people are using?
I got it. It's in the file you download.
So I'm really screwed here. I flashed a substartum theme that caused my phone to boot into fastboot mode. I cant delete the theme witha an adb command because its not recognizing my device.
Now I fastbooted the stock rom with flash all.bat and Im getting failed error commands. I just realized that Ive already updated to 10.0.55 and its not working. What do I do?
Can you flash it with the MSM tool?
Gordietm said:
So I'm really screwed here. I flashed a substartum theme that caused my phone to boot into fastboot mode. I cant delete the theme witha an adb command because its not recognizing my device.
Now I fastbooted the stock rom with flash all.bat and Im getting failed error commands. I just realized that Ive already updated to 10.0.55 and its not working. What do I do?
Click to expand...
Click to collapse
Try
fastboot -w
On fastboot
---------- Post added at 01:38 PM ---------- Previous post was at 01:32 PM ----------
cultofluna said:
Try
fastboot -w
On fastboot
Click to expand...
Click to collapse
Also, on flash all bat
Ignore, invalid sparse error....
Guitarfreak26 said:
Can you flash it with the MSM tool?
Click to expand...
Click to collapse
Have you fixed the FP issue?.
cultofluna said:
Try
fastboot -w
On fastboot
---------- Post added at 01:38 PM ---------- Previous post was at 01:32 PM ----------
Also, on flash all bat
Ignore, invalid sparse error....
Click to expand...
Click to collapse
Hey thanks. Everything finally worked and back to normal. I'm staying away from certain substratum themes from now on until we have twrp. ?
Sent from my OnePlus 8 Pro using XDA Labs
Gordietm said:
Hey thanks. Everything finally worked and back to normal. I'm staying away from certain substratum themes from now on until we have twrp. ?
Click to expand...
Click to collapse
TWRP probably not coming on dynamic partitions
( Oneplus 7Tpro , Pixel4/ 4xl still don't have a fully working twrp)
cultofluna said:
TWRP probably not coming on dynamic partitions
( Oneplus 7Tpro , Pixel4/ 4xl still don't have a fully working twrp)
Click to expand...
Click to collapse
Supposedly there are some working on 7's, and a private 8 one in China that can't be put on XDA.
cultofluna said:
TWRP probably not coming on dynamic partitions
( Oneplus 7Tpro , Pixel4/ 4xl still don't have a fully working twrp)
Click to expand...
Click to collapse
Wrong.
Its not ready yet but they posted update on Twitter this month that they made a lot of progress on Pixel 4 now it can decrypt data and install. So it will be coming to Android 10 only devices once they made changes.
Nekromantik said:
Wrong.
Its not ready yet but they posted update on Twitter this month that they made a lot of progress on Pixel 4 now it can decrypt data and install. So it will be coming to Android 10 only devices once they made changes.
Click to expand...
Click to collapse
Decrypt data only without pin/password/pattern and rom, magisk, gapps flashing wasn't tested yet
Related
Upon booting the 2nd RC build of Dirty Unicorns, I am faced with the dialog saying that the vendor image is out of date,
I have downloaded one from developer.google.com, I just need to know what I have to do to get it onto my Pixel.
fastboot flash vendor vendor.img
Which leads to the next question (or two):
Using a Windows computer, how do I compile the img file? (I could only find the binary at google, a tgz archive containing an .sh file)
Is there a fastboot flashable image available?
pTeronaut said:
Which leads to the next question (or two):
Using a Windows computer, how do I compile the img file? (I could only find the binary at google, a tgz archive containing an .sh file)
Is there a fastboot flashable image available?
Click to expand...
Click to collapse
If you download the full image from Google there is a second compressed file in the full image that has a vendor.img file. Also the just below the download link on the forum for the du ROM there is a link for the vendor image .
The third ROM release from DU does not require vendor image flash if you're already on the latest image.
Otherwise, reboot to bootloader.
Open your command prompt.
Use the command "fastboot flash vendor vendor.img".
I go the extra mile and do two commands.
"fastboot flash vendor_a vendor.img"
"fastboot flash vendor_b vendor.img"
Though it's probably not necessary.
As mentioned above, download the full Google image.
https://developers.google.com/android/images
Then extract it, and keep extracting it again and again until you find the vendor.img.
You can use TWRP to flash the vendor image. No need for fastboot.
spaceman860 said:
You can use TWRP to flash the vendor image. No need for fastboot.
Click to expand...
Click to collapse
Does that work with twrp on pixel?
toknitup420 said:
Does that work with twrp on pixel?
Click to expand...
Click to collapse
Yes
spaceman860 said:
Yes
Click to expand...
Click to collapse
Sweet deal. I didn't know that was working on pixel yet. Good looks for the info.
Flashing
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Vestell said:
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Click to expand...
Click to collapse
Did you unzip the file twice
There another zip inside the folder. Extract that and open your command prompt in there
mac796 said:
Did you unzip the file twice
There another zip inside the folder. Extract that and open your command prompt in there
Click to expand...
Click to collapse
I exstract it to a ADB folder and I opened the command prop there.
Vestell said:
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Click to expand...
Click to collapse
Hello... Is your bootloader unlocked?
Good luck...
5.1 said:
Hello... Is your bootloader unlocked?
Good luck...
Click to expand...
Click to collapse
Hello,yes its unlocked, I flashed Revolution recovery for nougat, I tryed to do /vendor mount -f in terminal and it says:
Permission Denied,If I flash extracted system.img with fastboot flash system system.img it says OKAY and when its done, I boot up my p9 lite but it wont boot to the system.
Vestell said:
Hello,yes its unlocked, I flashed Revolution recovery for nougat, I tryed to do /vendor mount -f in terminal and it says:
Permission Denied,If I flash extracted system.img with fastboot flash system system.img it says OKAY and when its done, I boot up my p9 lite but it wont boot to the system.
Click to expand...
Click to collapse
Hello I never heard of revolution recovery...
I know about TWRP. You can install vendor.img with TWRP by the way. :good:
Also, maybe you should post in the P9 lite forum... This is the Google Pixel XL forum...
Good luck...
5.1 said:
Hello... Is your bootloader unlocked?
Good luck...
Click to expand...
Click to collapse
5.1 said:
Hello I never heard of revolution recovery...
I know about TWRP. You can install vendor.img with TWRP by the way. :good:
Also, maybe you should post in the P9 lite forum... This is the Google Pixel XL forum...
Good luck...
Click to expand...
Click to collapse
Its a TWRP for p9 lite,if I try to install it I can choose between Recovery and boot, and srry that Im posting in google pixel XL forum,but im just looking for solutions that I could try, btw there is no P9 lite forum
Vestell said:
Its a TWRP for p9 lite,if I try to install it I can choose between Recovery and boot, and srry that Im posting in google pixel XL forum,but im just looking for solutions that I could try, btw there is no P9 lite forum
Click to expand...
Click to collapse
Sorry... Since i don't own the device, it's unlikely I can help you. Maybe flashing g P9 lite requires a different process, I don't know. Again, i guess you won't find much help in this forum.
Good luck...
where do i get the vendor image to install in twrp? the only thing that showed up under, "install image" was twrp. Do I need to install a factory vendor image from google?
ken2736 said:
where do i get the vendor image to install in twrp? the only thing that showed up under, "install image" was twrp. Do I need to install a factory vendor image from google?
Click to expand...
Click to collapse
U need extracted vendor img from stock Google zip then flash image in twrp. Yes click image button. Then click on vendor then flash.
hey everyone,
I recently purchased a used Nexus 5x that is running fine so far. my only problem is i get the message "internal problem, contact manufacturer" after every boot.
the phone is running android 7.0 (NDR90S) and the seller told me he trie to root and flash custom firmware but somehow the boot loader always locked itself. Now its not possible to perform an OTA update to 8.0 (get it offered all the time).
According to the developer setting the Bootloader is unlocked. I read that it should be fine to flash the vendor.image. Is this correct so far?
FLASHING METHOD OF ROMS IN MI A3 thanks to EITIFO (a.k.a. Typhus) for guide
(For Flashing System images, ZIP method will be updated soon)
Enable USB Debugging
Your bootloader must be unlocked
Open a command prompt (or power shell ) window
Type:
adb reboot boot loader
Now you will see fastboot icon on your phone
"Make sure you are in the directory where the ROM images are"
Enter these commands in fastboot
fastboot set_active a
fastboot erase boot
fastboot erase system
fastboot -w (All data will be removed)
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot twrp-3.3.1-15-laurel_sprout-mauronofrio.img
fastboot reboot
(Hold vol+ to force boot into recovery)
Now we're on TWRP... Copy all of the following files to your phone Internal Memory (your phone should appear on your PC since TWRP has MTP enabled by default):
After booting , install these ZIPs twrp-3.3.1-15-laurel_sprout-mauronofrio-installer.zip; Magisk-v19.3.zip;
patch_no_fde.zip;
Flash boot.img as Image to Boot partition
Install twrp-3.3.1-15-laurel_sprout-mauronofrio-installer.zip
Install Magisk-v19.3.zip Install patch_no_fde.zip - [ ]
Reboot to system.
Congratulations ?? You have installed a custom ROM on your phone
Hit thanks
Reserved
You forgot about actually flashing the rom itself. Everything is there but the rom flash
Some GSI tested? Thanks
garylawwd said:
You forgot about actually flashing the rom itself. Everything is there but the rom flash
Click to expand...
Click to collapse
Look carefully I mentioned to flash system image .
I will update soon for ZIPs flashing
RaghavTeck said:
Look carefully I mentioned to flash system image .
I will update soon for ZIPs flashing
Click to expand...
Click to collapse
Yup I see that now my bad
Spardantex said:
Some GSI tested? Thanks
Click to expand...
Click to collapse
Will do . Currently on Stock
I cant find the btd.img file. Can some help me
Can i shift 1 custom rom to other custom rom by using twrp (PE android 10 to miui 11 ) or flash stock and then custom ??
A$h!$h said:
Can i shift 1 custom rom to other custom rom by using twrp (PE android 10 to miui 11 ) or flash stock and then custom ??
Click to expand...
Click to collapse
Nope . You need to flash stock and then install miui
Mowb said:
I cant find the btd.img file. Can some help me
Click to expand...
Click to collapse
Not needed for installation. Just skip it
Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
RMX1971_fastboot CN
Code:
ro.build.date=Fri Aug 23 00:23:36 CST 2019
ro.xxversion=V0.5
ro.build.soft.majorversion=
ro.build.soft.version=A.06
ro.product.brand.sub=realme
ro.product.brand=realme
ro.product.model=RMX1971
ro.build.product=RMX1971
ro.product.name=RMX1971
ro.vendor.product.oem=RMX1971
ro.product.device=RMX1971CN
ro.vendor.product.device.oem=RMX1971CN
ro.build.fingerprint=realme/RMX1971/RMX1971CN:9/PKQ1.190101.001/1561347112:user/release-keys
ro.bootimage.build.fingerprint=realme/RMX1971/RMX1971CN:9/PKQ1.190101.001/1561347112:user/release-keys
ro.build.version.base_os=realme/RMX1971/RMX1971CN:9/PKQ1.190101.001/1557221182:user/release-keys
ro.build.version.google_patch=20190705
ro.build.version.security_patch=2019-07-05
ro.build.version.sdk=28
ro.treble.enabled=true
persist.sys.build.gms_cn=true
ro.build.version.ota=RMX1971_11.A.06_0060_201908230002
ro.build.display.id=RMX1971_11_A.06
ro.build.display.full_id=RMX1971_11_A.06_190823
ro.build.kernel.id=4.9.112
persist.version.confidential=false
ro.build.version.opporom=V6.0
RMX1971EX_11_OTA_0110_fastboot IN
Code:
ro.build.date=Mon Oct 21 09:45:02 CST 2019
ro.xxversion=V0.5
ro.build.soft.majorversion=
ro.build.soft.version=A.11
ro.product.brand.sub=realme
ro.product.brand=realme
ro.product.model=RMX1971
ro.build.product=RMX1971
ro.vendor.product.oem=RMX1971
ro.vendor.product.device.oem=RMX1971
ro.build.version.google_patch=20191005
ro.build.version.security_patch=2019-10-05
ro.build.version.sdk=28
ro.treble.enabled=true
ro.build.version.ota=RMX1971EX_11.A.11_0110_201910210916
ro.build.display.id=RMX1971EX_11_A.11
ro.build.display.full_id=RMX1971_11_A.11_191021
ro.build.kernel.id=4.9.112
persist.version.confidential=false
ro.build.version.opporom=V6.0
Fastboot Commands :
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
Latest Fastboot :
Download
Fastboot Images For Other Realme Devices :
Github
Guide to extract Fastboot images from ozip :
Credits :
jamflux
Regards,
acervenky
FAQs
I'm getting the "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." Error, what should I do now?
Flash the vbmeta using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm getting the "Invalid sparse file format at header magic" Error, does that mean that the images are corrupt?
No! Just ignore the error, if you get the "Finished" message it means that the image has been flashed without any issues.
Can I cross-flash images?(CN -> IN & vice versa)
Some users have reported that the images can't be flashed due to different partition sizes, proceed at your own risk!
Regards,
acervenky
Enter Fasboot mode ?
How to Enter Fasboot mode ? i try on Recovery Mode (Power Button + Vol DOWN) but cant detect my Device
faisalxp said:
How to Enter Fasboot mode ? i try on Recovery Mode (Power Button + Vol DOWN) but cant detect my Device
Click to expand...
Click to collapse
Fastboot doesn't work without bl unlock!
Regards,
acervenky
acervenky said:
Fastboot doesn't work without bl unlock!
Regards,
acervenky
Click to expand...
Click to collapse
i thinks so....now all people just wait for new in-deep-test.apk to unlock bl.
Here is Google Drive mirror including indian varient and ota.
How do I flash these:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
From a 7z file? I can't even decompress the 7z archive to see what's in it. 7z says its not a decomressable archive.
uaevuon said:
Here is Google Drive mirror including indian varient and ota.
Click to expand...
Click to collapse
Link added to OP, thanks!
greenys' said:
How do I flash these:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
From a 7z file? I can't even decompress the 7z archive to see what's in it. 7z says its not a decomressable archive.
Click to expand...
Click to collapse
Extract the file first then use commands!
The file is working fine for me.
Regards,
acervenky
acervenky said:
Link added to OP, thanks!
Extract the file first then use commands!
The file is working fine for me.
Regards,
acervenky
Click to expand...
Click to collapse
Indeed it does. I had to redownload the 7z file because seems it was corrupted presumably because of weak Internet connection. Now it works and I could successfully flash the files via adb. Now my phone works with stock rom. However as soon as I modify boot or recovery the system reacts to it and won't boot showing a message saying the boot/recovery was modified thus I should take my device to service. Anyway, the 7z file was a solution to my bootloader stuck problem.
what the easiest way to flash realme q to realme 5 pro firmware?
greenys' said:
Indeed it does. I had to redownload the 7z file because seems it was corrupted presumably because of weak Internet connection. Now it works and I could successfully flash the files via adb. Now my phone works with stock rom. However as soon as I modify boot or recovery the system reacts to it and won't boot showing a message saying the boot/recovery was modified thus I should take my device to service. Anyway, the 7z file was a solution to my bootloader stuck problem.
Click to expand...
Click to collapse
Have you tried flashing modified vbmeta?
sun9111 said:
what the easiest way to flash realme q to realme 5 pro firmware?
Click to expand...
Click to collapse
Don't cross-flash roms until someone confirms that it is safe!
Regards,
acervenky
acervenky said:
Have you tried flashing modified vbmeta?
Click to expand...
Click to collapse
Not yet. I can try and report back on monday.
greenys' said:
Indeed it does. I had to redownload the 7z file because seems it was corrupted presumably because of weak Internet connection. Now it works and I could successfully flash the files via adb. Now my phone works with stock rom. However as soon as I modify boot or recovery the system reacts to it and won't boot showing a message saying the boot/recovery was modified thus I should take my device to service. Anyway, the 7z file was a solution to my bootloader stuck problem.
Click to expand...
Click to collapse
hey i cant boot have you installed back the os?
---------- Post added at 04:50 PM ---------- Previous post was at 04:25 PM ----------
acervenky said:
Link added to OP, thanks!
Extract the file first then use commands!
The file is working fine for me.
Regards,
acervenky
Click to expand...
Click to collapse
hello im stuck in bootloop with this method can u help me?
anunimuus said:
hey i cant boot have you installed back the os?
---------- Post added at 04:50 PM ---------- Previous post was at 04:25 PM ----------
hello im stuck in bootloop with this method can u help me?
Click to expand...
Click to collapse
Yes I can help, please explain your situation in detail!
Regards,
acervenky
@anunimuus Yes. I can help. I flashed stock realme_q fastboot rom files via fastboot after extracting the 7z file. That's all.
OP Updated with RMX1971EX_11_A.11 for Realme 5 Pro!
Regards,
acervenky
Need stock recovery
Hi, i need stock recovery for installing ozip file please.
Tegarcs142 said:
Hi, i need stock recovery for installing ozip file please.
Click to expand...
Click to collapse
Flash the boot image, it contains stock recovery!
Regards,
acervenky
Help
acervenky said:
Flash the boot image, it contains stock recovery!
Regards,
acervenky
Click to expand...
Click to collapse
i did flash to stock but after boots in few seconds turn off and on couple time until reboot itself
can i downgrage from A.09 to this version on my realme Q?
Here's what I've learned far about the E6:
Mostly from Treble Info app from Hackintosh Five
VNDK-28
Arm32 BINDER64
It's actually AB, according to it having System As Root.
No Seamless upgrade.
Binder64-AB/A64-AB GSIs work on this device.
Quack GSI should be the first we focus on.
TO INSTALL:
Code:
fastboot -w flash system <gsiname.img>
BOOTS
Quack GSI (AOSP 10, bb)!
Will list others as I come across them.
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
LgPWN'd said:
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
Click to expand...
Click to collapse
Yes, please! it's very nice that u did that, I'll link it in the main post when u do
For a working recovery see this
https://forum.xda-developers.com/moto-e6/development/development-team-looking-testors-t4120171
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
soulmaker2207 Did you do the -w in fastboot after you installed the gsi? If you didn't it is definitely worth a try Beware it will erase all data including the internal sd
soulmaker2207 said:
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
Click to expand...
Click to collapse
Alongside the fastboot -w advice, try renaming every img you download to "system.img." I have had way more success doing that than using long img names.
Also, I noticed that for a lot of GSIs, USB Tethering does not work.
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
scottyrick2 said:
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
Click to expand...
Click to collapse
Yeah USB Tethering doesn't seem to work for ANY GSI ROMs.
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
scottyrick2 said:
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
Click to expand...
Click to collapse
How odd. I can't get any Android 11 GSI to work on my E6
Are you trying to update from Android 10? I don't think you can.
scottyrick2 said:
Are you trying to update from Android 10? I don't think you can.
Click to expand...
Click to collapse
Yes I was trying to update from Android 10
I am running phhusson aosp 11 v300.l gsi rom right now. Super fast. Amazing, really.
If you are on the T-Mobile system, you need to do 3 things in order to make VoLTE and sms work properly. Hopefully, this will not be needed in future updates, but it might be.
1. using a root file explorer (I use 3C) to locate and move the org.codeaurora.ims folder from /data/app to /system/app
2. reboot
3. using *#*#4636*#*# on the dialer to open "phone information menu", change the band to GMS/WCDMA/LTE, and close the menu.
That's it. I hope this helps you to consider moving up to gsi roms. They are truly amazing.
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile2.bat with the following and put this .bat file in the same directory as Step1
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the flashfile2.bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
b00ster23 said:
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile.bat with the following and put this file in the same directory as Step1
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the .bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
Click to expand...
Click to collapse
ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
Something to make it easier on others.
There was a link for TWRP on this post but had to remove it because the link is dead. I'll explore other options before re-updating this post
koyo said:
Some things to add to this post to make it easier
1) ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
2) I prefer doing it via this method rather than flashing stock files: - E6 AIO ToolKit Mod Release- | XDA Developers Forums (xda-developers.com)
This has a TWRP for E6 which allows you to flash things like magisk, universal encryption disabler, gapps, et cetera. Things that might not be built into the native ROM.
Click to expand...
Click to collapse
The links are all broken, and I see no TWRP available.
b00ster23 said:
The links are all broken, and I see no TWRP available.
Click to expand...
Click to collapse
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
koyo said:
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
Click to expand...
Click to collapse
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
b00ster23 said:
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
Click to expand...
Click to collapse
Telegram: Contact @Android_General_Chat
t.me
Had an 11.2.3.3 Global rooted via Magisk OP9 Pro that I wanted to update via OTA to 11.2.4.4, which was offered via system update. I used Magisk to restore images before update, did the update, and then went back to install to inactive slot. Rebooted and it was still on 11.2.3.3 so I tried again. Upon trying again, my phone got to a Qualcomm debug/error mode. I experienced this before when on a different boot slot for some other diagnosis of another issue in the past so I switched boot slots.
The other boot slot is stuck in fastboot mode I come to find so I check what it shows if I reverted back to the other boot slot, which was the Qualcomm error. Now instead of a Qualcomm error, it shows language options, one of which is English, and then gives me "boot reason", "wipe data and cache" and "advanced". I believe this is the OnePlus recovery menu, which I have not needed to use before and in the past, used TWRP on other devices.
Can't I just reflash a whole system image for 11.2.4.4 (it'd have to be the European one right now since Global isn't available) via fastboot and it should be fixed, albeit unrooted and I can just re-root? I'd like to try this, but there's no "flash-all.bat" and I don't know the proper flash order for the Euro images within payload.bin as there's no xml file (I looked up a guide for directions on how to flash without flash-all.bat that I have used on other devices). Oh, and I tried to fastboot a known good boot.img and on one of the slots, it works fine, but still wont boot. The other gives error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". I'm stumped.
Wondering if this has been experienced by anyone else before. Wiping my device is the last resort and shall be avoided at all costs after how much I have configured it to my liking.
I saw the following on another guide:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
Followed this guide here after extracting the Europe full system image via Payload-dumper and it now boots somewhat, but after it looks like it's loading into OOS and boot is complete, I get a black screen instead of the lock screen. I get charging sounds when plugged into the computer, but just a black screen.
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Wondering if this has to do with the Europe 11.2.4.4 on my Global device. Going to try reverting to 11.2.2.2 Global full image now.
Geez, good luck
vibrantliker said:
Geez, good luck
Click to expand...
Click to collapse
Just tried flashing the older 11.2.2.2 images one at a time and now it's stuck in recovery...
The closest I can get it to full booting is with 11.2.4.4 Europe full image and I get a black screen only, after it boots up with the OnePlus logo. When plugged in, I get a charging sound every 10-20 seconds or so. Too bad there's no 11.2.4.4 full image for Global or I'd try that.
Also just tried fastboot boot 11.2.4.4_global_boot.img on this 11.2.4.4 Europe image and still no go. Boots and makes sounds, but black screen still.
Have you tried the MSM tool?
hadesflames said:
Have you tried the MSM tool?
Click to expand...
Click to collapse
I was considering it, but don't want to lose any data. Next step is to contact OnePlus technical support during normal hours and see if they can work with me to resolve this one. I believe I read here on XDA that people have contacted them and usually are able to resolve the issue. Trying to avoid clearing data as the device is fine as it boots, but I think the Europe image is conflicting somewhere and not allowing me into the system since it boots all the way to the lock screen, but I don't see a lock screen, just a blank screen with sounds after boot seemingly working, along with charging sounds (albeit, sounding every 10-20s like its periodically charging).
This is so odd though because I did everything as I should've and update seemingly occurred, but system version still showed 11.2.3.3. So I go back to system update and it said there was an issue and to restart again. Did that two times with magisk revert image and restore to inactive and it then stopped booting.
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
djsubterrain said:
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
Click to expand...
Click to collapse
Does stock recovery support ADB? At 8 pro you needed modified one..
pyry666 said:
Does stock recovery support ADB? At 8 pro you needed modified one..
Click to expand...
Click to collapse
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
Click to expand...
Click to collapse
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
pyry666 said:
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
Click to expand...
Click to collapse
Yeah I'm working at the moment so not on my own PC, can't really test it out
djsubterrain said:
Yeah I'm working at the moment so not on my own PC, can't really test it out
Click to expand...
Click to collapse
Just tried. ADB with stock recovery is "unauthorized"..So modified is needed if one wants to use stock recovery with adb
djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
Click to expand...
Click to collapse
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
bulletbling said:
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
Click to expand...
Click to collapse
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
djsubterrain said:
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
Click to expand...
Click to collapse
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
Are there actual hw differences between AA and BA?
bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
There's a pinned post at the top of the forum with all the available latest roms. Not sure they've added Global yet tho. Best going there or Oxygen Updater (when the phone is working) than the download page tbh, OnePlus ALWAYS takes ages to add builds there
pyry666 said:
Are there actual hw differences between AA and BA?
Click to expand...
Click to collapse
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
bulletbling said:
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
Click to expand...
Click to collapse
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
pyry666 said:
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
Click to expand...
Click to collapse
I wish I could go without my phone for weeks until they post the latest firmware to see if that even works, but I can't so I guess I'll have to use the msm tool and wipe all of my internal storage of documents, including taxes, and various files and downloads I've amassed over the past half decade. This really sucks. All because of a simple OTA that should've never caused this. They really should prevent this from being possible with the OTA update tool built-in to their system.