Related
Hello A2 Community, how is it going? well, i'm a bit confused here, had a Samsung phone before this and i don't know nothing about the Fastboot Commands, i'm in windows 7 x64, downloaded the fastboot and tried to execute right after i booted in AP Fastboot mode and while the phone was connected by the usb cable to the computer. so now what? How do i use the Fastboot commands ? Where do i have to put it and how to use it in CMD? i read the guide in begginners and noobs thread in General, but i don't understand :S
My other doubt is about the A2 variants, there is an International MB865, the retail version from India, and ATT Variant, which is MB865 too.. My question is.. Can i flash through RSD Lite any Fastboot files from international version like, Mearet, Searet, AsiaOPS? I hate ATT Stuff and ATT Logo "Rethink Possible" ¬¬ I'd like a clean 2.3.6 like a retail firmware, also i wanted to know the risks, because in the future, when ICS is released by Motorola officialy, there is a possibility that motorola also launches a Latinoamerican firmware only for international MB865, wich could be very useful for me because of the radio software. Well, thats all, thanks guys
maxiordoqui said:
Hello A2 Community, how is it going? well, i'm a bit confused here, had a Samsung phone before this and i don't know nothing about the Fastboot Commands, i'm in windows 7 x64, downloaded the fastboot and tried to execute right after i booted in AP Fastboot mode and while the phone was connected by the usb cable to the computer. so now what? How do i use the Fastboot commands ? Where do i have to put it and how to use it in CMD? i read the guide in begginners and noobs thread in General, but i don't understand :S
My other doubt is about the A2 variants, there is an International MB865, the retail version from India, and ATT Variant, which is MB865 too.. My question is.. Can i flash through RSD Lite any Fastboot files from international version like, Mearet, Searet, AsiaOPS? I hate ATT Stuff and ATT Logo "Rethink Possible" ¬¬ I'd like a clean 2.3.6 like a retail firmware, also i wanted to know the risks, because in the future, when ICS is released by Motorola officialy, there is a possibility that motorola also launches a Latinoamerican firmware only for international MB865, wich could be very useful for me because of the radio software. Well, thats all, thanks guys
Click to expand...
Click to collapse
Ok, I have got to ask... Why are you in fastboot, if you really have no clue what it is for?
Tell us EXACTLY what you are after here. If you want to flash ROMs you need to root and install the bootstrap in the noob guide. If you need to get back to stock you need to use RSDlite and use the proper FXZ for your version of the Atrix2.
jimbridgman said:
Ok, I have got to ask... Why are you in fastboot, if you really have no clue what it is for?
Tell us EXACTLY what you are after here. If you want to flash ROMs you need to root and install the bootstrap in the noob guide. If you need to get back to stock you need to use RSDlite and use the proper FXZ for your version of the Atrix2.
Click to expand...
Click to collapse
Hi Jim! Thanks for replying so fast everytime, i actually don't want to do anything to the Phone, i just wanted to learn ! And also wanted to know if ATT version of Atrix is compatible with International version firmwares.. Those things could be useful for me in the future to know what to do if i'm facing a problem. My phone actually works perfectly, i'm in 2.3.6 from ATT waiting the official OTA, just wanted to know more about how to use fastboot commands, i dont understand the prodecure that explaings the begginers' guide.
maxiordoqui said:
Hi Jim! Thanks for replying so fast everytime, i actually don't want to do anything to the Phone, i just wanted to learn ! And also wanted to know if ATT version of Atrix is compatible with International version firmwares.. Those things could be useful for me in the future to know what to do if i'm facing a problem.
Click to expand...
Click to collapse
1) If you want to run the fastboot commands, you will need to have the moto-fastboot binary that is the ONLY one that will let you run the RSDlite similar flash commands... there is no point in just running the command unless you REALLY have to, and 100% know what you are doing. You can brick the phone VERY easily with that command.
2) No you can not run any other firmware on an AT&T variant phone, ONLY the AT&T US firmware is compatible. You might be able to flash just the radio from one of the other international versions using moto-fastboot, or just editing the xml file, to only flash the radio.img file with RSDlite, but again this is not task for normal users.
jimbridgman said:
1) If you want to run the fastboot commands, you will need to have the moto-fastboot binary that is the ONLY one that will let you run the RSDlite similar flash commands... there is no point in just running the command unless you REALLY have to, and 100% know what you are doing. You can brick the phone VERY easily with that command.
2) No you can not run any other firmware on an AT&T variant phone, ONLY the AT&T US firmware is compatible. You might be able to flash just the radio from one of the other international versions using moto-fastboot, or just editing the xml file, to only flash the radio.img file with RSDlite, but again this is not task for normal users.
Click to expand...
Click to collapse
Thanks you Jim, i'll keep that in Mind. Have a nice weekend.
I recently had my Orange Galaxy S2 i9100P unlocked by the local phone shop.
The unlocking worked fine, but I have now noticed that it has been rooted too.
It has a superuser app installed, which he said he didn't realise it had installed.
Not sure that I want it to be rooted when I sell it as it might put off potential buyers.
So I called the shop and asked if it has to be rooted to unlock it and he said that it does.
He said that the other way to unlocked it is to use a code but that system is currently down (the website that gives out codes) and it would cost £26 instead of the £10 that I paid to have it unlocked using root. I asked him if I could unroot it by flashing with the standard Orange firmware (using Keis) and he said yes I could and that would unroot it. When asked that if this would then lock it again he said that no it shouldn't, but he didn't seem too sure about what he was saying.
So some specific questions:-
1) Did he have to root it to unlock it?
2) Did it have to be left in root once unlocked?
3) Can I unroot it and return to standard firmware (using Keis) and it still remain unlocked?
4) If the answer to 3) is no, then can I delete / uninstall the superuser app?
5) When I run the superuser app, there is a temp unroot option. What does that do? Can I use that to unroot it?
MrModbus said:
1) Did he have to root it to unlock it?
2) Did it have to be left in root once unlocked?
3) Can I unroot it and return to standard firmware (using Keis) and it still remain unlocked?
4) If the answer to 3) is no, then can I delete / uninstall the superuser app?
5) When I run the superuser app, there is a temp unroot option. What does that do? Can I use that to unroot it?
Click to expand...
Click to collapse
1. Yes root was required to unlock from the carrier. Or else you had to pay full price to get the unlock.
2. Not exactly! If he made a permanent change then no need, But if he's using something dependent to unlock it then it needs to be rooted.
3. Not sure, cause if the stock Orange firmware finds the phone as locked it might re-lock it again. So there's a risk. If you can find a fresh carrier free firmware for your model why not flash that?
4. I used SuperSU there's an unroot button there but nothing that says 'Temporary'. But if the root binaries are once flashed I'm not sure that gets rid of it.
Just trying to be helpful.
Tiash420 said:
1. Yes root was required to unlock from the carrier. Or else you had to pay full price to get the unlock.
Click to expand...
Click to collapse
Ah OK.
Tiash420 said:
2. Not exactly! If he made a permanent change then no need, But if he's using something dependent to unlock it then it needs to be rooted.
Click to expand...
Click to collapse
How do you mean? Are you saying that there is another appliocation that is running that is performing the unlock and that needs root to do its stuff?
Tiash420 said:
3. Not sure, cause if the stock Orange firmware finds the phone as locked it might re-lock it again. So there's a risk. If you can find a fresh carrier free firmware for your model why not flash that?
Click to expand...
Click to collapse
That is an option. But Last time I looked (a few years back) I couldn't find any i9100P specific unbranded firmware. There was i9100 firmware, but that didn't support the i9100P NFC chip.
Tiash420 said:
4. I used SuperSU there's an unroot button there but nothing that says 'Temporary'. But if the root binaries are once flashed I'm not sure that gets rid of it.
Click to expand...
Click to collapse
My app is just called "superuser" and is at v3.1.3. I suppse that I could try the temp unroot and see what happens.
Yes, I'm saying there might be some app keeping the unlock alive. Cause that's how I unlocked my iPhone 4, quite a lot of times. :3
And you should search again for unofficial rom.
And also try the temporary unroot button.
Rightho, I have now moved over to the S5 and I would like to get my S2 ready for sale.
Someone mentioned earlier that Keis might not recognise the device. Well you are correct it doesn't and will not let my flash. I does not recognise it as a Samsung device.
So I would like some generic I9100P firmware that supports NFC.
I would also like to unroot the device.
Current firmware is V4.1.2
Baseband version is I9100PBVLS2
Kernel is 3.0.31 - 1246097
[email protected] - 109 #3
SMP PREEMPT Tue Jun 4 15:49:20 KST 2013
Build number is JZO54K.I9100PXXLSS
I do not get a yellow warning triangle so I assume that it is a secure kernel.
So can anyone help me to:-
1) Unroot the device.
2) Get it so that Keis will talk to it again.
3) Keep it unlocked
4) Get a secure kernel if mine is insecure.
MrModbus said:
Rightho, I have now moved over to the S5 and I would like to get my S2 ready for sale.
Someone mentioned earlier that Keis might not recognise the device. Well you are correct it doesn't and will not let my flash. I does not recognise it as a Samsung device.
So I would like some generic I9100P firmware that supports NFC.
I would also like to unroot the device.
Current firmware is V4.1.2
Baseband version is I9100PBVLS2
Kernel is 3.0.31 - 1246097
[email protected] - 109 #3
SMP PREEMPT Tue Jun 4 15:49:20 KST 2013
Build number is JZO54K.I9100PXXLSS
I do not get a yellow warning triangle so I assume that it is a secure kernel.
So can anyone help me to:-
1) Unroot the device.
2) Get it so that Keis will talk to it again.
3) Keep it unlocked
4) Get a secure kernel if mine is insecure.
Click to expand...
Click to collapse
Flash a custom recovery through Odin and then backup your current Rom. And then find flashable-zip official firmwares and then flash and see results. If anything goes wrong revert back to the old firmware.
The solution seems to be to download and install firmware XXLSU Android 4.1.2 Jelly Bean.
This will install a generic unlocked stock ROM and generic firmware, which is just what I need.
See here.
w w w.ibtimes.co.uk/galaxys2-i9100p-xxlsu-android412-jellybean-update-install-501998
However, I am not able to find the update ROM / Firmware files as all the links in all the websites that I have found are all dead.
I have founf some working links but this is for Spanish / French versions. Will these be OK?
MrModbus said:
The solution seems to be to download and install firmware XXLSU Android 4.1.2 Jelly Bean.
This will install a generic unlocked stock ROM and generic firmware, which is just what I need.
See here.
w w w.ibtimes.co.uk/galaxys2-i9100p-xxlsu-android412-jellybean-update-install-501998
However, I am not able to find the update ROM / Firmware files as all the links in all the websites that I have found are all dead.
I have founf some working links but this is for Spanish / French versions. Will these be OK?
Click to expand...
Click to collapse
Keep in mind to use the firmware with the right "MODEM" version. SamMobile offers the firmware version(s) you are looking for. BUT don't risk flashing another firmware, if its much more easy. Install "SuperSU" from the play store. Open it an switch ROOT to "SuperSU", you will be prompted to uninstall the current superuser (root). Accept it. Reboot your phone. Open SuperSU and perform "Complete Unroot". Thats it
Ok that will unroot it but stay with orange firmware and be re-locked to orange?
I was wanting a generic ROM and firmware that supports NFC.
SamMobile has the I9100PXXLSU firmware which I believe I need. However, it has 2 versions:-
Date Country/Carrier Version PDA CSC MODEM
2013 August France 4.1.2 I9100PXXLSU I9100PXEFLS3 I9100PXXLS8
2013 August Spain (Vodafone) 4.1.2 I9100PXXLSU I9100PATLLS6 I9100PBULS3
Should I be concerned about the carrier / country?
You say get the correct MODEM version but how do I know what the correct one is?
My current details are:-
PDA: I9100PXXLSS
PHONE: I9100PBVLS2
CSC: I9100PPORALS6
Please can someone just tell me where I can get a generic ROM / firmware and tell me which one I should be using.
It all seems to be riddles and cryptic clues.
I am confident of downloading the ROM / firmware using ODIN, but I just want to know what to download.
MrModbus said:
Ok that will unroot it but stay with orange firmware and be re-locked to orange?
I was wanting a generic ROM and firmware that supports NFC.
SamMobile has the I9100PXXLSU firmware which I believe I need. However, it has 2 versions:-
Date Country/Carrier Version PDA CSC MODEM
2013 August France 4.1.2 I9100PXXLSU I9100PXEFLS3 I9100PXXLS8
2013 August Spain (Vodafone) 4.1.2 I9100PXXLSU I9100PATLLS6 I9100PBULS3
Should I be concerned about the carrier / country?
You say get the correct MODEM version but how do I know what the correct one is?
Please can someone just tell me where I can get a generic ROM / firmware and tell me which one I should be using.
It all seems to be riddles and cryptic clues.
I am confident of downloading the ROM / firmware using ODIN, but I just want to know what to download.
Click to expand...
Click to collapse
Vodafone firmware is Vodafone branded, so i won't use it as its probably highly customized by vodafone. The France version should not have a branding. You can check your modem version in Android: "Settings-->about Phone". If you get you right, you want to sell a branded phone as unbranded and potentially next owner may not know. sounds not very good
I was just trying to get rid of all the ornage bloatware. If someone wants to use a different network operator, they might not want all the orange stuff on there. I was certainly not wanting to trick anyone. I suppose I could just unroot it and leave it as it is (it is obviously an orange branded phone as it has orange logos on it). Or I could just download the standard orange ROM / Firmware and return it to stock. My worry is that this will lock it again. I keep asking this question but no one seems to give me a straight answer if it will or not. Maybe it is an unknown. As I am a newby I have no idea.
MrModbus said:
I was just trying to get rid of all the ornage bloatware. If someone wants to use a different network operator, they might not want all the orange stuff on there. I was certainly not wanting to trick anyone. I suppose I could just unroot it and leave it as it is (it is obviously an orange branded phone as it has orange logos on it). Or I could just download the standard orange ROM / Firmware and return it to stock. My worry is that this will lock it again. I keep asking this question but no one seems to give me a straight answer if it will or not. Maybe it is an unknown. As I am a newby I have no idea.
Click to expand...
Click to collapse
I suppose its hard to say, because no one but the shop owner exactly knows what method was used to unlock the phone. Thats the reason why there is no guarantee that the unlock survives a firmware flash. If you just want to get rid of unwanted apps, you can use "Titanium Backup" to uninstall whatever you want. I would never use a non rooted phone again, so may be the new owner is happy that its already rooted
LS.xD said:
Keep in mind to use the firmware with the right "MODEM" version. SamMobile offers the firmware version(s) you are looking for. BUT don't risk flashing another firmware, if its much more easy. Install "SuperSU" from the play store. Open it an switch ROOT to "SuperSU", you will be prompted to uninstall the current superuser (root). Accept it. Reboot your phone. Open SuperSU and perform "Complete Unroot". Thats it
Click to expand...
Click to collapse
Yeah this works, if you really wanna get rid off the orange BS. Just uninstall all the BS with Titanium Backup and then simply unroot. :3 And the device fresh and unlocked and not rooted without the BS. :3 And everybody's happy, right?
Hey guys,
My dad has a SM-G930A 6.0.1 unlocked running on T-Mobile. It is starting to show it's age (battery drain, apps not running like they should, etc.) and is still stuck on 6.0.1.. From my understanding, it should be possible to flash to SM-G930T, however I am a bit lost as to where to begin the process to do so. I tired going straight to 8.0 by flashing the SM-G930T 8.0 firmware files but this didn't work (I didn't think it would work, but it was worth a try). With that said, would it be better for me to just stick to updating to SM-G930A 7.0 via the guides posted, or is there a way for me to Flash the SM-930T 8.0 firmware? Thanks in advance.
leprkon said:
Hey guys,
My dad has a SM-G930A 6.0.1 unlocked running on T-Mobile. It is starting to show it's age (battery drain, apps not running like they should, etc.) and is still stuck on 6.0.1.. From my understanding, it should be possible to flash to SM-G930T, however I am a bit lost as to where to begin the process to do so. I tired going straight to 8.0 by flashing the SM-G930T 8.0 firmware files but this didn't work (I didn't think it would work, but it was worth a try). With that said, would it be better for me to just stick to updating to SM-G930A 7.0 via the guides posted, or is there a way for me to Flash the SM-930T 8.0 firmware? Thanks in advance.
Click to expand...
Click to collapse
Wow you guys really get screwed over there in the US with cell phones. It's a pain in the a** to do anything with your phones.
Anyway I'm guessing the phone was originally AT&T right? And now it's unlocked to any carrier.
If you just want to update the phone to the latest firmware then just flash AT&T Oreo. It won't affect the SIM it will still work as before.
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Make sure you back up all the things you want to keep before flashing
cooltt said:
Wow you guys really get screwed over there in the US with cell phones. It's a pain in the a** to do anything with your phones.
Anyway I'm guessing the phone was originally AT&T right? And now it's unlocked to any carrier.
If you just want to update the phone to the latest firmware then just flash AT&T Oreo. It won't affect the SIM it will still work as before.
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Make sure you back up all the things you want to keep before flashing
Click to expand...
Click to collapse
Thanks for the reply! I appreciate the direction. You are right, US phones are a pain. And yes, the phone was originally an AT&T phone, but was unlocked.
As for unlocking the bootloader, I've found different sources that say that unlocking the bootloader on this particular phone is not possible with this particular phone. I did read something about an engineering bootloader being used to get around a locked bootloader for rooting. Could this be used for flashing as well?
cooltt said:
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Click to expand...
Click to collapse
That's not entirely true. Using Odin you can flash any USA firmware onto any other USA device, no bootloader unlocking required.
It's very common for people to flash G930U over their G930V/T/A/P devices to remove bloatware
leprkon said:
As for unlocking the bootloader, I've found different sources that say that unlocking the bootloader on this particular phone is not possible with this particular phone. I did read something about an engineering bootloader being used to get around a locked bootloader for rooting. Could this be used for flashing as well?
Click to expand...
Click to collapse
It's unstable and only lets the device charge up to 80%, your best bet woulld just be a full flash with Odin
This guide is a bit dated but it's the best one out there. Just make sure you google the latest Odin and use all 4 firmware files when flashing https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Beanvee7 said:
That's not entirely true. Using Odin you can flash any USA firmware onto any other USA device, no bootloader unlocking required.
It's very common for people to flash G930U over their G930V/T/A/P devices to remove bloatware
It's unstable and only lets the device charge up to 80%, your best bet woulld just be a full flash with Odin
This guide is a bit dated but it's the best one out there. Just make sure you google the latest Odin and use all 4 firmware files when flashing https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Click to expand...
Click to collapse
Thanks for the reply! I had tried flashing the 8.0 G930T variant last night with the latest version of Odin and the PrinceComsy version and got a Model Mismatch error. I read that the modified Odin3 v3.13.1_3B_PatcheD would let me flash the firmware and ignore the Model Mismatch error. However, I didn't go through with it because I was not sure if I would brick my phone and instead erred on the side of caution and made my post here. Would I be safe to flash the files from SM-G930T_1_20180625111401_xf3965l42p_fac onto my current device?
If your firmware files are from a trusted source like sammobile, updato or samfirmtool then it should be fine
Odin3 v3.13.1_3B_PatcheD seems to have positive feedback here on XDA so should be fine too https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Beanvee7 said:
If your firmware files are from a trusted source like sammobile, updato or samfirmtool then it should be fine
Odin3 v3.13.1_3B_PatcheD seems to have positive feedback here on XDA so should be fine too https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
Thanks for the assist! Everything worked like a charm!
leprkon said:
Thanks for the assist! Everything worked like a charm!
Click to expand...
Click to collapse
Great glad it all worked out
leprkon said:
Thanks for the assist! Everything worked like a charm!
Click to expand...
Click to collapse
Greetings-
I apologize for jumping in an already created thread, but I think I am in the same situation, and like to verify with you both before I use the advice please. I have a SM-G930T that I just purchased, and really like to run a custom rom. But I understand I can not because I have Android 8 on it. I know how to use Odin, and have the latest version plus you guys talked about it here. I have also already downloaded the stock rom from sammobile site. What are my options? Is there a rom I can flash the phone with using Odin that would provide better performance, less G..bage, and more battery life? Is there a way for me to root the phone? I really need an app that requires the phone to be rooted.
Thanks
[email protected] said:
Greetings-
I apologize for jumping in an already created thread, but I think I am in the same situation, and like to verify with you both before I use the advice please. I have a SM-G930T that I just purchased, and really like to run a custom rom. But I understand I can not because I have Android 8 on it. I know how to use Odin, and have the latest version plus you guys talked about it here. I have also already downloaded the stock rom from sammobile site. What are my options? Is there a rom I can flash the phone with using Odin that would provide better performance, less G..bage, and more battery life? Is there a way for me to root the phone? I really need an app that requires the phone to be rooted.
Ok, so flash any unbranded Stock Rom for your device using this version of Odin which has been specifically modified to flash US devices. https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572 PatcheD.zip is the file you want to download.
Then when you have checked the phone is working ok on undrnaded firmware you can go ahead and root the device using this method which is again for US Qualcomm devices. https://www.****************/2018/0...on-galaxy-s7-and-s7-edge-on-android-8-0-oreo/
Take you time and read instructions.
Click to expand...
Click to collapse
Can I get unbranded stock firmware from sammobile? I understand the generic meaning of it, but I need more information on how to get them and what I need to know to work with them.
[email protected] said:
Can I get unbranded stock firmware from sammobile? I understand the generic meaning of it, but I need more information on how to get them and what I need to know to work with them.
Click to expand...
Click to collapse
If I understand it correctly there is no unbranded firmware for the US, its all network specific but you can flash unbranded UK firmware and it will work fine, UK BTU is the one you want from sammobile.
Load into the modified version of Odin and flash.
This is what I found, and downloading.
[email protected] said:
This is what I found, and downloading.
Click to expand...
Click to collapse
Yes that's the right one but like the beanvee and i have said there is a specific way to flash this stock then root the device.
You also need Samsung USB drivers installed so your pc can talk to your device, there's plenty of guides around how to flash with Odin and what you need to do beforehand, the only difference with you is the version of Odin your using and then the method of rooting afterwards.
cooltt said:
Yes that's the right one but like the beanvee and i have said there is a specific way to flash this stock then root the device.
You also need Samsung USB drivers installed so your pc can talk to your device, there's plenty of guides around how to flash with Odin and what you need to do beforehand, the only difference with you is the version of Odin your using and then the method of rooting afterwards.
Click to expand...
Click to collapse
Thanks. I have used Odin before, and I already downloaded the patchD version of Odin from the link. Thank you so much. I'll keep you posted on how it turns out. I still do not have a verified version of a custom recovery for this. Do you guys know of any? I found this link but the link to the suggested twrp does not work. I think it is this one. But I can not be sure. The original link points to a slightly different url.
[email protected] said:
Thanks. I have used Odin before, and I already downloaded the patchD version of Odin from the link. Thank you so much. I'll keep you posted on how it turns out. I still do not have a verified version of a custom recovery for this. Do you guys know of any? I found this link but the link to the suggested twrp does not work. I think it is this one. But I can not be sure. The original link points to a slightly different url.
Click to expand...
Click to collapse
Nope do not use that TWRP, it will flash TWRP but not boot it and you'll be stuck on Samsung logo forever.
There is still no way to unlock a Qualcomm snapdragon bootloader and i'm not sure anyone is working on it anymore.
All it means is you need to flash custom Roms via Odin or possibly the inbuilt S7 recovery, you just need to check the ROM is in a format which can be flashed that way.
With regards to finding a TWRP solution you'll have to do some serious searching on google and read everything.
There are already several de-bloated stock Roms on the forum if thats what you want to do. Root and custom recovery TWRP are two different things though, you get rooted so your good to go?
cooltt said:
Nope do not use that TWRP, it will flash TWRP but not boot it and you'll be stuck on Samsung logo forever.
There is still no way to unlock a Qualcomm snapdragon bootloader and i'm not sure anyone is working on it anymore.
All it means is you need to flash custom Roms via Odin or possibly the inbuilt S7 recovery, you just need to check the ROM is in a format which can be flashed that way.
With regards to finding a TWRP solution you'll have to do some serious searching on google and read everything.
There are already several de-bloated stock Roms on the forum if thats what you want to do. Root and custom recovery TWRP are two different things though, you get rooted so your good to go?
Click to expand...
Click to collapse
Yes root is my main goal, and you are right the debloated roms will work just fine. I can do w/o twrp. Just double checking here; since I am flashing the UK rom, and I believe one of the comments on this thread was how US images are locked tighter, would not I be able to find a UK version of TWRP for my phone? Just checking.
[email protected] said:
Yes root is my main goal, and you are right the debloated roms will work just fine. I can do w/o twrp. Just double checking here; since I am flashing the UK rom, and I believe one of the comments on this thread was how US images are locked tighter, would not I be able to find a UK version of TWRP for my phone? Just checking.
Click to expand...
Click to collapse
Now pull up a chair and listen closely.....99% of the American devices (including yours) have an extremely uncooperative Qualcommm Snapdragon cpu at it's heart and thus refuses point blank to play ball. The online community have done a fantastic job creating the modifications you are now using. The rest of the world (i'm happy to say) enjoy the S7 with an extreamly cooperative Exynos cpu at it's heart. It just loves to be fiddled with, it's a whore of a chip, constantly on the go with all kinds of neat tricks.
Anyhoo... my point is, the software has to be compatible with the hardware you catch my drift? All the cool little programs are written with a specific piece of hardware in mind, unfortunately for you guys Qualcomm is the ice queen.
cooltt said:
Now pull up a chair and listen closely.....99% of the American devices (including yours) have an extremely uncooperative Qualcommm Snapdragon cpu at it's heart and thus refuses point blank to play ball. The online community have done a fantastic job creating the modifications you are now using. The rest of the world (i'm happy to say) enjoy the S7 with an extreamly cooperative Exynos cpu at it's heart. It just loves to be fiddled with, it's a whore of a chip, constantly on the go with all kinds of neat tricks.
Anyhoo... my point is, the software has to be compatible with the hardware you catch my drift? All the cool little programs are written with a specific piece of hardware in mind, unfortunately for you guys Qualcomm is the ice queen.
Click to expand...
Click to collapse
Thank you so much. You guys are amazingly patient, and informative. Thank you for educating me, and helping me achieve my goal.
I have tried a few times but can not flash the files. I have attached screenshots, and followed the instructions here. Do you see anything I should be doing differently?
I initially thought the code came as one tar file, which I could flash, but it was a zip file, which I had to unpack.
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
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).