To go back to Sprint stock use this:
Sprint Restore:
https://forum.xda-developers.com/oneplus-7-pro/how-to/sprint-msmdownloadtool-unbrick-t3989841
Crossflashing to European 5G (GM1920):
Outdated method (REQUIRED BOOTLOADER UNLOCK):
Pie
(to set APNs on Sprint, go to *#*#4636#*#* and set the network mode to "LTE/CDMA/UMTS auto (PRL)" , then set your APNs and reboot.)
Input Sprint APNs:
Name: Sprint LTE
APN: x.ispsn
MMSC: http://mms.sprintpcs.com
MMS proxy: oap7.sprintpcs.com
MMS port: 80
APN type: default,mms,supl,hipri,ims,cbs,ia
Protocol/Roaming Protocol: IPv4/IPv6
Flash this in Magisk to enable VoLTE on Sprint:
https://github.com/edgd1er/voenabler/archive/master.zip
If you update to a newer Pie build, you will need to reflash your modem from Sprint, here's a link: http://www.mediafire.com/file/x5g69dx5q64tibk/modem.img/file
OTA updates are fully functional.
The missing information in "About Phone" is normal and does not affect the function of the phone.
If Sprint is your carrier and you update to 10, you will lose APN access for the time being. (Though, humorously, the modem has been unified as of 10 and doesn't need to be reflashed after 10)
10
(Not recommend for Sprint users right now, as there are issues with APNs, GSM/NON SPRINT CARRIERS ARE FINE!)
*Modem has been unified so, you don't need to reflash the Sprint modem after update as of 10.0.4*
Aside from any potential Google SafetyNet updates that break SafetyPatch., this build works perfectly.
"About Phone" is still missing information.
How to flash (applies to conversion and stock restore):
Unlock your bootloader as per:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
Follow these steps in order or you will have to MSM restore to stock and try again
Run TWRPadb.bat first
Format Data after the successful flashing of TWRPadb.bat
Reboot bootloader
Run fastbootimages.bat
Reboot
NEW LOCKED BOOTLOADER METHOD: 04/07/2020 (FULL SAFETYNET PASS):
Download the conversion tool HERE
CONVERSION INSTRUCITONS:
Unplug and power off the phone COMPLETELY
Open the MSM download tool
Uncheck SHA256 check
Connect your USB cable to your PC
Hold Volume DOWN and UP at the same time.
While holding those keys, insert the USB.
Keep holding those keys, click 'Enum' in the tool.
Click start.
Wait about 5-10 minutes, setup over Wifi, OTA to 10, PROFIT!
Code:
[LIST]
[*] [COLOR="red"][COLOR="red"][B]*Modem will not work at first, setup over wifi and OTA to Android 10, it has been unified so, you just need to update to 10.0.5*[/B][/COLOR][/COLOR]
[*] Not recommend for Sprint customers right now, as there are issues with APNs.
[INDENT][INDENT][B][U][COLOR="Red"]**GSM/NON-SPRINT CARRIERS WORK FINE!**[/COLOR][/U][/B][/INDENT][/INDENT]
[*] "About Phone" is still missing information.
[/LIST]
Code:
Q. HELP! I HAVE NO SIGNAL AFTER CROSSFLASH!
A. Connect to wifi and update to Android 10 via OTA.
Q. Can I use a custom ROM built for OnePlus 7 Pro:
A. Not recommend as they have major issues, ROMs are coming!
Q. Can I crossflash to international non 5G and get dual SIM?
A.
[URL="https://forum.xda-developers.com/oneplus-7-pro/how-to/port-oxygen-os-beta-oneplus-7-pro-5g-t4075597"]See here for Open Beta 11[/URL]
Credits:
@nickman529
(Testing and flashing everything I told him to without question, and uploading the flash zips and writing the bats for me because my internet is way too slow)
@mauronofrio (for building us TWRP)
@Some_Random_Username(moral support and lots of OnePlus knowledge)
And lots of others in our test community!
Donations are also welcome, see my signature for way to donate or my PayPal is:
http://PayPal.me/windows8user
Screenshots:
(Reserved)
Magisk ROM should work with the unlocked Sprint phone. I've only tested xXx NoLimits but as long as these magisk ROMs don't interfere with much you should be good to go.
lreyes said:
Magisk ROM should work with the unlocked Sprint phone. I've only tested xXx NoLimits but as long as these magisk ROMs don't interfere with much you should be good to go.
Click to expand...
Click to collapse
Do you mean bootloader unlocked? Or sim unlock?
nickman529 said:
Do you mean bootloader unlocked? Or sim unlock?
Click to expand...
Click to collapse
Bootloader of course
Whoareyou said:
Bootloader of course
Click to expand...
Click to collapse
Do we have a twrp flashable modem?
*Due to differences in the metadata of recovery flashable zips, in order to install ROMs you need to extract the payload.bin and flash in fastboot*
Click to expand...
Click to collapse
Whats the flash command for this? reboot to recovery after and flash twrp and magisk?
nickman529 said:
Whats the flash command for this? reboot to recovery after and flash twrp and magisk?
Click to expand...
Click to collapse
To install a 7 Pro (non-5G) ROM on the 7 Pro 5G:
Use this tool to extract the payload.bin from inside the rom.zip, use fastboot to manually flash each image
https://github.com/cyxx/extract_android_ota_payload
fastboot -w flash system system.img
fastboot flash vendor_b(/a) vendor.img
fastboot flash dtbo_b(/a) dtbo.img
fastboot flash boot_b(/a) boot.img
fastboot --disable-verity --disable-verification flash vbmera_b(/a) vbmeta.img
fastboot boot twrp.img
Mount /system and /vendor IN TWRP
adb pull /system/system/build.prop build.prop.system
adb pull /vendor/build.prop build.prop.vendor
Open each build.prop and change this line in both or whichever it appears:
Code:
persist.radio.multisim.config=dsds
to
Code:
persist.radio.multisim.config=ssss
adb push build.prop.system /system/system/build.prop
adb push build.prop.vendor /vendor/build.prop
flash twrp from: https://dl.twrp.me/guacamole/twrp-installer-3.3.1-4-guacamole.zip.html
Reboot
Can't give you a 100% guarantee that every ROM will boot or function properly, but that is how I got Lineage 16 going somewhat well.
Whoareyou said:
To install a 7 Pro (non-5G) ROM on the 7 Pro 5G:
Use this tool to extract the payload.bin from inside the rom.zip, use fastboot to manually flash each image
https://github.com/cyxx/extract_android_ota_payload
fastboot -w flash system system.img
fastboot flash vendor_b(/a) vendor.img
fastboot flash dtbo_b(/a) dtbo.img
fastboot flash boot_b(/a) boot.img
fastboot --disable-verity --disable-verification flash vbmera_b(/a) vbmeta.img
fastboot boot twrp.img
Mount /system and /vendor IN TWRP
adb pull /system/system/build.prop build.prop.system
adb pull /vendor/build.prop build.prop.vendor
Open each build.prop and change this line in both or whichever it appears:
Code:
persist.radio.multisim.config=dsds
to
Code:
persist.radio.multisim.config=ssss
adb push build.prop.system /system/system/build.prop
adb push build.prop.vendor /vendor/build.prop
flash twrp from: https://dl.twrp.me/guacamole/twrp-installer-3.3.1-4-guacamole.zip.html
Reboot
Can't give you a 100% guarantee that every ROM will boot or function properly, but that is how I got Lineage 16 going somewhat well.
Click to expand...
Click to collapse
Okay cool, good info. i was going to try RR or Havoc and see what i could get working. Do you need to reflash sprint modem as well?
EDIT: Also should I flash to my active or inactive slot?
nickman529 said:
To install a 7 Pro (non-5G) ROM on the 7 Pro 5G:
Use this tool to extract the payload.bin from inside the rom.zip, use fastboot to manually flash each image
https://github.com/cyxx/extract_android_ota_payload
fastboot -w flash system system.img
fastboot flash vendor_b(/a) vendor.img
fastboot flash dtbo_b(/a) dtbo.img
fastboot flash boot_b(/a) boot.img
fastboot --disable-verity --disable-verification flash vbmera_b(/a) vbmeta.img
fastboot boot twrp.img
Mount /system and /vendor IN TWRP
adb pull /system/system/build.prop build.prop.system
adb pull /vendor/build.prop build.prop.vendor
Open each build.prop and change this line in both or whichever it appears:
to
Okay cool, good info. i was going to try RR or Havoc and see what i could get working. Do you need to reflash sprint modem as well?
EDIT: Also should I flash to my active or inactive slot?
Click to expand...
Click to collapse
Just your active slot, and no, you only need to flash the modem if you flash a different modem.img (like flashing the euro oos build)
C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_android_ot
a_payload-master>extract_android_ota_payload.py havocop7p.zip /tmp/
Extracting 'payload.bin' from OTA file...
Extracting 'boot.img'
Traceback (most recent call last):
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payl
oad
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.d
ata_sha256_hash)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress
_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subproces
s.PIPE)
File "C:\Users\remstar\AppData\Local\Programs\Python\Python38\lib\subprocess.p
y", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\remstar\AppData\Local\Programs\Python\Python38\lib\subprocess.p
y", line 1307, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_android_ot
a_payload-master>extract_android_ota_payload.py havocop7p.zip /tmp/
Extracting 'payload.bin' from OTA file...
Extracting 'boot.img'
Traceback (most recent call last):
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payl
oad
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.d
ata_sha256_hash)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress
_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subproces
s.PIPE)
File "C:\Users\remstar\AppData\Local\Programs\Python\Python38\lib\subprocess.p
y", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\remstar\AppData\Local\Programs\Python\Python38\lib\subprocess.p
y", line 1307, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
EDIT: solved, bad dependancies
---------- Post added at 11:48 AM ---------- Previous post was at 11:17 AM ----------
I'm now getting "invalid sparse file format at header magi"
nickman529 said:
C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_android_ot
a_payload-master>extract_android_ota_payload.py havocop7p.zip /tmp/
Extracting 'payload.bin' from OTA file...
Extracting 'boot.img'
Traceback (most recent call last):
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payl
oad
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.d
ata_sha256_hash)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress
_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subproces
s.PIPE)
File "C:\Users\remstar\AppData\Local\Programs\Python\Python38\lib\subprocess.p
y", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\remstar\AppData\Local\Programs\Python\Python38\lib\subprocess.p
y", line 1307, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_android_ot
a_payload-master>extract_android_ota_payload.py havocop7p.zip /tmp/
Extracting 'payload.bin' from OTA file...
Extracting 'boot.img'
Traceback (most recent call last):
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payl
oad
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.d
ata_sha256_hash)
File "C:\Users\remstar\Downloads\extract_android_ota_payload-master\extract_an
droid_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress
_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subproces
s.PIPE)
File "C:\Users\remstar\AppData\Local\Programs\Python\Python38\lib\subprocess.p
y", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\remstar\AppData\Local\Programs\Python\Python38\lib\subprocess.p
y", line 1307, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
EDIT: solved, bad dependancies
---------- Post added at 11:48 AM ---------- Previous post was at 11:17 AM ----------
I'm now getting "invalid sparse file format at header magi"
Click to expand...
Click to collapse
That's not an error, it's normal when flashing system and I think vendor
Whoareyou said:
That's not an error, it's normal when flashing system and I think vendor
Click to expand...
Click to collapse
Even though I tried to flash and nothing happened? No change in phone and it still reboot to oos
nickman529 said:
Even though I tried to flash and nothing happened? No change in phone and it still reboot to oos
Click to expand...
Click to collapse
You need to let it flash everything.
Don't cancel it or unplug or interrupt it.
Flash all the images it extracted
Whoareyou said:
You need to let it flash everything.
Don't cancel it or unplug or interrupt it.
Flash all the images it extracted
Click to expand...
Click to collapse
Okay. Will fastboot show any indication of flashing. And why did it reboot to OOS even after I cancelled the flash. I thought it failed
nickman529 said:
Okay. Will fastboot show any indication of flashing. And why did it reboot to OOS even after I cancelled the flash. I thought it failed
Click to expand...
Click to collapse
No the only indication will be in the command prompt, because it didn't wipe the system or start anything, you canceled it before it even sent the image
Whoareyou said:
No the only indication will be in the command prompt, because it didn't wipe the system or start anything, you canceled it before it even sent the image
Click to expand...
Click to collapse
I understand. I'm sorry haha. This is my first a/b device and I'm still figuring everything out
Whoareyou said:
No the only indication will be in the command prompt, because it didn't wipe the system or start anything, you canceled it before it even sent the image
Click to expand...
Click to collapse
flashed all. now twrp wont boot up
---------- Post added at 01:57 PM ---------- Previous post was at 01:21 PM ----------
Well i got havoc Q based to boot up and run smooth but no mobile signal
Update, got havoc pie flashed. couldnt boot twrp at all. just goes to a black screen. swapped to slot b and it booted twrp. flashed installer. swapped slots. no luck. currently trying flashing havoc with a known good twrp on slot b
Related
Hi all,
this one is for the brave, as it is still untested.
Nevertheless, please find here some information what I did:
Got the latest full OTA package here from xda
Extracted payload.bin into the fastboot compatible .img files
Adapted the "flash_all_except_storage script" in order to automate the flashing and included it
As I have right now (just my luck) an issue with fastboot not detecting my phone, I cannot test right now. Will try again myself in the evening though, at least that is the plan.
In the meantime any brave (no guarantees, no warranties) are welcome to test it. Apart from the above mentioned changes, it is the update as it was distributed by Xiaomi/ Google including the January security patch:
Android 8.0.0 [OPR1.170623.026.8.1.10]
link removed as official version is now available here
I am looking forward to your feedback.
P.S.: For more information how to use it, please have a look here
UPDATE: system.img seems to be not flashable right now and I have no more ideas right now what I could do about it. So sorry guys, back to waiting for Xiaomi again.
downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?
i dont have a Mac, windows 10. how do i flash it ?
soeschelz said:
downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?
Click to expand...
Click to collapse
Rawwr said:
i dont have a Mac, windows 10. how do i flash it ?
Click to expand...
Click to collapse
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot set_active a
fastboot reboot
majamee said:
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still either flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
Click to expand...
Click to collapse
cant you make a script ? it is hard to enter every code at once
@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
Code:
fastboot flash system_a system.img
I got the following error:
Code:
invalid sparse file format at header magi
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker
soeschelz said:
@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
I got the following error:
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker
Click to expand...
Click to collapse
Thank you for your helpful feedback. I will see if I can do something about it, except waiting for xiaomi to finally release the fastboot image themselves or I get my ota without reading play services data.
Can you explain me how you extracted payload.bin to .img files
ramesh1686 said:
Can you explain me how you extracted payload.bin to .img files
Click to expand...
Click to collapse
I can tell you the basic instructions, but for the details I have to ask you to please have a look yourself how to do it for your Operating System.
So,
You download both python scripts from here: https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15
You make sure you have installed python and google-protobuf binding for python
You open a terminal/ shell/ cmd and navigate via the "cd" command to the directory the payload.bin and the both .py scripts are
run the following command "payload_dumper.py payload.bin"
I personally did these parts on a Linux system as it was at least for me the easiest way to have python and protobuf set up in no time.
----
Btw. I had another look, if I can do something about the system.img not being flashable at the moment. Nevertheless no luck so far, I begin to wonder if the OTA package is really a full OTA, due to that or just a very big update as it is intended to update Android N to O...
Sorry, for the failed attempt, at least it was worth a try.
I had issue with "invalid sparse file format at header magi" before (also extracted image from OTA), but it flashed successfully. Flashing just took longer than usual. However I had issues with failed video recording and the only fix for me was to use full flash of stock fastboot ROM. There might be something missing in extracted images from OTA package.
I have unpacked the latest payload.bin file from Android 8.0.0 [OPR1.170623.026.8.1.10] and the size of the system.img is 3.2 GB . This is too much?
The system partition has a size of 3072 MB. It's some error of unpacking?
Fastboot ROM is available http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
Source: http://en.miui.com/thread-1596182-1-1.html
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery 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 7 Pro in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=294300
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro
OnePlus 7 Pro Persist: https://androidfilehost.com/?fid=6006931924117929081
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 to extract images.zip before proceed)
Fastboot Partitions:
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
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.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
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/
Thanks to @SaiBork for first time tested
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.
I know you said not for branded devices, are the partitions different for these devices?
Just wondering if this could be what we need to convert the T-Mobile version and if so if you need tester.
criptix said:
I know you said not for branded devices, are the partitions different for these devices?
Click to expand...
Click to collapse
Yes, sometimes also the rom is different. Actually the branded devices can't use this rom also if they want, because to use this rom you need to have an unlocked bootloader
Yeah figured bootloader would need to be unlocked as well.
If you happen to need testers for the conversion ( if your working on it) let me know.
I just SIM unlocked my T-Mobile variant today, and also applied for my unlock .bin on the OnePlus site!
Thank you! You revived my phone!
zzs001 said:
Thank you! You revived my phone!
Click to expand...
Click to collapse
Perfect, like for others oneplus devices i will continue to support them, if you want to contribute and help me, please consider making a donation, thanks.
I've F-ed my international 7 Pro up, used your flash all, seemed to have work, but stuck in a loop now... Anyone got any suggestions, please?
I was so happy when I found this post, I thought my problems were over, but yeah... apparently not
posedatull said:
I've F-ed my international 7 Pro up, used your flash all, seemed to have work, but stuck in a loop now... Anyone got any suggestions, please?
I was so happy when I found this post, I thought my problems were over, but yeah... apparently not
Click to expand...
Click to collapse
which version you had before use fastboot rom? which fastboot rom did you used?
I was on stock, tried to install twrp, didnt go well (wouldn't mount), and i wanted to wipe data/cache, and mistakenly wiped system as well because i wasnt paying attention. Tried putting the stock recovery, still wouldnt boot due to obvious reasons.... then I found this
Basically I had the 9.5.4 with deleted system when I attempted to use the flash all bat.
GM21BA, european 12gb one, if it makes any difference...
posedatull said:
I was on stock, tried to install twrp, didnt go well (wouldn't mount), and i wanted to wipe data/cache, and mistakenly wiped system as well because i wasnt paying attention. Tried putting the stock recovery, still wouldnt boot due to obvious reasons.... then I found this
Basically I had the 9.5.4 with deleted system when I attempted to use the flash all bat.
GM21BA, european 12gb one, if it makes any difference...
Click to expand...
Click to collapse
So you should use the 9.5.4 fastboot rom, have you used it?
of course.
I am hoping maybe a failed download, so I just redownloaded it and trying again now
posedatull said:
of course.
I am hoping maybe a failed download, so I just redownloaded it and trying again now
Click to expand...
Click to collapse
The process can take a lot of time, just wait until you see something like "presse a key to proceed"
also:
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."
tose missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 153.005s
Press any key to exit..."
and then the phone tries to boot, i get to the spinning 1+ logo, and it stays there for even an hour if i let it...
posedatull said:
also:
"extracting android-info.txt (0 MB) to RAM...
extracting boot.img (96 MB) to disk... took 0.386s
target reported max download size of 805306368 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.030s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (3472 MB) to disk..."
tose missing files, is that normal?
downloaded your zip, extracted it, started flash-all.bat, no modifications done whatsoever
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
the zip finishes, no problem,ends with
"writing 'userdata'...
OKAY [ 0.003s]
rebooting...
finished. total time: 153.005s
Press any key to exit..."
and then the phone tries to boot, i get to the spinning 1+ logo, and it stays there for even an hour if i let it...
Click to expand...
Click to collapse
so i don't know, try to use the other flashall, you should unpack image.zip and other flashall in the main folder and then you should run the flash-all-fastboot.bat.
If you want you can try to flash the twrp in the boot partition and then try to flash the stock rom through sideload
i've just tried all of them one by one... still bootloop every time
posedatull said:
i've just tried all of them one by one... still bootloop every time
Click to expand...
Click to collapse
do you want to contact me on telegram? Maybe i can help you better
i'm struggling this at work, but i'll be home in about 2hours.
if you could help then, i would seriously appreciate it
posedatull said:
i'm struggling this at work, but i'll be home in about 2hours.
if you could help then, i would seriously appreciate it
Click to expand...
Click to collapse
Yes yes, write me on telegram, the nick is always the same: mauronofrio
hello, how long should it take to first boot after flashing all? I'm waiting for so long...
Ah yes, Oneplus released that new update. Now I must download 2+ GB off my capped data plan, then flash it to recovery, carefully switch back my slot then flash my custom ROM again to the slot I just flashed OOS to and then flash OOS again to the other slot and then I must repeat everything above. After that I must delete the 2 fake partitions the updater created on data because they are useless. Oh wait it doesn't let me delete them who'd have thought?
Seriously? What on earth happened there
A better solution is required, especially something that grants more control. Well here it is
The boring stuff:
I am not responsible for anything you do to your device
These zips contain the following files:
Code:
The firmware (duh)
flashall - flashes both a and b
flash_a - only flashes slot a
flash_b - only flashes slot b
The following partitions found in the official oxygenos zip have been removed:
Code:
vbmeta
boot
dtbo
odm
system
vendor
reserve
india
Because for custom ROM users these partitions are either unused or used by the currently running custom ROM
How to flash?
From TWRP (it doesn't even need to support decryption):
Code:
adb push abl.img aop.img bluetooth.img cmnlib64.img cmnlib.img devcfg.img dsp.img flash_a flashall flash_b hyp.img keymaster.img LOGO.img modem.img oem_stanvbk.img qupfw.img storsec.img tz.img xbl_config.img xbl.img /tmp/
adb shell
cd /tmp
chmod 777 flashall # or flash_a/b
./flashall # or sh flashall or use flash_a/b
I suggest you use one of the flash_a/b scripts to only flash your current slot and test the changes out before running flashall
From termux:
You might need to set selinux to permissive while flashing. Only try to flash your current slot, reboot and if there are no errors flash the other slot
unzip the zip file to a directory and cd to it. If you use termux you should already know this
Just run one of the flashing scripts as root
Note that the flashing takes some time. Do not abort it
From adb root:
Sadly I don't have adb root so if someone has it they can let me know how it goes and how they flashed it
Do NOT believe in myths. You do NOT need to wipe cache/dalvik/any other nonsense while upgrading firmware. Stop wasting your time
Downloads:
Open beta 9: https://glassrom.pw/guacamole-ob9fw.zip
More will be added when I have time
Yes I personally tested this on my device and it was fine. Except that the popup camera pops out sometimes but I just suspect big brother. Nothing abnormal
Happy flashing. Or whatever
Anybody caught the latest OOS release link yet? All I found was an incremental OTA
Is this project discontinued? If yes, I'd like to see a revival of this.
hellcat50 said:
Is this project discontinued? If yes, I'd like to see a revival of this.
Click to expand...
Click to collapse
He doesn't care about support
The link is dead.
Does anyone have this zip?
I need these files
flashall
flash_a
flash_b
in order to make an up to date zip.
alessio89g said:
The link is dead.
Does anyone have this zip?
I need these files
flashall
flash_a
flash_b
in order to make an up to date zip.
Click to expand...
Click to collapse
you can get the file list and the firmware collection from the glassrom device tree
i stopped maintaining this as now i just ship firmware into my roms
Bitbucket
bitbucket.org
flash_a, flash_b and flashall really were just script generated scripts
something like
```
for i in $(ls *img | sed 's/.img$//g')
do
echo dd if="$i".img of=/dev/block/bootdevice/by-name/"$i"_a;
done
```
same for slot b:
```
for i in $(ls *img | sed 's/.img$//g')
do
echo dd if="$i".img of=/dev/block/bootdevice/by-name/"$i"_b;
done
```
concetenate flash_a and flash_b as follows:
```
cat flash_a flash_b > flashall
```
PS: you need to remove the oem_stanvbk_{a,b} entries as that is not an A/B partition. also i have just shown you roughly what i use to generate the flash scripts. there is no guarantee these work. example you might need to remove the $ from the regex
I can confirm that Android 11 beta 2 can be flashed to our device!!!!
This is the efran google pixel gsi... He is the dev of the of the gsi and should get all the credit I am just putting this info out here for everyone to try. It is functional and stable. Also it can be rooted but not many if any Magisk mods are functional. I have tested this on Lake XT-1965-2. It should work for any other XT-1965 build just make sure you have the correct stock Android 10 latest firmware downloaded.
Pixel GSI
https://mirrors.lolinet.com/firmware/gsi/Pixel/Pixel-AB-11-20200709-ErfanGSI.img-0455.7z
XT-1965-2 stock firmware
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
TWRP
https://dl.twrp.me/lake/
GMS core
https://www.apkmirror.com/apk/googl...0400-319035315-android-apk-download/download/
I take no responsibility what so ever for using this guide. Below worked for me. This process fully formats the phone so if you got data you want to save make sure you back it up. As with any mod your warranty will be void and a hard brick is a possibility just like any other Rom flash..
Instructions
Have adb/fastboot installed on PC
Bootloader needs to be unlocked using procedure from Motorola
Unzip your firmware, the Pixel Gsi, and the Lake TWRP .img to where you have adb/fastboot installed
Put the twrp-installer-3.4.0-0-lake.zip, the copy partitions-AB.zip, and the lagfix.zip on your sd card.
Unzip the GMScore.zip and propfiles.zip to your sd card
You will need to fully wipe the phone by factory reset through stock recovery or using TWRP to format data and wipe dalvik, system, vendor, data, oem, and internal.
Reboot to bootloader and hook up to PC. Open command prompt where you have fastboot installed. Then type these commands: Note if you are using different firmware adjust accordingly. Below is for XT-1965-2 from the link above.
Do not flash the stock System sparse 0 thru 5 .img files that come in the stock firmware !!!!!!!
(you can copy all of these commands at once and paste to the command line to make it easier)
fastboot --set-active=a
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 erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system Pixel-AB-11-20200709-ErfanGSI.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo logo.bin
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
Do not flash the stock System sparse 0 thru 5 .img files !!!!!!!
reboot.. Now let the phone start up do not worry about setting anything up that you normally would. Navigate to settings about phone and click on the build 7 times to unlock developer options. Open developer options to enable usb debugging. Also in developer options under the drawing heading change Smallest width value to 408. This will bring the screen size back to normal. Now reboot to bootloader.
BOOT the TWRP .img from the link above using this command:
fastboot boot twrp-3.4.0-0-lake.img
In twrp install the twrp-installer-3.4.0-0-lake.zip from your sd card. reboot to recovery..then install the copy partitions-AB.zip from your sd card.
CRITICAL STEPS!!! If you fail to do this part correctly the phone will become unstable lag very bad and no playstore.
THESE PROP FILES ARE FOR XT-1965-2 WITH THE LINKED FIRMWARE FROM ABOVE!!!!!! If on a different build you will need to edit to match your firmware!!!!
while in TWRP recovery mount the system... go to the file manager under the advanced tab. navigate to /system_root/system/product. Select the build.prop and delete. navigate to back to where you have the new system.product.build.prop and move it to /system_root/system/product. rename the file build.prop and hit the chmod 755 to set permission. Repeat the same process for the /system_root/system/build.prop using the new system.build.prop make sure to rename and set permissions.
navigate to /system_root/system/product/priv-app and delete the folder prebuiltgmscore then move the new GMScore folder with the apk to the same directory and set permissions on the folder with chmod 755 tab
install the lag fix zip from TWRP reboot and enjoy Moto G7 plus with Android 11
Can You share XT-1965-3 prop Files or what to edit?
Trimis de pe al meu moto g(7) plus folosind Tapatalk
antonio2001 said:
Can You share XT-1965-3 prop Files or what to edit?
basically what u need to edit is any reference the Google pixel or walleye from the build fingerprint:
This is the original gsi /system/product/build.prop
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.product.build.date=Wed Jun 24 19:47:27 UTC 2020
ro.product.build.date.utc=1593028047
ro.product.build.fingerprint=google/walleye/walleye:11/RPB2.200611.009/6625208:user/release-keys
ro.product.build.id=RPB2.200611.009
ro.product.build.tags=release-keys
ro.product.build.type=user
ro.product.build.version.incremental=6625208
ro.product.build.version.release=11
ro.product.build.version.release_or_codename=11
ro.product.build.version.sdk=30
ro.product.product.brand=google
ro.product.product.device=walleye
ro.product.product.manufacturer=Google
ro.product.product.model=Pixel 2
ro.product.product.name=walleye
# end common build properties
#
ro.build.characteristics=nosdcard
ro.postinstall.fstab.prefix=/product
ro.charger.enable_suspend=true
ro.config.alarm_alert=Bright_morning.ogg
ro.config.notification_sound=Popcorn.ogg
ro.config.ringtone=The_big_adventure.ogg
ro.opa.eligible_device=true
ro.atrace.core.services=com.google.android.gms,com.google.android.gms.ui,com.google.android.gms.persistent
ro.com.android.dataroaming=false
ro.com.google.clientidbase=android-google
ro.error.receiver.system.apps=com.google.android.gms
ro.setupwizard.enterprise_mode=1
ro.setupwizard.esim_cid_ignore=00000001
ro.setupwizard.rotation_locked=true
setupwizard.feature.baseline_setupwizard_enabled=true
setupwizard.feature.show_pai_screen_in_main_flow.carrier1839=false
setupwizard.feature.skip_button_use_mobile_data.carrier1839=true
setupwizard.theme=glif_v3_light
ro.com.google.ime.theme_id=5
ro.facelock.black_timeout=700
ro.facelock.det_timeout=2500
ro.facelock.rec_timeout=3500
ro.facelock.est_max_time=600
setupwizard.enable_assist_gesture_training=true
ro.cp_system_other_odex=0
ro.nnapi.extensions.deny_on_product=true
ro.lmk.kill_heaviest_task=true
ro.lmk.kill_timeout_ms=100
ro.lmk.use_minfree_levels=true
ro.setupwizard.mode=DISABLED
ro.vndk.lite=false
ro.control_privapp_permissions=disable
this is the one I used for my device XT-1965-2:
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.product.build.date=Wed Jun 24 19:47:27 UTC 2020
ro.product.build.date.utc=1593028047
ro.product.build.fingerprint=Motorola/XT-1965/Lake:11/RPB2.200611.009/6625208:user/release-keys
ro.product.build.id=RPB2.200611.009
ro.product.build.tags=release-keys
ro.product.build.type=user
ro.product.build.version.incremental=6625208
ro.product.build.version.release=11
ro.product.build.version.release_or_codename=11
ro.product.build.version.sdk=30
ro.product.product.brand=Motorola
ro.product.product.device=XT-1965
ro.product.product.manufacturer=Motorola
ro.product.product.model=G7 Plus
ro.product.product.name=Lake
# end common build properties
#
# ADDITIONAL PRODUCT PROPERTIES
#
ro.build.characteristics=nosdcard
ro.postinstall.fstab.prefix=/product
ro.charger.enable_suspend=true
ro.config.alarm_alert=Bright_morning.ogg
ro.config.notification_sound=Popcorn.ogg
ro.config.ringtone=The_big_adventure.ogg
ro.opa.eligible_device=true
ro.atrace.core.services=com.google.android.gms,com.google.android.gms.ui,com.google.android.gms.persistent
ro.com.android.dataroaming=false
ro.com.google.clientidbase=android-google
ro.error.receiver.system.apps=com.google.android.gms
ro.setupwizard.enterprise_mode=1
ro.setupwizard.esim_cid_ignore=00000001
ro.setupwizard.rotation_locked=true
setupwizard.feature.baseline_setupwizard_enabled=true
setupwizard.feature.show_pai_screen_in_main_flow.carrier1839=false
setupwizard.feature.skip_button_use_mobile_data.carrier1839=true
setupwizard.theme=glif_v3_light
ro.com.google.ime.theme_id=5
ro.facelock.black_timeout=700
ro.facelock.det_timeout=2500
ro.facelock.rec_timeout=3500
ro.facelock.est_max_time=600
setupwizard.enable_assist_gesture_training=true
ro.cp_system_other_odex=0
ro.nnapi.extensions.deny_on_product=true
ro.lmk.kill_heaviest_task=true
ro.lmk.kill_timeout_ms=100
ro.lmk.use_minfree_levels=true
ro.setupwizard.mode=DISABLED
ro.vndk.lite=false
ro.control_privapp_permissions=disable
These Lines need to be changed:
ro.product.build.fingerprint=google/walleye/walleye:11/RPB2.200611.009/6625208:user/release-keys
ro.product.build.id=RPB2.200611.009
ro.product.product.brand=google
ro.product.product.device=walleye
ro.product.product.manufacturer=Google
ro.product.product.model=Pixel 2
ro.product.product.name=walleye
So I believe that you can use your Android 10 firmware from Xt-1965-3 and use my prop file because it wont make a difference and should still boot....
Please try and post your results so other s will know
Click to expand...
Click to collapse
Playstore Fix
Flash this with Magisk or TWRP and it will unlock all the APKs in the playstore that say no compatibility....
After you flash and reboot: clear the app cache and data from the Google play store app in system settings menu...
And here are some screenshots with some of the magisk mods that I have found to work.....
Also it is possible to flash the GSI from TWRP as long as you are coming from a factory reset Stock Android 10 moto build...
How to unlock the Realme 8 Pro bootloader?
1. you'd better write in english, to get a broader range of people who understand you question ;-).
2. Also waiting for that ... it's a shame.
Greetz
Kurt
How to unlock bootloader realme 8 5G
Answer from [email protected] from today :
Unlock Bootloader tutorial for Realme 8 Pro RMX3081 is not available as of now.Further, keep following our social media handles and official community portal for the latest updates,
Yeah, we can achieve the bootloader unlock of realme 8 pro. Mine is unlocked. The build number and security patch must be (RMX3081_11_A.44) (November 5,2021)
This is Export rom not the GDPR rom (EU)
Have flashed it and can unlock and flash files via fastboot.
OFP - Original Firmware Project :
Code:
Model Project Project ID Download link
RMX3081 20711 (Project ID-20711)_INDIA,MM,BD,PK RMX3081export_11_A.44 https://fileload.coloros.com/504197RMX3081export_11_A.44_2021110921030235.zip
RMX3081 20712 (Project ID-20712)_PH,VN,KH,-EG,IQ,MY RMX3081export_11_A.44 https://fileload.coloros.com/504198RMX3081export_11_A.44_2021110921100000.zip
RMX3081 20713 (Project ID-20713)_LUX,CH,ES,UK,FR,IT,DE,NL,BE,NO,PT,FIN,CY RMX3081GDPR_11_A.44 https://fileload.coloros.com/504200RMX3081GDPR_11_A.44_2021110921090000.zip
RMX3081 20713 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504199RMX3081export_11_A.44_2021110921060000.zip
RMX3081 20714 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504201RMX3081export_11_A.44_2021110921110000.zip
@Shibu Shaji share us the
getprop ro.build.display.full_id
Yeah, we can achieve the bootloader unlock of realme 8 pro. Mine is unlocked. The build number and security patch must be (RMX3081_11_A.44) (November 5,2021)
StratOS_HTC said:
This is Export rom not the GDPR rom (EU)
Have flashed it and can unlock and flash files via fastboot.
OFP - Original Firmware Project :
Code:
Model Project Project ID Download link
RMX3081 20711 (Project ID-20711)_INDIA,MM,BD,PK RMX3081export_11_A.44 https://fileload.coloros.com/504197RMX3081export_11_A.44_2021110921030235.zip
RMX3081 20712 (Project ID-20712)_PH,VN,KH,-EG,IQ,MY RMX3081export_11_A.44 https://fileload.coloros.com/504198RMX3081export_11_A.44_2021110921100000.zip
RMX3081 20713 (Project ID-20713)_LUX,CH,ES,UK,FR,IT,DE,NL,BE,NO,PT,FIN,CY RMX3081GDPR_11_A.44 https://fileload.coloros.com/504200RMX3081GDPR_11_A.44_2021110921090000.zip
RMX3081 20713 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504199RMX3081export_11_A.44_2021110921060000.zip
RMX3081 20714 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504201RMX3081export_11_A.44_2021110921110000.zip
@Shibu Shaji share us the
getprop ro.build.display.full_id
Click to expand...
Click to collapse
Here is my id : RMX3081export_11_A.44_2021110921030235
Yeah, see it's exported Project ID-20711 and don't have a bootloader locked.
Have flashed it previously and know that.
The GDPR versions of ROM you cannot do almost nothing 4 now.
Oh bro, this is not GDPR version.. After I unlocked my bootloader, i tried to root realme 8 pro with patched boot image from OFP Rom but it's doesn't work for me..
Any thing to say about this?
StratOS_HTC said:
Yeah, see it's exported Project ID-20711 and don't have a bootloader locked.
Have flashed it previously and know that.
The GDPR versions of ROM you cannot do almost nothing 4 now.
Click to expand...
Click to collapse
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Since jour project id is 20711
Guess your PCB shows 0020711*
dial : *#899#
press the PCB num
StratOS_HTC said:
Well let me guide you throught it :
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Click to expand...
Click to collapse
Yeah , tried but nothing seems to be work.
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_sys
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Click to expand...
Click to collapse
Yeah i tried the steps that u said above to ROOT realme 8 pro, but it doesn't work for me... here are the steps that i did.
Fastboot mode
*Fastboot flashing unlock
*Fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
*Fastboot flash boot (magisk patched) boot.img
Result : Device went to bootloop. Retrieved from
bootloop by flashing stock boot image that previously extracted from OFP file and now the device is fine.
Also tried this step
Fastboot mode
*Fastboot flashing unlock
*Fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
* Fastboot --disable-verity --disable-verification
flash vbmeta_system vbmeta_system.img
*Fastboot --disable-verity --disable-verification
flash vbmeta_vendor vbmeta_vendor.img
*Fastboot flash boot (magisk patched) boot.img
Result : Bootlooped. Retrieved by flashing stock boot image..
And also, i tried to BOOT patched boot image... and it shows
FAILED <remote: unknown command>
ABV is still active.
THX @Shibu Shaji
For showing us the 20711 EXPORT .44 ROM fastboot getvar all infos.
I have also the 20713 GDPR .44 ROM fastboot getvar all infos.
The bootloader in EXPORT is unlocked and is not userspaced.
From green to orange state ... some progress after all ...
It seems your bootloader unlocked? actually how? I think ur AVB is now disabled
StratOS_HTC said:
View attachment 5505451
From green to orange state ... some progress after all ...
Click to expand...
Click to collapse
Wow, how did you do it?
currently via isp ufs access and help of a reversing from a friend.
On bootloop also ...
Oh bro, So what to do next? Is there any other problems with ur partitions after this?
Since EDL is not configured correctly (No kernel driver supported: Operation not supported or unimplemented on this platform) after the firehose programmer sucessfully boot ...
Also QFIL and unimplemented <CONFIGURE> or <SIG> and signed and certed things the only thing to do is via ISP UFS control.
OR possible USB port communication debug via MSM flash.
For EXPORT version have prepared seen action on the screen for this ROM
Code:
Project 20711
RMX3081
Version Flash MSM download tool v.2.0.51 for eMMC/UFS
Rom ofp : RMX3081export_11_A.28_202104090210
Server : India
Use default NV=yes
Reboot on finish=yes
Download Firehose protocol file
Sahara communication succeeded
Boot via firehose
Trying to handshake
Get sign data
Verify data
Getting NV code from server
Failed to get NV code. Default NV code would be used
Firehose GetUfsInfo
Erasing the partition Primarly GPT
Erasing the partition BackupGPT
Erasing the partition userdata
Downloading cdt_engineering_release.img
Erasing partition keystore
Downloading cache.img
Downloading recovery.img
Downloading metadata.img
Downloading userdata.img
Downloading gpt_main0.bin
Downloading xbl.elf
Downloading gpt_main1.bin
Downloading gpt_main2.bin
Downloading aop.mbn
Downloading tz.mbn
Downloading NON-HLOS.bin
Erasing the partition mdtpsecapp
Erasing the partition mdtp
Downloading abl.elf
Downloading dspso.bin
Downloading boot.img
Downloading devcfg.mbn
Downloading vbmeta_vendor.img
Downloading dtbo.img
Downloading imagefv.elf
Downloading oppo_sec.mbn
Downloading dpAP.mbn
Erasing the partition spunvm
Downloading splash.img
Downloading logfs_ufs_8mb.bin
Erasing the partition cateloader
Erasing the partition rawdump
Erasing the partition logdump
Download multi_image.mbn
Erasing the partition catefv
Downloading gpt_main4.bin
Download static_nvbk.bin
Erasing the partition opporeserve1
Downloading emmc_fw.bin
Downloading DRIVER.ISO
Downloading gpt_main5.bin
Restarting
Downloading Firehose protocol file
Sahara communication succeeded
Trying to handshake via Firehose
Configure the settings of Firehose
Get sign data
Verify data
Downloading super partsuper.0
Downloading super partsuper.1
Downloading super partsuper.2
Get basic data
Write patch image to user partition
Restarting
Download succeeded
Get sign data
Verify data
Currently non-implemented/documented also by MSM7125 ?