Database Develop

[Rum Float] First flash ever, a bit nervous

I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-

MeeGz said:
I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-
Click to expand...
Click to collapse
The RUU DOES NOT CONTAIN MY ROM. It is an official tool used by HTC for upgrading and returning to stock.
Android market will keep tabs on purchased apps. It will not keep track of free apps.
You need an sdcard to keep safe.
The RUU is easy to run. Its just an exe. Follow the on-screen prompts.
I don't know what you are trying to restore but it would appear you have your terminology and methods all mixed up.
RUU will get you a stock ics. And it will wipe your apps and settings. It will act like a phone you just pulled out of the box with ics.
In order to run rum float (or any aftermarket rom) you need to unlock your bootloader. Rooting has nothing to do with it. Unlock bl then flash recovery on then flash rom and kernel.
Your steps as you perceive them are slightly off. I don't recommend you do anything to your phone right now.

After you complete the RUU you'd have to go to htc.dev and unlock your bootloader. After you can fastboot flash a recovery and CWM with root. After that's complete you can flash a rom of your choice. I'd get familiar with using fastboot commands in ADB (command prompt). I guess you can use the supertool to root but it isn't necessary really a matter of preference. Check out the superguide. Maybe PG or someone can update it with specific steps if you are using the RUU but the process is the same. It starts with the unlocking the bootloader. Definitely pick up an SD card!

Thanks for the quick replies and the clarification. I think I get it now, I would do the following to get to a rooted custom ICS Rom: Unlock the boot loader, root and run titanium backup to save my apps(using an ad card), run the RUU and get to stock HTC ics, copy ROM to sd card, re-root, download and run CWM, root again and restore apps with titanium backup, enjoy!
The only things that may be a bit off in that process is running the RUU as I don't need that to just flash a custom ROM, assuming said ROM includes the ICS kernel. If did have to use the RUU would I have to re-root to run cwm? Also the actual ROM itself is installed from HBoot, correct?
Sorry if these sound like dumb questions, I'm just new at this. I really appreciate the replies. I'm sure I will pick this up fairly quickly as I have years of linux & OS X command line experience and am well versed with c. It's just kind of information overload on this board as there is such a wealth and variety of info here!
Thanks again,
-MeeGz-

So you can run the ruu.exe even if you are rooted, unlocked bootloader, on att stock? Or do you have have to relock bootloader to proceed with the ruu?
Sent from my HTC PH39100 using XDA

RUU is for stock roms IIRC. If you are rooted and already unlocked I'd use the original method PG and Thecubed created.

