Related
Good morning,
I've recently moved to Japan and purchased an HTC 10 from AU / KDDI. The version information is as follows: CID KDDI_801, MID 2PS670000 / htc_pmeuhljapan. This is my first time dealing with a non-US phone. I've unlocked, s-offed, etc and installed CyanogenMod on my US HTC phones. I've managed to S-OFF / Unlock the AU phone. However, I was unable to root without TWRP or backup the stock recovery. So I flashed TWRP onto it, rooted and that whole deal without issue. I've also backed up my System Image / Boot.
This broke my OTA updates (surprise surprise) but I found an update here: http://forum.xda-developers.com/htc-10/help/htc-10-au-japan-ota-zip-file-t3490829/page2 and attempted to flash. I cannot flash the entire zip file, however, my phone will take the firmware file within. This seems to update the firmware from 1.28 to 1.95. However, this breaks the phone's WiFi (WiFi won't see any networks), but seems to re-install stock recovery.
Still, the OTA updates failed. So I reflashed TWRP recovery and restored my backup. WiFi works just fine again. After I restore the backup it says OS-1.95.970.4 in download mode, however, in the OS itself it shows the old build number 1.28.xxxx. Does anyone have an applicable copy of the stock recovery I can throw on there and attempt to get an OTA update? If not, would international ROM's work with this phone or do I need to find Japan specific? I know they have some of their own bands so I'm not sure of compatibility issues. If you need any additional information please let me know. Sorry if any of the questions / circumstances seem ridiculous, again, I've never had to deal with a non-US phone so there's a bit less information available.
i also use htc 10 of Au japan, can you upload an stock or backup of stock of it. my phone cant boot now
is this phone water proof?
minori_aoi said:
is this phone water proof?
Click to expand...
Click to collapse
No
Hi..which twrp did you flash?
Sir how you unlocked this phone. ?
I dont know i try sunshine and the htcdev there is no way to unlocked bootloader it's furstasing.... :crying:
And another way is buy xtc2clip the price is like so so expensive :crying:
Dear all
There are so many people looking for exactly samething that iam looking for but unfortunately there is not any proper tutorial available.
Could you confirm if there is anyway to install any other ROM on chinese moto z play ? i don't mind if i have to install each OTA manually.
If so could you please guide step by step guide how to perform this?
If there so no any ROM that can work with chinese variant is there any custom ROM that would and support Moto Mods?
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
freeman_g said:
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
Click to expand...
Click to collapse
Did you try editing build.prop?
jameelmemon said:
Did you try editing build.prop?
Click to expand...
Click to collapse
I see that you has not even tried to look through my thread (link was provided in previous post). Suggest to do that (espesially the very end) before further questions / discussion
I have gone through almost all threads including your befiore posting or asking you that question
you are referring to
2) target script is probably /device/company_name/device_name/init.device_name.usb.rc
3) there is a string in that script: write /sys/class/android_usb/android0/iProduct ${ro.product.model}
aactualy {ro.product.model} is variable in build.prop so that script (/device/company_name/device_name/init.device_name.usb.rc) from build.prop
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Finally i manage to install 7.1.1
My phone is addison after installing RETAIL version (7.0)
I installed RETAIL version then downloaded ota then installed 7.1.1 OTA from this thread https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
phone should not be locked/encrypted or protected at least i bricked it and it was not booting up.
Now need to change two things those are in bootloader (SKU and ro.carrier) fastboot getvar all
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Just found ro.carrier comes from kernel and will be taken from kernel each time devices boots up. so we need someone to customize the kernel and add retru or retus to kernel as ro.carrier.
sku i can not change as i am getting error of command is not allowed
can anyone help regarding this?
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
freeman_g said:
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Click to expand...
Click to collapse
freeman_g said:
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Click to expand...
Click to collapse
Just install fresh retail version then sideload first ota via adb then boot your phone do not complete setup.
then install 7.1.1 then do factory restore then you are good to go
and it have so many great features you can view them here specially camera app
freeman_g said:
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
Click to expand...
Click to collapse
Initally it didn't work and stuck on bootloader unlock warning but later it worked perfect and iam using 7.1.1 and now trying to figure out how we can change sku and channel to get official OTA.
Sku (XT1635-03) is in bootloader but i can't write is with Fastboot, channel (retcn) is in kernel.
Lucky you I still have the same problem
Yesterday I tried to start with flashing stock retail 7.0 (the link you have provided earlier) but due to fact I had already flashed image with April security patch I didn't manage to downgrade bootloader and gpt (security downgrade issue)
Despite this fact phone boots but small OTA with April security patch did not agree to flash for the same reason: wrong name "addison_retcn"
So I believe the problem is in bootliader and I will probably manage to fix it only with full 7.1.1 retail image.
Glad to see you guys are making some progress. I'll try flashing the retail version on my Chinese Z Play. I'm currently on Epsilon rom (stock rooted 7.0) with January patch. Can I flash retail and then the ota?
I woulf suggest the following:
1) At your current firmware install Aida64 and check if you have addison or addison_cn product name in System section. If you see only addison - then you may install retail firmware and OTAs
2) If you still have addison_cn here then try to install retail firmware provided above (bootloader can be upgraded) and then check product name in Aida64 again. If it changed to addison - you can sideload OTAs. If still addison_cn - then you can't
Thanks @freeman_g
Here is a screenshot of AIDA64 on my device: https://imgur.com/gallery/Or2JF
I guess I should be good to go, right?
Yes, should work
What I can't understand why I still with addison_retcn. Probably, will have to wait for full 7.1.1 retail image
Sorry for the noobie question, but how did you guys with XT1635-03 flash the XT1635-02 firmware? Did you use this script? Did you flash the full rom, including partition, fsg, and modem, no restrictions? I bought my device at Banggood. I know it will come with a shop rom and I would like to install the stock firmware. I want to be prepared when it arrives. Don't want to take the risk of brick it and would like to leave the custom roms for later.
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
freeman_g said:
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
Click to expand...
Click to collapse
Awesome, many thanks for sharing. Does this mean you'll receive future OTAs?
Hello, today i recived an LG G7, but it has firmware brand (TIM)
I was wondering if I changed the firmware with another one, would I get the automatic updates via ota?
Thanks
I bought a TIM branded device, flashed stock 10k OPEN kdz and I don't think the OTA is working
i have the same issue, someone can help?
frenkio said:
Hello, today i recived an LG G7, but it has firmware brand (TIM)
I was wondering if I changed the firmware with another one, would I get the automatic updates via ota?
Thanks
Click to expand...
Click to collapse
I also had tim and when I switched to no brand I stopped receiving ota and also lg bridge no longer updates my phone. I now use LGUP every time there is an update and do a manual upgrade. The lg bridge update log says the phone fails an imei test so I believe there's no other way to update for me and probably for you too.
Sneppahtihs said:
I bought a TIM branded device, flashed stock 10k OPEN kdz and I don't think the OTA is working
Click to expand...
Click to collapse
I bought G7 TIM branded and I flashed EU open kdz. Even though I dont see any branded apps or stuff, in software info I still see 10q-222-01. Do u know how to make it EU Open?
torrat95 said:
I bought G7 TIM branded and I flashed EU open kdz. Even though I dont see any branded apps or stuff, in software info I still see 10q-222-01. Do u know how to make it EU Open?
Click to expand...
Click to collapse
That's the same thing mine is showing, isn't 10q open?
Sneppahtihs said:
That's the same thing mine is showing, isn't 10q open?
Click to expand...
Click to collapse
If it was pure open stock, it shouldn't show that "222-01" thing in software info. It should be "EUR-XX". And I can't make it that way. I'm wondering if anybody achieved it.
Same issue..received a Tim branded G7 so installed GBR open firmware from LG fan now all good no branding just no OTA UPDATES..Anyone know of a fix for this save flashing every new update.?
Any help/information much appreciated....
I’m going to try and flash the Italy open rom if there is one...see if that makes any difference..
What is the Italy code? Is it ITC?
So i flashed a few open firmwares..ITC and GBR open latest ones and earleir releases and none would OTA update only flashing back to origanal TIM firmware did it update OTA.
So its put up with branding etc and get all ota updates or flash a EU open firmware and keep doing this with every update.
frenkio said:
Hello, today i recived an LG G7, but it has firmware brand (TIM)
I was wondering if I changed the firmware with another one, would I get the automatic updates via ota?
Thanks
Click to expand...
Click to collapse
No, only with hands through lgup
So is there any way for users to istall an open F.W so you don’t have network branding or bloatware
And still receive the OTA updates?and security patches
I know it don’t really make a massive difference but the branding and boot screen really winds me up for some reason..
I could send device back as I purchased in the uk thinking it would be a uk phone but it’s Italian..still says LG-G710EM so I guess it’s the Euro variant..
guys, for LMG710EM which firmware should i flash to remove brand?
thanks in advance
opetany said:
guys, for LMG710EM which firmware should i flash to remove brand?
thanks in advance
Click to expand...
Click to collapse
Any that’s an open for your regional area...
Be aware if you do this you will no longer receive OTA updates.
I'm asking because i'm fresh in this topic (and generally in android) and i prefer to ask before i do something wrong.
Yes, i know that i will no longer receive OTA updates what is quite logic, but manual update via LGup isn't a big problem for me. Just less convenience.
So, for Poland, firmware G710EM10q_00_OPEN_EU_OP_1219.kdz should be okay, yes? and one more question, the process of updating via LGup looks like normal firmware updating (keeping the configuration and data) or like clean firmware flashing?
opetany said:
I'm asking because i'm fresh in this topic (and generally in android) and i prefer to ask before i do something wrong.
Yes, i know that i will no longer receive OTA updates what is quite logic, but manual update via LGup isn't a big problem for me. Just less convenience.
So, for Poland, firmware G710EM10q_00_OPEN_EU_OP_1219.kdz should be okay, yes? and one more question, the process of updating via LGup looks like normal firmware updating (keeping the configuration and data) or like clean firmware flashing?
Click to expand...
Click to collapse
Yes that’s an okay firmware for Poland and yes LGUP wipes and gives clean install each time I’ve used it..there maybe a way to upgrade once you have initial new firmware as you don’t want issues so clean install is best to start then investigate upgrade for next time.
When should 9.0 roll out? the G8 already released with it...
mikelt89 said:
When should 9.0 roll out? the G8 already released with it...
Click to expand...
Click to collapse
Christmas maybe.?
sas007 said:
Yes that’s an okay firmware for Poland and yes LGUP wipes and gives clean install each time I’ve used it..there maybe a way to upgrade once you have initial new firmware as you don’t want issues so clean install is best to start then investigate upgrade for next time.
Click to expand...
Click to collapse
Everything went well, thanks for your help!
Hi guys, I recently purchased a refurbished S9+ without knowing the model and it turned out to be a SM-G965U. After a failed software update ("Your current software isn't supported. Visit a service centre"), I've been trying to find a way to update the phone to 'official' Android 10. Does anyone know if this is possible or is the phone locked to Android 9?
'OEM Unlock' is missing from developer settings which (I think) means it can't be rooted with any common method. But is it possible to flash the phone with an official, working version of Android 10?
I'm willing to use any method required (within reason) to update the phone to a working version of Android 10. I'm aware of the "Extreme Syndicate" root method but the bugs / missing features rule it out for me. I intend to get a refund for the phone if it can't be updated to Android 10 so I'd really appreciate any answers to my questions.
Thanks!
You can manually update your phone by using Odin, and download the latest firmware available by using Frija
B1nz said:
You can manually update your phone by using Odin, and download the latest firmware available by using Frija
Click to expand...
Click to collapse
That's good news. Just to confirm, I can manually update with Odin WITHOUT unlocking OEM in the develop settings? Thanks for replying.
Just confirming that I successfully updated to Android 10 using Odin. The CSC I used is for an American carrier and the phone tries to register on its network but that's easily disabled. Had to be done after every reboot but it's a small price to pay for a working phone....
Hello Guys, I'm currently stuck on G965USQU3ZRLG
I made use of firmware.science to update my S9 plus to this point, but it seems there's no further firmware update for G965USQU3ZRLG to the next update file. Kindly assist, thank you.
Can someone please point me in the direction to Unlock Bootloader and Root the OnePlus 9 Pro T-Mobile Version? I had the Global US Unlocked OnePlus 8 Pro and it was simple. Thank you in advance!
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Have u received token from tmo
Alright, my bootloader is unlocked now, but I'm not sure how to root at this point. My software version is 11.2.2.2.LE54CB. I can't find that last part (LE54CB) anywhere for download, so I'm not sure where to get my boot.img from. Anybody have some ideas?
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
glitchsys said:
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
Click to expand...
Click to collapse
Please let me know if you find a way. I'm super hesitant because of this other thread but I'm not willing to stop using my rooted OP7pro until my 9 is rooted.
I'm about to use https://forum.xda-developers.com/t/...ot-image-and-apply-root-to-the-phone.4263811/ djsubterrain's guide. Seems straight-forward.
1. I downloaded the Payload_Dumper program
2. I grabbed the official ROM from OnePlus's support site (https://www.oneplus.com/support/softwareupgrade/details?code=PM1617074857015) which is the same version my phone is already running.
3. I unzipped the OnePlus9ProOxygen_22.O.05_OTA_0050_all_2103242259_3611e0858f954e7d.zip file I got from OnePlus and there is a payload.bin file
I have to reboot out of linux and into my Windows partition in order to do the next part. But the Payload_Dumper program is supposed to extract a "boot.img" file from the payload.bin; I copy the boot.img file to my phone, into a temporary directory or whatever, and I use the Magisk application on my phone (which can be installed even if not rooted) to patch the boot.img file. I can then use fastboot to flash that image file. (Fastboot Boot rooted_boot.img) and after I reboot, I should, in theory, be rooted.
Since I didn't touch the stock recovery, I should also, in theory, be able to accept OTA updates pushed to my phone. Just normally an OTA update would "unroot" your phone, but guide has a "To retain root access after ROM/OTA update" section that I'm sure to try out next time an update is available. Worst case scenario though, the OTA update unroots me and I have to grab the new version from OnePlus's support site and go through the procedure again to extract the boot.img, patch it on the phone then flash it.
hmm. technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA"
So there is a slight difference. Meh, should be ok. Worst case scenario I have to flash the entire "11.2.2.2.LE15AA "from OnePlus and I get T-Mobile De-Bloated.
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
jfsat said:
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
Click to expand...
Click to collapse
Happy to report it worked just fine. I was able to grab the boot.img from the "11.2.2.2.LE15AA" file on OnePlus's support site. I was able to use Magisk to patch the boot.img file. Then moment of truth..
"fastboot boot 11.2.2.2.LE15AA_patched_boot.img"
And my phone booted just fine. And it was now (temporarily) rooted. I was able to then go back into Magisk and direct-install root. Then reboot.
Magisk confirmed I'm still rooted.
So to all those curious, the boot.img from OnePlus Stock 11.2.2.2.LE15AA works fine on the T-Mobile 11.2.2.2.LE5ACB version.
I may look into using OOM or something to try and force-flash 11.2.2.2.LE5ACB onto my phone and completely De-T-Mobile this phone. I suspect I'll get OTA updates faster from OnePlus than I will from T-Mobile.
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
ryantf420 said:
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
Click to expand...
Click to collapse
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
glitchsys said:
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
Click to expand...
Click to collapse
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
glitchsys said:
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
Click to expand...
Click to collapse
yes yes please that would help
Rooting is simple. Once your boot loader is unlocked head over to the thread on how to unlock the boot loader. He posted a patched boot IMG for T-Mobile. Flash it in fast boot restart open open magisk manager click direct install it will detect your boot IMG is patched it installs and reboot.
MurphSAN84 said:
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Click to expand...
Click to collapse
ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Flash your tmobile modem over global.
Where to get tmo modem img?
ryantf420 said:
Where to get tmo modem img?
Click to expand...
Click to collapse
You were supposed to back your's up prior to conversion...