Convert GM1915 to GM1917? - OnePlus 7 Pro Questions & Answers

Hello, I've bought a OnePlus 7 Pro a while ago, and during my first efforts of installing the OnePlus drivers on the computer, then flashing it (unfortunately, I can't recall which image that was), my phone was identified as "GM1917" in the Windows notification area and the phone's about screen.
I continued playing around with ROMs, and at some point I bricked it...
I think it was guacamole_21_P.01_211210_repack.ops together with "MSM download tool 4.0-patched" (which also happened to be in a "Rebrand T-Mobile to Global 7 Pro" package) that allowed me to unbrick & flash it with an image again - however, it was now identified as "GM1915"! Using any other unbricking packages (like OnePlus_7_Pro_Global_OxygenOS_11.0.5.1.zip) resulted in the MSM tool saying "Param preload: Device not match image".
The phone's about screen says I'm using model 1915, but it runs 11.0.7.1.GM21AA!
I'm completely confused. I would feel better if I could use the seemingly better-supported GM21AA ROMs (not just OxygenOS, but maybe also others), can I 'convert' my phone somehow?

rookey said:
Hello, I've bought a OnePlus 7 Pro a while ago, and during my first efforts of installing the OnePlus drivers on the computer, then flashing it (unfortunately, I can't recall which image that was), my phone was identified as "GM1917" in the Windows notification area and the phone's about screen.
I continued playing around with ROMs, and at some point I bricked it...
I think it was guacamole_21_P.01_211210_repack.ops together with "MSM download tool 4.0-patched" (which also happened to be in a "Rebrand T-Mobile to Global 7 Pro" package) that allowed me to unbrick & flash it with an image again - however, it was now identified as "GM1915"! Using any other unbricking packages (like OnePlus_7_Pro_Global_OxygenOS_11.0.5.1.zip) resulted in the MSM tool saying "Param preload: Device not match image".
The phone's about screen says I'm using model 1915, but it runs 11.0.7.1.GM21AA!
I'm completely confused. I would feel better if I could use the seemingly better-supported GM21AA ROMs (not just OxygenOS, but maybe also others), can I 'convert' my phone somehow?
Click to expand...
Click to collapse
Ever figure out how to get your phone back to reading as GM1917? I have a similar issue.

Whether or not your phone says GM1917 or GM1915 completely depends on the rom. But idk why that matters, everything functions the exact same way.

Related

OnePlus 7 Pro MSM Tool "Packed image not exist"

I am trying to rebrand my t-mobile OnePlus 7 Pro back to the t-mobile software after changing it to international a few months ago. I have to trade in my phone with t-mobile and have to flash the software. I downloaded all the necessary files, but when I run the MSM tool, I get the "Package image not exist" error. I have tried running it regular and as an admin and still get it. I do still have the OP7Pro international files and the MSM tool from that and tried launching it, but it seems that that one works.
Any ideas?
Roccothepro said:
I am trying to rebrand my t-mobile OnePlus 7 Pro back to the t-mobile software after changing it to international a few months ago. I have to trade in my phone with t-mobile and have to flash the software. I downloaded all the necessary files, but when I run the MSM tool, I get the "Package image not exist" error. I have tried running it regular and as an admin and still get it. I do still have the OP7Pro international files and the MSM tool from that and tried launching it, but it seems that that one works.
Any ideas?
Click to expand...
Click to collapse
did you fix? Same thing for me
Idk if you guys figured this out yet, but I came across this myself, messing with my old Tmobile Based OnePlus 7 Pro, with the whole "package image not exist", The Msm tool has to be in the same folder as the guacamole zip, and the L2 drivers, and using something like Winrar/7zip you gotta extract them from the .rar and .7z. then run the Msm tool again. Hope this helps.
Roccothepro said:
I am trying to rebrand my t-mobile OnePlus 7 Pro back to the t-mobile software after changing it to international a few months ago. I have to trade in my phone with t-mobile and have to flash the software. I downloaded all the necessary files, but when I run the MSM tool, I get the "Package image not exist" error. I have tried running it regular and as an admin and still get it. I do still have the OP7Pro international files and the MSM tool from that and tried launching it, but it seems that that one works.
Any ideas?
Click to expand...
Click to collapse
If you are still needing some help with this, I can try to dump my firmware and put it together for flashing in fastboot.
@EVOuser94 @phillipmckinnish @Roccothepro
This is also for all other T-Mobile users who want to convert back to TMO firmware.
I uploaded Android 11.0.1.2 firmware images to a new ROM thread. To convert back to TMO firmware without using the MSM tool you can follow the instructions in the thread.
Since you are converting from International or another non TMO ROM, you will be required to wipe your data.
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)