back on my computer for a little better explanation.
the RUU or the methods that thecubed and i have laid out will get you the necessary HBOOT/RADIO/etc that you will need to flash a custom ICS rom
either method will get you the same thing....an updated HBOOT and ICS
if you run the bootloader unlock tool from htcdev, YOU WILL LOSE ALL YOUR SETTINGS! it will wipe the device like its brand new......do NOT include this in your dreams of getting backups prior to flashing a custom rom....
please just read through the posts and understand what is going on.
in order for ICS to happen on your vivid you need the new HBOOT, Radio, and various other components that the RUU/PH39IMG contain
there are 3 different roads you can follow to get there, the EASIEST being just run the RUU (WHICH WILL ALSO WIPE SETTINGS!), afterwards, reboot to bootloader, unlock bootloader, reboot to fastboot, fastboot flash the boot.img and the recovery.img of your choice on (limited on boot.img's at the moment, better use the one from the rom), reboot to recovery and flash the rom
the other methods imply you understand somewhat how the process works.
relock bootloader (if unlocked), run PH39IMG install, unlock bootloader, fastboot flash recovery and boot.img, reboot to recovery and flash rom.....
if you wrap your head around HOW it works, its all really simple....so the first step is understanding HOW it works, not blindly following some tutorial or walkthrough.
please try to LEARN and UNDERSTAND what it is you are doing....
PS. you have involved ROOTING too many times in your post...... the rom is already ROOTED, you dont have to ROOT to unlock, flash rom or anything....ROOTING is only applicable INSIDE the booted OPERATING SYSTEM, and has nothing to do with recovery/bootloader

i feel i need to apologize to the board here.
frustrations were not directed at the OP of this thread, just in general....
i have been inundated with PM's and seeing the same barrage of questions for the last few days on the forum....
i can understand everyone's excitement...hell i was excited to get this too.
but you all need to read, and try to take it all in before attempting anything. sometimes those of us that understand whats going on, dont explain in a whole lot of detail, because we take the knowledge for granted, and assume if you are on this site, you are here to learn. it is frustrating to see the same questions pop up on nearly an hourly basis...
all i ask is that you take forth the effort to learn how these tools of ours work and understand that a lot of us working on things like this rely on you guys to assist each other in the process. that leaves us more time to deal with what we need to deal with and try and fix and squash bugs/processes/etc.
in return i apologize if i seem on edge the last couple of days...its because i am. if you can imagine one question multiplied by a hundred.....and having people freaking out about them 'bricking'.....after being warned its possible, but unlikely. i think most of these 'bricks' are salvageable and just require someone that understands how they work.
sorry to seem like an ass, but mainly its because i am an ass, and i have a hard time being nice most of the time.

Thanks pirateghost. I understand how to do the other methods but wanted to use something less complicated with less risk for user error. I read and read everything that is posted on the forums. I try not to ask a question unless I am not understanding what has been posted. Thanks for your patience and understanding.
Sent from my HTC PH39100 using XDA

PG, so im pretty sure i "bricked" it lol. im not upset as it was entirely my fault, just wondering if there is any way to get this mother to turn on? i know that when i plug it into the computer it recognizes it but not as anything i have seen lol..if i can find the correct drivers can this be reversed?

Thanks
Thanks to PG for everything and the instructions. I thought I had bricked my phone, but theCube was able to help me on IRC, which is where I suggest anybody go for real-time assistance.

This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium

Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares
Click to expand...
Click to collapse
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.

Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.

formicae said:
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.
Click to expand...
Click to collapse
I totally 100% agree with you. If you HAVE taken the time to read and are still a bit confused, ask! For me I'm not even a week into this platform and I WILL NOT do anything that I don't entirely understand. The problem with android, if you could even call it a problem, is that there is such a huge variety of handsets and a big variety methods for doing this, that, and the other thing. It basically results in a non-linear process to get from point A to point B. It's imperative to understand the basic proceedures. If you were here since the G1, great, you've been able to.follow things from the start. I've used iOS for years, and I still love it btw.(only jailbroken of course!) I'll probably buy an iPad 3! The software is integrated with the hardware amazingly well, battery life is phenomenal, and ONCE JAILBROKEN, iOS is an excellent platform. Sure the "spec numbers" may not be as high but it boils down to.performance. That has always been great for me, obviously battery life is exceptional on apple devices as well. I'm hoping with a rooted ICS Rom there won't be cpu-time hogging processes and ill be able to adjust other things accordingly to get somewhat better battery life. I really wish each OEM would take the time to optimize the SW that they're using to the HW that they're selling. B/C from what I've seen the "Nexus" devices generally perform extremely well, even.against higher spec'd devices. So far I'm loving Android and my Vivid. I love the freedom that I get even on a non-rooted device! It's an excellent platform. Flexible, dynamic, and personal. Customization is there from the get-go. There are a million different things that one could do, even while staying un-rooted. The only reason that I've waited so long to get on board with android is ibwas waiting for it to grow and mature, if I could have a device that tri-booted Android, iOS, and WebOS I'd be a very happy person. I love using multiple platforms.
PG - I'm sorry if I bothered you, thanks for the great info though!
I think knowledge-wise I'm at a point where I'm not going to brick my phone. Wish me luck!

Pirateghost said:
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.
Click to expand...
Click to collapse
Seriously if that is how you feel do get the f*ck off this site please. The devs in all mobile hacking communities are unpaid and do it for fun. You sir are a prime example of WHY THEY LEAVE!!! IF YOU DON'T KNOW AND HAVE READ, ASK, DON'T BE A ****!!!

Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
REALLY? You want the UNNPAID DEV'S TO REMOVE ALL THREATS?!?!?! FROM WHAT IS BASICALLY OSS AND A FIRMWARE THAT SOMEBODY DL'D? REALLY? These guys take a FW and cook it into a ROM for FREE and just b/c you didn't take the time to understand it you're gonna put it on them? WTF?!?!?!?

i'll make him a deal. next time we get a hold of something like this, i will let him figure out how to get it on his phone....i don't have to share how...

Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You know, its users like you that get Devs frustrated and not want to share the work that they have accomplished. XDA is a site for Devs, its not a WalMart that people can stop by and expect to be spoonfed and be on their merry way. Pirateghost is a very talented Dev who wanted to share something with this community, and instead of saying "thank you" you decide to look a the glass as half empty instead of half full and EXPECT MORE from him?
Reading your post, it tells me that you dont frequent the HTC forums at all, and instead of reading up, you just decided to flash. Just because it didnt go as smoothly as you thought it would is NO REASON to tell a Dev that they needed to do more. That part lays on you.
Next time you decide to tell a Dev that "they need to do more" I think you need to do more reading so it prevents you from having to buy a new phone. If it dosent make sense to you or you dont think theres enough documentation/step-by-step instructions YOU HAVE THE POWER TO SAY NO AND NOT FLASH IT.

Uh, there's a reason every single solitary dev puts a disclaimer on their ROM threads. Their work, if directions are not followed to the letter can turn your device into a +/- 200$ paperweight. I've been lurking around these forums for a hot minute, rarely post ( not an ounce of dev skill being the main reason), and really, when's the last time a dev didn't post at least semi detailed instructions to go along with his/her OP.
@pirateghost- bought a vivid literally 12 hours ago, got home, saw your thread, FOLLOWED THE DIRECTIONS CAREFULLY, and now have ICS on my device. Just wanted to say thanks.
And now for the most epic noob question of all time. Wth is RUU? I'm very familiar with flashing roms, cam, tibu, etc from my days on the sgsII SR forums. So most if not all HTC terminology is new to me.
Sent from my HTC PH39100 using xda premium

[Q] Still able to Root?

Can the Hasoon2000 kit still root the HTC Vivid(4.0.3)? I have found no answer to this as that is why am asking.

At the moment it can't he is working on updating script to work on ics.
Sent from my HTC PH39100 using xda premium

megatronisbeast
Did the toolkit work for you? Ive seen several of your post, and was woundering if it did. Did you have to do anything different other than the instructions?

The toolkit does work, just can't root at the moment.
Sent from my HTC PH39100 using xda premium

megatronisabeast
Would you happen to know about how long it takes to script? I'm just woundering because I hate the new update and would like to root(s-off) and then flash a rom. I liked sense but want vanilla-android. Thanks again for your helpful post. I'm not asking if you know an ETA or anything like that, just from your experience.

playerjunglejosh said:
Would you happen to know about how long it takes to script? I'm just woundering because I hate the new update and would like to root(s-off) and then flash a rom. I liked sense but want vanilla-android. Thanks again for your helpful post. I'm not asking if you know an ETA or anything like that, just from your experience.
Click to expand...
Click to collapse
Really don't know that info, however if you want to get root but don't want to wait there are other ways to do it. Let me know if you are interested and I will post them up. Consider though it will take longer than it would using the toolkit.

megatronisabeast
I'll try pretty much anything. I've rooted several devices, so findind a new way for another one won't hurt. Only thing that I really would like to do is avoid making a gold card, but if you have to do that I think I will wait for the toolkit. Thanks!! Do you know if it's possible to temp root, flash a kernal with cwm, and then flash a rom?

Here is what you need to do to root your phone, etc.
First thing is to download android sdk:
http://developer.android.com/sdk/index.html
It will allow you to send files to your phone from your computer-no s-off so can't flash kernel in recovery only fastboot.
While that is downloading if you haven't already you need to unlock boot loader by going to:
http://htcdev.com/
Don't forget to keep the unlock code so if you need to relock your boot loader.
Next, it sounds like you want to flash a custom rom. If so the best one in my opinion is found here:
http://www.wcxxperia-nce.com/index.php
You have to register to see the vivid section.
Once there you will download the zip file, put a copy on your phone, the other copy unzip and place the boot.img and wcx recovery in the same folder that you have the fast boot file that you downloaded earlier from sdk.
Then you put your phone into hboot mode, plug it in to usb port, make sure on phone screen is says fast boot usb in red.
Then open command prompt in your folder with fast boot by clicking shift and the right mouse button.
Type in these commands:
fastboot flash boot boot.img
fastboot flash recovery wcxrecovery.img
After those steps power down phone, unplug from computer, return to hboot, click on recovery, then flash the zip file that you placed on there earlier.
That's it, you got it root and all.
Also if you do use his rom, restart phone 3 times to settle phone in and cycle battery 3 times to make sure everything is working correctly.
Here is a video if you feel overwhelmed to help guide you brought to you by randong!
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
Hope this has helped you!

You can use wild child's recovery to perm root ics check it site for the video if you need proof
Sent from my HTC PH39100 using xda premium

We just need S-OFF so we can simplify this entire thing by using CWM. It's so much easier being able to flash a scripted .zip package in there than dealing with fast boot.
Sent from my HTC Vivid

slapdaddy said:
We just need S-OFF so we can simplify this entire thing by using CWM. It's so much easier being able to flash a scripted .zip package in there than dealing with fast boot.
Sent from my HTC Vivid
Click to expand...
Click to collapse
True, I just wish I knew how long "scripting" takes. I know the video is very clear, and that I'm very good with technology, however I do think that there is a good chance I might mess up...thus I believe I will wait, but I will do some more research be4 deciding what to do

playerjunglejosh said:
True, I just wish I knew how long "scripting" takes. I know the video is very clear, and that I'm very good with technology, however I do think that there is a good chance I might mess up...thus I believe I will wait, but I will do some more research be4 deciding what to do
Click to expand...
Click to collapse
I've never done it myself but it shouldn't be that difficult. I think I'm just spoiled coming from the Inspire - it was rooted, S-OFF'd, and had a few custom ROMs up the within a couple days of its launch. The level of development for that device was extreme from the very beginning.
Sent from my HTC Vivid

True, I still have an Inspire and the development is still booming. I personally just wish HTC would have made the Vivid as dependable as the Inspire, bc my Vivid has all sorts of problems. Turns off randomly, and each time when it turns back on it says "upgrading android" and then it optimizes the apps for ICS. Most of the time it won't flip my pictures(rotate)<--yes auto rotate is on...but all in all HTC went down in quality with the Vivid. Personally this is why I want to root, that way I don't have to worry with HTC screwing up the update.

it does work but i have found that busybox isnt installed/installed correctly and have had to install it from the market for titanium backup to recognize my root.

A reply to numerous posts...you don't need S-OFF on the Vivid, developers have yet to figure out how to do so. It's rumored some users have received their phones shipped with S-OFF, but to my knowledge it's not because of any modifications.
Follow this thread to accomplish everything Hassons2000 tool is trying to do for the Vivid. I didn't work for me either.
****read the following thread VERY carefully***
http://forum.xda-developers.com/showthread.php?t=1416836.
If you have any questions, feel free to ask me.

?
so at the moment there is no real way to root the vivid with stock ICS and basically everything stock? im kindaconfused

Kurrytacos said:
so at the moment there is no real way to root the vivid with stock ICS and basically everything stock? im kindaconfused
Click to expand...
Click to collapse
The link I provided in my previous post will teach you every thing you need to know. It is definately possible If you get stuck on any particular step or if something doesn't make sense, feel free to ask me to explain.

akafarmer said:
A reply to numerous posts...you don't need S-OFF on the Vivid, developers have yet to figure out how to do so. It's rumored some users have received their phones shipped with S-OFF, but to my knowledge it's not because of any modifications.
Follow this thread to accomplish everything Hassons2000 tool is trying to do for the Vivid. I didn't work for me either.
****read the following thread VERY carefully***
http://forum.xda-developers.com/showthread.php?t=1416836.
If you have any questions, feel free to ask me.
Click to expand...
Click to collapse
Having S-OFF let's you flash a kernel through recovery. It simplifies the flashing process and makes developing ROM packages easier for the user.
Sent from my HTC Vivid

slapdaddy said:
Having S-OFF let's you flash a kernel through recovery. It simplifies the flashing process and makes developing ROM packages easier for the user.
Sent from my HTC Vivid
Click to expand...
Click to collapse
Do you have S-OFF on your Vivid?

akafarmer said:
Do you have S-OFF on your Vivid?
Click to expand...
Click to collapse
I wish I did. I was ready to do testing for those devs working on S-OFF but my Linux skills are relatively non-existent lol.
Sent from my HTC Vivid

[MINI-GUIDE] Roadmap to a Custom ROM!

Roadmap to Custom ROM​
1.Unlock Bootloader from htcdev.com.
2.Flash a multi hboot recovery.
3.Root using the permanent root solution flashed via recovery, found here.
4.Flash S-OFF Hboot from unlimited.io.
5.Flash custom ROM with no problems.
To check your Unlock Token, Flash Recovery and S-OFF you should use the tool provided by me here .

This is the easiest guide to follow.. I'm also using this step to install custom Rom on my SXL before I got One X.. I'm also don't get it.. why people don't use unlimited.io trick.. it easier for me.
BTW.. it good to see a new dev for sxl.. it a good device.. but lack of developer.. wish you good luck with your project.
Sent from my HTC One X using Tapatalk 2

Agreed.
I've flashed on a lot of devices and the SXL guides are all a bit random.
The info is out there but sometimes you need to dig a lot to find it.
And a lot are out of date.
Hope this becomes the go-to guide for everyone and hope to see some dev work happening.
I think its time to move on for me..... getting flash withdrawal.

Prof Peach said:
Agreed.
I've flashed on a lot of devices and the SXL guides are all a bit random.
The info is out there but sometimes you need to dig a lot to find it.
And a lot are out of date.
Hope this becomes the go-to guide for everyone and hope to see some dev work happening.
I think its time to move on for me..... getting flash withdrawal.
Click to expand...
Click to collapse
I'm just getting familiar with the forum and the device (almost 4 days since i bought it).
Soon enough if i have time (back2school), i will try to work on CM9 or CM10, depends, CM9 seems the obvious road to take as some work was previosly made by [vertigo], and some fixes are needed (he said that are kernel related), so i think i will try to fix his CM9 rather than port it again form scratch.
As for CM10, i think the best road to take is to compile AOSP JB from source and edit the kernel so it likes the jelly flavour.
If everything works as intedend, in a couple of months we should see both CM9 and JB/CM10 up and going.
(The worst thing is that i will surely need help, i think i can find around the forum, some testers already enrolled to the call to arms thread, so maybe we can build up a team., i really like this device )

I will say that some of the guides are if you were on a GB rom, and then installing a custom rom wasn't so easy, but since the upgrade to ICS it has become a lot easier, although I had noticed that it is easier to softbrick the phone if you don't flash the chinese boot.img and then chinese rom. Also s-off isn't essential for flashing custom roms...

[vertigo] said:
I will say that some of the guides are if you were on a GB rom, and then installing a custom rom wasn't so easy, but since the upgrade to ICS it has become a lot easier, although I had noticed that it is easier to softbrick the phone if you don't flash the chinese boot.img and then chinese rom. Also s-off isn't essential for flashing custom roms...
Click to expand...
Click to collapse
Well, i'm fairly new to this device, but from what i've learned, the chinsese rom is optional if you have s-off, as s-off let's you to access all the partitions, system and other things you need.
Maybe i'm wrong, that's why i've started this thread, i think this is easier, and softbricking a phone with Android seems almost impossible to me...as i said, to me

Yeah I know the chinese rom is optional, but as I said from my point of view, once I'd flashed the chinese rom, I didn't manage to softbrick the phone where as before when I was trying various ports I managed to softbrick it a few times. Just my opinion and what I'd noticed with my device...
As for s-off mine (although broken) is still s-on and I've never felt the need to make it s-off. Again just my opinion

[vertigo] said:
Yeah I know the chinese rom is optional, but as I said from my point of view, once I'd flashed the chinese rom, I didn't manage to softbrick the phone where as before when I was trying various ports I managed to softbrick it a few times. Just my opinion and what I'd noticed with my device...
As for s-off mine (although broken) is still s-on and I've never felt the need to make it s-off. Again just my opinion
Click to expand...
Click to collapse
Well, i know what youre pointing at, i was just wandering when i first read te forum, why on earth should i install a Chinsese ROM when i will change it anyways for a new ROM...so the boot.img is a different one in the custom one, and other things.
I'm not so expeirenced with S-Off/On, as this is my first HTC phone i have and changed ROM (not too many HTC's in my area), but from what i've read online, S-Off is the best road to take to ensure you don't softbrick your phone, as you have the real "Full Control" over the Device and the ROM parts you can flash, like you, this is my opinion, a begginers opinion

