Unlocked boot loader and slower phone? - X Style (Pure) Q&A, Help & Troubleshooting

Not too long ago I had unlocked my bootloader and experimented with my phone with roms then decided to unroot it by putting back the original rom assuming it was back to stock my phone asked to update its and I did... My question is does having my bootloader unlocked make my phone slower? How can I relock it back to original? How can I be sure I am really back to normal stock rom without any fes missing or being messed up?

tecnikstr0be said:
Not too long ago I had unlocked my bootloader and experimented with my phone with roms then decided to unroot it by putting back the original rom assuming it was back to stock my phone asked to update its and I did... My question is does having my bootloader unlocked make my phone slower? How can I relock it back to original? How can I be sure I am really back to normal stock rom without any fes missing or being messed up?
Click to expand...
Click to collapse
Unfortunately once you unlock the bootloader there is no re locking it. For going back to stock use this thread for the XT1575 and this one for the XT1572 . There are instructions how to flash in those threads as well. You can get rid of the annoying boot on the XT1575 warning logo with this thread.

running "fastboot oem lock" should relock the bootloader.
The only way to be sure you are on complete stock is to use RSD to flash the stock MM or LP firmware.

asuhoops8628 said:
running "fastboot oem lock" should relock the bootloader.
The only way to be sure you are on complete stock is to use RSD to flash the stock MM or LP firmware.
Click to expand...
Click to collapse
Make sure you are completely back to stock before attempting to relock the bootloader. I read with some other devices it will brick it if you relock with a modified system. Better to be safe than sorry. That's good RSD works with this phone, I wasn't sure.

Misterxtc said:
Make sure you are completely back to stock before attempting to relock the bootloader. I read with some other devices it will brick it if you relock with a modified system. Better to be safe than sorry. That's good RSD works with this phone, I wasn't sure.
Click to expand...
Click to collapse
so all i do is go in command prompt and do that? or how do i do it?

Misterxtc said:
Make sure you are completely back to stock before attempting to relock the bootloader. I read with some other devices it will brick it if you relock with a modified system. Better to be safe than sorry. That's good RSD works with this phone, I wasn't sure.
Click to expand...
Click to collapse
the newer motos should warn you if you are not stock and will error out when relocking. However, to be safe, you are probably right
tecnikstr0be said:
so all i do is go in command prompt and do that? or how do i do it?
Click to expand...
Click to collapse
Look for the sticky thread in the general forum. There should be something in there with stock firmware and instructions for flashing via rsd lite.
After you are back to stock, boot the phone to the bootloader (hold power, vol -) when it is off, then open your adb instance and type:
Code:
fastboot oem lock

tecnikstr0be said:
so all i do is go in command prompt and do that? or how do i do it?
Click to expand...
Click to collapse
I just flashed back to stock 5.1 and I was unable to relock the bootloader. It said I need to install fully signed software or something like that. I did read on here that you can not relock it and so far I find that true. I think what slows down the phone is rooting it. After I rooted it took longer for my wifi to connect than being stock. I'm upgrading to 6.0 now via OTA.
EDIT: 6.0 stock slowed down my WIFI connecting so it wasn't rooting that caused it.
---------- Post added at 02:42 PM ---------- Previous post was at 02:32 PM ----------
asuhoops8628 said:
the newer motos should warn you if you are not stock and will error out when relocking. However, to be safe, you are probably right
Look for the sticky thread in the general forum. There should be something in there with stock firmware and instructions for flashing via rsd lite.
After you are back to stock, boot the phone to the bootloader (hold power, vol -) when it is off, then open your adb instance and type:
Code:
fastboot oem lock
Click to expand...
Click to collapse
I get this when I try to relock and I'm stock....
C:\Users\Rick\Desktop>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Users\Rick\Desktop>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.005s]
finished. total time: 0.005s

If my status code is 3 and software status says official what does that mean? This is on bootloader, does this mean im on stock?