Question Phone Hard Bricked in EDL mode

Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.
chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.
Click to expand...
Click to collapse
I had to do the same thing. I am using a LE2113 and managed to brick my phone in a way where only EDL could save it. I came from the latest OOS (colorOS) firmware and tried to flash LineageOS when everything went south. I tried to use the Oneplus 9 EU MSM tool but this one did not work for me. Since there is no official EU MSM for the LE2113 the only way I could repair it was by using the EU OnePlus 9 pro msm firmware. It only worked with the "use lite firehose" option for me. After that was done I unlocked the bootloader once again and flashed OOS (Android 11) for OnePlus 9 again. This was the way I got the original firmware back on my device although I do not think it would've been possible to relock the bootloader at this point.
Straight after that I once again flashed lineage and everything is working fine now. Certainly a shady approach but it is the end result that counts I'd say.
Nullifii said:
Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)
Click to expand...
Click to collapse
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??
jab5555 said:
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??
Click to expand...
Click to collapse
That's the thing though. I had the LE2115 MSM tool but it was in Chinese for some reason I have a LE2115 phone as well but it said that the files didn't match up. Maybe they uploaded the wrong variant to the website? None of the tools that I had downloaded were in English, all in Chinese.
chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for y
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
This what I used m8, got it off OP when they tried to remote flash my phone , couldn't do it on AMD Ryzen, done on my old pc, driver issue lol, good luck m8

Question [SOLVED] Can anyone help me unbrick? I have tried lite firehose, MSM for global, MSM for Indian 9 Pro, none work

I modded the global MSM so that it will flash to this frankenphone.
All of those stuck on Indian firmware, rejoice! I modded the global MSM!
Long story short, I bricked my device today, had to use the Indian 9 Pro firmware to fix it as the global MSM wasn't recognizing it, and was very frustrated I couldn't go back to full global firmware. I figured out how to fix this. Just use it...
forum.xda-developers.com
EDIT: For anyone else trying this and getting unsupported target O2, click the Target dropdown and change it to India. It's a device mismatch that can be overridden that way. It's flashing now and I'm sure it will work fine.
EDIT2: Yeah, that worked fine. To get back to global and get a working phone, follow the steps here: https://forum.xda-developers.com/t/...ection-error-check-this.4308601/post-86528671
TWRP has been updated since that guide was made and no longer has you select between A/B partitions to format and it will give you errors on partitions when you flash but it does work regardless and boots up fine with full working radio.
When it's back up and running, if you don't plan to go straight to a custom ROM, turn USB debugging back on, reboot to fastboot, boot (don't flash) TWRP again, and use this copy partitions script to make sure both partitions have the same software.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Now you should be good to go (until the next time this insanely finicky device decides it doesn't want to cooperate). I have not figured out how to make it actually be recognized as the global device that it is, if anyone knows how to do that, please let me know. It is now recognized as an Indian 9 Pro variant which means I have to use the Indian 9 Pro MSM and go through this headache any time it decides to be a pain.
Original post: So I have an LE2115 and was doing some testing for a ROM dev. He asked me to flash Lineage to see if something worked there, I flashed the recovery, it booted back to fastboot. Tried flashing it again, same thing. Tried the global fastboot stock flash that's pinned here and that seemed to go okay until it rebooted, from there I had a black screen.
Fired up my global MSM tool which has always worked before, Sahara error. Got it back into EDL again, checked lite firehose, device not match image... Tried Indian 9 Pro MSM and it says unsupported target.
Am I just completely hosed here or is there something else I can do? I'm not new to ROM flashing, been doing it since the HTC Hero in 2009 and long before that with Windows Mobile 5 on my PPC-6700 and this is the first time I have what appears to be a totally bricked device so any help would be greatly appreciated.
It doesn't do anything but go to EDL.