Double Post because reedited thread

Hi Lexmazter,
Thanks for making this guide, it is easy to follow. But I'm stuck at a small point and face below response; -
>>>>>>>>>>>>>>'fastboot' is not recognized as an internal or external command, operable program or batch file.<<<<<<<<<<<<<
Please let me know where did I do wrong? Thanks.
My steps were: -
factory reset
root via DooMLoRD_v4_ROOT
titanium backup worked and restore all apps and settings
unclocked the bootloader from htcdev.
all data gone, no more, like factory reset again
superuser app still exist, didn't root again
booted and rooted as you said
connect PC to phone via USB in charge mode only.
run your tool
doing select 5 Flash HBOOT S-OFF Unprotected (via adb) - choose hg hi both failed - but face above message 3 repeat lines.
reboot to bootloader FASTBOOT, >>>>>USB<<<<< appear
UNLOCK at top also appear
then select 4 Flash Recovery. (via fastboot) - then choose rei reg both failed - but face above message. 1 line.
Hope can teach me, thank you very much in advance.
And I'm sure I didn't do something right before hand.

cx5 said:
Hi Lexmazter,
Thanks for making this guide, it is easy to follow. But I'm stuck at a small point and face below response; -
>>>>>>>>>>>>>>'fastboot' is not recognized as an internal or external command, operable program or batch file.<<<<<<<<<<<<<
Please let me know where did I do wrong? Thanks.
My steps were: -
factory reset
root via DooMLoRD_v4_ROOT
titanium backup worked and restore all apps and settings
unclocked the bootloader from htcdev.
all data gone, no more, like factory reset again
superuser app still exist, didn't root again
booted and rooted as you said
connect PC to phone via USB in charge mode only.
run your tool
doing select 5 Flash HBOOT S-OFF Unprotected (via adb) - choose hg hi both failed - but face above message 3 repeat lines.
reboot to bootloader FASTBOOT, >>>>>USB<<<<< appear
UNLOCK at top also appear
then select 4 Flash Recovery. (via fastboot) - then choose rei reg both failed - but face above message. 1 line.
Hope can teach me, thank you very much in advance.
And I'm sure I didn't do something right before hand.
Click to expand...
Click to collapse
Extract the contents of the archive in C:/ and try again, it is most likely because you are running from a folder that has spaces (" ").