Misterxtc said:
I just flashed back to stock 5.1 and I was unable to relock the bootloader. It said I need to install fully signed software or something like that. I did read on here that you can not relock it and so far I find that true. I think what slows down the phone is rooting it. After I rooted it took longer for my wifi to connect than being stock. I'm upgrading to 6.0 now via OTA.
EDIT: 6.0 stock slowed down my WIFI connecting so it wasn't rooting that caused it.
---------- Post added at 02:42 PM ---------- Previous post was at 02:32 PM ----------
I get this when I try to relock and I'm stock....
C:\Users\Rick\Desktop>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Users\Rick\Desktop>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.005s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Read my reply above this reply

tecnikstr0be said:
Read my reply above this reply
Click to expand...
Click to collapse
I'm not sure what code 3 means but official is stock I believe. I'm not really familiar with Motorola as I came from Samsung mainly.

Misterxtc said:
I just flashed back to stock 5.1 and I was unable to relock the bootloader. It said I need to install fully signed software or something like that. I did read on here that you can not relock it and so far I find that true. I think what slows down the phone is rooting it. After I rooted it took longer for my wifi to connect than being stock. I'm upgrading to 6.0 now via OTA.
EDIT: 6.0 stock slowed down my WIFI connecting so it wasn't rooting that caused it.
---------- Post added at 02:42 PM ---------- Previous post was at 02:32 PM ----------
I get this when I try to relock and I'm stock....
C:\Users\Rick\Desktop>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Users\Rick\Desktop>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.005s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Misterxtc said:
I'm not sure what code 3 means but official is stock I believe. I'm not really familiar with Motorola as I came from Samsung mainly.
Click to expand...
Click to collapse
So I'll still receive updates over the air?

tecnikstr0be said:
So I'll still receive updates over the air?
Click to expand...
Click to collapse
Yes if you are unrooted and have the stock recovery installed. The bootloader can be unlocked but the rest of the system needs to be stock and unmodified.

Misterxtc said:
[/COLOR]
I get this when I try to relock and I'm stock....
C:\Users\Rick\Desktop>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Users\Rick\Desktop>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.005s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Never tried to relock my BL, so you might be right.
Misterxtc said:
I'm not sure what code 3 means but official is stock I believe. I'm not really familiar with Motorola as I came from Samsung mainly.
Click to expand...
Click to collapse
code 3 means that the bootloader is unlocked. The codes have nothing to do with the SW you are running

asuhoops8628 said:
Never tried to relock my BL, so you might be right.
code 3 means that the bootloader is unlocked. The codes have nothing to do with the SW you are running
Click to expand...
Click to collapse
I did lock the bootloader back up but the warning message remains and can be removed but code 3 stays permanently because it's a blown efuse from unlocking. The error message I got was because I was doing it wrong. I followed the directions in this thread and it went well. Thanks for the info on code 3, it was useful. Oh and don't use RSD to flash the firmware, it will fail and make your phone boot to the bootloader screen first. Thankfully I figured out how to fix it.

thanks for that reply on how to flash in RSD w/o fail. Was having that issue with another recent moto

Related

Can't Relock Bootloader

