Related
I'd like to update my RAZR i to JB by flashing one of the "Homemade Fastboots", but I can't get the unlock status of this device and so I am a bit afraid the flash process might fail halfway in and the device becoming unusable. I have never played around with things like unlocking or rooting before.
The command found on page 9 of "Unlock the Bootloader on Your RAZR i" is not recognized (see below). The adt-bundle I used was just downloaded today.
C:\RAZR\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot oem getvar all
...
(bootloader) unrecognized oem command
(bootloader) List of oem commands:
(bootloader) system
(bootloader) showtext
(bootloader) partitions
(bootloader) partition
(bootloader) md5
(bootloader) fb_mode_set
(bootloader) fb_mode_clear
(bootloader) blank
(bootloader) build-signature
(bootloader) help
(bootloader) unlock
(bootloader) lock
(bootloader) get_unlock_data
(bootloader) pull
(bootloader) push
(bootloader) dump
(bootloader) bosconsole
(bootloader) prod_fuse
(bootloader) nvm
(bootloader) config
(bootloader) dnx_timeout
(bootloader) proxy
FAILED (remote failure)
finished. total time: 0.240s
Btw, I did get an unlock key through the Motorola website, but the unlock command also doesn't work.
C:\RAZR\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot oem unlock ............
...
(bootloader) Not supported on engineer phone!
FAILED (remote failure)
finished. total time: 0.186s
Does anyone know if the Homemade Fastboots can be loaded on this RAZR i without "bricking" it?
Ok, if unsure about flashing the homemade fastboots, is there any other reasonably safe way to flash a regular JB firmware on this RAZR i that currently has obviously a non-standard firmware?
I am somewhat worried to get another "not supported on this phone" or other error message in the middle of the process of loading another firmware, when I've already gotten beyond the point of no return, and then being stuck with a non-working phone.
Iridium8 said:
(bootloader) Not supported on engineer phone!
Click to expand...
Click to collapse
This mean that your phone is a prototype for test purposes, not a retail phone. (Hope you didn't pay for it...)
A have one of this too. Have you manage to update your phone?
Thanks a lot!
evilinheaven said:
This mean that your phone is a prototype for test purposes, not a retail phone. (Hope you didn't pay for it...)
A have one of this too. Have you manage to update your phone?
Thanks a lot!
Click to expand...
Click to collapse
Hi,
Sorry for the late reply, I didn't check back here recently.
Apparently mine is some kind of retail phone, but with a specially built software version. Since I wanted this phone so badly (and I still believe this it the one phone on the market that suits me best), but I didn't have a chance to go to Europe at the time, I bought this from a store in China that had imported it to there. However, to be able to sell this phone in China they are putting these "specially made" software versions with added Chinese UI language on the phone. Since I couldn't get any useful advise in this forum I later contacted those who sold me this phone and they told me I should be able to put any official 4.0.4 version on it (which would then be upgradable OTA), but also warned me that I could then end up with a sim-locked/net-locked RAZR i. So I didn't pursue this any further. I might try it once I've got my next smartphone, but at the moment I am still very happy with my RAZR i.
Hello,
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.
Whenever I try and update click the CHECK FOR UPDATE, it says, " NO UPDATE FOUND " your device is up to date.
The phone is NOT ROOTED as there are no superuser type apps on the phone. Not sure about the bootloader though. Phone runs perfectly fine just this update thing is getting me worried.
Its currently on 4.2.2
Can anybody please tell me why I cant get the OTA or what should I do to update it to KITKAT?
Thank you in advance.
I tried the adb fastboot thing, but it says waiting for device and never shows anything. Does that have anything to do with the phone or the Operating System im using (WINDOWS 8.1)
Please see -> No OTAs on AT&T XT1058
Please do what is listed in Post #5 and post the results. also include what it says for (bootloader) iswarrantyvoid: and who is the carrier you are using it on?
C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version-bootloader: 3070
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Elpida S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Toshiba REV=06 PRV=00 TY
(bootloader) product: ghost
(bootloader) revision-hardware: 0x81B0
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: LXAA1H0042
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: 420E19000C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Reboot to bootloader
(bootloader) ro.build.date: Sat Jul 6 01:51:06
(bootloader) ro.build.id: 13.9.0Q2.X-116-X-17
(bootloader) ro.build.tags: bldacfg,release-keys
(bootloader) ro.build.type: userPAEH\♦☺è
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 8
(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/g
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-
(bootloader) ro.build.fingerprint[2]: g,release-
(bootloader) ro.build.version.full[0]: Blur_Vers
(bootloader) ro.build.version.full[1]: ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.
(bootloader) kernel.version[1]: 699-00155-g0f202
(bootloader) kernel.version[2]: 3lnxdroid79) (gc
(bootloader) kernel.version[3]: google 20120106
(bootloader) kernel.version[4]: C) ) #1 SMP PREE
(bootloader) kernel.version[5]: :04:24 CDT 2013
I am using wataniya on it. Phone and everything works pretty fine. I am just stuck on 4.2.2. Like the member in the thread you pointed out to.
OmMeE said:
I am using TELENOR on it. Phone and everything works pretty fine. I am just stuck on 4.2.2. Like the member in the thread you pointed out to.
Click to expand...
Click to collapse
And like the member in that other thread... you have...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
were the IMEI and SKU really reported as 0's, or did you do that in your post here to keep them hidden?
Btw, if you follow that other thread, I gave a lot of warnings of the phone being in an unknown state, I wasn't sure if it was safe or not to try and flash, do so at your own risk, etc... in the end, the user flashed the Rogers Canada XT1058 rom -> http://www.filefactory.com/file/5z0...4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip using mFastboot, and did a factory reset. It didn't cure the values I'm pointing out which are not standard.. but it did get him to 4.4.4 and was working on his GSM carrier..
If you're up for it, and are willing to take the risk, maybe that will work for you too... and hopefully it doesn't brick your phone.
KidJoe said:
And like the member in that other thread... you have...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
were the IMEI and SKU really reported as 0's, or did you do that in your post here to keep them hidden?
Btw, if you follow that other thread, I gave a lot of warnings of the phone being in an unknown state, I wasn't sure if it was safe or not to try and flash, do so at your own risk, etc... in the end, the user flashed the Rogers Canada XT1058 rom -> http://www.filefactory.com/file/5z0...4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip using mFastboot, and did a factory reset. It didn't cure the values I'm pointing out which are not standard.. but it did get him to 4.4.4 and was working on his GSM carrier..
If you're up for it, and are willing to take the risk, maybe that will work for you too... and hopefully it doesn't brick your phone.
Click to expand...
Click to collapse
I didnt hide anything, just posted as it came on the CMD.
So if I flash to that rogers rom, will I be getting future updates or will I have to flash everytime?
Also, my apologies, but can you point me towards a step by step guide for using mfastboot, as im new to this and running windows 8.1.
OmMeE said:
I didnt hide anything, just posted as it came on the CMD.
So if I flash to that rogers rom, will I be getting future updates or will I have to flash everytime?
Also, my apologies, but can you point me towards a step by step guide for using mfastboot, as im new to this and running windows 8.1.
Click to expand...
Click to collapse
Ok, well, seeing those things things, let me reiterate that your phone is in an "unknown" or at least "unusual" state. Anything you do at this point is risky! So its up to you if you really want to do anything (like flashing) or leave it like it is (since its working).
There is a chance you will not get updates if you are using the XT1058 rom branded for another carrier. (i.e. if you have the ATT XT1058 rom on an XT1058 being used on a different carrier).
As for step by step... you have a few options..
http://mark.cdmaforums.com/MotoX-ReturnToStock.html See the requirements at the top of the page, and then option 5
Or...
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Oh, and I only suggested the Rogers Canada XT1058 rom because it worked for that other user in that other thread, and I THINK it might have less bloat than the ATT XT1058 rom.
And I do suggest you read that entire thread... there are a few good posts in there with info that might help you understand the situation... because this is a weird state.
KidJoe said:
Please see -> No OTAs on AT&T XT1058
Please do what is listed in Post #5 and post the results. also include what it says for (bootloader) iswarrantyvoid: and who is the carrier you are using it on?
Click to expand...
Click to collapse
KidJoe said:
Ok, well, seeing those things things, let me reiterate that your phone is in an "unknown" or at least "unusual" state. Anything you do at this point is risky! So its up to you if you really want to do anything (like flashing) or leave it like it is (since its working).
There is a chance you will not get updates if you are using the XT1058 rom branded for another carrier. (i.e. if you have the ATT XT1058 rom on an XT1058 being used on a different carrier).
As for step by step... you have a few options..
http://mark.cdmaforums.com/MotoX-ReturnToStock.html See the requirements at the top of the page, and then option 5
Or...
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Oh, and I only suggested the Rogers Canada XT1058 rom because it worked for that other user in that other thread, and I THINK it might have less bloat than the ATT XT1058 rom.
And I do suggest you read that entire thread... there are a few good posts in there with info that might help you understand the situation... because this is a weird state.
Click to expand...
Click to collapse
Thank you very much for the reply.. I followed your instructions and I am now on 4.4.4. The same happened exactly, home button not working, active display not working, quick settings could not be reached.. FACTORY RESETED it and its working fine now.
Hi guys,
Today I woke up with myMoto G5Splus (completely stock & never unlocked bootloader) in bootloader mode showing the error "Start up failed: Your device didn't start up successfully. ecc".
Fastboot can see it, ADB can't. No luck with LMVA or RSC Lite. No luck with any fastboot command.
Here you can see fastboot getvar all output.
Code:
C:\Program Files (x86)\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(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: *omitted by me*
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 39694B0200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.099s
From here I can see CID = 0xDEAD, which doesn't sound really reassuring. Any hint? Is my phone gone for good?
Your phone is stuck in "AP Fastboot mode (secure)" right?
I have the same problem! Even my getvar shows cid as 0xDEAD, no IMEI!
I am trying to roam around the XDA forum to find an answer but not luck! (I even asked for assistance yesterday but no one replied!)
daisiesk said:
Your phone is stuck in "AP Fastboot mode (secure)" right?
I have the same problem! Even my getvar shows cid as 0xDEAD, no IMEI!
I am trying to roam around the XDA forum to find an answer but not luck! (I even asked for assistance yesterday but no one replied!)
Click to expand...
Click to collapse
Exactly, without any reason. I am sure that it was still alive at least until 3am (I can see last backup), today at 7am it was "AP Fastboot mode (secure)" and 0xDEAD.
Biz92k said:
Exactly, without any reason. I am sure that it was still alive at least until 3am (I can see last backup), today at 7am it was "AP Fastboot mode (secure)" and 0xDEAD.
Click to expand...
Click to collapse
is your phone a XT1804, too?
Even i tried LMSA (and of course, it did not work), so after that went to show my phone to the Motorola customer service (in the midst of a pandemic!). No luck. Instead of helping me with the phone they started accusing me that I took my to some unofficial service center! This is completely false!
Then tried RSD lite, fastboot, mfastboot but I can't get past fastboot oem fb_mode_set. It says remote failure.
Now, I think we are in same (if not, at least similar) situation here. Annnnd I think I have a bad news about our phone.
In this case, we can, 1) Replace the eMMC/ whole motherboard (or whatever it is.... I have no idea).
2) Buy a new. (But I love my MOTO :crying: )
daisiesk said:
is your phone a XT1804, too?
Even i tried LMSA (and of course, it did not work), so after that went to show my phone to the Motorola customer service (in the midst of a pandemic!). No luck. Instead of helping me with the phone they started accusing me that I took my to some unofficial service center! This is completely false!
Then tried RSD lite, fastboot, mfastboot but I can't get past fastboot oem fb_mode_set. It says remote failure.
Now, I think we are in same (if not, at least similar) situation here. Annnnd I think I have a bad news about our phone.
In this case, we can, 1) Replace the eMMC/ whole motherboard (or whatever it is.... I have no idea).
2) Buy a new. (But I love my MOTO :crying: )
Click to expand...
Click to collapse
Mine is actually a XT1805, but it seems that the issue is exactly the same. I am actually already looking forward to the moto G8 plus because I need a phone in my everyday life, and right now I gave back life to my old Moto G (2013).
Btw, there is a way to at least access the memory? Might be useful to get access to the data stored in my phone (not saved on the SD card).
Biz92k said:
Mine is actually a XT1805, but it seems that the issue is exactly the same. I am actually already looking forward to the moto G8 plus because I need a phone in my everyday life, and right now I gave back life to my old Moto G (2013).
Btw, there is a way to at least access the memory? Might be useful to get access to the data stored in my phone (not saved on the SD card).
Click to expand...
Click to collapse
No offence, you still want to go for Motorola?
And about the data, I don't think it is possible. I think the problem with our phone is that the phone's partitions are corrupted (and, apparently, cannot be formatted).
daisiesk said:
No offence, you still want to go for Motorola?
Click to expand...
Click to collapse
Actually I really like the active display, and in the price tag (around 200€) I didn't found anything that really caught my attention, so I might actually go for the G8 plus. What would be your recommendation? I actually didn't check deeply, I just surfed Amazon a bit.
daisiesk said:
And about the data, I don't think it is possible. I think the problem with our phone is that the phone's partitions are corrupted (and, apparently, cannot be formatted).
Click to expand...
Click to collapse
At this point I think is not even a software problem, but I'm getting the idea that something definitely fried on the inside. Which would probably cost more to repair than to get a new phone
Biz92k said:
Actually I really like the active display, and in the price tag (around 200€) I didn't found anything that really caught my attention, so I might actually go for the G8 plus. What would be your recommendation? I actually didn't check deeply, I just surfed Amazon a bit.
Click to expand...
Click to collapse
I agree with the display as well as its classy look! I always wanted to own a MOTO phone, like from the days of MOTO G4 play. But I went for Xiaomi redmi 1s (I have to use it until I fix or buy a new phone).
Even I stated looking for a new phone. My budget is similar as you and all I can see are Samsung phones of which I am not a fan, TBH! Well Nokia was good, but not in the competition anymore.
You know about Motorola, I heard that.. since it is now owned by Lenovo, the quality of the phones aren't as good as it was before (I think, now, i am starting to believe that). My personal opinion is that I don't want to think about Motorola anymore because this phone has given me a headache!
[At this point I think is not even a software problem, but I'm getting the idea that something definitely fried on the inside. Which would probably cost more to repair than to get a new phone
Click to expand...
Click to collapse
Oh yes, the repair cost! But, I think, once they mess up with the insides of the phone, we cannot guarantee that it'll survive for long. I am afraid that after the repair, it might die without giving me a chance to save my personal data!
Guys,
I have the G7 plus XT19645-3 UK device, never been rooted or messed around with.
I had some issues with bluetooth not working with one particular car, so my neighbour 'upgraded' it to Android 10.
I was not happy with Android 10, so he then tried to revert t back to Android 9, which failed.
Currently, the phone boots, shows the Motorola logo, then the message 'Your device is corrupt, it cannot be trusted and may not work properly', then, it displays 'Verity mode is set to eio'.
I then have to restart it by holding the power button, I can get into fastboot using the volume down and power button, and it is recognised by fastboot devices.
Before I make the situation worse, can anyone show me how to get it back to ANY version of Android so I can use the phone please.
I have tried reading through the various posts on here, but quite frankly I am confused as which to follow.
Any help most gratefully received.
I see 2 options:
First option is to try download and use the Rescue and smart assistant (formerly the lenovo moto smart assistant) to recover the device. It easy to use with an user friendly interface
Second option is since you can boot into fastboot, than you just need to download a rom for the device and flash it. You can download the stock rom from lolinet (Here's the android 9 for reteu devices: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) and then flash it manually via cmd or use the blankflash script thats laying somewhere here in the xda treads for the phone
Hi Teo S, thank you for coming back to my request, I have tried smart assistant, it failed with an error something like 'key information could not be read from your device'.
I then tried using the flashfile.bat script, using the rome you linked to above, and the Android 10 rom from Olinet.
The Android 9 failed, with two errors related to' system_b system_b.img_sparsechunk.0' and 'system_b system_b.img_sparsechunk.1'.
The Android 10 rom flashed successfully as far as I can tell looking at the messages in the cmd window all commands finish with 'OKAY'.
However, when I reboot the device, I still get the Motorola logo, which flashes on and off a few times, then get the same message 'Your device is corrupt, it cannot be trusted and may not work properly', then, it displays 'Verity mode is set to eio'.
So although it looked like it had flashed correctly, something is still not right, can you suggest anything else?
A further bit of info, I left the phone for about 10 minutes with the message 'Verity mode is set to eio' and the Motorola logo, when I came back to it, that screen had gone, and was replaced with a black screen with yellow and red text, essentially it said 'Boot Failed', followed by red text about how to contact customer service and if it is a Verizon device (which is is not), but below that was more yellow text which said 'No Bootable A/B slot', 'failed to boot Linux, falling back to fastboot'
staffstony said:
was not happy with Android 10, so he then tried to revert t back to Android 9, which failed.
Currently, the phone boots, shows the Motorola logo, then the message 'Your device is corrupt, it cannot be trusted and may not work properly', then, it displays 'Verity mode is set to eio'.
Click to expand...
Click to collapse
staffstony said:
Hi Teo S, thank you for coming back to my request, I have tried smart assistant, it failed with an error something like 'key information could not be read from your device'.
I then tried using the flashfile.bat script, using the rome you linked to above, and the Android 10 rom from Olinet.
The Android 9 failed, with two errors related to' system_b system_b.img_sparsechunk.0' and 'system_b system_b.img_sparsechunk.1'.
The Android 10 rom flashed successfully as far as I can tell looking at the messages in the cmd window all commands finish with 'OKAY'.
However, when I reboot the device, I still get the Motorola logo, which flashes on and off a few times, then get the same message 'Your device is corrupt, it cannot be trusted and may not work properly', then, it displays 'Verity mode is set to eio'.
So although it looked like it had flashed correctly, something is still not right, can you suggest anything else?
Click to expand...
Click to collapse
So it sounds like you unlocked the bootloader before doing all of this? Please confirm. Not sure if you could still request unlock code if you don't have it yet.
Also, did you reset the device?
Could you dump all fastboot variables, and post them here ( fastboot getvar all ).
Notice that XDA upgrade scripts for flashing are often missing a step or two, due to them being for older versions. Extract "flashfile.xml" from you current ROM, and check line by line that everything is flashed and erased properly. It must be line for line exact!
I think your phone is totally recoverable, just need to follow the correct steps.
To be honest, my neighbour 'updgraded' my device from Android 9 to 10 so I am not sure if he unlocked the bootloader or not.
I have the unlock code though from Motorola in case it is required.
Here is the output from getvar all, i've replaced the device serial and IMEI with '*'.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-200214
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: WEJP
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: B429986C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***************
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1965-3
(bootloader) carrier_sku: XT1965-3
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 3773
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_reteu_n/lake_n:10/QP
(bootloader) ro.build.fingerprint[1]: WS30.61-21-9/664a:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 10 06:08:41 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9-200214
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-200214
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-200214
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-200214
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
I am unsure exactly which rom I should be looking at the flashfile.xml, Android 9 or 10?
The device is a UK G7 Plus, purchased from a UK national company.
Really apreciate any help you can give, i'm kinda stuck without my phone!!
staffstony said:
...
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
...
(bootloader) sku: XT1965-3
(bootloader) carrier_sku: XT1965-3
...
(bootloader) ro.build.fingerprint[1]: WS30.61-21-9/664a:user/release-key
...
(bootloader) ro.carrier: retgb
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
I am unsure exactly which rom I should be looking at the flashfile.xml, Android 9 or 10?
The device is a UK G7 Plus, purchased from a UK national company.
Really apreciate any help you can give, i'm kinda stuck without my phone!!
Click to expand...
Click to collapse
OK, things seem fairly clear now. It's still locked (iswarrantyvoid: no).
You may want to try first to switch the bootloader slot to a (fastboot --set-active=a). And reboot to fastboot, do getvar all again. Compare which version it is in slot A now, is it still 9 or 10 already. Your version B has some older 10, compared to Lolinet. Also, try Moto recovery software from both slots, just in case. Sounds like you already tried from B, now switch to A and try again. Your locked phone should be detected somehow. That software is exactly for issues like yours!
If neither A/B work, I am not sure if you can flash the full 9 or 10 to the locked device.
Your fastboot says GB channel, XT1965-3, so either of these 2 ROMs could work for you, 9 or 10:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Either zip will have flashfile.xml, so you can try 9 first, then 10. For each version follow its respective flashfile.xml for the exact files. It won't let you flash things that cannot be downgraded, so don't worry about trying it.
Anyway, if you are unable to flash with the locked BL, unlock it, flash 9 or 10, then boot to verity, and relock it if you care.
Update: read up here
https://www.reddit.com/r/AndroidQuestions/comments/in2zga
I say use the official procedures first, do not unlock yet.
In another place, if you google for 'Verity mode is set to eio', it says this:
I didn’t succeed. I returned the customer without repair. I believe it is a memory or processor failure.
Update2: It seems you actually cannot go back to 9, and must stick to 10 to avoid the EIO issue. It checks for roll back, and 9 after 10 is a rollback, which means - it thinks it's been tampered with. So do reload 10 back:
Verifying Boot | Android Open Source Project
source.android.com
bibikalka, thank you for the reply, lots of info for me to digest there.I have just tried to switch to slot a, for some reason that didn't work, this is what I got.
D:\fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.003s
So I guess I have fallen at the first hurdle..
Ok, I have made some progress, I downloaded the RetailGB rom for Android 10 that you linked to, then unzipped it and looked at the flashfile.xml.
I then compared the contents to the flashfile.bat I had downloaded.
They were almost exactly the same except the flashfile.bat was missing this line from flashfile.xml
<step MD5="b3a54937c84fb5f3e7f71fc019c11c78" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
So I modified the flashfile.bat to include the line
mfastboot flash system system.img_sparsechunk.5
And tried again, and it worked perfectly, after rebooting, the phone booted up normally with the Motorola logo and then went through the setting up menus.
I popped my sim back in and it registered on the network
Before I go ahead and re-install all my apps / data, is there any point in rooting it, and if so how do I do that, i'd like to get it in a state where should anything happen again, I can be in a better position to recover it.
Thank you for the help and assistance in getting me back up and running.
staffstony said:
They were almost exactly the same except the flashfile.bat was missing this line from flashfile.xml
<step MD5="b3a54937c84fb5f3e7f71fc019c11c78" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
So I modified the flashfile.bat to include the line
mfastboot flash system system.img_sparsechunk.5
And tried again, and it worked perfectly, after rebooting, the phone booted up normally with the Motorola logo and then went through the setting up menus.
I popped my sim back in and it registered on the network
Before I go ahead and re-install all my apps / data, is there any point in rooting it, and if so how do I do that, i'd like to get it in a state where should anything happen again, I can be in a better position to recover it.
Click to expand...
Click to collapse
OK, so it looks like you were missing a chunk of the /system - no wonder it did not work before ...
Unlock can be useful, or may be a nuisance. Decide for yourself. Is it out of warranty now? If so, you won't lose anything by unlocking. Before unlocking, you'd install all the OS updates that are being offered. It will be more difficult to do it later. With unlock/root you get :
TWRP
Magisk
Titanium Backup
Other ROMs if you fancy those
But some apps seem to refuse to run if they detect a rooted device
Tethering (if you want to bypass the carrier restrictions)
Other little things
If you don't care about any of this, stay locked.
@bibikalka, I think I would like to root the device, mainly so I can use Titanium to back it all up.That said, having read this thread
[RECOVERY] Official TWRP 3.3.1 for Moto G7 Plus [lake]
Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
I am not sure, the info in there is a bit confusing, how simple is it to do?
I have downloaded the relevant TWRP .zip and .img, downloaded the magisk .apk file for the G7 Plus, the device dows not yet have any apps installed, so wiping it is no problem either, there is no data on it that I am not prepred to lose.
The phone is out of warranty anyway, I have the bootloader unlock code from Motorola, so I guess I have everything required, just need a hand hold to actually do the unlock.
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.