Thanks for replying so quickly, some questions before sleep tonight.
I moved the folder to c:\xmtool and run as administrator as usual. But without connecting the phone, and select 5 flash H boot. The 3 repeat message appear still. Hahah, may be I want to test in theory.
Anyway, reading more more other post and try again this weekend.
Thanks !!!! many of your post and reply has been insightful.

HTC One Bricked?

Ok so I recently rooted my HTC One and I think I might've bricked my phone. I tried out the Renovate ROM (I think it was the latest version) and it didn't work somehow, and my phone was stuck in boot, so I went into recovery, and factory reset but I accidently checked the button for system and then my OS was deleted. To fix that, I adb pushed Insert Coin ROM and flashed that, but when I booted my phone, it started up fine, but then after 10 seconds or so, the phone would just freeze and then reboot. I went back into recovery adb pushed the stock Sprint HTC One ROM and flashed that and the same thing is happening, but this time, when the phone turns on, it just shows a black screen with the notification bar at the top, and I can't use it in any way. It also freezes and reboots after like 10 second.
TL: DR
My Sprint HTC One keeps on freezing then rebooting after ten seconds, no matter what ROM I try.
Thanks in advance.

Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium

HTC_M7 said:
Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I believe I have done the same thing as I am very new to this. Is there a link or something to find this ruu? and doesn't it need to be a certain one?
Like my phone is a Sprint HTC One. I am stuck in a boot loop and no matter what ROM I try it just keeps rebooting? Please any help would be greatly appreciated!

Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904

