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

[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.

[SOLVED] Understanding Custom ROMS, Kernels and Nandroid backups

Hey everyone,
Like every HTC One M7 International (Mexican?? :crying: ) owner, I'm having some trouble getting S-OFF on my device. While SunShine is a good result, I don't feel like paying 25$ for something I can do with a bit extra work, but for free.
So I got myself thinking out loud: if I were to preform a nandroid backup, install custom ROM and kernels, get S-OFF using FireWater and live happily ever after... will I be still able to return to my original stock ROM and kernel simply by restoring a nandroid backup?

ArmyMan007 said:
Hey everyone,
Like every HTC One M7 International (Mexican?? :crying: ) owner, I'm having some trouble getting S-OFF on my device. While SunShine is a good result, I don't feel like paying 25$ for something I can do with a bit extra work, but for free.
So I got myself thinking out loud: if I were to preform a nandroid backup, install custom ROM and kernels, get S-OFF using FireWater and live happily ever after... will I be still able to return to my original stock ROM and kernel simply by restoring a nandroid backup?
Click to expand...
Click to collapse
You'll still show s-off in Bootloader.
Sent from my One using Tapatalk

ArmyMan007 said:
Hey everyone,
Like every HTC One M7 International (Mexican?? :crying: ) owner, I'm having some trouble getting S-OFF on my device. While SunShine is a good result, I don't feel like paying 25$ for something I can do with a bit extra work, but for free.
So I got myself thinking out loud: if I were to preform a nandroid backup, install custom ROM and kernels, get S-OFF using FireWater and live happily ever after... will I be still able to return to my original stock ROM and kernel simply by restoring a nandroid backup?
Click to expand...
Click to collapse
Short answer is yes. But, you need to know that unlocking bootloader will wipe your phone memory clean and also some default apps will be erased too
Powered by non removable 2300 mAh battery

I already have an unlocked bootloader and the phone is rooted. So, just to be sure: will a nandroid backup be sufficient to return to stock ROM and kernel?

ArmyMan007 said:
I already have an unlocked bootloader and the phone is rooted. So, just to be sure: will a nandroid backup be sufficient to return to stock ROM and kernel?
Click to expand...
Click to collapse
Yes it would. As ghostryder12 mentioned, you'll still be S-Off when you restore the backup but yes you'll be back on stock ROM and kernel.

KidCarter93 said:
Yes it would. As ghostryder12 mentioned, you'll still be S-Off when you restore the backup but yes you'll be back on stock ROM and kernel.
Click to expand...
Click to collapse
Hurry for nandroid backups! ^_^
One final question: is there any tutorial on how to install custom ROMs and kernels as well as preform a nandroid restore?
And what kind of custom ROM and kernel would I need in order to help me get S-OFF?

ArmyMan007 said:
Hurry for nandroid backups! ^_^
One final question: is there any tutorial on how to install custom ROMs and kernels as well as preform a nandroid restore?
And what kind of custom ROM and kernel would I need in order to help me get S-OFF?
Click to expand...
Click to collapse
Instructions for flashing a ROM/kernel are usually in the first post of the ROM/kernel thread. As long as you do what it says, you shouldn't have any issues.
The exact instructions for performing a nandroid are gonna be slightly different depending on which custom recovery you choose to use. Once you've decided which you want to use (it doesn't really matter, as they all work, but I prefer to use TWRP), I'd suggest checking YouTube for a tutorial on how to do it.
Also, it doesn't matter what ROM and kernel you're using when trying to S-Off, as it's a completely separate process. I'd suggest doing a bit of reading around this forum before heading into it as doing something wrong could easily brick your device (especially when dealing with S-Off).

KidCarter93 said:
Instructions for flashing a ROM/kernel are usually in the first post of the ROM/kernel thread. As long as you do what it says, you shouldn't have any issues.
The exact instructions for performing a nandroid are gonna be slightly different depending on which custom recovery you choose to use. Once you've decided which you want to use (it doesn't really matter, as they all work, but I prefer to use TWRP), I'd suggest checking YouTube for a tutorial on how to do it.
Also, it doesn't matter what ROM and kernel you're using when trying to S-Off, as it's a completely separate process. I'd suggest doing a bit of reading around this forum before heading into it as doing something wrong could easily brick your device (especially when dealing with S-Off).
Click to expand...
Click to collapse
Will do. Thanks a bunch!

