Hey I was following this guide and got to Part 2 A, flashing TWRP. I believe i followed every step but am unable to access recovery, when i try to from fastboot it simply turns off the phone, when i try to from ADB it says "no command" with a picture of the broken android . I tried a newer TWRP img but it did not change anything.
I am using Android 6.0 and the Moto G2 Dual sim. I have unlocked the bootloader, updated drivers and there is no errors. Please help.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.0.0-1-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (8264 KB)...
OKAY [ 0.286s]
writing 'recovery'...
OKAY [ 0.290s]
finished. total time: 0.578s
Apologies if i have made a mistake in this post or have not provided enough detail, i'm new to rooting and using forums. Thanks for any help!
Moto G2 Dual-SIM is not enough info.
You probably don't have a Moto Titan, but a Moto Thea.
Do you know the exact code name of your phone? XT106x or XT107x?
If you're not sure, download and flash TWRP for Thea. If your phone is a LTE (Thea), you should be able to continue the steps in that tutorial, BUT you will have to choose a ROM for Thea, not Titan.
FCorvin said:
Moto G2 Dual-SIM is not enough info.
You probably don't have a Moto Titan, but a Moto Thea.
Do you know the exact code name of your phone? XT106x or XT107x?
If you're not sure, download and flash TWRP for Thea. If your phone is a LTE (Thea), you should be able to continue the steps in that tutorial, BUT you will have to choose a ROM for Thea, not Titan.
Click to expand...
Click to collapse
Ah, i downloaded the titan version, i've just checked my model number and it is XT1068
RavingSmurf said:
Ah, i downloaded the titan version, i've just checked my model number and it is XT1068
Click to expand...
Click to collapse
I tried a download for the thea but it still didnt work, ill try find some more downloads.
No, XT1068 is indeed Titan. You got it right from the start.
Try the latest version from their site.
Did you succesfully unlock your phone? Check if your bootloader is unlocked in fastboot mode it must say "Device is UNLOCKED. Status code: 3". If it doesn't say that your bootloader is still locked.
FCorvin said:
No, XT1068 is indeed Titan. You got it right from the start.
Try the latest version from their site.
Click to expand...
Click to collapse
Ah ok ill try it again, thanks!
felipe_hdez said:
Did you succesfully unlock your phone? Check if your bootloader is unlocked in fastboot mode it must say "Device is UNLOCKED. Status code: 3". If it doesn't say that your bootloader is still locked.
Click to expand...
Click to collapse
Yeah i checked it thanks
Hey again, sorry for the delay. i tried it again, along with alot of other files but it hasnt worked. Maybe something is wrong with the phone?
The guide you mentioned does not show you how to actually unlock your phone; it gives you links to another guide and a YouTube video.
You checked those out, right?
FCorvin said:
The guide you mentioned does not show you how to actually unlock your phone; it gives you links to another guide and a YouTube video.
You checked those out, right?
Click to expand...
Click to collapse
Ive unlocked the phone but i didnt follow those guides, i have been using this.
Yes, that's the one you mentioned.
But look closely: it doesn't show you how to unlock anything - it gives you a link to another tutorial for unlocking and then skips to rooting.
So... how exactly did you unlock it?
FCorvin said:
Yes, that's the one you mentioned.
But look closely: it doesn't show you how to unlock anything - it gives you a link to another tutorial for unlocking and then skips to rooting.
So... how exactly did you unlock it?
Click to expand...
Click to collapse
Ah I see what you mean, i followed the Motorola guide. You have to make an account to see it though.
http://forum.xda-developers.com/attachment.php?attachmentid=3821476&stc=1&d=1469278472
Well, if you did paste the code correctly and hit enter, then your phone must be unlocked.
Although I'm not so sure. With updated drivers, USB debugging enabled in Developer options and Minimal ADB installed, you should have been able to perform miracles.
Type in a CMD window from within the ADB folder:
Code:
fastboot devices
What happens? If you do get the device, type further:
Code:
fastboot oem device-info
What does it say?
FCorvin said:
Well, if you did paste the code correctly and hit enter, then your phone must be unlocked.
Although I'm not so sure. With updated drivers, USB debugging enabled in Developer options and Minimal ADB installed, you should have been able to perform miracles.
Type in a CMD window from within the ADB folder:
Code:
fastboot devices
What happens? If you do get the device, type further:
Code:
fastboot oem device-info
What does it say?
Click to expand...
Click to collapse
Hey, it gave me an error message.
It doesn't look good
Unfortunately, I am out of suggestions for you.
Good luck.
Ok, Thanks anyway. I might contact motorola support but i doubt they would help
Related
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
cropythy said:
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
flashallthetime said:
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
Click to expand...
Click to collapse
I tried manually entering it (3 times) i have tried copying it directly, and I have tried copying into notepad and making sure there are no spaces, but it still says my devices is not eligible for a bootloader unlock. Guess I'm calling motorola after work tomorrow.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
I just tried unlocking a Rogers Canada phone and it told me the phone isn't eligible. It certainly should be and I know I'm doing everything correctly as I unlocked a different one a few days ago.
So being you're seeing the same thing my conclusion is that the backend server which the website communicates with to manage the unlocking is broken at the moment.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
Try it again today, so far from my testing the unlock website is working again.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
As others have said, you need a code. The reason is you have to see like five warnings that the warranty will be voided before you get the code. They want to make sure people can't use the "I didn't know it would void the warranty" response if something goes wrong.
GSM Dev Can't go into CWM recovery
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
hondamarlboro said:
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
Click to expand...
Click to collapse
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Volume UP is the "select"
lensgrabber said:
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Click to expand...
Click to collapse
Thank you!!! This is my first moto device and I don't know this manner. Successfully recovery into CWM. Thank you again!
Welcome.
Sent from my XT1053 using Tapatalk
Is possible, Lock bootloader ?
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
I'm trying to figure out the same thing. I followed motorola's instructions on reflashing https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images but it does not re-lock. It tells me "No valid PIV block in SP for userdata"
edit - deleted userdata and it locked, but i still get the warning screen on boot
warranty
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
vespadaddy said:
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
Click to expand...
Click to collapse
Anyone knows anything about that?
Also, is the image altered in any way after a unlock? or is it exactly the same as a factory reset?
---
edit:
apparently it is all fine
Requesting an unlock code will no longer void the device’s warranty
We will start posting return-to-factory software images
Click to expand...
Click to collapse
-- http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html
Why really lock?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
Why would you unroot and/or unlock?
If it is a dev edition, it will not hurt the warranty.
The reason for this phone is for unlocking, rooting, flashing and roming.
Once you have saved a nandroid with a custom recovery (TWRP) you can't mess anything up. Go crazy and have fun
Hello everyone,
I bought an HTC one off ebay, having in mind I would flash custom rom on the device which I prefer for obvious reasons. But each time I open Hasson2000 Tool to get ID token I get this error in command prompt below:
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
'error: device offline
I have tried searching for solutions but I cant get one to actually fix my own issue, I do know the HTC bootloader has been unlocked and rooted because I can boot to bootloader menu, boot to recovery mode and on top on the screen it says *****TAMPERED***** just below it says ***UNLOCKED*** I figured the previous owner tried locking bootloader before selling it off.
I noticed other commands dont work like reboot device on the tool probably because of that error or my htc is not recognised am not sure. am running Windows 8.1 Pro on my laptop.
What I have done so far
Rebooted phone several times
Rebooted my laptop several times
Unplugged and plugged in usb cable
Used different usb ports it recognises my htc because I can view my SD card or transfer files between laptop and phone.
Please guys I neeed your help with this, thanks.
WOW over 52 views and not a single reply thanks heart breaking
Infoseye said:
WOW over 52 views and not a single reply thanks heart breaking
Click to expand...
Click to collapse
try this
first relock the bootloader
"fastboot oem lock"
and then go to htcdev.com/bootloader and follow the steps to unlock it again
Boachti said:
try this
first relock the bootloader
"fastboot oem lock"
and then go to htcdev.com/bootloader and follow the steps to unlock it again
Click to expand...
Click to collapse
Okay I will give it a try and tell you the out come.
Infoseye said:
Okay I will give it a try and tell you the out come.
Click to expand...
Click to collapse
ok
Boachti said:
ok
Click to expand...
Click to collapse
Okay I have locked and relocked Bootloader, installed custom recovery. So what do I do now?
I got an OTA update from HTC for WIFI fix, I could not update via recovery it gave an error is it because the bootloader is locked?
Am on Kitkat 4.4.2, S-ON,TWRP,4.19.401.9, HTC_001 please how do I just restore it to original HTC stock not custom ROM?
Infoseye said:
I got an OTA update from HTC for WIFI fix, I could not update via recovery it gave an error is it because the bootloader is locked?
Click to expand...
Click to collapse
now unlock it again
go to htcdev.com/bootloader
Boachti said:
now unlock it again
go to htcdev.com/bootloader
Click to expand...
Click to collapse
I have unlocked it again its now unlocked, right now I just want to go back to original stock so that I can get updates official updates from HTC but unfortunately I dont have a copy of stock rom since I bought it off ebay already rooted.
Infoseye said:
I have unlocked it again its now unlocked, right now I just want to go back to original stock so that I can get updates official updates from HTC but unfortunately I dont have a copy of stock rom since I bought it off ebay already rooted.
Click to expand...
Click to collapse
Depending on the carrier the device was made for and the one you use, OTA updates may not be an option. If it is a carrier device then updates will be pushed OTA from the OG carrier. IF you use a different carrier then you wont get OTA. And to be honest they are over rated and cause more issues then anything else.
zelendel said:
Depending on the carrier the device was made for and the one you use, OTA updates may not be an option. If it is a carrier device then updates will be pushed OTA from the OG carrier. IF you use a different carrier then you wont get OTA. And to be honest they are over rated and cause more issues then anything else.
Click to expand...
Click to collapse
Its unbranded HTC One unlocked its not locked to any carrier, so are you saying I cant go back to a stock or use a nand backup from this forum. I have found alot of topics but the procedures are abit confusing can you direct me a link or thread that can directing on how to flash a custom rom on my HTC?
Infoseye said:
Hello everyone,
I bought an HTC one off ebay, having in mind I would flash custom rom on the device which I prefer for obvious reasons. But each time I open Hasson2000 Tool to get ID token I get this error in command prompt below:
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
'error: device offline
I have tried searching for solutions but I cant get one to actually fix my own issue, I do know the HTC bootloader has been unlocked and rooted because I can boot to bootloader menu, boot to recovery mode and on top on the screen it says *****TAMPERED***** just below it says ***UNLOCKED*** I figured the previous owner tried locking bootloader before selling it off.
I noticed other commands dont work like reboot device on the tool probably because of that error or my htc is not recognised am not sure. am running Windows 8.1 Pro on my laptop.
What I have done so far
Rebooted phone several times
Rebooted my laptop several times
Unplugged and plugged in usb cable
Used different usb ports it recognises my htc because I can view my SD card or transfer files between laptop and phone.
Please guys I neeed your help with this, thanks.
Click to expand...
Click to collapse
What about using the command prompt instead of a toolkit? No disrespect to Hasson2000, but toolkits aren't ideal imo
In most cases, ''device offline'' is caused by an outdated version of the android sdk or a bad usb cable/usb port (btw use usb 2.0 ports).
Also in windows devices manager, your phone must be listed as Android usb device ---> My HTC. If not, you have drivers issue.
If your phone still boot normally, just copy the rom inside the sdcard, reboot in recovery and install it. I will highly suggest you make sure adb and fastboot works correctly before as they will be required if something goes wrong when installing the custom rom. Also make a nandroid backup of your current config before flashing the rom and make a copy of that backup on your computer.
alray said:
What about using the command prompt instead of a toolkit? No disrespect to Hasson2000, but toolkits aren't ideal imo
In most cases, ''device offline'' is caused by an outdated version of the android sdk or a bad usb cable/usb port (btw use usb 2.0 ports).
Also in windows devices manager, your phone must be listed as Android usb device ---> My HTC. If not, you have drivers issue.
If your phone still boot normally, just copy the rom inside the sdcard, reboot in recovery and install it. I will highly suggest you make sure adb and fastboot works correctly before as they will be required if something goes wrong when installing the custom rom. Also make a nandroid backup of your current config before flashing the rom and make a copy of that backup on your computer.
Click to expand...
Click to collapse
Well actually I used command prompt since the Hasson2000 tool did not work, Yes my HTC displays under device manager when plugged in. I think its my adb that is out of date.
How do I update my adb?
Infoseye said:
Well actually I used command prompt since the Hasson2000 tool did not work, Yes my HTC displays under device manager when plugged in. I think its my adb that is out of date.
How do I update my adb?
Click to expand...
Click to collapse
what is the output of
Code:
adb version
?
alray said:
what is the output of
Code:
adb version
?
Click to expand...
Click to collapse
I dont undertsand what you mean by adb version, how do find out the version am a newbie to all this stuff
Infoseye said:
I dont undertsand what you mean by adb version, how do find out the version am a newbie to all this stuff
Click to expand...
Click to collapse
open a cmd prompt from your adb/fastboot folder and type ''adb version'' and hit enter.
alray said:
what is the output of
Code:
adb version
?
Click to expand...
Click to collapse
C:\adb>adb version
Android Debug Bridge version 1.0.26 what do I do next?
Infoseye said:
C:\adb>adb version
Android Debug Bridge version 1.0.26 what do I do next?
Click to expand...
Click to collapse
1.0.26 is outdated.
Go here and download the sdk.
alray said:
1.0.26 is outdated.
Go here and download the sdk.
Click to expand...
Click to collapse
I downloaded another Android Debug Bridge version 1.0.31
In fastboot mode where it is supposed to say device is unlocked or device is locked my device says "DEVICE IS ENGINEERING".
Also when I try to unlock the bootloader in WUG's toolkit it says everything ran correctly but when the device reboots it is still locked and never even reset.
I am trying to upgrade android as I am currently in a developer preview. How can I unlock my bootloader to upgrade to the latest stock version of android M?:
Why do people use toolkits on a Nexus device? I know it's just "click, click, click, score!", but only until something goes wrong (and eventually it does go wrong), and there they are totally out of practice to use the basic adb and fastboot commands.
So you should try fastboot, and copy here its output, then maybe somebody will know how to help.
How did you get to have a developer preview? I have a poor memory, but I think it had to be installed manually, and I'm pretty sure that you had to be unlocked to install manually? Can someone with a better memory comment?
Have you even tested fastboot flashing (manually)? I cant imaging an engineering device with a locked bootloader. That said, lets hope the hardware in that thing is identical to the Nexus 6 otherwise flashing something could break it. fastboot boot twrp.img should be the first test as it does not flash anything and should give an indication by the recovery boot being successful that the hardware is at least mostly, identical.
i have same problem, have you found a solution?
I am having same problem. I Installed the MRA58K a month ago and now trying to upgrade to MRA58R, using the Nexus Root Toolkit, I can't get the boot loader unlocked , it says device is engineering.
Please advise if you know the solution.
Thanks
frusso21 said:
In fastboot mode where it is supposed to say device is unlocked or device is locked my device says "DEVICE IS ENGINEERING".
Also when I try to unlock the bootloader in WUG's toolkit it says everything ran correctly but when the device reboots it is still locked and never even reset.
I am trying to upgrade android as I am currently in a developer preview. How can I unlock my bootloader to upgrade to the latest stock version of android M?:
Click to expand...
Click to collapse
1. Don't use toolkits, type commands one by one.
2. Try the new unlock command: fastboot flashing unlock
3. If it still doesn't work, paste the output here, and people will know if they can help or not.
Also: How did you install MRA58K?
istperson said:
1. Don't use toolkits, type commands one by one.
Click to expand...
Click to collapse
+1! Read and do it manually!
Make sure that "OEM unlocking" in developer options is enabled
OEM unlocking is enabled
Droidphilev said:
+1! Read and do it manually!
Make sure that "OEM unlocking" in developer options is enabled
Click to expand...
Click to collapse
OEM unlocking is enabled
istperson said:
2. Try the new unlock command: fastboot flashing unlock
Click to expand...
Click to collapse
Hello, can you explain? i only know the command "fastboot oem unlock"
Droidphilev said:
Hello, can you explain? i only know the command "fastboot oem unlock"
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/verified-boot.html
istperson said:
https://source.android.com/security/verifiedboot/verified-boot.html
Click to expand...
Click to collapse
Thanks for the link but this is too complicated for me. I unlocked using "fastboot oem unlock". I was on Lollipop back then. Should i run this new command also now? I don't understand the difference between 'old' and 'new'.
Thanks!
Droidphilev said:
Thanks for the link but this is too complicated for me. I unlocked using "fastboot oem unlock". I was on Lollipop back then. Should i run this new command also now? I don't understand the difference between 'old' and 'new'.
Thanks!
Click to expand...
Click to collapse
It's not a new state, they just changed the command.
Code:
void usage(void)
{
fprintf(stderr,
/* 1234567890123456789012345678901234567890123456789012345678901234567890123456 */
"usage: fastboot [ <option> ] <command>\n"
"\n"
"commands:\n"
" update <filename> reflash device from update.zip\n"
" flashall flash boot, system, vendor and if found,\n"
" recovery\n"
" flash <partition> [ <filename> ] write a file to a flash partition\n"
" flashing lock locks the device. Prevents flashing"
" partitions\n"
" flashing unlock unlocks the device. Allows user to"
" flash any partition except the ones"
" that are related to bootloader\n"
" flashing lock_critical Prevents flashing bootloader related"
" partitions\n"
" flashing unlock_critical Enables flashing bootloader related"
" partitions\n"
" flashing get_unlock_ability Queries bootloader to see if the"
" device is unlocked\n"
Code:
} else if(!strcmp(*argv, "oem")) {
argc = do_oem_command(argc, argv);
} else if(!strcmp(*argv, "flashing") && argc == 2) {
if(!strcmp(*(argv+1), "unlock") || !strcmp(*(argv+1), "lock")
|| !strcmp(*(argv+1), "unlock_critical")
|| !strcmp(*(argv+1), "lock_critical")
|| !strcmp(*(argv+1), "get_unlock_ability")) {
argc = do_oem_command(argc, argv);
} else {
usage();
return 1;
}
istperson said:
It's not a new state, they just changed the command.
Click to expand...
Click to collapse
I see. Probably the old command still works? It's still here:
https://developers.google.com/android/nexus/images?hl=en
Droidphilev said:
I see. Probably the old command still works? It's still here:
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
The page is not up to date, I bet they'll change it to flashing too soon. The command still works, see above, but it's not checked anymore for syntax, so it's only kept for compatibility reasons, but it's treated as obsolete.
istperson said:
The page is not up to date, I bet they'll change it to flashing too soon. The command still works, see above, but it's not checked anymore for syntax, so it's only kept for compatibility reasons, but it's treated as obsolete.
Click to expand...
Click to collapse
I see, thanks for all!
Ill be honest. If typing commands or following the directions on the nexus google site is too complicated for you then to be honest leave your device stock. Dont go messing with something you dont understand or you will end up with a brick and no one will help you fix it.
istperson said:
https://source.android.com/security/verifiedboot/verified-boot.html
Click to expand...
Click to collapse
My friend, i'm sorry that i lost the link but yesterday i have read somewhere that this new command is for 6P only. Don't know if that's correct. Just FYI.
Droidphilev said:
My friend, i'm sorry that i lost the link but yesterday i have read somewhere that this new command is for 6P only. Don't know if that's correct. Just FYI.
Click to expand...
Click to collapse
If looking at the source, the main command in fastboot is flashing, and OEM is the compatibility one. But I'm sure to use flashing you need a new bootloader that can actually understand it, because fastboot only sends the command, and it's the bootloader that does the unlocking.
So it's possible that the bootloaders up to 58R were not updated to the new commands. Maybe I can check it...
But only later, my virtualbox is acting up.
istperson said:
If looking at the source, the main command in fastboot is flashing, and OEM is the compatibility one. But I'm sure to use flashing you need a new bootloader that can actually understand it, because fastboot only sends the command, and it's the bootloader that does the unlocking.
So it's possible that the bootloaders up to 58R were not updated to the new commands. Maybe I can check it...
But only later, my virtualbox is acting up.
Click to expand...
Click to collapse
No need to do any further investigation. I think we will soon know when the 'old' command doesn't work anymore.
But since you are able to check such things: are you also able to check whether a bootloader is downgradable (in the future)? Would be much more interesting IMHO!
Thanks for your time!
Droidphilev said:
No need to do any further investigation. I think we will soon know when the 'old' command doesn't work anymore.
But since you are able to check such things: are you also able to check whether a bootloader is downgradable (in the future)? Would be much more interesting IMHO!
Thanks for your time!
Click to expand...
Click to collapse
Well, I checked it anyway, and the result was:
Code:
$ fastboot flashing unlock
...
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot oem unlock
...
(bootloader) Device state transition will erase userdata.
(bootloader) Are you sure you want to continue this transition?
(bootloader)
(bootloader) Press POWER key to continue.
(bootloader) Press VOL UP or VOL DOWN key to cancel state transition.
(bootloader) State transition canceled!
OKAY [ 69.909s]
finished. total time: 69.909s
I didn't try if it erases the phone even if it was unlocked.
As for downgrading, I don't know if it's a problem, but it hasn't changed since the last preview.
hai guys i tried to unlock bootloader by official sony method by selecting xperia xz(because xz1c not listed) and got my unlock code by my imei,but when i hit the unlock command ,its not working, can someone please help me to unlock my bootloader i am on the version(47.1.a.8.49), one more doubt is as iam on the latest version(1st december 2017 security patch) does the twrp for the older security patch works for my version,because i didnt find the proper twrp for the latest security patch
jinishpv said:
hai guys i tried to unlock bootloader by official sony method by selecting xperia xz(because xz1c not listed) and got my unlock code by my imei,but when i hit the unlock command ,its not working, can someone please help me to unlock my bootloader i am on the version(47.1.a.8.49), one more doubt is as iam on the latest version(1st december 2017 security patch) does the twrp for the older security patch works for my version,because i didnt find the proper twrp for the latest security patch
Click to expand...
Click to collapse
Did you enable OEM unlocking in the developer options?
You know you're going to lose you camera right? I mean no pictures whatsoever.
No I'm not sure TWRP is working for December update yet.
You can't flash old version TWRP with new 47.1.A.8.49
Didgesteve said:
You know you're going to lose you camera right? I mean no pictures whatsoever.
Click to expand...
Click to collapse
There's actually a recently released DRM fix, which reportedly fixes the camera: https://forum.xda-developers.com/xp...lopment/oreo-xz1c-drmfix-root-ricoff-t3727029
Didgesteve said:
No I'm not sure TWRP is working for December update yet.
Click to expand...
Click to collapse
modpunk just updated TWRP with December security patch: https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
BetaLyte said:
There's actually a recently released DRM fix, which reportedly fixes the camera: https://forum.xda-developers.com/xp...lopment/oreo-xz1c-drmfix-root-ricoff-t3727029
modpunk just updated TWRP with December security patch: https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Click to expand...
Click to collapse
My mistake, it's only been out a day so I hadn't spotted it.
Looks like there's some success on the thread, but I'll hold back a bit before I jump.
Didgesteve said:
Looks like there's some success on the thread, but I'll hold back a bit before I jump.
Click to expand...
Click to collapse
Yeah, me too. sToRm// is taking a look at it, at will include it in XperiFix. But it's still important to notice, that it's a fix, and not a DRM backup / restore solution, so the original TA partition / DRM keys will still be lost and won't be recoverable.
BetaLyte said:
Yeah, me too. sToRm// is taking a look at it, at will include it in XperiFix. But it's still important to notice, that it's a fix, and not a DRM backup / restore solution, so the original TA partition / DRM keys will still be lost and won't be recoverable.
Click to expand...
Click to collapse
Yes, it's a one way step and you're reliant on the developer bringing a new version of the fix each time there's a firmware update.
No offence to the developer, but I know nothing of M-Rom or aledoom, it would be good to know a little of their background before I open my phone to some software from a unkown forum.
Since nobody bothered to give an answer...
1. Go to the Sony Bootloader Unlock page here
2. Follow the steps for the Xperia XZ
3. Get the email, click the link, type in your IMEI
4. Follow the instructions on the page.
lokio27 said:
Since nobody bothered to give an answer...
1. Go to the Sony Bootloader Unlock page here
2. Follow the steps for the Xperia XZ
3. Get the email, click the link, type in your IMEI
4. Follow the instructions on the page.
Click to expand...
Click to collapse
It looks more like you didn't bother to read OP's post.
He has already done all that, he's asking why the unlock command isn't working.
Unfortunately, up until recently, unlocking the bootloader on this phone is extremely unappealing, so like almost no one has tried unlocking it, and those who did probably didn't run into this problem, so no one was able to offer an actual answer.
The first reply actually provided some suggestions. If you bothered to read.
mhaha said:
It looks more like you didn't bother to read OP's post.
He has already done all that, he's asking why the unlock command isn't working.
Unfortunately, up until recently, unlocking the bootloader on this phone is extremely unappealing, so like almost no one has tried unlocking it, and those who did probably didn't run into this problem, so no one was able to offer an actual answer.
The first reply actually provided some suggestions. If you bothered to read.
Click to expand...
Click to collapse
I couldn't find any help anywhere when I was looking for help on that, so I felt like a post was needed in general.
problem solved
tried bootloaderunlock on my desktop pc and it worked,flashed latest twrp ,flashed drm fix every thing is working fine,anyone had sucess in magisk and viper4android?
jinishpv said:
tried bootloaderunlock on my desktop pc and it worked,flashed latest twrp ,flashed drm fix every thing is working fine,anyone had sucess in magisk and viper4android?
Click to expand...
Click to collapse
Hi, I have maybe the same issue :
Code:
fastboot -i 0x0fce oem unlock 0xMyKey
returns only
Code:
...
and seems stuck : nothing happens.
So I would like to unlock my bootloader, but I cannot manage to do it (of course *#*#7378423#*#* then Service info > Configuration > Rooting Status Bootloader unlock allowed says Yes).
How did you manage to unlock your bootloader?
OldBeurt said:
How did you manage to unlock your bootloader?
Click to expand...
Click to collapse
I did not find a proper solution. It is still impossible to unlock my XZ1c with my laptop. Fortunately, I did manage to unlock it using my (very) old former laptop (it’s 32 bits, I had to use the old ADB v23), and it worked like a charm.
I don’t know why it failed on my current laptop (either with my usual OS Linux, nor with Windows 10).
Old thread is old? i don't care. because i want to say that looks like Sony finally give the XZ1c into the data base and there is a hot to guide over the Dev mode of the Phone. i will past the Sony guide to it here so this info will spread where it needed:
"To be able to unlock your Xperia XZ1 Compact, prepare it by following these steps:
Go into Settings > About phone and tap seven times on Build number to enable developer options.
From Settings, go into Developer options and enable OEM unlocking.
Warning:
Camera stops working on certain software releases.
Device protection features will not work on this device while this setting is turned on. Note: It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialer and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
"
Source: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
/€: Again, you guys are way to deep into the matter and i found several things that was never mention by any tutorial.
after several testings and also failings i will add: under windows 10, you have to check the Drivers double and make sure you use one that works!
EVEN IF IT APPEARS THAT THE DRIVER IS CORRECT IT MAY NOT THE CASE!
To check this you have to use "ADB DEVICES" and "FASTBOOT DEVICES".
Only if your device appears in the list IN BOTH (!) cases the driver setting is correct. This is very important.
Also you have to consider that after reboot into bootloader ("adb reboot bootloader") the device will NOT RECOGNIZE (!) by windows and appears as new device without any driver! (check Device Manager for this) so you can't access it in that state EVEN it was recognized before!
You have to install the Google Android USB Driver in this case. Also you have to check if the device appears still in both (adb, fastboot) lists.
Only then you can preform the Guides correctly!
summary: you have to install two (!) driver to get proper access to your device, one driver can only be installed in a certain state of your device (bootloader state) you have to make sure that your device is accessible in all states to preform your unlocking AND img pushing correctly.
Your bootloader is unlocked if on Power up the message appears "Your device has been is unlocked and can't be trusted. Your device will boot in 5 seconds"
...and now i go and found a way to get rid of the "non access on external cards for apps" _feature_ ...ands no all the tools and images and guides DON'T WORK.
muhschaf said:
To check this you have to use "ADB DEVICES" and "FASTBOOT DEVICES".
Only if your device appears in the list IN BOTH (!) cases the driver setting is correct. This is very important.
Click to expand...
Click to collapse
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
mosbyxz1c said:
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
Click to expand...
Click to collapse
Have you checked that your phone can be unlocked?
Some providers sell phones that can't be unlocked so that they don't have to deal with the warranty mess.
Open your phone and type *#*#7378423#*#* - then look under Service info\Configuration under Rooting status it should say Bootloader unlock allowed: Yes
If it says No, then you need to stop, there is no way round this.
Didgesteve said:
Have you checked that your phone can be unlocked?
Some providers sell phones that can't be unlocked so that they don't have to deal with the warranty mess.
Open your phone and type *#*#7378423#*#* - then look under Service info\Configuration under Rooting status it should say Bootloader unlock allowed: Yes
If it says No, then you need to stop, there is no way round this.
Click to expand...
Click to collapse
I bought it straight from amazon without any carriers but yes it is allowed (that's what I meant with "settings show it's possible", sorry if that was unclear).
I just double checked, just to be 100% sure. And yes:
Rooting status:
bootloader unlock allowed: Yes
mosbyxz1c said:
I bought it straight from amazon without any carriers but yes it is allowed (that's what I meant with "settings show it's possible", sorry if that was unclear).
I just double checked, just to be 100% sure. And yes:
Rooting status:
bootloader unlock allowed: Yes
Click to expand...
Click to collapse
Presumably you've enabled OEM unlocking in the developer options?
Otherwise it's a driver problem, good luck with that.
mosbyxz1c said:
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere.
Click to expand...
Click to collapse
I got the same problem, I just removed the "-i 0x0fc" part, so it became "fastboot oem unlock 0x<insert your unlock code>".
I think there may be a newer version of fastboot that lacks the -i option.
Nerre said:
I got the same problem, I just removed the "-i 0x0fc" part, so it became "fastboot oem unlock 0x<insert your unlock code>".
I think there may be a newer version of fastboot that lacks the -i option.
Click to expand...
Click to collapse
Thanks for trying to help.
Got a little hopeful but now i get a
Code:
FAILED (remote: Command did not succeed)
I'm going crazy... I'm really thinking about setting up a dualboot linux (or boot from usb). you guys think thats useful? I have no problems with drivers at least. If yes, ubuntu enough? I don't have a lot of linux experience..
mosbyxz1c said:
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
Click to expand...
Click to collapse
Your mention of "Volume up" button indicates that your try to reboot it per button pressing. Try to avoid that. Your device should reboot by typing in the fast boot command and press enter. then you have to check the driver state in the Device manager and their install the correct driver (Google ADB driver). Don't unplug your Phone during this.
Im trying to unlock the bootloader on this phone. with no luck. Ive followed various guides on here.
fastboot devices/adb devices both recognize it. I was able to get the token identifier. which i used on motorola's website for the unlock.
it first told me that it was missing a puid... then it told me it couldnt be unlocked. i used adb reboot-bootloader to get the phone into fastboot mode. 95% of the commands come back failed (remote not implement)
I need help please.
Thats lame. I really want to mod this phone
Naksuhd said:
Thats lame. I really want to mod this phone
Click to expand...
Click to collapse
Hello!
If you want to unlock the bootloader of G50 you need special fastboot from Motorola. Im attaching it in reply. Also you need to have bootloader unlock code.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/ here you can optain your code. You can ask me if you need more. Also i made a guide how to install GSI on moto G50 if you want.
I hope that i helped.