Khilbron said:
Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!

Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA

O.M.J said:
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA
Click to expand...
Click to collapse
Thank you! would I also need to install the open recovery twrp to gain root access as well?

Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.

Knixson said:
Thank you! would I also need to install the open recovery twrp to gain root access as well?
Click to expand...
Click to collapse
yep...unlock, flash recovery, flash ROM

Rirere said:
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.
Click to expand...
Click to collapse
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS

Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
1) If all you are doing is flashing Roms right now you don't need to s-off.
2) You flash the zip.
and I will second the notion that you should do a lot of reading before you do too much. This is an easy process to screw up if you don't know what you are doing and taking your phone out of commission can be a real pain in the ass.
Good Luck!

Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.

Rirere said:
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.
Click to expand...
Click to collapse
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation

Knixson said:
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation
Click to expand...
Click to collapse
There was a really good one in one of the threads in the development section, but I can't for the life of me remember what ROM had it posted. I'll take another look for it later, but in the meantime I would try reading on XDA's wiki.

Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!

Knixson said:
Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!
Click to expand...
Click to collapse
You can flash over it (which is often called a dirty flash) but you are much better off wiping first. I usually use This tool. Just put it on your sd card and flash it before you flash your new ROM.

I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!

Knixson said:
I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!
Click to expand...
Click to collapse
also do a nandroid before flashing, so you have a fall back