As @KidCarter93 explained, each Dev has instructions for installation. Also, some devs also prefer one recovery over another. I've used both over the past and like KidCarter93, prefer TWRP because it's very easy to understand and get it to do what I want with little thought.
Always, always make a nandroid backup and always read thru instructions several times before delving into s-off. Some methods are confusing to my feeble brain.
Since there's more than one method, find the one that's the easiest to follow. But like I said, read thru them several times to understand what you have to do and what's going to happen at each step. Nothing worse than your phone doing something that you weren't expecting and panicking for nothing. Not good for your heart.
Sent from my One using Tapatalk

I need help 5.03.651.3

I NEED HELP WITH THIS http://forum.xda-developers.com/showthread.php?t=2795856
how my phone is now
HTC one m7 rooted S-off unloacked
Hboot 1.55
4.4.2
4.06.651.9
openrecovery-twrp-2.8.0.2-m7wls
I did everything in the video
using Fast boot with the Modified Firmware everything went ok with no problems
I did not even get the "please flush image again immediately" thing
after booting back into the phone I find out that nothing has changed what so ever
& I know what to look for because my mom has the same phone all up to date but with out root & s-off etc...
I want this update real bad so I can turn off blinkfeed & you can only do that on Sense 5.5 or higher.
Well the place where you go to turn it off is not there :crying:
I'm no noob but I don't do this kind of updating everyday
so what am I doing wrong????

Are you trying to use that RUU?
If so you will need to flash the full firmware first then the RUU.

Now my phone is fubar!!!!!!
I was trying 5.03.651.3_modified_firmware_RUU.zip when I did it
the full what??
be descriptive
and to make matters worst I have ****ed up the OS.
I got sick of w8ing for help so I tried doing the full 5.03.651.3_firmware_RUU.zip
it will no longer boot into the OS
all I got now is Hboot & twrp This is bull **** there has got to be easier ways then this
So now what do I do????????????????????????????
The good news I'm now on Hboot 1.57

I know it's frustrating but easy with the swear words.
Run the RUU and you should be good.

I need help!!!!!!
ok dude I'm not trying to be an ass H
I'm just realy realy realy Fing mad
so if you are not going to give me step by step instructions
then your not going to be much help to me
I'm no pro at this
so to recap my HTC one is fubar & all I got is Hboot 1.57 & twrp-2.8.0.2-m7wls
I went into twrp & did a wipe on sys in the hope that would fix
so I did the wipe & went back to Hboot & flash boot the 5.03.651.3_modified_firmware_RUU.zip & now when I boot into the OS
all I get the white HTC screen & nothing more

is there anyone who is going to help me?????

Well looks like it a brick now
nothing I do is fixing this
not 5.03.651.3_modified_firmware_RUU.zip
not 5.03.651.3_firmware_RUU.zip
and I tried rolling back to the old one modified_firmware_4.06.651.9.zip
no matter what I do all I get the white HTC screen & nothing more :crying:
looks like I will have to go to sprint tomorrow :crying::crying::crying::crying::crying::crying::crying:

Flash Full Firmware
Run RUU

OMG!!!!!!!!!!!!!!!!!
OMG! dude you are killing me "give me step by step instructions"
what is Run RUU??????????
I am not a pro at this I don't do this everyday!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

E-TARD_The_LifeCaster said:
OMG! dude you are killing me "give me step by step instructions"
what is Run RUU??????????
I am not a pro at this I don't do this everyday!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
-Download Sprint_HTC_One_m7wls_5.03.651.3_RUU.zip
-extract zip to a folder on your pc
-boot into bootloader (various ways)
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader (S-ON ONLY)
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock

OK I'm downloading that now
OK I'm downloading that now, its big so will take 19 min to D/L
but why do I need that one?
why can't I use the 5.03.651.3_modified_firmware_RUU.zip?
just so I know for next time...

