[Completed] Htc one mini m4 go back to stock rom - XDA Assist

Hello everyone!
I've had my m4 for about 5/4 years now and my battery has been getting worse more and more slowly for about 2 months now. Because I want to invoke my guarantee I tried to return the phone to stock rom from Insertcoin, unroot it and lock the bootloader. I flashed the stock rom from this(http://forum.xda-developers.com/showthread.php?t=2791725) thread and everthing was working fine. After that I went into fastboot and typed the command "fastboot oem lock", because I read so on the internet. Now there seems to be no rom or recovery on my phone anymore and everytime i reboot it just straigth goes into the bootloader. None of the tools I found on google worked so I thought somebody here could help me because I'm almost getting desperate.
I will also include a link to a photo of the bootloader, maybe it's helpful (https://www.dropbox.com/s/0j7830bw6mxjjrv/IMG_20150511_190346.jpg?dl=0).
Also notice that this is one of my first posts in this forum and english isn't my mother tongue.
I would really appreciate a fast but especially useful and relative easily written response.
Thanks!

Hi, thank you for using XDA Assist. I would unlock the bootloader, fasboot oem unlock, and flash the stock firmware from the link you provided.

fastboot oem unlock error
I tried fastboot oem unlock but it just wrote "[ERR] Command error!!!". I also tried to unlock it via HTCdev again but the sites seems to be down, everytime i select my device and click on Begin Unlock Bootloader it opens this small window and says that the site is unavailable, I also tried it a few different times. Is there no other tool to unlock the bootloader or somehow get my rom started again, because I'm wondering why it's erasing or at least not giving me access to the rom that was perfectly working before anymore after locking the bootloader.
-Edit:
OK so i found out how to do it with HTCdev. I just had to create an account, log in and do exactly the same as before. I had to give it a few tries, but in the end it worked. Now my question is how I can relock my bootloader without causing the same again? I didn't find anything other than the cmd prompt fastboot oem lock so if maybe somebody could help me.

Thread closed.

Related

[Q] Cannot unlock bootloader.

Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
wimobile246 said:
Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
Click to expand...
Click to collapse
Not really sure what it is, but have you tried to launch SDK Manager and update platform-tools and google driver?
wimobile246 said:
Hello,
Before posting here I tried to find the solution to my problem by searching on this site and also google but couldn't find the answer so finally decided to post it here.
I have Motorola Xoom MZ600...
So when I type in the command "fastboot oem unlock" nothing happens on the tablet and it shows on the command prompt that
"<bootloader> oem unlock is currently under construction"
What does that mean and what should I do to unlock the bootloader?
Thanks.
Click to expand...
Click to collapse
Its likely cause your tablet is booting into the OS and not fastboot...
Use this AIO_scripts_R.A.H._TWRPv2.6.3.zip - 12.00 MB
Ive created that for installing twrp recovery but also included tools to unlock your boot loader.
under the windows folder and click the runme.bat and simply folliw the prompts for what you want to do...cant get any easier.
Sent from my SCH-I605 using Tapatalk 2
Thanks guys for the reply.
@mikecore - SDK manager, platform-tools and drivers were up to date. @runandhide05 - I made sure I was in the fastboot mode. And thank you so much for the link but it wasn't that I was doing wrong, the problem was the bootloaders were very old from the very first built or probably even before the xoom was released to public (when it was in manufacture trial or something). So whenever I tried to check the software update it said it was uptodate but it was running froyo (2.5 or something). What I did was I got the imgs of the latest built available from motorola and pushed that in fastboot mode. After that I got like 5 software updates OTA and it updated the bootloader to the latest version and now I am running android 4.1. Also I was able to unlock the bootloader now.

Can't Relock Bootloader

Hey guys,
So i went to walmart a couple days ago and bought the virgin mobile Moto G. The first thing i did when i got home was root it. Turns out that the phone i got does not work for my plan. so i need to return it, and i'd like to make it completely stock for warranty reasons. The only problem is that i can't get the bootloader to relock. I've tried using the Windroid universal android tool and have followed this guide with the correct files for my phone http://forum.xda-developers.com/showthread.php?t=2646415. Everything Went fine, phone is completely stock..but the bootloader still says its unlocked. Could anyone help me with this?
Thanks!
http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728
Scroll to the bottom of the post and you will find how to lock it again.
@eddie298 - Once Bootloader has been unlocked, it's permanent. Fastboot screen will always state unlocked, even if you do so-called 'OEM relocking' - Fastboot command:
fastboot oem lock​

OEM Unlocking issue [SOLVED]

I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net

Google Pixel in crashing during boot - oem disabled so I can't unlock it again

So I installed twrp root on my Pixel and got annoyed at the fact my phone kept telling me to relock my bootloader. I did what it told me. But beforehand I decided to disable oem. I've researched for hours trying to figure out if I can enable it from CMD on PC but nothing works. I'd appreciate it if someone could help me.
FalseFriendsGaming said:
So I installed twrp root on my Pixel and got annoyed at the fact my phone kept telling me to relock my bootloader. I did what it told me. But beforehand I decided to disable oem. I've researched for hours trying to figure out if I can enable it from CMD on PC but nothing works. I'd appreciate it if someone could help me.
Click to expand...
Click to collapse
You may need to reflash back to stock via ADB or you could try this thread to jumpstart OEM unlock again https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
If you get back up and running just ignore that relock bootloader, I've never relocked it once root and twrp are installed, I'd only relock the bootloader if I've gone back to full stock.
Good luck
Sent from my Pixel using XDA Labs

Bootloader question, PLEASE HELP!

I have a TracFone moto g pure (XT2163DL) running android 12, build number S3RHS32.20-42-13-2-1. I managed to get my oem unlock to show up and turned it on. First I tried using the Motorola unlock site to unlock my bootloader but it said it wasn't eligible. So then I tried using fastboot command "fastboot oem unlock" and a screen popped up telling me I can choose to unlock my bootloader and when I told it to unlock I received a message saying it was successful. But it isn't. It said it's unlocked but yet it is still locked anyway. I know TracFone has problems unlocking bootloader's but why would it let me get that far if it is impossible to unlock? Is there anything else I can do? If anyone knows something else I can try please point me in the right direction. I don't mind doing my homework after all that's how I learn but I'm just at a point where I need some guidance.please help me and always thank you so much for your time in advance...
If the bootloader reports unlocked, what makes you say it's still locked?
V0latyle said:
If the bootloader reports unlocked, what makes you say it's still locked?
Click to expand...
Click to collapse
Nothing is wiped and it still says OEM secured on the fastboot page. The only difference now is when I try to reboot back into system it will first boot back into the bootloader again and then it will boot into system when I reboot a second time

Categories

Resources