I noticed there were 2 newer images on the Google developers page and thought I would flash the latest and greatest (MDB08M) since it wasn't coming down OTA. I enabled Developer Options and set USB debugging and OEM unlock, rebooted to bootloader, did a fastboot oem unlock, rebooted then back to bootloader and ran the flash-all.bat from the new image, rebooted and all was well. I re-enabled USB debugging and went back to bootloader to re-lock the bootloader and am getting an error:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Results of fastboot getvar version-main are blank:
version-main:
finished. total time: -0.000s
I rolled back to MDB08K but it made no difference. I then tried rolling back to MDA89D and letting it pull MDB08K OTA but that too made no difference.
Any suggestions?
Are you using the following command after flashing stock images?
fastboot flashing lock
Click to expand...
Click to collapse
Cares said:
Are you using the following command after flashing stock images?
Click to expand...
Click to collapse
No, I was trying to do "fastboot oem lock". "fastboot flashing lock" relocked the bootloader, but fastboot getvar version-main is still blank. I suppose I have achieved my goal of relocking the bootloader, but should I worry about the version-main being blank?
boofa said:
No, I was trying to do "fastboot oem lock". "fastboot flashing lock" relocked the bootloader, but fastboot getvar version-main is still blank. I suppose I have achieved my goal of relocking the bootloader, but should I worry about the version-main being blank?
Click to expand...
Click to collapse
That I have no idea. I just know that the fastboot commands have changed so that's why you couldn't relock.
Cares said:
That I have no idea. I just know that the fastboot commands have changed so that's why you couldn't relock.
Click to expand...
Click to collapse
Why are you locking the bootloader anyway? If you're flashing system images and then locking the bootloader you are risking having a device with a non-functioning OS and no way to fix it. Either stay locked and wait for OTA's or leave it unlocked.
I was going to root it, but decided against it since I only needed root for Tasker and WiFi hotspot in the past and I get WiFi hotspot at no charge since switching to Fi. I'll just do without the Tasker stuff since alot of what it was doing is probably not necessary any more and was setup back on Jellybean. I wasn't attempting to lock the bootloader until I had done a clean boot and verified basic functionality. I'm all good now though, thanks for the assist.

[ROM] [STOCK] KDZ V20L 6.0 H901 T - Mobile

Update V20E 6.0 T - Mobile
H901 - T Mobile
V20e (6.0)
https://drive.google.com/open?id=0B3R77elw9JjNSmVsVjhjbWdLcEU
V20j (6.0)
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1FRFU652MMA4P3503B0ON/H90120j_00_0712.kdz
V20l (6.0)
http://pkg03.lime.gdms.lge.com/dn/d...1478794859&h=59e2525cdab042c7ac78e39941ad3362
Woww. Thánks for sharing
reachedxyz said:
Woww. Thánks for sharing
Click to expand...
Click to collapse
Bày đặt nói tiếng anh
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?
Sent from my LG-H901 using XDA-Developers mobile app
diamantericos said:
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?[/URL]
Click to expand...
Click to collapse
KDZs are factory firmware files, untouched.
Is it possible to root? Bootloader remains unlocked?
jonsat said:
Is it possible to root? Bootloader remains unlocked?
Click to expand...
Click to collapse
Bootloader can be unlocked. No word on root yet
Do you have to have stock recovery to used the kdz file
I'll wait for the rooted stock version, but I'm sure we'll be seeing it this week!
shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
I nand back to a stock build thru twrp. Booted to Android ran LG bridge and it worked fine
Sent from my LG-H901 using XDA-Developers mobile app
shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
sikander3786 said:
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
SmileBigNow said:
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
No I don't think so. Not with MM KDZ.
sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
sikander3786 said:
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
Click to expand...
Click to collapse
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Eliminater74 said:
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Click to expand...
Click to collapse
That's bad, real bad.
The first thing most of us will want to know here is if downgrade to 5.1.1 is safe? If yes, which build? I don't think we have many options there.
For rooting, can we try opening the LG Com port using the old 9% method? Maybe then we can try flashing a root injected system image? I am away from PC so can't try this right now. Won't be asking otherwise.
I will wait for a flashable zip. And hope it will have root. Or maybe stick with the Korean Mm port
Sent from my LG-H901 using XDA-Developers mobile app
Yep. Flashable zip is the way to go for now (if it somehow becomes available). I am not sure how to read system dump from a locked-down device and create a Flashable zip.
I will try downgrading to 5.1.1 in the morning.
Just wondering, why allow bootloader unlock if LG and T-Mobile want to lock down everything else?

Blasted kingroot - bricked my phone?

Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key

No recovery, bootloader relocked

