Related
I am currently switching our Cricket phones over to Tracfone with their BYOP kits. My daughters' phones are both stock and their phones immediately recognized the new sim. (However, their phones are LG Risio)
My phone has AlexOS 5.0, after trying unsuccessfully the first time to get it to recognize Tracfone's sim, I did factory reset from TWRP. Still no luck.
Do I need to flash back to stock? If so where can I get it?
Also, if stock is currently only on 5.x can that even be flashed over 6.x (downgraded)?
Thanks
ETA - Checked sim card in other phone and it is fine. So it's definitely my phone.
Looks like maybe Mobile Upgrade Q is the answer? Would that make me lose TWRP?
If you update using Mobile Upgrade, you'll lose root, TWRP, and go back to stock.
Does the Idol 3 need to be network unlocked in order to work with Tracfone?
I think so, we have the unlock code directly from Cricket. The problem is that the phone simply says "No Sim" with the Tracfone sim, the others phones immediately asked for an unlock code after switching sims.
Try a different sim card in the phone to see if the phone prompt's for the unlock code? If not prompted, the phone may have to be flashed back to stock.
This is an unlocked T-Mobile G5, but why have a special ROM for unlocked phone? I wonder if I flash other ROMs, I could lose the unlock. Anyone have any problem rooting and install twrp?
Conclusion after a month long discussion:
G5 with H83020i_un ROM is NOT factory unlock. Upgrading or downgrading will result in SIM lock to T-Mobile, period.
Once locked, it can only be unlocked by T-Mobile customers via T-Mobile unlocked app. Some has to go thru T-Mobile customer service and request SIM unlock by adding IMEI to their database.
I bought 6 (New to New other) unlocked H830 and 2 has the hacked ROM H83020i_un and 4 were completely locked to T-Mobile. Yes, those stupid sellers on ebay just keep sending lock phones as unlocked phone! Good luck getting a unlocked one.
No, you cannot install TWRP or root this version.
I ended up returning mine.
You shouldn't lose the unlock by flashing another ROM.
A ROM isn't just about 'locked or unlocked'. The ROM is the operating system. While it will still be Android no matter what you do, different ROMs are modified differently to provide additional features, or more control over the settings or just a slightly different user interface.
This has NOTHING to do with the phone being unlocked for use on any GSM network.
For example some people want to be able to control the CPU processor speed on the phone more. Some ROM's give you that control built into the settings and use customer kernels that allow the CPU to run faster than it does running stock. Other people just like a more simple UI that you get on base Android ROM's (rather than some of the overlays LG puts on)
Skipjacks said:
You shouldn't lose the unlock by flashing another ROM.
A ROM isn't just about 'locked or unlocked'. The ROM is the operating system. While it will still be Android no matter what you do, different ROMs are modified differently to provide additional features, or more control over the settings or just a slightly different user interface.
This has NOTHING to do with the phone being unlocked for use on any GSM network.
For example some people want to be able to control the CPU processor speed on the phone more. Some ROM's give you that control built into the settings and use customer kernels that allow the CPU to run faster than it does running stock. Other people just like a more simple UI that you get on base Android ROM's (rather than some of the overlays LG puts on)
Click to expand...
Click to collapse
I can't confirm this personally, but @autoprime mentioned on IRC that everyone who tried flashing other KDZs over this specific firmware lost the SIM unlock.
BehindTheMath said:
I can't confirm this personally, but @autoprime mentioned on IRC that everyone who tried flashing other KDZs over this specific firmware lost the SIM unlock.
Click to expand...
Click to collapse
So we can't flash this device?
dkyu said:
So we can't flash this device?
Click to expand...
Click to collapse
Well, technically you can, but as of now it sounds like you'd lose the SIM unlock.
BehindTheMath said:
Well, technically you can, but as of now it sounds like you'd lose the SIM unlock.
Click to expand...
Click to collapse
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
It seems that this is not a regular unlock. When I open the T-Mobile app, it says the phone is still locked, but it works anyway.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
I just tried downgrading to 20A and lost the SIM unlock.
BehindTheMath said:
I just tried downgrading to 20A and lost the SIM unlock.
Click to expand...
Click to collapse
Did you confirm that by trying the phone with a non T Mobile SIM on a different network? Or did you just let the T Mobile unlocker app tell you it's still locked?
The app isn't the most reliable thing in the world. It's known to say it's not unlocked when it is or that it can't be unlocked when it already is. Etc etc...
Unlocking it manually (through codes, ADB, root, etc....) messes with the unlocker app. But the unlock itself should still be valid.
Skipjacks said:
Did you confirm that by trying the phone with a non T Mobile SIM on a different network? Or did you just let the T Mobile unlocker app tell you it's still locked?
The app isn't the most reliable thing in the world. It's known to say it's not unlocked when it is or that it can't be unlocked when it already is. Etc etc...
Unlocking it manually (through codes, ADB, root, etc....) messes with the unlocker app. But the unlock itself should still be valid.
Click to expand...
Click to collapse
I took the active H2o (At&t MVNO) SIM from my current device and tried it in this one. I could not make phone calls or access data, both in stock 20A and Resurrection Remix.
BehindTheMath said:
I took the active H2o (At&t MVNO) SIM from my current device and tried it in this one. I could not make phone calls or access data, both in stock 20A and Resurrection Remix.
Click to expand...
Click to collapse
that's sucks.
I wonder if you can actually get an unlock code to unlock the phone now.
dkyu said:
that's sucks.
I wonder if you can actually get an unlock code to unlock the phone now.
Click to expand...
Click to collapse
If I'm not mistaken, you can't unlock this phone with an unlock code.
dksoni411 said:
I don't know when people will understand that it has nothing to do with sim unlock. I have T-Mobile unlocked sim lg g5 and flashed roms, custom and stock both several times and never had any problem with sim lock stuffs. Just install twrp, root, flash custom rom, there will never hurt anything in your phone.
Click to expand...
Click to collapse
Maybe it is something to the specific phones people are getting from the ebay seller. They are being sold as new yet are not factory sealed and missing the Tmo sim card. People are claiming Android pay doesn't work and the phone isn't rooted. A new out of the box phone shouldn't have that issue. So something isn't necessarily kosher.
Guys, I have the same version (H83020i_un) and it has April security update and T-Mobile has different version #s on their website. I have checked for update, but nothing came up. So I can't get T-Mobile updates?
The software version H83020i_un is apparently not an official ROM released by T Mobile or LG.
There is a lot of speculation on Slickdeals (a website for coupons and stuff where this eBay deal has been discussed quite a bit) that the unlock was done by flashing a modified ROM. If so that would explain why flashing a new ROM loses the unlock.
Additionally people are saying that Android Pay doesn't work on this phone with that software update, presumably because it's not official firmware. I've never used Android Pay so I have no idea if it works or not.
All in all if you have the H83020i_un software and bought the phone 'new' I think you got conned. It's not new and that seems to be unofficial software.
I spent a lot of time, with help from @autoprime, trying to figure out where the unlock is stored. I was able to dump the partitions from 20i_un using the method here. After I downgraded to 20A and flashed TWRP, I flashed back all the 20i_un partitions (besides recovery, cache, and userdata), and it still wasn't unlocked. So I'm baffled as to how the unlock works.
Skipjacks said:
The software version H83020i_un is apparently not an official ROM released by T Mobile or LG.
There is a lot of speculation on Slickdeals (a website for coupons and stuff where this eBay deal has been discussed quite a bit) that the unlock was done by flashing a modified ROM. If so that would explain why flashing a new ROM loses the unlock.
Additionally people are saying that Android Pay doesn't work on this phone with that software update, presumably because it's not official firmware. I've never used Android Pay so I have no idea if it works or not.
All in all if you have the H83020i_un software and bought the phone 'new' I think you got conned. It's not new and that seems to be unofficial software.
Click to expand...
Click to collapse
I see. It will be used as a second device, so it is fine. I flashed the phone with stock T-Mobile H83020a, then got few OTA updates. Now my phone has H83020i, but T-Mobile's page(below) shows an "f" version as the latest. So is the H83020i, the latest update or not? Also would be good if anyone with real T-Mobile unit could chime in.
https://support.t-mobile.com/docs/DOC-30673
BehindTheMath said:
I spent a lot of time, with help from @autoprime, trying to figure out where the unlock is stored. I was able to dump the partitions from 20i_un using the method here. After I downgraded to 20A and flashed TWRP, I flashed back all the 20i_un partitions (besides recovery, cache, and userdata), and it still wasn't unlocked. So I'm baffled as to how the unlock works.
Click to expand...
Click to collapse
And there is no way to root the phone without downgrading to 20A right?
Charkatak said:
I see. It will be used as a second device, so it is fine. I flashed the phone with stock T-Mobile H83020a, then got few OTA updates. Now my phone has H83020i, but T-Mobile's page(below) shows an "f" version as the latest. So is the H83020i, the latest update or not? Also would be good if anyone with real T-Mobile unit could chime in.
https://support.t-mobile.com/docs/DOC-30673
Click to expand...
Click to collapse
Looks like 20i is the latest.
https://forum.xda-developers.com/tm...ock-h830-20i-rom-flashable-zips-imgs-t3609735
dkyu said:
And there is no way to root the phone without downgrading to 20A right?
Click to expand...
Click to collapse
Correct.
BehindTheMath said:
Looks like 20i is the latest.
https://forum.xda-developers.com/tm...ock-h830-20i-rom-flashable-zips-imgs-t3609735
Correct.
Click to expand...
Click to collapse
So if 20i is the latest, then it is possible that T-Mobile's variant of the phone could have a different model # than H830...
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?
Hi All,
Been at this for several hours today and feeling a bit frustrated. Here's the context.
I bought a used Verizon Galaxy Note 10 and took it to another country.
I arrived and put a sim card in *(the phone is intended to stay here)
4G signal appeared and text messages came in
Phone blocked signal and said "sorry, your device cannot be activated on another Network right now" then it says to call Verizon.
I call Verizon and ask how to unlock.
After transferring to multiple agents, the answer is that the phone is not locked in their system and that upon inserting a SIM from another carrier, I should be prompted to put in a code and it will be "00000000" to unlock the phone
The phone never presents this option and is perpetually unable to activate because of this sim lock.
At this point, I started reading up on how I could get around this and settled on using odin to flash firmware for a different carrier and maybe having to flash the SM-N970U1 packages because that should allow me to have different stock firmware.
So I proceed to download various different images.
Here is the TMB image for SM-N970U that I downloaded:
https://samfw.com/firmware/SM-N970U/TMB/N970USQU6FUBH
I also figured maybe I would be able to flash the verizon base image and get around this lock:
https://samfw.com/firmware/SM-N970U/VZW/N970USQU6FUCD
So then I proceed to use Odin3_v3.14.4 and place all of the 4 files in their corresponding fields in odin. The file list is as follows for one of the packages:
BL_N970USQU6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_N970USQU6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
CP_N970USQU6FUD9_CP19049000_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OMC_OYN_N970UOYN6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
I click start, the phone is recognized and then the flashing appears to occur successfully until it says pass at the end.
I reboot the phone and I notice right away that the signal is present, but then disappears and as the phone initializes the VERIZON message appears again.
Immediately I'm thinking, ok, I've just reflashed it with the TMobile image but the phone boots and says verizon and the sim lock is still there, so I probably didn't do something right.
So I factory reset, try again, no changes, I try adding the USERDATA and it also does nothing different.
At this point I'm willing to try the U1 firmware, so I download from here:
https://forum.xda-developers.com/t/n970u-and-n970u1-firmware-links-here.3957705/
But when I run the odin flash, I get model mismatch, yet the thread says they're compatible as U1 is just the samsung unlocked version. so I try the odin patch b found here:
https://odindownload.club/download/197/Odin3-v3.14.1-3B-PatcheD.zip
And it fails to write.
I am in desperate need of help as I've been unable to find more specific information, typically in threads people may say they've resolved the issue, but then they don't actually indicate what steps they took, or any of the details surrounding the resolution. If I can get help getting this resolved, I can document the exact steps i've taken in explicit detail so that others can follow them and achieve the same result.
Update:
Downloaded FRIJA to get the latest firmware, am going to explore doing a nand erase and repartition, followed by flashing tmobile firmware to see if that gets around it.
following:
https://technastic.com/odin-nand-erase-samsung/
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Verizon has a 6 month unlock policy. if the phone is free of debt and older than 6 months it should be automatically unlocked. phone them, you bought the phone in good faith.
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
That's why I am thinking of wiping the NVRAM and just re-partitioning. Then I'll flash a non-verizon system onto it. Could be that this resolves it.
Thoughts?
3mel said:
Verizon has a 6 month unlock policy. if the phone is free of debt and older than 6 months it should be automatically unlocked. phone them, you bought the phone in good faith.
Click to expand...
Click to collapse
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
4rg3ntum said:
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
Click to expand...
Click to collapse
With AT&T they give you requested then they gave you an unlock code, it's not automatic. At least it was like this a few years back.
4rg3ntum said:
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
Click to expand...
Click to collapse
sorry yeah, 60 days is the right period.
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
So this appears to be true.
I loaded up ADB and turned on USB debugging and started passing shell commands through and found these files in the system with nvram in the name:
/sys/module/dhd/parameters/nvram_path
/vendor/firmware/nvram.txt_ES03_semco_b0
/vendor/firmware/nvram.txt_1rh_es13_b0
/vendor/firmware/nvram.txt_CS01_semco_b1
/vendor/firmware/nvram.txt_ES02_semco_b0
/vendor/firmware/nvram.txt_1rh_es43_b1
/vendor/firmware/nvram.txt_1rh_es41_b1
/vendor/firmware/nvram.txt_1rh_es32_b0
/vendor/firmware/nvram.txt_ES00_semco_b0
/vendor/firmware/nvram.txt_ES01_semco_b0
/vendor/firmware/nvram.txt_1rh_es12_b0
/vendor/firmware/nvram.txt_1rh_es42_b1
/vendor/firmware/nvram.txt_1rh_es11_b0
Makes me wonder if the value for locked/unlocked is editable in one of those files.
a sample of what is in the /vendor/firmware/nvram.txt_ES03_semco_b0 file:
### RSDB mode Parameters(Both core are active)
## 2g normal:15dB airplane:14dB
#slice/1/grip_rsdb_dynsar_2g=0xbcbc
#slice/1/grip_rsdb_dynsar_2g_2=0xb8b8
## 5g normal:13dB airplane:12dB
#grip_rsdb_dynsar_5g=0xb4b4
#grip_rsdb_dynsar_5g_2=0xb0b0
#
### FCC Mode: 10dB
#slice/1/fccpwrch12=0x28
#slice/1/fccpwrch13=0x28
In any case I have an issue that I can't seem to resolve. Every guide I have found about how to change carrier firmware is pretty straightforward. Yet when I flash the firmware successfully through odin for say, the sprint version of the phone, upon reboot, in about phone still says VZW, which basically tells me the phone isn't actually flashing.
I need to understand why I can't seem to get it to have another carrier's firmware. What am I doing wrong?
jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
Maybe I can edit this with ADB?
I have seen several forums where people with the same error message simply flashed another carriers firmware onto the phone and were able to get around it.
Here is someone saying they tried the U1 firmware and it gave them the option to put in an unlock code:
https://forum.xda-developers.com/t/is-verizon-locking-s10.3908683/post-80813873
Every time I try to flash the U1 firmware odin tells me model mismatch.
Update:
I flashed the latest available ATT version of U1 firmware from here:
https://samfw.com/firmware/SM-N970U1/ATT/N970U1UEU6FUDA
Using Odin patch 3B downloaded from here:
https://www.droidmirror.com/downloading/download-odin3_v3-13-1_3b_patched-zip
Having tried many U firmware + USERDATA from different carriers and never was able to get it to say anything other VZW in the about phone section.
By going to the U1 version I was able to get the unlock code portion to pop up when inserting the sim card, the phone also claims it's model number is SM-N970U1 instead of SM-N970U now.
The code Verizon gave me on the phone 0000 0000 flat out DOESN'T work. I called again today and they had their manager use a tool to provide an unlock code because the "unlock" button in their system didn't appear for my IMEI.
That system said the unlock code is 0000 0000 just like the tech the previous day. So now, they're transferring me to the advanced technical support, but somehow I doubt they will give me a code.
In any case, what I would rather do is go through ADB and try to get some binaries or text files out (may require root for these files) and get the unlock code from the device itself.
I wish this thread was more active because there are some good opportunities here to explore the OS itself and the files in it as well as tools that can be used to read the binary.
Spoke with "Advanced" support at verizon. They had no way to generate a code to unlock the device. Basically Verizon's systems didn't automatically generate an unlock code after the previous owners had the phone activated for the minimum 60 days. Because the phone was a prepaid phone and not a post paid phone, their system deleted the history of the of the prepaid account after a certain period of time when the previous owner had sold the phone to the repair shop and it sat there for months.
BASICALLY, Verizon phones are uniquely equipped with a block that prevent legitimate purchasers of various types from being able to use their devices as they hold everyone hostage with their network locking.
It looks like I can't root the device either because of the oem unlock option not being present and the workaround of changing the date not presenting the option.
At this point I'm looking to root the device so I can inspect the OS
4rg3ntum said:
It looks like I can't root the device either because of the oem unlock option not being present and the workaround of changing the date not presenting the option.
At this point I'm looking to root the device so I can inspect the OS
Click to expand...
Click to collapse
Hello I came across your thread because I am having the same issue. I think mine is similar because thus phone was a replacement through asurion/verizon. It also says its unlocked when verszon looks and when asurion looks, but I do not have service for more than 10 secind with my new AT&T Sim. Have you found anything new?.
I also looked into rooting the phone but I don't plan to keep this phone and if I want to do the trade in process and they see the root on the back end I will not receive the trade in money.
TomHanks92 said:
Hello I came across your thread because I am having the same issue. I think mine is similar because thus phone was a replacement through asurion/verizon. It also says its unlocked when verszon looks and when asurion looks, but I do not have service for more than 10 secind with my new AT&T Sim. Have you found anything new?.
I also looked into rooting the phone but I don't plan to keep this phone and if I want to do the trade in process and they see the root on the back end I will not receive the trade in money.
Click to expand...
Click to collapse
If Verizon says the phone is unlocked, make sure to Flash the U package with Verizon bloat. Connect phone to Wifi and the unlock should happen. They only seem to unlock when on the Verizon bloat U package. Anything other than that and the phone stays locked. Once it unlocks you can flash back to whatever you want.
Question. I have switched my carrier from Verizon to T-Mobile. How do I remove the Big Red branding/splash screen/apps and replace them with the T-Mobile stuff? Can it be done with a factory reset or do I need to go deeper?
Thanks
If you have a T-Mobile sim. Just call them and have them reprovision your phone. All they will do is have you turn it off, they will send a new signal. Once you turn it on, it should update to all T-Mobile.. I forgot on question. Is this a factory unlocked version? If so I do not think you will get much T-Mobile apps. I know I do not have that annoying boot screen, and that is how I like it..
I have a VZW branded device. I want to get rid if all the Big Red stuff. I'm even contemplating flashing the U1 firmware or the latest Tmo or their CSC. I just want to make sure I get the security updates ss I should and not get them from Verizon.
FernBch said:
I have a VZW branded device. I want to get rid if all the Big Red stuff. I'm even contemplating flashing the U1 firmware or the latest Tmo or their CSC. I just want to make sure I get the security updates ss I should and not get them from Verizon.
Click to expand...
Click to collapse
If you have a Verizon Branded, but a T-mobile sim, do as I suggested, or you should be able to flash the U1 firmware
Will do. Thanks
Learned something.
Samsung BYOD carrier update only works with carrier unlocked devices bought directly from Samsung. If you change carriers and want either their bloat or no bloat you must flash via Odin. Nice part is if you flash the unlocked firmware you can uninstall all the bloat. The jury is still out on OTAs....