MSM Tool "Sahara communication failed and Automatic DDR failed"

I'm hoping someone can help me out here. I've been trying for hours to restore my OnePlus 8T with the global MSM tool and I keep getting the Sahara communication failed error over and over again. My drivers are successfully installed and I've tried 5 different USB ports and 3 different types of cables and nothing works. I've tried rebooting my PC multiple times, and 2 out of the 3 cables I've used are official OnePlus cables.
My phone stuck in edl.
Is there a possibility to get my phone back to life?
For me, I've been receiving this err when trying to use msm inside a windows kvm virtual machine with usb passthrough enabled...
When I switch to a normal windows install, no more errors.
So, it has been rumored that an usb 2.0 port works better than 3.0 for this.
Also check whether your tool fits your device or not. Log shows your tool is for T-Mobile version, do you have a kb2007?
If you do have a kb2007, I can confirm that MsmTools from here [ https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/ ] works.
Also check this [ https://forum.xda-developers.com/t/...-global-version-with-msmdownloadtool.4495057/ ] if you want global OOS instead of TMO's older version installed.
You can also try to press power button for a long time like 30s to reboot your device (still into edl mode but might fix some random errors).
IAAxl said:
For me, I've been receiving this err when trying to use msm inside a windows kvm virtual machine with usb passthrough enabled...
When I switch to a normal windows install, no more errors.
So, it has been rumored that an usb 2.0 port works better than 3.0 for this.
Also check whether your tool fits your device or not. Log shows your tool is for T-Mobile version, do you have a kb2007?
If you do have a kb2007, I can confirm that MsmTools from here [ https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/ ] works.
Also check this [ https://forum.xda-developers.com/t/...-global-version-with-msmdownloadtool.4495057/ ] if you want global OOS instead of TMO's older version installed.
You can also try to press power button for a long time like 30s to reboot your device (still into edl mode but might fix some random errors).
Click to expand...
Click to collapse
new error "unsupported target h2, Preload Param" appeared
BladeForm said:
new error "unsupported target h2, Preload Param" appeared
Click to expand...
Click to collapse
That means you're using worng version msmtool.
In the log it shows that you're trying to flash kebabt_15_O.01_210121, which means TMO version rom.
But your device (aka target to flash) is "h2" version, not TMO version. So the error comes out.
ARE YOH SURE YOU'RE HOLDING A T-MOBILE 8T???
I don't know exactly what "h2" stands for, but definitely not TMO, for I have a TMO 8T and the target code is "TMO".
Tell me how do you get this phone. I doubt"h2" might stand for Chinese version but I'm not sure.
If you want to cross-flash other region's rom, you must modify the msmtool manually.
And this might help if your phone isn't Chinese brand (aka kb2000).
[SOLVED] Unbrick hard-bricked OP 8T
Hello people, unfortunately, I bricked my phone and am stuck trying to unbrick it. How the bricking happened: I bricked my OP 8T when I tried to update my OS from Lineage OS 18.1 (Android 11) to 19.1 (Android 12) following this guide: Official...
forum.xda-developers.com
If your phone do is Chinese brand, XDA can't provide you a suitable msmtool because that version runs a Chinese-only system. You have to find it yourself.
If you find it, you do can cross-flash it to global version with the method provided below:
[Guide] Convert locked OnePlus 8T TMO to Global version with MsmDownloadTool
This can: Bypass TMO flash lock as it uses 9008 EDL. Remove TMO sim lock and oem lock as you will be using global rom. Convert your KB2007 (KB09CB) to KB2005 (KB05AA) as much as possible. (Although you're using the latest KB2005 firmware, any...
forum.xda-developers.com
IAAxl said:
That means you're using worng version msmtool.
In the log it shows that you're trying to flash kebabt_15_O.01_210121, which means TMO version rom.
But your device (aka target to flash) is "h2" version, not TMO version. So the error comes out.
ARE YOH SURE YOU'RE HOLDING A T-MOBILE 8T???
I don't know exactly what "h2" stands for, but definitely not TMO, for I have a TMO 8T and the target code is "TMO".
Tell me how do you get this phone. I doubt"h2" might stand for Chinese version but I'm not sure.
If you want to cross-flash other region's rom, you must modify the msmtool manually.
Click to expand...
Click to collapse
I made a typo, I don't have T-MOBILE
BladeForm said:
I made a typo, I don't have T-MOBILE
Click to expand...
Click to collapse
Then stop using TMO version msmtool.
Go get the version that matches your device.
Your log file shows you're using TMO msmtool. This will never work.
IAAxl said:
Then stop using TMO version msmtool.
Go get the version that matches your device.
Your log file shows you're using TMO msmtool. This will never work.
Click to expand...
Click to collapse
flashed through msm to the system does not load, the bootloader is closed
Is there a possibility to get my phone back to life?
Not enough info...
BladeForm said:
flashed through msm
Click to expand...
Click to collapse
Does the flash succeed? What version of msm tool did you use?
BladeForm said:
the system does not load
Click to expand...
Click to collapse
Any error message? Please describe how you get this and what did you do exactly.
BladeForm said:
the bootloader is closed
Click to expand...
Click to collapse
Is this differs from the status before flash? By saying closed, do you mean fastboot flash is locked?
BladeForm said:
Is there a possibility to get my phone back to life?
Click to expand...
Click to collapse
Hard to say. If your device has no failure hardware, the chance is good. But you should provide more info so that others could tell.

Question Easiest/best way to get to stock Android 13?

So I've got a TMobile OnePlus 9 that's been converted to the global ROM. From here what's the easiest way to get updated to stock OxygenOS Android 13? When I run the system update in settings it'll update to Android 12 but the phone says that there's no sim card in. Am I doing something wrong? I don't mind unlocking the bootloader and flaking a recovery if there's a stock rooted zip I can flash.
I've tried myself but updating anything to 12 and up my touchscreen stops working, but using the TMobile India modded MSM should work getting to the global rom "but now realizing it was cuz I used something else to recover from a brick" but here
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
th
underworld737 said:
I've tried myself but updating anything to 12 and up my touchscreen stops working, but using the TMobile India modded MSM should work getting to the global rom "but now realizing it was cuz I used something else to recover from a brick" but here
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks I'll ck it out
this doesn't work for my device le2119 the mod fix zip throws an error unsupported device eu. I made the mistake of activating slot b. is there any way of switching back without fastboot. all I get is a black screen no matter what button combo I press. I can only get edl and I'd rather not flash the eu msm again.
paulb1977 said:
this doesn't work for my device le2119 the mod fix zip throws an error unsupported device eu. I made the mistake of activating slot b. is there any way of switching back without fastboot. all I get is a black screen no matter what button combo I press. I can only get edl and I'd rather not flash the eu msm again.
Click to expand...
Click to collapse
ive gotten the same error too, im on 11.2.10.10, but cant upgrade to OOS12/13 without the touchscreen breaking/dual sim bug, i forgot the link to the 9 pro india msm to flash it with, but ive tried flashing one that was 9 pro and kept getting "device not match image", no clue why
I just read somewhere that downgrading to 11.2.2.2 may work but only place I can find that firmware is on some Chinese site. I can flash the eu pro version all day long. but now I tried flashing an India mod firmware with no success and reflasjed eu again but phone is stuck at 0% power and all I get is a bootloop

Categories

Resources