I bought used Moto Z Play (after my first MZP got stolen) XT1635-02 and don't receive updates.
M8953_10229.50.0465R
ADDISON_ROW_cust
Is this official ROM? I tried root app from Google play and it says no root.
Sent from my XT1635-02 using Tapatalk
Hmm, can you show us a screenshot of About Phone (Settings app>About Phone), to show us what build you have please and other details?
If you have ADB on a computer, then you could also try getting the getvar info from the device (assuming you have minimal ADB and preferably the Motorola USB drivers too):
Boot the device to the bootloader. Connect the device to your computer via USB.
Open the ADB terminal on your computer and type 'fastboot getvar all' without quotes into the terminal. Press Enter.
Please copy and paste the command output into a post here - you may wish to omit IMEI from the output (but please state if it's present if you remove it). This output should be a list of your device variables including what stock firmware it has.
echo92 said:
Hmm, can you show us a screenshot of About Phone (Settings app>About Phone), to show us what build you have please and other details?
If you have ADB on a computer, then you could also try getting the getvar info from the device (assuming you have minimal ADB and preferably the Motorola USB drivers too):
Boot the device to the bootloader. Connect the device to your computer via USB.
Open the ADB terminal on your computer and type 'fastboot getvar all' without quotes into the terminal. Press Enter.
Please copy and paste the command output into a post here - you may wish to omit IMEI from the output (but please state if it's present if you remove it). This output should be a list of your device variables including what stock firmware it has.
Click to expand...
Click to collapse
could not insert image., will try later. Have to use image hosting site?
Build number: NPNS26.118-22-2-12
vokmed said:
could not insert image., will try later. Have to use image hosting site?
Build number: NPNS26.118-22-2-12
Click to expand...
Click to collapse
Apparently I don't have permission to post an attachment in this forum.
Sent from my XT1635-02 using Tapatalk
vokmed said:
I bought used Moto Z Play (after my first MZP got stolen) XT1635-02 and don't receive updates.
M8953_10229.50.0465R
ADDISON_ROW_cust
Is this official ROM? I tried root app from Google play and it says no root.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
First off do we even know if the bootloader is unlocked if not then there is no way it is rooted. If the BL is unlocked is there any sign of a root app such as SU or Magisk? Being you had this same model before it was stolen, does any of the software seem different or missing any sign that the phone is rooted?
Jimi Mack said:
First off do we even know if the bootloader is unlocked if not then there is no way it is rooted. If the BL is unlocked is there any sign of a root app such as SU or Magisk? Being you had this same model before it was stolen, does any of the software seem different or missing any sign that the phone is rooted?
Click to expand...
Click to collapse
There is no sign of Magisk or SU. Comparing boxes seems the same model and the other phone had already security update on about january 12 installed. On current used phone , December 1st 2017 security patch. Could it be unlocked, flashed with different ROM? IMEI matches Packaging box label. And when I check about phone it has: ADDISON_ROW_cust, is that mean custom ROM?
In regards to fastboot, I'll have to buy usb cable, got stolen from my carry on in airport.
Jimi Mack said:
First off do we even know if the bootloader is unlocked if not then there is no way it is rooted. If the BL is unlocked is there any sign of a root app such as SU or Magisk? Being you had this same model before it was stolen, does any of the software seem different or missing any sign that the phone is rooted?
Click to expand...
Click to collapse
vokmed said:
There is no sign of Magisk or SU. Comparing boxes seems the same model and the other phone had already security update on about january 12 installed. On current used phone , December 1st 2017 security patch. Could it be unlocked, flashed with different ROM? IMEI matches Packaging box label. And when I check about phone it has: ADDISON_ROW_cust, is that mean custom ROM?
In regards to fastboot, I'll have to buy usb cable, got stolen from my carry on in airport.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know if you can flash stock with locked bootloader, but if you want to make sure you can flash this one , it's the latest ROM.
Btw: if you are on December 2017 patch level then it's no surprise you don't receive Updates, there are none
Artim_96 said:
I don't know if you can flash stock with locked bootloader, but if you want to make sure you can flash this one , it's the latest ROM.
Btw: if you are on December 2017 patch level then it's no surprise you don't receive Updates, there are none
Click to expand...
Click to collapse
I had a January update on my stolen phone...
Sent from my XT1635-02 using Tapatalk
vokmed said:
I had a January update on my stolen phone...
Click to expand...
Click to collapse
Well, that can't be January 2018 since that one isn't released yet
echo92 said:
Hmm, can you show us a screenshot of About Phone (Settings app>About Phone), to show us what build you have please and other details?
If you have ADB on a computer, then you could also try getting the getvar info from the device (assuming you have minimal ADB and preferably the Motorola USB drivers too):
Boot the device to the bootloader. Connect the device to your computer via USB.
Open the ADB terminal on your computer and type 'fastboot getvar all' without quotes into the terminal. Press Enter.
Please copy and paste the command output into a post here - you may wish to omit IMEI from the output (but please state if it's present if you remove it). This output should be a list of your device variables including what stock firmware it has.
Click to expand...
Click to collapse
Ok, here we go:
icrosoft Windows [Version 6.1.7601]
opyright (c) 2009 Microsoft Corporation. All rights reserved.
:\Users\Xxxxxx>fastboot getvar all
bootloader) version: 0.5
bootloader) version-bootloader: moto-msm8953-C1.13
bootloader) product: addison
bootloader) board: addison
bootloader) secure: yes
bootloader) hwrev: P7
bootloader) radio: 2
bootloader) storage-type: emmc
bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
bootloader) cpu: MSM8953
bootloader) serialno: ZY223NK9ZF
bootloader) cid: 0x0032
bootloader) channelid: 0x80
bootloader) uid: 0965095100000000000000000000
bootloader) securestate: oem_locked
bootloader) iswarrantyvoid: no
bootloader) max-download-size: 536870912
bootloader) reason: Volume down key pressed
bootloader) imei: XXXXXXXXXXXXXXX
bootloader) meid:
bootloader) date: 11-06-2016
bootloader) sku: XT1635-02
bootloader) battid: SNN5974A
bootloader) iccid:
bootloader) cust_md5:
bootloader) max-sparse-size: 268435456
bootloader) current-time:
bootloader) ro.build.fingerprint[0]: motorola/addison/addison:7.1.1/NPN
bootloader) ro.build.fingerprint[1]: S26.118-22-2-12/15:user/release-ke
bootloader) ro.build.fingerprint[2]: ys
bootloader) poweroffalarm: 0
bootloader) ro.build.version.full[0]: Blur_Version.26.241.15.addison.re
bootloader) ro.build.version.full[1]: tail.en.US
bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
bootloader) version-baseband: M8953_10229.50.04.65R ADDISON_ROW_CUST
bootloader) kernel.version[0]: Linux version 3.18.31-perf-gdc74c68 (hud
bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
bootloader) kernel.version[3]: ue Dec 5 06:42:56 CST 2017
bootloader) sbl1.git: git=MBM-NG-VC1.13-0-g12bcf78
bootloader) rpm.git: git=5578f74
bootloader) tz.git: git=82f94af-dirty
bootloader) devcfg.git: git=82f94af-dirty
bootloader) keymaster.git: git=82f94af-dirty
bootloader) cmnlib.git: git=82f94af-dirty
bootloader) cmnlib64.git: git=82f94af-dirty
bootloader) prov.git: git=82f94af-dirty
bootloader) aboot.git: git=MBM-NG-VC1.13-0-gd027fe9
bootloader) qe: qe 0/0
bootloader) frp-state: protected (77)
bootloader) ro.carrier: retca
ll: listed above
inished. total time: 0.102s
vokmed said:
Ok, here we go:
icrosoft Windows [Version 6.1.7601]
opyright (c) 2009 Microsoft Corporation. All rights reserved.
:\Users\Xxxxxx>fastboot getvar all
bootloader) version: 0.5
bootloader) version-bootloader: moto-msm8953-C1.13
<snip>
bootloader) securestate: oem_locked
bootloader) iswarrantyvoid: no
bootloader) max-download-size: 536870912
bootloader) reason: Volume down key pressed
<snip>
bootloader) ro.build.fingerprint[0]: motorola/addison/addison:7.1.1/NPN
bootloader) ro.build.fingerprint[1]: S26.118-22-2-12/15:user/release-ke
bootloader) ro.build.fingerprint[2]: ys
bootloader) poweroffalarm: 0
bootloader) ro.build.version.full[0]: Blur_Version.26.241.15.addison.re
bootloader) ro.build.version.full[1]: tail.en.US
bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
bootloader) version-baseband: M8953_10229.50.04.65R ADDISON_ROW_CUST
bootloader) kernel.version[0]: Linux version 3.18.31-perf-gdc74c68 (hud
bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
bootloader) kernel.version[3]: ue Dec 5 06:42:56 CST 2017
bootloader) sbl1.git: git=MBM-NG-VC1.13-0-g12bcf78
bootloader) rpm.git: git=5578f74
bootloader) tz.git: git=82f94af-dirty
bootloader) devcfg.git: git=82f94af-dirty
bootloader) keymaster.git: git=82f94af-dirty
bootloader) cmnlib.git: git=82f94af-dirty
bootloader) cmnlib64.git: git=82f94af-dirty
bootloader) prov.git: git=82f94af-dirty
bootloader) aboot.git: git=MBM-NG-VC1.13-0-gd027fe9
bootloader) qe: qe 0/0
bootloader) frp-state: protected (77)
bootloader) ro.carrier: retca
ll: listed above
inished. total time: 0.102s
Click to expand...
Click to collapse
Thanks for that. A few things:
1)Your iswarrantyvoid flag is still no, so suggests the previous owner did not unlock the bootloader. The warranty is still with the previous owner however, I'm not sure if Motorola will honour the warranty if you have any issues.
2)You have the December 2017 7.1.1 firmware on your device. As Artim_96 has pointed out, that seems to be the latest stock firmware for Moto Z Play devices. You'd likely only have a January 2018 patch with a custom ROM or perhaps if you were with the Motorola Feedback Network? Either way, you aren't expecting OTA updates yet (seems Oreo is in the works).
3)The baseband matches up with the baseband in that December 2017 stock ROM too:
Code:
BUILD REQUEST INFO:
SW Version: addison-user 7.1.1 NPNS26.118-22-2-12 15 release-keysM8953_10229.50.04.65R
MBM Version: C1.13
Modem Version: M8953_10229.50.04.65R
FSG Version: FSG-8953-04.90
Build Fingerprint: motorola/addison/addison:7.1.1/NPNS26.118-22-2-12/15:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 26.241.15.addison.retail.en.US
Model Number: XT1635-02
Android Version: 7.1.1
Baseband Version: M8953_10229.50.04.65R
Build Id: NPNS26.118-22-2-12
SW Display Build ID: NPNS26.118-22-2-12
Build Date: Tue Dec 5 06:32:05 CST 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.26.241.15.addison.retail.en.US
Version when read from CPV: addison-user 7.1.1 NPNS26.118-22-2-12 15 release-keys
AB Update Enabled: False
Full Treble Enabled: False
In summary, looks like you have the latest firmware on your device and the previous owner did not attempt to unlock the bootloader, so you should have Android Pay and Moto Mods active.
Thank you for prompt reply, appreciated!!!
1 - Even if I request a proof of of purchase from original owner? (when unlocked and re locked that flag will show "yes"?
2 - My other MotoZplay were getting security patches like a clock work once a month,...
3 - Reason all started that I cannot read NFC with it, it's enabled from menu
echo92 said:
Thanks for that. A few things:
1)Your iswarrantyvoid flag is still no, so suggests the previous owner did not unlock the bootloader. The warranty is still with the previous owner however, I'm not sure if Motorola will honour the warranty if you have any issues.
2)You have the December 2017 7.1.1 firmware on your device. As Artim_96 has pointed out, that seems to be the latest stock firmware for Moto Z Play devices. You'd likely only have a January 2018 patch with a custom ROM or perhaps if you were with the Motorola Feedback Network? Either way, you aren't expecting OTA updates yet (seems Oreo is in the works).
3)The baseband matches up with the baseband in that December 2017 stock ROM too:
Code:
BUILD REQUEST INFO:
SW Version: addison-user 7.1.1 NPNS26.118-22-2-12 15 release-keysM8953_10229.50.04.65R
MBM Version: C1.13
Modem Version: M8953_10229.50.04.65R
FSG Version: FSG-8953-04.90
Build Fingerprint: motorola/addison/addison:7.1.1/NPNS26.118-22-2-12/15:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 26.241.15.addison.retail.en.US
Model Number: XT1635-02
Android Version: 7.1.1
Baseband Version: M8953_10229.50.04.65R
Build Id: NPNS26.118-22-2-12
SW Display Build ID: NPNS26.118-22-2-12
Build Date: Tue Dec 5 06:32:05 CST 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.26.241.15.addison.retail.en.US
Version when read from CPV: addison-user 7.1.1 NPNS26.118-22-2-12 15 release-keys
AB Update Enabled: False
Full Treble Enabled: False
In summary, looks like you have the latest firmware on your device and the previous owner did not attempt to unlock the bootloader, so you should have Android Pay and Moto Mods active.
Click to expand...
Click to collapse
vokmed said:
Thank you for prompt reply, appreciated!!!
1 - Even if I request a proof of of purchase from original owner? (when unlocked and re locked that flag will show "yes"?
2 - My other MotoZplay were getting security patches like a clock work once a month,...
3 - Reason all started that I cannot read NFC with it, it's enabled from menu
Click to expand...
Click to collapse
1) You could get a proof of purchase from the original owner, if they're willing to give it to you. However, the warranty legal info does suggest the warranty is only awarded to the original purchaser and not transferable (this is for the UK: https://motorola-global-en-uk.custh...233517/redirect/1/filename/Warranty_EN_24.pdf ) However, depending on your local consumer protection laws, you may be able to get a repair. That being said, if the device is still in its warranty period (which is usually between 1-2 years), you could always try for a warranty repair, as the service centre may check the IMEI. Your experience may vary.
2)Yeah, seems that the Z Play updates are on hold whilst the Oreo update is being tested (since I've not seen any OTA updates, and the test build for Oreo seems to come with the February 2018 patch), so it's possible normal service and updates will resume once the new OS is deployed.
3)Hmm, that's odd - how are you testing NFC (I'm guessing with debit/credit cards?), is Android Pay working okay?
echo92 said:
1) You could get a proof of purchase from the original owner, if they're willing to give it to you. However, the warranty legal info does suggest the warranty is only awarded to the original purchaser and not transferable (this is for the UK: https://motorola-global-en-uk.custh...233517/redirect/1/filename/Warranty_EN_24.pdf ) However, depending on your local consumer protection laws, you may be able to get a repair. That being said, if the device is still in its warranty period (which is usually between 1-2 years), you could always try for a warranty repair, as the service centre may check the IMEI. Your experience may vary.
2)Yeah, seems that the Z Play updates are on hold whilst the Oreo update is being tested (since I've not seen any OTA updates, and the test build for Oreo seems to come with the February 2018 patch), so it's possible normal service and updates will resume once the new OS is deployed.
3)Hmm, that's odd - how are you testing NFC (I'm guessing with debit/credit cards?), is Android Pay working okay?
Click to expand...
Click to collapse
NFC I tested with tags that created with other MZP phone. With Android Pay I got only Amex card that I can add to AP and I haven't tested yet.
Thank for explaining my questions.
Sent from my XT1635-02 using Tapatalk
vokmed said:
NFC I tested with tags that created with other MZP phone. With Android Pay I got only Amex card that I can add to AP and I haven't tested yet.
Thank for explaining my questions.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
Just a thought, is it possible the NFC tags are linked to your other device? I wonder if a new NFC tag would register okay on your replacement device.
Could be worth seeing if the Amex card works.
echo92 said:
Just a thought, is it possible the NFC tags are linked to your other device? I wonder if a new NFC tag would register okay on your replacement device.
Could be worth seeing if the Amex card works.
Click to expand...
Click to collapse
Just tried with new tags from tagger.com with the case on and off in just a possibility of case blocking signal and ii does not work.
Sent from my XT1635-02 using Tapatalk
vokmed said:
Just tried with new tags from tagger.com with the case on and off in just a possibility of case blocking signal and ii does not work.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
[SOLVED] Just tried again and it worked, I guess I forgot about this weird antenna placement in top right corner that I did not move tags high enough...
Related
This thread's content might brick your device.
This is not a ROM thread, so I'm not going to answer again and again and again the same questions over and over and over again.
You can't read - quit this thread now. You can read but you can't understand more or less simple things - quit as well.
You can read and you understand things, but you are too lazy to read the whole thread before asking the question - watch this first. And quit.
This is what we know so far:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some conclusions:
1. It's very nice to see that finally someone separated "internal sd card" from userdata partition. So it's no longer linked to /data/media, as it used to be on Asus Transformer, Transformer Prime, Galaxy Nexus etc. but it's a separate partition now - mmcblk0p14. Basically the biggest benefit from that is that now formatting userdata partition will no longer erase virtual sd card content.
2. It seems that NFC and WLAN deep settings are stored on separate partitions: mmcblk0p1 (wlan) and ? (NFC).
3. There is a 5th PHYSICAL core, but it's invisible to the system. Android only sees the 4 main cores. The 5th companion core is not controlled by Android. Tegra 3 architecture itself handles the load balancing between the main cores and the companion core. (Thanks to Diamondback)
4. There is no radio.img in current RUUs.
Download firmware for HTC One X (PJ4610000)
Firmware from 1.28.401.9 RUU
--- MD5 checksum: 83375DF988C86E92417AA8949012A1C2 *PJ46IMG.zip ---
Supported devices:
--- CID's added by users requests are marked with green color ---
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__016
cidnum: HTC__M27
Why it's better then full RUU:
1. It doesn't contain stock recovery
2. It doesn't contain stock, non rooted system
3. It doesn't contain secured boot.img
4. It wont wipe your data partition
5. It's much smaller
PJ46IMG.zip content: [UPDATE: 25.03.2012]
android-info.txt - updated [20.04.2012]
bct.img - updated [25.03.2012]
rcdata.img - updated [20.04.2012]
How to flash:
1. Check your CID using fastboot getvar cid and MID using fastboot getvar mid
2a. If your CID and MID are supported by default, navigate to point 3.
2b. If your CID or MID is not supported by default, do this: (you do it at your own risk)
2c. Open PJ46IMG.zip (don't extract it)
2d. Open android-info.txt in text editor
2e. Add your cidnum: <your CID> or modelid: <your MID> to the list, save file and close archive
3. Place PJ46IMG.zip on your SD card
4. Boot your device holding power button + vol down button
5. Follow instructions on the screen
Additional information:
1. Flash above firmware at your own risk!
2. It's recommended to flash it before flashing custom ROM based on proper RUU!
3. Unlocking via htcdev.com will change your CID number into "none".
4. RUU variants:
x.xx.61.x - Orange UK (United Kingdom)
x.xx.75.x - Orange ES (Spain)
x.xx.110.x - T-Mobile UK (United Kingdom)
x.xx.111.x - T-Mobile DE (Germany)
x.xx.112.x - T-Mobile AT (Austria)
x.xx.114.x - T-Mobile NL (Netherlands)
x.xx.118.x - T-Mobile PL (Poland)
x.xx.161.x - Vodafone UK (United Kingdom)
x.xx.166.x - Vodafone CH-DE (Switzerland - Germany)
x.xx.163.x - Vodafone FR (France)
x.xx.169.x - Vodafone AT (Austria)
x.xx.206.x - O2 UK (United Kingdom)
x.xx.207.x - O2 DE (Germany)
x.xx.401.x - World Wide English
x.xx.707.x - Asia WWE (World Wide English)
x.xx.720.x - Asia India
x.xx.771.x - Hutchison 3G UK (United Kingdom)
x.xx.862.x - Voda-Hutch AU (Australia)
x.xx.980.x - Optus AU (Australia)
x.xx.1400.x - HTC China
Please post here your findings, thoughts or experience with after flashing images listed above.
Here are some details about CPU kernel settings:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
51000 | 102000 | 204000 | 340000 | 475000 | 640000 | 760000 | 880000 | 1000000 | 1100000 | 1200000 | 1400000 | 1500000
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
interactive conservative ondemand powersave userspace performance
Some details about how Tegra 3 works on HTC One X:
1. While screen is turned OFF only cpu0 is online. cpu1, cpu2 and cpu3 are all offline.
2. I think that cpu2 and cpu3 are online only on heavy load. That needs to be confirmed.
3. While screen is turned OFF only interactive governor is available.
4. When battery is < 20%, CPU downclocks to 1.0 GHz.
Fastboot commands that doesn't work without S-OFF:
fastboot flash rcdata rcdata.img
fastboot oem writesecureflag
fastboot oem writecid
Arent there 4 main cores and 1 companion core, so only companion core should be running when screen off?
shaky156 said:
Arent there 4 main cores and 1 companion core, so only companion core should be running when screen off?
Click to expand...
Click to collapse
I don't see any companion core for now:
ls /sys/devices/system/cpu
cpu0
cpu1
cpu2
cpu3
cpu_on (output on ls = 2)
cpu_on_mdelay (output on ls = 0)
cpufreq
cpuidle
kernel_max
offline (output on ls = 1-3)
online (output on ls = 0-3)
possible (output on ls = 0-3)
present (output on ls = 0-3)
mike1986. said:
I don't see any companion core for now:
ls /sys/devices/system/cpu
cpu0
cpu1
cpu2
cpu3
cpu_on (output on ls = 2)
cpu_on_mdelay (output on ls = 0)
cpufreq
cpuidle
kernel_max
offline (output on ls = 1-3)
online (output on ls = 0-3)
possible (output on ls = 0-3)
present (output on ls = 0-3)
Click to expand...
Click to collapse
Thats weird :s
Cpu0 to cpu3 = main cpu cores
Any sign of a cpu1p? (Cpu1p = companion core)
shaky156 said:
Thats weird :s
Cpu0 to cpu3 = main cpu cores
Any sign of a cpu1p? (Cpu1p = companion core)
Click to expand...
Click to collapse
I haven't found such yet. I know for sure that cpu0 is online all the time.
mike1986. said:
I haven't found such yet. I know for sure that cpu0 is online all the time.
Click to expand...
Click to collapse
EDIT: removed text, unsure if its true or false
shaky156 said:
Yup just found out that companion core is cpu0 (explains why cpu0 is on all the time)
There is only 4 physical cores
Wow thought they had 5 physical cores, guess not lol
EDIT: ill double check to confirm
EDIT: yup thats what it looks like
The saving power core is cpu0, it enters LP2 state when saving power
Click to expand...
Click to collapse
No that is wrong. There is a fith PHYSICAL core but it's invisble to the system. Android only sees the four main cores.
The fith companion core is NOT, i repeat NOT, controlled by android. The tegra architecture itself handels to load balacing between the main cores and the companion core.
YOu won't find any traces of this companion core in the system.
Diamondback said:
No that is wrong. There is a fith PHYSICAL core but it's invisble to the system. Android only sees the four main cores.
The fith companion core is NOT, i repeat NOT, controlled by android. The tegra architecture itself handels to load balacing between the main cores and the companion core.
YOu won't find any traces of this companion core in the system.
Click to expand...
Click to collapse
Thanks for clearing that up, I was thinking its hidden but then looking @ kernel code, when idle cpu0 enters LP2 state :s + cpu0 is online all the time
shaky156 said:
Thanks for clearing that up, I was thinking its hidden but then looking @ kernel code, when idle cpu enter LP2 state :s
Click to expand...
Click to collapse
Some time ago there was an official article from Nvidia about this topic, stating all those things, maybe I'll search for that
Having only that one core online probably means that in the end most of the time only the companion core does the work, but we don't really know.
Tegra handels that stuff on its own (and it does a great job btw on my Prime. Standby times are incredible.)
Diamondback said:
Some time ago there was an official article from Nvidia about this topic, stating all those things, maybe I'll search for that
Having only that one core online probably means that in the end most of the time only the companion core does the work, but we don't really know.
Tegra handels that stuff on its own (and it does a great job btw on my Prime. Standby times are incredible.)
Click to expand...
Click to collapse
So there definitely is a fifth core?
shaky156 said:
So there definitely is a fifth core?
Click to expand...
Click to collapse
Yes.
Sent from my Samsung Galaxy Nexus
shaky156 said:
So there definitely is a fifth core?
Click to expand...
Click to collapse
Unless Nvidia is lying to us in their official press releases, yes. There are 5 cores in a tegra 3.
4 high power cores and one low power core.
I am not an expert on that but this nvidia video shows the CPU core stress and it's running android of course. And thus app (if it's one) can see the companion core?!
So it needs to be seen by android os right?
http://www.youtube.com/watch?v=R1qKdBX4-jc&feature=youtube_gdata_player
Maybe this video will help you a little bit if you didn't know it (what I don't think)...
Sent from my HTC HD2 using xda premium
Diamondback said:
Unless Nvidia is lying to us in their official press releases, yes. There are 5 cores in a tegra 3.
4 high power cores and one low power core.
Click to expand...
Click to collapse
Thanks, it was just a quick scan through kernel, ill have a more indepth look at it tommorow, its very interesting.
@youtube video: notice how the companion core turns off before main core go online?, why cant the companion core be turned on with main cpu cores? (Maybe it can be tested when device released).
Im very interested in this, well i could be very wrong, there may well be a fifth physical core, but dunno got a weird feeling about this
EDIT: I dont think it matters of its 4 or 5 cores though, cause its still powerfull!, but it makes more sense/ save money if its done with 4 cores
shaky156 said:
Thanks, it was just a quick scan through kernel, ill have a more indepth look at it tommorow, its very interesting.
@youtube video: notice how the companion core turns off before main core go online?, why cant the companion core be turned on with main cpu cores? (Maybe it can be tested when device released).
Im very interested in this, well i could be very wrong, there may well be a fifth physical core, but dunno got a weird feeling about this
Click to expand...
Click to collapse
Yes I was thinking exactly the same thing about that.
If it would run on its highest level + the main cores there shouldn't be a huge higher battery drain since it stays under the 500mhz but gives more power to the app/video/game etc... Who knows what nvidia wanted to prevent with this, we will see and possibly be able to change that which would make sense (at least to me).
Sent from my HTC HD2 using xda premium
shaky you can see clearly five cores in the photo of the chipset, unless Nvidia is lying to the whole planet and the fifth core is just a disabled extra core to insure better yields lol
ofcourse the tradermarked 4-plus-1 term and the possibility of a massive lawsuit makes this highly unlikely
lookout the tegra3 slides and anandtech article, it says the load balancing is hardware locked and invisible to the system, although I don't really get it since they can still use the fifth core along the main four for Directtouch
hamdir said:
shaky you can see clearly five cores in the photo of the chipset, unless Nvidia is lying to the whole planet and the fifth core is just a disabled extra core to insure better yields lol
ofcourse the tradermarked 4-plus-1 term and the possibility of a massive lawsuit makes this highly unlikely
lookout the tegra3 slides and anandtech article, it says the load balancing is hardware locked and invisible to the system, although I don't really get it since they can still use the fifth core along the main four for Directtouch
Click to expand...
Click to collapse
Agree, just weird why they would keep cpu0 online
EDIT: has anyone tested with current tegra 3 devices? E.g. transformer prime?
EDIT: tweeted htcdev, waiting for reply lol
EDIT: ill have a look @ kernel today, i can confirm that cpu0 is always online, and only 3cpus go offline and cpu 0 enter what nvidea call a LP2 state
Sent from my Desire HD
If someone is really interested in this, here is an official whitepaper from Nvidia about the tegra 3.
http://www.nvidia.com/content/PDF/t...ecture-for-Low-Power-and-High-Performance.pdf
I might be wrong with the "invisible to the system" thing, they are not 100% clear in the paper about that.
But in fact the fifth core is not visible the "normal" android way. CPU apps only see the four main cores.
Sorry I'm not a developer so hopefully this doesn't sound too stupid... but this is how I would think it could be...CPU0 in the Kernel is just an address to the physical core and what is happening on the hardware level is that the address is being switched between the physical first core and the physical fifth core.
Possible?
Here is the thing.
I have bought an refurbished HTC one M8 online and after using it for a while i did the android updates. It had android 4.4 then it installed 5.0.1 and then it updated to 6.0, after a couple of days the back camera started to crush when opened. I did a little research and as a presumed problem was the android update i did. So i tryed to install the European Ruu from the htc site but without success. Can anyone help me further.
The mob cid: 11111111
Please let me know what details to provide if needed.
Thanks
So i flashed the ruu of unlock/developer also that of AT&T but all the same, no success with the camera. I don't know what to do anymore, please someone help.
ALBI SHTYLLA said:
Here is the thing.
I have bought an refurbished HTC one M8 online and after using it for a while i did the android updates. It had android 4.4 then it installed 5.0.1 and then it updated to 6.0, after a couple of days the back camera started to crush when opened. I did a little research and as a presumed problem was the android update i did. So i tryed to install the European Ruu from the htc site but without success. Can anyone help me further.
The mob cid: 11111111
Please let me know what details to provide if needed.
Thanks
Click to expand...
Click to collapse
Post the results of fastboot getvar all minus your IMEI and serial#, and I or someone else here will be able to direct you to the right RUU/firmware
xunholyx said:
Post the results of fastboot getvar all minus your IMEI and serial#, and I or someone else here will be able to direct you to the right RUU/firmware
Click to expand...
Click to collapse
I flashed the ruu of unlock/developer also that of AT&T but all the same, no success with the camera. I don't know what to do anymore, please someone help.
ALBI SHTYLLA said:
I flashed the ruu of unlock/developer also that of AT&T but all the same, no success with the camera. I don't know what to do anymore, please someone help.
Click to expand...
Click to collapse
If you aren't going to do what I asked of you, then I can't help you.
xunholyx said:
Post the results of fastboot getvar all minus your IMEI and serial#, and I or someone else here will be able to direct you to the right RUU/firmware
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can you help me wih this picture ?
i'll wait for my friend to give me the phone then i'll do "fastboot getvar all"
thanks advancely
idir543 said:
can you help me wih this picture ?
i'll wait for my friend to give me the phone then i'll do "fastboot getvar all"
thanks advancely
Click to expand...
Click to collapse
You have a Verizon device, and can only use Verizon firmware. US Unlocked and AT&T firmware won't work.
You can get the RUU.zip that you need from here.
That's LRA device .. flashing Verizon firmware is not recommended.
xunholyx said:
You have a Verizon device, and can only use Verizon firmware. US Unlocked and AT&T firmware won't work.
[/URL].
Click to expand...
Click to collapse
Thanks , is there a tutorial? Do i have to unlock bootloader or no? Do i need s-off or s-on ? Thanks
---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------
ckpv5 said:
That's LRA device .. flashing Verizon firmware is not recommended.
Click to expand...
Click to collapse
Hum , i didn't understand, why?
idir543 said:
Hum , i didn't understand, why?
Click to expand...
Click to collapse
Because the radio config data (rcdata) on Verizon meant for Verizon network but
LRA rcdata is for non-Verizon network
When you install Verizon firmware which has Verizon rcdata, your data most probably won't work.
Read this : http://forum.xda-developers.com/htc-one-m8/help/help-friends-t3402398
Does this help?
xunholyx said:
If you aren't going to do what I asked of you, then I can't help you.
Click to expand...
Click to collapse
This is the at&t ru installed provided from the htc support website
My results
xunholyx said:
If you aren't going to do what I asked of you, then I can't help you.
Click to expand...
Click to collapse
Does this help?
ALBI SHTYLLA said:
Does this help?
Click to expand...
Click to collapse
Like I said before, post the results of fastboot getvar all
The app you are using is just reading from the build.prop and doesn't tell the information needed to find a proper RUU for you.
ALBI SHTYLLA said:
So i tryed to install the European Ruu from the htc site but without success.
Click to expand...
Click to collapse
They don't post the Euro RUUs on the HTC website. You flashed something else. Try providing the exact file name, instead of vague, incorrect statements like "European RUU" (which even if true - which its not - wouldn't tell us what version number Euro RUU).
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
ALBI SHTYLLA said:
Does this help?
Click to expand...
Click to collapse
It really does not.
It only provides a portion of the info, and those apps often report incorrect info.
Do fastboot getvar all, as asked previously. If you can't manage doing that, you shouldn't be messing with the phone.
The results.
xunholyx said:
Post the results of fastboot getvar all minus your IMEI and serial#, and I or someone else here will be able to direct you to the right RUU/firmware
Click to expand...
Click to collapse
As you asked. Thanks.
What firmware should I flash? i am getting different software version information in bootloader and in settings> software info, page. What to do
here is the data from bootloader and screenshot from the cell.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:[COLOR="Red"] 4.28.502.1[/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <removed>
(bootloader) imei: <removed>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6768a7b1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
chshahid2k said:
What firmware should I flash? i am getting different software version information in bootloader and in settings> software info, page. What to do
here is the data from bootloader and screenshot from the cell.
(bootloader) version-main: 4.28.502.1
(bootloader) product: m8_ul
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
What RUU to flash, indeed. You have a mess going on there.
Don't go by the screenshot, which shows Software version in Settings. It just corresponds to the currently installed ROM, which may be a Euro based (4.16.401.10)custom ROM; and really has no bearing on what RUU to run.
The getvar data is what you need to go by, but you have some conflicting info:
Model ID (MID) 0P6B13000 is for T-Mobile US. Product m8_ul would also correspond to T-Mob US (although other versions also are m8_ul, including Euro version). However, the main version 4.28.502.1 seems to indicate that someone flashed AT&T firmware to the device. CID 1111111 is SuperCID, which would also indicate the device was modified (as does the s-off indicator).
Since the phone is s-off, you have some options. Your best bet in your case is probably to change the MID, then flash the corresponding RUU. An unbranded variant's MID and RUU (such as Euro or Asia) is probably preferred, given your location. But what version exactly would somewhat depend on what band support you need for 3G and LTE for your carrier.
The results
redpoint73 said:
They don't post the Euro RUUs on the HTC website. You flashed something else. Try providing the exact file name, instead of vague, incorrect statements like "European RUU" (which even if true - which its not - wouldn't tell us what version number Euro RUU).
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
It really does not.
It only provides a portion of the info, and those apps often report incorrect info.
Do fastboot getvar all, as asked previously. If you can't manage doing that, you shouldn't be messing with the phone.
Click to expand...
Click to collapse
Please help me....
ALBI SHTYLLA said:
Please help me....
Click to expand...
Click to collapse
Your getvar seems to indicate the phone was originally AT&T version based on product name m8_ul_ca and firmware version 6.20.502.5; but at some point someone tried to convert it to another version (s-off, superCID and Euro model ID). Either that conversion was not completed properly (otherwise it would not have ATT firmware number 6.20.502.5) or it was converted, but had ATT firmware flashed again later.
I assume you would prefer to use Euro RUU, as AT&T RUU is not preferred by most folks, unless you are in the US and an actual AT&T customer (even then, I'm on ATT, and I can't stand the ATT stock ROM).
If that is the case, you can try the Euro RUU here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
This is a zip format RUU (not an exe) so follow the instructions in the post.
One thing I'm not sure of, is if the ATT firmware will interfere with the installation of this Euro RUU. If it doesn't install, we may need to do some additional steps, such as flash Euro RUU firmware.zip, then Euro RUU.
redpoint73 said:
What RUU to flash, indeed. You have a mess going on there.
Don't go by the screenshot, which shows Software version in Settings. It just corresponds to the currently installed ROM, which may be a Euro based (4.16.401.10)custom ROM; and really has no bearing on what RUU to run.
The getvar data is what you need to go by, but you have some conflicting info:
Model ID (MID) 0P6B13000 is for T-Mobile US. Product m8_ul would also correspond to T-Mob US (although other versions also are m8_ul, including Euro version). However, the main version 4.28.502.1 seems to indicate that someone flashed AT&T firmware to the device. CID 1111111 is SuperCID, which would also indicate the device was modified (as does the s-off indicator).
Since the phone is s-off, you have some options. Your best bet in your case is probably to change the MID, then flash the corresponding RUU. An unbranded variant's MID and RUU (such as Euro or Asia) is probably preferred, given your location. But what version exactly would somewhat depend on what band support you need for 3G and LTE for your carrier.
Click to expand...
Click to collapse
Thanks for the reply. Well I am from Pakistan, Middle East Region.
My OTA update thingy countinuously giving me notification about Update 4.16.401.13 is available (57.xx MB) but when its fully downloaded it gives me an error of "Variant Software Detected" and it doesnt install. I have once changed its MID to 0P6B10000 but it didnt work. Well I am getting more info in "Simple CID Getter" App. Some of the Info is attached.
Code:
[DEVICE_PROVISIONED]: [1]
[gsm.version.baseband]: [[email protected]_40.45.C33065.00_F]
[ro.aa.customizationid]: [980227]
[ro.aa.maincid]: [HTC__001]
[ro.aa.mainsku]: [401]
[ro.aa.modelid]:[COLOR="Red"] [0P6B10000][/COLOR]
[ro.aa.project]: [[COLOR="red"]M8_UL_L50_SENSE60_MR][/COLOR]
[ro.aa.romver]: [4.16.401.10]
[ro.aa.skulist]: [401]
[ro.aa.taskid]: [417003]
[ro.baseband]: [[email protected]]
[ro.bc_tmo]: [300]
[ro.board.platform]: [msm8974]
[ro.boot.baseband]: [[email protected]]
[ro.boot.batt_poweron]: [good_battery]
[ro.boot.bootloader]: [3.19.0.0000]
[ro.boot.carrier]: [ALL]
[ro.boot.ddrmid]: [(0x3)]
[ro.bootloader]: [3.19.0.0000]
[ro.build.buildline]:[COLOR="red"] [M8UL_HTC_WWE_L50_CRC_Sense60_Stable_MR][/COLOR]
[ro.build.changelist]: [448934]
[ro.build.characteristics]: [default]
[ro.build.date.utc]: [1421333072]
[ro.build.date]: [四 1月 15 22:44:32 CST 2015]
[ro.build.description]: [4.16.401.10 CL448934 release-keys]
[ro.build.display.id]: [LRX22C release-keys]
[ro.build.fingerprint]: [htc/htc_europe/htc_m8:5.0.1/LRX22C/448934.10:user/release-keys]
[ro.build.host]: [ABM101]
[ro.build.id]: [LRX22C]
[ro.build.languageremove]: []
[ro.build.product]: [htc_m8]
[ro.build.project]: [M8_UL_L50_SENSE60_MR:417003]
[ro.build.sense.version]: [6.0]
[ro.build.sku]: [HTC Europe]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [buildteam]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.htcsdk]: [HTCExt:HTCExtension_Sense60_L_2;SDK:6.55;hdkbase:19.2]
[ro.build.version.incremental]: [448934.10]
[ro.build.version.release]: [5.0.1]
[ro.build.version.sdk]: [21]
[ro.carrier]: [unknown]
[ro.chipset.model]: [MSM8974]
[ro.chipset.vendor]: [QCT]
[ro.chipset.version]: [1.x]
[ro.chk_prd]: [1]
[ro.cid]: [T-MOB010]
[ro.com.android.dataroaming]: [false]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.com.google.clientidbase]: [android-htc-rev]
[ro.com.google.gmsversion]: [5.0_r1]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.htc.enableCOTA]: [1]
[ro.customer.HTC__J15]: [PROJECT_G0005_flag, 0x0034]
[ro.customer.HTC__K18]: [PROJECT_G0005_flag, 0x0034]
[ro.customer.default]: [PROJECT_G0005_flag, 0x0034]
[ro.cwkey]: [CWS__001]
[ro.language.HTC__J15]: [LANGUAGE_ARA_flag, 0x0019]
[ro.language.HTC__K18]: [LANGUAGE_ISR_flag, 0x0038]
[ro.language.default]: [LANGUAGE_WWE_flag, 0x0000]
[ro.lb]: [1]
[ro.mid]: [COLOR="red"][0P6B13000][/COLOR]
[ro.product.manufacturer]: [HTC]
[ro.product.model]: [HTC One_M8]
[ro.product.name]: [htc_europe]
[ro.product.ram]: [2GB]
[ro.product.version]: [4.16.401.10]
[ro.ril.vmail.22201]: [41901,I TIM]
[ro.ril.vmail.22210]: [42020,Vodafone IT]
[ro.ril.vmail.22288]: [4200,I WIND]
[ro.ril.vmail.22299]: [4133,3ITA]
[ro.ril.vmail.23410]: [901,O2 UK,905,TESCO,443,giffgaff]
[ro.ril.vmail.23415]: [1571,BT,121,VDF UK]
As i highlighed i can see different MID in it.
Tell me what to do? Can i have MarshMallow Official ROM (if any) directly flashed over the current version using stock recovery or adb.
Can i flash this OTA Update on it? All In One - [OTA] Firmware 4.16.401.13 + NoRedText HBOOT + TWRP 2.8.7.0 Recovery
Thanks and Regards
Shahid
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HTC 10 OREO
~ Firmware Downloads ~
HOW TO FLASH FIRMWARE
(Thanks to @Sneakyghost)
__________
I had previously provided a few firmware zips for Oreo in the older firmware thread.
Some users have/had a difficult time reading and finding the newer links I had posted.
So I am providing Oreo firmware here in a centralized Oreo focused thread, as my free time and resources allow.
This is in hopes of making the latest Oreo firmware easier to find for HTC 10 Users, as the thread linked above, only covers up to Nougat.
THIS THREAD IS A WIP AND WILL FILL IN MORE AS MORE TIME PASSES!
Bear with me please...and enjoy! :good:
XDA:DevDB Information
HTC 10 OREO FIRMWARE, Tool/Utility for the HTC 10
Contributors
santod040
Version Information
Status: Stable
Current Stable Version: Oreo
Created 2018-02-27
Last Updated 2018-03-03
ASIA/AUS:
modelid: 2PS620000
cidnum: HTC__039
cidnum: OPTUS001
cidnum: VODAP021
cidnum: TELNZ001
NOTES:
I have provided 2 different zips for the Oreo Asia/AUS 3.20.710.2 firmware
Please pay attention to the details and choose the proper package for your situation.
3.20.710.2_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.20.710.2_NoBootImg_Twrp3.2.1-4_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-4 and WILL NOT WIPE
ASIA/HK:
modelid: 2PS620000
cidnum: HTC__622
NOTES:
I have provided 2 different zips for the Oreo Asia/HK 3.16.708.3 firmware
Please pay attention to the details and choose the proper package for your situation.
3.16.708.3_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.16.708.3_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-2 and WILL NOT WIPE
ASIA/TW:
modelid: 2PS620000
cidnum: HTC__621
3.16.709.8
NOTES:
I have provided 2 different zips for the Oreo Asia/TW 3.16.709.8 firmware
Please pay attention to the details and choose the proper package for your situation.
3.16.709.3-3.16.709.8_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 3.16.709.3 and will replace Twrp with stock recovery
Full_3.16.709.8_NoBootImg_Twrp3.2.1-4_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-4 and WILL NOT WIPE
3.16.709.3
NOTES:
I have provided 2 different zips for the Oreo Asia/TW 3.16.709.3 firmware
Please pay attention to the details and choose the proper package for your situation.
3.16.709.3_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.16.709.3_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-2 and WILL NOT WIPE
H3G:
modelid: 2PS620000
cidnum: H3G__001
cidnum: H3G__106
cidnum: H3G__003
cidnum: H3G__G04
NOTES:
I have provided 2 different zips for the Oreo H3G 3.18.771.1 firmware
Please pay attention to the details and choose the proper package for your situation.
3.18.771.1_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.18.771.1_NoBootImg_Twrp3.2.1-4_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-4 and WILL NOT WIPE
India_SEA:
modelid: 2PS620000
cidnum: HTC__060
NOTES:
I have provided 3 different zips for the Oreo India_Sea 3.18.400.2 firmware
Please pay attention to the details and choose the proper package for your situation.
2.41.400.51--3.18.400.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.41.400.51 and will replace Twrp with stock recovery
2.41.400.51--3.18.400.2_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to incrementally update firmware from 2.41.400.51 and will update Twrp to 3.2.1-2
Full_3.18.400.2_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to jump from any previous firmware to the current 3.18.400.2 firmware and will update Twrp to 3.2.1-2
Orange/EU:
modelid: 2PS620000
cidnum: ORANG219
NOTES:
I have provided 2 different zips for the Oreo Orange/EU 3.18.89.1 firmware
Please pay attention to the details and choose the proper package for your situation.
3.18.89.1_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.18.89.1_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-2 and WILL NOT WIPE
Sprint:
modelid: 2PS640000
cidnum: SPCS_001
NOTES:
@OMJ has provided 3 different zips for the Oreo Sprint 3.18.651.3 firmware
Please pay attention to the details and choose the proper package for your situation.
Sprint Oreo Firmware Zips
Telstra/WWE:
modelid: 2PS620000
cidnum: TELST001
NOTES:
I have provided 3 different zips for the Oreo Telstra WWE 3.18.841.1 firmware
Please pay attention to the details and choose the proper package for your situation.
2.48.841.31--3.18.841.1_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.48.841.31 and will replace Twrp with stock recovery
3.18.841.1_FULL_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and SHOULD NOT WIPE
3.18.841.1_NoBootImg_Twrp3.2.1-4_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-4 and WILL NOT WIPE
T-Mobile/DE:
modelid: 2PS620000
cidnum: T-MOB101
NOTES:
I have provided 2 different zips for the Oreo T-Mobile/DE 3.18.111.2 firmware
Please pay attention to the details and choose the proper package for your situation.
3.18.111.2_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.18.111.2_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-2 and WILL NOT WIPE
T-Mobile/PL:
modelid: 2PS620000
cidnum: T-MOB009
NOTES:
I have provided 2 different zips for the Oreo T-Mobile/PL 3.18.118.1 firmware
Please pay attention to the details and choose the proper package for your situation.
3.18.118.1_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.18.118.1_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-2 and WILL NOT WIPE
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
NOTES:
I have provided 3 different zips for the Oreo US Unlocked 3.16.617.2_r3 firmware
Please pay attention to the details and choose the proper package for your situation.
2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
3.16.617.2_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.16.617.2_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-2 and WILL NOT WIPE
Verizon:
modelid: 2PS650000
cidnum: VZW__001
NOTES:
I have provided 5 different zips for the Oreo Verizon 3.18.605.13 firmware
Please pay attention to the details and choose the proper package for your situation.
3.18.605.13 Combined Firmware with stock boot.img and stock recovery removed(will NOT wipe)
(Recommended firmware zip ^^^ for most users)
(for users coming from any previous firmware)
3.18.605.13 Combined Firmware with stock boot.img removed and Twrp3.2.1-4 included(will NOT wipe)
(for users coming from any previous firmware)
2.41.605.36-to-3.18.605.13 Full-Incremental Signed Stock Firmware with stock boot.img and stock recovery included(will replace/remove Twrp/may wipe/encrypt)
(for users coming from previous 2.41.605.36 Nougat firmware)
3.18.605.13 Stock Boot.Img
3.18.605.13 Stock Recovery
Vodafone/CH-DE:
modelid: 2PS620000
cidnum: VODAP110
NOTES:
I have provided 2 different zips for the Oreo Vodafone/CH-DE 3.18.166.2 firmware
Please pay attention to the details and choose the proper package for your situation.
3.18.166.2_FULL-WIPE_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will replace Twrp with stock recovery and WILL WIPE
3.18.166.2_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to update from any previous firmware and will update Twrp to 3.2.1-2 and WILL NOT WIPE
WWE:
modelid: 2PS620000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__M27
cidnum: HTC__034
cidnum: HTC__002
cidnum: HTC__016
NOTES:
I have provided 3 different zips for the Oreo WWE 3.16.401.2 firmware
Please pay attention to the details and choose the proper package for your situation.
2.41.401.41--3.16.401.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.41.401.41 and will replace Twrp with stock recovery
2.41.401.41--3.16.401.2_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to incrementally update firmware from 2.41.401.41 and will update Twrp to 3.2.1-2
Full_3.16.401.2_NoBootImg_Twrp3.2.1-2_firmware.zip - Can be used on S-Off devices to jump from any previous firmware to the current 3.16.401.2 firmware and will update Twrp to 3.2.1-2
CID LIST
This is only a partial list of CIDs for reference.
It should only be used as such and not as a 100% complete list.
(I may or may not add more in time, although it's not the priority here)
ASuperCID 11111111
Asia-HK-CHT HTC__622
ATT CWS__001
BM BM___001
Bouygues-Telecom BOUYG201
Brightstar-PTB BSTAR502
Brightstar-SPA BSTAR301
Chunghwa-Taiwan CHT__601
CA_Dave DAVE_001
CA_Videotron VIDEO001
CT HTCCN702
CU HTCCN703
DCM DOCOM801
DOPOD DOPOD701
Era T-MOB009
Entel BSTAR306
Tigo BSTAR307
Movistar BSTAR308
Fastweb-IT FASTW401
GOOGLE GOOGL001
H3G-AT H3G__106
H3G-DAN H3G__F05
H3G-Italy H3G__402
H3G-ROI H3G__003
H3G-SWE H3G__G04
H3G-UK H3G__001
HTC-Asia-SEA HTC__037
HTC-Asia-SEA-WWE HTC__044
HTC-Australia HTC__023
HTC-BE HTC__E41
HTC-Czech HTC__C24
HTC-Denmark HTC__F08
HTC-Dutch HTC__E11
HTC-EastEurope HTC__032
HTC-ELL HTC__N34
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-FRA-NRJ HTC__249
HTC-GCC HTC__J15
HTC-GER HTC__102
HTC-India HTC__038
HTC Israel HTC__K18
HTC-ITA HTC__405
HTC-Nor HTC__Y13
HTC-Norway HTC__H10
HTC-Poland HTC__B25
HTC-PTG HTC__506
HTC-Russia HTC__A07
HTC-SPA HTC__304
HTC-Sweden HTC__G09
HTC-Tesco HTC__052
HTC-Turkey HTC__M27
HTC-WWE HTC__001
Hutch-Australia HUTCH001
O2-DE O2___102
O2-UK O2___001
Open-Channel HTCCN701
Optus-Australia OPTUS001
ORANGE-AT ORANG113
ORANGE-BE ORANG012
ORANGE-CH-FRA ORANG203
ORANGE-CH-GER ORANG104
ORANGE-ES ORANG309
ORANGE-French ORANG202
ORANGE-PL ORANGB10
ORANGE-PO ORANG008
ORANGE-SK ORANG006
ORANGE-UK ORANG001
Rogers ROGER001
SKT_KR SKT__901
SMC-Voda-HK SMCVD001
SPRINT SPCS_001
TELEF-Spain TELEF301
Telstra TELST001
TELUS TELUS001
TIM-Italy TIM__401
TMA T-MOB102
TMCZ T-MOB004
TMD T-MOB101
TMH T-MOB007
TMHR T-MOB006
TMMK T-MOBL11
TMNL T-MOB003
TMSK T-MOB008
TMUK T-MOB005
TMUS T-MOB010
TWM-TW HTC__621
VERIZON VZW__001
VIRGIN-UK VIRGI001
VODA-Africa-South HTC__016
VODA-Australia VODAP021
VODA-Germany VODAP102
VODA-Greece VODAP006
VODA-Ireland VODAP019
VODA-Italy VODAP405
VODA-Mobilkom VODAP120
VODA-Netherland VODAPE17
VODA-New-Zealand VODAP022
VODA-Portugal VODAPD18
VODA-Proximus VODAP024
VODA-SA VODAP026
VODA-SFR VODAP203
VODA-Spain VODAP304
VODA-Swisscom-DE VODAP110
VODA-Swisscom-FR VODAP212
VODA-Swisscom-IT VODAP416
VODA-Swisscom-WWE VODAP015
VODA-TR VODAPM27
VODA-UK VODAP001
This one too...
Downgrading
Want To Return/Downgrade To Nougat From Oreo?
This is not the thread for discussing that.
PLEASE GO HERE: Downgrade Thread
Safe to update while using magisk? Should I restore stock boot before the update?
FluffyDiscord said:
Safe to update while using magisk? Should I restore stock boot before the update?
Click to expand...
Click to collapse
These are not RUUs, these are not OTAs, these are firmware only.
To be used in combination with a stock Oreo based rom.
If you're not sure what this means or what these are for, then you probably shouldn't download these.
Hi Santod040,
I have a few question, my phone is S-ON with 2.41.401.41 firmware. My CID is HTC_034 (Europe), I don't see it in your CID list, is it safe to flash your firmware?
Also do you know if Nougat rom works with Oreo firmware? It would be great if I can check my phone can still boot after flashing firmware and before installing any other rom x)
@santod040 i think you'd better add also the last nougat fw for the folks who will surely be asking how to get back to 7.0
from what i read these last days, there is now a solution for going back with deleting a partition.
if not, this thread will be spammed with those questions as is @LeeDroid 's
cobrax2 said:
@santod040 i think you'd better add also the last nougat fw for the folks who will surely be asking how to get back to 7.0
from what i read these last days, there is now a solution for going back with deleting a partition.
if not, this thread will be spammed with those questions as is @LeeDroid 's
Click to expand...
Click to collapse
Return to Nougat link will be added, that's all.
Was already planned, which is why I said it's a WIP (work in progress).
This thread won't be spammed with folks telling me what to post, asking redundant questions, or with folks downgrading.
That's not what this is for. I will simply lock the thread and only open it to add files, if that begins.
I almost locked it before going to bed last night, to avoid the nonsense, looks like I probably should have....
damn, you are jumpy...
i was trying to be helpful to you, save you the trouble. sorry for that
cobrax2 said:
damn, you are jumpy...
i was trying to be helpful to you, save you the trouble. sorry for that
Click to expand...
Click to collapse
Jumpy...?
Thanks, that was enough for me, thread closed until I add more resources.
Which is what I was doing when you posted this.
Sorry, but telling me to add the Nougat firmware here, I did not find helpful.
They are all already posted in the thread I linked initially in the OP.
This thread is for Oreo firmware, period. That's all.
(I have no problem saving myself trouble and if that was my main goal, I would just not post here at all)
T-Mobile/DE:
modelid: 2PS620000
cidnum: T-MOB101
mainver: 3.18.111.2
Firmware added to Second Post.
ASIA/TW:
modelid: 2PS620000
cidnum: HTC__621
mainversion: 3.16.709.3
Firmware added to second post.
Orange/EU:
modelid: 2PS620000
cidnum: ORANG219
mainver: 3.18.89.1
Firmware added to Second Post.
T-Mobile/PL:
modelid: 2PS620000
cidnum: T-MOB009
mainver: 3.18.118.1
Firmware added to Second Post.
ASIA/HK:
modelid: 2PS620000
cidnum: HTC__622
mainver: 3.16.708.3
Firmware added to Second Post.
India_SEA:
modelid: 2PS620000
cidnum: HTC__060
mainver: 3.18.400.2
Firmware added to Second Post.
Sprint:
modelid: 2PS640000
cidnum: SPCS_001
mainver: 3.18.651.3
Firmware(links) added to Second Post.
Telstra/WWE:
modelid: 2PS620000
cidnum: TELST001
mainver: 3.18.841.1
Firmware added to Second Post.
Recently I've been googling on how to unlock my jiofi jmr540 device and found nothing.
But I discovered something else. I don't think we need a custom rom to unlock the device. I'm not a expert in these stuff.
Every jiofi device has web UI.
I discovered that every jiofi device have a hidden web UI that is engineer mode.
I didn't find any rom for my device but I found for jmr520 which was in bin format. I opened it using notepad in my pc and discovered that engineer mode does exist in its coding. There is lots of options present in engineer mode like manually selecting network band, choosing between 2g, 3g, and 4g, manual network search, and I also saw some network unlock coding which I couldn't understand by entering unlock code.
Can anyone help to access engineer mode in my device. I think it is also a html just like jiofi.local.html.
It would be really great if someone helped as many jiofi users are still wanting to unlock the device.
My device details are,
Firmware Version: FXN_JMR540_R6.11
Hardware Version: FXN_JMR540_V055
Device manufacturer : Foxconn
Interesting. Did you have any success?
mGforCe said:
Interesting. Did you have any success?
Click to expand...
Click to collapse
Nope. I gave up. Jiofi is not like other devices. Other devices can be configured using data cables from any computers with the device configuration software. But jiofi can be configured only using Web UI. That is the MAJOR problem.
How to enter in engineer mode in jiofi jrm520
How to enter in engineer mode in jiofi jrm520
None of the blue whales in this ocean can fix it?
Found Some interesting Facts on JIOFI3 ( JMR540 )
I managed to make the device into FASTBOOT.
using ANDROID BOOTLOADER INTERFACE.
Able to ping the hardware and get the following:
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:V055
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x8000000
(bootloader) serialno:8*32***4
(bootloader) kernel:lk
(bootloader) product:JioFi3
Click to expand...
Click to collapse
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel: OKAY
Any firmware available till now , mdm9607 firmware can be flashed via adb.... if anyone has firmware kindly share :
unlocked devices are sold at alibaba JMR541, both are same chipset
https://www.alibaba.com/product-det...?spm=a2700.details.deiletai6.2.2ea36c5acxqHqD
tr
Jio-fi-3 JMR_541
how did you did that @ Electroboy_Prakash
Electroboy_Prakash said:
Found Some interesting Facts on JIOFI3 ( JMR540 )
I managed to make the device into FASTBOOT.
using ANDROID BOOTLOADER INTERFACE.
Able to ping the hardware and get the following:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel: OKAY
Click to expand...
Click to collapse
How did you get fastboot menu? Can you extract firmware and send it.
Here is another jio fi 2. You can log in to Jio fi. Use 192.168. Username Administrator Password is written on Jio Fi box.
ODMPegasusProduct IDM2
IMEI 911522-----------
Firmware VersionPEG_M2_B38.2Firmware Creation Date2019-11-29
Frequency Bands Supported B3,B5,B 40
I've managed it to unlock this device. Enabled diagnostic mode and adb. Custom firmwares are possible in this devices. Once modified firmware can be flashed via fastboot mode which is easily accessible without any modification.
Check my Twitter thread here https://twitter.com/ab_hi_j/status/1395394412545515521
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you help me with the procedure i also want to unlock my jiofi3
sksinha said:
Can you help me with the procedure i also want to unlock my jiofi3
Click to expand...
Click to collapse
Here is the unlocking guide
[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks
Unlocked Firmware for JioFi 3 JMR540 & JMR541 Disclaimer I am not responsible for any kind of damage to your device. Use this firmware at your own risk Post is for educational purpose only. ONLY FOR JMR 540 & JMR 541 I was able to dump and...
forum.xda-developers.com
Vismay G S said:
Recently I've been googling on how to unlock my jiofi jmr540 device and found nothing.
But I discovered something else. I don't think we need a custom rom to unlock the device. I'm not a expert in these stuff.
Every jiofi device has web UI.
I discovered that every jiofi device have a hidden web UI that is engineer mode.
I didn't find any rom for my device but I found for jmr520 which was in bin format. I opened it using notepad in my pc and discovered that engineer mode does exist in its coding. There is lots of options present in engineer mode like manually selecting network band, choosing between 2g, 3g, and 4g, manual network search, and I also saw some network unlock coding which I couldn't understand by entering unlock code.
Can anyone help to access engineer mode in my device. I think it is also a html just like jiofi.local.html.
It would be really great if someone helped as many jiofi users are still wanting to unlock the device.
My device details are,
Firmware Version: FXN_JMR540_R6.11
Hardware Version: FXN_JMR540_V055
Device manufacturer : Foxconn
Click to expand...
Click to collapse
need this. please take look
abhimortal6 said:
Here is the unlocking guide
[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks
Unlocked Firmware for JioFi 3 JMR540 & JMR541 Disclaimer I am not responsible for any kind of damage to your device. Use this firmware at your own risk Post is for educational purpose only. ONLY FOR JMR 540 & JMR 541 I was able to dump and...
forum.xda-developers.com
Click to expand...
Click to collapse
I have accidentally erased the recovery partition of JMR540 and my jiofi not starting always go in fastboot mode. Can you please provide boot.img file of JMR540 jiofi.
message removed
Jio pushed new firmware JMR540 and following changes are made.
-> locked boot loader
-> TTL RX disabled so we are not able to access root shell via UART.
only option to unlock modem is
-> boot modem to EDL( Emergency Download Mode) mode.
-> take backup and flash old recovery via QPST (qualcomm firehose prog file required for MDM9207)
@abhimortal6
sorry for chasing you again. Hope you know the exact procedure.
Can you share
1) EDL points for JMR 540 to short and boot to EDL mode.
2) Qualcomm firehose prog file for MDM9207
It's fine @jithinvp4, okay so there's no exact test points you can short. Trick is to stop power to EMMC for fraction of a second while booting. There's a single resistor 2nd one from bottom in left of EMMC. You can use RPi pico to build brute switch.
If done correctly while booting it'll fail and fall to un-secure download mode. Yes you read that right un-secure it's an old Qualcomm thing.
I had chat with one of Manager/People from JioFi device team after first exploit. I'm not sure they'll fix this too. It's doable I think. Not sure if they'll do this because not everyone can do this. So yeah private exploit is still there
@abhimortal6 Thanks for your response.
I was spending too much time for last few weeks to find a method to unlock JMR 540 . I thought there is a test-point . Don't have much knowledge to use RPi pico.
please let me know any other simple method available to boot EDL .
Otherwise i will be monitoring your tread for your next unlock solution.
LG G7 One OTA Collection
You can contribute by giving us the OTA link in my 3rd post below.
Join our Telegram Group: https://t.me/LGG7One
Disclaimer:
Anyone can try those zip files below but I am not responsible for bricking up your phone.
As anyone can see there are 3 Variants of the LG G7 One. Here are also the network bands associated with it:
LG G7 One LMQ910UM (North America/32gb ROM):
4G LTE: B1 (2100), B2 (1900), B3 (1800), B4 (1700/2100 AWS 1), B5 (850), B7 (2600), B8 (900), B12 (700), B13 (700), B17 (700), B20 (800), B28 (700), B38 (TDD 2600)
3G UMTS: B1 (2100), B2 (1900), B4 (1700/2100 AWS A-F), B5 (850), B8 (900)
2G GSM: B2 (1900), B3 (1800), B5 (850), B8 (900)
LG Q9 One LMQ927L (South Korea/64gb ROM):
4G LTE: B1 (2100), B3 (1800), B5 (850), B7 (2600), B8 (900), B40 (TDD 2300)
3G UMTS: B1 (2100), B2 (1900), B5 (850), B8 (900)
2G GSM: B2 (1900), B3 (1800), B5 (850), B8 (900)
LG X5 X5AO/X5LG10a (Japan/64gb ROM):
4G LTE: B1 (2100), B2 (1900), B3 (1800), B4 (1700/2100), B5 (850), B7 (2600), B8 (900), B13 (700), B17 (700), B20 (800), B38 (TDD 2600), B12 (700), B28 (700)
3G UMTS: B5 (850), B8 (900), B4 (1700/2100), B2 (1900), B1 (2100)
2G GSM: B2 (1900), B3 (1800), B5 (850), B8 (900)
Android 11:
March 2021 Q910UM40b - 0.93gb
https://android.googleapis.com/packages/ota-api/package/171d85833220a982ac9d346802218e23dc95f3a8.zip
Android 10:
October 2020 Q910UM30o - 1.3gb
https://ota.googlezip.net/packages/.../1686f52e42a64a373c725b94b499978430ba28e5.zip
Septermber 2020 Q910UM30n - 19.47mb
https://ota.googlezip.net/packages/.../428b7bcbe67185318cf181eedd8955b4064ce296.zip
August 2020 Q910UM30m - 1.3gb
https://ota.googlezip.net/packages/.../94d2961a87d475a9ce9df2bfa08b47cc7fa6ed8e.zip
July 2020 Q910UM30I - 1.3gb
https://ota.googlezip.net/packages/.../375afb56a92bb9f91fed75c4b178988e7e7b3da1.zip
June 2020 Q910UM30k - 1.3gb
https://ota.googlezip.net/packages/.../f3c3833263f02380b30333f23f4c49efff1a0bcf.zip
May 2020 Q910UM30j - 1.3gb
https://ota.googlezip.net/packages/.../71515d665e1404b6069065340eff9a188f0a63d3.zip
April 2020 Q910UM30h - 20.27mb
https://ota.googlezip.net/packages/.../afbb4dfd845f4084dd9db11ab356f4ec5534313c.zip
March 2020 Q910UM30g - 1239mb
https://ota.googlezip.net/packages/.../89819b8c83348ee0e50ca4cafd32b0f3607b9e74.zip
February 2020 Q910UM30f - 22.6mb
https://ota.googlezip.net/packages/.../d066c67f0fccb087b56c8f418e3ca19bde35be8b.zip
January 2020 Q910UM30e - 261.7mb
https://ota.googlezip.net/packages/.../c18253560371d976c2f174118a3efabd38f89136.zip
November 2019 Q910UM30d - 741.9mb
https://ota.googlezip.net/packages/.../e02103e7424387218de9f791156e0706df395e2d.zip
Android Pie 9.0:
Big Updates:
September 2018 Q910UM10c to July 2019 Q910UM20q - 895.9MB
https://ota.googlezip.net/packages/.../4eba92fd33c5a1813495e95b23df6ecfa09e42fe.zip
September 2018 Q910UM10c - January 2019 - 830.37MB
https://ota.googlezip.net/packages/.../47753268118349c259995dff14acff3533b735d4.zip
May 2019 Q910UM20p to July 2019Q910UM20r
https://ota.googlezip.net/packages/.../d2ac38a911adfe44c1bfd48396b76c51f7a7cdd3.zip
Android Oreo 8.0:
November 2019 Q910UM20v - 108.9mb
https://ota.googlezip.net/packages/.../9c17f783d607f7f1076c408f9cf8441392593947.zip
October 2019 Q910UM20u - 101.4mb
https://ota.googlezip.net/packages/.../72081565f0b021189b51d4887fc664b6cb15deb4.zip
September 2019 Q910UM20t - 124.7mb
https://ota.googlezip.net/packages/.../76beb350b47ec0969a5c33d1fe21ffe5abe58fbb.zip
August 2019 Q910UM20s - 113.7mb
https://ota.googlezip.net/packages/.../eed83632d9bddff888ae32192e17c5099cdbba03.zip
July 2019 Q910UM20r - 124.28mb
https://ota.googlezip.net/packages/.../5e10e289dc613d0a892af1b9408062fc2939ab55.zip
June 2019 Q910UM20q - 298.1mb
https://ota.googlezip.net/packages/.../0d098343b03ddfbb2567035c1717cf100fc1600e.zip
May 2019 Q910UM20p 230.6MB
No further information yet
April 2019 Q910UM20m - 121MB
No further information yet
March 2019 Q910UM20k - 338MB
No further information yet
January 2019
No further information yet
December 2018 - 260.4MB
https://ota.googlezip.net/packages/.../0b213263ed3f52acd479c436c7f43e2c847932f3.zip
November 2018 Q910UM20d - 812.2MB
No further information yet
Where to check for the next updates on your LG G7 One device:
Fido Update Page
Rogers Update Page
FYI: If someone uses my captured OTA link, at least a small gratitude by giving a credit (Attention/CTTO) would be much appreciated. Thanks!
Tutorial
How to apply OTA
Via Phone
The package "com.evenwell.OTAUpdate" has been deleted since November 2018 Update, this means, the *#*#874#*#* method, is no longer available
Prerequisites
Your charged phone
No PC & SD Card needed
Directions
1. Download the OTA zip file from this page first.
2. Go to download folder and rename the package to the corresponding zip name.
Example: B2N-322C-0-00WW-B01-update.zip
3. Place it to root directory of internal storage.
4. Open Phone App and dial *#*#874#*#* to update.
5. Wait for the update to finish and restart when prompted.
Via Recovery
Prerequisites
To update a device using a downloaded image, you will need the latest adb tool on your computer. You can get this from the Android SDK Platform-Tools package, which can be downloaded from here.
1. Ensure to modify the environment variable which includes the PATH where the adb executable can be found.
2. Ensure you've set up USB access for your device, as described in Run Apps on a Hardware Device (may have to remove hyperlink).
Download the build and flash your device
1. Ensure your device is up to date by going to Settings > About phone > System updates
2. Download the required image from the download button below.
3. With your device powered on and USB debugging enabled, execute: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can alternatively use the following procedure:
A. Power off device, and insert USB to enter power off charge mode.
B. Press the Power key and Volume Up keys together for about 10 seconds.
C. Release both keys when the device vibrates.
D. After the Android screen, you should now be in Recovery Mode, indicated by the Android Warning logo and "No command".
E. Select the Recovery option from the bootloader menu and you should now be in "Recovery Mode" (confirmed by Android logo & red exclamation mark).
4. Hold the Power button and press Volume Up once, and a menu will appear:
Option 1: Via SD Card
Select the option “Apply update from SD Card” from the recovery options. Navigate to the OTA update zip and select it. Confirm installation.
Option 2: Via ADB
A. Select the option "Apply update from ADB".
B. Run the following command: adb devices and confirm your device displays "sideload".
C. Run the following command: adb sideload ota_file.zip - where "ota_file.zip" is the name of the downloaded file.
5. Once the update has finished, reboot the phone by selecting "Reboot system now".
6. For added security, you should consider disabling USB debugging when the device is not being updated.
Tutorial
How to Capture OTA Link
Requirements
1. You will first need to enable USB debugging on your Android phone.
2. Also, set up ADB and Fastboot on your PC.
3. If you have rooted your device using SuperSU or Magisk or installed TWRP recovery, then you will not be able to install the OTA update. However, the OTA notification will still be intact.
4. Make sure that the OTA update notification has arrived on your specific device. Do not download or install it just yet.
Method 1: Capture OTA Update URL using PC
1. Connect your phone to the PC using the USB cable.
2. Go to C:\adb on your PC. This is the folder where all the ADB and Fastboot binaries are present.
3. Hold the SHIFT key and right-click on an empty space inside this folder. Or type "CMD" in the Windows explorer's address bar where the adb is located.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Select ‘Open Command window here’ or ‘Open PowerShell window here’ option.
5. The command-line window shall open up on your PC.
6. Enter the command to capture OTA update URL on Windows:
adb logcat > ota.txt
7. As soon as you execute this command, grab your device without disturbing the USB connection.
8. Open the system update window and start downloading the update. After 10-15 seconds, pause/cancel the download.
9. Go back to the command-line screen and press the Ctrl + C key on your keyboard.
10. Now go to C:\adb and open the ‘ota.txt‘ file.
Search (Ctrl + F) the text file for this link:
Code:
https://ota.googlezip.net/packages/ota-api/lge_phoenixsprout_phoenixlaocom/
Using these keywords, you shall be able to locate and capture OTA URL. Once you have the URL, paste in your browser’s address bar and download the file.
Rooted users can simply use a terminal emulator to capture OTA update URL. Simply install a terminal emulator (Termux) on your phone. And then use the ‘logcat > /sdcard/ota.txt‘ command to capture a full logcat of the system. Remember, only push the download button when you have executed the command. The ota.txt file will be placed on the root of your device’s storage. Note that this method only allows you to capture Android OTA URL. You wouldn’t be able to sideload the .zip file on a rooted device.
Method 2: Capture OTA Update URL using ‘Take bug report’ Option
1. First, enable ‘Developer options‘ and install Solid Explorer on your phone.
2. Go to the system updates and start downloading the new update.
3. Quickly go to ‘Settings’ -> ‘Developer options’ and tap on ‘Take bug report’.
4. When prompted, select ‘Interactive report’.
5. Finally, tap on ‘REPORT’ to capture OTA update URL of the latest firmware.
6. The feature will automatically take a capture a complete log of your system.
7. You will be able to see the progress in the persistent notification.
8. Once complete, tap on the notification to share the bug report.
9. Tap on ‘Solid Explorer’ in the share menu and save the bug report to the storage.
When the report has been saved, open the file and search the text file for this link:
Code:
https://ota.googlezip.net/packages/ota-api/lge_phoenixsprout_phoenixlaocom/
You shall easily be able to capture Android OTA update URL in the file.
If you have been able to capture OTA update URL for your Android device, then kindly share it with us through the comments. It would be nice to help each other, right? Stay tuned while we get more tips to ease out your Android experience.
Reserved
July 2019 Spotted!
Sent from my LG G7 One using Tapatalk
May 2019 to July 2019 OTA link now available.
Here's the Metadata:
ota-property-files=payload_metadata.bin:7338:547587,payload.bin:7338:328879093,payload_properties.txt:328886489:155,care_map.txt:894:235,compatibility.zip:1182:6109,metadata:69:777
ota-required-cache=0
ota-streaming-property-files=payload.bin:7338:328879093,payload_properties.txt:328886489:155,care_map.txt:894:235,compatibility.zip:1182:6109,metadata:69:777
ota-type=AB
post-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/1917620469a32:user/release-keys
post-build-incremental=1917620469a32
post-sdk-level=28
post-security-patch-level=2019-07-01
post-timestamp=1561463188
pre-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/191191607fb2e:user/release-keys
pre-build-incremental=191191607fb2e
pre-device=phoenix_sprout
Got another OTA links from different phones. Here are the metadata of those OTA:
September 2018 Q910UM10c - January 2019
ota-property-files=payload_metadata.bin:9779:552953,payload.bin:9779:870695951,payload_properties.txt:870705788:155,care_map.txt:898:235,compatibility.zip:1186:8546,metadata:69:781
ota-required-cache=0
ota-streaming-property-files=payload.bin:9779:870695951,payload_properties.txt:870705788:155,care_map.txt:898:235,compatibility.zip:1186:8546,metadata:69:781
ota-type=AB
post-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/190041836549e:user/release-keys
post-build-incremental=190041836549e
post-sdk-level=28
post-security-patch-level=2019-01-01
post-timestamp=1546594552
pre-build=lge/phoenix_lao_com/phoenix_sprout:8.1.0/OPM1.171019.026/182691521a86a:user/release-keys
pre-build-incremental=182691521a86a
pre-device=phoenix_sprout
September 2018 Q910UM10c to July 2019 Q910UM20q
ota-property-files=payload_metadata.bin:7342:569445,payload.bin:7342:939426062,payload_properties.txt:939433462:155,care_map.txt:898:235,compatibility.zip:1186:6109,metadata:69:781
ota-required-cache=0
ota-streaming-property-files=payload.bin:7342:939426062,payload_properties.txt:939433462:155,care_map.txt:898:235,compatibility.zip:1186:6109,metadata:69:781
ota-type=AB
post-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/1917620469a32:user/release-keys
post-build-incremental=1917620469a32
post-sdk-level=28
post-security-patch-level=2019-07-01
post-timestamp=1561463188
pre-build=lge/phoenix_lao_com/phoenix_sprout:8.1.0/OPM1.171019.026/182691521a86a:user/release-keys
pre-build-incremental=182691521a86a
pre-device=phoenix_sprout
Got another OTA links from different phones. Here are the metadata of those OTA:
September 2018 Q910UM10c - January 2019
ota-property-files=payload_metadata.bin:9779:552953,payload.bin:9779:870695951,payload_properties.txt:870705788:155,care_map.txt:898:235,compatibility.zip:1186:8546,metadata:69:781
ota-required-cache=0
ota-streaming-property-files=payload.bin:9779:870695951,payload_properties.txt:870705788:155,care_map.txt:898:235,compatibility.zip:1186:8546,metadata:69:781
ota-type=AB
post-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/190041836549e:user/release-keys
post-build-incremental=190041836549e
post-sdk-level=28
post-security-patch-level=2019-01-01
post-timestamp=1546594552
pre-build=lge/phoenix_lao_com/phoenix_sprout:8.1.0/OPM1.171019.026/182691521a86a:user/release-keys
pre-build-incremental=182691521a86a
pre-device=phoenix_sprout
September 2018 Q910UM10c to July 2019 Q910UM20q
ota-property-files=payload_metadata.bin:7342:569445,payload.bin:7342:939426062,payload_properties.txt:939433462:155,care_map.txt:898:235,compatibility.zip:1186:6109,metadata:69:781
ota-required-cache=0
ota-streaming-property-files=payload.bin:7342:939426062,payload_properties.txt:939433462:155,care_map.txt:898:235,compatibility.zip:1186:6109,metadata:69:781
ota-type=AB
post-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/1917620469a32:user/release-keys
post-build-incremental=1917620469a32
post-sdk-level=28
post-security-patch-level=2019-07-01
post-timestamp=1561463188
pre-build=lge/phoenix_lao_com/phoenix_sprout:8.1.0/OPM1.171019.026/182691521a86a:user/release-keys
pre-build-incremental=182691521a86a
pre-device=phoenix_sprout
save my phone.helppppppp
hello. can you backup g7 one phone system for me？my phone doesn't work. case I flash wrong firmware. so i need system backup to write in my phone. help me please .please save my phone s life.
Head's up!
August 2019 Q910UM20s Security Patch is up!
OP has been updated.
Here's the Metadata:
ota-property-files=payload_metadata.bin:7338:344099,payload.bin:7338:119230934,payload_properties.txt:119238330:155,care_map.txt:894:235,compatibility.zip:1182:6109,metadata:69:777
ota-required-cache=0
ota-streaming-property-files=payload.bin:7338:119230934,payload_properties.txt:119238330:155,care_map.txt:894:235,compatibility.zip:1182:6109,metadata:69:777
ota-type=AB
post-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/19200121451c4:user/release-keys
post-build-incremental=19200121451c4
post-sdk-level=28
post-security-patch-level=2019-08-01
post-timestamp=1563505981
pre-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/1917620469a32:user/release-keys
pre-build-incremental=1917620469a32
pre-device=phoenix_sprout
a72066 said:
hello. can you backup g7 one phone system for me？my phone doesn't work. case I flash wrong firmware. so i need system backup to write in my phone. help me please .please save my phone s life.
Click to expand...
Click to collapse
I'm sorry. If it's hard brick, you need to send it to your local store for that.
edwaine said:
I'm sorry. If it's hard brick, you need to send it to your local store for that.
Click to expand...
Click to collapse
thanks
Just curious. I recently bought a used/unlocked Canadian LG G7 One. On getting it i updated to latest PIE update that showed up. However the security patch in my device is Dec 2018. Any idea why this is happening?
prmbasheer said:
Just curious. I recently bought a used/unlocked Canadian LG G7 One. On getting it i updated to latest PIE update that showed up. However the security patch in my device is Dec 2018. Any idea why this is happening?
Click to expand...
Click to collapse
Did you try to factory reset? Maybe you'll get the whole latest update if you try to factory reset your phone.
MARK: Android 10 has been released to the public today. Hopefully, we get this final upgrade on our device before end of this quarter (Q3 2019).
September 2019 Q910UM20t is now up!
OP has been updated!
Heres the metadata:
ota-property-files=payload_metadata.bin:7338:409755,payload.bin:7338:130766804,payload_properties.txt:130774200:155,care_map.txt:894:235,compatibility.zip:1182:6109,metadata:69:777
ota-required-cache=0
ota-streaming-property-files=payload.bin:7338:130766804,payload_properties.txt:130774200:155,care_map.txt:894:235,compatibility.zip:1182:6109,metadata:69:777
ota-type=AB
post-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/1924514258a6b:user/release-keys
post-build-incremental=1924514258a6b
post-sdk-level=28
post-security-patch-level=2019-09-01
post-timestamp=1567401903
pre-build=lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/19200121451c4:user/release-keys
pre-build-incremental=19200121451c4
pre-device=phoenix_sprout
As per check, it seems there's another September update that will arrive for LG G7 One users.
prmbasheer said:
Just curious. I recently bought a used/unlocked Canadian LG G7 One. On getting it i updated to latest PIE update that showed up. However the security patch in my device is Dec 2018. Any idea why this is happening?
Click to expand...
Click to collapse
I am in the same boat! Bought the phone on eBay a few weeks ago. Dec 2018 is the lastest patch. Were you able to find a solution to this?
ydmf222 said:
I am in the same boat! Bought the phone on eBay a few weeks ago. Dec 2018 is the lastest patch. Were you able to find a solution to this?
Click to expand...
Click to collapse
I tried searching for solution everywhere. I am yet to find one. There are some suggestions that re-flashing the device with a compatible firmware would help. But I am done with that kind of stuff for a long time now. I am just going to keep using it the way it is. It is something to do with being a retail unit is my guess. i don't think it is will see another update.
prmbasheer said:
I tried searching for solution everywhere. I am yet to find one. There are some suggestions that re-flashing the device with a compatible firmware would help. But I am done with that kind of stuff for a long time now. I am just going to keep using it the way it is. It is something to do with being a retail unit is my guess. i don't think it is will see another update.
Click to expand...
Click to collapse
I also have this on my LG G7 One. December 2018 is latest update. Also, weird software version number. It's Q910UM25a - the 25a seems like a non-standard build. I have no idea how to switch it to a normal build. My phone doesn't seem to have a recovery mode - I can get the sideways robot exclaimation mark screen, but hitting power and volume up restarts the phone, it doesn't take me to another menu where I can select anything.