There's been a lot of new users picking up cheap G7 ThinQ G710ULM (US Unlocked) versions on ebay lately, then getting frustrated when they find out it a hacked Sprint version (G710pm).
I'm finding posts from new users on different corners of the internet, Telegram groups, Reddit, etc, usually saying that they can't upgrade from Oreo and their device is missing a serial number, and the IMEI is actually from the Sprint pm version. I couldn't find a lot of info in one place about these handsets, so I'm starting this thread to discuss them. There's a good chance any ULM on ebay for a good price is one of these. I bought 3 of them for different people from different sellers, and this was the case on all of them. I almost returned them all and gave up until I did some research and found out THIS ISN'T NECESSARILY A BAD THING!
In fact, it may actually be beneficial compared to the real ULM version in some ways. First of all, it WILL work with T-mobile USA just fine. The bands all seem to work, it even supports WiFi calling and VOLTE, and there's a chance even B71 will work (although this isn't 100% verified, it shows up as an available band to test in the service menu). The real ULM supposedly skips this band. Some people even say the real ULM version is also missing bands for AT&T, but the PM crossflashed version seems to connect to them (this might be an isolated incident or fluke, but at least one redditor claims this was his experience). I'm still not clear on how the unlocked official US version can be missing AT&T bands, so I'd love for other people to maybe chime in here with their experiences.
Yes, you can update to Pie. The OTA updates won't work, likely because of the missing serial number. On that note, I'd LOVE to find out why that is. Can anyone explain why these crossflashed devices are missing the SN? Does that happen on other crossflashed devices?
Either way, follow this guide here:
https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Note, this guide was written for flashing a European variant, but the same steps apply. Just choose a kdz for the ULM variant from here: https://lg-firmwares.com/lg-lmg710ulm-firmwares/#tab=firmwares
^ I recommend the latest Google Fi firmware version, which is G710ULM20e_00_NAO_US_OP_1010.kdz , from 2019-11-14
There is a more recent version from BPT, but it is unclear what that firmware is for. BPT seems to be some sort of regional carrier, so you are better off with the regular USA or Fi version.
Also note, you may need to use 7zip to extract the dll file from that guide. That took me a while to figure out, as Windows explorer throws an error with it. Once you finish, your phone will reboot with a shiny new (relatively) up to date Pie firmware!
There. You now saved yourself a few bucks and got a solid phone. Feel free to share your experiences with the handset here.
Dishe said:
There's been a lot of new users picking up cheap G7 ThinQ G710ULM (US Unlocked) versions on ebay lately, then getting frustrated when they find out it a hacked Sprint version (G710pm).
I'm finding posts from new users on different corners of the internet, Telegram groups, Reddit, etc, usually saying that they can't upgrade from Oreo and their device is missing a serial number, and the IMEI is actually from the Sprint pm version. I couldn't find a lot of info in one place about these handsets, so I'm starting this thread to discuss them. There's a good chance any ULM on ebay for a good price is one of these. I bought 3 of them for different people from different sellers, and this was the case on all of them. I almost returned them all and gave up until I did some research and found out THIS ISN'T NECESSARILY A BAD THING!
In fact, it may actually be beneficial compared to the real ULM version in some ways. First of all, it WILL work with T-mobile USA just fine. The bands all seem to work, it even supports WiFi calling and VOLTE, and there's a chance even B71 will work (although this isn't 100% verified, it shows up as an available band to test in the service menu). The real ULM supposedly skips this band. Some people even say the real ULM version is also missing bands for AT&T, but the PM crossflashed version seems to connect to them (this might be an isolated incident or fluke, but at least one redditor claims this was his experience). I'm still not clear on how the unlocked official US version can be missing AT&T bands, so I'd love for other people to maybe chime in here with their experiences.
Yes, you can update to Pie. The OTA updates won't work, likely because of the missing serial number. On that note, I'd LOVE to find out why that is. Can anyone explain why these crossflashed devices are missing the SN? Does that happen on other crossflashed devices?
Either way, follow this guide here:
https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Note, this guide was written for flashing a European variant, but the same steps apply. Just choose a kdz for the ULM variant from here: https://lg-firmwares.com/lg-lmg710ulm-firmwares/#tab=firmwares
^ I recommend the latest Google Fi firmware version, which is G710ULM20e_00_NAO_US_OP_1010.kdz , from 2019-11-14
There is a more recent version from BPT, but it is unclear what that firmware is for. BPT seems to be some sort of regional carrier, so you are better off with the regular USA or Fi version.
Also note, you may need to use 7zip to extract the dll file from that guide. That took me a while to figure out, as Windows explorer throws an error with it. Once you finish, your phone will reboot with a shiny new (relatively) up to date Pie firmware!
There. You now saved yourself a few bucks and got a solid phone. Feel free to share your experiences with the handset here.
Click to expand...
Click to collapse
The devices lose the s/n and possibly imei because people are flashing using lgup 1.14 dev version which causes issues with nvdata.
Lgup 1.15 fixes this when you go back to oreo then update to pie.
Also crossflashed devices do not get ota because lgup marks these devices as crossflashed in nvdata using a 0x01 value for certified_device
loonycgb2 said:
The devices lose the s/n and possibly imei because people are flashing using lgup 1.14 dev version which causes issues with nvdata.
Click to expand...
Click to collapse
Wow, that's some good info right there, thank you for sharing!
Hmm- messing with nvdata though? So you're saying the SN missing is some sort of accident or goof? That doesn't sound so cool. Should I be concerned anything else is messed up? There's a ton of these in the wild now and it seems the SN is the only weird side effect that has been noticed.
As far as I know the IMEI is fine (looking it up reveals it is a PM imei, which is correct, and it does work with voice over Wifi and VOLTE, which I think wouldn't work if the IMEI was messed up). In fact, it's interesting because when that screen loads in Settings>About, etc, it shows "checking" under S/N, then checking goes away and it comes back blank. None of the other fields seem to need any sort of checking first. There's something fishy about how the S/N is stored that it has to check it first and then error out.
Lgup 1.15 fixes this when you go back to oreo then update to pie.
Click to expand...
Click to collapse
Hmm. It came with Oreo, and I used 1.15 to flash to Pie. So you're saying I should flash another Oreo kdz with my LGUP and it will magically fix any corrupt NVdata?
Also crossflashed devices do not get ota because lgup marks these devices as crossflashed in nvdata using a 0x01 value for certified_device
Click to expand...
Click to collapse
Oh, that is unfortunate. And that value stays with it forever, even if you go back to it's native firmware? I'm assuming that value can't be manipulated with any of the tools we have available.
Thank you so much for sharing this knowledge. Any insight on how the bands work? Is that from nvdata as well, and completely independent of firmware? So essentially, I have whatever band support a G710pm has? Or perhaps was it manipulated by the seller/refurbisher, who possibly used some nvram voodoo tricks which killed the S/N as a result?
Even tho the s/n is blank and at time if you try to show the imei it might also be blank, it is still stored internally and not lost forever.
There is multiple oreo's which for ulm is 10g and 11g, but i would have said flash to the original firmware but you cannot as sprint kdz is not available and the people who have an Original firmware still on device cannot or will not back it up for us.
The value for certified device returns to normal when flashed to the original firmware as lgup has an internal database used for identifying models.
As far as the basebands, all g7 thinq's come with the same bands no matter the firmware or region. The difference is the kdz gives band priority to the ones prefered by the carrier.
All of that can be changed by getting into the lg data secret menu or the dialer code menu
Remember now bootloader and root for the LG g7 is just the beginning. You talk about nvdata you might as well throw out EFS backup as well.
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
I prefer the manual backup using adb shell you can do it with terminal emulator as well.
Qfil is very powerful for Qualcomm devices and we'll figure out how to make back ups of all partitions that involve serial numbers and IMEI ( nvdata and efs).
Just wait you'll see.
netookska05 said:
Remember now bootloader and root for the LG g7 is just the beginning. You talk about nvdata you might as well throw out EFS backup as well.
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
I prefer the manual backup using adb shell you can do it with terminal emulator as well.
Qfil is very powerful for Qualcomm devices and we'll figure out how to make back ups of all partitions that involve serial numbers and IMEI ( nvdata and efs).
Just wait you'll see.
Click to expand...
Click to collapse
Thats already been possible since day 1, use qpst with your msl code to backup qcn with imei and s/n.
netookska05 said:
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
Click to expand...
Click to collapse
I don't understand. What does twrp have to do with any of this? My bootloader is locked and the stock recovery is still there. The devices are likely just flashed with LGup as is, and that doesn't seem to have effected much outside of a missing SN.
Are you saying that my cross flashed phone would effect things if I tried to root somehow? Or am I missing the point here?
loonycgb2 said:
Thats already been possible since day 1, use qpst with your msl code to backup qcn with imei and s/n.
Click to expand...
Click to collapse
Can you please elaborate for those unfamiliar with this?
Dishe said:
I don't understand. What does twrp have to do with any of this? My bootloader is locked and the stock recovery is still there. The devices are likely just flashed with LGup as is, and that doesn't seem to have effected much outside of a missing SN.
Are you saying that my cross flashed phone would effect things if I tried to root somehow? Or am I missing the point here?
Can you please elaborate for those unfamiliar with this?
Click to expand...
Click to collapse
Using TWRP to create a backup of efs. Sometimes the restore is faulty.
EFS partition holds up the unique IMEI number of the device, also other identifying numbers like MAC address, MEID, and ESN are stored up in this partition.
Check you IMEI with this.
https://imeipro.info/check_lg.html
To get your sn.
Oh ok.
So I don't actually need to know my SN but I'd like it to not be blank if flashing back to a previous version would restore it... Especially if there are possibly other parts of nvram that may be corrupt that I'm unaware of?
Thanks for the info. The one I got said it can't work on Sprint or Verizon networks, and is missing the serial #, as you said.
I got just one from bay with S/N missing and software version G710ULM10g. Latest patch level Sep 1, 2018 (Android 8.0.0). Is there any way to install Android 10 based ROM?
Assuming that after following the steps (Part 1 only) (hope we can skip part 2?) to somehow install G710ULM20e_00_NAO_US_OP_1010 (Android 9), is there a way to follow similar steps after part-1 to update it to Android 10 based ROM?
It would be great if someone can help to install Android 10 directly from Android 8.0 (without the need to installing Android 9). I am not sure if its even possible to get Android 10 on such bay unlocked devices without S/N.
vishal198900 said:
I got just one from bay with S/N missing and software version G710ULM10g. Latest patch level Sep 1, 2018 (Android 8.0.0). Is there any way to install Android 10 based ROM?
Assuming that after following the steps (Part 1 only) (hope we can skip part 2?) to somehow install G710ULM20e_00_NAO_US_OP_1010 (Android 9), is there a way to follow similar steps after part-1 to update it to Android 10 based ROM?
It would be great if someone can help to install Android 10 directly from Android 8.0 (without the need to installing Android 9). I am not sure if its even possible to get Android 10 on such bay unlocked devices without S/N.
Click to expand...
Click to collapse
If you must know the serial number there is a one site that you enter imei and it'll tell you what it is. Just gotta search on Google.
Serial number is lost when bootloader is unlocked. You can regain it if you relock and go back to stock. Not sure what version of g7 you have. More likely it's probably crossflashed and sold like that so there won't be a kdz to go back to stock.
Android 10 has a thread they tell you what kdz to crossflash too and how to update to android 10 with the activity launcher app.
I just got a 710pm off ebay. I unlocked the bootloader, crossflashed to ulm pie, and rooted. It works just fine. [emoji106]
Sent from my LM-G710 using Tapatalk
netookska05 said:
If you must know the serial number there is a one site that you enter imei and it'll tell you what it is. Just gotta search on Google.
Serial number is lost when bootloader is unlocked. You can regain it if you relock and go back to stock. Not sure what version of g7 you have. More likely it's probably crossflashed and sold like that so there won't be a kdz to go back to stock.
Click to expand...
Click to collapse
I don't know if there's much use of serial number. Isn't it better to have unlocked bootloader?
netookska05 said:
Android 10 has a thread they tell you what kdz to crossflash too and how to update to android 10 with the activity launcher app.
Click to expand...
Click to collapse
Can you please help me with the correct thread post for crossflashed devices like mine bought through ebay? I appreciate your help.
vishal198900 said:
I don't know if there's much use of serial number. Isn't it better to have unlocked bootloader?
Can you please help me with the correct thread post for crossflashed devices like mine bought through ebay? I appreciate your help.
Click to expand...
Click to collapse
Here's the crossflashing thread using command line lgup.
Thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
There's another lgup dualmode you can use the partion dl option to install the Korean kdz that Android 10 uses. Search for that.
To install the Android 10 LGUP_FOTA.up update which you use activity launcher to install.
Thread:
https://forum.xda-developers.com/lg-g7-thinq/how-to/android-10-beta-lg-g7-g710n-t4059483
netookska05 said:
Here's the crossflashing thread using command line lgup.
Thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
There's another lgup dualmode you can use the partion dl option to install the Korean kdz that Android 10 uses. Search for that.
To install the Android 10 LGUP_FOTA.up update which you use activity launcher to install.
Thread:
https://forum.xda-developers.com/lg-g7-thinq/how-to/android-10-beta-lg-g7-g710n-t4059483
Click to expand...
Click to collapse
Thanks. My phone (G710PM) is cross-flashed with G710ULM firmware Android 8. Please suggest is below plan will work?
1) First update existing firmware to stock Android 9.0 i.e. G710ULM20e_00_NAO_US_OP_1010 using these steps.
2) Then install Lineage OS 17.1 (based on Android 10) because it needs stock Android 9.0 as a pre-requisite using these steps.
vishal198900 said:
Thanks. My phone (G710PM) is cross-flashed with G710ULM firmware Android 8. Please suggest is below plan will work?
1) First update existing firmware to stock Android 9.0 i.e. G710ULM20e_00_NAO_US_OP_1010 using these steps.
2) Then install Lineage OS 17.1 (based on Android 10) because it needs stock Android 9.0 as a pre-requisite using these steps.
Click to expand...
Click to collapse
Yes it will work.
I'd also like to add that Google Pay will not work, at retail brick and mortar stores.
A pop up says device may be rooted or modified.
I have magisk installed and it seems to trick Schwab banking app.
Edit:
Edit: I followed the instruction from the following video, and was able to get GPay to accept the card. Also Gpay needs to be manually hidden in magisk, be sure to select 'display system apps' to find it.
https://www.youtube.com/watch?v=wKYC0r-m0Mo
Click to expand...
Click to collapse
I am not an expert but I just bought one of these Ebay phones. It has Pie but what would like to know is how can I get the security updates? Or is that not possible? Please help. Thanks in advance.
captain barbosa said:
I am not an expert but I just bought one of these Ebay phones. It has Pie but what would like to know is how can I get the security updates? Or is that not possible? Please help. Thanks in advance.
Click to expand...
Click to collapse
If you're on Pie, I doubt you have one of these Sprint phones. Check if you pass SafetyNet and if so, you have a native ULM model. Most G7 variants receive very few updates (including the ULM).
Related
Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
ryn.ste said:
Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
Click to expand...
Click to collapse
Can u share the link I wanna try it also
ryn.ste said:
Well I've obtained the actual .kdz file from the pre beta program in Korea. Now too flash it into my Canadian g710awm. The firmware is actually for model# g710N so wish me luck...
Click to expand...
Click to collapse
Is it a 8.0 kdz to update to 9.0 or directly a 9.0 kdz?
Did it work?
MishaalRahman said:
Did it work?
Click to expand...
Click to collapse
Lack of response, I'm gonna guess no? LoL
dah brick dah bricks.
???
The suspense is killing me. Personally I'm waiting for the official, but it would be nice to know...
i guess i would be able to flash it on my g7 , but i only have a .up file instead of a kdz and that doesnt work
Warning!
From what I read recently; LG has started to use unique RSA keys for each device (within a group, i.e G7) starting with V35 (I think), thus flashing a KDZ from another G7 would definitively cause hardbrick.
Edit: Apparently this was (mostly?) wrong. At least some confirmed models can be cross-flashed.
askermk2000 said:
Warning!
From what I read recently; LG has started to use unique RSA keys for each device (within a group, i.e G7) starting with V35 (I think), thus flashing a KDZ from another G7 would definitively cause hardbrick.
Click to expand...
Click to collapse
I thought that was only for TMoile but not the rest of variants?
GROOVYJOSHCLARK said:
I thought that was only for TMoile but not the rest of variants?
Click to expand...
Click to collapse
Well, like I said, not anymore.
IIRC, this is what @runningnak3d said in a tread somewhere (I don't recall exactly, maybe V30 forums).
He is the current resident expert on LG root, and bootloader matters. At least the most active one, and he's provided root for many previous LG devices.
askermk2000 said:
Well, like I said, not anymore.
IIRC, this is what @runningnak3d said in a tread somewhere (I don't recall exactly, maybe V30 forums).
He is the current resident expert on LG root, and bootloader matters. At least the most active one, and he's provided root for many previous LG devices.
Click to expand...
Click to collapse
I am definitely not arguing as I dont know the answer 100% myself.
What I DO know for sure is that I can, (and I have) flashed other LG G7's firmware on my G7 (Sprint) through my Octoplus box. This is using the Octoplus box, not LGUP, but if the RSA keys were an issue, I would expect it to not work (flashing another variant .KDZ), or I would expect the device not to work (boot) afterwards. It boots and works just fine. I also know of numerous others who have converted their LG G7's (except TMobile) to the unlocked model (ULM). My understanding was that only the TMobile ones were using a custom RSA key coming FROM TMobile themselves (I could be wrong but this is what I read) and since I dont own a TMobile flavor, I cant test myself to confirm.
In that case maybe I remember wrong, or runningnak3d statement was not accurate (maybe doesn't apply to G7 specifically).
askermk2000 said:
In that case maybe I remember wrong, or runningnak3d statement was not accurate (maybe doesn't apply to G7 specifically).
Click to expand...
Click to collapse
All good, I dont know for sure myself so I cant confirm nor deny anything except for my personal Octoplus flashing. I just want ROOT, thats what I am pressing through to figure out how to achieve. I HATE that LG locks the bootloaders, if I had known prior, I would NEVER have switched from HTC!
LG mobile will go out of business soon enough if they dont cut the crap.
Yeah, not to mention that we don't have a way to fix ourselves bricked devices. It would be a trivial matter with a simple qualcomm type firehose-file.
Instead now it's basically dead weight. They seem to think it's ok to produce lots of electronic garbage, and not make efforts to reduce this.
askermk2000 said:
Yeah, not to mention that we don't have a way to fix ourselves bricked devices. It would be a trivial matter with a simple qualcomm type firehose-file.
Instead now it's basically dead weight. They seem to think it's ok to produce lots of electronic garbage, and not make efforts to reduce this.
Click to expand...
Click to collapse
Exactly, hopefully the drop in sales will be enough to kick their butt's in gear BEFORE they become the next Blackberry! If they would simply give us a restore KDZ, we would love LG, instead, they lock us out, and make it damn near impossible to restore or recover our devices from normal things, such as a bad OTA updates. BUT NO, for some dumb A$$ reasons, they dont so it WILL be their demise. Its almost like being able to see the future. If they took notice of all the predecessors before them, all their mistakes, made changes then history wouldn't have to repeat itself. If not, LG will be another forgotten company no one gives a crap about.
GROOVYJOSHCLARK said:
I am definitely not arguing as I dont know the answer 100% myself.
What I DO know for sure is that I can, (and I have) flashed other LG G7's firmware on my G7 (Sprint) through my Octoplus box. This is using the Octoplus box, not LGUP, but if the RSA keys were an issue, I would expect it to not work (flashing another variant .KDZ), or I would expect the device not to work (boot) afterwards. It boots and works just fine. I also know of numerous others who have converted their LG G7's (except TMobile) to the unlocked model (ULM). My understanding was that only the TMobile ones were using a custom RSA key coming FROM TMobile themselves (I could be wrong but this is what I read) and since I dont own a TMobile flavor, I cant test myself to confirm.
Click to expand...
Click to collapse
What partitions did you flash?
All of the KDZs I have been able to pull down have different RSA certs (granted it is only a couple) but it is not just the TMO that was different.
If you don't mind, link to the exact KDZ for your model, and the KDZ that you flashed -- I would love to compare the certs.
-- Brian
runningnak3d said:
What partitions did you flash?
All of the KDZs I have been able to pull down have different RSA certs (granted it is only a couple) but it is not just the TMO that was different.
If you don't mind, link to the exact KDZ for your model, and the KDZ that you flashed -- I would love to compare the certs.
-- Brian
Click to expand...
Click to collapse
There is no KDZ for the PM (Sprint model) yet so I cannot go back to Sprint or link to one (until one is released) but I wish there was one for others who are in a loop or brick situation, here are the 2 I used:
EM (European Model - bootload unlockable approved by LG):
G710EM10b_00_0521.kdz
https://drive.google.com/file/d/1W14Y-jbvnwDt4UOfitni8hDGfwYsXesV/view?usp=sharing
ULM (US Unlocked Model):
G710ULM10g_00_NAO_US_OP_0913.kdz
http://pkg02.lime.gdms.lge.com/dn/d...XADM55F9FR80/G710ULM10g_00_NAO_US_OP_0913.kdz
I flash ALL partitions through Octoplus EXCEPT the modems (MODEM1/2), I left those from Sprint (stock), not sure if it helps or not, but I have service so I like to think it did. There are lots of users who have also used the LGUP (somehow) to cross flash the KDZ's to the ULM (unlocked) model but I haven't personally used this LGUP method so I cant comment if its valid or not. Octoplus, most definitely works though (and I have the logs to show the partitions if one was interested).
GROOVYJOSHCLARK said:
There is no KDZ for the PM (Sprint model) yet so I cannot go back to Sprint or link to one (until one is released) but I wish there was one for others who are in a loop or brick situation, here are the 2 I used:
<snip>
Click to expand...
Click to collapse
There will never be a Sprint KDZ -- neither Sprint or AT&T release KDZs (I don't think they even use them internally).
I am downloading them now, and I will pull the certs / post the results as soon as they are done.
Thanks!
-- Brian
i just ordered an lg v20 at&t model, and would like to know how to either update it or convert it to the unbranded version, as I am from the UK. Is it also possible it can be done without root, and by just using the software flashing tool?
thanks
sol.j146 said:
i just ordered an lg v20 at&t model, and would like to know how to either update it or convert it to the unbranded version, as I am from the UK. Is it also possible it can be done without root, and by just using the software flashing tool?
thanks
Click to expand...
Click to collapse
Yeah, grab yourself the modded version of LGUP, download the KDZ (Most likely US996) and flash it. No root involved.
I'm in the same boat as the OP, in the UK.
I broke my International version HD990DS which I've had for a couple of years, and scored a replacement H910 on ebay (£115, sealed in box, 2019 date on battery). I received it this morning.
I wasn't aware when I bought it that it was an AT&T brand (unlocked), on Android 7, and un-updateable OTA here in the UK.
The kdz I'm downloading is 'US99620f_00_1120.kdz' from here: https://www.mylgphones.com/unlocked-lg-v20-us996-received-oreo-update-us99620f.html
Should this be good to go? I'm not aware what bands this enables. The bands EE use here are 1,3,7 & 20.
Is there a 'better' kdz I should be downloading?
TIA.
[edit] further to the above, for any UK EE users, the page here gives EE APN details which will need inputting if your phone isn't going to be a wifi only paperweight. Other operators and phones are listed in the site:
https://apn-uk.gishan.net/en/apn/ee/lg-v20
In this page you'll note EE does not support the H915 for 4G at all.
The H910 isn't listed, but it is supported for 4G by EE.[/edit]
Excudent said:
Yeah, grab yourself the modded version of LGUP, download the KDZ (Most likely US996) and flash it. No root involved.
Click to expand...
Click to collapse
Modded LGUP says : "Error:KDZ file is invalid' H910->US996"
I wish it had been that simple....
Anyone any pointers?
stateit said:
Modded LGUP says : "Error:KDZ file is invalid' H910->US996"
I wish it had been that simple....
Anyone any pointers?
Click to expand...
Click to collapse
to flash cross model use partition dl mode, select all partitions. iirc
(not applicable to you specifically, but as a reminder to anyone else who reads this)
Remember, never ever flash (T-mobile) H918 firmware on anything but an H918, and if you have an H918 never ever flash another model's firmware. Instant permanent brick.
Thanks for your input. I'll give it a go tonight.
With LGUP does "DUMP" fo a restorable backup?
I've not used LGUP before a couple of days ago. I used to use Odin a lot, but that was years ago (see my forum join date...)
[edit] OK, I've found what I need to know about LGUP here: https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/ [/edit]
stateit said:
Thanks for your input. I'll give it a go tonight.
With LGUP does "DUMP" fo a restorable backup?
I've not used LGUP before a couple of days ago. I used to use Odin a lot, but that was years ago (see my forum join date...)
[edit] OK, I've found what I need to know about LGUP here: https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/ [/edit]
Click to expand...
Click to collapse
Did you manage to get oreo on H910? My mother has a H910 stuck in Nougat, but I'd like her to get the oreo update without having to mess with root or anything hard for her to use.
Not yet... I'm waiting until I've had the crap annoyed out of me enough before I invest the few hours time to put everything back on this phone that I want.
As all partitions have to be rewritten then its a case of starting from a totally fresh phone. Which is a chore that I'll do sometime, but not until this week at least is of the way....
Salvaparalyzer said:
Did you manage to get oreo on H910? My mother has a H910 stuck in Nougat, but I'd like her to get the oreo update without having to mess with root or anything hard for her to use.
Click to expand...
Click to collapse
Lgup patched linked above using partial download you can load Oreo from us996 or h915. H915 = H910 only Canadian version with respective network software.
Salvaparalyzer said:
Did you manage to get oreo on H910? My mother has a H910 stuck in Nougat, but I'd like her to get the oreo update without having to mess with root or anything hard for her to use.
Click to expand...
Click to collapse
I'm using H91520a_00_RGS_CA_OP_0717.kdz
Downloaded from LG-Firmwares here: https://lg-firmwares.com/downloads-file/...
IIRC it was the world's slowest download, reminiscent of using a dial-up modem (well, almost).
The H915 is the canadian version of the US H910, so no worries about hardware incompatibilities
Update in patched LGUP (using 'partitions.dl' option) took about 5 minutes and was painless (one warning screen popped up at start of f/w update process in LGUP saying USB was disconnected, but I ignored this throughout the update and left it showing) .
APN numbers need to be added
I backed up data (phone logs, messages etc) first in LG Mobile Switch app first, saving to SD Card. Which I took out of the phone first before the update 'just in case'.
No more AT&T crap, and Android 8.0.0, which is back to how my last V20 990DS was before I broke it (water damage).
It's a bargain phone for £120 on eBay. Good luck!
Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Will this work on the reteu devices (being from a different channel)?
FelixNevorsky said:
Hi i found official stock rom
mirrors.lolinet.com/firmware/moto/troika/official/RETAIL/TROIKA_RETAIL_10_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS
takoa said:
What Does The Letter QSB Mean?
In The Previous Rom Are PSB Or PSBS
Click to expand...
Click to collapse
My guess is that QSB is for Android 10 (it was called Q for some time). And PSB is 9.0 (aka Pie)
I mean the letters sbs and sb. thanks
takoa said:
I mean the letters sbs and sb. thanks
Click to expand...
Click to collapse
ummmm......Stable build.....maybe
Was Anyone able to root this version?
Wintershade said:
Will this work on the reteu devices (being from a different channel)?
Click to expand...
Click to collapse
Yes, it should. It's been already tested here on the forum with pretty good results. So yeah, I'd say it will. But if you're not in a hurry, maybe you can wait for a bit longer to get the official build for RETEU.
Channel Signification Firmware
Is a list exist for channel signification for https://mirrors.lolinet.com/firmware/moto/troika/official/
or a way to knows the signication ?
RETEU = Europe
RETUS = USA
RETCA = Canada
RETRU = ???
etc ...
Compatibility Variant / Firmware
Is exists a thumb rule for compatibility firmwares in between XT2013-1, XT2013-2, XT2013-3, XT2013-4.
Actually, I have a XT2013-4 device and I would like flash another firmware variant.
Thanks
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards
arsradu said:
RETRU = Russia
RETBR = Brazil
RETAR = Argentina
etc...
Well, I don't think there is any compatibility table or something... At least not an official one. )
Also, I would not try a "-1" firmware for example, on a "-4" device. If I'm not mistaken, one of them (probably the -4 variant...?) is Single SIM. The other ones I think are Dual SIM models (XT2013-2 surely is). So I don't think that's gonna work.
The only compatibility I can confirm is a XT2013-2 device running the RETAIL version without major issues (the signal seems to be lower for both carrier and wifi, for some reason, but other than that, everything works). Everything else is at your own risk. But again, I would not recommend flashing a -1/-2/-3 ROM onto your -4 device. Unless someone else did it and it went ok.
Click to expand...
Click to collapse
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks
Gypsy said:
There's an interesting channel listing on a XDA TREAD "Identify Software Channel"
https://forum.xda-developers.com/moto-z-play/help/identify-software-channel-t3555285
/Thanks
Click to expand...
Click to collapse
that is very good to know. thank you!
Gypsy said:
Thanks for your answer, I have a XT2013-4 and I can confirm that's is a Single SIM.
For info, on my XT2013-4 I tried two différents android 10 firmware made for XT2013-2 and they both runs very smooth but time will tells if there's any issues
- TROIKA_RETAIL_10_QSBS30.62-17-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
- XT2013-2_TROIKA_RETRU_10_QSB30.62-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
/Regards
Click to expand...
Click to collapse
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time.. ?
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know.. ?
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?
zaqiezsbelelzsinski said:
Hi..
I have one action with xt2013-4 too.. and wait update to android 10 for long time..
Will you give me an information if my phone model may get OTA android 10? If yes when? If you know..
Otherwise, if I want to flash android 10 to my device, will you give me a guidance how to flash with another ROM model TROIKA, but it compatible with my device like you information before..
Thanks for the feedback
?
Click to expand...
Click to collapse
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.
arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Click to expand...
Click to collapse
arsradu said:
@zaqiezsbelelzsinski
I can't and more to @arsradu's answers, but just in case you decide to unlock your bootloader for whatever reason, it voids your warranty., there's the link:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Good luck, if you have any difficulty, please ask!
Click to expand...
Click to collapse
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.[/QUOTE]
One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.
arsradu said:
Nobody knows when. At least you won't find this information publicly available. Since XT2013-4 seems to be the only remaining model to update...I guess it shouldn't be that much longer.
If you can wait, I would advise you to wait. Flashing is not that difficult. But it comes with some risks, and in case you need to unlock your bootloader for whatever reason, it voids your warranty. So, while not impossible, it would be easier to wait, if you can. I know it's not easy! )
Basic instructions (in case you really wanna do this):
1. get the script attached to THIS post specifically (you're gonna need adb and fastboot files in the same folder as your ROM). You can also type the commands manually, but why bother when you can use a script to do it automatically for you? Also, make sure you choose Android 10! The commands are different for Android 10 compared to Android 9!
2. download the ROM from here (if you want to use the RETAIL channel).
3. unzip it
4. add adb and fastboot into the same folder, along with the script
5. connect the phone to your PC and enable USB Debugging, as well as the fingerprinting pop-up that follows it (also check the box for Always Allow)
6. boot into bootloader/fastboot (from a cold start, press Power + Volume Down).
7. flash with fastboot (using the script above)
8. done.
/!\ MAKE SURE YOU DON'T UPDATE YOUR SECURITY PATCH! THE SECURITY PATCH VERSION YOU'RE CURRENTLY USING AND THE ONE YOU'RE ABOUT TO FLASH NEED TO MATCH, in order to have the least amount of troubles!
Otherwise you might have some issues if you're trying to go back. I know it's tempting to just go and flash the newest version. BUT DON'T!
Again, this is just so you know in a few steps, how it's done. I would still advise you to wait, if you can. So you don't flash the wrong thing, or brick your phone, or stuff like that.
Click to expand...
Click to collapse
Thank you for the feedback
Yes, I understand about the risk. Many years ago I always flashing my device (Nexus 5) while it was release update, but that was then ?. Now, Maybe I will be waiting till my device get update to android 10.
The problem is, there is no valid information from Motorola especially TROIKA XT2013-4 about update to android 10.
Thanks for your advice about flashing ROM..
Cheers ???
You could try to contact your local Motorola Support team. I don't think they will give you an actual ETA. But maybe they can tell you wether or not there will be an update to Android 10 for this particular model (XT2013-4). I think there should be. I see no reason why this particular model would be an exception. But you could double check that. Just in case.
Logic would suggest that there should be one soon. XT2013-1 and XT2013-2 already got the update. So it would make sense for the "-4" model to follow.
Sent from my motorola one action using Tapatalk
arsradu said:
One thing I forgot to mention: simply requesting the bootloader unlock code will void your warranty. You don't even need to use it. Once you requested it, it's done.
Now, if you're super careful with that security patch I mentioned above, you might not need to request it in the first place, since you might not need to unlock your bootloader in the first place. Cool, huh?
Unfortunately I don't have so much experience with this. And it's not like I have a bunch of Moto One Actions I can test with. I only have my own. ) But in theory, if you don't update/downgrade your security patch, if you only flash ROMs with the exact same security patch, you could (again, this is just a theory, based on my own experience) go from Android 9 to 10 and back, without unlocking the bootloader. Because it looks like it's not the Android downgrade that's causing the issues. It's the security patch downgrade that forces you to unlock the bootloader.
And I wish I had this piece of knowledge before I requested my unlock code. )) But I didn't. So I'm just happy it wasn't for nothing and I learned a lot in the process.
Click to expand...
Click to collapse
@arsradu
I notice you have experience with security patches, tanks you to had shared!
IF I REALLY NEED TO DOWNGRADE MY SECURITY PATCH ! EVEN with all amounts of troubles, IS THERE A WAY doing it?
Thanks
Hey all,
I bought a new OnePlus 8 5g T-mobile phone for my wife. She's on the RedPocket annual GMSA/ATT plan. I've stopped the auto OO11 update and I've gone into *#*#4636#*#* and selected "LTE Only" for the connection type (like I did with my old OP6) but it doesn't stick after a reboot.
My real question is:
Since 4G LTE seems to work properly with the T-Mobile stock OS, what are the reasons for converting over to the international version?
Will 4G still work after I update it to OO11.x? I don't mind it having the T-Mobile boot or bloat. I have mostly disabled/uninstalled the apps she doesn't need.
Thanks!!!
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware, and even if you don't really "care" about it, every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
FoxyDrew said:
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware. And even if you don't really "care" every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
Click to expand...
Click to collapse
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
chuddler said:
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
Click to expand...
Click to collapse
np man, that guide is very complicated for no reason, converting to global is rather simple, but it's a 3 step process. This all assumes you can unlock your bootloader though.
1.) MSM back to stock T-Mobile Android 10 firmware. Specifically this one. This will re-lock your BL if its unlocked.
2.) Let that boot up, go into settings to enable OEM unlocking, and then unlock the bootloader.
3.) Once the bootloader is unlocked, flash THIS global Android 10 ROM via fastboot. There's a flash-all.bat file to make it simple. Once you've finished this step your essentially done, and on global firmware, you just need to...
4.) Boot the phone up and take the OTA update in settings to Android 11. There will be 2 OTAs to take, one FULL OTA to Android 11, than an incremental one to the latest Android 11 build
Optionally afterwards you can re-lock your bootloader, or keep it unlocked and root if that's what you/she wants.
If you're not familiar with MSM tool, and the drivers it needs, check out this thread.
Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
vansteering said:
Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Honestly I've been trying to figure out the best way to go about this as well. My fiance is interested in having her phone rooted. I'm just trying to figure a well to where i can just access the boot image off the phone somehow so i can patch it using magisk. well obviously backing up the original image first, but i've heard twrp doesn't work and i tried using QFIL to see if i can access it but i don't think it has EDL. If you figured out a way to do it without flashing a older update to the phone. Please let me know. I'll do the same after I look into it a bit more. I feel like i'm just over complicating somehow lol I have a tendency of doing that.
vansteering said:
Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Just tried this and had no issues at all, Hope this helps
[RECOVERY][UNOFFICIAL] TWRP 3.5.2_10 for Moto G 5G (kiev)
DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff. What has been tested and...
forum.xda-developers.com
InvisibleAOD said:
Just tried this and had no issues at all, Hope this helps
Click to expand...
Click to collapse
On Build number 95-9? Or a previous version? I'm asking because I couldn't even get the bootloader unlocked on a 95-9 phone (unlock "failed" after getting the code from Moto). I'm still trying to get an answer as to whether if the newest OTA is a problem.
vansteering said:
. . . I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Is this what you're asking for?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
As for 40-95-9 firmware, a sure way to get that firmware is Moto/Lenovo's "Rescue and Smart Assistant", aka "LMSA" (search, should be easy to find). Use the Rescue option and stop (EDIT/ADD: let the download finish), go to the folder where it was downloaded (make sure to get the download link shown in the utility) and find the firmware in the ".../ROMfiles" subfolder I think it is. That's the full firmware including boot.img. I used that subfolder to reflash the entire 95-9 firmware. EDIT/ADD: But this assumes Rescue and Smart Assistant on Windows, NOT Linux. I don't know if there is a Linux version for that, sorry. {--Or do you have a Windows emulator in your Linux that might solve this particular issue?--)
I DO NOT KNOW -- yet -- if 95-9 is rootable or even unlockable. Unlock failed for me on a 95-9 phone . . . although I did get an Unlock Code from Moto (on a Windows PC).
So this is a question back at you: HAVE YOU MANAGED TO UNLOCK THE BOOTLOADER on your 95-9 phone?
Moondroid said:
On Build number 95-9? Or a previous version? I'm asking because I couldn't even get the bootloader unlocked on a 95-9 phone (unlock "failed" after getting the code from Moto). I'm still trying to get an answer as to whether if the newest OTA is a problem.
Click to expand...
Click to collapse
Yeah it was on 95-9, just make sure to read through the thread cause I kind of messed up in the process but once you flash twrp and boot into it, flash the kiev file and magisk. I had to keep reading. I flashed to both partition a and b.
InvisibleAOD said:
Yeah it was on 95-9, just make sure to read through the thread cause I kind of messed up in the process . . .
Click to expand...
Click to collapse
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Moondroid said:
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Click to expand...
Click to collapse
Unlocked on 95-9
been away for awhile. Thanx Moondroid, and Invisible AOD, & everyone for all the info. I'll try a few things this weekend.
InvisibleAOD said:
Unlocked on 95-9
Click to expand...
Click to collapse
Moondroid said:
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Click to expand...
Click to collapse
no hijacking here, just much needed info. More is better.