Hey guys, I finally got my phone!
I want to install a custom ROM but first I need to unlock the bootloader and I'm having a nightmare doing it. Is there an specific thread where I can ask for help with, since I didn't find any I created this one but feel free to delete it.
On the FAQ thread I found this:
"First you need to unlock your bootloader. To do that, go to http://www.htcdev.com/bootloader. On the supported devices list, choose "HTC One (M8)"
If I go there, i am able to get up to step #5, but when I enter the command "fastboot oem get_identifier_token" I get that "fastboot" is not a recognized command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've searched on Google, but all thread (or most of them) only point to old devices or another brands. I also tried to use a root toolkit, but everything takes to that #5 step.
What am I missing here?
pinktheater said:
Hey guys, I finally got my phone!
I want to install a custom ROM but first I need to unlock the bootloader and I'm having a nightmare doing it. Is there an specific thread where I can ask for help with, since I didn't find any I created this one but feel free to delete it.
On the FAQ thread I found this:
"First you need to unlock your bootloader. To do that, go to http://www.htcdev.com/bootloader. On the supported devices list, choose "HTC One (M8)"
If I go there, i am able to get up to step #5, but when I enter the command "fastboot oem get_identifier_token" I get that "fastboot" is not a recognized command.
I've searched on Google, but all thread (or most of them) only point to old devices or another brands. I also tried to use a root toolkit, but everything takes to that #5 step.
What am I missing here?
Click to expand...
Click to collapse
This will help you set up adb/fastboot in your System path, the rest is as you've already done...
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
EddyOS said:
This will help you set up adb/fastboot in your System path, the rest is as you've already done...
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Click to expand...
Click to collapse
Thanks mate! I finally did it, but damn it took a lot of work
pinktheater said:
Thanks mate! I finally did it, but damn it took a lot of work
Click to expand...
Click to collapse
If you now have adb in your system path you can run the commands in any location - makes life a LOT easier moving forward (and it applies to ALL Android devices)
Related
well i had no problem what so ever making fastboot work, sadly though there are certain times were one has to use ADB! anyway, i have htc sync installed, and i know that the computer recognizes my device because of this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so obviously there is a problem that i do not understand, because when i check in my sdk (fastboot) folder by typing "adb devices", the list of devices is empty!
please help i really need this!
ADB detects your device while it's inside the OS (running) or in recovery mode. Make sure to install latest version of HTC Sync.
tomascus said:
ADB detects your device while it's inside the OS (running) or in recovery mode. Make sure to install latest version of HTC Sync.
Click to expand...
Click to collapse
so it cant detect my device while it's in fastboot mode? so it's impossible to use ADB if your bootloader is relocked right? cuz i am trying to follow this guide: http://www.flow-wolf.net/2012/10/install-jelly-bean-on-htc-one-x-maximus.html
however i cant find a way to successfully install PJ46IMG.zip !
That guide is extremely outdated and I don't suggest you use it. To flash the firmware zip package use the fastboot command 'fastboot oem rebootRUU' and then type 'fastboot flash zip (name of zip here)'
Sent from my HTC One X using xda app-developers app
tomascus said:
That guide is extremely outdated and I don't suggest you use it. To flash the firmware zip package use the fastboot command 'fastboot oem rebootRUU' and then type 'fastboot flash zip (name of zip here)'
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
yeah when i did that before i also got an error, cant remember actual wording, but the good new is i gave up on OrDroid and Maximus, decided to try out Jeffix and it worked, i am guessing it was an issue related to Hboot, but happily all my issues have been resolved, thanks for the help though!
Hi guys,
Ive rooted a lot of devices . But ive been using an iPhone for a few years. I recently switched back to Android and jm rustY rooting. Can someone write up a guide on how to root the device using osx? I tried following the windows guide but it isn't working out so well.
I've been having issues as well, but I think it's an issue with my phone rather than using a macbook.
Did you manage to get htc unlock to work? I haven't even gotten that far.
What's the problem? It's very similar to the way you do it in windows. Use terminal instead of cmd and write "./" in the beginning of each command. Example "./fastboot reboot"
Sent from my HTC One M9
tacofromhell said:
What's the problem? It's very similar to the way you do it in windows. Use terminal instead of cmd and write "./" in the beginning of each command. Example "./fastboot reboot"
Sent from my HTC One M9
Click to expand...
Click to collapse
Ive had no problems with using a mac ever. See the post above. That's the main difference.
tacofromhell said:
What's the problem? It's very similar to the way you do it in windows. Use terminal instead of cmd and write "./" in the beginning of each command. Example "./fastboot reboot"
Sent from my HTC One M9
Click to expand...
Click to collapse
Thanks for the reminder. I had forgotten since I had rooted last phone. Hopefully, I can get it done when I get home from work.
I was having the same issue but I Installed this adb and now I can do everyting with it.
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
If you have an issue just read the second comment and you will be fine.
Hope this helps!
I should probably make a new thread for this, but I'll try to ask here first, since I'm a mac user.
I can get my macbook to recognize my m9 and transfer files just fine when it is running normally. But when I get to the bootloader mode, the phone isn't. Here's a pic of the messages I get at the bottom of my screen every time I enter the bootloader. Does anyone know what these mean? And if they are related to any know unlocking issues? I can't even start unlocking it seems.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mr.BungIe said:
I should probably make a new thread for this, but I'll try to ask here first, since I'm a mac user.
I can get my macbook to recognize my m9 and transfer files just fine when it is running normally. But when I get to the bootloader mode, the phone isn't. Here's a pic of the messages I get at the bottom of my screen every time I enter the bootloader. Does anyone know what these mean? And if they are related to any know unlocking issues? I can't even start unlocking it seems.
View attachment 3325604
Click to expand...
Click to collapse
the phone searches for that update.zip when you enter download mode
it's normal. fastboot commands will still work from that screen
I don't normally post in the forums however I figured this may be important.
Lets hope that this time we may be able to get our bootloaders unlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Saw same, subscribed to thread!
Searching for the exact phrase, not much out there I found other than a G4 question regarding the same...
Copied and pasted this from a source I found..
For those new to “OEM unlock,” just know that this is a part of the command used to unlock a Nexus phone’s bootloader. After installing the Android SDK, plugging your phone into a computer, opening adb, and rebooting to the bootloader, a simple command in adb of “fastboot oem unlock” will start the process of phone freedom.
It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk
My understanding is that this is hard built into the developer mode, so stock vanilla Google phones like nexus and I'm guessing probably the moto lines are the only phones for which this will work. Basically, you're telling the phone whether to ignore the command altogether or to actually execute the command when it's toggled on. Think of this like the following: oem unlock toggle : permit execution of 'oem unlock' command :: USB enabled toggle :: being able to use the adb command
As @51ngular1ty said above, Sam phones have a completely different recovery architecture, so they respond to different commands/software.
51ngular1ty said:
It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Fastboot is a commandline tool used through adb. You plug you phone in while its on and you can use adb commands but you have yo enable it in the dev settings
Hello guys, this is what i have on my htc m9
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could I restore Stock rom on my htc m9 and how to do that?
And how I now which RUU to chose?
https://www.google.com/url?q=https:...134000&usg=AFQjCNGdzDwYjWYwYr-RSW3t2U9j47aOJw
Download this file. Copy it to your ext sdcard and rename it to 0PJAIMG.zip
Connect your phone to fastboot and type fastboot oem lock
Boot into download mode. Phone will prompt you to install. Press volup and wait.
Before u start backup ecerything
If you're already linking one of my files you could've linked my instructions, too, since what you wrote isn't completely correct. Re-locking the bootloader is unnecessary if you use the SD card method. In the worst case (e.g. if the RUU fails and OEM unlock isn't activated in the developer options) you could end up with a non-booting phone that can't be re-unlocked. The M9 has security checks that prevents it from booting if it isn't completely stock and the bootloader gets (re-)locked. And although I tested that RUU there can always be reasons why it fails to flash.
Could you be more specific please, I am new with htc and I dont know anything about it, What is fastboot? And if you have some time to tell me step buy step how to do that i would be greatiful. Sorry for bad english
Im sorry Flippy498 i just want to help him. You are a genious and i respect you. You are a life saver.
https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml
My bad. I didn't notice that my signature isn't visible in this thread.
Edit: I don't know why the link gets broken as soon as I save this post. You'll need to copy'n'paste the link.
THX a lot, now I'm gonna to try to restore stock rome!
@Flippy498 I have just one question, I followed your instructions and it worked perfectly but I still have Software Status marked as Modified. Would I be able to receive software updates ?
Yes, you will. And you'll be able to install them, as well. (Receiving updates is not the problem, it's being able to install them if the system has been modified. However, a RUU reverts every modification you made.)
It's just strange that the flag still says that your system is modified. Normally the SD card method should reset it to original. But that shouldn't be a problem. OTAs don't check that flag. They compare whether the checksum of the system is the same as the reference value. Since a RUU overwrites the current system with the stock one you won't face any problems here.
Thanks a lot dude for your great work and quick reply !
Good day to yall!
I've been trying to download the Pixel Experience ROM on my phone for the past few hours and I keep getting this error.
I've already used the ./adb kill-server; ./adb start-server commands on PowerShell and my device says I've given all the necessary permissions to the computer I'm performing the ROM installation on. But I keep getting the same error over and over again.
Any help would be appreciated!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Chambuligu said:
Good day to yall!
I've been trying to download the Pixel Experience ROM on my phone for the past few hours and I keep getting this error.
I've already used the ./adb kill-server; ./adb start-server commands on PowerShell and my device says I've given all the necessary permissions to the computer I'm performing the ROM installation on. But I keep getting the same error over and over again.
Any help would be appreciated!!
View attachment 5478869
Click to expand...
Click to collapse
Guide: https://telegra.ph/Flashing-PEPPUI-09-09
Have you unlocked your bootloader?
Compass.
Compass Linux said:
Guide: https://telegra.ph/Flashing-PEPPUI-09-09
Have you unlocked your bootloader?
Compass.
Click to expand...
Click to collapse
I have. Otherwise I wouldn't be able to make use of the "XiaoMiTool_V2", which is the tool I'm using to install the ROM on my phone.
And after I kept on trying, I noticed that my main problem is that when I get to the phase in which my phone enters recovery mode, it unistalls TWRP, or more specifically, it deletes the image. And after that it just reboots and the process fails. However, I was not able to figure out how to solve the problem... Still would appreciate any help. Thanks in advance.
Chambuligu said:
I have. Otherwise I wouldn't be able to make use of the "XiaoMiTool_V2", which is the tool I'm using to install the ROM on my phone.
And after I kept on trying, I noticed that my main problem is that when I get to the phase in which my phone enters recovery mode, it unistalls TWRP, or more specifically, it deletes the image. And after that it just reboots and the process fails. However, I was not able to figure out how to solve the problem... Still would appreciate any help. Thanks in advance.
Click to expand...
Click to collapse
If you've managed to install TWRP properly you cannot boot into MIUI. MIUI removes TWRP if allowed to boot.
Follow the guide: https://telegra.ph/Flashing-PEPPUI-09-09
This guide is the official one and has more details on the installation process: https://wiki.pixelexperience.org/devices/begonia/install/
Compass.
I sincerely thank you. I was able to install everything properly with the help of the guide you linked.
Cheers!
So the issue you had was you had to select "ADB Sideload" on TWRP to make the tool detect it
also MIUI automatically replaces your recovery every time you boot to system