Related
It seems as if Google removed the option to unlock the bootloader on KitKat (4.4.2). Now the command "fastboot oem unlock" fails with an error and the htcdev token method does not work on GPe. Are we out of luck? Is there another way to unlock the bootloader?
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
HT36Jxxxxxxx device
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.608s]
finished. total time: 0.608s
Here is my getvar all info
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Is this a GPE conversion or a genuine GPE device?
cschmitt said:
Is this a GPE conversion or a genuine GPE device?
Click to expand...
Click to collapse
Genuine GPE. Never been tampered with.
I am experiencing the same issue
cschmitt said:
Is this a GPE conversion or a genuine GPE device?
Click to expand...
Click to collapse
I am also experiencing the same "Loading custom splash failed" issue. Mine is a genuine HTC One Google Play Edition that has been updated to 4.4.2 over the air. It has never been unlocked or rooted.
applsplatz said:
I am also experiencing the same "Loading custom splash failed" issue. Mine is a genuine HTC One Google Play Edition that has been updated to 4.4.2 over the air. It has never been unlocked or rooted.
Click to expand...
Click to collapse
You are not the only one having this issue. Many other GPE owners on 4.4.2 are facing the same problem.
Waiting4MyAndroid said:
You are not the only one having this issue. Many other GPE owners on 4.4.2 are facing the same problem.
Click to expand...
Click to collapse
This is an interesting problem.
The error:
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
is occurring while hboot is attempting to read the unlock splash image from pg2fs (mmcblk0p7) -- this is where the pg2fs_spcustom.img found in RUU's is written.
The traverse offset is 0x839, or the 0x840th 16-byte page in the partition. If you dump p7 using dd and check address 0x8400 it starts with 'HTCCUSSP', which is the header for the beginning of the unlock splash image.
Basically, hboot is saying that the read failed for some reason.
What doesn't make sense is that GPE users on 4.3 are able to fastboot oem unlock, but on 4.4.2 they aren't, yet the 4.4.2 OTA firmware.zip for 3.62.1700.1 only contains hboot (1.54.0000), boot, recovery, and rpm. It doesn't contain the pg2fs_spcustom.img, so how could it get changed or corrupted?
Also, the GPE 1.54.0000 hboot works fine to fastboot oem unlock on other devices. I have an AT&T One, flashed the 3.58.1700.1 firmware, then the 3.62.1700.1 firmware, locked the bootloader, and then did a fastboot oem unlock and the unlock splash screen popped right up.
I'd be interested to hear from GPE owners as to which OS version the unlock works and which it does not, and also collect a couple of mmcblk0p7 images from GPE owners on 4.2.2, 4.3, and 4.4.2 for comparison.
To dump mmcblk0p7:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7.bin
exit
exit
adb pull /sdcard/mmcblk0p7.bin
Then zip it up and post in this thread (it zips to under 100KB.)
Maybe we arrive at some solution for this.
cschmitt said:
This is an interesting problem.
The error:
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
is occurring while hboot is attempting to read the unlock splash image from pg2fs (mmcblk0p7) -- this is where the pg2fs_spcustom.img found in RUU's is written.
The traverse offset is 0x839, or the 0x840th 16-byte page in the partition. If you dump p7 using dd and check address 0x8400 it starts with 'HTCCUSSP', which is the header for the beginning of the unlock splash image.
Basically, hboot is saying that the read failed for some reason.
What doesn't make sense is that GPE users on 4.3 are able to fastboot oem unlock, but on 4.4.2 they aren't, yet the 4.4.2 OTA firmware.zip for 3.62.1700.1 only contains hboot (1.54.0000), boot, recovery, and rpm. It doesn't contain the pg2fs_spcustom.img, so how could it get changed or corrupted?
Also, the GPE 1.54.0000 hboot works fine to fastboot oem unlock on other devices. I have an AT&T One, flashed the 3.58.1700.1 firmware, then the 3.62.1700.1 firmware, locked the bootloader, and then did a fastboot oem unlock and the unlock splash screen popped right up.
I'd be interested to hear from GPE owners as to which OS version the unlock works and which it does not, and also collect a couple of mmcblk0p7 images from GPE owners on 4.2.2, 4.3, and 4.4.2 for comparison.
To dump mmcblk0p7:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7.bin
exit
exit
adb pull /sdcard/mmcblk0p7.bin
Then zip it up and post in this thread (it zips to under 100KB.)
Maybe we arrive at some solution for this.
Click to expand...
Click to collapse
Thank you for the detailed response. Is there a way to dump mmcblk0p7 without SU access? My phone is unrooted and S-ON.
Waiting4MyAndroid said:
Thank you for the detailed response. Is there a way to dump mmcblk0p7 without SU access? My phone is unrooted and S-ON.
Click to expand...
Click to collapse
Hmm, not that I'm aware of.
Waiting4MyAndroid said:
Thank you for the detailed response. Is there a way to dump mmcblk0p7 without SU access? My phone is unrooted and S-ON.
Click to expand...
Click to collapse
cschmitt said:
Hmm, not that I'm aware of.
Click to expand...
Click to collapse
you can try firewater temproot exploit, but i dont think it'll help much... GPE "fastboot oem unlock" no longer works
Im also having this issue. Is there anything that we can make this progress? I haved check all over the internet and there is not many people talking about this issue
cruel91 said:
Im also having this issue. Is there anything that we can make this progress? I haved check all over the internet and there is not many people talking about this issue
Click to expand...
Click to collapse
I read on another thread about someone calling Google support and was told a patch is in the works to fix this bug in kitkat. Google is aware of the problem.
**Edit**
Here is the link http://forum.xda-developers.com/showthread.php?t=2547894&page=2
Sent from my HTC One using xda app-developers app
@nkk71 I've been looking into this today.
Flashed a 1.54 GPE hboot (Aug 13th version), did an oem relock, rebooted to bootloader, then oem unlock. Unlock splash appeared, but I selected 'no' as I didn't want to wipe my device. (since I'm still s-off I use revone to unlock if needed.)
As device was rebooting I held volume down to reenter bootloader, but screen remained blank. So I issued oem readcid (still connected to usb) to check it it was alive. Crazy thing, it reported cid as 11111111, but my cid is actually set to BS_US001!
Next did fastboot reboot-bootloader, this time display is on, cid displays BS_US001 but mainver is now blank on both display and in getvar all.
Soo. Something weird happened while attempting to unlock on this hboot (or during following reboot ) that basically wiped the first few hundred bytes of p19 where current cid and mainver are stored.
I had to reflash firmware to get mainver back.
Just sharing this because maybe the attempted unlock is causing the corruption leading to the active command line overflow issue.
cschmitt said:
@nkk71 I've been looking into this today.
Flashed a 1.54 GPE hboot (Aug 13th version), did an oem relock, rebooted to bootloader, then oem unlock. Unlock splash appeared, but I selected 'no' as I didn't want to wipe my device. (since I'm still s-off I use revone to unlock if needed.)
As device was rebooting I held volume down to reenter bootloader, but screen remained blank. So I issued oem readcid (still connected to usb) to check it it was alive. Crazy thing, it reported cid as 11111111, but my cid is actually set to BS_US001!
Next did fastboot reboot-bootloader, this time display is on, cid displays BS_US001 but mainver is now blank on both display and in getvar all.
Soo. Something weird happened while attempting to unlock on this hboot (or during following reboot ) that basically wiped the first few hundred bytes of p19 where current cid and mainver are stored.
I had to reflash firmware to get mainver back.
Just sharing this because maybe the attempted unlock is causing the corruption leading to the active command line overflow issue.
Click to expand...
Click to collapse
Thanks for the info;
interesting about the CID, the one being read by fastboot is actually stored in p4 and p5 (one possibly being a backup for the other?)... maybe when bootloader got stuck, it automatically activated SuperCID as a "safety measure"??
as for the missing version-main, this has happened a lot (and for countless reasons, and pretty much with little consistency)... but those never resulted in the Active cmdline overflow. so i don't think p19 would be the cause of that.
still all of it is very strange.
This is really irritating. I don't think I'm ever going to buy a Google Edition phone again! How am I supposed to sell this phone on eBay when it's in a half-working condition, sure it works and runs the latest version of Android, but anyone interested in buying this phone will want to unlock it as soon as they get it and when it gives them this error...they are going to be hunting me down questioning me why it can't be unlocked or rooted...
sionicion said:
This is really irritating. I don't think I'm ever going to buy a Google Edition phone again! How am I supposed to sell this phone on eBay when it's in a half-working condition, sure it works and runs the latest version of Android, but anyone interested in buying this phone will want to unlock it as soon as they get it and when it gives them this error...they are going to be hunting me down questioning me why it can't be unlocked or rooted...
Click to expand...
Click to collapse
I am contacting both Google and HTC support. Please check my post here. You can contribute by sending new support case about this issue. They would hear us
http://forum.xda-developers.com/showthread.php?t=2547894
Sent from my HTC One using Tapatalk
Does GPE 5.1 solved the problem ?
imadsaber said:
Does GPE 5.1 solved the problem ?
Click to expand...
Click to collapse
We don't know yet. I am still waiting for the OTA. I will attempt to unlock bootloader right after installing the OTA. Will report back soon. Fingers crossed.
Lollipop OTA did not fix the problem. Still getting same error when attempting to unlock the bootloader. That is so [email protected]#ked up!
if any one know anything please tell us ! thank you
Waiting4MyAndroid said:
Lollipop OTA did not fix the problem. Still getting same error when attempting to unlock the bootloader. That is so [email protected]#ked up!
Click to expand...
Click to collapse
Oh noooooooooo :'(
Hi, I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T. When I installed WhatsApp, it said that my phone has a 'custom ROM' and that some features won't work, but otherwise the phone is working just fine. Due to this ROM I'm not getting OTAs as well and I'm stuck on 4.2.2 Jellybean.
My question is that can I flash any other ROM on the phone so that I start receiving OTAs and while making sure that my phone remains unlocked? I don't want to end up locking my phone again. Can flashing a new ROM lock my phone again? Can I revert to stock ROM somehow (maybe the set isn't originally of AT&T)? Or can I flash Rogers ROM which also of XT1058?
In need of help. Thanks.
Flashing a ROM will not lock your bootloader.
You can only flash same firmware versions or newer, never downgrade.
Yes you can flash the stock Rogers firmware. You can find it in the going back to stock guide.
nhizzat said:
Flashing a ROM will not lock your bootloader.
You can only flash same firmware versions or newer, never downgrade.
Yes you can flash the stock Rogers firmware. You can find it in the going back to stock guide.
Click to expand...
Click to collapse
Thanks. Sorry for bothering but I meant SIM locking. Will flashing a ROM SIM lock my phone again or is the answer still the same?
Secondly, how would I know which is the stock ROM for me? It says XT1058 and 'Assembled in China' on the back, so maybe it's from some Latin American country. Should I still go for the Rogers ROM because it's bloat-free?
RafaySid said:
Thanks. Sorry for bothering but I meant SIM locking. Will flashing a ROM SIM lock my phone again or is the answer still the same?
Click to expand...
Click to collapse
It will not SIM lock your phone.
RafaySid said:
Secondly, how would I know which is the stock ROM for me? It says XT1058 and 'Assembled in China' on the back, so maybe it's from some Latin American country. Should I still go for the Rogers ROM because it's bloat-free?
Click to expand...
Click to collapse
Since your phone has already been Bootloader unlocked (because the ROM in your phone is not stock right now), it doesn't matter which ROM you choose. I'd say choosing a bloat-free ROM is great!
RafaySid said:
Hi, I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T. When I installed WhatsApp, it said that my phone has a 'custom ROM' and that some features won't work, but otherwise the phone is working just fine. Due to this ROM I'm not getting OTAs as well and I'm stuck on 4.2.2 Jellybean.
My question is that can I flash any other ROM on the phone so that I start receiving OTAs and while making sure that my phone remains unlocked? I don't want to end up locking my phone again. Can flashing a new ROM lock my phone again? Can I revert to stock ROM somehow (maybe the set isn't originally of AT&T)? Or can I flash Rogers ROM which also of XT1058?
In need of help. Thanks.
Click to expand...
Click to collapse
First you need to know if your bootloader is unlocked or locked.
Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
If the bootloader is locked, you'll only be able to flash Stock ROMs signed by Moto, and made for the same "(bootloader) cid:" as your phone.
Flashing a ROM will not lock a bootloader that has been unlocked. The only time I've seen flashing a ROM re-sim lock is the Sprint XT1056 where a hack is used to sim unlock it.
Btw, ATT phones usually have the ATT carrier branding on the case, even if it was from Moto Maker.
KidJoe said:
First you need to know if your bootloader is unlocked or locked.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
If the bootloader is locked, you'll only be able to flash Stock ROMs signed by Moto, and made for the same "(bootloader) cid:" as your phone.
Flashing a ROM will not lock a bootloader that has been unlocked. The only time I've seen flashing a ROM re-sim lock is the Sprint XT1056 where a hack is used to sim unlock it.
Btw, ATT phones usually have the ATT carrier branding on the case, even if it was from Moto Maker.
Click to expand...
Click to collapse
2nd line: 30.70 (sha-88483d6, 2013-07-02 15:32:03)
.
.
.
.
Device is UNLOCKED. Status Code: 1
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Farooq>cd/
C:\>cd android
C:\Android>fastboot getvar all
(bootloader) version-bootloader: 3070
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: TA1760BS0H
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: EF8D10040C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Fri Jul 12 11:37:14 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X_140
(bootloader) ro.build.tags: intcfg,test-keys
(bootloader) ro.build.type: userdebug
(bootloader) ro.build.user: e13522
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 23546373
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X_140/23546373:userdebug
(bootloader) ro.build.fingerprint[2]: /intcfg,test-keys
(bootloader) ro.build.version.full[0]: Blur_Version.13.0.23546373.ghost
(bootloader) ro.build.version.full[1]: _att.ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-eng-g
(bootloader) kernel.version[1]: 66c71d4 ([email protected])
(bootloader) kernel.version[2]: (gcc version 4.6.x-google 201201
(bootloader) kernel.version[3]: 06 (prerelease) (GCC) ) #1 SMP P
(bootloader) kernel.version[4]: REEMPT Fri Jul 12 11:55:44 CDT 2
(bootloader) kernel.version[5]: 013
all:
finished. total time: 0.122s
C:\Android>
A few things..
With Bootloader of 30.70, that is the initial shipping bootloader. Based on the versions, it appears to also been the initial shipping ATT ROM. (i.e. the previous owner did not flash only PARTS of a ROM).
Unlocked Status 1 is good. You should be able to flash signed and unsigned roms. So if you want to switch to CM or such, you can. And you can flash 3rd party recovery and root too.
A few things that concern me from the fastboot output...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
I've only seen it say YES or NO for those. This is the first I've seen "Not Supported"
(bootloader) cid: 0xdead
I've not seen the CID listed as DEAD before. Its always been a hex value.
And I'm hoping you just removed your imei and meid, and not that they are actually missing from the output.
One last thing I missed in your other posts, that it says XT1058 on the back and MADE IN CHINA. The ATT XT1058's all said made in USA if I'm not mistaken. So chances are best that its NOT an ATT XT1058.
What carrier are you using this phone on? Do they sell the XT1058? If so, consider finding the latest XT1058 SBF for that carrier and flashing it.
RISKS of doing that: It might fail and brick your phone in the process. It might be successful but you end up having no IMEI/MEID in the process. You end up in a state where you have that SBF on there, but improper carrier settings so future OTA's fail and you have to flash them manually. Or Best case.... It works, and those variables go back to "normal" values.
Its your call if you want to take the chance.
Thanks for the kind reply, I really appreciate it.
I asked Motorola's support person on live chat and he said that the previous owner most probably damaged the phone while flashing as it is not showing any IMEI number. I think the previous guy most probably flashed an AT&T ROM on it and this phone is likely to be from Latin America (XT1058). I'm interested in flashing Roger's ROM as it is bloat-free. I won't flash KitKat on it since it has battery draining issues and will wait for Lollipop.
But are the..
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
..things to be worried about? Will I most probably end up bricking it?
RafaySid said:
Thanks for the kind reply, I really appreciate it.
I asked Motorola's support person on live chat and he said that the previous owner most probably damaged the phone while flashing as it is not showing any IMEI number. I think the previous guy most probably flashed an AT&T ROM on it and this phone is likely to be from Latin America (XT1058). I'm interested in flashing Roger's ROM as it is bloat-free. I won't flash KitKat on it since it has battery draining issues and will wait for Lollipop.
Click to expand...
Click to collapse
Yes, definitely caused while screwing around and doing something that shouldn't have been done.
So the IMEI is definitely missing? I would think in that case you wont see the mobile/cellular network and only Wifi would work. But you said other than the OTA's the phone was working fine.
There were some threads about some getting into that situation (Missing IMEI). I know there were some XT1052 users trying to flash Non-XT1052 roms and running into this, but being unable to recovery. I think there was some users who ran into it for other reasons and were able to recover. Its time to start searching. Like -> http://forum.xda-developers.com/moto-x/moto-x-qa/cdn-rogers-1058-fr-4-4-2-update-to-4-4-t2842787
RafaySid said:
But are the..
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
..things to be worried about? Will I most probably end up bricking it?
Click to expand...
Click to collapse
As I've said, the "Not Supported" and "0xdead" values do worry me. I've not seen them before, so I can't tell you what impact they have on flashing. That is why I said bricking was a risk and that its your choice what to do.
At this point, if you have a working phone, keep with it and using it. Or you try and flash a Rogers XT1058 SBF, taking the chance of bricking it in the process. If you take this route, use Option 5 (and its pre-req's) at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html Get roms from places in this thread -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
I would really suggest flashing the LATEST SBF, in this case 4.4.4.
As for the "battery drain" reported under 4.4.4, for me anyway it seems to vary depending on installed apps. I can still get more than a day with my XT1060 running 4.4.4 with all google and moto apps updated. Occasionally after a bunch of apps update, I see less battery life, but then it seems to settle down and go back to normal.
If you want to flash Rogers 4.4.4, per this thread -> http://forum.xda-developers.com/mot...rogers-canada-4-4-4-sbf-t2905525/post56055157 it appears to be XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip BUT I HAVE NOT CONFIRMED THIS SO PROCEED WITH CAUTION!!!
Good Luck!!
The cellular network is working fine. Can I at least root it? Which method should I choose?
RafaySid said:
The cellular network is working fine. Can I at least root it? Which method should I choose?
Click to expand...
Click to collapse
First, find a copy of the SBF for the rom on your phone before you do anything.
Since you have an unlocked bootloader, just follow -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
Because you have an older rom and bootloader, just use the versions linked in there. If you ever update the ROM on your phone, you would want to consider using newer versions of TWRP and SuperSU
In order to root, do I need a custom recovery? I'm at 4.2.2 Jellybean atm.
In order to root, you need to read. Seriously, just read and you'll have your answer.
I'm being 'extra careful' because of those abnormal values.
Sent from my Moto X using Tapatalk
RafaySid said:
In order to root, do I need a custom recovery? I'm at 4.2.2 Jellybean atm.
Click to expand...
Click to collapse
There are two ways to root one is for LOCKED bootloaders, the other is if your bootloader is UNLOCKED.
Unlocked bootloader is done by flashing a custom recovery like TWRP, rebooting to bootloader (so the recovery sticks), entering the recovery, and TWRP will usually ask you if you want to root so you answer yes. (sometimes manually installing SuperSU from TWRP is needed). This both roots and disables write protection.
For a LOCKED bootloader you are exploiting vulnerabilities in the roms. You need to be on a certain rom for it to work, there are extra hacks needed to disable write protection. Its a complicated process that sometimes requires flashing different roms. (I don't remember back to the original shipping 4.2.2 for locked bootloader process, I think it might be PwnMyMoto??).
Because of those values on your phone, any flashing or hacking could be risky. Doing the unlocked method (thread link I pasted earlier) of flashing twrp, is the easiest way to root.
Unless you are willing to take a chance, and risk bricking your phone, I'm not sure how to really advise you because everything at this point is unknown territory.
KidJoe said:
There are two ways to root one is for LOCKED bootloaders, the other is if your bootloader is UNLOCKED.
Unlocked bootloader is done by flashing a custom recovery like TWRP, rebooting to bootloader (so the recovery sticks), entering the recovery, and TWRP will usually ask you if you want to root so you answer yes. (sometimes manually installing SuperSU from TWRP is needed). This both roots and disables write protection.
For a LOCKED bootloader you are exploiting vulnerabilities in the roms. You need to be on a certain rom for it to work, there are extra hacks needed to disable write protection. Its a complicated process that sometimes requires flashing different roms. (I don't remember back to the original shipping 4.2.2 for locked bootloader process, I think it might be PwnMyMoto??).
Because of those values on your phone, any flashing or hacking could be risky. Doing the unlocked method (thread link I pasted earlier) of flashing twrp, is the easiest way to root.
Unless you are willing to take a chance, and risk bricking your phone, I'm not sure how to really advise you because everything at this point is unknown territory.
Click to expand...
Click to collapse
Yes thank you. I had already rooted using TWRP.
Can I install an offline update instead of flashing, to update 4.2.2?
Sent from my Moto X using Tapatalk
These 2 threads have everything you need to know,
Rooting,
http://forum.xda-developers.com/showthread.php?t=2826159
Flashing firmware, (returning to stock section)
http://forum.xda-developers.com/showthread.php?t=2603358
I'm not sure what you are meaning by "offline" update... But how to update manually is covered in above thread. ?
Yeah I meant manually updating. Thanks.
Sent from my Moto X using Tapatalk
RafaySid said:
Yeah I meant manually updating. Thanks.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
there are two types of Update.
OTA update (they are incremental, only flash what changed since the last version, need to be stock recovery, and rest of phone as close to stock as possible. and you'll need a certain version on your phone)
Flashing a full SBF (as explained earlier when I mentioned about possibly flashing the Rogers XT1058 rom, and pointed you towards using Option 5 and its pre-req's at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html . It has a couple commands repeated which makes it a little more successful. )
Either way, in your situation, is risky.
Hello,
I am a beginner at rooting phones. I am currently trying to unlock bootloader on my Moto X 2013 (xt1058). As of now, whenever I input the "fastboot oem get_unlock_data" I am recieving this:
C:\Users\{Username}\AppData\Local\Android\sdk\platform-tools>fastboot oem get_unlock_data
(bootloader) Variable not supported!
(bootloader) Variable not supported!
(bootloader) Variable not supported!
...
(bootloader) 3A35120665262996#54303131333043
(bootloader) 56334300000000000000000000#DC4A
(bootloader) E30140AB74170713FB64AE43E64BED9
(bootloader) 52E37#500B81040C000100000000000
(bootloader) 0000000
OKAY [ 0.350s]
When I go to the Motorola's website to see if my device can have the bootloader unlocked, it says it can't.
My system version is 222.201.1.ghost_att.ATT.en.US att
Also my phone is unlocked (meaning it works with any carrier) and I am not sure if that affects the bootloader unlock process.
Any help would be much appreciated and I am open to alternate methods as well. I currently want to install cm13 and use twrp recovery.
Thanks in advance!
smartish123 said:
Hello,
I am a beginner at rooting phones. I am currently trying to unlock bootloader on my Moto X 2013 (xt1058). As of now, whenever I input the "fastboot oem get_unlock_data" I am recieving this:
C:\Users\{Username}\AppData\Local\Android\sdk\platform-tools>fastboot oem get_unlock_data
(bootloader) Variable not supported!
(bootloader) Variable not supported!
(bootloader) Variable not supported!
...
(bootloader) 3A35120665262996#54303131333043
(bootloader) 56334300000000000000000000#DC4A
(bootloader) E30140AB74170713FB64AE43E64BED9
(bootloader) 52E37#500B81040C000100000000000
(bootloader) 0000000
OKAY [ 0.350s]
When I go to the Motorola's website to see if my device can have the bootloader unlocked, it says it can't.
My system version is 222.201.1.ghost_att.ATT.en.US att
Also my phone is unlocked (meaning it works with any carrier) and I am not sure if that affects the bootloader unlock process.
Any help would be much appreciated and I am open to alternate methods as well. I currently want to install cm13 and use twrp recovery.
Thanks in advance!
Click to expand...
Click to collapse
If Moto website that give code send you an email with the code, you can unlocked the phone.
Also the "(bootloader)" part must be cancelled, you only need the number and letter like they say on Moto website
Dear Friends,
Does this mean I have to flash correct version of the file in to my phone.
C:\Users\Rayzen>fastboot oem system-info
(bootloader) board_info: msmnile
(bootloader) mem_info: 8GB
(bootloader) cpu_freq: 2.96GHz
(bootloader) product_name: ASUS_I001_1
(bootloader) product_locale: zh-CN
(bootloader) product_carrier: ASUS-ASUS_I001D-WW
(bootloader) csc_build_version: CN_ZS660KL-16.0621.1906.24-0----------------<<<<<<Is this a WRONG VERSION?
(bootloader) bt_mac: 0xxxxxxxx3CD
(bootloader) wifi_mac: 0xxxxxxxx5AD
(bootloader) imei:
(bootloader) imei2:
(bootloader) ssn: K8AIKN06K111xxx
(bootloader) isn: ZS80K19725x12345
(bootloader) color: 1A
(bootloader) country: WW
(bootloader) customer: ASUS
(bootloader) ufs:
(bootloader) setupwizard: true
OKAY [ 0.021s]
Finished. Total time: 0.022s
can some one help me get this thing running - it is stuck on a boot logo for ages.
What exactly did you flash?
TikiThePug said:
What exactly did you flash?
Click to expand...
Click to collapse
didn't know at first so I used qpst and flash ww - it was stuck after the boot screen one and two at white screen
and then changed it to cn and there was no white screen but recently flashed with
WW_ZS660KL_16.0631.1910.64_M3.13.33.33-ASUS_1.1.253_Phone-user.raw
and saw welcome screen with english usa and charging notification and internet connectivity screen and then it rebooted.
I think I have to find a way to re heat a emmc or find a short in it of some kind
OR
do you want me to flash with the os it came with ?
WW_ZS660KL_16.0622.1906.19_M3.13.33.20-ASUS_1.1.93_Phone-user.raw
c0mputer said:
didn't know at first so I used qpst and flash ww - it was stuck after the boot screen one and two at white screen
and then changed it to cn and there was no white screen but recently flashed with
WW_ZS660KL_16.0631.1910.64_M3.13.33.33-ASUS_1.1.253_Phone-user.raw
and saw welcome screen with english usa and charging notification and internet connectivity screen and then it rebooted.
I think I have to find a way to re heat a emmc or find a short in it of some kind
OR
do you want me to flash with the os it came with ?
WW_ZS660KL_16.0622.1906.19_M3.13.33.20-ASUS_1.1.93_Phone-user.raw
Click to expand...
Click to collapse
If your bootloader is unlocked, I suggest flashing the stock RAW your phone came with, then try the WW conversion instructions again
For those who are planning to buy from Motorola China (CN ROM), do NOT convert to Global ROM! Do NOT buy from an online retailer where the phone has been converted to global ROM.
This is a warning to everyone if you don't want any headache in software support.
Reasons why you should NOT convert to Global ROM:
1. You can NEVER re-lock your bootloader - your phone will get BRICKED if you try to re-lock your bootloader.
2. You can NEVER update your software over-the-air. Do you want to own a phone with an update-less software? Yes, this is NOT possible as there will be an error message everytime you try to update your phone's software.
3. There will be a WARNING MESSAGE ("Your bootloader is unlocked.. etc") every time you restart your phone. Do you want this nasty message to ruin your phone's software?
4. Google Pay will detect your phone as tampered won't meet security requirements.
5. Streaming platforms and banking apps may not work once your phone is rooted.
Why do you NEED to update to Global ROM when in fact, CN ROM OFFICIALLY SUPPORTS Google Play Services.
1. Just go to Settings > System > Google Play Services
2. Toggle to ON and you can now install Play Store and use it to download your favorite Google Apps.
NO issues whatsoever. As simple as that.
My device is converted and bl is locked. That's how it came to me, i have no idea It's not even unlocked right now )
Updates are coming and installing, no problem.
BL locked & no warning message.
Even if this was not the case, i would like to convert the device again, because there is no language in CN rom, as far as i know, only CN and EN languages.
My country Turkey & my language Turkish
Your question is a little pointless. Not everyone has to know Chinese or English. For this reason, it may need this procedure, for example I
cascade128 said:
My device is converted and bl is locked. That's how it came to me, i have no idea It's not even unlocked right now )
Updates are coming and installing, no problem.
BL locked & no warning message.
Even if this was not the case, i would like to convert the device again, because there is no language in CN rom, as far as i know, only CN and EN languages.
My country Turkey & my language Turkish
Your question is a little pointless. Not everyone has to know Chinese or English. For this reason, it may need this procedure, for example I
Click to expand...
Click to collapse
Read below
Pls don't spread false information that bl can be RE-LOCKED because Motorola modders know it will brick your phone
[CLOSED] Convert your Moto x30 Pro (CN) to Edge 30 Ultra (EU)
FIRST OFF: If you have not bought the phone yet and plan on getting it: DON'T. The camera is broken and Motorola refuses to communicate with their customers. Is a fix coming? I someone working on it? Who knows. The phone is also still on Android...
forum.xda-developers.com
ijuanp03 said:
Read below
Pls don't spread false information that bl can be RE-LOCKED because Motorola modders know it will brick your phone
[CLOSED] Convert your Moto x30 Pro (CN) to Edge 30 Ultra (EU)
FIRST OFF: If you have not bought the phone yet and plan on getting it: DON'T. The camera is broken and Motorola refuses to communicate with their customers. Is a fix coming? I someone working on it? Who knows. The phone is also still on Android...
forum.xda-developers.com
Click to expand...
Click to collapse
Dude, i don't give information to "lock it". I wrote "It was sold to me like this, i received it like this" look there, read it well, don't be idle
ijuanp03 said:
Read below
Pls don't spread false information that bl can be RE-LOCKED because Motorola modders know it will brick your phone
[CLOSED] Convert your Moto x30 Pro (CN) to Edge 30 Ultra (EU)
FIRST OFF: If you have not bought the phone yet and plan on getting it: DON'T. The camera is broken and Motorola refuses to communicate with their customers. Is a fix coming? I someone working on it? Who knows. The phone is also still on Android...
forum.xda-developers.com
Click to expand...
Click to collapse
I dont know if it can really brick your phone when you convert in a clean way and your device is recognized as the original.
But I put the warning there as a lot of people have bricked their devices before by not paying proper attention.
In theory it SHOULD be possible to relock, once you are on the original firmware but I strongly advise against it.
No idea how @cascade128 received a locked converted device though, seems to be possible.
I dont know why you are so radical against unlocking, of course it brings drawbacks but that was always the case since Samsung implemented efuses.
Also: Android Auto and Hey Google do not work on CN and there is a very limited language selection.
@cascade128: could you boot into fastboot / bootloader, create a "fastboot getvar all" dump and send it to me via PM?
I'd really like to take a look at this. Also: Does the Lenovo Rescue assistant recognize your device as xt2241-2?
Killuminati91 said:
I dont know if it can really brick your phone when you convert in a clean way and your device is recognized as the original.
But I put the warning there as a lot of people have bricked their devices before by not paying proper attention.
In theory it SHOULD be possible to relock, once you are on the original firmware but I strongly advise against it.
No idea how @cascade128 received a locked converted device though, seems to be possible.
I dont know why you are so radical against unlocking, of course it brings drawbacks but that was always the case since Samsung implemented efuses.
Also: Android Auto and Hey Google do not work on CN and there is a very limited language selection.
@cascade128: could you boot into fastboot / bootloader, create a "fastboot getvar all" dump and send it to me via PM?
I'd really like to take a look at this. Also: Does the Lenovo Rescue assistant recognize your device as xt2241-2?
Click to expand...
Click to collapse
I sent
Well the fact to have a converted device with a locked bootloader it is good for modding!
I guess @cascade128 bought from a vendor that has maybe contacts in Motorola (or is someone from Motorola itself) that has access to stuff that we don't.
It is interesting though...cause I'm holding on on unlocking the bootloader (and then rooting) for warranty purposes and I don't how long I can wait
Cause now my "Unlock OEM" option isn't greyed out anymore
I bought the device second hand and it was like this. I also get this error when i try to unlock BL.
Error:
(bootloader) Failed to get unlock data.
OKAY [ 0.026s]
Finished. Total time: 0.028s
Mobile phones imported in our country(Turkey) must be registered with a passport, paying tax (government tax $150). Conditions: Having entered/exited a country with this passport in the last 1 year and the sim card(s) to be used in the device belong to the passport holder. This device has to be used by this passport holder for 3 years. For this reason, the imei numbers of this device have also been changed. 2 imei numbers belong to an old Motorola brand device. Main question; how did he enable bootloader lock after doing these? I think what he's using is the software box. Otherwise, this operation is not possible! The guy who made it gave this information, paid $60.
My device:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-eqs-3d687e600d1-220914
(bootloader) product: eqs
(bootloader) board: eqs
(bootloader) secure: yes
(bootloader) lcs-state: SECURE_PROD_MODE
(bootloader) hwrev: PVT1C
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB SAMSUNG KLUEG4RHGB-B0E1 FV=0201 WB=2048
(bootloader) ram: 12GB SAMSUNG LP5 DIE=12Gb CH=4
(bootloader) cpu: SM_PALIMA 1.0
(bootloader) serialno: ***************
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 41E4067C001D90E1
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: allowed
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) chipid: 0000043B41E4067C
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: ********************
(bootloader) imei2: ******************
(bootloader) meid:
(bootloader) date: 08-21-2022
(bootloader) sku: XT2241-1
(bootloader) carrier_sku: XT2241-1
(bootloader) battid: SB18D62340
(bootloader) battery-voltage: 3975
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: reteu
(bootloader) ro.build.fingerprint[0]: motorola/eqs_ge/eqs:12/S3SQ32.16-5
(bootloader) ro.build.fingerprint[1]: 3-9/d68d4-cb5c2:user/release-keys
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.VENDOR.1.0.R1
(bootloader) ro.build.version.qcom[1]: .11.00.00.816.142
(bootloader) version-baseband[0]: M8475_DE10_240.2652.01.143.19R EQS_PVT
(bootloader) version-baseband[1]: 1C_ROWDSDS_CUST
(bootloader) kernel.version[0]: Linux version 5.10.101-android12-9-00001
(bootloader) kernel.version[1]: -g1b6eff567cae-ab8943976 ([email protected]
(bootloader) kernel.version[2]: ld-host) (Android (7284624, based on r41
(bootloader) kernel.version[3]: 6183b) clang version 12.0.5 (https://and
(bootloader) kernel.version[4]: roid.googlesource.com/toolchain/llvm-pro
(bootloader) kernel.version[5]: ject c935d99d7cf2016289302412d708641d52d
(bootloader) kernel.version[6]: 2f7ee), LLD 12.0.5 (/buildbot/src/androi
(bootloader) kernel.version[7]: d/llvm-toolchain/out/llvm-project/lld c9
(bootloader) kernel.version[8]: 35d99d7cf2016289302412d708641d52d2f7ee))
(bootloader) kernel.version[9]: #1 SMP PREEMPT Sat Aug 13 08:16:31 UTC
(bootloader) kernel.version[10]: 2022
(bootloader) git:xbl_config: MBM-3.0-eqs-01b1dd0a1-dirty-220914
(bootloader) git:xbl_ramdump: MBM-3.0-eqs-01b1dd0a1-dirty-220914
(bootloader) git:uefi: MBM-3.0-eqs-01b1dd0a1-dirty-220914
(bootloader) git:abl: MBM-3.0-eqs-3d687e600d1-220914
(bootloader) git:aop: MBM-3.0-eqs-abd531e6-dirty-220914
(bootloader) git:aop_config: MBM-3.0-eqs-abd531e6-dirty-220914
(bootloader) git:tz: MBM-3.0-eqs-896c99b46-dirty-220914
(bootloader) git:hyp: MBM-3.0-eqs-896c99b46-dirty-220914
(bootloader) git:devcfg: MBM-3.0-eqs-896c99b46-dirty-220914
(bootloader) git:keymaster: MBM-3.0-eqs-1a8597eb-220914
(bootloader) git:storsec: MBM-3.0-eqs-1a8597eb-220914
(bootloader) git:uefisecapp: MBM-3.0-eqs-1a8597eb-220914
(bootloader) gitrov: MBM-3.0-eqs-896c99b46-dirty-220914
(bootloader) git:qupfw: MBM-3.0-eqs-f3989a2-220914
(bootloader) git:cpucp: MBM-3.0-eqs-f3989a2-220914
(bootloader) git:shrm: MBM-3.0-eqs-01b1dd0a1-dirty-220914
(bootloader) git:spss: MBM-3.0-eqs-f3989a2-220914
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D53290
(bootloader) snapshot-update-status: none
(bootloader) primary-display[0]: csot_nt37701A_667_curve_1080x2400_dsc_c
(bootloader) primary-display[1]: md_c4
(bootloader) secondary-display: none
(bootloader) fdr-allowed: yes
all: listed above
Finished. Total time: 0.126s
Killuminati91 said:
I dont know if it can really brick your phone when you convert in a clean way and your device is recognized as the original.
But I put the warning there as a lot of people have bricked their devices before by not paying proper attention.
In theory it SHOULD be possible to relock, once you are on the original firmware but I strongly advise against it.
No idea how @cascade128 received a locked converted device though, seems to be possible.
I dont know why you are so radical against unlocking, of course it brings drawbacks but that was always the case since Samsung implemented efuses.
Also: Android Auto and Hey Google do not work on CN and there is a very limited language selection.
@cascade128: could you boot into fastboot / bootloader, create a "fastboot getvar all" dump and send it to me via PM?
I'd really like to take a look at this. Also: Does the Lenovo Rescue assistant recognize your device as xt2241-2?
Click to expand...
Click to collapse
Exactly. Did the person really received a converted and "locked" device?
Moto modders know too well this WILL brick your phone. It's a given fact already
SedyBenoitPeace said:
Well the fact to have a converted device with a locked bootloader it is good for modding!
I guess @cascade128 bought from a vendor that has maybe contacts in Motorola (or is someone from Motorola itself) that has access to stuff that we don't.
It is interesting though...cause I'm holding on on unlocking the bootloader (and then rooting) for warranty purposes and I don't how long I can wait
Cause now my "Unlock OEM" option isn't greyed out anymore
Click to expand...
Click to collapse
I can say the same without any proof whatsoever. Unless...
English Community-Lenovo Community
cascade128 said:
English Community-Lenovo Community
Click to expand...
Click to collapse
Your version is "reteu" which is NOT "retcn" (CN ROM) so your phone is Edge 30 Ultra from the beginning
Nope. Its possible to switch carrier info via fastboot command.
@cascade128: What happens when you try to get an unlock code from the official site with the ORIGINAL imei?
cascade128 said:
English Community-Lenovo Community
Click to expand...
Click to collapse
So now you have to tell us where you bought the phone in order for us to unlock and then relock the bootloader! hahahah
I don't know how much I can resist without unlocking, but I have to say that now without root you can do plenty of things comparing with the past.
ijuanp03 said:
Your version is "reteu" which is NOT "retcn" (CN ROM) so your phone is Edge 30 Ultra from the beginning
Click to expand...
Click to collapse
Killuminati91 said:
Nope. Its possible to switch carrier info via fastboot command.
@cascade128: What happens when you try to get an unlock code from the official site with the ORIGINAL imei?
Click to expand...
Click to collapse
You can't tell him, because that kid doesn't really know, but he has a lot of ideas/claims. He doesn't know anything. I guess that's enough for the last photo i sent to be silent
The original imei numbers of the device need to be rewritten. The person who will do it is in Istanbul, but i am not in Istanbul. I am in a far place. I will go at the first opportunity and write the original imei numbers and unlock the device there. Of course that will cost me another $60.
@SedyBenoitPeace I bought it second hand from one of the users, it was used for 1 week. He had these processes done by a software repairman in Istanbul, for 60$. No need to be surprised, our place is full of inventors
cascade128 said:
You can't tell him, because that kid doesn't really know, but he has a lot of ideas/claims. He doesn't know anything. I guess that's enough for the last photo i sent to be silent
The original imei numbers of the device need to be rewritten. The person who will do it is in Istanbul, but i am not in Istanbul. I am in a far place. I will go at the first opportunity and write the original imei numbers and unlock the device there. Of course that will cost me another $60.
@SedyBenoitPeace I bought it second hand from one of the users, it was used for 1 week. He had these processes done by a software repairman in Istanbul, for 60$. No need to be surprised, our place is full of inventors
Click to expand...
Click to collapse
Well thank you for the insight...for sure this Istanbul's guy is someone from Motorola or at least has some Motorola tools
SedyBenoitPeace said:
Well thank you for the insight...for sure this Istanbul's guy is someone from Motorola or at least has some Motorola tools
Click to expand...
Click to collapse
There are service boxes we call "Box", this friend is Turkish. It's not from Motorola, it's a software developer. I don't know exactly, but he's famous in his business. As i said, there are many such people here. There are some Syrians, even Iranians. They can solve insurmountable problems with the service equipment (different manufacturers) we call this "box", these works are quite famous in our country.
For example very famous this Box: https://sigmakey.com/
That these devices can "force flash" the event. In other words, they can flash firmware without the need for any unlock code or processing.
For example very famous again(update list / writing edge 30 ultra:
ChimeraTool supported models
9,925 supported models of Samsung, Blackberry, Nokia, Sony, HTC, LG, Huawei, Lenovo, Xiaomi, MTK, Vivo, Qualcomm, Generic Android, Oppo, Motorola, Utility, ASUS devices. Find your model!
chimeratool.com
ijuanp03 said:
For those who are planning to buy from Motorola China (CN ROM), do NOT convert to Global ROM! Do NOT buy from an online retailer where the phone has been converted to global ROM.
This is a warning to everyone if you don't want any headache in software support.
Reasons why you should NOT convert to Global ROM:
1. You can NEVER re-lock your bootloader - your phone will get BRICKED if you try to re-lock your bootloader.
2. You can NEVER update your software over-the-air. Do you want to own a phone with an update-less software? Yes, this is NOT possible as there will be an error message everytime you try to update your phone's software.
3. There will be a WARNING MESSAGE ("Your bootloader is unlocked.. etc") every time you restart your phone. Do you want this nasty message to ruin your phone's software?
Why do you NEED to update to Global ROM when in fact, CN ROM OFFICIALLY SUPPORTS Google Play Services.
Just go to Settings > System > Google Play Services
Toggle to ON and you can now install Play Store and use it to download your favorite Google Apps.
NO issues whatsoever. As simple as that.
Click to expand...
Click to collapse
Does this work with all Google services? Such as Google pay, assistant and so on? Debating buying the phone on aliexpress as there's a sale.
Either way, dont buy it until they fix the camera.