Related
For noobs their is alot of overwhelming info in regards to doing this and seems to be a lil more simple on other models.....have read for hours on the forum and seems to be conflicting info and also a kernel file issue on the rogers dream rooting has me a lil confused....i have had my phone for 6 months and customized as much as you can without a root but i am getting bored and is time to play with it...wanna run roms and all the latest stuff on it and have access to the paid market and save to my sd card and all that other good stuff everyone else is doing.....lol.....i don't want to brick my phone but i would like to root it.....
okay to the point..................
now when i open Flash Rec the "Flash Custom Recovery Image" button does not even appear and i cannot get to the into Recovery mode.
One thing i noticed in Flash Rec says Phone type is EB1/32A...thought would be 32B? could this be a problem from trying to flash earlier?
i need rooting rogers dream 32b for dummies instructions....lol....
p.s someone needs to develop idiot proof rooting software with android ready to explode their will be alot of noobs with bricks.....lol.....
Here's the tutorial I suggest following:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
And yes it does work with 32B. I cannot stress the importance of making sure you know and are 100% comfortable with what you're doing to your phone. If you have to annoy the heck out of xda users to do so then by all means do it .
wow,seems like the rogers dream is more of a pain to root and a little limited cause of kernel issue....sounds like it could make adding future roms a pain cause they could be buggy.....
Its really not that bad if you just want to stick with cyanogen because the EBI1 port is always released promptly. There might be some other EBI1 roms posted in the sapphire development section, check it out. There is another method that makes your the rogers dream compatible with any rom that works on the G1. Some people have reported some connection issues with this method but it works fine for many others. I would only recommend going with that method if the selection of EBI1 roms isn't enough for you.
http://forum.xda-developers.com/showpost.php?p=4280573&postcount=130
The rogers dream is actually EBI1/32B. The reason it says 32A is posted here.
If you have any questions about this be sure to ask away before you decide to root.
i would like to be able to run the latest roms 2.0 and 2.1 once stable and new and up coming roms,sense ui and gadgets..... is it better to go with the other method you mentioned then the cyanogenmod based on that?
thanks for your help
okay am going cyanogenmod way ....lil issue before i move on......
the cm-recovery screen should say "CyanogenMod v1.4 + JF but is saying CyanogenMod v1.2 + JF .. . . .. . . .
lol
what did i miss used the wiki guide and files.......
i downloaded everything according to the wiki page..... am i missing something or doing something wrong that would cause it to load v1.2 instead of v1.4?
soloution found and moved on am at this part now with a new issue
Type the following commands to wipe your Rogers system image (and userdata, and cache) and replace it with the HTC image:
fastboot erase system -w
fastboot flash system system.img
The system will flash and you will see a green progress bar on the fastboot screen while the image is transferring and a red progress bar while it's installing.
Click to expand...
Click to collapse
got past erasing part......
then when type in fastboot flash system system.img i get error: cannot load 'system.img'
chrisyak said:
then when type in fastboot flash system system.img i get error: cannot load 'system.img'
Click to expand...
Click to collapse
Make sure that the system.img file you downloaded is in the same folder as fastboot (the "tools" folder).
I put the system.img file in the same folder as fastboot (the "tools" folder) on my computer and tried it once again only to receive the same error message.
chrisyak said:
I put the system.img file in the same folder as fastboot (the "tools" folder) on my computer and tried it once again only to receive the same error message.
Click to expand...
Click to collapse
It does need to be in that folder but I am not sure why you are still getting that same message. You could try rebooting your phone and starting that section over again. The file could be corrupt. Verify the MD5 sum that is posted on the guide.
Edit: You need to cd to the tools directory before running that command
WIP Guide Up But Missing Pictures... When I Find Time I Will Do This For You
Im aware this is the guide set out by someone else.... I dont claim it as my own but i want to help people who are not sure about the android environment
Please note this will be for Unbranded Devices Only.
If you bought an O2 Desire C, Your ****ta Outta Luck My Friend...
RELOCKING BOOTLOADER
First thing you need to do is download the stock ROM (also known as a RUU for you newbs out there ) here.
Just realized there's the new RUU in a post here in this forum! If you want the newer RUU (2.0) get it here
Download from the first post
Once you've got that .exe, run the wizard until you get to the first screen. Now you need to find the temporary folder that it just extracted all its files into... open My Computer and at the top of the screen, in the navigation bar, type %temp%. There's probably a whole bunch of stuff, but look for two folders that have really long, messy (encrypted) names. One of them will have ROM.zip in it.
EDIT: If you have Nameless installed, or you used superboot, then go into the apps on your phone and select "SuperSU" and go into the menu. Look for the "Cleanup for full unroot" option and run that first. This should help with any problems.
Open this ROM.zip with WinRAR and extract recovery.img to C:\Android
IF IT ASKS YOU TO OVERWRITE because you have your CWM recovery file in there still, make sure you copy THAT one somewhere else so you don't have to re-download it if you later want to re-install this recovery.
Open up command (cmd) and dir to your C:\Android
Type in fastboot flash recovery recovery.img
Once this is done, go back to the wizard you still have open and let it finish. If you're having any problems with the above steps simply post in this thread or email me, my address is above somewhere.
After THAT is done, open cmd back up and type in fastboot oem lock
NOTE: After you're done these steps, your bootloader will say ***RELOCKED*** it is impossible to get it back to ***LOCKED*** once you've unlocked the bootloader.
That is awesome, I have a Nexus 4 on the way to replace my Desire C and want to return it to stock
Looking foward to your guide.
xorrbit said:
That is awesome, I have a Nexus 4 on the way to replace my Desire C and want to return it to stock
Looking foward to your guide.
Click to expand...
Click to collapse
Good choice, im going to buy a HTC Evo 3d tomorrow, i like the device as ive had it before ^__^
The guide is a WIP as on 2 occasions ive already bricked my phone tonight haha ^__^
Guide ?
Whats up with the guide , when will it be ready ?
Apologies Guys, Ive found there is already a guide to it... Ill post the link below, however iwhat i will do is a step by step picture guide on how to do it ,
fkofilee said:
Apologies Guys, Ive found there is already a guide to it... Ill post the link below, however iwhat i will do is a step by step picture guide on how to do it ,
Click to expand...
Click to collapse
I need it. Could you please post the link first? Thanks.
Or you could just use this http://forum.xda-developers.com/showthread.php?p=36529211#post36529211
wub901 said:
Or you could just use this http://forum.xda-developers.com/showthread.php?p=36529211#post36529211
Click to expand...
Click to collapse
Remember, this was written before the Stock Rom Was Produced.
I was sending peeps in the right direction
Sent from my LT26i using xda premium
Hello,
Links to RUU are dead :crying:
Cheers
One quick correction, You have to relock the bootloader with fastboot oem lock BEFORE you try to reinstall, or the update will fail with FAILED (remote: 99 unknown fail) in log.
download link doenst work!
both RUU links dead!
RUU
Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2
Mindstar1 said:
Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off
Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root
Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root
Click to expand...
Click to collapse
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2
What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off
Click to expand...
Click to collapse
How do I check which hboot I have?
Sent from my HTC One using Tapatalk 2
At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app
NxNW said:
At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
OK, I just did what you said and the HBOOT is 1.44.0000. So, based on what was said earlier, I am good to do the Revone option? If I do Revone, what am I missing out on compared to any other option? Thanks for the help!
Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.
Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Mindstar1 said:
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Click to expand...
Click to collapse
Yeah, I want to flash. If all I do is root, am I still able to flash other ROMs? I can never keep straight what each of the different processes do.
NxNW said:
Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.
Click to expand...
Click to collapse
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942. My goal is to flash 4.2.2 roms and soon 4.3, so would I want to do both or just Revone.
Mindstar1 said:
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942.
Click to expand...
Click to collapse
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.
NxNW said:
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.
Click to expand...
Click to collapse
Its funny, I came across the first article while looking for answers while I waited for your response. I never mess with radios so S-Off is not really important to me. The second article was even better and more clear so I think I know where I am now.
The last question for you is what you would suggest I use for the most trouble free rooting process. I am looking for a pretty low impact route, and you did seem to imply that it took some work to get revone working for you. The toolkit seems to be a good way to go, but it also says that it unlocks the boot, which I already have with the dev edition. Will that be a problem if the process tries to unlock an already unlocked phone?
Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.
NxNW said:
Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.
Click to expand...
Click to collapse
I ran into an issue following your directions (which were basically the same as the YouTube video about the "easiest way to install custom recovery for the htcone" that I got off another xda thread. I run the command to fastboot flash recovery, and my PC gives me an error saying that fastboot is not a valid command. I have the proper drivers installed, and I am in fastboot on my phone but it won't work. I did notice that on the thread you linked to above, they want my recovery file to be in some sdk folder or something. My directions didn't mention that and the directions you linked to mention an sdk file in the bootloader section, but it tells me to skip that if I have a dev edition. Is the sdk file the reason why my computer won't recognize the command? For what it's worth, I tried that toolkit and it did not seem to recognize my phone either.
Sent from my HTC One using Tapatalk 2
EDIT Just a general tip - you can copy the text of any error message you get and paste it into google and you will doubtless turn up a bunch of interesting info - you are very likely not the first person to encounter the issue.
Anyway here's what I think is happening:
Sometimes when you try to give a command from the command line, a computer doesn't know where the necessary executable file is.
If the SDK was installed ok , then somewhere on your computer is the actual fastboot.exe executable.
Find it.
If it is in a folder called C:\path\to\files\blah\blah then you need to actually type out C:\path\to\files\blah\blah\fastboot.exe to run it.
If you will be doing more commands in this location or any commands that refer to other files in the same location (and some if these procedures assume you will since you'll be putting the flashable image files in this location), you really should tell your terminal program to just change the "working directory" to that location: then whenever you refer to something the computer will look there first. Here's how that looks:
cd C:\path\to\files\blah\blah
fastboot
(Final note- going forward you can make it easier to launch executables by adding their location to your "PATH variable" - google it. )
Maybe you knew all this? But for the benefit of anyone else following these bread crumbs, here's the upshot: Most of these "procedures" that people write down assume some general knowledge of command line syntax. If you're not comfortable with that yet, you're going to need to be persistent and search google a lot.
all,
it was with reckless abandon and blind/naive decisions that got me to this point. i will just lay it all out what ive done in the hopes one of you brilliant minds will lead me into the light. before i lay out the steps in which ridiculous choices led me to this conundrum, here is the question...
Where do i go from here to resolve the issue that i have and can get into bootloader (tampered/unlocked and in S-ON) but i have no operating system?
keep in mind that Ive probably and admittedly should not have been dabbling in things i had no business doing with the little to no proper due diligence...."i am awarded no points and may god have mercy on my soul!!!!!!!!!!!!"
1) i used the htc dev process to unlock my bootloader and it worked well.
2) i then proceeded to flash some custom recovery .img files via "fastboot flash recovery <insert filename here" and the .img at the end of course.
recovery-clockwork-touch-6.0.3.4-m7 <---didnt take the first time or anytime. kept saying "entering recovery" but then the screen would go black, not boot into the recovery screen and then the phone would reboot as it would normally and go into stock OS
i then tried the following .img files below, all with the same result...
openrecovery-twrp-2.6.0.1-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.5.0.0-m7
recovery-clockwork-6.0.3.2-m7ul <<<---this was the only recovery .img file that would take so i then decided to play around with the options.
3) i then proceeded to make another ridiculous choice. under one of the options in clockwork recovery "classic" menus i went forth and selected the "wipe data/factory reset" option.
so what i have now is i believe a htc one sprint phone that has bootloader unlocked with what i believe is no OS. i hear on my computer the sound when it connects via "fastboot usb" but obviously the computer doesn't recognize it so i can copy and paste a zip file onto it.
i was looking at a few threads here and could really use some guidance/encouragement. the threads are
http://forum.xda-developers.com/showthread.php?t=2277892 <<< the FAQ sticky
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [ROM] stock sprint one 1.31.651.2 thread
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [RUU] sprint htc one 1.29.651.10 thread
what would be the best course of action for me to take? bear in mind that the end result would probably be obviously a working phone, probably stock or w/e seems best.
thank you for taking the time in reading my post. if you require any additional information, please ask. i am probably leaving out important pieces of info.
deadly
All you need to do is fastboot flash recovery a working recovery then check and see if adb works for you in recovery.
If it does then you can adb push a Rom to /sdcard and flash it in the recovery.
Sent from my HTCONE using xda app-developers app
insuusvenerati said:
All you need to do is fastboot flash recovery a working recovery then check and see if adb works for you in recovery.
If it does then you can adb push a Rom to /sdcard and flash it in the recovery.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
thank you for your quickresponse.
as i am very very "scared" to this up any further. what would the suggested "working recovery" file i should choose and then what rom should i use? honestly im tempted at the stock one that i linked but im worried that if that doesnt go smoothly, i will lose my unlocked bootloader feature.
deadlytwin said:
thank you for your quickresponse.
as i am very very "scared" to this up any further. what would the suggested "working recovery" file i should choose and then what rom should i use? honestly im tempted at the stock one that i linked but im worried that if that doesnt go smoothly, i will lose my unlocked bootloader feature.
Click to expand...
Click to collapse
Use this tool, you cant mess up http://forum.xda-developers.com/showthread.php?t=2236814 just make sure you use the Sprint recoveries and download and sideload a sprint Rom.
Konfuzion said:
Use this tool, you cant mess up http://forum.xda-developers.com/showthread.php?t=2236814 just make sure you use the Sprint recoveries and download and sideload a sprint Rom.
Click to expand...
Click to collapse
THANKS! i saw this thread earlier. ill take a look. ive at least watched wwjoshdew's video and i think that should work too. downloading the stuff now.
just tried wwjoshdew's directions. looks like i cant do the RUU 1.29xxxx. it goes through all the steps but at the end it says error because of the 1.31xxxx version i have already. i guess that means i have to wait until someone releases an RUU for 1.31.651.2
and if i am not sure if usb debugging mode ins enabled and i cant get back into normal bootup for the phone because i think i wiped my OS like stated in my first post. is my next step to do hansoon's AIO tool kit?
deadlytwin said:
all,
it was with reckless abandon and blind/naive decisions that got me to this point. i will just lay it all out what ive done in the hopes one of you brilliant minds will lead me into the light. before i lay out the steps in which ridiculous choices led me to this conundrum, here is the question...
Where do i go from here to resolve the issue that i have and can get into bootloader (tampered/unlocked and in S-ON) but i have no operating system?
keep in mind that Ive probably and admittedly should not have been dabbling in things i had no business doing with the little to no proper due diligence...."i am awarded no points and may god have mercy on my soul!!!!!!!!!!!!"
1) i used the htc dev process to unlock my bootloader and it worked well.
2) i then proceeded to flash some custom recovery .img files via "fastboot flash recovery <insert filename here" and the .img at the end of course.
recovery-clockwork-touch-6.0.3.4-m7 <---didnt take the first time or anytime. kept saying "entering recovery" but then the screen would go black, not boot into the recovery screen and then the phone would reboot as it would normally and go into stock OS
i then tried the following .img files below, all with the same result...
openrecovery-twrp-2.6.0.1-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.5.0.0-m7
recovery-clockwork-6.0.3.2-m7ul <<<---this was the only recovery .img file that would take so i then decided to play around with the options.
3) i then proceeded to make another ridiculous choice. under one of the options in clockwork recovery "classic" menus i went forth and selected the "wipe data/factory reset" option.
so what i have now is i believe a htc one sprint phone that has bootloader unlocked with what i believe is no OS. i hear on my computer the sound when it connects via "fastboot usb" but obviously the computer doesn't recognize it so i can copy and paste a zip file onto it.
i was looking at a few threads here and could really use some guidance/encouragement. the threads are
http://forum.xda-developers.com/showthread.php?t=2277892 <<< the FAQ sticky
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [ROM] stock sprint one 1.31.651.2 thread
http://forum.xda-developers.com/showthread.php?t=2368907 <<< the [RUU] sprint htc one 1.29.651.10 thread
what would be the best course of action for me to take? bear in mind that the end result would probably be obviously a working phone, probably stock or w/e seems best.
thank you for taking the time in reading my post. if you require any additional information, please ask. i am probably leaving out important pieces of info.
deadly
Click to expand...
Click to collapse
first off thats the wrong recovery, you want openrecovery-twrp-2.5.0.0-m7wls.img (this is for sprint the m7 is international)2.6 has been giving some problems, don't know if they have it worked out yet, 2.5 is good, so
deadlytwin said:
just tried wwjoshdew's directions. looks like i cant do the RUU 1.29xxxx. it goes through all the steps but at the end it says error because of the 1.31xxxx version i have already. i guess that means i have to wait until someone releases an RUU for 1.31.651.2
and if i am not sure if usb debugging mode ins enabled and i cant get back into normal bootup for the phone because i think i wiped my OS like stated in my first post. is my next step to do hansoon's AIO tool kit?
Click to expand...
Click to collapse
Use the tool I posted above and try to install htc drivers, install recovery and sideload a SPRINT rom. You could also try s-off and follow this guide for RUU on 1.31 if your still having trouble. http://forum.xda-developers.com/showthread.php?t=2390821
Konfuzion said:
Use the tool I posted above and try to install htc drivers, install recovery and sideload a SPRINT rom. You could also try s-off and follow this guide for RUU on 1.31 if your still having trouble. http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
appreciate it!
Update: yea my phone is not in usb debugging mode. ><
Aldo101t said:
first off thats the wrong recovery, you want openrecovery-twrp-2.5.0.0-m7wls.img (this is for sprint the m7 is international)2.6 has been giving some problems, don't know if they have it worked out yet, 2.5 is good, so
Click to expand...
Click to collapse
ill check this.
Update: im in recovery now. next step isnt looking so good ><
so this is starting to look bleak. i am now able to get into recovery but i cant do adb sideload. it fails. has it got to do with the possibility that usb debugging was not turned on before i wiped data?
any ideas on my next try?
deadlytwin said:
so this is starting to look bleak. i am now able to get into recovery but i cant do adb sideload. it fails. has it got to do with the possibility that usb debugging was not turned on before i wiped data?
any ideas on my next try?
Click to expand...
Click to collapse
go to file manager in twrp and see if there is an 0 folder at the top if so delete it(make sure its empty first) then try a sideload
or use es file explorer and look at your files
HOW TO get your HTC One M8S back to Factory / stock.
Attention 1: This is NOT for the regular HTC One M8.
Attention 2: This is for the HTC One M8S also known as the M8_QL_UL
(The One M8S does not have a separate subforum on XDA.)
Hi everyone! I saw that many people who have a HTC One M8S have problems with restoring the stock HTC RUU. It is a little bit difficult. So here I'll supply you again with steps that worked for me.
Most of this is a copy from a post I made earlier. But I saw that many of you still have some problems. So here is a dedicated thread.
I have used this method multiple times to restore my phone back to factory defaults. I hope it works for you too!
Warning. You will lose your settings. Everything will be reset to the defaults.
Read these important notes before you begin!
When you need fastboot: only HTC's own fastboot program will work. You will use fastboot, for example, when you want to flash a custom recovery.
Other fastboot applications will not work correctly in my experience! So be sure you use HTC's.
If you need it: HTC will send you a link when you unlock your bootloader. But you can also find fastboot via the same page as where you can find the RUUs.... see below.
Do you have an SDCard ready? You must have one to get this to work and it must be big enough. ADB sideload will NOT work!
Is your phone relocked? It must be! If not, relock it, then come back.
Most of the problems happen because people read too fast. This stuff just takes a long time.. so don't do it if you are in a hurry. And do read carefully.
Are you ready? Ok! Here we go.
Download the RUU zip you want to use. I have used ...HTC_Europe_1.16... BUT later I found this did not allow the newest OTA update (as of august 30th, 2015). Maybe I will test 1.11 some day later.
However, I think that 1.11 is the right version. Not sure where to download the RUU or fastboot? Click the button.
For me, I downloaded the RUU zip via the generous hosting by @El-Conkistador. You can find it via his post here. On his page there is a directory called Firmware (Expert). In there is a directory called Firmware Crypted (Original HTC). In that directory are multiple directories containing RUUs. Choose one for your device, download it, then come back here.
Open your sdcard. It must be fat32 or exFAT formatted.
Copy the RUU zip file onto the root of the sdcard. Do NOT extract it. Just copy it.
You must now rename it to: 0PKVIMG.zip. The first character is the number 0 (zero), not the letter O!
If you know how to do this, take the md5sum from the RUU zip on your computer, and 0PKVIMG.zip on your SDcard. They must be the same! If not, there can be a problem with your SDCard.
Safely unload and remove the SDCard from your computer.
Power off your phone.
Are you sure you want to continue? Then insert the SDCard into the phone..
Take a deep breath..
Boot the phone to the bootloader: hold Volume Down. Press the power button. Release both buttons when you are inside the bootloader.
When you are in the bootloader, press power once to enter fastboot mode.
The restoration process should will now start. Confirm on the screen when it's asked. Then wait patiently, it takes a long time!
Nice detail: there is a small sidebar at the top right side of the screen that will show you progress. Sometimes it will go back to 0; it will fill up more than once.
In case of failure
In my case it failed the first time. Probably because a sector on my SDCard was faulty. I found out by verifying the md5sum of the file on the sdcard, it was not the same as the RUU zip on my computer, but it has to be.
To fix it, I copied the RUU zip to the sdcard for the second time, *then* deleted 0PKVIMG.img, and *then* renamed the RUU zip to 0PKVIMG.zip. Then I looked at the md5sum again. Now it was the same as on my computer... and then the restoration worked.
Still need help?
If you have questions, ask and wait patiently. I am not on this page 24/7, no one is. Just don't panic. Don't demand help. Maybe read this stuff again and see if you made a mistake somewhere.
It is logical that you are annoyed if this stuff doesn't go how you want, sure, it is not the easiest thing to do. I have tried to make it easier, but again, if it still fails, just ask your questions and wait patiently. Treat others like how you want to be treated yourself. :angel:
Good luck!
-voidzero.
(reserved)
voidzero said:
(reserved)
Click to expand...
Click to collapse
Exactly what RUU do you need and when i click hboot in the bootloader it fails finding the 0PKVIMG.zip. so idk what to do
Alex-M8 said:
Exactly what RUU do you need and when i click hboot in the bootloader it fails finding the 0PKVIMG.zip. so idk what to do
Click to expand...
Click to collapse
The exact filename of the RUU I used:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Do you see a few green lines that say "searching for 0pkvimg.zip" when you go to hboot? They disappear pretty quickly.
voidzero said:
The exact filename of the RUU I used:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Do you see a few green lines that say "searching for 0pkvimg.zip" when you go to hboot? They disappear pretty quickly.
Click to expand...
Click to collapse
Yeah i saw the green lines but nothing happend after they disappear
Alex-M8 said:
Yeah i saw the green lines but nothing happend after they disappear
Click to expand...
Click to collapse
Is it a fat32 or exfat sdcard? Is the md5sum for 0pkvimg.zip correct? It should be 70eece34781f0b1449f98f03e842f249
voidzero said:
Is it a fat32 or exfat sdcard? Is the md5sum for 0pkvimg.zip correct? It should be 70eece34781f0b1449f98f03e842f249
Click to expand...
Click to collapse
i checked and it is fat32 and i still don't get where the md5sum is located and where i should put it .-.
the md5sum is a long string of characters called a checksum. It scans a file and calculates what number it should get. Other types of checksums are SHA-1, SHA-256, RIPE-MD160 and so on.
MD5 is fairly lightweight so that's why we usually choose md5 for files.
md5sum itself is a program that you can run from the command line. If you use linux, it should be on your computer already, so just do 'md5sum 0pkvimg.zip'. On windows, well, you need md5sum.exe and run that from a command line. But I have not used Windows in so many years that I don't know where to find md5sum.exe. I'm sure you can find it easily... I would google for this, but you can do that too so I'll leave that part up to you.
So: you don't put the md5sum anywhere.. you calculate an md5sum and compare it with the number I gave you previously. Hope this makes sense, keep asking if you need more help.
Hi guys,
Im new to all this I just want to ask for little help here my m8s has unlocked bootloader and modified (unofficial) software (says in bootloader)
Im running 5.0.2 soft ver
Soft number 1.16.401.10
Custom recovery TWRP
Phone is rooted but i need to send it back to htc as its dropping calls randomly within 25secs. All i need is the right ruu so its stock again and says relocked (i know how to relock) official soft and that OTAs would work.
Also do i leave this custom recovery there or before the ruu will i put in the stock one, relock the BL and then the ruu?
Any help is much appreciated.
Sent from my HTC One M8s using XDA Free mobile app
Just relock. The Ruu does the rest! I used 1.11, the exact filename is in my OP. If you have a vendor phone I'm not sure but I think you can still use the same RUU as I have; if not, you will be notified from hboot. Does that answer your question?
Yes thank you.
Sent from my HTC One M8s using XDA Free mobile app
Tried on windows twice then got a blue screen (on the pc) did the 1.11 on my macbook and phone is now back to official and relocked!
I owe you a pint of beer sir. Thank you!
Sent from my HTC One M8s using XDA Free mobile app
Great! Glad to hear.
Cyanogenmod is still in the works. I have finally gotten a preliminary version to boot, so to those of you who are interested, head over to the CyanogenMod 12 on M8s thread...
HTC One M8S: Cyanogenmod 12 Discussion
hi all,
I give up, downloaded three zips from this link:
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
1.03
1.11
1.11 - combined signed
and every time I get error "no image or image wrong....no gift file....loading image 0Pkvidiag.zip - No image! loading 0PKVIDIAG.nbh...no image or wrong image"
...inside the zip file there is no 0PKVIMG.img file so dont realy know what to rename . . .
...yes checked md5 sum and they are OK
...sd card is fat32 (tried copying zip file from two different laptops , no difference)
...Custom recovery TWRP
this is m8s european version which was rooted , fastboot shows now RELOCKED and this images just dont work ,
this phone is giving all sort of issues, no custom roms with updates, SIM_Card error sometimes 10+ times a day causing call disconnections and reboots, cant update to lates htc soft as on custom rom it just dont work.....
what I am doing wrong here? probably something stupid easy :laugh: help please
Thanks in advance !
new-noob said:
what I am doing wrong here? probably something stupid easy :laugh: help please
Click to expand...
Click to collapse
Hiya. Ugh I get how frustrating this can be!! But you're close, so we'll get you sorted out. FYI on saturday and sunday I'm not around much (family comes first ), so replies might take me a while... but we'll figure it out.
You need this exact file:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Copy that to the sdcard and rename it to 0PVKIMG.zip, don't extract it just rename it. The md5sum should be:
Code:
70eece34781f0b1449f98f03e842f249
If that won't work, we need to figure out why. That comes next. :good:
voidzero said:
Hiya. Ugh I get how frustrating this can be!! But you're close, so we'll get you sorted out. FYI on saturday and sunday I'm not around much (family comes first ), so replies might take me a while... but we'll figure it out.
You need this exact file:
Code:
0PKVIM[email protected]50311_15.00_016_F_release_430101_signed.zip
Copy that to the sdcard and rename it to 0PVKIMG.zip, don't extract it just rename it. The md5sum should be:
Code:
70eece34781f0b1449f98f03e842f249
If that won't work, we need to figure out why. That comes next. :good:
Click to expand...
Click to collapse
HI voidzero and thanks for taking the time and replaying!
I ended up installing Android Pandora 1.2 and ...waiting on feedback re: SIM errors, hopeful they are gone with new ROM,
I'll post quick update tomorrow.
Thanks again and enjoy ur weekend !
new-noob said:
HI voidzero and thanks for taking the time and replaying!
I ended up installing Android Pandora 1.2 and ...waiting on feedback re: SIM errors, hopeful they are gone with new ROM,
I'll post quick update tomorrow.
Thanks again and enjoy ur weekend !
Click to expand...
Click to collapse
You should use Cyanogenmod, not Pandora. Pandora is old, is not updated, and contains a very problematic security issue with libstagefright. Use cyanogenmod for your own good!
voidzero said:
You should use Cyanogenmod, not Pandora. Pandora is old, is not updated, and contains a very problematic security issue with libstagefright. Use cyanogenmod for your own good!
Click to expand...
Click to collapse
hey, yeap, pandora gives same SIM card error!
Thanks for advise, I will definitely try Cyanogenmmod, think this is the link : http://forum.xda-developers.com/htc-one-m8/general/htc-m8s-cyanogenmod-t3142668
?
Thank you!
hello.
i need help. my htc m8s is relock, my sd card is format fat 32, md5sum match, but still not recognize when i restart in fastboot.