Hello, i have a serious problem with my U Ultra.... Last night I unlocked the bootloader, I installed TWRP(lastest version from official site), before all this I made backup (with TWRP) of every partition and then I make back-up of system, data, boot I think, I have everything on my laptop.
But I wanted to back on stock (Don't ask me why...) and i restored a back-up, a full back-up of every partitions. Everything great, but google play didn't had Device Certification: Uncertified like in this pic and I tried to do this method and it didn't worked and I don't know why I thought that if I will relock the bootloader, everything will be okay :| and now I don't have TWRP anymore and of course neither stock recovery, but the stock rom boots but the password I have made it, is not working.
Tried to unlock bootloader but this error shows up
Code:
diesel-X550CL Downloads # fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Now how can I solve this problem?
How did you did the bootloader relocking?
For what purpose you need the Google Play certification?
QDT said:
How did you did the bootloader relocking?
For what purpose you need the Google Play certification?
Click to expand...
Click to collapse
Through fastboot with this command:
Code:
fastboot oem lock
I don't need it for a special purpose but some apps don't work and I saw that was the solution, anyways I don't need that no more, I just want the phone to work....
Just go to fastboot mode perform oem unlock and reinstall the twrp
QDT said:
Just go to fastboot mode perform oem unlock and reinstall the twrp
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
I can't because oem unlock is not turned off
kempactick said:
I can't because oem unlock is not turned off
Click to expand...
Click to collapse
You don't need to use the HTC file. Your phone is permanently hardware unlocked since the first flash.
All you now need to do is simple
Code:
fastboot oem unlock
QDT said:
You don't need to use the HTC file. Your phone is permanently hardware unlocked since the first flash.
All you now need to do is simple
Code:
fastboot oem unlock
Click to expand...
Click to collapse
i tried this one too...
Code:
diesel-X550CL Downloads # fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.005s
This error are just because of oem unlock from developer settings.. How can I trick this?
kempactick said:
i tried this one too...
Code:
diesel-X550CL Downloads # fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.005s
This error are just because of oem unlock from developer settings.. How can I trick this?
Click to expand...
Click to collapse
In what mode are you?
QDT said:
In what mode are you?
Click to expand...
Click to collapse
I'm on download mode, bootloader mod ain't for flashing
kempactick said:
I'm on download mode, bootloader mod ain't for flashing
Click to expand...
Click to collapse
Then what I can only advise is getting RUU of your system's current or newer version and force to reflash everything including bootloader.
QDT said:
Then what I can only advise is getting RUU of your system's current or newer version and force to reflash everything including bootloader.
Click to expand...
Click to collapse
Tried to flash RUU but is not working too, i'm trying with htc sync right now
I have the same issue after relocking my phone. Before I decided to lock my phone to downgrade to nougat, I did flash twrp and a rooted stocked oreo rom. After locking my phone using fastboot my phone stuck into download mode bootloop, I was able to get into download mode properly but I couldn't afford to download ruu from easy-firmware to flash in ruu mode
iAlcatrazZ said:
I have the same issue after relocking my phone. Before I decided to lock my phone to downgrade to nougat, I did flash twrp and a rooted stocked oreo rom. After locking my phone using fastboot my phone stuck into download mode bootloop, I was able to get into download mode properly but I couldn't afford to download ruu from easy-firmware to flash in ruu mode
Click to expand...
Click to collapse
I couldn't solve the problem myself, so I went to a gsm service and they couldn't solve it, 1 month of trying and one day my dad told me to go to the warranty service and I didn't, he went there and I don't know how they accepted the phone with the another reason and in a hour they solved the problem. I'm still using the phone and I can't wait to get rid of it.
So... I don't know how to help you, you should go to a gsm service, regards!
kempactick said:
I couldn't solve the problem myself, so I went to a gsm service and they couldn't solve it, 1 month of trying and one day my dad told me to go to the warranty service and I didn't, he went there and I don't know how they accepted the phone with the another reason and in a hour they solved the problem. I'm still using the phone and I can't wait to get rid of it.
So... I don't know how to help you, you should go to a gsm service, regards!
Click to expand...
Click to collapse
I managed to restore my phone :v, I could partially remember how I did it, I'm still gathering resources so that I can write a complete guide for everyone

Twrp-3.0.0.2-himar

Posting a new thread was my last resort, so here goes.
I'm looking for a TWRP recovery for a HTC One M9e PCE. It's obviously a rarer model so finding stuff for it is incredibly hard. While searching the forum I came to the conclusion that there once was a file named twrp-3.0.0.2-HIMAR.img hosted on androidfilehost. But all the links are dead.
Does anyone have a copy of that image lying around? I would greatly appreciate if someone would upload it again. If I'm not mistaken the author of that recovery was mars3712, if that helps.
EDIT: I'm aware that there's a repo on github also, though unfortunately it's on a 5.1 base. The device in question is 6.0 MM. Would it matter?
http://www.mediafire.com/folder/2wd1oprpj5ija/HTC_M9_PCE
twrp-3.0.2-0-himar2.img and twrp-3.0.2-1-himar2.img
Click to expand...
Click to collapse
both working perfect on my HTC M9 PCE better use newer
in 10min in folder will be uploaded
2PRGIMG_HIMAR_ML_UHL_M60_SENSE70GP_HTC_Europe_2.32.401.1_Radio_1.1550V70.2508.0304_HU[W.T]_release_488703_combined_signed_2_4.zip
Click to expand...
Click to collapse
to install from sd format sd download rom rename to 2PRGIMG.zip place on sd power and vol- (or + dont remember) and rom should install auto in download mode
Amazing, thanks for the upload. Apparently I need S-OFF to flash this. I've flashed some janky TWRP on this phone before and it never needed S-OFF. Any thoughts? Already running the ROM you posted.
Code:
[email protected]:~/Downloads$ sudo fastboot flash recovery twrp-3.0.2-1-himar2.img
target reported max download size of 134217728 bytes
sending 'recovery' (13544 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Image verification failed...
FAILED (remote: Err! Stop flashing due to S-ON...
)
finished. total time: 1.395s
You unlock bootloader at htcdev.com right?
I will back home in 2/3 hours and look on problem
GeoEgbA said:
You unlock bootloader at htcdev.com right?
I will back home in 2/3 hours and look on problem
Click to expand...
Click to collapse
Yes, the phone is unlocked.
Sorry just back home 2days away. So you must relock bootloader fastboot oem lock restart phone and again unlock bootloader but may use Unlock_code.bin if you have it from first unlock, if no then again generate it on htcdev
I did 2 tests, install clean rom from sd (2PRGIMGizip) and after try flash recovery and get same error as you, one dev i have s-on seccond s-off in both case after flash rom do
fastboot oem lock
Click to expand...
Click to collapse
then
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I used old tocken from first unlocking and after this
htc_fastboot flash recovery twrp-3.0.2-1-himar2.img
Click to expand...
Click to collapse
and work perfect in both case
So lock and relock bootloader
Try this and give feedback if all ok, i didnt sleep over 50h so my english grama may be little wrong
Will check here in fiew hs now i go rest.
GeoEgbA said:
Sorry just back home 2days away. So you must relock bootloader fastboot oem lock restart phone and again unlock bootloader but may use Unlock_code.bin if you have it from first unlock, if no then again generate it on htcdev
I did 2 tests, install clean rom from sd (2PRGIMGizip) and after try flash recovery and get same error as you, one dev i have s-on seccond s-off in both case after flash rom do
then
I used old tocken from first unlocking and after this
and work perfect in both case
So lock and relock bootloader
Try this and give feedback if all ok, i didnt sleep over 50h so my english grama may be little wrong
Will check here in fiew hs now i go rest.
Click to expand...
Click to collapse
Hello, do you happen to have the different region (CID HTC__621) RUU for my HTC One M9s (himaruhl)? Thank you very much!
Thanks for the information you provided
---------- Post added at 01:35 PM ---------- Previous post was at 01:28 PM ----------
I have installed twrp data password

Categories

Resources