Related
Just rooted the h81010o. Ive got xposed and the root cloak method doesnt work nor disabling su. Im not gonna flash back to stock just for android pay i just like making everything work. And as far as the bootloader unlock. I seen that the only version capable is the h815 int.. can it only be unlocked by lg or can a dev. Find a way? Last thing, custom recovery. Can be done with tmobile variant but is there a way for the att h810 to have a custom recovery without the bootloader unlocked or is that necessary?
Can I flash a h850 Rom on my h830 with twrp. I am really tired of this tmobile unlock app sh****t. I just want to put in unlock keys like the good old days. I won't go into my back story to much but I have a lg G5 I got off eBay and purchased tmobile prepaid sim add $100 to account. But as I am in Canada my imei is still not showing on tmobile imei check or in mytmobile. So tmobile can't do anything til shows usage. So I am screwed unless I can get this dam phone unlocked.
We don't know the software difference so short answer, no. You can try editing the customer xml file, i believe that's the file the unlock processor checks to use the app or device default unlock.
Do so at your own risk, this worked on HTC devices, since LG does a deeper software individuality I'm not sure the process is the same.
can't avoid the tmo unlock.
you can either go through tmobile or ebay to get it unlocked. flashing H850 would not work.. as well as brick your device (if flashing the H850 bootloader which is packed into the roms).
Come on you good guys and let's root and custom rom this device.
What I'd really love is for someone to work out how we can use root to insert the settings needed for VoLTE and VoWoFi on UK networks (seeing as LG refuse to enable it for the UK)
Sent from my LM-G710 using Tapatalk
stuclark said:
What I'd really love is for someone to work out how we can use root to insert the settings needed for VoLTE and VoWoFi on UK networks (seeing as LG refuse to enable it for the UK)
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
Why they refuse to enable it for UK? That is the reason why I can't find it in settings...
Boot-loader Unlock Available for TMG710TM
I still am waiting for being bale to unlock my T-mobile variant
Tetraguy said:
I still am waiting for being bale to unlock my T-mobile variant
Click to expand...
Click to collapse
Right I hope LG would let us but to be honest I highly doubt they will
Joe199799 said:
Right I hope LG would let us but to be honest I highly doubt they will
Click to expand...
Click to collapse
Things like that honestly makes me want to have gotten the Oneplus 6 instead because I love custom roms and building my own using AOSP, and to me it doesn't make sense how you can allow the same exact phone to be unlocked but not in all places, is annoying.
Tetraguy said:
Things like that honestly makes me want to have gotten the Oneplus 6 instead because I love custom roms and building my own using AOSP, and to me it doesn't make sense how you can allow the same exact phone to be unlocked but not in all places, is annoying.
Click to expand...
Click to collapse
I feel you homie it sucks, but that's how it is just gotta hope the lovely people here can figure something out, other than the lack of root I'm really enjoying this phone
Tetraguy said:
I still am waiting for being bale to unlock my T-mobile variant
Click to expand...
Click to collapse
Joe199799 said:
Right I hope LG would let us but to be honest I highly doubt they will
Click to expand...
Click to collapse
Won't happen the T-mobile variant G7. For the LG V30 H932, T-mobile not only stripped out the fastboot flash commands they also have different RSA encryption keys so you can't convert to another model (even temporarily) which has fastboot flash commands. They also did this for the LG G6 T-mobile, so I can't see them reversing course to help people who want to unlock bootloader and root.
Since back in May when we found the wonderful LG Oreo bootloader unlock exploit, every LG V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because they don't have fastboot flash commands and you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
ChazzMatt said:
Won't happen the T-mobile variant G7. For the LG V30 H932, T-mobile not only stripped out the fastboot flash commands they also have different RSA encryption keys so you can't convert to another model (even temporarily) which has fastboot flash commands. They also did this for the LG G6 T-mobile, so I can't see them reversing course to help people who want to unlock bootloader and root.
Since back in May when we found the wonderful LG Oreo bootloader unlock exploit, every LG V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because they don't have fastboot flash commands and you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Click to expand...
Click to collapse
That blows I literally don't have any other answer but that, I remember back in the day when Verizon was no go and T-Mobile were the easy phones to root. my my how the turntables. Fu**ing John Legere I thought he was all for unlocking bootloader's and was trying to talk to Samsung to not lock it down on the S6 or S7 a couple of years ago. Just F*** dude. Welp I'll live I honestly just miss viper4android and adaway, I've been doing fine with eqfy mixed with the stock EQ and Blokada but I wish it were root apps instead.
the 710TM does have Fastboot commands, I've already played around with them, such as "fastboot getvar device-id", "fastboot oem unlocked" give the bootloader locked status, you can even flash with fastboot to unlock the bootloader with "unlock.bin". Once LG gives 710TM owners the green light, they will give us the unlock.bin
Scotsman828 said:
the 710TM does have Fastboot commands, I've already played around with them, such as "fastboot getvar device-id", "fastboot oem unlocked" give the bootloader locked status, you can even flash with fastboot to unlock the bootloader with "unlock.bin". Once LG gives 710TM owners the green light, they will give us the unlock.bin
Click to expand...
Click to collapse
I really don't think LG will ever give us that green light, don't get me wrong I hope I'm wrong but I just don't see it happening
ChazzMatt said:
Won't happen the T-mobile variant G7. For the LG V30 H932, T-mobile not only stripped out the fastboot flash commands they also have different RSA encryption keys so you can't convert to another model (even temporarily) which has fastboot flash commands. They also did this for the LG G6 T-mobile, so I can't see them reversing course to help people who want to unlock bootloader and root.
Since back in May when we found the wonderful LG Oreo bootloader unlock exploit, every LG V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because they don't have fastboot flash commands and you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Click to expand...
Click to collapse
T-mo didnt demand this, If this was the case then all their devices would be the same way, I had the HTC10, None of the fastboot commands are stripped, everything is there.. you can even S/off and cross install.
and rebrand the phone........ If T-mo was at fault for the LG devices, then all would be the same way.. its only LG and LG only.. LG started doing that with the MM update on the V10 which screwed over everyone.
the only reason none of the other American devices outside the US unlocked version didnt do that.. because they didnt think anyone would be able to unlock it..
T-mo has always allowed you to unlock bootloader if OEM allows it...... This isnt T-mo its LG that has done it.. They dont want any US variant to have fastboot commands..
and since you found that Oreo Bug, you can be sure that futures devices and so on by LG will have that fixed...
This has always been LG that has done this to the American Market not US Carriers, Even the MOTO from T-mo is unlockable with full fastboot commands..................
Scotsman828 said:
the 710TM does have Fastboot commands, I've already played around with them, such as "fastboot getvar device-id", "fastboot oem unlocked" give the bootloader locked status, you can even flash with fastboot to unlock the bootloader with "unlock.bin". Once LG gives 710TM owners the green light, they will give us the unlock.bin
Click to expand...
Click to collapse
Fastboot commands are not fastboot flash commands.
All fastboot flash commands are stripped out. And T-Mobile has different RSA encryption, apparently per demand of T-Mobile.
T-Mobile LG G6, V30 and now G7.
---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------
Eliminater74 said:
T-mo didnt demand this, If this was the case then all their devices would be the same way,
I had the HTC10, None of the fastboot commands are stripped, everything is there.. you can even S/off and cross install.
and rebrand the phone........
T-mo has always allowed you to unlock bootloader if OEM allows it...... This isnt T-mo its LG that has done it.. They dont want any US variant to have fastboot commands..
and since you found that Oreo Bug, you can be sure that futures devices and so on by LG will have that fixed...
Click to expand...
Click to collapse
HTC 10 is 2016 phone. Things have changed since then. T-MOBILE is no longer dev friendly. You are living in the past.
T-Mobile even tweeted for the LG V30 you would NOT be able to unlock the bootloader. Yeah you can "fake" unlock it, but without fastboot flash commands you can't do anything with the "unlocked" bootloader. It's like having the keys to the car -- but there's no car.
We went through all this with the 2017 LG G6 and LG V30. Sorry you haven't kept up?
T-Mobile users who want root with V30 have to buy another North America variant and root it, and use on T-Mobile.
Yes, T-Mobile did demand the different RSA encryption or LG wouldn't have done it JUST for T-Mobile models.
Yes, LG stripped fastboot flash commands out of most of the North America carrier variants, but you can convert ALL those -- EXCEPT for the T-Mobile H932 -- to carrier unlocked model US998. The reason you can't do that with the T-Mobile H932 is because ONLY that model has different encryption keys than other North America variants. Why would LG do that for ONLY T-Mobile H932?
I used an unlock.bin from a V30 just to see if it would attempt to flash with "fastboot flash unlock unlock.bin", it attempted to flash but errored out because of wrong unlock.bin.
Guide: Returning to stock firmware + re-lock bootloader.
NOTE: following this guide will factory reset your phone so back up your data before hand.
Hi all, after having to do a fair bit of digging around last night in order to return my G7 to stock firmware i
figured i would make a all in one guide to make it a bit easier for people to follow!
First half of this guide is how to re-flash stock firmware:
1. Download LGUP here:Link
1.1 Download additional file we will need later: Link
1.2 Download stock KDZ file: Link
2. Install LGUP, after it has been installed extract the file from step 1.2 and place it here:
"C:\Program Files (x86)\LG Electronics\LGUP\model\common"
You will most likely have to create the common folder first and then place the file "LGUP_Common.dll" inside, this allows the LGUP software to recognise the device.
3. Next power down your device, once it is fully powered off hold the volume up key and insert the USB cable into your device
while continuing to hold volume up, continue to hold until your device enters download mode.
4. Open the LGUP software and drag the KDZ file into the file path section within the software, if your device is not showing
it means you dont have the correct drivers installed or haven't placed the .dll file from step 2 in the correct place.
5. Once the KDZ file is showing in LGUP simply click start and wait for the stock firmware to flash! Once it has completed
your device will reboot!
6. (Optional) download and install LG Bridge and check for any software updates after the flash has completed, OTA updates
can also be checked but in my experience it didnt show any updates where as LG Bridge did.
Second half of this guide will be how to re-lock the bootloader:
1. Download and install Android ADB + Fastboot drivers. The best guide I've found for this can be seen here:Link
2.Navigate to the folder where you have ADB and fastboot installed, usually this folder will be called platform tools.
hold shift and right click inside the folder then select "open powershell window here". Next make sure USB debugging is
enabled in developer settings and then head back to your powershell window and enter the following commands in order:
"adb reboot bootloader"
"fastboot oem lock"
"fastboot reboot"
3. Your phone will reboot and go through the usual first time start up, make sure to enable developer options again and
un-checking "OEM unlock". Your bootloader is now locked again!
If you followed the above steps you should now be back to complete stock! Enjoy
I think it's better to flash stock firmware first to avoid problems when relocking the bootloader, because locking the bootloader just erases /data and /cache, and if you have some modifications like root or twrp it could cause a bootloop.
What I do is first flash stock and then relock the bootloader, with that order you will prevent any problems after relocking.
mprovi_15 said:
I think it's better to flash stock firmware first to avoid problems when relocking the bootloader, because locking the bootloader just erases /data and /cache, and if you have some modifications like root or twrp it could cause a bootloop.
What I do is first flash stock and then relock the bootloader, with that order you will prevent any problems after relocking.
Click to expand...
Click to collapse
Thanks for the advice mate, I've updated the post and switched the order
Can you use this guide to flash different carrier firmware on device?
mrpickem said:
Can you use this guide to flash different carrier firmware on device?
Click to expand...
Click to collapse
You can always try! I would probably recommend sticking to the firmware from your carrier though just to be on the safe side. If worst comes to worst you can always use this guide again to re-flash your carrier specific firmware if you find you are having issues! Let me know how you get on if you do try or need any help
camy25695 said:
You can always try! I would probably recommend sticking to the firmware from your carrier though just to be on the safe side. If worst comes to worst you can always use this guide again to re-flash your carrier specific firmware if you find you are having issues! Let me know how you get on if you do try or need any help
Click to expand...
Click to collapse
Thanks
I have been reading a bit and apparently there are different modems used between carriers. I currently have an unlocked Tmobile device and was wanting to flash the unlocked firmware...just dont want to risk bricking the phone. The phone works ok with tmobile fw, just wanted to get rid of bloat since I am now using it on ATT prepaid. Can find no info where anyone has done this. I 've flashed several Galaxy phones (to diff f/w)recently and Moto G's a few years back and it worked great.
mrpickem said:
Thanks
I have been reading a bit and apparently there are different modems used between carriers. I currently have an unlocked Tmobile device and was wanting to flash the unlocked firmware...just dont want to risk bricking the phone. The phone works ok with tmobile fw, just wanted to get rid of bloat since I am now using it on ATT prepaid. Can find no info where anyone has done this. I 've flashed several Galaxy phones (to diff f/w)recently and Moto G's a few years back and it worked great.
Click to expand...
Click to collapse
I know it's possible to flash the boot.img seperate, as I've done that already myself but I'm unsure about flashing a different modem. I imagine the process will be very similar to flashing the boot but I'd need to do some digging and find out exactly! Even if you could there's no guarantee that it would work. I'll do some digging and see what I can find and get back to you!
mrpickem said:
I have been reading a bit and apparently there are different modems used between carriers. I currently have an unlocked Tmobile device and was wanting to flash the unlocked firmware...just dont want to risk bricking the phone.
The phone works ok with tmobile fw, just wanted to get rid of bloat since I am now using it on ATT prepaid. Can find no info where anyone has done this. I 've flashed several Galaxy phones (to diff f/w)recently and Moto G's a few years back and it worked great.
Click to expand...
Click to collapse
Assuming LG has made the same decisions for the G7 as they did for the V30, the answer is no.
At least on the V30 series, T-mobile variant can NOT be flashed to anything else because it has different RSA encryption keys from any other V30 phone. This is why back in May when we found the wonderful LG Oreo bootloader unlock exploit, every V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Someone with a G7 came in to the V30 Frankenstein thread to ask if it works on G7, but that seems like something that should be discussed in this forum.
ChazzMatt said:
Assuming LG has made the same decisions for the G7 as they did for the V30, the answer is no.
At least on the V30 series, T-mobile variant can NOT be flashed to anything else because it has different RSA encryption keys from any other V30 phone. This is why back in May when we found the wonderful LG Oreo bootloader unlock exploit, every V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Someone with a G7 came in to the V30 Frankenstein thread to ask if it works on G7, but that seems like something that should be discussed in this forum.
Click to expand...
Click to collapse
Thanks for the reply and that's kinda what what I been reading, just not as much detail. Thanks for detailed explanation
ChazzMatt said:
Assuming LG has made the same decisions for the G7 as they did for the V30, the answer is no.
At least on the V30 series, T-mobile variant can NOT be flashed to anything else because it has different RSA encryption keys from any other V30 phone. This is why back in May when we found the wonderful LG Oreo bootloader unlock exploit, every V30/V30+/V30S on the planet can now be bootloader unlocked and rooted -- EXCEPT for the the T-mobile H932. Because you need Oreo and you need (at least temporarily) fastboot flash commands.
So, all the carrier unlocked US998, European H930 and even the dual SIM H930DS (which have fastboot flash commands) can immediately be bootloader unlocked and rooted. For the others -- like the North American variants AT&T H931, Canadian H933, Verizon VS996, Sprint LS998 -- you first flash the carrier unlocked US998 firmware (aka Frankenstein) over those models to "convert" them to US998 to add back fastboot flash commands. We use dev patched LGUP. Then, after bootloader unlock and root, Sprint and Verizon users often flash back either all or part of their firmware to get back features or LTE bands (Sprint especially). They are still rooted, they still have TWRP. As a result of this, we suddenly now have tons of ROMs and custom kernels are under development.
But T-mobile H932 users are locked out of this development bonanza, because you can't cross flash anything without bricking the phone. I would assume the same for G7? T-mobile must have demanded this, because all the other North American V30 variants share the same RSA encryption keys which make cross flashing possible. If T-mobile demanded it for their V30, seems they would do the same for the next phone also.
Someone with a G7 came in to the V30 Frankenstein thread to ask if it works on G7, but that seems like something that should be discussed in this forum.
Click to expand...
Click to collapse
Ok what about flashing the European LMG710EM firmware onto the Sprint G7? Would i risk bricking my device? Im trying to find a solution to unlocking my sprint phone
mastervideogamer79 said:
Ok what about flashing the European LMG710EM firmware onto the Sprint G7? Would i risk bricking my device? Im trying to find a solution to unlocking my sprint phone
Click to expand...
Click to collapse
did you try flashing G710EM firmware in the sprint g7? i also have a sprint variant and want to unlock it.
UPDATE: just tried to flash it but lg up doesnt even start flashing the kdz file, it gives "LAF WRITE PROTECTION" and "Cross flash is not supported" messages
luckily phone is working just fine with the original software, i mean it didnt bricked the phone since it didnt even started to flash.
in other post i saw a user that tried flashing tmobile firmware with lg v20 dll and bricked his sprint g7
elmy24 said:
did you try flashing G710EM firmware in the sprint g7? i also have a sprint variant and want to unlock it.
UPDATE: just tried to flash it but lg up doesnt even start flashing the kdz file, it gives "LAF WRITE PROTECTION" and "Cross flash is not supported" messages
luckily phone is working just fine with the original software, i mean it didnt bricked the phone since it didnt even started to flash.
in other post i saw a user that tried flashing tmobile firmware with lg v20 dll and bricked his sprint g7
Click to expand...
Click to collapse
Oh man thats why I didnt want to risk it but thanks for trying. Haven't found a way to unlock it, phones just sitting there
Hi everyone,No-one haven't successful crossflash the lg g7,I have the verizon g7 variant I would like to flash it to a different carrier.,
elmy24 said:
did you try flashing G710EM firmware in the sprint g7? i also have a sprint variant and want to unlock it.
UPDATE: just tried to flash it but lg up doesnt even start flashing the kdz file, it gives "LAF WRITE PROTECTION" and "Cross flash is not supported" messages
luckily phone is working just fine with the original software, i mean it didnt bricked the phone since it didnt even started to flash.
in other post i saw a user that tried flashing tmobile firmware with lg v20 dll and bricked his sprint g7
Click to expand...
Click to collapse
I am getting same error. I have sprint LG g7. Trying to flash canadian AWM rom.
I followed this tutorial in my LG G7 variant model LM-G710EMW and works. Now, I'm downloading the specific firmware in lg-firmwares.com to install with this method.
I bought my LG G7 in Brazil, with CLARO mobile operator and now I have a LG G7 without bond. Thanks for this tutorial!
With this guide warranty come back?
mastervideogamer79 said:
Oh man thats why I didnt want to risk it but thanks for trying. Haven't found a way to unlock it, phones just sitting there
Click to expand...
Click to collapse
akyl001 said:
I am getting same error. I have sprint LG g7. Trying to flash canadian AWM rom.
Click to expand...
Click to collapse
just found a way to unlock the sprint variant by flashing european rom
elmy24 said:
just found a way to unlock the sprint variant by flashing european rom
Click to expand...
Click to collapse
You should make a post verifying the way you did it and giving proof of this happening. If you do it you will help a lot of people, and maybe it will help other variants to reach root.
How can I solve the "unsecure flashing image to secure flashing device" problem?
Eltoniz said:
How can I solve the "unsecure flashing image to secure flashing device" problem?
Click to expand...
Click to collapse
model number?
software version?
is it KDZ or TOT firmware?
So I just paid off my Sprint OnePlus 7 Pro 5G. I got off the phone with them today and it should be SIM unlocked by this time tomorrow.
I have a few questions for anyone who might know the answers.
1. Will this enable the grayed out "OEM Unlocking" In developer options so I can get an unlock bin from OnePlus? If not is it currently possible to enable the grayed out "OEM Unlocking" option in developer options? (For example on my OnePlus Nord N200 a simple adb fastboot command removing an app enabled it and gave me the ability to toggle the option.
2. Looking around it looks like there isn't much support for the Sprint version of this phone. Are there custom ROMs that work universally that are fairly established in the community that will work on all carriers?
3. Is it possible to get a custom ROM or Root on the Sprint OnePlus 7 Pro 5G with out an unlocked bootloader?
4. Is it possible to flash from a Sprint version to a T Mobile version?
Main reason here is come this time next year Sprints old network will be fully shut down and I want to be able to use this Sprint branded phone on other networks and feel like I'll need an unlocked bootloader, root, or a custom rom to do so.
xVoidx said:
So I just paid off my Sprint OnePlus 7 Pro 5G. I got off the phone with them today and it should be SIM unlocked by this time tomorrow.
I have a few questions for anyone who might know the answers.
1. Will this enable the grayed out "OEM Unlocking" In developer options so I can get an unlock bin from OnePlus? If not is it currently possible to enable the grayed out "OEM Unlocking" option in developer options? (For example on my OnePlus Nord N200 a simple adb fastboot command removing an app enabled it and gave me the ability to toggle the option.
2. Looking around it looks like there isn't much support for the Sprint version of this phone. Are there custom ROMs that work universally that are fairly established in the community that will work on all carriers?
3. Is it possible to get a custom ROM or Root on the Sprint OnePlus 7 Pro 5G with out an unlocked bootloader?
4. Is it possible to flash from a Sprint version to a T Mobile version?
Main reason here is come this time next year Sprints old network will be fully shut down and I want to be able to use this Sprint branded phone on other networks and feel like I'll need an unlocked bootloader, root, or a custom rom to do so.
Click to expand...
Click to collapse
1. It's possible to unlock the bootloader using a patched MSM tool or converting to the EU 5G firmware and doing it the old fashioned traditional method.
2. There is no support at all. Custom ROMs can and will install but most will either bootloop or face modem, location and rotation issues. I've tried porting tons of roms at this point and nothing has worked. GSIs though do work but they come with their set of issues.
3. You can root the stock OOS 10 firmware, but fully functional custom ROMs are out of the question. BUT rooting with a LOCKED bootloader is IMPOSSIBLE.
4. No. Due to a different partition scheme and modem, you cannot convert to the international or T-Mobile firmware.
I've made a little write up linked here (
https://www.reddit.com/r/OnePlus7Pro/comments/pnpvjx
). If you would like to know as much as possible about this device.
Thanks for all the info this really helps.
So is it not possible then to even use this device on T-Mobiles network?
Assuming its unlocked(By Sprint or so they say it is now) the hardware should be able to connect to T Mobiles 4G network and maybe the 5G?
xVoidx said:
Thanks for all the info this really helps.
So is it not possible then to even use this device on T-Mobiles network?
Assuming its unlocked(By Sprint or so they say it is now) the hardware should be able to connect to T Mobiles 4G network and maybe the 5G?
Click to expand...
Click to collapse
You might be able to use it on T-Mobile's LTE/4G network but not 5G. I can't confirm as I live in Canada though.
hey!
can confirm, this version sucks, I have this phone and I just totally bricked it lol
I'm able to access fastboot but I'm not able to find any images I can use to get the default OS back. I just want to restore it to factory settings, but alas :\
xVoidx said:
Thanks for all the info this really helps.
So is it not possible then to even use this device on T-Mobiles network?
Assuming its unlocked(By Sprint or so they say it is now) the hardware should be able to connect to T Mobiles 4G network and maybe the 5G?
Click to expand...
Click to collapse
also, I am able to use it on t-mobile's network, that's what I'm doing right now
There is a custom ROM for the 5g variant... YAAP
Gazdre84 said:
There is a custom ROM for the 5g variant... YAAP
Click to expand...
Click to collapse
I currently have this variant which is the 5g version of sprint, could you tell me which is the custom rom and what are the steps please