I have been trying to do this for a while. I have a Nexus 7 and want to enable band 12. I am rooted and have multirom working. Nothing I have tried seems to be working. Is this possible?
Thanks!
Okay, here is an update. I was able to get into diag mode with terminal emulator. I can see the com port in device manager. I installed various qpst and qxdm programs but cannot read all the nv from phone. It only reads to line 04122 WLAN QoS Mode. I am stuck!
I used adb to put it in diag mode, unlocked bootloader and rooted. I have connected in qxdm but still can't read or write. I need to get past this point to do anything. This tablet has a Qualcomm WRT1605L that supports 7 lte bands so I need to disable one (which one?) and enable band 12.
I have seen threads about the Nexus 5, which has the same chip, enable different bands. Help me please.
applegatetech said:
I have been trying to do this for a while. I have a Nexus 7 and want to enable band 12. I am rooted and have multirom working. Nothing I have tried seems to be working. Is this possible?
Thanks!
Click to expand...
Click to collapse
This is a method I've used on a number of Moto smartphones (Qualcomm chipsets only) to enable various LTE bands, including Band 12. In theory, since the Asus Nexus 7 is Qualcomm based, this method should work. It is my understanding that this works on pretty much any device with a Qualcomm platform. Also, as you likely already know, this method involves some rather tedious procedures involving binary coding within QXDM and QPST. If you are not already familiar with binary coding, it would be well advised to explore the topic before proceeding. The OP does delineate a fairly thorough explanation of this topic. https://forum.xda-developers.com/moto-e-2015/general/guide-enable-lte-bands-surnia-t3351673
It is also noteworthy that you should be running pure stock firmware to avoid any problems. Of course, once you have enabled the desired LTE band(s), you may then install a custom or stock based ROM of your choosing, as the enabled LTE band(s) will remain fully intact and fully functional. However, please note that LTE band support can be incumbent upon a particular ROM and the RIL/telephony configurations in place.
AeonFlux1603 said:
This is a method I've used on a number of Moto smartphones (Qualcomm chipsets only) to enable various LTE bands, including Band 12. In theory, since the Asus Nexus 7 is Qualcomm based, this method should work. It is my understanding that this works on pretty much any device with a Qualcomm platform. Also, as you likely already know, this method involves some rather tedious procedures involving binary coding within QXDM and QPST. If you are not already familiar with binary coding, it would be well advised to explore the topic before proceeding. The OP does delineate a fairly thorough explanation of this topic. https://forum.xda-developers.com/moto-e-2015/general/guide-enable-lte-bands-surnia-t3351673
It is also noteworthy that you should be running pure stock firmware to avoid any problems. Of course, once you have enabled the desired LTE band(s), you may then install a custom or stock based ROM of your choosing, as the enabled LTE band(s) will remain fully intact and fully functional. However, please note that LTE band support can be incumbent upon a particular ROM and the RIL/telephony configurations in place.
Click to expand...
Click to collapse
I still get stuck on reading the values from the nv browser. I have tried many different drivers. I think this is the problem. None of the drivers seem to work.
applegatetech said:
I still get stuck on reading the values from the nv browser. I have tried many different drivers. I think this is the problem. None of the drivers seem to work.
Click to expand...
Click to collapse
Which of the Qualcomm drivers are you using? And, if you are running Windows 10 - 64 bit, you must enable test signing on your PC or laptop in order to properly install the unsigned Qualcomm drivers. I've seen several people get into a snag over installing the unsigned drivers, and yours sounds like a driver issue... I agree with you there. You will not be able to properly access any of the NV values if drivers are not installed correctly.
I did get the drivers working by typing setprop sys.usb.config diag. Previously I was using setprop sys.usb.config diag,adb and I could read but not write. Now I can change the gsm radio but the lte bands reset to 1,2,3,4,5,13,17. I'm wondering if this is hardware locked. I read that there are filters on the chipset which is Qualcomm WRT1605L.
I tried a custom kernel also without success. Then I flashed 4.3 and rooted, nope. I think it is hopeless.
applegatetech said:
I tried a custom kernel also without success. Then I flashed 4.3 and rooted, nope. I think it is hopeless.
Click to expand...
Click to collapse
Have you tried downgrading your Baseband to a previous version?
AeonFlux1603 said:
Have you tried downgrading your Baseband to a previous version?
Click to expand...
Click to collapse
I thought it was included in the factory image from google. I flashed 4.3 (original os for this device) from fastboot.
Thanks for your help.
applegatetech said:
I thought it was included in the factory image from google. I flashed 4.3 (original os for this device) from fastboot.
Thanks for your help.
Click to expand...
Click to collapse
Ahh, yes -- you are 100% correct. By flashing a factory stock image, which is previous in build to the build number currently on your device, you are thus fully downgrading your stock Android OS, stock kernel, stock recovery, stock modem firmware, etc.
I'm still on the theory that your Q-comm & vCom drivers may not be installed correctly on your PC or laptop. If you are running the Windows 10, 64-bit OS on your computer, you will need to configure a few things first, including the enablement of Test Signing. Here is an excellent how-to guide on installing unsigned drivers on 64-bir Windows 10. https://www.supportrix.com/kb/how-to-install-unsigned-drivers-in-windows-10/
Note: there are two methods listed for authorizing your PC/laptop to install unsigned driver packages. Either method you choose will suffice.
Related
hello guys
need yout help, tried searching google for sulotion but came up empty.
ive rooted the lg g4 h815(android 6.0-V20c-SEA) before via iroot pc but after factory reset its returned to be unrooted.
when i try to root again its keep failing because of debugging issue (the software keep telling me its not in debugging altough it is)
i think the problem is when i do usb debugging - connecting to pc the option is checked in the check box but it turns gray.whats the problem is? how can i fix it ?
thank you in advance
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, if the the G4 Factory Reset protocol deletes the system partition, and then reinstalls it, then this would explain why/if you lost root, I do not know if that's the protocol though. If iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
I recommend wiping Data, Cache and Dalvik from TWRP next time, if that's not what you did this time. :good:
Williquah said:
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, although I've never heard of that, if iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
Click to expand...
Click to collapse
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
mikmikush said:
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
Click to expand...
Click to collapse
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Williquah said:
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Click to expand...
Click to collapse
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
About phone ????
mikmikush said:
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
Click to expand...
Click to collapse
Sorry for forgetting the whole reason you're in this problem is because of a factory reset lol, of course you have your data backed up. And trust me, I understand about the brick, I really messed up my G3 2 years back. Thanks also for the device pictures, could you post a shot of "About Phone=>>Software Info". That would be great!
Funny thing I just did that same phone rotation thing very recently XD
Lol love rotation, here
mikmikush said:
Click to expand...
Click to collapse
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Williquah said:
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Click to expand...
Click to collapse
Thank you thank you! You are awesome.
I will follow the links later and reply ...
I will ???? thank you
@mikmikush You're welcome, my pleasure!
Williquah said:
@mikmikush You're welcome, my pleasure!
Click to expand...
Click to collapse
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
its like my problem?
what did u do?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
H815 SEA?/Same software version and error?
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
htr5 said:
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Williquah said:
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
H815 SEA?/Same software version and error?
Click to expand...
Click to collapse
Williquah said:
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Click to expand...
Click to collapse
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
mikmikush said:
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
Click to expand...
Click to collapse
Trust me, I understand your frustration, I'm going to make a guide for you in the next 6 hours or so.
Try a different computer if you can, I haven't had adb fail but many other tools sometimes work
on different computers for me. I've also heard "Dell PC Suite" should be uninstalled as it could cause adb hang ups,
if you have it. @htr5's guide might work for you if you have a software update available, I'm not sure though since it's not specifically for your device.
Regardless, I'm sure you will need to use adb soon, so we have to fix that.
I will try to make that guide asap, I obviously can only do so much, again, since I don't have your device, hopefully it will help though. I highly suggest trying on a fresh/different computer though.
Edit: Try USB 2.0 if you were using a 3.0 port (3.0 ports have the SS along with the usb "logo")
USB 2.0 is on the right:
"H815 SEA Root/General Guide"
@mikmikush
It does seem that you can treat your SEA device very similarly to the EU common version, in ways such as flashing KDZ's and rooting.
I cannot confirm this, but mentions in this thread: http://forum.xda-developers.com/g4/help/safe-root-h815-v10b-sea-variant-t3184152 make it seem like it should be okay.
Aoi_sora9x said:
I'm a SEA variant holder here.
It's fine, you can use the Low Effort Root method. You can also flash the EU open KDZ without any problem.
You lose VoLTE, but to me it doesn't matter so I don't really care.
I'm running the latest 10E ATM, and it's much much better than 10B, so flash away.
Click to expand...
Click to collapse
Yes, that post is for v10b, but it should also work for v20d/v20c. (Not the Low Effort Root method) - You will be working with EU software v20d.. while you are with SEA v20c,
so it's up to you if you want to try this, but it's the closest I can come right now. Thank @htr5 because I believe he has all of this in his guide, and I'll probably send you to his guide halfway through.
You may lose some features or brick your device by flashing firmware/software made for other devices. Trust your instinct!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install adb setup from here this includes necessary adb drivers, adb itself, and fastboot.
2. Install LG Mobile Driver
3. Download LGUP tool from here (This is for restoring your device to stock if you softbrick via KDZ)
Follow this thread if/when you need to.
4. Here contains a KDZ for EU v20C, which I'm 99.9% sure will match your current software, even though it says for EU.
5. Here contains every partition including the KDZ for 20d by @autoprime, which will be necessary if you decide to root from @htr5's guide (v20d Root Method)
6. Once again, try to unlock the bootloader officially through LG, if you are successful, you can follow @htr5's 20d Root Guide here
7. Be careful and let me know how it goes
@autoprime Mentions that there is "NO anti-rollback qfuse used in this update" (20d) so if you flash the 20d KDZ and it works, I believe you should then be able to downgrade successfully to an earlier firmware version - without worrying about qfuse - and root using a Lollipop (5.0/5.1) method if you can't get anywhere on Marshmallow (6.0). - This I'm not 100% positive about, again, but it is my thinking.
Please thank anyone I mentioned and anyone who's link I provided, they all deserve it!
Hi!
So I bought a HTC 10 from Amazon back in May and, even though the product description said it was the US version which had LTE bands for US carriers (specifically 4-AWS), they sent me a M10h, which is the international/asian version that doesn't support band 4. I can't return the phone though, since I'm from Argentina and with the insane customs ruling here, sending the phone to the US and back would cost me almost as much as just buying selling mine (at a highly reduced pricepoint since it doesn't support LTE in my country) and buying a new one.
After a lot of reading here in XDA, paying 25$ to be S-Off, flashing radios, changing roms and kernels, and a bunch of other stuff, I've come to the conclusion that my only alternative left is to change the 06828 NV value (which determinates what LTE bands are activated) with QXDM/DFS tools/whatever program. I've managed to put the phone in diag mode (for those who don't know how, I'll leave a little tutorial in the end of the thread), but when I write the value and then read it again it's back to its original state. I guess this is some kind of protection Qualcomm/HTC/whoever put in place to avoid users messing around with this stuff.
I read in the HTC One M9 forums that users with CDMA phones could change the 06828 value, while I, using a GSM phone, have been able to change 06829. I tried using a Verizon radio, which turns on and off the diag mode for some reason, and a Sprint radio, which gives me a "diag error response" in QXDM when I try to read/write any NV value.
Maybe a custom kernel can help avoid the write protection for NV values? I don't know a lot about that kind of stuff, so it's the only thing that I believe could change my situation
Phone info:
White HTC 10 M10h model
LeeDroid 10 v2.4.1-stable rom with CleanSlate kernel
S-Off and root
Baseband version [email protected]_51.01_F
---------------------------------------------------------------------------
For those who can't make it to Diag Mode:
1) Install the HTC Diag Drivers in your PC
2) Install a terminal emulator in your phone (in my case I used SManager)
3) Connect the phone to the computer with the USB cable
4) In the terminal emulator use:
Code:
su
and then
Code:
setprop sys.usb.config diag
5) Now touch on the "Use USB for" notification.
6) If everything worked, the phone should block you from choosing any option in the list besides Charging and USB tethering
7) Choose USB tethering
8) Your phone should appear in the Windows Device Manager as HTC Diagnostic Interface, which means the phone is in Diag Mode
9) To return to the default USB mode, repeat step 4, but replacing setprop sys.usb.config diag for
Code:
setprop sys.usb.config mtp
--------------------------------------------------------------------------
Does anyone know any way to make my phone work? Any kernel made from scratch I can try? I'm really desperate.
Thank you all for reading!
wouldnt flashing the us unlocked ruu work out since your all s-off and unlocked?
afuller42 said:
wouldnt flashing the us unlocked ruu work out since your all s-off and unlocked?
Click to expand...
Click to collapse
Unfortunately, it doesn't. As I can check both trying to use the phone or reading the NV values with DFS tool, the LTE bands remain the same no matter what RUU, radio or whatever I try.
Up!
Nachorl250 said:
Up!
Click to expand...
Click to collapse
Could you post a guide as to how can it be done?
INDIAN-MAfIA said:
Could you post a guide as to how can it be done?
Click to expand...
Click to collapse
I'm sorry, I don't get what you're asking me. A guide to do what?
Nachorl250 said:
I'm sorry, I don't get what you're asking me. A guide to do what?
Click to expand...
Click to collapse
I thought you got your unlocked band 'up and running' not realising you just wanted to accelerate your thread to the top. My bad.
INDIAN-MAfIA said:
I thought you got your unlocked band 'up and running' not realising you just wanted to accelerate your thread to the top. My bad.
Click to expand...
Click to collapse
No problem!
Nachorl250 said:
Unfortunately, it doesn't. As I can check both trying to use the phone or reading the NV values with DFS tool, the LTE bands remain the same no matter what RUU, radio or whatever I try.
Click to expand...
Click to collapse
As I have stated in other posts, we need a kernel built from scratch rather than a "custom kernel".
No custom kernel for Sense is going to work for this purpose.
Cyanogenmod technically provides that built-from-scratch kernel that we need., but the trick there is enabling Diagnostic Mode.
You can either flash Resurrection or Beanstalk and try to find a way to activate it.
An idea that could work is messing arround with the init.qcom.usb.rc and init.usb.rc files.
Those files include the triggers for several usb modes (the setprop sys.usb.config line).
The problem for Cyanogenmod is that those files don't include triggers for Diag.
So one way could be to replace them or modifying them.
I'm no coder at all, but to modify those files we need to modify the ramdisk at the boot partition.
If we don't, every modification to these files won't be kept past reboot.
Even achieving it won't assure Diag Mode, but I'm running out of ideas.
This certainly trascends my scarce knowledge
And CM is not at a point suitable for daily driver, so any testing there would be going back and forth between CM and Sense.
So unless we find a way to enable Diagnostic Mode on CM we are stuck.
I ran into the same issue as you. I bought a white 32gb thinking it was all the same, didn't know that it was the m10h.
I had to s-off, and change the CID and MID number to SuperCID and US unlocked MID , then install the latest US RUU to get the US firmware/radios/etc.
Currently on T-mobile, and all I have in my area is Band 12 (which my phone picks up), and I saw it pick up another band, but can't recall what it was. I wanna say that it worked, but I can't verify that my phone is actually reading all of the US LTE bands.
I'm switching to cricket (att) sometime this week. Once I switch over, I can check to see which bands im getting around my home and work
activated my cricket SIM, and I'm currently connecting to band 17.
will drive around town and take notes on what bands i pick up
Sports same issue here, I can't get my phone to work on au network in Japan.
kainanmaki said:
As I have stated in other posts, we need a kernel built from scratch rather than a "custom kernel".
No custom kernel for Sense is going to work for this purpose.
Cyanogenmod technically provides that built-from-scratch kernel that we need., but the trick there is enabling Diagnostic Mode.
You can either flash Resurrection or Beanstalk and try to find a way to activate it.
An idea that could work is messing arround with the init.qcom.usb.rc and init.usb.rc files.
Those files include the triggers for several usb modes (the setprop sys.usb.config line).
The problem for Cyanogenmod is that those files don't include triggers for Diag.
So one way could be to replace them or modifying them.
I'm no coder at all, but to modify those files we need to modify the ramdisk at the boot partition.
If we don't, every modification to these files won't be kept past reboot.
Even achieving it won't assure Diag Mode, but I'm running out of ideas.
This certainly trascends my scarce knowledge
And CM is not at a point suitable for daily driver, so any testing there would be going back and forth between CM and Sense.
So unless we find a way to enable Diagnostic Mode on CM we are stuck.
Click to expand...
Click to collapse
Thank you for all the info! We should make a main thread on the subject so that we can better organize ourselves and everyone can help solve this problem.
Nachorl250 said:
Thank you for all the info! We should make a main thread on the subject so that we can better organize ourselves and everyone can help solve this problem.
Click to expand...
Click to collapse
I agree. But I think it could be better to wait for a full port of Cyanogenmod.
Guys over there are making big strides, and maybe they could help us achieving diag mode for CM.
Don't want to bug them with this issue until they are at peace with the full port (and they seem to be really close to the end).
It's sad, but I don't even know how to bake a rom modifying a couple of files.
Even in that case, my idea was to use part of the code of init.qcom.usb.rc and init.usb.rc from Sense.
And introduce it on the init.qcom.usb.rc and init.usb.rc files of CM.
Checking which folders are involved on the code, they are present too in CM.
Which makes me believe that modifying those files on CM could prove enough for DIAG to be activated with "setprop sys.usb.config diag". It's just a guess though.
I'm sure that maybe crpalmer and squid2 could help us with this later.
De alguna forma va a salir...
[FONT="]echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
[FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="]did you try this code? it work[FONT="]ed f[FONT="]or me on M8 on custom roms viper one, A[FONT="]RHD[FONT="], maximusHD and few others.
[FONT="]BTW i [FONT="]still cant get to write nv values on my phone either[FONT="]. The[FONT="]y[/FONT]revert to old values after reboot. Still trying to figure out a way. will be flashing [FONT="]custom [FONT="]kitkat bas[FONT="]ed rom with custom revovery to try my luck.
[FONT="]I even t[FONT="]r[FONT="]ied[FONT="] [/FONT][/FONT] to disable one supported band 20 just to be sure if [FONT="]is hardware limitation that is causing the nv val[FONT="]ues to revert. But i[FONT="] found out that the nv values[FONT="] are not being written al all. So it is definitely not [FONT="]band compatibility issue.
[FONT="]May you too could try the same and check if at all you are able to write to nv.[/FONT]
[/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT] [/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT]
---------- Post added at 05:51 PM ---------- Previous post was at 05:06 PM ----------
Nachorl250 said:
Unfortunately, it doesn't. As I can check both trying to use the phone or reading the NV values with DFS tool, the LTE bands remain the same no matter what RUU, radio or whatever I try.
Click to expand...
Click to collapse
Dont you have the option to select which radio band region to select as in Unlocked intl M8?
what does it show when you open phone info->select 3 dots->select radio band ? do you atleast have this option?
smartpal said:
[FONT="]echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
[FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="]did you try this code? it work[FONT="]ed f[FONT="]or me on M8 on custom roms viper one, A[FONT="]RHD[FONT="], maximusHD and few others.
[FONT="]BTW i [FONT="]still cant get to write nv values on my phone either[FONT="]. The[FONT="]y[/FONT]revert to old values after reboot. Still trying to figure out a way. will be flashing [FONT="]custom [FONT="]kitkat bas[FONT="]ed rom with custom revovery to try my luck.
[FONT="]I even t[FONT="]r[FONT="]ied[FONT="] [/FONT][/FONT] to disable one supported band 20 just to be sure if [FONT="]is hardware limitation that is causing the nv val[FONT="]ues to revert. But i[FONT="] found out that the nv values[FONT="] are not being written al all. So it is definitely not [FONT="]band compatibility issue.
[FONT="]May you too could try the same and check if at all you are able to write to nv.[/FONT]
[/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT] [/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT]
---------- Post added at 05:51 PM ---------- Previous post was at 05:06 PM ----------
Dont you have the option to select which radio band region to select as in Unlocked intl M8?
what does it show when you open phone info->select 3 dots->select radio band ? do you atleast have this option?
Click to expand...
Click to collapse
Instead of using "echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on", we use the setprop type of lines.
They work properly on stock HTC rom. You can enable ADB,MTP, RNDIS, Modem and so on, including the all important DIAG (Diagnostic).
And the reason it's not working on CM is that the presets that enable and disable this kind of command do not include DIAG in any of them.
So you can't use setprop to invoke DIAG, or at least to my knowledge. Would love to be proven wrong here.
Since the presets work in a script fashion, maybe using the line related to DIAG could trigger the mode, I just don't know how to use it.
For E.G, the setprop sys.usb.config=diag does the following on tht init.qcom.usb.rc file (located at root of FS).
Code:
on property:sys.usb.config=diag
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 900E
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/functions diag
write /sys/class/android_usb/android0/enable 1
setprop sys.usb.state ${sys.usb.config}.
Maybe someone does have a clue of how to use it on CyanogenMod. Which is closer to be a reality so maybe in some weeks we can ask the guys over the CM thread for some help.
kainanmaki said:
Instead of using "echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on", we use the setprop type of lines.
They work properly on stock HTC rom. You can enable ADB,MTP, RNDIS, Modem and so on, including the all important DIAG (Diagnostic).
And the reason it's not working on CM is that the presets that enable and disable this kind of command do not include DIAG in any of them.
So you can't use setprop to invoke DIAG, or at least to my knowledge. Would love to be proven wrong here.
Since the presets work in a script fashion, maybe using the line related to DIAG could trigger the mode, I just don't know how to use it.
Click to expand...
Click to collapse
setprop sys.usb.diag.config diagon
this code worked for me on M8 with CM11. It did enable the diag mode atleast for me. Just now tried it.
smartpal said:
[FONT="]echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
[FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="][FONT="]did you try this code? it work[FONT="]ed f[FONT="]or me on M8 on custom roms viper one, A[FONT="]RHD[FONT="], maximusHD and few others.
[FONT="]BTW i [FONT="]still cant get to write nv values on my phone either[FONT="]. The[FONT="]y[/FONT]revert to old values after reboot. Still trying to figure out a way. will be flashing [FONT="]custom [FONT="]kitkat bas[FONT="]ed rom with custom revovery to try my luck.
[FONT="]I even t[FONT="]r[FONT="]ied[FONT="] [/FONT][/FONT] to disable one supported band 20 just to be sure if [FONT="]is hardware limitation that is causing the nv val[FONT="]ues to revert. But i[FONT="] found out that the nv values[FONT="] are not being written al all. So it is definitely not [FONT="]band compatibility issue.
[FONT="]May you too could try the same and check if at all you are able to write to nv.[/FONT]
[/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT] [/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT][/FONT]
---------- Post added at 05:51 PM ---------- Previous post was at 05:06 PM ----------
Dont you have the option to select which radio band region to select as in Unlocked intl M8?
what does it show when you open phone info->select 3 dots->select radio band ? do you atleast have this option?
Click to expand...
Click to collapse
We don't have that option in the HTC 10
Nachorl250 said:
We don't have that option in the HTC 10
Click to expand...
Click to collapse
dont you have any option to go in testing mode just like *#*#4636#*#* for M8?
smartpal said:
dont you have any option to go in testing mode just like *#*#4636#*#* for M8?
Click to expand...
Click to collapse
Oh, I was looking for it in the settings menu. It doesn't change anything, though.
Hey all. I Have a AT&T LG K10 (K425 Build number is MXB48T). As the new model is slated to release, im becoming more set on the opinion that our devices will not be receiving Nougat. So my sights have been set on rooting. My question is this: what can I do to root my device? (And to give you a clue to my experience, I have been using a Huawei fusion 2 from 2010 ( old I know. I didn't have a choice in that one ) which had a slim ROM on it, with a hugely modified system which was for a virtual memory file to increase its performance).
I've noticed that there isn't exactly much development on other versions, but if someone could point me in the right direction, that'd be great.
Nobodyslight said:
Hey all. I Have a AT&T LG K10 (K425 Build number is MXB48T). As the new model is slated to release, im becoming more set on the opinion that our devices will not be receiving Nougat. So my sights have been set on rooting. My question is this: what can I do to root my device? (And to give you a clue to my experience, I have been using a Huawei fusion 2 from 2010 ( old I know. I didn't have a choice in that one ) which had a slim ROM on it, with a hugely modified system which was for a virtual memory file to increase its performance).
I've noticed that there isn't exactly much development on other versions, but if someone could point me in the right direction, that'd be great.
Click to expand...
Click to collapse
Since you have qualcomm chipset there is no way to root it.
gottlasz said:
Since you have qualcomm chipset there is no way to root it.
Click to expand...
Click to collapse
What's the deal with the Qualcomm chipset?
Nobodyslight said:
What's the deal with the Qualcomm chipset?
Click to expand...
Click to collapse
Non of the k10s that's running marshmallow (so 95% of them) can be rooted by any one click stuff (like kingroot,...). So the other solution would be to install Supersu in TWRP. In order to get into TWRP you either need to be rooted (obviously you are not) or you should get into fastboot and boot into TWRP from there. The MTK versions can get to fastboot and boot into TWRP without any problems. However the qualcomm versions are rarely able to get into fastboot and even if you manage to get into fastboot there is no way to flash or even just boot into TWRP... not to mention that you need to unlock your bootloader first which is also problematic in the qualcomm case.
gottlasz said:
Non of the k10s that's running marshmallow (so 95% of them) can be rooted by any one click stuff (like kingroot,...). So the other solution would be to install Supersu in TWRP. In order to get into TWRP you either need to be rooted (obviously you are not) or you should get into fastboot and boot into TWRP from there. The MTK versions can get to fastboot and boot into TWRP without any problems. However the qualcomm versions are rarely able to get into fastboot and even if you manage to get into fastboot there is no way to flash or even just boot into TWRP... not to mention that you need to unlock your bootloader first which is also problematic in the qualcomm case.
Click to expand...
Click to collapse
Why does qualcomm devices have so much troubles with fastboot, is it only with K10's or something else
Professor Woland said:
Why does qualcomm devices have so much troubles with fastboot, is it only with K10's or something else
Click to expand...
Click to collapse
My former LG LEON had the same symptoms. I guess it's qualcomms "secret" weapon against people trying to validate their warranty even if they messed up the device themselves...
Is it possible to downgrade to LL, and then root?OR Would doing that just be superlative to have MM?
Nobodyslight said:
Hey all. I Have a AT&T LG K10 (K425 Build number is MXB48T). As the new model is slated to release, im becoming more set on the opinion that our devices will not be receiving Nougat. So my sights have been set on rooting. My question is this: what can I do to root my device? (And to give you a clue to my experience, I have been using a Huawei fusion 2 from 2010 ( old I know. I didn't have a choice in that one ) which had a slim ROM on it, with a hugely modified system which was for a virtual memory file to increase its performance).
I've noticed that there isn't exactly much development on other versions, but if someone could point me in the right direction, that'd be great.
Click to expand...
Click to collapse
You can root if you are in MM too... Forget KingRoot... I am working on a new root method based of dirty cow. It involves very deep analysis of "init" and replacing sepolicy and getting root. It will be out in few days.
---------- Post added at 11:48 PM ---------- Previous post was at 11:44 PM ----------
gottlasz said:
Since you have qualcomm chipset there is no way to root it.
Click to expand...
Click to collapse
Almost every phone is rootable but most of them see easy root methods like one click root and stuff.
I am working on a new root method based of dirtycow. I am able to get temporary root using dirty cow on Android 6.0. Now I am making it permanent. Even MTK can root using the method. It will be out in few days!
Check this: https://forum.xda-developers.com/lg-k10/how-to/qualcomm-root-android-6-0-t3553674
Hi all. I would like to reinstall the firmware on my P6Pro, and though it's a UK unlocked, unbranded Vodafone model can I reinstall it with the EE firmware as it's the SIM I've used from day one?
My phone firmware is :
SQ1D. 220105.007
As far as I know, SQ1D.220105.007 is the only latest (January) firmware available for the Pixel 6 Pro. Correct me if I'm wrong, though. It's the only one listed at that official Google Pixel firmware webpage.
The above is correct, as is often the case they have consolidated all of it into one image in January.
Thanks people.
I have the Jan update.
Do you know why they even list selecting a carrier first?
greycounciller said:
Thanks people.
I have the Jan update.
Do you know why they even list selecting a carrier first?
Click to expand...
Click to collapse
Probably just a generic prompt for those devices or months that there are separate firmwares for different carriers.
Can't seem to get this feature to work.
When I go to "rescue" mode and connect phone, the repair doesn't seem to connect to phone and remains on loader page with phone showing "No Command"with the android bot on his back with a triangle above his open chest.
Retried it with different UK carriers and unlocked carrier.
Any thoughts?
greycounciller said:
Can't seem to get this feature to work.
When I go to "rescue" mode and connect phone, the repair doesn't seem to connect to phone and remains on loader page with phone showing "No Command"with the android bot on his back with a triangle above his open chest.
Retried it with different UK carriers and unlocked carrier.
Any thoughts?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool instead and see if that helps any better. I know Official Google Pixel Update and Software Repair is official, too - I'm not even clear on when the repair site will help that the flash site won't, since I've never used either. Lots of folks on here have used Official Google Android Flash Tool with great success, though. Let us know what happens.
Pixel repair tool hasn't been updated to support the 6/Pro yet - the only part of that website that works for either phone is the Fingerprint Calibration tool.
As above, install Google adb/fastboot drivers & then try to use the Android Flash Tool, that should work for you
DanielF50 said:
Pixel repair tool hasn't been updated to support the 6/Pro yet - the only part of that website that works for either phone is the Fingerprint Calibration tool.
As above, install Google adb/fastboot drivers & then try to use the Android Flash Tool, that should work for you
Click to expand...
Click to collapse
Thanks so much. That all makes sense.
DanielF50 said:
Pixel repair tool hasn't been updated to support the 6/Pro yet - the only part of that website that works for either phone is the Fingerprint Calibration tool.
As above, install Google adb/fastboot drivers & then try to use the Android Flash Tool, that should work for you
Click to expand...
Click to collapse
this is the right answer. Also, for every other Pixel that supports this Pixel Repair website (Pixel 3+), it's actually really hit or miss if the phone ever gets recognized at all.
Considering how amazing the Android Flash Tool works - unfortunately it looks like pixelrepair isn't getting the attention it deserves - probably for reasons that we aren't aware of - but development time is probably one of them.
Hi guys, just to let you know, eventually managed to do a flash with the 'Flash.andriod.com' tool. 5 mins and all easily done.
Thanks for all the help though.
I have a OnePlus 9 Pro. Lost my dual sim function after updating to Android 13 in a weird way (it was ok at first). Now it shows only one. I want to revert to the European LE2123 as saw it can support it. I am in Hong Kong and seems this is the best option as I don't need the India version and I don't necessarily need Chinese (at least I don't read Chinese).
I have searched and gone down too many rabbit holes- so hope someone has been there already and can guide me.
Thanks!
David
XDAdaveHK said:
I have a OnePlus 9 Pro. Lost my dual sim function after updating to Android 13 in a weird way (it was ok at first). Now it shows only one. I want to revert to the European LE2123 as saw it can support it. I am in Hong Kong and seems this is the best option as I don't need the India version and I don't necessarily need Chinese (at least I don't read Chinese).
I have searched and gone down too many rabbit holes- so hope someone has been there already and can guide me.
Thanks!
David
Click to expand...
Click to collapse
Your phone model ?
XDAdaveHK said:
I have a OnePlus 9 Pro. Lost my dual sim function after updating to Android 13 in a weird way (it was ok at first). Now it shows only one. I want to revert to the European LE2123 as saw it can support it. I am in Hong Kong and seems this is the best option as I don't need the India version and I don't necessarily need Chinese (at least I don't read Chinese).
I have searched and gone down too many rabbit holes- so hope someone has been there already and can guide me.
Thanks!
David
Click to expand...
Click to collapse
To revert your OnePlus 9 Pro to the European version of Android 13 (LE2123), you will need to flash the firmware for that version onto your device. This is a technical process that involves using specialized software to replace the operating system on your device.
Before you begin, you should make sure that you have backed up all of your important data, as the process will erase everything on your device. You will also need to download the firmware for the European version of Android 13 (LE2123) and the appropriate flashing tool.
To flash the firmware onto your device, you will need to follow these steps:
Enable developer mode on your device by going to Settings > About phone > Software information > More > Developer options.
Enable USB debugging on your device by going to Settings > Developer options > USB debugging.
Connect your device to your computer using a USB cable.
Open the flashing tool and follow the prompts to install the firmware onto your device.
When the process is complete, your device will restart and you should be able to use the European version of Android 13 (LE2123).
It is important to note that this process can be risky and may result in data loss or damage to your device if not done correctly. If you are not comfortable with technical processes or are unsure about how to proceed, it is recommended that you seek the assistance of a professional.
ElitePotato said:
Your phone model ?
Click to expand...
Click to collapse
Oneplus 9 Pro. LE2125. But I read somewhere that the LE2125 can be changed to LE2123 with the software change as it is not hardware-dependent entirely. Yes, the Indian hardware version has different radio frequencies, but the EU and US are very similar. Anyway- I have gone down a rabbit hole and not really sure.
XDAdaveHK said:
Oneplus 9 Pro. LE2125. But I read somewhere that the LE2125 can be changed to LE2123 with the software change as it is not hardware-dependent entirely. Yes, the Indian hardware version has different radio frequencies, but the EU and US are very similar. Anyway- I have gone down a rabbit hole and not really sure.
Click to expand...
Click to collapse
Use LE2125 msmtool and then flash the LE2123 OOS11 rom through fastboot. It can be done by payload flasher also, payload file is included in full rom zip. Once you have converted to LE2123, do a factory reset and you can update it normally all the way to OOS13.
.
.
Read the op9 guide if you are confused.
ChristianMorris said:
To revert your OnePlus 9 Pro to the European version of Android 13 (LE2123), you will need to flash the firmware for that version onto your device. This is a technical process that involves using specialized software to replace the operating system on your device.
Before you begin, you should make sure that you have backed up all of your important data, as the process will erase everything on your device. You will also need to download the firmware for the European version of Android 13 (LE2123) and the appropriate flashing tool.
To flash the firmware onto your device, you will need to follow these steps:
Enable developer mode on your device by going to Settings > About phone > Software information > More > Developer options.
Enable USB debugging on your device by going to Settings > Developer options > USB debugging.
Connect your device to your computer using a USB cable.
Open the flashing tool and follow the prompts to install the firmware onto your device.
When the process is complete, your device will restart and you should be able to use the European version of Android 13 (LE2123).
It is important to note that this process can be risky and may result in data loss or damage to your device if not done correctly. If you are not comfortable with technical processes or are unsure about how to proceed, it is recommended that you seek the assistance of a professional.
Click to expand...
Click to collapse
Thank you- thank you for being professional to provide assistance. I can do the flash but wanted to make sure it was safe/possible before I tried. Currently, the phone is not working well enough to keep it as is, so worth any risk to fix it. Currently using a Xiaomi 11T Pro and love it- so I know there is a huge gap in getting the OnePlus working properly again.
But where is the 'flashing tool' found?
XDAdaveHK said:
Thank you- thank you for being professional to provide assistance. I can do the flash but wanted to make sure it was safe/possible before I tried. Currently, the phone is not working well enough to keep it as is, so worth any risk to fix it. Currently using a Xiaomi 11T Pro and love it- so I know there is a huge gap in getting the OnePlus working properly again.
But where is the 'flashing tool' found?
Click to expand...
Click to collapse
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com