Related
Hi,
TL-DR; I rooted my phone, and want to update with minimal loss of data.
Sorry for this newbie question but I really couldn't figure out everything and wanted to confirm before proceeding.
I have MHA-L29C185B138 and rooted step-by-step via the instructions on this link:
HOW TO ROOT YOUR MATE 9 with Decrypted Data in TWRP without needing a patched Boot.img
I want to update. What should I do? I isntalled Firmware Finder and downloaded MHA-L29C185B172 FULLOTA-MF. (downloaded all 3 files)
I couldn't find a complete tutorial for rooted roms. Read different and partial recommendations on different threads. Somewhere I read that I need to restore my boot and recovery partition before update. I backed my boot partition as it was a step in rooting guide but I didn't back up my recovery partition.
So could you please point me a beginner friendly guide that explains step by step updating rooted mate 9?
Thanks in advance.
I bump up this question as I'm interested in that answer also
Sent from my MHA-L29 using Tapatalk
Updating and keeping root is basically not possible, as far as I know.
Regardless of installation method, your phone will be re-locked and wiped when new firmware is installed on a rooted phone.
Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.
vipivj said:
Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.
Click to expand...
Click to collapse
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Sent from my MHA-L29 using XDA-Developers Legacy app
jr313 said:
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Click to expand...
Click to collapse
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?
vipivj said:
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?
Click to expand...
Click to collapse
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise it will fail.
sent from my rotary phone
jr313 said:
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise it will fail.
sent from my rotary phone
Click to expand...
Click to collapse
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk
itenos said:
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk
Click to expand...
Click to collapse
Sorry about that, you want to use the RECOVERY.img not recovery2. You fastboot that img and you will have stick recovery, and it will place it in the correct spot so need to worry about where you would need to flash it to. Hope that helps
sent from my rotary phone
Hey all,
I am unlocked, rooted, etc. I have latest platform tools. i am trying to reflash a modem img using fastboot on windows 10 64 but am given "FAILED (remote: 'Not allowed to flash (modem_b)')"
Can someone point me in the right direction?
Xdevillived666 said:
Hey all,
I am unlocked, rooted, etc. I have latest platform tools. i am trying to reflash a modem img using fastboot on windows 10 64 but am given "FAILED (remote: 'Not allowed to flash (modem_b)')"
Can someone point me in the right direction?
Click to expand...
Click to collapse
Is there a "modem.img" that you extracted from the factory image?
Badger50 said:
Is there a "modem.img" that you extracted from the factory image?
Click to expand...
Click to collapse
Yes. I've tried opening command window as admin, too. Seems to return this error noattwr what:-/
Xdevillived666 said:
Yes. I've tried opening command window as admin, too. Seems to return this error noattwr what:-/
Click to expand...
Click to collapse
Are you trying to use a different radio/baseband from a previous month? I've actually never seen anyone wanting to flash a modem.img for whatever reason. So now I'm curious.
Badger50 said:
Are you trying to use a different radio/baseband from a previous month? I've actually never seen anyone wanting to flash a modem.img for whatever reason. So now I'm curious.
Click to expand...
Click to collapse
Nope. Long story short I'm trying to use qpst and pdc tool. Getting a qmi error and read on a German thread that sometimes reflashing modem will fix it. Problem is that I can't flash individual images aside from radio or bootloader with fastboot -_-
Are your platform tools up to date?
jsauder2 said:
Are your platform tools up to date?
Click to expand...
Click to collapse
Yeah. Is this normal for a pixel 3 to be so locked down? I know my pixel one wasn't
Xdevillived666 said:
Yeah. Is this normal for a pixel 3 to be so locked down? I know my pixel one wasn't
Click to expand...
Click to collapse
If it's a Verizon model, you can't unlock the bootloader. If it's from Google, you should be fine. I've not tried flashing a modem. If you can flash the factory images, just use the flash all script and remove the w. That will flash everything, including the modem, but will not wipe your data.
jsauder2 said:
If it's a Verizon model, you can't unlock the bootloader. If it's from Google, you should be fine. I've not tried flashing a modem. If you can flash the factory images, just use the flash all script and remove the w. That will flash everything, including the modem, but will not wipe your data.
Click to expand...
Click to collapse
I can use the script but opening it in notepad ++ , the flash all bat doesn't show anything about modem. I've tried everything from just fastboot flash modem modem.img to
Flash modem slot a, etc. Keeps giving remote error flash modem not allowed . I really think Google just locked this phone down that much more. Ridiculous.
The factory image does flash the modem. It doesn't say so in the bat or sh files, but you'll also notice that it doesn't mention the boot, system, or vendor files either (along with many other things), even though those are most certainly flashed during an update. That's because those are all inside the image zip that is referenced in the last line of the bat or sh (where you remove the -w). It flashes everything inside of that, including the modem.
If a screwed up modem is your problem, flashing the factory image will fix it. If that doesn't fix it, then the modem is not your issue.
Xdevillived666 said:
I can use the script but opening it in notepad ++ , the flash all bat doesn't show anything about modem. I've tried everything from just fastboot flash modem modem.img to
Flash modem slot a, etc. Keeps giving remote error flash modem not allowed . I really think Google just locked this phone down that much more. Ridiculous.
Click to expand...
Click to collapse
I don't know if this will work. I also don't know what the fastboot update command does under the hood. But the flash-all batch file does flash the modem image using the fastboot update command. What if you created a zip file with your modem image in it and then tried to flash it with the update command, or possibly replace the modem.img in the zip in the factory image with your image?
Sent from my [device_name] using XDA-Developers Legacy app
I wanted to root my new Samsung Galaxy M20 (Oreo 8.1.0).Please provide necessary files for it.
craxoid said:
I wanted to root my new Samsung Galaxy M20 (Oreo 8.1.0).Please provide necessary files for it.
Click to expand...
Click to collapse
Please take the time to look for yourself before you post questions here.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Please take the time to look for yourself before you post questions here.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Well, since there are no TWRP files available..
mhgxd said:
Well, since there are no TWRP files available..
Click to expand...
Click to collapse
If there is no TWRP for the device, the only options left are to try the various universal rooting apps for android or the various universal android rooting programs on PC and hope that one of them has an exploit that works on this device or to try using Magisk on PC to create a modified boot.img then flash that modified boot.img then install Magisk.
If none of the universal apps have a working exploit, then you are out of luck unless you or someone else builds a TWRP for this device or unless one of the various universal rooting tools gets updated with new exploits that just happen to work on this device.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If there is no TWRP for the device, the only options left are to try the various universal rooting apps for android or the various universal android rooting programs on PC and hope that one of them has an exploit that works on this device or to try using Magisk on PC to create a modified boot.img then flash that modified boot.img then install Magisk.
If none of the universal apps have a working exploit, then you are out of luck unless you or someone else builds a TWRP for this device or unless one of the various universal rooting tools gets updated with new exploits that just happen to work on this device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I already tried some universal apps for rooting however none worked. First time owning an android and building a TWRP seems a bit too technical for me
I'll try magisk tomorrow and hope I can get root. Would be better if someone with more knowledge gets on sharing a TWRP. Thanks for your replies :good:
I've managed to get Magisk installed.
For OP and anyone interested here is my patched boot.img file. It is in .tar.gz format as that's what I've needed for Odin as I couldn't make the fastboot recognize my device.
Please I'm not sure whether this works for other M20s, so please use at your own risk as this is my first time doing this.
Original boot.img was downloaded from SAMFIRM software.
SM-M205F - CSC: INS
www . sendspace .com /file/34w6qk
mhgxd said:
I've managed to get Magisk installed.
For OP and anyone interested here is my patched boot.img file. It is in .tar.gz format as that's what I've needed for Odin as I couldn't make the fastboot recognize my device.
Please I'm not sure whether this works for other M20s, so please use at your own risk as this is my first time doing this.
Original boot.img was downloaded from SAMFIRM software.
SM-M205F - CSC: INS
www . sendspace .com /file/34w6qk
Click to expand...
Click to collapse
Fastboot didn't work because Samsung does not use fastboot in any kind of way.
It would be better if you could convert the boot.img to .tar.md5 as that is the format Odin is designed to use, it might avoid issues on other devices when used on those devices. Tar.gz works though.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Fastboot didn't work because Samsung does not use fastboot in any kind of way.
It would be better if you could convert the boot.img to .tar.md5 as that is the format Odin is designed to use, it might avoid issues on other devices when used on those devices. Tar.gz works though.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Whoa, I've literally spent more than 2 hours trying to figure why adb was working and fastboot was not recognizing my device and fastboot for samsung is all over google results and forums.
I'm not sure how to convert it becuase compressing with linux the .img file to .tar.gz wasn't working for Odin. I had to generate .tar from Magisk otherwise Odin couldn't read the file.
mhgxd said:
Whoa, I've literally spent more than 2 hours trying to figure why adb was working and fastboot was not recognizing my device and fastboot for samsung is all over google results and forums.
I'm not sure how to convert it becuase compressing with linux the .img file to .tar.gz wasn't working for Odin. I had to generate .tar from Magisk otherwise Odin couldn't read the file.
Click to expand...
Click to collapse
I've never understood why there is stuff on the internet about using fastboot on Samsung devices, I've never owned and have never known of a Samsung device that could actually use fastboot. Unless there has been some kind of change in how Samsung does things in the last 2 years, fastboot is a no-go for Samsung.
Yes, adb and adb shell work perfectly fine with Samsung devices, maybe the stuff on the internet is confusing adb with fastboot since they are both installed together using the same installer and both use a terminal. Maybe the people that have posted information don't know the difference.
As long as the file flashes, maybe no one will have issues with the .tar.gz.
Sent from my LGL84VL using Tapatalk
Hey mate,
You can follow this guide to root your Samsung galaxy M20. I followed the same guide and it helped me rooting my m20 device. I Hope it helps for you too.
Hi, is anyone here able to backup their persist.img and share it here? I somehow corrupted my partition and my sensors aren't working. I don't know if this applies to this device, but I found this guide on a Xiaomi Mi A1 guide (https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/), or else you can try this (https://youtu.be/LGkDZtQ_ERE?t=124) from 2:04 . If you can achieve the result with a different method you can also share the file here. Thanks in advance to whoever does this.
You're going to need to specify which exact build you're looking for this from...
..or you could just use "Payload Dumper" to extract all the img files from the released packages :
https://androidfilehost.com/?fid=818070582850510260
Didn't think it would matter, anyways, I'm on 9.5.5 GM1913, but if needed I can switch to 9.5.4
@djsubterrain https://i.imgur.com/Z1GyAlR.png no persist here. Do you mind sharing yours?
MrVoshel said:
@djsubterrain https://i.imgur.com/Z1GyAlR.png no persist here. Do you mind sharing yours?
Click to expand...
Click to collapse
Unfortunately TWRP doesn't list that as a backup option so I don't think I can unless you know how.
djsubterrain said:
Unfortunately TWRP doesn't list that as a backup option so I don't think I can unless you know how.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=it
can you try using this app?
Gm1917 9.5.6 if it helps you
https://www.dropbox.com/s/8q8hy66obsnfdmw/persist_backup_2019-05-31_17-36-15.img?dl=0
Sent from my GM1917 using Tapatalk
OK, Here you go. Just to confirm I'm on EU 9.5.5, I have Rice magisk module enabled and ElementalX latest kernel, also rooted with latest Magisk :
https://www.androidfilehost.com/?fid=6006931924117886178
The folder contained the img and 2 other files so I just stuck them in there too.
I note that you're in the US so, the post above mine is T-Mobile version (9.5.6 isn't on other versions I don't think), if that's the one you have you might want to go with theirs.
Thanks guys, both working. I'm not in the US, I randomly chose a country. Anyways I flashed the GM1917 9.5.6 on my GM1913 9.5.4, and no problems. Also tested the 9.5.5 GM1913 and working. I don't think persist is phone/update-dependant, also because OnePlus hasn't done any updates or specific changes to the sensors directly from the persist partition. For anyone interested, just get a persist.img, reboot to fastboot and connect your phone to the computer, type this command into fastboot "fastboot flash persist persist_name_xxxx.img" and reboot.
MrVoshel said:
Thanks guys, both working. I'm not in the US, I randomly chose a country. Anyways I flashed the GM1917 9.5.6 on my GM1913 9.5.4, and no problems. Also tested the 9.5.5 GM1913 and working. I don't think persist is phone/update-dependant, also because OnePlus hasn't done any updates or specific changes to the sensors directly from the persist partition. For anyone interested, just get a persist.img, reboot to fastboot and connect your phone to the computer, type this command into fastboot "fastboot flash persist persist_name_xxxx.img" and reboot.
Click to expand...
Click to collapse
Glad to hear you're back up and running.
Glad to hear it worked. I don't think 9.5.6 is a T-Mobile patch. Non T-Mobile phones were getting it ota and it fixed an issue for Verizon users. I think 1+is unifying their build numbers back together.
Sent from my GM1917 using Tapatalk
MrVoshel said:
Thanks guys, both working. I'm not in the US, I randomly chose a country. Anyways I flashed the GM1917 9.5.6 on my GM1913 9.5.4, and no problems. Also tested the 9.5.5 GM1913 and working. I don't think persist is phone/update-dependant, also because OnePlus hasn't done any updates or specific changes to the sensors directly from the persist partition. For anyone interested, just get a persist.img, reboot to fastboot and connect your phone to the computer, type this command into fastboot "fastboot flash persist persist_name_xxxx.img" and reboot.
Click to expand...
Click to collapse
if you mess up persist.img
does it flash from the MSM tool?
virtyx said:
if you mess up persist.img
does it flash from the MSM tool?
Click to expand...
Click to collapse
It didn't for me, took a little bit to figure out why my wifi wasn't working with any of the custom kernels that inline the wifi module in the boot img. Used msm tool as well as fastboot ROM... No luck. After finding this persist img and fastboot flashing, no problem since. Was on 9.5.7 Global when flashed.
zoman7663 said:
It didn't for me, took a little bit to figure out why my wifi wasn't working with any of the custom kernels that inline the wifi module in the boot img. Used msm tool as well as fastboot ROM... No luck. After finding this persist img and fastboot flashing, no problem since. Was on 9.5.7 Global when flashed.
Click to expand...
Click to collapse
really? i wouldve thought the MSM tool would bring it back
do you have the persist.img? do you have a link for those of us who break things.
virtyx said:
really? i wouldve thought the MSM tool would bring it back
do you have the persist.img? do you have a link for those of us who break things.
Click to expand...
Click to collapse
I got the img from this thread, first or second post...
zoman7663 said:
I got the img from this thread, first or second post...
Click to expand...
Click to collapse
Thank you
When fastboot flashing does it wipe persist before flashing the IMG?
virtyx said:
Thank you
When fastboot flashing does it wipe persist before flashing the IMG?
Click to expand...
Click to collapse
Not that I'm aware of, I think it just overwrites it
[/COLOR]
zoman7663 said:
Not that I'm aware of, I think it just overwrites it
Click to expand...
Click to collapse
great! thanks
Sorry to ressurect an old thread. I was just wondering if this persist.img(or this method) can be used to flash the relevant persist.img onto a oneplus 7t pro to restore widevine L1?
I've looked into Decrypting the OPS files used for MSMDownloadTool, in order to use the Firehose in QFIL. So we can accomplish single partition flashing via EDL using QFIL.
I've successfully implemented BKerlers decryption python script which can be found here: https://github.com/bkerler/oppo_decrypt , to retrieve the partition xmls.
The problem is, this method requires you to go through the flashing process in MSMDownloadTool... I own a Sprint OP7 Pro 5G, and therefore do not have access to an OPS file to flash in order to obtain the Firehose and partitions.
With the ability to flash individual partitions through QFIL, we can flash any signed partitions we want without recovery or fastboot. Which would open up the possibility of not requiring SIM unlocks to achieve BL unlocks.
Another nice thing about this would be the ability to backup and restore partitions.
jthein1989 said:
I've looked into Decrypting the OPS files used for MSMDownloadTool, in order to use the Firehose in QFIL. So we can accomplish single partition flashing via EDL using QFIL.
I've successfully implemented BKerlers decryption python script which can be found here: https://github.com/bkerler/oppo_decrypt , to retrieve the partition xmls.
The problem is, this method requires you to go through the flashing process in MSMDownloadTool... I own a Sprint OP7 Pro 5G, and therefore do not have access to an OPS file to flash in order to obtain the Firehose and partitions.
With the ability to flash individual partitions through QFIL, we can flash any signed partitions we want without recovery or fastboot. Which would open up the possibility of not requiring SIM unlocks to achieve BL unlocks.
Click to expand...
Click to collapse
yes you are correct, I know the layout pretty well.. I have the xml and loader for the OP6T and 7Pro, and also, you are right, you can flash twrp with a patch0.xml that will allow to bypass locked bootloader..
as of matter of fact, I just did that to my brother in laws old ZTE Zmax Pro, which now had twrp and root running on it, while bootloader is still locked...... or was locked.. Since you cant access fastboot mode to unlock it.
So yes, its possible............. Sorry if I am late on this reply and has already been fixed or replied else where.. but I just happen to see this and wanted to add my 2 cents..
Don't be sorry. This is a road that is still wide open, but OnePlus stated that even they don't have the MSMDownload Tool for the 5G version... Which is ridiculous!
And ?
Eliminater74 said:
yes you are correct, I know the layout pretty well.. I have the xml and loader for the OP6T and 7Pro, and also, you are right, you can flash twrp with a patch0.xml that will allow to bypass locked bootloader..
as of matter of fact, I just did that to my brother in laws old ZTE Zmax Pro, which now had twrp and root running on it, while bootloader is still locked...... or was locked.. Since you cant access fastboot mode to unlock it.
So yes, its possible............. Sorry if I am late on this reply and has already been fixed or replied else where.. but I just happen to see this and wanted to add my 2 cents..
Click to expand...
Click to collapse
Does that mean we can copy the widevine l1 keys and copy it over after we bl unlock so we can watch HD Netflix on a bl unlocked phone?
So, question? How can I help, I want to do whatever would be helpful to allow the oneplus 7 t or pro from t-mobile or any other oem to be converted with out unlocked bootloader.
Eliminater74 said:
yes you are correct, I know the layout pretty well.. I have the xml and loader for the OP6T and 7Pro, and also, you are right, you can flash twrp with a patch0.xml that will allow to bypass locked bootloader..
as of matter of fact, I just did that to my brother in laws old ZTE Zmax Pro, which now had twrp and root running on it, while bootloader is still locked...... or was locked.. Since you cant access fastboot mode to unlock it.
So yes, its possible............. Sorry if I am late on this reply and has already been fixed or replied else where.. but I just happen to see this and wanted to add my 2 cents..
Click to expand...
Click to collapse
Bro please tell me how u do it can u please help me do install twrp without unlock bootloader on oneplus 7
gigawatt said:
So, question? How can I help, I want to do whatever would be helpful to allow the oneplus 7 t or pro from t-mobile or any other oem to be converted with out unlocked bootloader.
Click to expand...
Click to collapse
Do you still have a LOCKED bootloader and are on the oneplus 7T (tmobile) or do you know anyone who is? This would be of EXTREME help. If so I know a way you could be of HUUUUUGGE help... Basically, the theory is that once the bootloader is unlocked, it deletes a file (/data/reserve/reserve.img) and without this file, tmobile phones cannot take OTA's. The good news is that the file can be extracted with a special tool(edl.py) without an unlocked bootloader, be placed back on an unlocked device and can take OTA's. So what we would have you do is run this edl.py tool and pull the data partition and extract that specific reserve.img file. And then we could distribute it and everyone with unlocked bootloaders could again take OTAs. Please contact me immediately.
Hi, what about if I upgraded to the 5g would this still help?
Eliminater74 said:
yes you are correct, I know the layout pretty well.. I have the xml and loader for the OP6T and 7Pro, and also, you are right, you can flash twrp with a patch0.xml that will allow to bypass locked bootloader..
as of matter of fact, I just did that to my brother in laws old ZTE Zmax Pro, which now had twrp and root running on it, while bootloader is still locked...... or was locked.. Since you cant access fastboot mode to unlock it.
So yes, its possible............. Sorry if I am late on this reply and has already been fixed or replied else where.. but I just happen to see this and wanted to add my 2 cents..
Click to expand...
Click to collapse
Can you please tell me the process in explained way to extract ops file,I tried (bkerler) way but I didn't succeed,please help me ..
jthein1989 said:
I've looked into Decrypting the OPS files used for MSMDownloadTool, in order to use the Firehose in QFIL. So we can accomplish single partition flashing via EDL using QFIL.
I've successfully implemented BKerlers decryption python script which can be found here: https://github.com/bkerler/oppo_decrypt , to retrieve the partition xmls.
The problem is, this method requires you to go through the flashing process in MSMDownloadTool... I own a Sprint OP7 Pro 5G, and therefore do not have access to an OPS file to flash in order to obtain the Firehose and partitions.
With the ability to flash individual partitions through QFIL, we can flash any signed partitions we want without recovery or fastboot. Which would open up the possibility of not requiring SIM unlocks to achieve BL unlocks.
Click to expand...
Click to collapse
jthein1989 said:
I've looked into Decrypting the OPS files used for MSMDownloadTool, in order to use the Firehose in QFIL. So we can accomplish single partition flashing via EDL using QFIL.
I've successfully implemented BKerlers decryption python script which can be found here: https://github.com/bkerler/oppo_decrypt , to retrieve the partition xmls.
The problem is, this method requires you to go through the flashing process in MSMDownloadTool... I own a Sprint OP7 Pro 5G, and therefore do not have access to an OPS file to flash in order to obtain the Firehose and partitions.
With the ability to flash individual partitions through QFIL, we can flash any signed partitions we want without recovery or fastboot. Which would open up the possibility of not requiring SIM unlocks to achieve BL unlocks.
Click to expand...
Click to collapse
do you extract .ops files with it if yes please guide how you can do it
Eliminater74 said:
yes you are correct, I know the layout pretty well.. I have the xml and loader for the OP6T and 7Pro, and also, you are right, you can flash twrp with a patch0.xml that will allow to bypass locked bootloader..
as of matter of fact, I just did that to my brother in laws old ZTE Zmax Pro, which now had twrp and root running on it, while bootloader is still locked...... or was locked.. Since you cant access fastboot mode to unlock it.
So yes, its possible............. Sorry if I am late on this reply and has already been fixed or replied else where.. but I just happen to see this and wanted to add my 2 cents..
Click to expand...
Click to collapse
can you send One Plus 7 Pro xml and loader files for me, because im trying messing around with qfil and i need those file rawprogram and patch0
It's does not matter . The firehose programmer elf has the write disabled.I have unpacked multipal ops files. OnePlus MSM tool signs the write option ,so you will not be able to write with any other tool.even with the xml files
justencase6 said:
It's does not matter . The firehose programmer elf has the write disabled.I have unpacked multipal ops files. OnePlus MSM tool signs the write option ,so you will not be able to write with any other tool.even with the xml files
Click to expand...
Click to collapse
Could you provide me all those files? Or teach me how to extract it?
luciferobert said:
Could you provide me all those files? Or teach me how to extract it?
Click to expand...
Click to collapse
Even if you get those files you can't do anything with that....i have tried everything that you are trying to do right now..! Nothing going to work
@justencase6 helpd me with it
Prinçe çharming ap said:
Even if you get those files you can't do anything with that....i have tried everything that you are trying to do right now..! Nothing going to work
@justencase6 helpd me with
Click to expand...
Click to collapse
Prinçe çharming ap said:
Even if you get those files you can't do anything with that....i have tried everything that you are trying to do right now..! Nothing going to work
@justencase6 helpd me with it
Click to expand...
Click to collapse
Probably Jtag is my last weapon to resurrect my OP7P
luciferobert said:
Probably Jtag is my last weapon to resurrect my OP7P
Click to expand...
Click to collapse
If you need firehose and xml for OnePlus 7 pro then it is already available on xda.
Prinçe çharming ap said:
If you need firehose and xml for OnePlus 7 pro then it is already available on xda.
Click to expand...
Click to collapse
Can you give me the link please