Need helps! How to access boot loader mode with HTC touch pro? - General Questions and Answers

My phone is sim locked and i need to access boot loader mode to change its ROM.
Please help me.
Thanks in advance.

Welcome to forums
Please have a deep read here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Rhodium
You´ll find all you need!
Good luck,

hdts said:
My phone is sim locked and i need to access boot loader mode to change its ROM.
Please help me.
Thanks in advance.
Click to expand...
Click to collapse
Read well, because your statement is a bit simplistic.
You do not need to change your rom to sim unlock your phone.
And you do not necessarily need to enter bootloader to flash a new rom.
What is it that you are looking to accomplish.

Related

[Completed] Hard bricked HTC one

Hi, i'm new in the forum and i want to ask for advice.
Well... in all the threads it says that i need to unlock the bootloader before doing anything else, but that is the problem, i can't. I can flash the unlock code with the console but the phone don't show the notification about the bootloader unlock.
Can't do factory reset and can't enter recovery.
Hope you can help me guys.
bocadillosnake said:
Hi, i'm new in the forum and i want to ask for advice.
Well... in all the threads it says that i need to unlock the bootloader before doing anything else, but that is the problem, i can't. I can flash the unlock code with the console but the phone don't show the notification about the bootloader unlock.
Can't do factory reset and can't enter recovery.
Hope you can help me guys.
Click to expand...
Click to collapse
Greetings!
Please let me know which model of the One you have so I can direct you where to post.
Thanks!

Help

Hi. I have got a problem. I currently have a lg nexus 4 . i accidently installed twrp in boot. so every time i open my phone twrp comes. and half of my touch screen does not work. so i can't fully swipe to install roms and cant type certain lettrs in keyboard in terminal and the bootloader is locked. so how do i get out of this . any help will be greatly appreciated . Thank you
You need to try unlocking bootloader.
HippoInWindow said:
You need to try unlocking bootloader.
Click to expand...
Click to collapse
umm could you please teach me how to do so?

Need help - "The system has been destroyed"

So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
boxof said:
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
Click to expand...
Click to collapse
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Azev said:
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
Click to expand...
Click to collapse
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
Mackay53 said:
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Click to expand...
Click to collapse
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
boxof said:
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
Click to expand...
Click to collapse
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
Unless you have got unlock permission and linked phone to account you can't unlock.
Unlock like how you would normally - put the phone into fastboot, connect it to your PC, and run the mi unlock tool. For this to work, hopefully you have associated your device to a mi account and have met the unlock requirements ie. surpassed the waiting period. Otherwise you're out of luck as there is no other ways (that i know of) to register the device now as you can't get into the system.
As a last resort you can try opening up the back of the phone and flash new firmware using the test point if unlocking is not possible. I'm not sure how or where the testing point is located exactly, but it's a possible solution that i found while researching when my device was bricked. Good luck!
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
u say u can only access to fastboot..
How about pressing volume up and power button? can u enter in stock mi recovery with mi assistant options?

Unable to unlock bootloader (OEM unlocking disabled)

Hello,
I couldn't unlock the bootloader as the OEM unlocking's disabled and i can't access system! Everything's erased!
Any help????
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
junglism93 said:
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
Click to expand...
Click to collapse
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
eldeen said:
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
Click to expand...
Click to collapse
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
junglism93 said:
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
Click to expand...
Click to collapse
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
eldeen said:
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
Click to expand...
Click to collapse
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
AndroidNazi said:
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
Click to expand...
Click to collapse
Thanks for help, but could you please show me how to do that?
eldeen said:
Thanks for help, but could you please show me how to do that?
Click to expand...
Click to collapse
Make sure you have the latest fastboot. On the bootloader your phone will either say "slot a" or "slot b" and you should type "fastboot --set-active=b" if you are on slot a or "fastboot --set-active=a" if you are on slot b
still didn't fix the problem... any probable solutions please?

[locked OEM] Please help.

Hey guys,
first of all I'm only posting here because for some reason I can't post on the Questions section.
Unfortunately I miss-clicked the lock oem after I had it unlocked. Now my phone says its corrupt. I managed to enter into fastboot again. But now I cant flash anything because it says Boot / flash / not allowed in Lock State.
Please guys what to do , because all data is on that phone. please help.
lucasluize said:
Hey guys,
first of all I'm only posting here because for some reason I can't post on the Questions section.
Unfortunately I miss-clicked the lock oem after I had it unlocked. Now my phone says its corrupt. I managed to enter into fastboot again. But now I cant flash anything because it says Boot / flash / not allowed in Lock State.
Please guys what to do , because all data is on that phone. please help.
Click to expand...
Click to collapse
Boot into bootloader and reunlock it
Can't. Lock State can't use command oem unlock as well. I'm trying using the MSM tool now fingers crossed
Are you on stock oxygen? Are you able to use the stock recovery to factory reset? You unlocked the bootloader using something other than command prompt/platform tools?
lucasluize said:
Hey guys,
first of all I'm only posting here because for some reason I can't post on the Questions section.
Unfortunately I miss-clicked the lock oem after I had it unlocked. Now my phone says its corrupt. I managed to enter into fastboot again. But now I cant flash anything because it says Boot / flash / not allowed in Lock State.
Please guys what to do , because all data is on that phone. please help.
Click to expand...
Click to collapse
Download msm download tool, Qualcomm drivers and use it, you can find all into guide section.
VampireHeart said:
Download msm download tool, Qualcomm drivers and use it, you can find all into guide section.
Click to expand...
Click to collapse
Thank you. Managed to do it! It was a bit hard finding the right driver. But in the end worked.
lucasluize said:
Thank you. Managed to do it! It was a bit hard finding the right driver. But in the end worked.
Click to expand...
Click to collapse
Good

Categories

Resources