Htc One Stuck In Cwm And Cant Flash A Rom
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....

jake012 said:
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....
Click to expand...
Click to collapse
Check PM

Need to reinstall phone

hey guys, Just trying to get my bearings on where to start. A friend game me a HTC Desire 510 that was not loading for him. Just sticking on the HTC loading screen.
He managed to "unlock" it. Not sure if it has root access.
In anycase it will not loal anymore, stuck on HTC load screen. I followed a few threads and tried to reset/restore things but now it looks like i need to just reinstall the OS.
Where I am lost is where/can i get the stock OS for this phone?
If not , do i need to get root access, load in a bootloader and then load in a custom ROM?
last time I did all this before was 2 years ago on a Samsung so I am a little rusty on the steps.
details
HTC Desire 510 - europe (Irish)
HBOOT - 3.19.0.0000
Radio 01.02.012
When I load up the bootloader I have "Sofrware status: Officaial *** at the tope and UNLOCKED under that.
Cheers

check the htc website for the latest rom(update) also this thread is sprint/virgin/boost
http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521
cricket stock rom: http://forum.xda-developers.com/desire-510/help/stock-rom-cricket-htc-desire-510-t3161697
id see if the htc site works first but thats just me.
hope i was of help to you with your issues if not wait for more experanced members to assist.

