Related
I am baffled by my XT1058. I got it from ebay (clearlya mistake), so I don't know its history. The phone works fine with TMobile SIM cards; this should imply that the phone has no SIM locks. However, h2o and AT&T SIM cards ask for a network unlock PIN!
I've tried going through TMobile to get a network unlock PIN, but they say that the phone didn't originate with them (obviously) so they can't provide a PIN. Motorola has told me that the phone should already be SIM unlocked, so no help there.
Anyone have any thoughts on this? Could it be some kind of software issue? (I've tried flashing the stock AT&T sbf; didn't resolve the issue.)
Go through a 3rd party online unlocking company like cell unlocker net. Only costs like $8.99 or something.
I did this for my XT1058 in Canada, purchased at Fido. I'm now using on Bell.
Thanks for the advice.. I'm not very confident that they'll be able to produce a working code, but I've submitted an order to one of the unlocking services.
I bought an unlock code for my rogers 1058 no problem. On telus since day one.
ChadFM said:
Thanks for the advice.. I'm not very confident that they'll be able to produce a working code, but I've submitted an order to one of the unlocking services.
Click to expand...
Click to collapse
If their code has several groups of 8 numbers, read the instructions carefully, e.g., you may be required to enter the 2nd group of 8 numbers and ignore the rest.
I tried an unlocking service "Motorola unlock code All Models/Networks", and they told me that they couldn't unlock it. (I was quickly refunded, thankfully.) Any other thoughts/suggestions..?
Is the bootloader unlocked and what firmware was installed when you received it?
@ChadFM are you sure its an XT1058? Does it have the ATT logo on its back?
Can you see any model number on its back (near the bottom edge, by the little hole)? Its often small and difficult to read.
KidJoe said:
@ChadFM are you sure its an XT1058? Does it have the ATT logo on its back?
Can you see any model number on its back (near the bottom edge, by the little hole)? Its often small and difficult to read.
Click to expand...
Click to collapse
The case says it's an XT1058, yeah - no AT&T branding, FCC ID IHDT56PA1, assembled in the USA.
There is no XT-1058 that should be locked to t-mobile, well there is no Moto X period that should be locked to t-mobile. I am wondering if it is really even a XT-1058 or if it has had the back cover swapped out. For sure it is an odd ball phone that someone messed with or was some sort of demo/sample phone early in its life.
Steve-x said:
There is no XT-1058 that should be locked to t-mobile, well there is no Moto X period that should be locked to t-mobile. I am wondering if it is really even a XT-1058 or if it has had the back cover swapped out. For sure it is an odd ball phone that someone messed with or was some sort of demo/sample phone early in its life.
Click to expand...
Click to collapse
It's crossed my mind that the back might have been swapped out. To make matters more complicated, the phone was running an XT1053 custom rom when I got it.. Interesting idea that it might have been some kind of demo/sample.
Hmm, Any chance it is maybe some CDMA(Verizon, Sprint, or a smaller regional carrier) variant of the phone that happens to allow t-mobile but not AT&T and the seller slapped some other rom on to it along with a new back cover.
You might want to try the following command at the fastboot screen "fastboot getvar all" which will give detailed information regarding the hardware in the phone. Post the output if you can, removing all of your unique information. I'd really like to know which radio it has installed - that should tell us the actual hardware model you have.
Steve-x said:
Hmm, Any chance it is maybe some CDMA(Verizon, Sprint, or a smaller regional carrier) variant of the phone that happens to allow t-mobile but not AT&T and the seller slapped some other rom on to it along with a new back cover.
You might want to try the following command at the fastboot screen "fastboot getvar all" which will give detailed information regarding the hardware in the phone. Post the output if you can, removing all of your unique information. I'd really like to know which radio it has installed - that should tell us the actual hardware model you have.
Click to expand...
Click to collapse
Now that would be very interesting, if this is actually a CDMA variant. I've combed through the getvar info before, when previously trying to figure out if the phone's actually an XT1058 - I didn't notice any interesting radio info, but I wasn't looking for it specifically. I'll post a dump of that info later this evening!
Here's the getvar output; note that I've got an XT1053 rom running currently. (I get the same SIM behavior on the stock AT&T rom.)
Do the radio/hwrev codes here have any significance?
(bootloader) version-bootloader: 30B4
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x82B0
(bootloader) radio: 0x6
(bootloader) secure: yes
(bootloader) mid: 026b
(bootloader) serialno: LXTU2K0005
(bootloader) qe: qe 1/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) uid: <snip>
(bootloader) imei: <snip>
(bootloader) meid:
(bootloader) sku: XT1053
(bootloader) cid: 0x00
(bootloader) iccid:
(bootloader) date: 06-15-2013
(bootloader) cust_md5:
(bootloader) reason: Reboot to bootloader
(bootloader) ro.build.date: Fri Jan 10 22:11:02 CST 2014
(bootloader) ro.build.id: KXA20.16-1.25
(bootloader) ro.build.tags: release-keys
(bootloader) ro.build.type: user
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 31
(bootloader) ro.build.version.release: 4.4.2
(bootloader) ro.mot.build.customerid: Retail
(bootloader) ro.product.name: ghost_retail
(bootloader) ro.build.fingerprint[0]: motorola/ghost_retail/ghost:4.4.
(bootloader) ro.build.fingerprint[1]: 2/KXA20.16-1.25/31:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.161.44.25.ghost_row
(bootloader) ro.build.version.full[1]: .Retail.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-g8ee710a (h
(bootloader) kernel.version[1]: [email protected]) (gcc version
(bootloader) kernel.version[2]: 4.7 (GCC) ) #1 SMP PREEMPT Fri J
(bootloader) kernel.version[3]: an 10 22:24:43 CST 2014
This line should indicate which version it is - (bootloader) radio: 0x6
I am not at home to verify but am 99% sure that an XT-1058 will report radio 0x1.
I am also pretty sure that the XT-1053 has radio 0x6 - hopefully someone can verify.
Steve-x said:
This line should indicate which version it is - (bootloader) radio: 0x6
I am not at home to verify but am 99% sure that an XT-1058 will report radio 0x1.
I am also pretty sure that the XT-1053 has radio 0x6 - hopefully someone can verify.
Click to expand...
Click to collapse
Another thread seems to support those values: http://forum.xda-developers.com/moto-x/general/moto-x-cyanognmod-11-nightlies-to-start-t2627812
If there is a definite correlation between that value and the model number (the value is HW based), then this situation is even more complicated.. Does a sim-locked XT1053 even exist?
ChadFM said:
Here's the getvar output; note that I've got an XT1053 rom running currently. (I get the same SIM behavior on the stock AT&T rom.)
Do the radio/hwrev codes here have any significance?
<SNIP>
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) uid: <snip>
(bootloader) imei: <snip>
(bootloader) meid:
(bootloader) sku: XT1053
<SNIP>
Click to expand...
Click to collapse
So it appears its an XT1053 and has its bootloader unlocked.
The iswarrantyvoid being yes, makes me question if its the "unlocked GSM (comes with T-Mobile SIM)" version, or does the GSM Dev Edition say that too?
Taking a step back, are these getvar all values hardware based, or could they have been modified by flashing different firmwares..?
ChadFM said:
Taking a step back, are these getvar all values hardware based, or could they have been modified by flashing different firmwares..?
Click to expand...
Click to collapse
it is my understanding that the uid, imei, meid, sku, cid, iccid, and a few others are hardware based. Those that start with ro.build, and kernel are based on the rom flashed on the device.
In the OP you mention you tried flashing the stock XT1058 SBF... what was the last SBF you flashed to this phone? If it was the ATT XT1058 sbf, and the phone still reports XT1053 for SKU, then at least that field is hardware based.
And to answer your earlier question, No I haven't seen an XT1053 that is SIM-Locked. Moto sells the XT1053 as the "GSM Unlocked (ships with T-Mobile SIM)" version, and the GSM Dev Edition, both are sim unlocked out of the box.
I did last flash an AT&T XT1058 SBF.. so you're right, that supports that at least some of the fields are HW-based.
Maybe there's some international carrier that locks the XT1053, and it just happens to work on TMobile?
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.
I recently bought a used Moto X AT&T Version from a retailer (it's AT&T, back printed with its logo). It's functioning normally. GSM Network is recognized. I was also able to take an OTA upgrade to 4.4.4 (it was previously 4.4.2). Everything is working up to the mark.
Well, I rebooted my phone in Fastboot Mode (just for curiosity) and was completely shocked when I read Device is Unlocked: Status Code 1 printed on the screen. But, I know this variant can't be unlocked and secondly, I have never read about Status Code: 1. My Developer Edition prints Status Code: 3 which is obviously unlocked. Amazed of what I read, I got worried! So I issued fastboot getvar all command to the phone.
The result variables got me more worried! I have added them below for reference:
(bootloader) version-bootloader: 30B7
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Elpida S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x6
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: LXXXXXXXXXX
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: XXF8F3030C000100000000000000
(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: Wed Jun 25 00:10:28 PDT 2014
(bootloader) ro.build.id: KXA21.12-L1.26
(bootloader) ro.build.tags: bldacfg,release-keys
(bootloader) ro.build.type: user
(bootloader) ro.build.user: dbbuild
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 26
(bootloader) ro.build.version.release: 4.4.4
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.4.4/K
(bootloader) ro.build.fingerprint[1]: XA21.12-L1.26/26:user/bldacfg,re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.212.44.26.ghost_att
(bootloader) ro.build.version.full[1]: .ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-gb444bf1-00
(bootloader) kernel.version[1]: 004-g6b785f7 ([email protected]
(bootloader) kernel.version[2]: id14) (gcc version 4.7 (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed Jun 25 00:21:2
(bootloader) kernel.version[4]: 1 PDT 2014
Click to expand...
Click to collapse
1. Why the IMEI is being reported as 00000000000..... If I go to System>About>Status, IMEI is being correctly reported. Dialing *#06# also displays the IMEI correctly.
2. Why CID is 0xdead? From my knowledge CID is always a hex value. And what this CID 0xdead implies?
3. Bootloader reports unlocking is not supported. My friend also has a Moto X AT&T. His reports 'no' and also correctly shows IMEI and CID. Why this?
4. Does this means my Moto X is unlocked and I can flash any custom recovery on it? As Device reports it's unlocked.
5. Stock Recovery doesn't seem to work as it always says 'No Command'. Is it safe to flash the stock recovery?
From all this, I have only come to the conclusion that the device was tampered. But how such happened?
Thanks to everyone, who replies!
mfbcool said:
Device is Unlocked: Status Code 1 printed on the screen.
Click to expand...
Click to collapse
That is the factory state.
In bootloader mode do you see AP Fastboot Flash Mode (S) or (NS)?
---------- Post added at 08:23 AM ---------- Previous post was at 08:21 AM ----------
mfbcool said:
From all this, I have only come to the conclusion that the device was tampered. But how such happened?
Thanks to everyone, who replies!
Click to expand...
Click to collapse
Maybe it was a factory device and someone cloned an IMEI onto it - that might be what happened here.
---------- Post added at 08:30 AM ---------- Previous post was at 08:23 AM ----------
mfbcool said:
4. Does this means my Moto X is unlocked and I can flash any custom recovery on it? As Device reports it's unlocked.
Click to expand...
Click to collapse
I think it does. Try flashing TWRP and you will see.
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
mfbcool said:
5. Stock Recovery doesn't seem to work as it always says 'No Command'. Is it safe to flash the stock recovery?
Click to expand...
Click to collapse
It is always safe to flash stock, signed files as long as you have the right version for your device.
Thanks JulesJam for the reply!
AP Fastboot Flash Mode is NS (please see picture in the attachment)
I'll try flashing TWRP tonight. Hope everything goes well! If bootloader locked I won't be even able to pass the flashing step, right? (as pre flash signature validation will fail)
Flashed TWRP 2.8.6.0 successfully! Everything is working like a charm.
Flashed Carbon ROM 5.1.1. Working flawlessly!
Where do all those factory devices suddenly come from?
Exactly my question!
dagoban said:
Where do all those factory devices suddenly come from?
Click to expand...
Click to collapse
I think such phones are actually being secretly stolen from the factory or being leeched out secretly. How could it be possible that Motorola sells a bootloader factory unlocked smartphone?
FYI, there are several old threads covering phones in this state.
The oldest example:
http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
mfbcool said:
Thanks JulesJam for the reply!
AP Fastboot Flash Mode is NS (please see picture in the attachment)
I'll try flashing TWRP tonight. Hope everything goes well! If bootloader locked I won't be even able to pass the flashing step, right? (as pre flash signature validation will fail)
Flashed TWRP 2.8.6.0 successfully! Everything is working like a charm.
Flashed Carbon ROM 5.1.1. Working flawlessly!
Click to expand...
Click to collapse
Flash away dude!!! Just keep in mind that your device is very unsecure in that if you lose it, anyone with any knowledge about these things will be able to do anything they want with that device just like you are able to. They will be able to circumvent any security on the device b/c the fastboot is not secure.
---------- Post added at 07:15 PM ---------- Previous post was at 07:13 PM ----------
mfbcool said:
I think such phones are actually being secretly stolen from the factory or being leeched out secretly. How could it be possible that Motorola sells a bootloader factory unlocked smartphone?
Click to expand...
Click to collapse
They definitely weren't supposed to be sold to retail customers.
These devices didn't have IMEIs and so someone had to put an IMEI on the device, which is shady depending on how the IMEI was obtained.
just received a lot of defected 2013 x's and one is like i have never seen, it has no branding on bat cover and bootloader is unlocked with 4.2.2 os, it has a very weird home screen with a pic of file folder in right bottom home screen with colored blocks on it, when taped tinnier icons appear, has a test cam, fr on ,settings...., it has no google apps or services with some apps i cant remember ever seeing on a x.
baseband version
msm8960pro_bp_2323.010.71.00r
kernel version
3.4.42-xline-eng-g9c632ef-00003-g99060a2
[email protected] #1
system version
unknown
build number
factory_ghost-userdebug 4.2.2
13.9.0q2.x-118_ghost-gnpo-6 8 test-keys
imei is listed as (0),
in ap fastboot we got, mode (ns)
30.50
was hoping maybe i got some thing that can be useful to one of our respected developers if not what frimware should i try to install?
In the bootloader if you type:
fastboot getvar all
Click to expand...
Click to collapse
You might be able to get a bit more info.
killsforpie said:
In the bootloader if you type:
You might be able to get a bit more info.
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: 3050
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Elpida 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: TA17607A81
(bootloader) qe:
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: 6D3830040C000100000000000000
(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: Mon Jul 1 16:34:20 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X-118-GHOST_GNPO-6
(bootloader) ro.build.tags: release-keys
(bootloader) ro.build.type: userdebug
(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:
(bootloader) ro.product.name: factory_ghost
(bootloader) ro.build.fingerprint[0]: motorola/factory_ghost/ghost:4.2
(bootloader) ro.build.fingerprint[1]: .2/13.9.0Q2.X-118-GHOST_GNPO-6/8
(bootloader) ro.build.fingerprint[2]: :userdebug/release-keys
(bootloader) ro.build.version.full:
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-eng-g
(bootloader) kernel.version[1]: 9c632ef-00003-g99060a2 (hudsoncm
(bootloader) kernel.version[2]: @il93lnxdroid50) (gcc version 4.
(bootloader) kernel.version[3]: 6.x-google 20120106 (prerelease)
(bootloader) kernel.version[4]: (GCC) ) #1 SMP PREEMPT Mon Jul
(bootloader) kernel.version[5]: 1 16:57:14 CDT 2013
all:
finished. total time: 0.149s
this device seams to be some test or prototype device, maybe valuable to the right dev, it has no cam app but does have a test cam app also missing a lot of stock apps, app called( rf on) which seams to be some testing app, my pc recognized it as factory_ghost and not model number ,
Where did you get it man.
adity said:
Where did you get it man.
Click to expand...
Click to collapse
it was in a large lot of phones i got at an auction, i have no history, it has to be some sort of test device or prototype? did i mention in first post that bootloader is unlocked? what do you think?
also missing some settings compared to 444
touchless control
motorola connect
motorola privacy
motorola device id
about phone has no (system update)
hugh a said:
just received a lot of defected 2013 x's and one is like i have never seen, it has no branding on bat cover and bootloader is unlocked with 4.2.2 os,
Click to expand...
Click to collapse
In bootloader mode, go to barcodes - it should tell you the model number.
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
hugh a said:
did i mention in first post that bootloader is unlocked? what do you think?
Click to expand...
Click to collapse
Is the unlocked bootloader status code 3 or status code 1?
---------- Post added at 08:43 AM ---------- Previous post was at 08:22 AM ----------
hugh a said:
ro.product.name: factory_ghost
Click to expand...
Click to collapse
My XT1060 retail Verizon model and XT1060 Dev Ed both say:
ro.product.name: ghost_verizon
So what you have likely is a factory model. It should be unlocked status code 1, which is how they are manufactured and then they are locked in the factory and become status code 0.
Can you take a pic of the screen in bootloader mode?
Have you tried a factory reset to see if you get the standard settings + launcher back?
JulesJam said:
In bootloader mode, go to barcodes - it should tell you the model number.
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
Is the unlocked bootloader status code 3 or status code 1?
---------- Post added at 08:43 AM ---------- Previous post was at 08:22 AM ----------
My XT1060 retail Verizon model and XT1060 Dev Ed both say:
ro.product.name: ghost_verizon
So what you have likely is a factory model. It should be unlocked status code 1, which is how they are manufactured and then they are locked in the factory and become status code 0.
Can you take a pic of the screen in bootloader mode?
Click to expand...
Click to collapse
status code 1
dagoban said:
Have you tried a factory reset to see if you get the standard settings + launcher back?
Click to expand...
Click to collapse
yes, no change
hugh a said:
status code 1
Click to expand...
Click to collapse
That's definitely a factory device. Status code 1 unlocked is how they are in the factory before they get locked and shipped out as status code 0 locked.
Also, I believe that AP Fastboot Flash Mode (NS) the NS means not secure unlike on the production models where it is S for secure. I am not sure what this means exactly but I think I read it means you could get fastboot to flash a custom bootloader. Not sure.
Then the bootloader has an additional option - Switch console. Not sure what that means.
I would think a dev would be interested in the device - jcase or beaups in particular since they were the ones to have rooted and unlocked Moto X's in the past.
Obviously the device can never operate as a phone b/c of the lack of an IMEI number - you could clone one but that is illegal.
JulesJam said:
That's definitely a factory device. Status code 1 unlocked is how they are in the factory before they get locked and shipped out as status code 0 locked.
Also, I believe that AP Fastboot Flash Mode (NS) the NS means not secure unlike on the production models where it is S for secure. I am not sure what this means exactly but I think I read it means you could get fastboot to flash a custom bootloader. Not sure.
Then the bootloader has an additional option - Switch console. Not sure what that means.
I would think a dev would be interested in the device - jcase or beaups in particular since they were the ones to have rooted and unlocked Moto X's in the past.
Obviously the device can never operate as a phone b/c of the lack of an IMEI number - you could clone one but that is illegal.
Click to expand...
Click to collapse
im very interested in donating the board to the right dev could you please put the word out, this was the main purpose of me starting this thread, you are right the more i thought about it what good would it be to install os with out imei and i for sure dont even want to go there!
so jcase or beaups if you are interested pm me.
hugh a said:
im very interested in donating the board to the right dev could you please put the word out, this was the main purpose of me starting this thread, you are right the more i thought about it what good would it be to install os with out imei and i for sure dont even want to go there!
so jcase or beaups if you are interested pm me.
Click to expand...
Click to collapse
You have to put an @ in front of their names like this to get them notified
@jcase @beaups - @hugh a has a factory moto x 2013 that he would like to donate to a dev if you would like it as a test device. It is status code 1 unlocked with fastboot flash mode (NS) as shown in the pics this thread. Please PM him if you are interested.
The bootloader is version 30.50, which I have never seen before. I think the earliest bootloader released for sale was the 30.70. And this factory device has an additional option in the bootloader menu - Switch Console. It doesn't have an IMEI. He bought it in an auction of a batch of moto x's.
JulesJam said:
You have to put an @ in front of their names like this to get them notified
@jcase @beaups - @hugh a has a factory moto x 2013 that he would like to donate to a dev if you would like it as a test device. It is status code 1 unlocked with fastboot flash mode (NS) as shown in the pics this thread. Please PM him if you are interested.
The bootloader is version 30.50, which I have never seen before. I think the earliest bootloader released for sale was the 30.70. And this factory device has an additional option in the bootloader menu - Switch Console. It doesn't have an IMEI. He bought it in an auction of a batch of moto x's.
Click to expand...
Click to collapse
JulesJam :good:
I cannot find the stock rom for the Brazilian retail variant
Model: XT2087-1
Hardware Version: pvt
Software Channel: retbr
S/N on the box: PAKL0000BR
Actual build number: QPA30.19-Q3-32-39-1
Plus I c a few stock roms that says
AB Update Disabled
But according to fastboot, my device has 2 slots....
I'd like to know where can we find any of the stock rom versions.
I'm still postponing buying this device because I want to be sure I can get the stock rom to root it. No root is a deal breaker for me.
cesardemi said:
I'd like to know where can we find any of the stock rom versions.
I'm still postponing buying this device because I want to be sure I can get the stock rom to root it. No root is a deal breaker for me.
Click to expand...
Click to collapse
I c a lot of versions on lolinet, but I don't think they have the RETBR, or Retail Brazilian variant
As far as I know, since around the time of the g5 lineup all stock images for lenovo/moto phones have been available through their official app, lenovo moto smart assistant - https://support.lenovo.com/us/en/downloads/ds101291
I've used it before to get signed system images for my g5 plus, I'll be getting the g9 plus in a day or two and will post if I could fetch images for it.
MrZeroXD said:
I cannot find the stock rom for the Brazilian variant
Model: XT2087-1
Hardware Version: pvt
Software Channel: retbr
Click to expand...
Click to collapse
Possible sources for signed factory images:
- LMSA tool provided by Lenovo (mentioned above)
- https://mirrors.lolinet.com/firmware/moto/
(see readme.html at end of list for code name <=> device model)
- https://t.me/s/motoupdatestracker
(use search function: XT19xx or XT20xx)
- https://motoota.lolinet.com/guid.php
=> page only provides a download of available ota.zip (not full firmware images!!). You need to fill these fields:
1. OTA SHA1 (ro.mot.build.guid) = output of
Code:
getprop ro.mot.build.guid
- or -
see /oem/oem.prop
2. Carrier (ro.carrier) = output of
Code:
getprop ro.carrier
that's your software channel e.g. retus,retin and so on
WoKoschekk said:
Possible sources for signed factory images:
- LMSA tool provided by Lenovo (mentioned above)
- https://mirrors.lolinet.com/firmware/moto/
(see readme.html at end of list for code name <=> device model)
- https://t.me/s/motoupdatestracker
(use search function: XT19xx or XT20xx)
- https://motoota.lolinet.com/guid.php
=> page only provides a download of available ota.zip (not full firmware images!!). You need to fill these fields:
1. OTA SHA1 (ro.mot.build.guid) = output of
Code:
getprop ro.mot.build.guid
- or -
see /oem/oem.prop
2. Carrier (ro.carrier) = output of
Code:
getprop ro.carrier
that's your software channel e.g. retus,retin and so on
Click to expand...
Click to collapse
Thanks a lot, I'll check if I find it, so OTA is not the full firmware? What comes with an OTA file?
MrZeroXD said:
Thanks a lot, I'll check if I find it, so OTA is not the full firmware? What comes with an OTA file?
Click to expand...
Click to collapse
An OTA brings you only the updated files as a patch for the partition they belong. That's the same file you have to download when receiving an update notification. So, it has only a size of 100-200MB.
This method might be interesting for only a few users or to check for available updates.
---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------
But the LMSA tool is really recommended. You'll find a detailed documentation as a download directly on the website.
---------- Post added at 11:23 PM ---------- Previous post was at 11:16 PM ----------
The very last chance is a Google search. Search for your build no. e.g. »QPA30.19-Q3-32-39-1«
WoKoschekk said:
An OTA brings you only the updated files as a patch for the partition they belong. That's the same file you have to download when receiving an update notification. So, it has only a size of 100-200MB.
This method might be interesting for only a few users or to check for available updates.
---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------
But the LMSA tool is really recommended. You'll find a detailed documentation as a download directly on the website.
---------- Post added at 11:23 PM ---------- Previous post was at 11:16 PM ----------
The very last chance is a Google search. Search for your build no. e.g. »QPA30.19-Q3-32-39-1«
Click to expand...
Click to collapse
So, after all the research I did, I ended up using LMSA, and the image that it "maked" me download is for the US users apparently, cuz my carrier is RETBR, and the one from the tool is RETAIL, by Googling, I found a few websites that appears to have the correct image for my device, but they're all paid. Also, I still learning English, not a native lol.
MrZeroXD said:
So, after all the research I did, I ended up using LMSA, and the image that it "maked" me download is for the US users apparently, cuz my carrier is RETBR, and the one from the tool is RETAIL, by Googling, I found a few websites that appears to have the correct image for my device, but they're all paid. Also, I still learning English, not a native lol.
Click to expand...
Click to collapse
Code:
fastboot getvar all
use this command and post the output message here
WoKoschekk said:
Code:
fastboot getvar all
use this command and post the output message here
Click to expand...
Click to collapse
Here's all of the output, I masked a few things cuz I'm scared lol, If u need, PM me:
Code:
[email protected] ~> fastboot getvar all 1
< waiting for any device >
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-odessa_retail-7326ad2e6a-200922
(bootloader) product: odessa
(bootloader) board: odessa
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRLA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM5V7001DM-B621 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 06 10 12
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: XXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: XXXXXX
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: XXXXXXXXXXXXXXXXX
(bootloader) imei2: XXXXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 09-16-2020
(bootloader) sku: XT2087-1
(bootloader) carrier_sku: XT2087-1
(bootloader) battid: SB18C80753
(bootloader) battery-voltage: 4126
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/odessa_retail/odessa:10/Q
(bootloader) ro.build.fingerprint[1]: PA30.19-Q3-32-39-1/5ca099:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.qcom: LA.UM.8.9.r1-09300-SM6xx.0
(bootloader) version-baseband: M7150_19.24.04.62R ODESSA_BRLADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Tue Sep 22 10:
(bootloader) kernel.version[3]: 56:34 CDT 2020
(bootloader) git:xbl: MBM-3.0-odessa_retail-ad2505258-200922
(bootloader) git:xbl_config: MBM-3.0-odessa_retail-ad2505258-200922
(bootloader) git:aop: MBM-3.0-odessa_retail-f7b05a34-200922
(bootloader) git:tz: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) git:hyp: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) git:devcfg: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) git:cmnlib: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) git:cmnlib64: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) git:keymaster: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) git:storsec: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) git:prov: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) git:abl: MBM-3.0-odessa_retail-7326ad2e6a-200922
(bootloader) git:uefisecapp: MBM-3.0-odessa_retail-15dea13a1-200922
(bootloader) frp-state: protected (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C82118
all: listed above
finished. total time: 0.039s
Why do you need a stock ROM? Your bootloader is locked and you should be able to receive and install updates via OTA.
This is your fingerprint:
Code:
motorola/odessa_retail/odessa:10/QPA30.19-Q3-32-39-1/5ca099:user/release-keys
It also shows <odessa_retail> but it's a <retbr> version. Maybe the LMSA tool downloaded the correct ROM after all...
WoKoschekk said:
Why do you need a stock ROM? Your bootloader is locked and you should be able to receive and install updates via OTA.
This is your fingerprint:
Code:
motorola/odessa_retail/odessa:10/QPA30.19-Q3-32-39-1/5ca099:user/release-keys
It also shows <odessa_retail> but it's a <retbr> version. Maybe the LMSA tool downloaded the correct ROM after all...
Click to expand...
Click to collapse
I need the stock rom to root my device ( patching the boot.img ) that way I'll need the stock, cuz I don't know if I'll stay rooted or revert it in case something goes wrong, u know
I'm sure the tool provides the correct ROM matching with your device.
Have a look at this:
BUILD REQUEST INFO:
SW Version: evert-user 9 PPWS29.116-20-23 3dc61 release-keysM660_30.77.01.101R
Modem Version: M660_30.77.01.101R
FSG Version: FSG-660-05.93
MBM Version: MBM-3.0-evert_retail-4149b81ab-200430
Build Fingerprint: motorola/evert/evert:9/PPWS29.116-20-23/3dc61:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 29.381.32.evert.retail.en.US
Model Number: moto g(6) plus
Android Version: 9
Build Id: PPWS29.116-20-23
SW Display Build ID: PPWS29.116-20-23
Build Date: Thu Apr 30 14:00:08 CDT 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.29.381.32.evert.retail.en.US
Version when read from CPV: evert-user 9 PPWS29.116-20-23 3dc61 release-keys
AB Update Enabled: True
Full Treble Enabled: True
This is the info text from my stock ROM .zip for Moto G6+, reteu
As long as the ROM matches with the last digit of your SKU (XT2087-1) you should have no problems. This digit shows you to what channel your ROM belongs.
WoKoschekk said:
I'm sure the tool provides the correct ROM matching with your device.
Have a look at this:
BUILD REQUEST INFO:
SW Version: evert-user 9 PPWS29.116-20-23 3dc61 release-keysM660_30.77.01.101R
Modem Version: M660_30.77.01.101R
FSG Version: FSG-660-05.93
MBM Version: MBM-3.0-evert_retail-4149b81ab-200430
Build Fingerprint: motorola/evert/evert:9/PPWS29.116-20-23/3dc61:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 29.381.32.evert.retail.en.US
Model Number: moto g(6) plus
Android Version: 9
Build Id: PPWS29.116-20-23
SW Display Build ID: PPWS29.116-20-23
Build Date: Thu Apr 30 14:00:08 CDT 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.29.381.32.evert.retail.en.US
Version when read from CPV: evert-user 9 PPWS29.116-20-23 3dc61 release-keys
AB Update Enabled: True
Full Treble Enabled: True
This is the info text from my stock ROM .zip for Moto G6+, reteu
As long as the ROM matches with the last digit of your SKU (XT2087-1) you should have no problems. This digit shows you to what channel your ROM belongs.
Click to expand...
Click to collapse
Thanks, but I c a few weird things, like the following, take a look at the AB Update/Full Trebble:
BUILD REQUEST INFO:
SW Version: odessa_retail-user 10 QPA30.19-Q3-32-39-1 5ca099 release-keysM7150_19.24.04.62R
Modem Version: M7150_19.24.04.62R
FSG Version: FSG-6150-07.51
MBM Version: MBM-3.0-odessa_retail-ad2505258-200922
Build Fingerprint: motorola/odessa_retail/odessa:10/QPA30.19-Q3-32-39-1/5ca099:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.61.1.odessa_retail.retail.en.US
Model Number: moto g(9) plus
Android Version: 10
Build Id: QPA30.19-Q3-32-39-1
SW Display Build ID: QPA30.19-Q3-32-39-1
Build Date: Tue Sep 22 09:34:58 CDT 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.30.61.1.odessa_retail.retail.en.US
Version when read from CPV: odessa_retail-user 10 QPA30.19-Q3-32-39-1 5ca099 release-keys
AB Update Enabled: False
Full Treble Enabled: False
Extracted from this file ( ODESSA_RETAIL_QPA30.19-Q3-32-39-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt ) inside the stock rom downloaded from LMSA.
And when I install Treble Check on my phone, I c that it supports A/B updates plus Treble, will I lose this if I flash this stock?
MrZeroXD said:
Thanks, but I c a few weird things, like the following, take a look at the AB Update/Full Trebble:
BUILD REQUEST INFO:
SW Version: odessa_retail-user 10 QPA30.19-Q3-32-39-1 5ca099 release-keysM7150_19.24.04.62R
Modem Version: M7150_19.24.04.62R
FSG Version: FSG-6150-07.51
MBM Version: MBM-3.0-odessa_retail-ad2505258-200922
Build Fingerprint: motorola/odessa_retail/odessa:10/QPA30.19-Q3-32-39-1/5ca099:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.61.1.odessa_retail.retail.en.US
Model Number: moto g(9) plus
Android Version: 10
Build Id: QPA30.19-Q3-32-39-1
SW Display Build ID: QPA30.19-Q3-32-39-1
Build Date: Tue Sep 22 09:34:58 CDT 2020
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.30.61.1.odessa_retail.retail.en.US
Version when read from CPV: odessa_retail-user 10 QPA30.19-Q3-32-39-1 5ca099 release-keys
AB Update Enabled: False
Full Treble Enabled: False
Extracted from this file ( ODESSA_RETAIL_QPA30.19-Q3-32-39-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt ) inside the stock rom downloaded from LMSA.
And when I install Treble Check on my phone, I c that it supports A/B updates plus Treble, will I lose this if I flash this stock?
Click to expand...
Click to collapse
What images are inside the .zip? Do you have a system_other.img or a oem_other.img? Those get flashed on the slot _b partition.
---------- Post added at 07:20 PM ---------- Previous post was at 07:17 PM ----------
treble = you have a vendor partition (vendor.img) and a system partition (system.img). Non-treble would mean system partition includes a vendor directory. This is for old Android versions.
MrZeroXD said:
I c a lot of versions on lolinet, but I don't think they have the Brazilian variant
Click to expand...
Click to collapse
Just to confirm, this is the correct section, right? The "Odessa" ones: https://mirrors.lolinet.com/firmware/moto/odessa/official
I think there are a couple from Brazil in there (TIMBR, AMXBR).
cesardemi said:
Just to confirm, this is the correct section, right? The "Odessa" ones: https://mirrors.lolinet.com/firmware/moto/odessa/official
I think there are a couple from Brazil in there (TIMBR, AMXBR).
Click to expand...
Click to collapse
TIMBR=TIM (Telecom Italia)
AMXBR=Claro (America Movil)
All for branded devices only. Devices without branding need RETBR (Retail Brasil).
cesardemi said:
Just to confirm, this is the correct section, right? The "Odessa" ones: https://mirrors.lolinet.com/firmware/moto/odessa/official
I think there are a couple from Brazil in there (TIMBR, AMXBR).
Click to expand...
Click to collapse
Yeah, I was using this one, and yep, here in brazil we have a carrier called Tim, but I never heard about AMX, plus my phone is not linked with a carrier, I can use any sim card I want basically
Edit: AMX is for Claro, and here we have that
MrZeroXD said:
Yeah, I was using this one, and yep, here in brazil we have a carrier called Tim, but I never heard about AMX, plus my phone is not linked with a carrier, I can use any sim card I want basically
Edit: AMX is for Claro, and here we have that
Click to expand...
Click to collapse
Version QPA30.19-Q3-32-39-1 is the initial build for Moto G9 plus and that's the reason why you see this text in the info.xml
Code:
AB Update Enabled: False
Full Treble Enabled: False
You could see this in every build no matter for what software channel they are.
You told me:
MrZeroXD said:
I need the stock rom to root my device ( patching the boot.img ) that way I'll need the stock, cuz I don't know if I'll stay rooted or revert it in case something goes wrong, u know
Click to expand...
Click to collapse
You should take the boot.img downloaded by LMSA tool and patch it with Magisk. Then you just try to boot it. Don't flash it, boot it!
Code:
fastboot boot magisk_patched.img
This command won't change anything on your stock boot partition. If it fails, you only have to reboot your phone.
But if not and your phone boots up with Magisk installed, then everything is fine with that build you downloaded with the tool.
You also have the option to grep your stock boot.img because you just booted a patched image and did not flash it.
There's nothing to loose. You should try it.
WoKoschekk said:
Version QPA30.19-Q3-32-39-1 is the initial build for Moto G9 plus and that's the reason why you see this text in the info.xml
Code:
AB Update Enabled: False
Full Treble Enabled: False
You could see this in every build no matter for what software channel they are.
You told me:
You should take the boot.img downloaded by LMSA tool and patch it with Magisk. Then you just try to boot it. Don't flash it, boot it!
Code:
fastboot boot magisk_patched.img
This command won't change anything on your stock boot partition. If it fails, you only have to reboot your phone.
But if not and your phone boots up with Magisk installed, then everything is fine with that build you downloaded with the tool.
You also have the option to grep your stock boot.img because you just booted a patched image and did not flash it.
There's nothing to loose. You should try it.
Click to expand...
Click to collapse
Cool, thanks for the info, but sadly I'll be forced to not unlock the bootloader now, I don't know if It'll trigger safetynet ( g9 plus is hardware eval type ) and I can't lose a few apps, since g9+ is my primary and only phone unfortunately , really thing I'll be forced to wait till someone root it and confirms that safetynet can be bypassed, anyway thanks again for the info and for your patience