Help Identifying moto x model - Moto X Q&A

Hey everyone!
My sister got a Motorola like 2 or 3 years ago, which model I can't Identify, but looking at photos, it seems like a Moto X.
Problem is, I can't remove the back cover, the phone is stuck in the bootloader unlocked screen, and the phone has TWRP installed, and that's everything I have Access too (and fastboot of course 30.B7).
Is there a way to get the model from an ADB command or something like that?
The phone is the one on the link below
http://www.gsmarena.com/motorola_moto_x-5601.php
I would like to know if there's a way to recover the phone with a ZIP (if ADB transfer is possible), or if there's another way to flash the phone, without losing the recovery (of if it's easier to install later).
Any help will be appreciated.
UPDATE: I didn't find a way to identify the model, I just took a flashable ZIP around the forums, took the XT1052 GB and uploaded via adb sideload, and it just worked, now I need to ask for the nano sim and check if it's working

To find the model number, turn the phone over and look on the back cover at the bottom around the mic hole. Embossed very lightly is the model number, FCC ID, and it says "DESIGNED & ASSEMBLED IN THE USA." You'll have to hold it at an angle so that light reflects off of it or else it doesn't appear to be there. It's much harder to see on phones with a white back, but it's always there.

Related

heres a repair idea that just might be new....

or at least not documented in a good place.
heres my long story/adventure for the past 2 days.(the short story is after the break\/ \/ \/)
picked up a "broken" htc dream from craigslist... phone is stuck on rainbow bootloader, so everything online is saying flash the dreaimg.nbh file on the root of a fat32 formatted microsd card. then other info about if it fails. but no info if it completes, and verifies every line and say ok, then do the command to reboot, and it still goes into bootloader... as if the camera button is stuck!! great idea, ill remove my camera button from the main board to test that theory that some ppl can force on you like a religion... phone still started in boot loader mode... with camera button desoldered from the phones main logic board(or whatever the official term for it is) so to the guy who said he didnt care if it felt like the camera button is clicking fine or not, somethings wrong with it, no ifs, ands, and buts about it. you might be wrong....
anyways, i picked up another broken g1, this one with a cracked lcd. the screen was half visible, so i tested to ensure it booted before paying for it. it booted fine and fast, i was in good luck, and the radio was already at 2.xx.xx.xx, so dangerspl wasnt a problem. so i took apart phone two and replaced only the main board in each phone. mainboard 1 in phone 2 boots fine(with camera button desoldered from mainboard), and mainboard 2 in phone 1 goes to the bootloader screen, but will still go into recovery mode with no problem. i then just swapped out the front button board from phone 2, over to phone 1, with phone 1's original mainboard. and it boots perfectly fine. so i have come to the conclusion that the front board is what make it not function properly. i have since upgraded mainboard 1's radio to 2.xx.xx.xx, dangerSPL, cyanogenmod 6, psgroove.....
______________Short Story___________________
so i guess what i am saying is if your phone seems like the "camera" button is stuck, cuz the phone isnt bricked due to its other responsiveness(recovery manager), you might need to replace one of these following two items.
This is what i believe to be the main culprit, but i havent tested each peice individually yet, so i could be wrong. and this is the other part that you might consider replacing.
and to prevent a few questions, both of these phones were tmobile US phones, not european or rogers or any other provider one.
That's some good ol' fashioned trouble shooting!
yes, much trouble, but no shooting.... but it was well worth it..
What I said is it MIGHT be the camera button, or it MIGHT be the BACK button. BOTH of those buttons can cause it to jump into fastboot!
And so rather than TRYING BOTH, you decided to try ONE and then give up and replace the entire board containing the button.
Well guess what you've proven: It was the BACK button.
Just like I said it was.

[Q] Help! Black Screen, Can't see recovery or Download, but Odin recognises my Tab

I tried to flash a stock ROM after getting sick of the little glitches in custom ROMs. Big mistakeand possibly fatal (for my Tab anyway).
I get a Black screen only, but I know it is on as my PC recognises it. I can't go into Download or Recovery either.
I managed to flash a Pit (hidden Pit) through Odin, so I know it can be seen, but I get the thing to boot properly.
I'm assuming it is a locked bootloader issue.
Are there any solutions?
Successfully flashed Roto-JME-Full-v4.tar but still black screen
Successfully flashed Roto-JME-Full-v4.tar but still black screen
My issue, for any who are interested, was a burnt out component on the main board.
It was repaired under warranty.
Took a week here in Melbourne, Australia.
1. Can you specify which component?
2. Does it have anything to do with the flashing?
I have to admit I was afraid to go into any detail about flashing the Tab with the repairer in case it voided my warranty.
I wouldn't have thought i'd blow a main board using Odin!?
Part numbers on the repair docket are:
1 x A/S ASSY-PBA MAIN(COMM) GT_P1000
1 x A/S ASSY-PBA MAIN(AUTL.) GT-P1000T
This probably doesn't help though, as these look like labour codes.
Personally I dont think it was ODIN that burnt out the component... It would have to just be a bung component in tab... Either that or your USB is doing something weird with voltage, don't think so though because usually that just fries EVERYTHING...
Had it happen to a HTC Jam once, big flash onscreen, shutdown and wouldn't start up again... I really liked that phone at the time, brought tears to my eyes...
search on the forums for "Telstra rom galaxy tab" to find a "backup" of the telstra rom in case needed again...
SO you say you had a black screen? Where you able to see the Samsung logo and get into clockwork? Cause I can do all of that, but no matter what I flash, nothing will work.
I just want to go back to stock before I started screwing around :'(
No, my screen was totally dead!

Couple quick questions: TWRP's memory footprint and edge program

I have the 32g turbo and like having lots of music on my phone. I want to load TWRP but am concerned about how much space it takes up. Can anybody clue me in to that info?
Also, I bought the phone on the edge program, so if I turn it in, will it be a problem with Verizon that the bootloader is unlocked? Has anyone had any experience with this?
devlop said:
I have the 32g turbo and like having lots of music on my phone. I want to load TWRP but am concerned about how much space it takes up. Can anybody clue me in to that info?
Also, I bought the phone on the edge program, so if I turn it in, will it be a problem with Verizon that the bootloader is unlocked? Has anyone had any experience with this?
Click to expand...
Click to collapse
TWRP lives in a separate partition than where your user data is kept, so it will have 0 impact on the amount of storage space on your phone.
I don't have any first hand experience with the edge program, but I can almost guarantee you that you'll have to pay the full price for the phone if you try to turn it in. Unlocking the bootloader is a permanent modification. Even if you re-lock it, the flash counter will still indicate that the phone has been unlocked at some point.
Thanks for the reply. According to my contract, once 75% is paid off, I can trade it in for another phone. I'm just not sure if looking for an unlocked bootloader is one of the things they consider during trade in.
devlop said:
Thanks for the reply. According to my contract, once 75% is paid off, I can trade it in for another phone. I'm just not sure if looking for an unlocked bootloader is one of the things they consider during trade in.
Click to expand...
Click to collapse
What does it say that they look for?
Did a little digging, found this on their site :
The device must be in good working condition and must meet the following requirements or it will be rejected and returned to you:
Device has a functioning battery
Device can power on and off
Device has an intact, functioning LCD screen and glass with no cracks or breaks
Device and charging port must be intact (not broken or charging port missing)
Device and connecting ports must be free of visible corrosion and water damage
If your previous device is an AppleĀ® device with iOS 7 or later, you must disable Find My iPhone prior to sending it back
Looks like I might be in the clear. I always just assumed they reflashed any device that was traded in or turned in for warranty anyways. Seems like the easiest route instead of trying to go through each phone to clear out memory to put back on the shelf. I have in the past turned in phones for warranty that were rooted and unlocked. Never been an issue.
devlop said:
Did a little digging, found this on their site :
The device must be in good working condition and must meet the following requirements or it will be rejected and returned to you:
Device has a functioning battery
Device can power on and off
Device has an intact, functioning LCD screen and glass with no cracks or breaks
Device and charging port must be intact (not broken or charging port missing)
Device and connecting ports must be free of visible corrosion and water damage
If your previous device is an AppleĀ® device with iOS 7 or later, you must disable Find My iPhone prior to sending it back
Looks like I might be in the clear. I always just assumed they reflashed any device that was traded in or turned in for warranty anyways. Seems like the easiest route instead of trying to go through each phone to clear out memory to put back on the shelf. I have in the past turned in phones for warranty that were rooted and unlocked. Never been an issue.
Click to expand...
Click to collapse
Oh nice. Looks like you're good to go then.

Massive issues- don't know how to resolve

Hello everyone!
I may be in deep trouble. Over the past few months, my phone has been in (self-hands) service.
I have bought a Sony Xperia Z1 C6903 used with a faulty battery and faulty audio jack port.
I have ordered a new battery and new audio jack port for my phone from eBay. I feel it is worth noting that all my orders below are from eBay. Roughly 2 weeks after I have ordered the presumed "original" parts for my phone, some one in my family has 'unknowingly' stepped on to the charge cable while the phone was charging thus resulting the phone's screen to be cracked half-way.
After that rather pleasant aftermath, I placed an order for a new 'OEM' screen digitizer along with new adhesive tapes for the phone.
After receiving my items, I proceeded to apply and replace. During the old screen tear down, I have managed to tear the loudspeaker flex ribbon. After that stressful moment, I ordered an 'original' Power On/Off-Volume-Camera flex ribbon. After that, I have replaced the ribbon and applied the adhesive tapes on the phone panels.
Before the whole part replacing, my phone was running on the DstrikerZ1Kai ROM (Version SP002X) because I was unable to unlock its boot-loader. it also had the dual recovery system installed on it.
After all that nightmare, I wanted to revert the phone back to stock ROM because of the following issues:
1. The phone stopped recognizing my USB sticks. Tried all the USB-Stock mount-etc apps on play and the net. Could not get it running.
2. It was starting to get hard to charge the phone. Now I have read about these types of problems. It is said that it is related to the ROM. May be also related to the USB problems I had.
3. I wanted to flash the Kryptonian v5 Final ROM.
Now comes my current big problem.
I was using the Xperia Companion tool to revert back to stock. Everything went fine up to the point where it told me to put the phone to flash mode.
I proceeded to try to put the phone into flash mode, however, as I immediately realized, the Volume Down button did not work at all. I then quickly thought it was a software issue and not a hardware problem. I put the phone to TWRP recovery using the inbuilt dual recovery app (forgot it's precise name), and put the DstrikerZ1Kai ROM to stock, as if I have just flashed it. Of course, I have made a backup before that in case something went awry. But during the re-flash, I have received an error. I don't remember what the error was unfortunately. After that, I accidentally rebooted the phone and now all I receive is the Sony Logo.
I wanted to use the Flash Tool to re-flash an FTP, however, I can not enter Flash Mode since my Volume Down isn't working. I can enter Fast-boot Mode, but then that is it. If I use the Fastboot menu options in Flash Tool, I can get some device info, but then, that is it. I can't use the ADB option, because it says "Device must be in ADB Mode". If I put the phone on charger, I get a red light at the top.
During the phone repair, I have reinstalled my PC to Win 7 Ultimate 64-bit. I don't know if I have the correct drivers installed, to be honest.
Please help me everyone. I am totally stuck here and don't know how to proceed forward. Should I take the phone apart again and try to press the Volume Down manually and not with the buttons itself? Should I buy a new Flex ribbon.
Dujo13309 said:
Hello everyone!
I may be in deep trouble. Over the past few months, my phone has been in (self-hands) service.
I have bought a Sony Xperia Z1 C6903 used with a faulty battery and faulty audio jack port.
I have ordered a new battery and new audio jack port for my phone from eBay. I feel it is worth noting that all my orders below are from eBay. Roughly 2 weeks after I have ordered the presumed "original" parts for my phone, some one in my family has 'unknowingly' stepped on to the charge cable while the phone was charging thus resulting the phone's screen to be cracked half-way.
After that rather pleasant aftermath, I placed an order for a new 'OEM' screen digitizer along with new adhesive tapes for the phone.
After receiving my items, I proceeded to apply and replace. During the old screen tear down, I have managed to tear the loudspeaker flex ribbon. After that stressful moment, I ordered an 'original' Power On/Off-Volume-Camera flex ribbon. After that, I have replaced the ribbon and applied the adhesive tapes on the phone panels.
Before the whole part replacing, my phone was running on the DstrikerZ1Kai ROM (Version SP002X) because I was unable to unlock its boot-loader. it also had the dual recovery system installed on it.
After all that nightmare, I wanted to revert the phone back to stock ROM because of the following issues:
1. The phone stopped recognizing my USB sticks. Tried all the USB-Stock mount-etc apps on play and the net. Could not get it running.
2. It was starting to get hard to charge the phone. Now I have read about these types of problems. It is said that it is related to the ROM. May be also related to the USB problems I had.
3. I wanted to flash the Kryptonian v5 Final ROM.
Now comes my current big problem.
I was using the Xperia Companion tool to revert back to stock. Everything went fine up to the point where it told me to put the phone to flash mode.
I proceeded to try to put the phone into flash mode, however, as I immediately realized, the Volume Down button did not work at all. I then quickly thought it was a software issue and not a hardware problem. I put the phone to TWRP recovery using the inbuilt dual recovery app (forgot it's precise name), and put the DstrikerZ1Kai ROM to stock, as if I have just flashed it. Of course, I have made a backup before that in case something went awry. But during the re-flash, I have received an error. I don't remember what the error was unfortunately. After that, I accidentally rebooted the phone and now all I receive is the Sony Logo.
I wanted to use the Flash Tool to re-flash an FTP, however, I can not enter Flash Mode since my Volume Down isn't working. I can enter Fast-boot Mode, but then that is it. If I use the Fastboot menu options in Flash Tool, I can get some device info, but then, that is it. I can't use the ADB option, because it says "Device must be in ADB Mode". If I put the phone on charger, I get a red light at the top.
During the phone repair, I have reinstalled my PC to Win 7 Ultimate 64-bit. I don't know if I have the correct drivers installed, to be honest.
Please help me everyone. I am totally stuck here and don't know how to proceed forward. Should I take the phone apart again and try to press the Volume Down manually and not with the buttons itself? Should I buy a new Flex ribbon.
Click to expand...
Click to collapse
You might want to buy another phone. Most after-market flex ribbons are defective: the phone either won't boot or screen wouldn't work, or various buttons wouldn't work.
You can try to buy a defective phone very cheap: it could even be sim locked, as all you need is the middle frame with all ribbons intact. Then you can transfer your current motherboard and all other electronic parts to the new frame. Keep in mind that there is a risk you can damage your screen while doing that... . Those are your options.

Huawei P10 lite oem and firmware needed

Good day
I've searched everywhere, high and low, left and right but cant get anywhere in life.:crying:
I was playing around with my device a few months ago and landed up with the wrong firmware, i flashed my device got it bricked and so on, trying to make it a dual sim as the people i got it from, got it single SIM thus leaving me with a Problem, certain apps are not running the way they should and I've put up with it for as long as possible...
Long story short, could someone please get me the single sim flashable zip oem for the C185 or if even possible the dual sim oem but it must be C185, attached you'll see my problem i have put together screen captures of what i need and what i no longer want....
Both oem and firmware and how to install it would he much appreciated. @KingOfMezi if you find this you were supposed to help me with it also but didn't get back to me.
Please could someone help me:crying:

Categories

Resources