roymcd said:
hey guys, Just trying to get my bearings on where to start. A friend game me a HTC Desire 510 that was not loading for him. Just sticking on the HTC loading screen.
He managed to "unlock" it. Not sure if it has root access.
In anycase it will not loal anymore, stuck on HTC load screen. I followed a few threads and tried to reset/restore things but now it looks like i need to just reinstall the OS.
Where I am lost is where/can i get the stock OS for this phone?
If not , do i need to get root access, load in a bootloader and then load in a custom ROM?
last time I did all this before was 2 years ago on a Samsung so I am a little rusty on the steps.
details
HTC Desire 510 - europe (Irish)
HBOOT - 3.19.0.0000
Radio 01.02.012
When I load up the bootloader I have "Sofrware status: Officaial *** at the tope and UNLOCKED under that.
Cheers
Click to expand...
Click to collapse
Are you in Europe? If you are that's most likely a 64 bit phone and you'll need Philz Touch Recovery unless you have one installed. You'll also need to find a 64 bit stock HTC desire 510 rom.. It should work after installing them.
Edit: The HTC websites rom updater will not work since the phones boot is unlocked.. Just try what I said above.

Yes I am in Europe.
Will give what suggested a go and let you know..
cheers

here is your man for the job
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button

bcbradley12 said:
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
Click to expand...
Click to collapse
It's actually fastboot oem lock

bcbradley12 said:
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
Click to expand...
Click to collapse
MrMike2182 said:
Are you in Europe? If you are that's most likely a 64 bit phone and you'll need Philz Touch Recovery unless you have one installed. You'll also need to find a 64 bit stock HTC desire 510 rom.. It should work after installing them.
Edit: The HTC websites rom updater will not work since the phones boot is unlocked.. Just try what I said above.
Click to expand...
Click to collapse
Ok guys , getting around to trying this now but running into some small problems.
Question 1
I have installed adb.exe and it does work with my main phone (HTC m8) but when i plug in the broken phone it does not pick up that phone (when i do a ">adb.exe devices") I saw some comments saying that I need to enable debug mode but how can I do that when i cannot even load the phone up ?
Question 2
I would like to install this Philz Touch Recovery , so i can installed the new RUU but I see on some sites that I need to install ClockworkMod first. Now I am not sure if this is needed or not but i still have the problem of being unable to install it from the bootloader screen. There is no option to install from zip? So this might sound like a real n00b question but how can install anything to my phone when all i have it the bootloader screen. My options when i boot up are . . .
Fastboot
-->HBOOT
-->RAMDUMP
-->REBOOT
-->REBOOT fastboot
-->power down
recovery
factory reset
simlock
check smartSD
image CRC show barcode.
Review. . .
I would think my issue is with the broken phones connecting to my laptop and the use of adb.exe. If I could get that working i can use adb.exe to installl clockworkmod and from that I can boot up the phone and install Philz Touch Recovery, and then using phils installer I can install the original 64bit Rom and be in business?
does that seem right?
Cheers

roymcd said:
Ok guys , getting around to trying this now but running into some small problems.
Question 1
I have installed adb.exe and it does work with my main phone (HTC m8) but when i plug in the broken phone it does not pick up that phone (when i do a ">adb.exe devices") I saw some comments saying that I need to enable debug mode but how can I do that when i cannot even load the phone up ?
Question 2
I would like to install this Philz Touch Recovery , so i can installed the new RUU but I see on some sites that I need to install ClockworkMod first. Now I am not sure if this is needed or not but i still have the problem of being unable to install it from the bootloader screen. There is no option to install from zip? So this might sound like a real n00b question but how can install anything to my phone when all i have it the bootloader screen. My options when i boot up are . . .
Fastboot
-->HBOOT
-->RAMDUMP
-->REBOOT
-->REBOOT fastboot
-->power down
recovery
factory reset
simlock
check smartSD
image CRC show barcode.
Review. . .
I would think my issue is with the broken phones connecting to my laptop and the use of adb.exe. If I could get that working i can use adb.exe to installl clockworkmod and from that I can boot up the phone and install Philz Touch Recovery, and then using phils installer I can install the original 64bit Rom and be in business?
does that seem right?
Cheers
Click to expand...
Click to collapse
Never mind if figured it out. .

roymcd said:
Never mind if figured it out. .
Click to expand...
Click to collapse
Nice to see you figured it out!

MrMike2182 said:
Nice to see you figured it out!
Click to expand...
Click to collapse
Well now that you say that. I am having a strange issue. The phone will boot but only when I select "recovery" mode from the bootloader?
I presume what I have done is flashed the wrong image to the wrong section. I think i need to to flash something to boot and not to recovery when I was running the "fastboot flash recovery image.img!"
ideas?

