Related
I asked the guy i bought it from if he modified the bootloader or rom and he said "no", but how do I verify this?
I guess since it won't take the update then I should go ahead and attempt to root, right?
My goal is to get the camera patch on it one way or another.
When I go to the bootloader screen is says:
AP fastboot Flash Mode (US)
30.70
DEVICE is UNLOCKED. Status Code: 1
Normal Powerup
Recovery
Factory
Switch Console [NULL: null]
Barcodes
BP Tools
Thanks!
Maybe I am missing something, but how is an AT&T unlocked? Is it a developer edition?
Sent from my XT1058 using Tapatalk
Can you show the kernel version string too ?
Looks like you bought a non att unit of which the user reflashed The aTT ROM. E.g maybe one of these american movil units from eBay ?
Should apply the update manually, e.g download from sbf droid.
Sent from my XT1058 using xda app-developers app
Appreciate the help!
How do I get the kernel version string? I thought I had that in one of my screenshots in original post.
This Moto X has blue buttons & camera ring so it looks like it was ordered via Moto Maker.
I am coming from an iphone 5 but had a Galaxy Nexus and a few other droids before the iphone.
Trying to get up to speed on the Moto X now.
planktoid said:
Can you show the kernel version string too ?
Looks like you bought a non att unit of which the user reflashed The aTT ROM. E.g maybe one of these american movil units from eBay ?
Should apply the update manually, e.g download from sbf droid.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Also, how do i verify if bootloader is unlocked?
DEVICE is UNLOCKED. Status Code: 1
I thought a "1" meant it is actualy a locked bootloader?
Never mind I was able to flash TWRP so I guess that answers all my questions.
Thanks guys!
Judging by the screenshot it looks like you may have gotten a production model. They were test devices that shouldn't have made it into the hands of the public. Your screenshot shows you are on:
139.7.17_ghost_att.ATT.en.US
Retail models were shipped with:
139.9.51_ghost_att.ATT.en.US
Your best bet to make sure you get updates is to flash an FXZ file via rsdlite or fastboot.
Sent from my Moto X
You should pull the system first....in case there are any goodies in there. Might be useful to devs to look at if it is a preproduction unit.
My friend Has a verizon carrier motox. Rooted.Not Unlock. I wan't to unlock it.So,I got a verizon dev. ed. motox cid.img and unlock code,wan't unlock it.
I restore the dev. ed Motox cid.img(mmcbll0p29) using adb shell:
Code:
cat /sdcard/cid.img > /dev/block/platform/msm_sdcc.1/by-name/cid
But...friend's motox Bricked....
AP Fastboot Mode tips CID wrong.Stuck in the ap,status system hub 0x39,Unable to boot.
I use dev.ed motox unlock code to unlock verizon motox, CMD display "fastboot oem unlock disabled! "...
The bricked verizon motox can't flash any firmware.Tip "Preflash validation failure"
What should I do????Help me..Please!!! Please!! Thanks!!!
Dusty tears said:
My friend Has a verizon carrier motox. Rooted.Not Unlock. I wan't to unlock it.So,I got a verizon dev. ed. motox cid.img and unlock code,wan't unlock it.
I restore the dev. ed Motox cid.img(mmcbll0p29) using adb shell:
Code:
cat /sdcard/cid.img > /dev/block/platform/msm_sdcc.1/by-name/cid
But...friend's motox Bricked....
AP Fastboot Mode tips CID wrong.Stuck in the ap,status system hub 0x39,Unable to boot.
I use dev.ed motox unlock code to unlock verizon motox, CMD display "fastboot oem unlock disabled! "...
The bricked verizon motox can't flash any firmware.Tip "Preflash validation failure"
What should I do????Help me..Please!!! Please!! Thanks!!!
Click to expand...
Click to collapse
You can not and will never be able to unlock the boot loader on a consumer Verizon variant, lesson learned. Your only hope in hell maybe? Is to run the 4.4.2 sbf firmware for Verizon only only only only only, no its not out and maybe awhile before its available
Sent on my Gummy running Lenoto X
flashallthetime said:
You can not and will never be able to unlock the boot loader on a consumer Verizon variant, lesson learned. Your only hope in hell maybe? Is to run the 4.4.2 sbf firmware for Verizon only only only only only, no its not out and maybe awhile before its available
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I think 4.4.2 firemware can't to save it.Because CID is wrong,can't flash anything.That sounds Bad..:crying:
maybe I substitute the CPU suite or substitute Phone main board can save it...Fixed it should spend about $135:crying::crying::crying::crying:....
Dusty tears said:
I think 4.4.2 firemware can't to save it.Because CID is wrong,can't flash anything.That sounds Bad..:crying:
maybe I change the CPU suite or change Phone main board can save it...Fixed it should spend about $135:crying::crying::crying::crying:....
Click to expand...
Click to collapse
Wait for the sbf firmware, if you can access the fastboot menu, it's not totally done, the sbf firmware will hopefully flash it back, you need it anyways ,even if you swap out the internals, and do not flash any other sbf firmware ,it will hard brick it
Sent on my Gummy running Lenoto X
---------- Post added at 11:13 AM ---------- Previous post was at 11:06 AM ----------
Wait ,you can flash the 4.4 Verizon sbf firmware because you haven't updated to 4.4.2 yet
Sent on my Gummy running Lenoto X
I'm new to Motorola flashing, can anyone explain the purpose of cid partition, thanks.
sent via tapatalk
eksasol said:
I'm new to Motorola flashing, can anyone explain the purpose of cid partition, thanks.
sent via tapatalk
Click to expand...
Click to collapse
CID partition is the unlock bootloader certificate.CID parition include the factory information and Carrier information.If no this parition or partition wrong,can't unlock bootloader,and can't flash any firmware.
But on droid razr, erase this parition can flash other carrier's firmware. e.g. XT910 UK retail firmware,
Like the attached picture:
Do you find something???
http://forum.xda-developers.com/attachment.php?attachmentid=2578154&stc=1&d=1392344682
flashallthetime said:
Wait for the sbf firmware, if you can access the fastboot menu, it's not totally done, the sbf firmware will hopefully flash it back, you need it anyways ,even if you swap out the internals, and do not flash any other sbf firmware ,it will hard brick it
Sent on my Gummy running Lenoto X
---------- Post added at 11:13 AM ---------- Previous post was at 11:06 AM ----------
Wait ,you can flash the 4.4 Verizon sbf firmware because you haven't updated to 4.4.2 yet
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Okey,man.I don't find another way.
DO YOU have the original CID partition ?just restore it ,i can help you
I have got phone with strange FW installed.
BL ver. 30.50
FW name factory_ghost-userdebug 4.2.2 13.9.0Q2.X-11
It works, but I would like to flash it to standard interface. How could I determine exact model of the phone? SKU in Barcodes: 0000...
Check the bottom on the back. The model number will be printed there in really small print.
nhizzat said:
Check the bottom on the back. The model number will be printed there in really small print.
Click to expand...
Click to collapse
+1
nhizzat said:
Check the bottom on the back. The model number will be printed there in really small print.
Click to expand...
Click to collapse
No covers at all. That's the problem
Download CPU-Z in the app store. The system tab will show you model information. Mine reads: XT1053(ghost_retail)
Thanks to all. It was CDMA. Sprint. Now works in GSM
P.S. CPU-Z shows same info from Barcodes
Vivjen said:
Thanks to all. It was CDMA. Sprint. Now works in GSM
P.S. CPU-Z shows same info from Barcodes
Click to expand...
Click to collapse
Yeah, most apps that can/will tell you the phone's model will go by the ROM installed on the phone.
If someone flashes an XT1058 with XT1053 ROM for example, the apps, adb queries, etc will all say the XT1053 info.
Vivjen said:
I have got phone with strange FW installed.
BL ver. 30.50
FW name factory_ghost-userdebug 4.2.2 13.9.0Q2.X-11
It works, but I would like to flash it to standard interface. How could I determine exact model of the phone? SKU in Barcodes: 0000...
Click to expand...
Click to collapse
Can you post a system dump? I'm sure it could be useful.
Not sure if OP resolved their issue, but in any case I suppose someone can use the imei and/or serial number to check online about info on the phone. those two numbers should be unchanged across ROMs. usually anyway. they can be found in About Phone -> Status or probably imprinted on the phone if the internals are exposed.
googling reveals a few such sites, one of the more reliable seems to be: http://sndeep.info/en
(I haven't tried it myself).
dtg7 said:
Not sure if OP resolved their issue, but in any case I suppose someone can use the imei and/or serial number to check online about info on the phone. those two numbers should be unchanged across ROMs. usually anyway
Click to expand...
Click to collapse
Some phones have "0" IMEI...
del
I have found right answer - radio version
fastboot getvar all
There are just 5 possible options:
0x1-XT1058
0x2-XT1060
0x4-XT1056 (including XT1049/XT1050?)
0x5-XT1055
0x6-XT1053
Vivjen said:
I have found right answer - radio version
fastboot getvar all
There are just 5 possible options:
0x1-XT1058
0x2-XT1060
0x4-XT1056 (including XT1049/XT1050?)
0x5-XT1055
0x6-XT1053
Click to expand...
Click to collapse
But again, what if someone flashes the XT1053 radio on an XT1058 device, or vice versa? Does that value change?
Something else that I know doesn't change is the CID... but I don't know all the numbers... Just that...
CID 0x00 = Verizon DEVELOPER EDTION XT1060
CID 0x01 = XT1058 ATT
CID 0X02 = Verizon XT1060 Non-Developer Edition
CID 0x09 = XT1053 All (as far as I know it covers all XT1053 variants.)
but those are the only ones I know.
I did buy an moto x from eBay couple of weeks ago and it say Device UNLOCKED Status Code 1 in the Fastboot Mode ...I cannot make any sense of it since all of the Moto X have the status code 3,not 1. Also it has on extra option in Fastboot menu Switch console [NULL: null]. othe thing is when I run Command Fastboot erase all it erases allot of partition on the phone,and not just a few like in the rest of the Moto X ...The only problem that i have is that the IMEI is missing and it cannot be used to make any kind of phone calls Does anybody knows anything about this issue and explain to me what is the deal with it? Any help is much appreciated
DejanPet said:
I did buy an moto x from eBay couple of weeks ago and it say Device UNLOCKED Status Code 1 in the Fastboot Mode ...I cannot make any sense of it since all of the Moto X have the status code 3,not 1. Also it has on extra option in Fastboot menu Switch console [NULL: null]. othe thing is when I run Command Fastboot erase all it erases allot of partition on the phone,and not just a few like in the rest of the Moto X ...The only problem that i have is that the IMEI is missing and it cannot be used to make any kind of phone calls Does anybody knows anything about this issue and explain to me what is the deal with it? Any help is much appreciated
Click to expand...
Click to collapse
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831
KidJoe said:
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831
Click to expand...
Click to collapse
A picture can say a million words.. Thanks a lot KidJoe for the reply
DejanPet said:
A picture can say a million words.. Thanks a lot KidJoe for the reply
Click to expand...
Click to collapse
Exactly what model do you have? What is stamped on the back of the phone in the FINE PRINT?
Based on those shots... 161.44.25 is XT1053 4.4.2. 30.B7 is 4.4.2 bootloader.
BUT as you can see, similar to those other threads, your phone reports...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
And your IMEI and SKU are all zeros...
I'm not sure how phones are getting into this state. And I don't have a fool proof way to fix them.
it is probably one of those "motorola confidential property" tagged phones used by company staff only, it may have been leaked into market, it often has unlocked bootloader like developer edition phones. it is a pre release phone with extra functions (that are not in mass production versions)
KidJoe said:
First... Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says
Also, you might want to see this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150
and this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/att-xt1058-stuck-4-2-2-t3045831
Click to expand...
Click to collapse
DejanPet said:
A picture can say a million words.. Thanks a lot KidJoe for the reply
Click to expand...
Click to collapse
KidJoe said:
Exactly what model do you have? What is stamped on the back of the phone in the FINE PRINT?
Based on those shots... 161.44.25 is XT1053 4.4.2. 30.B7 is 4.4.2 bootloader.
BUT as you can see, similar to those other threads, your phone reports...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
And your IMEI and SKU are all zeros...
I'm not sure how phones are getting into this state. And I don't have a fool proof way to fix them.
Click to expand...
Click to collapse
tahwer said:
it is probably one of those "motorola confidential property" tagged phones used by company staff only, it may have been leaked into market, it often has unlocked bootloader like developer edition phones. it is a pre release phone with extra functions (that are not in mass production versions)
Click to expand...
Click to collapse
hi dears
well, i've got the same issue (device is unlocked - status code 1)
it seems it has an unlocked bootloader, but for me, the unlocked bootloader warning has never appeared
i've even flashed twrp and cyanogenmod 12.1
my question is, (1) should i unlock it with the code and all that moto.com stuff?
one last question is, (2) why can't i just add supersu from twrp 2.8.7.0?
i turn it on at system, and i swipe to root, but the icon never appears on my apps drawer, is it related to the status code 1?
please help me...
For God sake! I have the same problem here. How can I root this phone? What code 1 means?
Longer story short... I bought what was supposed to be an XT1095 off of Amazon - one of the $300 deals (though this was black leather, 16gb). Amazon (and their sellers) had run out of the first batch when Moto first came out with the deal a couple of weeks back. They began sending out XT1092's and XT1097's, and stated the XT1095 for $300 wouldn't be available again for a couple of months. People got frustrated, Amazon put it on hold, then it suddenly came back up this week, including the 16gb black leather option for the same price.
When I got it I was suspicious. The IMEI checks I did returned results evident of AT&T's XT1097 rather than the pure XT1095. Without going into great detail, I believe now it's an AT&T XT1097 converted to Pure. It received all the updates out of the box (from 4.4.4 to 5.1), like a pure edition should.
We're on Cricket now, so if it has AT&T hardware, we're fine. But if we ever want to switch over to T-Mobile, I'm assuming that will be a problem for T-Mobile's LTE bands? Is the hardware between XT1097 and XT1095 different? Or are they just different at the software/baseband level - meaning what I'm holding should be precisely like having a pure edition XT1095 going forward?
It's not an AT&T xt1097. Those cannot be converted to xt1095 because their bootloader can't be unlocked.
Sent from my XT1095
AGISCI said:
It's not an AT&T xt1097. Those cannot be converted to xt1095 because their bootloader can't be unlocked.
Sent from my XT1095
Click to expand...
Click to collapse
Thanks for that. There are other variants of the XT1097 that are convertible though - so possibly it's one of those? I guess the main potential problem is band support between 1097 and 1095...
jntdroid said:
Thanks for that. There are other variants of the XT1097 that are convertible though - so possibly it's one of those? I guess the main potential problem is band support between 1097 and 1095...
Click to expand...
Click to collapse
Supposedly the 1097 has 1 extra band than 1095. Other than that they are identical, so there will be no issues if it really is a 1097, it will work with tmobile with no problems.
In fastboot is your bootloader locked, unlocked, or relocked?
If it's locked, then it's a 1095 for sure! If it's unlocked or relocked it could have been converted. If you unlocked it... then we will never know, lol.
Sent from my XT1095
AGISCI said:
Supposedly the 1097 has 1 extra band than 1095. Other than that they are identical, so there will be no issues if it really is a 1097, it will work with tmobile with no problems.
In fastboot is your bootloader locked, unlocked, or relocked?
If it's locked, then it's a 1095 for sure! If it's unlocked or relocked it could have been converted. If you unlocked it... then we will never know, lol.
Sent from my XT1095
Click to expand...
Click to collapse
Good idea - didn't think to check that. And no I haven't unlocked it fortunately. Hang on just a minute...
AGISCI said:
Supposedly the 1097 has 1 extra band than 1095. Other than that they are identical, so there will be no issues if it really is a 1097, it will work with tmobile with no problems.
In fastboot is your bootloader locked, unlocked, or relocked?
If it's locked, then it's a 1095 for sure! If it's unlocked or relocked it could have been converted. If you unlocked it... then we will never know, lol.
Sent from my XT1095
Click to expand...
Click to collapse
Well it looks like I'm pure... weird... thanks for that:
http://imgur.com/0pG7pik
jntdroid said:
Well it looks like I'm pure... weird... thanks for that:
http://imgur.com/0pG7pik
Click to expand...
Click to collapse
Sorry to disagree with you, but that means that your phone is locked, could be any model like 1097 or 1092 because there are retails of those models and they are receiving the update to 5.1 as fast as the pure edition. The only certain way to now what version you have is by checking the numbers that are printed next to the USB port (very tinny BTW) or download CPU-Z and check your system information. Regards
juliospinoza said:
Sorry to disagree with you, but that means that your phone is locked, could be any model like 1097 or 1092 because there are retails of those models and they are receiving the update to 5.1 as fast as the pure edition. The only certain way to now what version you have is by checking the numbers that are printed next to the USB port (very tinny BTW) or download CPU-Z and check your system information. Regards
Click to expand...
Click to collapse
Thanks. I'm still suspicious as well given my IMEI checks. FCC ID on the bottom is IHDT56QA1. CPU Z shows XT1095 (victara_tmo). But won't a converted one show the same in CPU Z?
Sent from my XT1095 using Tapatalk
jntdroid said:
Thanks. I'm still suspicious as well given my IMEI checks. FCC ID on the bottom is IHDT56QA1. CPU Z shows XT1095 (victara_tmo). But won't a converted one show the same in CPU Z?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
You are right. Here is what you have to do:
in bootloader mode just type: fastboot getvar all
and you will see the info of your hardware, for example, my phone is converted and here you can see that the original version is XT1097.
PS you dont need to unlock your device or root.
juliospinoza said:
You are right. Here is what you have to do:
in bootloader mode just type: fastboot getvar all
and you will see the info of your hardware, for example, my phone is converted and here you can see that the original version is XT1097.
PS you dont need to unlock your device or root.
Click to expand...
Click to collapse
Will report back later once I can plug it in and check. Thanks!
jntdroid said:
Will report back later once I can plug it in and check. Thanks!
Click to expand...
Click to collapse
In settings on your phone does it say tmo in version like this photo I attached? If so it is 1095. That is the 1095 software, and since the bootloader is locked it is not converted. Tmo is tmobile by the way.
Sent from my XT1095
AGISCI said:
In settings on your phone does it say tmo in version like this photo I attached? If so it is 1095. That is the 1095 software, and since the bootloader is locked it is not converted. Tmo is tmobile by the way.
View attachment 3400212
Sent from my XT1095
Click to expand...
Click to collapse
Yes that's what it says.
So the bottom line here is if it's been converted it can't say "Locked" b/c it has to be unlocked to be converted... so at best it would say "unlocked" or "re-locked" then - correct?
jntdroid said:
Yes that's what it says.
So the bottom line here is if it's been converted it can't say "Locked" b/c it has to be unlocked to be converted... so at best it would say "unlocked" or "re-locked" then - correct?
Click to expand...
Click to collapse
Correct, once you unlock it, it will never say "locked" again. Either unlocked or relocked.
So since it is "locked" it is 100% sure that it is 1095. Ignore the imei thing because that is from a 3rd party, not motorola, they made a mistake in the database, the phone is 1095.
Sent from my XT1095