Related
My HTC One X has a dead screen. The actual OS, lights and touch digitizer work as they should.
I have a lot of documents and photos on the phone that I would love to get off the phone via USB, but I cant quite get to the settings page without a screen.
If there is a way to pull the data off without having to go into the settings and set USB to file transfer, or if someone can send screenshots so I can see where to tap, that would be great.
I need a screenshot of the password screen (keypad), the settings screen all the way until i get to the usb screen, if anyone would please.
Thanks. First thread.
What recovery do you have (a custom one?) You can boot into that and enable ums and then retrieve data.
I may guide you
RE
Mr Hofs said:
What recovery do you have (a custom one?) You can boot into that and enable ums and then retrieve data.
I may guide you
Click to expand...
Click to collapse
Recovery? I dont know what you are talking about, so I believe i use stock. I stumbled upon a different way to get the files off via a hack on a different thread, but its ADB hack. Im a little clueless with this, but if you could guide me that would be appreciated.
The other thread i found is here: http://forum.xda-developers.com/showthread.php?t=1573744
Ah you are fully stock, no unlocked bootloader and custom rom ?
Well at least we can try this :
Download android SDK bundle (Google ) and unpack it to lets say :
C:\android
So we can find it easily ! Navigate with windows explorer to that folder and unfold the folders to a folder named "platform-tools" and check that you have adb.exe inside that folder.
Hold down shift and right click the mouse, select "open command window here.
Now connect the phone and type :
Adb devices in the command window
TehEngineer said:
My HTC One X has a dead screen. The actual OS, lights and touch digitizer work as they should.
I have a lot of documents and photos on the phone that I would love to get off the phone via USB, but I cant quite get to the settings page without a screen.
If there is a way to pull the data off without having to go into the settings and set USB to file transfer, or if someone can send screenshots so I can see where to tap, that would be great.
I need a screenshot of the password screen (keypad), the settings screen all the way until i get to the usb screen, if anyone would please.
Thanks. First thread.
Click to expand...
Click to collapse
well you should follow MR HOFS he will guide you easily but on your request here is the lock screen
RE
Mr Hofs said:
Ah you are fully stock, no unlocked bootloader and custom rom ?
Well at least we can try this :
Download android SDK bundle (Google ) and unpack it to lets say :
C:\android
So we can find it easily ! Navigate with windows explorer to that folder and unfold the folders to a folder named "platform-tools" and check that you have adb.exe inside that folder.
Hold down shift and right click the mouse, select "open command window here.
Now connect the phone and type :
Adb devices in the command window
Click to expand...
Click to collapse
It says "List of devices attached" and nothing else, then goes back to where it was. My phone does come up in "My computer" as drive K, but it cant be opened, probably due to the phone not allowing access, yknow when you hook it up it asks what you want it to do with the USB, like sync or charge, but its defaulted to charge only. But yeah, ADB DEVICES doesnt really do anything as far as I notice.
Then you probably have the problem that usb debugging is not enabled
You are on JB .... do you know how to get the phone on its homescreen ?
RE
Mr Hofs said:
Then you probably have the problem that usb debugging is not enabled
You are on JB .... do you know how to get the phone on its homescreen ?
Click to expand...
Click to collapse
Yeah, but I have no way of telling if im on the home screen or if im tapping the right buttons, which is why i asked for a screenshot. Not trying to sound rude.
Open ddms
Sent from my HTC One X using xda premium
Yeah open ddms ?!? Thats what i call short info.
You got your screenshot. If you are on the homescreen after the pincode the MTP should be enabled and your sdcard should be accessible
RE
Mr Hofs said:
Yeah open ddms ?!? Thats what i call short info.
You got your screenshot. If you are on the homescreen after the pincode the MTP should be enabled and your sdcard should be accessible
Click to expand...
Click to collapse
I tried to enter the code a few times, ive tried ADB every attempt. Ill keep trying until something happens.
RE
TehEngineer said:
I tried to enter the code a few times, ive tried ADB every attempt. Ill keep trying until something happens.
Click to expand...
Click to collapse
I had no luck unlocking the phone. I believe I did, but it still didnt show up on the command prompt.
Im sorry I dont have much knowledge on android, but i presume there is no way to directly pull data from the device, without having to unlock it, correct?
Edit
I dont think the digitizer is functioning anymore. I cannot get any touch response out of it anymore. Is it a goner?
Re
I cant get any response out of it anymore. Am I out of options?
Unfortunately yes.....
RE
Mr Hofs said:
Unfortunately yes.....
Click to expand...
Click to collapse
Alright. thanks for the help though.
Yeah well ! Can't think of any other solution !
Mr Hofs said:
Yeah well ! Can't think of any other solution !
Click to expand...
Click to collapse
I just had one last thing to add.
Sorry for the late reply, but, It still has internet connection and I can install an app from the Play store remotely. I just cant run it due to the broken screen, but, if possible, is there a remote-access app that doesnt require setup that you know of? Or an app that enables file access somehow, Im not sure.
Or im still out of options. thanks again for your attention.
THIS METHOD WILL NOT WORK IN NEWER VERSIONS OF ANDROID
Click to expand...
Click to collapse
1.Please note that by using this method you can unlock phone without losing any data.
2.This must not be used for any illegal purpose.
3.I do not hold any responsibility of any phones bricked using this method(though it is tested)
.
.
Requirements
Links
1.Download Android Multi Tools- Click Here
2.Universal Adb Drivers - Click Here
Click to expand...
Click to collapse
.
.
Now lets begin
1.First unpack the tool.
2.Then install the adb driver.
3.Turn on your phone and connect it to pc via data cable.
4.Now press 1 to check if your device is connected properly.
5.Now if you have pin,password or face-lock please press 2.
6.If you have pattern lock then press 3.
7.Device will reboot and it will be unlocked.
8.If it still shows pattern,pin or password enter window simply simply give any to unlock.
Click to expand...
Click to collapse
.
.
Other action that can be done by this program are below
.
Choice detail
1.check device for check connection of device to pc.
4.reset gmail for reset gmail login after try many time wrong unlock
5.wipe data for reset all data to factory setting.
6.reboot for reboot device to normal mode or exit from adb shell.
7.check device on fastboot mode for check connection of device to on fastboot mode.
8.wipe data / cache on fastboot mode for erase user datat and cache on fastboot mode to resolve freeze,stuk on boot logo or slow down device. That is often found in the cpu spreadtrum sc6280/sc8810.
9.exit fastboot mode for reboot your pc or exit fastboot.
0.go to command promt for entering dos promt.you can use command in this soft folder and can return to the main program by type exit
s.software info for info cpu inside,firmware version and etc.
H.hardware info for determine the ic number of gsensor,touch screen,camera,wifi and more
Click to expand...
Click to collapse
.
.
.
thanks for reading this post
Written By
Pranto Roy
XDA
Click to expand...
Click to collapse
Links
1.download android multi tools- http://d-h.st/rCh
2. universal adb drivers - http://adbdriver.com/upload/AdbDriverInstaller.exe
prantoroy said:
Links
1.download android multi tools-
2. universal adb drivers -
Click to expand...
Click to collapse
thanks
my younger bro face this problem yesterday and today i got ans
will try and update
Jpjayesh said:
thanks
my younger bro face this problem yesterday and today i got ans
will try and update
Click to expand...
Click to collapse
Sure Please Update
Thnks
Sent from my HTC One X using xda app-developers app
chrisb906 said:
Thnks
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
hmm. . . gud
share it!!
Unfortunately, I was not at my work machine.
Pranto Roy said:
1.Please note that by using this method you can unlock phone without losing any data.
2.This must not be used for any illegal purpose.
3.I do not hold any responsibility of any phones bricked using this method(though it is tested)
.
.
.
.
.
.
.
.
.
Click to expand...
Click to collapse
Hello to everyone!
This description is very good, but unfortunately I can not help of mind. The Freetab 2099 tablet is set, the OSD, I forgot, offered through the recovery gmail account, but the machine is not connected to the Internet, and it can not be solved. The Windows XP felimeri the machine, but only shows an empty folder adb driver installation, and Total Commander, however does not see downloaded from the manufacturer's website drivers installed, but not working this solution, a multitool can not find device. Maybe a factory reset would solve the matter but has not yet been described find or install a new rom that is. Img extension of the manufacturer's side, but I do not know bekepcsolni debug mode on the machine, it does not allow the zárképrnyőről to move on.
If anyone knows a solution to my problem, thanks in advance.
Hello, Valer
Tiszaba said:
Hello to everyone!
This description is very good, but unfortunately I can not help of mind. The Freetab 2099 tablet is set, the OSD, I forgot, offered through the recovery gmail account, but the machine is not connected to the Internet, and it can not be solved. The Windows XP felimeri the machine, but only shows an empty folder adb driver installation, and Total Commander, however does not see downloaded from the manufacturer's website drivers installed, but not working this solution, a multitool can not find device. Maybe a factory reset would solve the matter but has not yet been described find or install a new rom that is. Img extension of the manufacturer's side, but I do not know bekepcsolni debug mode on the machine, it does not allow the zárképrnyőről to move on.
If anyone knows a solution to my problem, thanks in advance.
Hello, Valer
Click to expand...
Click to collapse
Seriously Man.
Didn't Understood A Word.
Give Details and Only Ask The Main Question
Pranto Roy said:
Seriously Man.
Didn't Understood A Word.
Give Details and Only Ask The Main Question
Click to expand...
Click to collapse
The "Freetab 2099" table host forgot the password and can not login. The Android Multi Tools does not recognize your computer, Windows can only see empty folders. How to factory reset the computer to do?
Tiszaba said:
The "Freetab 2099" table host forgot the password and can not login. The Android Multi Tools does not recognize your computer, Windows can only see empty folders. How to factory reset the computer to do?
Click to expand...
Click to collapse
If The Computer Doesn't Recognize It Install Drivers.
Without Identifying Its Not Possible.
Pranto Roy said:
If The Computer Doesn't Recognize It Install Drivers.
Without Identifying Its Not Possible.
Click to expand...
Click to collapse
Hello!
The Adb Driver Installer does not recognize the machine, so I installed the manufacturer's website for official drivers. Only one folder is empty, or whatever it may be copied, "The device is not responding or is not connected."
Tiszaba said:
Hello!
The Adb Driver Installer does not recognize the machine, so I installed the manufacturer's website for official drivers. Only one folder is empty, or whatever it may be copied, "The device is not responding or is not connected."
Click to expand...
Click to collapse
I'll Get The Drivers
ts, i tried to used the tool the the .exe recognize my device it shows the serial number but when i tried to unlock using otion 2 or 3 it doesn't work i got skk mobile a1 device it has somewhat like ios GUI
ghepier said:
ts, i tried to used the tool the the .exe recognize my device it shows the serial number but when i tried to unlock using otion 2 or 3 it doesn't work i got skk mobile a1 device it has somewhat like ios GUI
Click to expand...
Click to collapse
If It Recognized Ur Device It Will Work
And Please Add Details
Eg. What Error Message etc.
Hi there, i have tried to use the following software but it doesnt work
so basically I have a samsung G3 i9300T and I know the pattern code but i still want to try out.
firstly when i ran the Multi-tool, it doesn't recongized my phone. So i realized i have to turn on USB debugging in order to let the software to detect my phone.
So i have turned the usb debug mode on and it finally picks up my phone.
Press 1 and it has my serial number, good, good. Then I go to option 3 as you mentioned in order to unlock pattern lock.
It reboots, and the pattern lock is still sitting on screen. So i tried to swipe anywhere on the pattern lock but it doesnt allow me to go further unless i input the right code.
Now i am wondering what could went wrong?
Fossil_Sioux said:
Hi there, i have tried to use the following software but it doesnt work
so basically I have a samsung G3 i9300T and I know the pattern code but i still want to try out.
firstly when i ran the Multi-tool, it doesn't recongized my phone. So i realized i have to turn on USB debugging in order to let the software to detect my phone.
So i have turned the usb debug mode on and it finally picks up my phone.
Press 1 and it has my serial number, good, good. Then I go to option 3 as you mentioned in order to unlock pattern lock.
It reboots, and the pattern lock is still sitting on screen. So i tried to swipe anywhere on the pattern lock but it doesnt allow me to go further unless i input the right code.
Now i am wondering what could went wrong?
Click to expand...
Click to collapse
That Is The Exact Process
I'll test it On S3
Didn't work on Motorola XT901
Thanks for supplying such a tool, unfortunately I tried it and had the same result has Fossil_Sioux on a Motorola XT901. Phone is recognized and when I select option 2 it reboots, but the lock screen is still displayed. I enter in any random pin and it just prompts me to try again. Any suggestions?
thanks
thanks for your time in posting this information because i find it very helpful
Nice
Nice thread...thnx man.
Devill007 said:
Nice thread...thnx man.
Click to expand...
Click to collapse
Thanks
I plan to unlock my bootloader, but not rooting the phone yet, want to see if I can live without root. But in case I find out I couldn't I don't want to wipe my device again, thus unlocking now before actually moving all my stuff over from my old Nexus.
My question is, does it have any drawback to unlock bootloader? Does it actually affect anything (besides the hyper-annoying nag screen on boot), that would make it better just to leave it locked, and do the wipe and everything only if I ever decide to actually root it? Tough decision, I'd love to hear your opinions.
Thank you!
Assuming you aren't flashing TWRP, right?
Drawbacks... Security, maybe? Can't really think of anything else. OTAs will still work, as will all the usual upsides.
Upside, you can flash the latest factory images as soon as they are released.
PhoenixTank said:
Assuming you aren't flashing TWRP, right?
Click to expand...
Click to collapse
Yes, no flashing nothing, just a plain fastboot oem unlock, then pretending to be a basic user with a locked phone. I wonder if from the OS side anything can be perceived by apps, security/integrity checks, etc.
Yeah, then nothing in android will know, apart from the checkbox you need to enable in developer options.
Only when you change the boot or system images, does it really flag up anything. Hope that helps.
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
IVBela said:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
Click to expand...
Click to collapse
It stays checked. I haven't tried to unchecked it yet
IVBela said:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
Click to expand...
Click to collapse
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??
sordup said:
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??
Click to expand...
Click to collapse
This. So far this is the only drawback I found.
IVBela said:
This. So far this is the only drawback I found.
Click to expand...
Click to collapse
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
gleggie said:
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
Click to expand...
Click to collapse
It may work with casual thug. Sophisticated thief will turn device off, reboot into bootloader, wipe device and take possession. Device protection is meant to discourage theft.
https://support.google.com/nexus/answer/6172890?hl=en
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Jemmy Ducks said:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Click to expand...
Click to collapse
There are three sets of drivers needed. One for fastboot, one for adb and one for MTP. When device is in fastboot mode you use command "fastboot devices" or Mac equivalent.
gleggie said:
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
Click to expand...
Click to collapse
This doesn't help if they get your device and factory reset it. If they factory reset it before you have a chance to lock it down then you are screwed. With device protection even when you factory reset it, it will prompt for the previous google account the phone was set up with. If your bootloader is unlocked and they are knowledgeable thieves then they can just reflash everything and wipe it out fully.
I work at Swappa and we see this all the time. Someone will sell their device, factory reset it and send it to the buyer. The buyer gets it and can't set it up because device protection was enabled and it prompts them for the previous google account info that was tied to the phone when they try to set it up
Jemmy Ducks said:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Click to expand...
Click to collapse
I tried using fastboot anyway, despite seeing no devices listed, and lo and behold, it worked. Bootloader unlocked for flashing.
Hello there.
I have been having the 'stupidly set baseband to USA and unable to change back' issue with my Nexus 5x, using a European version. I live in Croatia, so as you would imagine this has meant a complete loss of signal/mobile operator/3g etc.
As per my other thread in Nexus 5x help and troubleshooting,
http://forum.xda-developers.com/nexus-5x/help/usa-baseband-set-european-model-t3252879
I have exhausted other options and have come to the realisation that as per other users issues with other phones that the use of QPST tools and using a clean QCN file to inject into my phone is the only course of action left. However, I have no knowledge of such things (not to say that I am unable to inform myself).
I emailed a developer with regards to users issues with Nexus 5 phones (not 5x), and he said that I need to enter this mode on my phone.
Could anyone help me out with this, and in general with this issue? As some have tried to help but unfortunately my thread has more of my own replies than other users. (In elaborating on steps taken to resolve my misery).
I am not looking for a 'one button fix', I have educated myself far and beyond with regards to this issue, I just need some more expert help so that I can sort this out myself.
Please, anyone?
Marko
Thank God.
I can actually get a new phone. Help not needed in the end.
Thanks anyway.
Marko
was.once.dead said:
Thank God.
I can actually get a new phone. Help not needed in the end.
Thanks anyway.
Marko
Click to expand...
Click to collapse
glad you got your probelm fixed dont know if this will help you or others but if you press *#*#4636#*#* your phone will enter a radio diagnostics tool where you can set your preferred network type and also select your radio baseband by using the 3 dots at the top. For my 5X i can select USA BAnd or Band mode 6, Band mode 7.
sorry if this is OT and not related to your issue.
Thank you for your input. However my phone does not have those options. Only USA band, which led to this week long stress for me. Im going to be able to get a replacement device in the end, so im happy about that, but this issue is unfortunately somewhat of a one way street wherin the usual simple solutions or even more complex adb, fastboot, etc etc things do not bring about any resolutions.
Again, thanks for trying to help but its a phone to phone kind of thing.
Marko
Best advice I can give. Don't mess with the basebands
zelendel said:
Best advice I can give. Don't mess with the basebands
Click to expand...
Click to collapse
Best advice ever...
But.... If you are really hot on getting the 5x into diagnostic mode to run QPST, QXDM, etc., do this. (I did this on my 5x to obtain the QCN file to check out the NV and EFS items, grab QXDM logs, etc.)
1. Use Heisenberg's most excellent step-by-step tutorial on unlocking the boot loader, rooting the phone, and installing super user apk.
2. Once rooted, connect the phone to a PC and open up adb, then issue the adb shell command.
3. Once in adb shell, type: su -c 'setprop sys.usb.config diag,adb'
4. At this point, you should see a pop up on the phone to authorize super user access. Click to allow access.
5. Now you will probably have to load a driver on the computer for diag access. I got lucky (since I have a mess of drivers on my computer) and the driver loaded automatically. As I recall, my computer selected qcusbser.sys. Seems to be a pretty generic QCOM driver vs. an LG specific driver.
6. You now have diag access. You will have to run steps 2 - 3 after each phone reboot. In other words, these steps aren't "sticky" between reboots.
7. ????
8. Profit
I did this and it worked for me.
clivemckracken said:
Best advice ever...
But.... If you are really hot on getting the 5x into diagnostic mode to run QPST, QXDM, etc., do this. (I did this on my 5x to obtain the QCN file to check out the NV and EFS items, grab QXDM logs, etc.)
1. Use Heisenberg's most excellent step-by-step tutorial on unlocking the boot loader, rooting the phone, and installing super user apk.
2. Once rooted, connect the phone to a PC and open up adb, then issue the adb shell command.
3. Once in adb shell, type: su -c 'setprop sys.usb.config diag,adb'
4. At this point, you should see a pop up on the phone to authorize super user access. Click to allow access.
5. Now you will probably have to load a driver on the computer for diag access. I got lucky (since I have a mess of drivers on my computer) and the driver loaded automatically. As I recall, my computer selected qcusbser.sys. Seems to be a pretty generic QCOM driver vs. an LG specific driver.
6. You now have diag access. You will have to run steps 2 - 3 after each phone reboot. In other words, these steps aren't "sticky" between reboots.
7. ????
8. Profit
I did this and it worked for me.
Click to expand...
Click to collapse
Please give me the global version of rfnv files:good:
Please give me the global version of rfnv files
Sorry, bro. I only have the values from my US version.
To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)
JTC Intl said:
To unlock Bootloader:
[NOTE: device with root access no longer receives official update notifications from the manufacturer)
Click to expand...
Click to collapse
Mine did until I went into Developer Setting and un ticked automatic software updates..
I thought I had found the perfect Z2 for me. Ordered on eBay for $130 with no scratches and very slight screen burn-in. I don't worry about light burn-in as I always use Substratum and turn all my screens amoled black with light text, I never notice the burn-in anyway.
Only problem was it being a T-Mo version but I couldn't unlock the bootloader. I did all that was required to receive the Unlock Code, however, when I input it the second time, it states "code verification failure." Verifed correct code multiple times and upon checking the Motorola unlock help thread, there is a list at the beginning with CID #s of bootloaders that can be unlocked and those that can not. Any CID not listed as "can be unlocked" are unable to be unlocked even if the # does not appear under "cannot be unlocked" list. My CID of 0x0015 was not on either list, therefore deemed unlockable.
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA
MrBrazil1911 said:
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA
Click to expand...
Click to collapse
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.
Ace42 said:
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.
Click to expand...
Click to collapse
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?
MrBrazil1911 said:
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?
Click to expand...
Click to collapse
Bands stay following SIM and Bootloader unlocks. But, when the modem of another model is flashed access to LTE is lost.
Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt
mike2246 said:
Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt
Click to expand...
Click to collapse
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.
41rw4lk said:
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.
Click to expand...
Click to collapse
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck
allrightlite said:
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck
Click to expand...
Click to collapse
3.0 ports won't be a problem for everyone, but for some it is. Some have only been able to use one port on their pc for flashing, some have had to use hubs to dumb their ports down. That's why it is generally recommended to use 2.0 port. Saves having to repeat the same info 100x in every other post.
This worked perfectly until the last step for my Sprint version of Z2 Force. Kudos to JTC Intl for crystal clear instructions.
When I launch the Magisk Manager , it asks me if I want to "Upgrade to full Magisk to finish set up. Download and install?" I respond OK, then after sometime, it says "There was a problem parsing the package".
Instead of v18 of Magisk, I downloaded v22 that too not as a ZIP, but it was only available as an APK from their GITHub. (https://github.com/topjohnwu/Magisk/releases/tag/v22.1)
EDIT - I tried the troubleshooting suggestions for this problem in their wiki ( clearing cache, clearing data, reinstalling etc). Did not help.
Please help. I'm almost there.
Thank you.
hi i need help is there any other way i can unlock the boot loader because when i enter my code it says device not eligible....
JTC Intl said:
To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)
Click to expand...
Click to collapse
Does rooting the phone work for an AT&T Moto Z2 force phone?