roymcd said:
Well now that you say that. I am having a strange issue. The phone will boot but only when I select "recovery" mode from the bootloader?
I presume what I have done is flashed the wrong image to the wrong section. I think i need to to flash something to boot and not to recovery when I was running the "fastboot flash recovery image.img!"
ideas?
Click to expand...
Click to collapse
I don't get what you're trying to do. If you wanna get back up and running, all you have to do is relock the bootloader and run the RUU... That's it. Your recovery doesn't matter. You don't need a custom recovery for that. Any custom recovery you have will be replaced by the stock one when you run the RUU.
I haven't been on this forum much lately, (so please correct me if I'm wrong, somebody) but from what I remember, the only custom recovery available for the 64-bit variant 510 is Philz. If that's the case then you shouldn't be flashing CWM

Surj138 said:
I don't get what you're trying to do. If you wanna get back up and running, all you have to do is relock the bootloader and run the RUU... That's it. Your recovery doesn't matter. You don't need a custom recovery for that. Any custom recovery you have will be replaced by the stock one when you run the RUU.
I haven't been on this forum much lately, (so please correct me if I'm wrong, somebody) but from what I remember, the only custom recovery available for the 64-bit variant 510 is Philz. If that's the case then you shouldn't be flashing CWM
Click to expand...
Click to collapse
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.

roymcd said:
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
Click to expand...
Click to collapse
I did say you needed philz touch recovery if you have a 64 bit phone and you never really answered the 64 bit question and I asked because you said you are in Europe (Irish) and if you do have a 64 bit phone then you do need philz if you want to use other roms like the rest (most) of us on here do.

MrMike2182 said:
I did say you needed philz touch recovery if you have a 64 bit phone and you never really answered the 64 bit question and I asked because you said you are in Europe (Irish) and if you do have a 64 bit phone then you do need philz if you want to use other roms like the rest (most) of us on here do.
Click to expand...
Click to collapse
Yeah it was a 64bit phone.
I wanted the original OS back on the phone so that is why i did not need phils tool.

roymcd said:
Yeah it was a 64bit phone.
I wanted the original OS back on the phone so that is why i did not need phils tool.
Click to expand...
Click to collapse
I kinda figured all that out on my own already but why do you just want stock? Why don't you want a rooted phone so you can do a lot more with it?
---------- Post added at 05:46 AM ---------- Previous post was at 05:28 AM ----------
roymcd said:
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
Click to expand...
Click to collapse
I've read through this entire thread more than 3 times and I never once seen anyone in this thread tell you to run CWM(ClockWorkMod).. or to even use that so where did get that idea from... The only thing I suggested was Philz Touch Recovery as did @Surj138 for a good reason cause it's the only one that's 64 bit for your phone!

MrMike2182 said:
I kinda figured all that out on my own already but why do you just want stock? Why don't you want a rooted phone so you can do a lot more with it?
---------- Post added at 05:46 AM ---------- Previous post was at 05:28 AM ----------
I've read through this entire thread more than 3 times and I never once seen anyone in this thread tell you to run CWM(ClockWorkMod).. or to even use that so where did get that idea from... The only thing I suggested was Philz Touch Recovery as did @Surj138 for a good reason cause it's the only one that's 64 bit for your phone!
Click to expand...
Click to collapse
It was from other threads that I read to install Phils recovery I would need install CWM but I think now that is for other phones. I said it was in this thread by mistake.
As for going for the original ROM as opposed to a custom ROM my reasoning is three fold. . . .
1. This phone will not be staying with me. Will be giving it back to my friend who is giving it to his daughter. She is would have no use for a root phone.
2. The last time I was using custom ROM was with my Samsung S2 about 3 years ago. I did like all the extra features, free apps and full customization that you can do with it but I did find that no matter what custom ROM I found there would be little problems with each one. Performance would slowly drop the more i switched around the custom ROMS.
3. Custom ROMs are great and all but we cannot be 100% sure there is not hidden male-ware in some of them that is robbing my data. It was going to be a spare phone for playing games then i would not mind but to give to someone as there main phone is not the best option.

roymcd said:
It was from other threads that I read to install Phils recovery I would need install CWM but I think now that is for other phones. I said it was in this thread by mistake.
As for going for the original ROM as opposed to a custom ROM my reasoning is three fold. . . .
1. This phone will not be staying with me. Will be giving it back to my friend who is giving it to his daughter. She is would have no use for a root phone.
2. The last time I was using custom ROM was with my Samsung S2 about 3 years ago. I did like all the extra features, free apps and full customization that you can do with it but I did find that no matter what custom ROM I found there would be little problems with each one. Performance would slowly drop the more i switched around the custom ROMS.
3. Custom ROMs are great and all but we cannot be 100% sure there is not hidden male-ware in some of them that is robbing my data. It was going to be a spare phone for playing games then i would not mind but to give to someone as there main phone is not the best option.
Click to expand...
Click to collapse
Understood sir!!