Related
Have completed rumrunner root for htc one.
Have installed twrp through adb using command prompt.
Then when trying to reboot system it boots up in recovery.
Need help to find out how to get back on my phone.
Have found similar sites with information but not clear enough for me to understand
I'm able to access twrp so i would assume it's a mount of the sd card but i am not seeing that option anywhere
twrp v 2.6.3.0
I know it's late guys thanks for your help!
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img. please understand that you have overwritten something that is necessary for your phone to work so just open a rom you are preparing to flash and unzip. Copy the boot.img from the unzipped folder and move it to your fastboot folder where your going to open command prompt.
after you open command prompt in the same folder as your adb/fastboot/ and such using shift right click
you then type in the command prompt "fastboot flash boot boot.img" that should flash the boot image back and you should be able to turn on your phone.... wow that took a lot of stress but figured it out in the end. JUST HAD TO GET A GRIP! now happy flashing thanks!
kiit408 said:
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img.
Click to expand...
Click to collapse
Either the tutorial was completely written wrong, or you read them wrong. There's no way of telling which happened, but the point is to be very careful with fastboot.
The command "fastboot flash boot file.img" doesn't flash recovery in your boot partition unless you mis-labeled your .img file and flashed the wrong file in the wrong place.
Most people modding their phones are going to be using fasboot to flash to boot, recovery, system, or bootloader. It's important to understand all of the places that fastboot can flash before you start pushing in .img files. Understanding fastboot commands can also help you possibly identify if someone made a typo in their guides.
Want to put in recovery? "fastboot flash recovery recovery.img". Want to put in a new kernel? "fastboot flash boot boot.img", and so on. Ensure that you've got files that are properly named and you won't ever have to worry about flashing the wrong thing in the wrong place.
kiit408 said:
if you ever get this issue please understand that there are websites out there that are making you use "fastboot flash boot blah.img" which is making you flash recovery on top of your boot img. please understand that you have overwritten something that is necessary for your phone to work so just open a rom you are preparing to flash and unzip. Copy the boot.img from the unzipped folder and move it to your fastboot folder where your going to open command prompt.
after you open command prompt in the same folder as your adb/fastboot/ and such using shift right click
you then type in the command prompt "fastboot flash boot boot.img" that should flash the boot image back and you should be able to turn on your phone.... wow that took a lot of stress but figured it out in the end. JUST HAD TO GET A GRIP! now happy flashing thanks!
Click to expand...
Click to collapse
Jjust understand what you're flashing, you can't 100% trust a tutorial..
If you do the command, fastboot flash boot boot.img, you BEST DAMN be sure that is a kernel/boot.img you are flashing and make sure your working is right, if you fastboot flash a boot.img to say recovery.img, you are screwed.
make sure the file is right my MD5, also make sure the tutorial is good, messing with ANYTHING in fastboot is dangerous.
So i tried to get stock rom back on my htc one m8 which is locked to ee and is a uk phone. I cant seem to get past the bootloader page the white fastboot screen.
Please help me.
You'll need to give a little more information rather than "tried to get stock ROM".
What did you do, what did you flash, are you S-On or S-Off? Have you somehow wiped the /system partition? Do you have a custom recovery installed currently?
Have you even unlocked the bootloader?
EDIT: I have to go now. I'm not sure what situation you're in. I don't normally suggest people use Toolkits and the like, but if you are in difficulties, in the first instance do a search (I doubt if you are the first person to have been in whatever position you are in). If you can't sort yourself out from the results, then have a look at this thread.
nobnut said:
You'll need to give a little more information rather than "tried to get stock ROM".
What did you do, what did you flash, are you S-On or S-Off? Have you somehow wiped the /system partition? Do you have a custom recovery installed currently?
Have you even unlocked the bootloader?
Click to expand...
Click to collapse
S-ON i think the system partion is whiped because i cant do anything other than fastboot the bootloader is locked so i cant get into a custom recovery. I was following a youtube video on how to get back to stock after rooting the the guy had me do a oem command in fastboot.
OK. But I'm not sure that you have actually wiped your /system partition.
Before you do anything, in fastboot mode (the white screen with the mutli coloured writing on it), type the following in a command prompt from the fastboot folder/directory on your PC, then press enter:
Code:
fastboot erase cache
and if that does nothing
Code:
fastboot wipe cache
Then try to reboot by typing
Code:
fastboot reboot
and hit enter.
If that doesn't work, grab the toolkit I linked to and you'll want to
1. Unlock bootloader
2. Flash custom recovery (choose TWRP)
3. Sideload ROM from recovery and follow the relevant instructions in recovery (You'll need to download a ROM to your PC and place it in the relevant directory)
Hey!
So here's the deal:
I'm running LiquidSmooth ROM (KK Version) and I was trying to update the ROM to the newest Lollipop version, but it kept failing. No big deal, i nandroid backed up, and then did a total wipe and tried again. Failed.
Okay, maybe my TWRP recovery was out of date, i tried updating it using the official TWRP app...
then everything went wrong. The install failed and now whenever i ask my phone to go into recovery mode, it sends me into HBoot. I've been trying for 3 days to figure this out, and i cant, so any help would be greatly appreciated.
Im not incredibly well versed at this stuff, so it might have to be a dummy's guide.
in the meantime, here are the details...
When i try to flash ANY custom recovery using ROM Installer app, here is what the error message says:
"COMMAND:
flash image recovery /storage/emulated/legacy/romtoolbox/recoveries/openrecovery-twrp-2.7.1.0-m8.img"
"OUTPUT:
/dev/block/mmcblk0p34: write error: No space left on device
3+0 records in
2+0 records out
1024 bytes transferred in 0.004 secs"
And when i try to reboot into RECOVERY (and it sends me into BOOTLOADER instead), here is the information it gives me:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO - 1.14.21331931.LA02_2G
OpenDSP - v32.2.2-00542-m8974.0213
OS -
eMMC-boot 2048MB
JUNE 16 2014 18:47:55
FASTBOOT USB
thank you so much in advance. i have NO idea what happened... i know the fact that i have S-On might have something to do with it, but i dont have access to a PC, only MACs and i can't use the Sunshine app because i'm already running a custom rom. What can i do?
The thing I noticed is the block that's indicated is not the right one,if you look at the pic below the recovery block is mmcblk0p43.
I would download the custom recovery you want and manually input it "dd" method
Or
Download the custom recovery img and use an app called Flashify
If you can't boot into Android you'll need to fastboot flash your recovery. The one you're using is rather old (I believe 2.8.3.0 is the most recent version). You'll need to download the recovery img file and place it in your ADB/Fastboot folder on your computer. Connect your phone and computer in Fastboot USB mode. Open up a command terminal and type fastboot flash recovery nameofrecovery.img and hit enter (enter the actual recovery file name and not nameofrecovery). The new recovery should then be flashed to your phone, unless you get an error in the terminal on your computer.
As stated above, Flashify works great for flashing recoveries to your phone, but it only works if you can boot into the Android OS.
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Magnum_Enforcer said:
If you can't boot into Android you'll need to fastboot flash your recovery. The one you're using is rather old (I believe 2.8.3.0 is the most recent version). You'll need to download the recovery img file and place it in your ADB/Fastboot folder on your computer. Connect your phone and computer in Fastboot USB mode. Open up a command terminal and type fastboot flash recovery nameofrecovery.img and hit enter (enter the actual recovery file name and not nameofrecovery). The new recovery should then be flashed to your phone, unless you get an error in the terminal on your computer.
As stated above, Flashify works great for flashing recoveries to your phone, but it only works if you can boot into the Android OS.
Click to expand...
Click to collapse
I'll try to flash it from bootloader! Could you tell me how to place the recovery img file into my adb folder? Thank you!!!
nkk71 said:
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Click to expand...
Click to collapse
Oh damn thank you!!! Is this the exact code/command I'll use in Terminal on Mac OS or does it differ since it's not a PC?
jball said:
The thing I noticed is the block that's indicated is not the right one,if you look at the pic below the recovery block is mmcblk0p43.
I would download the custom recovery you want and manually input it "dd" method
Or
Download the custom recovery img and use an app called Flashify
Click to expand...
Click to collapse
What is DD method? Thank you so much for your help
karmendc said:
Oh damn thank you!!! Is this the exact code/command I'll use in Terminal on Mac OS or does it differ since it's not a PC?
Click to expand...
Click to collapse
Don't dd
Don't flashify
Just install mini adb+fastboot for Mac and do the commands mentioned. It's pretty much the same for Windows, Mac and Linux.
Sent from my HTC One_M8 using Tapatalk
nkk71 said:
Don't dd
Don't flashify
Just install mini adb+fastboot for Mac and do the commands mentioned. It's pretty much the same for Windows, Mac and Linux.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Why do you think I've mentioned the other methods.
Not everyone understands how to use fastboot like we do.
If he has a bootable OS than Flashify will work just fine (I wouldn't recommend an app that I haven't tried/used myself)
karmendc said:
What is DD method? Thank you so much for your help
Click to expand...
Click to collapse
dd is a method using a terminal emulator on your device.
The screenshot is from the twrp website and the "dd" method is described as a working method if in fact you can boot to the OS (SuperSU is needed)
jball said:
Why do you think I've mentioned the other methods.
Not everyone understands how to use fastboot like we do.
If he has a bootable OS than Flashify will work just fine (I wouldn't recommend an app that I haven't tried/used myself)
Click to expand...
Click to collapse
Because flashify, TWRP manager, ROM manager, etc apps expect the proper device info in build.prop
and will then dd whatever partition it sees fit... In this case, it thinks it's an m7
fastboot flash does not.
Sent from my HTC One_M8 using Tapatalk
nkk71 said:
Because flashify, TWRP manager, ROM manager, etc apps expect the proper device info in build.prop
and will then dd whatever partition it sees fit... In this case, it thinks it's an m7
fastboot flash does not.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I read what you've stated already.
I agree the sure fire way is fastboot .
Easy for you
Easy for me
But maybe not so easy for some.
As long as the OP gets what he wants is all I'm in here for(not a long drawn out tutorial as those already exist)
jball said:
I read what you've stated already.
I agree the sure fire way is fastboot .
Easy for you
Easy for me
But maybe not so easy for some.
As long as the OP gets what he wants is all I'm in here for(not a long drawn out tutorial as those already exist)
Click to expand...
Click to collapse
Sorry if my answers are short and not in much detail, I'm typing on the phone... I prefer a full keyboard
But dd is not something I easily recommend (much more difficult than fastboot flash)
and if you check the build.prop of the ROM mentioned by the OP you'd see it's not entirely proper
I've seen enough bricks due to "flashy apps" and one-clicks (no offence intended to any)
fastboot at least does some checking of what is being flashed and where, so that is what I personally recommend.
Sent from my HTC One_M8 using Tapatalk
nkk71 said:
Sorry if my answers are short and not in much detail, I'm typing on the phone... I prefer a full keyboard
But dd is not something I easily recommend (much more difficult than fastboot flash)
and if you check the build.prop of the ROM mentioned by the OP you'd see it's not entirely proper
I've seen enough bricks due to "flashy apps" and one-clicks (no offence intended to any)
fastboot at least does some checking of what is being flashed and where, so that is what I personally recommend.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you for the more detailed information.
Small keyboards blow for sure.
@nkk71 warning is quite valid
dd used correctly, but ideally from a script, is very useful and powerful.
dd is also affectionately know as 'disk destroyer'
just one small typo, or worse getting the input and output reversed, can really make a mess.
it will write more or less anything to anything including your boot sector and data.
just saying.
gazzacbr said:
@nkk71 warning is quite valid
dd used correctly, but ideally from a script, is very useful and powerful.
dd is also affectionately know as 'disk destroyer'
just one small typo, or worse getting the input and output reversed, can really make a mess.
it will write more or less anything to anything including your boot sector and data.
just saying.
Click to expand...
Click to collapse
Thank you for the second opinion kind sir.
http://www.youtube.com/watch?v=JUCM_tJaNHU
Here is a short video on how to input the "fastboot flash recovery recovery.img " command once you have drivers correctly installed and the img file in the proper location .
Now this video is from a tablet to my HTC one m8 and not from a
PC/Desktop as it's over obvious.
Just like all other videos I don't show how to "easily" set up the drivers for fastboot (oh that's cause you don't need drivers to adb or fastboot from a tablet to a phone).
nkk71 said:
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Click to expand...
Click to collapse
Okay so i finally tried flashing it using Terminal/FASTBOOT... I downloaded the latest TWRP recovery for GSM, placed it in my adb/fastboot folder...and typed in the command and it came up with an error. Here are the screenshots. Help? Im at my wits end.... thank you in advance!
wait, i got it! flashed!! I was in the wrong directory, i guess. So now i got into the correct directory, but the phone still wont go into recovery when i reboot. :crying:
Sigh. okay, back to square one.
edit:
and great. i think that "erase cache" command unmounted my internal storage...because now i get no phone signal and my local storage cannot be found.
What. is. happening.
karmendc said:
wait, i got it! flashed!! I was in the wrong directory, i guess. So now i got into the correct directory, but the phone still wont go into recovery when i reboot. :crying:
Sigh. okay, back to square one.
edit:
and great. i think that "erase cache" command unmounted my internal storage...because now i get no phone signal and my local storage cannot be found.
What. is. happening.
Click to expand...
Click to collapse
1) you're on hboot 3.18 so that would indicate you firmware (the OS- line or version-main from a fastboot getvar all) is still 2.xx.xxx.x version, so yes, you're going to have signal and wifi problems, as mentioned in the various ROM threads you need matching firmware to the ROM you're running.
2) this could also be the reason it's not entering the recovery, you could try an older version of TWRP, and make sure MD5 checks out on your download, a corrupt download could also be the reason
3) the "fastboot erase cache" doesnt affect your internal storage or anything, it just wipes the cache which will get rebuilt as needed
4) missing/not mounted internal storage, is a common issue on Android 5.x (not only HTC, many devices), download a terminal emulator to your phone (or alternatively open an abd shell), and do the following commands:
Code:
su
restorecon -FR /data/media/0
So i combed through the threads and either i missed it or it was removed but i'll ask anyways. So, BND-L24 with unlocked bootloader, no root, no twrp installed. How do I go about backing up my stock files. I tried booting into the twrp image through fastboot and it kept saying "remote connection not allowed" or something along that line. I'd like to back up everything including the stock recoveries and have something to fall back on in the event that something goes not to my liking. So what options do i have as far as this goes? Backup through a booted (not flashed) TWRP, backup through ADB commands? Any knowledge would be appreciated.
Here's a backup .bat file.
May want to try flashing TWRP instead of booting
You need to ADB while in TWRP, make sure you have a microSD card installed.
Its just a $ shell
https://drive.google.com/open?id=1AkZ0s7FIa8vvgQwGOiDaAEuaixNGDWEl
tlxxxsracer said:
Here's a backup .bat file.
May want to try flashing TWRP instead of booting
You need to ADB while in TWRP, make sure you have a microSD card installed.
Its just a $ shell
https://drive.google.com/open?id=1AkZ0s7FIa8vvgQwGOiDaAEuaixNGDWEl
Click to expand...
Click to collapse
But if I flash twrp, I won't be able to backup the stock recovery correct? So if something goes wrong down the line I won't be able to revert back to compete stock or install ota updates
boot into twrp dont flash, that way stock recovery isnt touched
tlxxxsracer said:
boot into twrp dont flash, that way stock recovery isnt touched
Click to expand...
Click to collapse
That's what I was attempting do but it wouldn't boot into it. It kept saying failed. I think I tried two different versions of twrp that are posted. Is there a different command line besides "fastboot boot twrp.img" that I need to be using? Or am I missing something else? I unlocked the bootloader and it is showing up in "fastboot devices" I moved the recovery image into the adb folder and renamed it twrp.img. Should've been pretty straight forward, never had problems with adb before
str8stryk3r said:
That's what I was attempting do but it wouldn't boot into it. It kept saying failed. I think I tried two different versions of twrp that are posted. Is there a different command line besides "fastboot boot twrp.img" that I need to be using? Or am I missing something else? I unlocked the bootloader and it is showing up in "fastboot devices" I moved the recovery image into the adb folder and renamed it twrp.img. Should've been pretty straight forward, never had problems with adb before
Click to expand...
Click to collapse
Hey OP were you able to figure this out?
mjtschmid said:
Hey OP were you able to figure this out?
Click to expand...
Click to collapse
Nah man. I thought about doing the no twrp install root method posted but decided against it because the twrp available isn't 100% made for our phone. And I keep reading they disabled "fastboot boot" command. I'm gonna hold off until they release the stock firmware did the L24 before I did into root and twrp
Well I can tell you I followed the steps for backup and took it for granted that it worked. Turns out my system.img and userdata.img we're 0 bytes. If someone has done it successfully I would appreciate if they posted their system.img for BND-L24
i'm not 100% sure but i think in order to boot twrp using "fastboot boot" command you have to specify, according to "fastboot help" , it's something like "fastboot [kernel] [ramdisk] boot [xxx.img]" and in other posts i see it being written as "fastboot -c "lge.kcal=0|0|0|x" boot <path to recover.img>" but i'm not sure which device that's for. i don't mess with adb and fastboot enough to know what's going on in there. maybe one of you guys can figure it out.
How do I find a post #??I was told to look at ..... .....post # but how do I find this???
Yesterday I had the excellent idea of rooting my phone and installing a custom ROM. The process was quite easy though it took me like 2 hours. After I was done I found that I didn't really like the Lineage OS on my M8 as it was draining my battery way too fast. So I decided to go back. This is where the problems began. Since being a total noob when it comes to rooting and flashing on Android I had no idea I had to make a backup of my OS(only did one of my data using HTC Sync Manager). I was able to find one online in the end. But when I wanted to update OTA to 6.1.0 it just boots into Recovery Mode. After some research I found out that I also have to flash a stock recovery file. I allegedly did that using a tool I found online (One M8 All in One Kit 2.0). But still I am unable to update OTA. I just want to go back to Marshmallow.
Would really appreciate some help here guys
Thanks.
Tupi311 said:
Yesterday I had the excellent idea of rooting my phone and installing a custom ROM. The process was quite easy though it took me like 2 hours. After I was done I found that I didn't really like the Lineage OS on my M8 as it was draining my battery way too fast. So I decided to go back. This is where the problems began. Since being a total noob when it comes to rooting and flashing on Android I had no idea I had to make a backup of my OS(only did one of my data using HTC Sync Manager). I was able to find one online in the end. But when I wanted to update OTA to 6.1.0 it just boots into Recovery Mode. After some research I found out that I also have to flash a stock recovery file. I allegedly did that using a tool I found online (One M8 All in One Kit 2.0). But still I am unable to update OTA. I just want to go back to Marshmallow.
Would really appreciate some help here guys
Thanks.
Click to expand...
Click to collapse
You could just run an RUU to get back to stock, since you already flashed the stock backup and have lost data now.
What does it say next to "OS" in your bootloader? With that information I can link you to the proper RUU
xunholyx said:
You could just run an RUU to get back to stock, since you already flashed the stock backup and have lost data now.
What does it say next to "OS" in your bootloader? With that information I can link you to the proper RUU
Click to expand...
Click to collapse
6.12.401.4
I don't quite understand how this RUU works. Will it still say in bootloader "Software status:Modified" after I do this? And will I have to unroot it again or how does it work? Cause it still says Unlocked in bootloader.
Tupi311 said:
6.12.401.4
I don't quite understand how this RUU works. Will it still say in bootloader "Software status:Modified" after I do this? And will I have to unroot it again or how does it work? Cause it still says Unlocked in bootloader.
Click to expand...
Click to collapse
The RUU will take you back to stock unrooted.
I forgot to ask if it said S-On or S-Off in your bootloader. I'll give full instructions for both.
Download this RUU.zip and place it into your adb/fastboot folder
Boot to bootloader and plug your phone into your PC, then get into fastboot
If you are S-On, enter fastboot oem lock That will relock your bootloader. If you are S-Off you can skip this step
Then: fastboot oem rebootRUU wait until the phone boots to a black screen with HTC on it
then fastboot flash zip **drag and drop the RUU.zip here**
When the flash is done, fastboot reboot and you'll be back to stock, unrooted
xunholyx said:
The RUU will take you back to stock unrooted.
I forgot to ask if it said S-On or S-Off in your bootloader. I'll give full instructions for both.
Download this RUU.zip and place it into your adb/fastboot folder
Boot to bootloader and plug your phone into your PC, then get into fastboot
If you are S-On, enter fastboot oem lock That will relock your bootloader. If you are S-Off you can skip this step
Then: fastboot oem rebootRUU wait until the phone boots to a black screen with HTC on it
then fastboot flash zip **drag and drop the RUU.zip here**
When the flash is done, fastboot reboot and you'll be back to stock, unrooted
Click to expand...
Click to collapse
This is exactly what I was talking about. I don't understand how to do those "bolded" instructions. Does it have something to do with the Android SDK? I know I read something.
I am on S-ON btw.
Tupi311 said:
This is exactly what I was talking about. I don't understand how to do those "bolded" instructions. Does it have something to do with the Android SDK? I know I read something.
I am on S-ON btw.
Click to expand...
Click to collapse
So there is the main problem with toolkits. I never use them and never recommend them. Reason being: they shortcut the learning process, and teach you just enough to get into trouble. Then you are stuck with no idea how to recover.
Knowing how to use fastboot (at least on a basic level) is absolutely mandatory in order to unlock the bootloader, and flash custom recovery (for the purpose or root or custom ROM). The manufacturers set it up this way, for a reason. Essentially, if a user doesn't know how to use fastboot, they have no business unlocking the bootloader. The makers of the toolkits bypass this requirement with the intent to make it "easier" for folks to root/ flash custom ROM (the toolkit issued fastboot commands, whether you know it or not). But as already mentioned, it's not a good idea to do that.
I don't blame you. You only know what you know, and we all were n00bs at some point, and had to start somewhere. But my advice to you, would be to learn the basics of what fastboot is about, and how to use it. Plus, there is a lot of nuance here. You actually have to use htc_fastboot to flash the RUU (the "generic" Google fastboot can't handle the large file size). You can get it (as well as the RUU) from the following thread:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
From there, you need to open the command prompt from whatever folder/directory htc_fastboot.exe or fastboot.exe (respectively) are located. There is a shortcut for doing this:
1) Open folder in Windows, where fastboot.exe (htc_fastboot.exe) is located. Different fastboot installers will install it to different places, so you will have to find it yourself.
2) Hover mouse over the folder, press Shift+Right mouse button. This will open a menu, from which you want to select "Open command window here"
3) The command prompt window will open, and that is where you want to type your fastboot commands.
Another note (and I know this will probably be confusing), I think that you can use htc_fastboot for all the fastboot commands (no need to flip flop between htc_fastboot and fastboot). You just have to use "htc_" before all the fastboot commands. For instance:
htc_fastboot oem lock
redpoint73 said:
So there is the main problem with toolkits. I never use them and never recommend them. Reason being: they shortcut the learning process, and teach you just enough to get into trouble. Then you are stuck with no idea how to recover.
Knowing how to use fastboot (at least on a basic level) is absolutely mandatory in order to unlock the bootloader, and flash custom recovery (for the purpose or root or custom ROM). The manufacturers set it up this way, for a reason. Essentially, if a user doesn't know how to use fastboot, they have no business unlocking the bootloader. The makers of the toolkits bypass this requirement with the intent to make it "easier" for folks to root/ flash custom ROM (the toolkit issued fastboot commands, whether you know it or not). But as already mentioned, it's not a good idea to do that.
I don't blame you. You only know what you know, and we all were n00bs at some point, and had to start somewhere. But my advice to you, would be to learn the basics of what fastboot is about, and how to use it. Plus, there is a lot of nuance here. You actually have to use htc_fastboot to flash the RUU (the "generic" Google fastboot can't handle the large file size). You can get it (as well as the RUU) from the following thread:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
From there, you need to open the command prompt from whatever folder/directory htc_fastboot.exe or fastboot.exe (respectively) are located. There is a shortcut for doing this:
1) Open folder in Windows, where fastboot.exe (htc_fastboot.exe) is located. Different fastboot installers will install it to different places, so you will have to find it yourself.
2) Hover mouse over the folder, press Shift+Right mouse button. This will open a menu, from which you want to select "Open command window here"
3) The command prompt window will open, and that is where you want to type your fastboot commands.
Another note (and I know this will probably be confusing), I think that you can use htc_fastboot for all the fastboot commands (no need to flip flop between htc_fastboot and fastboot). You just have to use "htc_" before all the fastboot commands. For instance:
htc_fastboot oem lock
Click to expand...
Click to collapse
I followed those steps but when I tried and flash it it gave me this error "target reported max download size of 1826418688 bytes" and I found no real solution to this online.
On a side note I already had the HTC Sync manager installed and I used it to backup some stuff so I can't uninstall it(according to the guide I have to uninstall it, but I guess that's just a suggestion since uninstalling it shouldn't interfere).
Though I feel like I'm close to succeeding.
Tupi311 said:
I followed those steps but when I tried and flash it it gave me this error "target reported max download size of 1826418688 bytes" and I found no real solution to this online.
Click to expand...
Click to collapse
Did you use htc_fastboot? The file size error is usually due to using the wrong fastboot (you need to use htc_fastboot, as the "generic" fastboot can't handle the file size).
Tupi311 said:
On a side note I already had the HTC Sync manager installed and I used it to backup some stuff so I can't uninstall it(according to the guide I have to uninstall it, but I guess that's just a suggestion since uninstalling it shouldn't interfere).
Click to expand...
Click to collapse
I've left HTC Sync installed without any issues. Like you said, it's mostly a suggestion.
Also, just a suggestion:but I would recommend to refrain from quoting someone else's long post (like you quoted my last post). I know it is the default when replying, to include the quote. But just delete what you aren't directly replying to (quote few lines at most) to avoid cluttering up the thread with redundant text.
redpoint73 said:
Did you use htc_fastboot? The file size error is usually due to using the wrong fastboot (you need to use htc_fastboot, as the "generic" fastboot can't handle the file size).
Click to expand...
Click to collapse
Seems like my pc didn't like that I was using those commands and I had to use \.htc_fastboot . It's all good now. Thank you very much. Have a good day.