I have followed the guides to the best of my ablity
This is the procedure I followed: From this thread
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
FAILED (remote: oem unlock is not allowed)
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.100s]
finished. total time: 0.100s
I then tried to downgrade to s19, but does not seem to work.
Anyway, if anyone has any ideas it would be welcomed, thank you
Is there an option you can turn on in dev options called "allow bootloader unlocks"? Because my mom's Le 2 has it and I assume it allows the unlock to go through. Are you on a vendor ROM? Flash the original stock Chinese 18s for your device.
Closest setting like that I have is the "OEM unlock" and I have it enabled
Well, did you have it enabled back when you were trying to unlock it? Because not having it enabled is usually what causes the unlock to fail.
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
I will try this asap, thanks
Woot! that worked
Hey can i lock the bootloaded after I am done? I want to use like android pay and stuff
Well I figured out I can relock it, bit now my issue is when I am in fastboot mode adb does not see the device...
I installed the drivers, did not work....
Even went to my wife's laptop that I have never once plugged my phone in to... Installed adb, and plugged in the phone in fastboot... Still not being seen when I do an "adb devices"
I really want to use android pay
Don't understand
slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
bobster82 said:
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
Make sure ur files are in the right directory or cd to where they are.
bobster82 said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
You may need to do the XBL as well:
Then
Run
and then
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
You need adb installed on your computer.
You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.
thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?
bobster82 said:
thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?
Click to expand...
Click to collapse
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium
mchlbenner said:
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727
bobster82 said:
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727
Click to expand...
Click to collapse
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium
mchlbenner said:
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
see this the only thing I don't understand. I booted into fastboot and attempted to flash the files eemc and the xl files to unlock bootloader. The first try gave me an error and then the screen went black and has not come back on yet. No vibrations,no lights, no nothing.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
sk8223 said:
You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.
Click to expand...
Click to collapse
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?
bobster82 said:
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?
Click to expand...
Click to collapse
Well, I simply rephrased slgooding's post in this thread. See the first page. And by brick, I assume you only have fastboot working.
Try the other commands: https://forum.xda-developers.com/showpost.php?p=74123111&postcount=5
hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?
bobster82 said:
hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?
Click to expand...
Click to collapse
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium
mchlbenner said:
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Hi I made sure I downloaded the correct twrp recovery and when I command in prompt its telling me now that it cannot load the image error. the build is Le_zl1 -eng 6.0.1 WAXCNFN5841510281D eng.letv.
I'm almost fixing to give up cause no matter what I do I cannot get into twrp recovery
Related
It took me about two days to figure out how to unroot and relock my Moto X. Figured I'd create a total noob guide for those who are also looking to do the same. This is for the Verizon Wireless Developer Edition Moto X ONLY! I have no clue if this will work for other variants like Sprint, AT&T, T-Mobile, etc. So just play it safe and don't...
I've unrooted and relocked my VZW Dev Edition Moto X twice using this method, so as long as you follow the steps below you should be fine. Also please note that I'm not at all responsible for anything that happens to your beloved phone.
Btw, this process wipes your phone completely clean, so back your sh** up.
So here goes.
1. You need a Windows PC.
2. Download and install the Motorola Device Manager (USB Drivers) to your PC. This will allow your Moto X to be recognized by your computer.
3. Plug your Moto X into your PC and let the drivers install automatically.
4. Download and unzip the VZW Developer Edition Factory Image for the Moto X to your desktop.
5. Download both the fastboot.exe and AdbWinApi.dll files and place them in the folder you just unzipped in step step 4.
6. Now grab your Moto X, unplug it from your PC and power it off. Once powered off, press and hold both the Power and Volume Down buttons for about 10 seconds or so to access Fastboot mode.
7. Now, back on your PC, open the folder you extracted on Step 4. Hold down the Shift key on your keyboard and Right Click on an empty space within that folder. From the menu that pops up, click on Open command window here. A command prompt window should open. Plug your phone back into your PC.
8. In the command prompt type fastboot devices to make sure your X is being detected. You should see something similar T0620059GA. If you don't see it, then you may have to reinstall the USB Drivers from Step 2.
9. Once your X has been detected by your computer, and while still in Fastboot mode, type the following commands (in the order shown) into the command prompt on your PC:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase cache
fastboot oem lock
fastboot reboot
...
That's it! You should now be locked and unrooted; back to the out of the box factory state. Don't forget to hit thanks and share!
Did re-locking ur bootloader get rid of the Bootloader Unlocked Warning Message?
tonyf7 said:
7. Now, back on your PC, open the folder you extracted on Step 4. Hold down the Shift key on your keyboard and Left Click on an empty space within that folder. From the menu that pops up, click on Open command window here. A command prompt window should open. Plug your phone back into your PC.
Click to expand...
Click to collapse
Right click sir.
mschumacher69 said:
Did re-locking ur bootloader get rid of the Bootloader Unlocked Warning Message?
Click to expand...
Click to collapse
Yes.
tonyf7 said:
Yes.
Click to expand...
Click to collapse
Just to make sure we're on the same page here, after re-locking ur bootloader, when u boot the phone, u get the Moto logo instead of the message that says Warning Bootloader Unlocked?
Because many other users said that u would still get this message even if u re-lock ur bootloader.
When I relocked the bootloader and rebooted the phone I didn't get the warning message. Went straight to the Moto logo. But then I immediately rooted and unlocked again. Only reason I unrooted and relocked in the first place was because I flashed a zip file that corrupted and broke Google Voice Search on my phone.
The second time I did this process I stopped right before locking the bootloader since I was going to root again anyways.
So maybe those other people are right. I've only rebooted my phone once since relocking the bootloader.
Sent from my XT1060 using xda app-developers app
If you want to get rid of the warning on startup, just flash the logo.bin. You can do this and remain unlocked. The instructions provided should have your phone looking and acting the same as it did out of the box. However, fastboot may note that it's been unlocked, to the OP, do you recall what status fastboot was reporting?
you need to reflash to stock in order to lock your bootloader? If not, I would appreciate if you separate the steps to just lock your boot loader.
I have my boot loader unlocked and the only reason I am considering to lock it again is so that if the phone is stolen, someone can't reimage it easily. I'm not sure that gives me any sort of protection though. But its just a thought.
In other words, I see unlocking and locking as a switch that stops you from flashing firmware. The OP makes it sound like the switch is tied to the firmware, ie only stock can have bootloader locked. I am not sure which is right.
esidnD Selim
I did it and keep receiving the warning unlock bootloader screen.
lopescesar304 said:
I did it and keep receiving the warning unlock bootloader screen.
Click to expand...
Click to collapse
Did u re-lock on your phone's ROM or after flashing another carrier's ROM?
mschumacher69 said:
Did u re-lock on your phone's ROM or after flashing another carrier's ROM?
Click to expand...
Click to collapse
My phone is Retail, I used the retail ROM to flash.
My device won't lock. I've run your commands listed, as well as the fastboot oem lock on it's own, and I can't seem to lock the device. Any help?
flavinator said:
My device won't lock. I've run your commands listed, as well as the fastboot oem lock on it's own, and I can't seem to lock the device. Any help?
Click to expand...
Click to collapse
Welcome to the "Relock" party..
The OP does not mention (that I can see) what OS version..are you on KK 4.4 and is there a "Factory Image" for KK 4.4 available for your device.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
NWKENT said:
Welcome to the "Relock" party..
The OP does not mention (that I can see) what OS version..are you on KK 4.4 and is there a "Factory Image" for KK 4.4 available for your device.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Click to expand...
Click to collapse
Yes, there is, flashed it, ran commands, and the relock command, multiple times and get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.120s]
finished. total time: 0.122s
Not sure what I am doing wrong.
flavinator said:
Yes, there is, flashed it, ran commands, and the relock command, multiple times and get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.120s]
finished. total time: 0.122s
Not sure what I am doing wrong.
Click to expand...
Click to collapse
I'd think you ran this as the first flash >> fastboot oem lock begin first!
Then all the OS files and then this for the last command >> fastboot oem lock > as the last command.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
http://forum.xda-developers.com/showthread.php?t=2575586
NWKENT said:
I'd think you ran this as the first flash >> fastboot oem lock begin first!
Then all the OS files and then this for the last command >> fastboot oem lock > as the last command.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Click to expand...
Click to collapse
I have no clue. At first I just flashed back using RSD Lite. Then I ran the lock command and got that error. Afterwards, I searched online, trying a bunch of different fastboots. That's when I stumbled on this list of commands, figured I'd run it from scratch, see if it makes a difference. Once it got to the relock command though, I got the same issue. And now I'm just frustrated...
---------- Post added at 06:41 PM ---------- Previous post was at 06:36 PM ----------
shane1 said:
http://forum.xda-developers.com/showthread.php?t=2575586
Click to expand...
Click to collapse
I think this might work, thanks shane1
@NWKENT have u managed to re-lock your bootloader yet?
mschumacher69 said:
@NWKENT have u managed to re-lock your bootloader yet?
Click to expand...
Click to collapse
Yes Sir..with Kit Kat 4.4..I have successfully"Unlocked", "Relocked" and "Unlocked" again..my XT1080MDEV (Droid Maxx)..No one could tell me exactly how to do it..Motorola Tech Line was absolutely NO HELP either..SO..after hours upon hours..I did figure it out..Now I'm working on "Relock" on JB 4.2.2
Sounds easy..and many have probably "Unlocked and "Relocked" on JB 4.2.2..BUT..The difficult part is once the XT1080 has been on KK 4.4..is when alot more firey hoops must be jumped thru..
ANYONE can chime in with help on this..NOT ADVICE..but proven procedures..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Yes, thanks guys.
Hey guys! Is there any way to unlock Redmi Pro's bootloader without waiting for permission from Xiaomi? Have anybody found a way to bypass it?
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
hello i haven't on my xiaomi redmi pro eom unlock in the devlopper mode help me pls
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
press in settings about phone 7 time on miui version
after that you will find developer options in aditional settings
criszz said:
press in settings about phone 7 time on miui version
after that you will find developer options in aditional settings
Click to expand...
Click to collapse
Sadly there is no oem unlock option in developer options. I'm on MIUI 8.1.2.0 Stable (MHQCNDI)
EDIT: i just switched to Developer ROM and still nothing.
sorry, my mistake i use another laguage, activate usb debuging , conect to the pc and run adb , if some permision asked alow
I can't unlock it using fastboot oem unlock since it's mediatek device =/ When I try I get
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.016s"
Click to expand...
Click to collapse
i unlocked that way, maybe you do something wrong
try another way without unlocking try flash twrp with spflash tool
Do you remember what miui version did you have when you unlocked this way? Maybe I can roll back to it and then try again. Were you using developer or stable rom?
i was on fake/vendor rom this i thinlk http://blog.geekbuying.com/index.ph...ndroid-6-0-smartphone-firmware-212302-161109/
Crissz, your bootloader was allready unlocked when you received your phone. You cannot do a simple oem unlock via fastboot with a xiaomi phone. It's a fact..
@KarKlim please try fastboot oem unlock-go comand too
This method does not work as many say
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Redmi Pro with Latest stable china rom
Is it possible? Xiaomi regoke my unclock previleges and now i have my Redmi Pro stuck in China Developer Rom. No way to install multilanguase Xiaomi.eu... can someone help please?
Maybe try with a new xiaomi account with different sim card.
And then from a different internet ip, from your friend or something.
I have no idea how they collect data or what. I'm just guessing here.
wow great news for Xiaomi lovers:
wow great news for Xiaomi lovers:
GeekBuying offering 73% off ( Xiaomi Redmi Pro 3GB + 64GB) 184.65 EURO
spam, all post of this user is spam
So, I bought my Redmi Pro today and i want to install xiaomi.eu ROM. Do I have to unlock bootloader first? Or can I do it with unlock bootloader?
No OEM in my xiaomi redmi pro
[[/B]
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
Can you help me please because I don't have a OEM unlock option in redmi pro and how to unlock bootloader... please man
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
Not worked for redmi note 8 pro ......failed.....
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
minimale_ldz said:
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
Click to expand...
Click to collapse
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
pldeep said:
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
Click to expand...
Click to collapse
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
minimale_ldz said:
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
Click to expand...
Click to collapse
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
pldeep said:
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
Click to expand...
Click to collapse
You've got instructions in this thread:
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Mind that you'll likely have more system.img_sparsechunk files, so make sure you flash all of them (just change commands accordingly).
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
pldeep said:
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
Click to expand...
Click to collapse
Your emmc ship is corrupt. That means your whole storage is broken and not fixable.
But i am able to flash some of the contents of the stock ROM. I get this "Pre flash validation failed" error only when I try to flash some of the files like (system.img_sparsechunk.0-9,recovery.img and gpt.bin). I even tried to reset the emmc_chip, I says that the command was succesfully executed.
Is there any other option left??
I am fighting this battle since a week now.
pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
kpamkar said:
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
Click to expand...
Click to collapse
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with
HTML:
fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
pldeep said:
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
Click to expand...
Click to collapse
In my case I had. 52 version of the ROM. I had a locked bootloader boot loop. But I was able to fix it using rsdLite. Are you using the latest version of the firmware and connecting the ports at the back of the pc? Also install proper drivers
You need to use RETASIA DS, the most recent version
@pldeep
firmware is here.
minimale_ldz said:
@pldeep
firmware is here.
Click to expand...
Click to collapse
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
try flashing it without gpt.bin and bootloader
Try booting into twrp without flashing it. Use fastboot boot command
---------- Post added at 08:44 PM ---------- Previous post was at 08:29 PM ----------
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
What are you trying to flash?
Same problem over here... Did you solve it?
Downloading right now the latest rom image for Moto X Play from this site.... //firmware.center/firmware/Motorola/Moto%20X%20Play/Stock/XT1563/
Hey install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Then run :- Fastboot reboot recovery.img
It will boot to twrp.
Any update for this? I'm in a similar situation now :-/
Tried RSD, it doesn't see my device (fastboot and adb works fine)
install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Click to expand...
Click to collapse
How can I do that?
Also, someone mentioned emmc_chip reset - how to do that?
Thanks
I have a Axon 7 with the bootloader unlocked but it is unrooted and doesn't have TWRP on it. When I go to settings to try to enable OEM unlocking it is grayed out saying "Bootloader is already unlocked" and I can't enable it. I've tried to boot into fastboot and it just takes me to the bootloader screen. Is their any way to enable OEM unlock using adb or something else?
Donte Dub said:
I have a Axon 7 with the bootloader unlocked but it is unrooted and doesn't have TWRP on it. When I go to settings to try to enable OEM unlocking it is grayed out saying "Bootloader is already unlocked" and I can't enable it. I've tried to boot into fastboot and it just takes me to the bootloader screen. Is their any way to enable OEM unlock using adb or something else?
Click to expand...
Click to collapse
Use axon7tool, don't try to use fastboot
Donte Dub said:
I have a Axon 7 with the bootloader unlocked but it is unrooted and doesn't have TWRP on it. When I go to settings to try to enable OEM unlocking it is grayed out saying "Bootloader is already unlocked" and I can't enable it. I've tried to boot into fastboot and it just takes me to the bootloader screen. Is their any way to enable OEM unlock using adb or something else?
Click to expand...
Click to collapse
The bootloader screen is where you issue fastboot commands. So when you reboot to bootloader just type "Fastboot oem unlock" (minus quotes) should bring up a menu that says something about unlocking wipes device etc. use volume rocker to select yes and power button to accept. When you use adb reboot bootloader and you're booted into the bootloader it will tell you if your bootloader is already unlocked.
There isn't a fastboot mode. Fastboot is just a protocol for issuing commands in order to flash to different partitions outside of recovery.
Choose an username... said:
Use axon7tool, don't try to use fastboot
Click to expand...
Click to collapse
When you try to root or flash TWRP it the toolkit reboots to fastboot.
jgates86 said:
The bootloader screen is where you issue fastboot commands. So when you reboot to bootloader just type "Fastboot oem unlock" (minus quotes) should bring up a menu that says something about unlocking wipes device etc. use volume rocker to select yes and power button to accept. When you use adb reboot bootloader and you're booted into the bootloader it will tell you if your bootloader is already unlocked.
There isn't a fastboot mode. Fastboot is just a protocol for issuing commands in order to flash to different partitions outside of recovery.
Click to expand...
Click to collapse
I've tried that and it says <Waiting for any device>
Donte Dub said:
I've tried that and it says <Waiting for any device>
Click to expand...
Click to collapse
I said axon7tool, not axon7toolkit. Axon7tool uses EDL mode which is finicky as hell but it sure works if you set everything right. Use Controllerboy's guide to root the A2017G but only do the TWRP part.
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
jgates86 said:
The bootloader screen is where you issue fastboot commands. So when you reboot to bootloader just type "Fastboot oem unlock" (minus quotes) should bring up a menu that says something about unlocking wipes device etc. use volume rocker to select yes and power button to accept. When you use adb reboot bootloader and you're booted into the bootloader it will tell you if your bootloader is already unlocked.
There isn't a fastboot mode. Fastboot is just a protocol for issuing commands in order to flash to different partitions outside of recovery.
Click to expand...
Click to collapse
Short and simple, there is no bootloader screen. ZTE killed it on the G and U versions. You can use MiFlash to get it back though
Choose an username... said:
I said axon7tool, not axon7toolkit. Axon7tool uses EDL mode which is finicky as hell but it sure works if you set everything right. Use Controllerboy's guide to root the A2017G but only do the TWRP part.
Click to expand...
Click to collapse
I've tried axon7tool and I followed all the steps but I still get no luck with trying to flash TWRP. I use the command axon7tool -w recovery recovery.bin and I get...
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
When I go back to the bootloader and try to reboot into recovery it boots into stock recovery.
Donte Dub said:
I've tried axon7tool and I followed all the steps but I still get no luck with trying to flash TWRP. I use the command axon7tool -w recovery recovery.bin and I get...
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
When I go back to the bootloader and try to reboot into recovery it boots into stock recovery.
Click to expand...
Click to collapse
Be sure that you have show file extensions enabled, otherwise you're naming the file "recovery.bin.img" without knowing
Choose an username... said:
Be sure that you have show file extensions enabled, otherwise you're naming the file "recovery.bin.img" without knowing
Click to expand...
Click to collapse
Ahh, it worked! Thank you so much for helping me get TWRP back.
hi, I'm trying to root my p9 lite to use it to run a 3d printing server ( https://github.com/d4rk50ul1/klipper-on-android )
I tried some rooting apps but it was unsuccesful.
after researching I used potatoNV to change the bootloader code
and SKR Tools to unlock bootloader and install twrp but i couldn't acces twrp via the phone. i locked back the bootloader with skr tools and now i can't get back to android, the phone is stuck on the " your device has been unlocked and can't be trusted. your device is booting now... " page, i left it like this for the nignt and it's not booting. I can't turn it off, My pc is not seeing it when pluged and I unpluged the battery for ten minutes but it's doing the same after replugging it .
what can i do to repair, root and use it ?
KilianBLRD said:
i locked back the bootloader with skr tools and now i can't get back to android,
Click to expand...
Click to collapse
you can relock bootloader only on clean stock firmware. If you did this on a modded system (TWRP installed etc.) you probably bricked the phone.
-Alf- said:
you can relock bootloader only on clean stock firmware. If you did this on a modded system (TWRP installed etc.) you probably bricked the phone.
Click to expand...
Click to collapse
what does this mean and what can i do ?
KilianBLRD said:
what does this mean and what can i do ?
Click to expand...
Click to collapse
A. Try your luck with testpoint & board software (check unfamiliar terminology by google or xda.
The instructions do not perform, if you do not know what you're doing.)
B. Use "DC-Phoenix" (paid service) .
-Alf- said:
A. Try your luck with testpoint & board software (check unfamiliar terminology by google or xda.
The instructions do not perform, if you do not know what you're doing.)
B. Use "DC-Phoenix" (paid service) .
Click to expand...
Click to collapse
I'm new to that, can you eplain a bit more please ?
Try to connect phone to PC in fastboot mode, run commands:
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
-Alf- said:
Try to connect phone to PC in fastboot mode, run commands:
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Click to expand...
Click to collapse
my pc is not seeing the phone
Maybe it's brick when you try to relock but it's still bootloader unlocked Don't worry
You can fix it with 4 method
1. Flashing with board firmware
2.fastboot flashing method
3.sd card upgrade method
4.usb upgrade method
KilianBLRD said:
my pc is not seeing the phone
Click to expand...
Click to collapse
i know but try the following:
press and hold the Power + Vol Down buttons for at least 10 sec and when the screen turns off, connect the USB cable to the phone.
-Alf- said:
i know but try the following:
press and hold the Power + Vol Down buttons for at least 10 sec and when the screen turns off, connect the USB cable to the phone.
Click to expand...
Click to collapse
What should I do next ?
KilianBLRD said:
What should I do next ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/need-help-to-root.4571641/post-88366105
-Alf- said:
https://forum.xda-developers.com/t/need-help-to-root.4571641/post-88366105
Click to expand...
Click to collapse
But fastboot mode is not working
KilianBLRD said:
But fastboot mode is not working
Click to expand...
Click to collapse
Do I really have to repeat everything twice???
https://forum.xda-developers.com/t/need-help-to-root.4571641/post-88366083
Good luck!
-Alf- said:
Try to connect phone to PC in fastboot mode, run commands:
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Click to expand...
Click to collapse
it says waiting for device and nothing happen
KilianBLRD said:
it says waiting for device and nothing happen
Click to expand...
Click to collapse
to check that the connection to the computer in fastboot mode is established normally, type the command
fastboot devices
,the serial number of the phone should be displayed.
If not, you're not in fastboot mode.