E-TARD_The_LifeCaster said:
OK I'm downloading that now, its big so will take 19 min to D/L
but why do I need that one?
why can't I use the 5.03.651.3_modified_firmware_RUU.zip?
just so I know for next time...
Click to expand...
Click to collapse
You need to RUU because you wiped your OS in twrp.
The modified firmware does not include hboot/recovery/boot.img(kernel)
The reason you don't have an OS is you wiped it in twrp.
Build number/Software won't change unless you flash a 5.03.651.3 rom.
The best way to check if it worked is to check the baseband to see if it changed.

ok its working again
ok its working again
I did not know that was the file I needed, I thought that's a stock rom so why would I want that
so I went for the other files.
This RUU app is new to me.
Thank you for helping me I just feel the way this http://forum.xda-developers.com/showthread.php?t=2795856 post was typed up did not help me at all (I was lost)
Be descriptive people! make life easy for everyone

No No-Thanks Meter? Damn!
Just checking in/out. Just sold my m7wls for 182$ on ebay.
Trying to figure out if the colorfly i108w 4g will work on any US dataservice...?
Thanks Cyanogen!!! and thanks to all the helpful people who make this forum a pleasure.
Please lock this thread.:good:

BD619 said:
You need to RUU because you wiped your OS in twrp.
The modified firmware does not include hboot/recovery/boot.img(kernel)
The reason you don't have an OS is you wiped it in twrp.
Build number/Software won't change unless you flash a 5.03.651.3 rom.
The best way to check if it worked is to check the baseband to see if it changed.
Click to expand...
Click to collapse
@BD619 your a saint with the patience of a monk...you help people all day long that can find the answers by simply searching but they are at least grateful for your help... But then you go a step further and help people like this.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2

all fixed
JoeNeckbone said:
@BD619 your a saint with the patience of a monk...you help people all day long that can find the answers by simply searching but they are at least grateful for your help... But then you go a step further and help people like this.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2
Click to expand...
Click to collapse
no the OS was Fed up before I did that sys wipe .
I only did the sys wipe because I thought that would help fix it what the modified firmware Fed up by removing the bad OS & retry installing the modified firmware.
before that I did the modified firmware & it soo did not work!!!!!
so I don't know what happened but I do know that post with the update was really vague for someone who does not do this kind of thing often.
I do have a?
& that is next time I do this
will it keep the app-data? or is there away to back that up
my phone is fine but I lost all app-data witch is kind of a pain in the but having to go over all the settings for all of my apps

JoeNeckbone said:
@BD619 your a saint with the patience of a monk...you help people all day long that can find the answers by simply searching but they are at least grateful for your help... But then you go a step further and help people like this.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2
Click to expand...
Click to collapse
yes, I agree.BD is a good man.

E-TARD_The_LifeCaster said:
no the OS was Fed up before I did that sys wipe .
I only did the sys wipe because I thought that would help fix it what the modified firmware Fed up by removing the bad OS & retry installing the modified firmware.
before that I did the modified firmware & it soo did not work!!!!!
so I don't know what happened but I do know that post with the update was really vague for someone who does not do this kind of thing often.
I do have a?
& that is next time I do this
will it keep the app-data? or is there away to back that up
my phone is fine but I lost all app-data witch is kind of a pain in the but having to go over all the settings for all of my apps
Click to expand...
Click to collapse
Use titanium backup next time. It will save game progress, app settings etc.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2

JoeNeckbone said:
@BD619 your a saint with the patience of a monk...you help people all day long that can find the answers by simply searching but they are at least grateful for your help... But then you go a step further and help people like this.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2
Click to expand...
Click to collapse
+1 for BD FTW
perfect example of why not everyone should be rooting their phones.

[Q] RUU

Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx

Linkalex1 said:
Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx
Click to expand...
Click to collapse
Still no RUU's avaiable as HTC wont release them. your best option is to use TWRP backup and restore.
Original stock backup

Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?

Linkalex1 said:
Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?
Click to expand...
Click to collapse
You need to send it as it is to your phone and use TWRP > restore. choose file and done.

Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?

Linkalex1 said:
Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?
Click to expand...
Click to collapse
Yes OTA updates should work just fine. just look for updates in settings>about >software update.
you may have one for polaris office.

Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)

arm1e said:
Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)
Click to expand...
Click to collapse
Stock Recovery
To unroot just lock bootloader:
fastboot oem lock