Original RUU - Verizon HTC One (M7)

Does anyone have a copy of the original stock encrypted ruu as an executable for windows. I can find the decrypted version but not the original.

no one has it is allowed to post it?
sucks though wish we had it.

Well that's lame. Thanks for the info. I'll see if I can recrypt the decrypted version with ruuveal. I would like to have a safety net before rooting if possible.

Gizmoe said:
Well that's lame. Thanks for the info. I'll see if I can recrypt the decrypted version with ruuveal. I would like to have a safety net before rooting if possible.
Click to expand...
Click to collapse
A re-encrypted RUU will do you no more good then the decrypted one, in my opinion.
You have to be S-Off to flash it either way, since it won't be signed with HTC's signatures.
Just trying to save you some time, since it won't be any more useful then the decrypted one already posted.
Again, if someone else has more or different info regarding this, I'm all ears!

santod040 said:
A re-encrypted RUU will do you no more good then the decrypted one, in my opinion.
You have to be S-Off to flash it either way, since it won't be signed with HTC's signatures.
Just trying to save you some time, since it won't be any more useful then the decrypted one already posted.
Click to expand...
Click to collapse
Ahh. Good to know. I've never recrypted an ruu before because in the past they were always readily available. I'm new to the whole encrypted ruu thing. I'll just have to accept that once I go s off I'll not be able to restore to stock and s on if I need to.

I think it might still signed, just decrypted.
Decryption doesn't mess with the signature if I remember correctly.

Is their any harm in trying out an ruuveal'ed recrypted RUU on S-ON phone?
Would it just not flash if not working, or is it possible it would flash but not work correctly?
If there is no harm, why not have someone use the tool and upload the RUU for someone with S-ON willing to try.
If it's not allowed to be posted, just use PM.
Although I am S-OFF, I am interested in this, and would love to have a stock working RUU.

Yeah I imagine the worst would be just an unsuccessful attempt. I think I'll try and recrypt it just to see what happens. That's if I'm able to re encrypt it. Hopefully HTC doesn't nuke my device for trying :-o

From what I've been told, it won't even flash in it's original encrypted form.
It fails on installing /system.
That's just what I have been told.
If that is the case, I doubt it's gonna get anyone very far.
But of course anyone is welcome to try. That's why it was posted I assume.
I don't see how decrypting and re-encrypting it doesn't break the signature though.
But that's cool if that's the case, when and if there is a complete ruu to work with.

santod040 said:
From what I've been told, it won't even flash in it's original encrypted form.
It fails on installing /system.
That's just what I have been told.
If that is the case, I doubt it's gonna get anyone very far.
But of course anyone is welcome to try. That's why it was posted I assume.
I don't see how decrypting and re-encrypting it doesn't break the signature though.
But that's cool if that's the case, when and if there is a complete ruu to work with.
Click to expand...
Click to collapse
I thought a new one was uploaded and works fine for those of us that are S-OFF?

andybones said:
I thought a new one was uploaded and works fine for those of us that are S-OFF?
Click to expand...
Click to collapse
Looks like it was possibly flashed successfully by one user.
So that may very well be the case. :good:

santod040 said:
Looks like it was possibly flashed successfully by one user.
So that may very well be the case. :good:
Click to expand...
Click to collapse
Hopefully someone with S-OFF will try for us soon to confirm., 100%

Related

Tester needed

Anyone brave enough to test an hboot that removed the development test on boot?
Requirements:
S-Off
fastboot knowledge
Brave soul
Click to expand...
Click to collapse
Before flash
Durring flash
After flash
Video of boot
Files:
will be sent a link on pm
Commands to run:
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hboot_nonag.zip
fastboot reboot-bootloader
I'm not s-off, but what does this do?
crazyg0od33 said:
I'm not s-off, but what does this do?
Click to expand...
Click to collapse
When you're S-Off there's a little warning message that pops up on the splash screen on bootup, I'm guessing this gets rid of that. I am definitely not brave enough to try it, but it'd be cool if someone could confirm it worked.
PapaSmurf6768 said:
When you're S-Off there's a little warning message that pops up on the splash screen on bootup, I'm guessing this gets rid of that. I am definitely not brave enough to try it, but it'd be cool if someone could confirm it worked.
Click to expand...
Click to collapse
Exactly that. If we wanted to we could add a custom message to it as well.
why not try and make a plug in for this?
http://forum.xda-developers.com/showthread.php?t=1786498
unless it's been confirmed to not work on newer HTC devices?
It was a lot of fun playing with it on the HTC Inc4G LTE
unfortunately I don't know how to make the plug-in or I'd make one and try it when my phone comes back from Sonic.
andybones said:
why not try and make a plug in for this?
http://forum.xda-developers.com/showthread.php?t=1786498
unless it's been confirmed to not work on newer HTC devices?
It was a lot of fun playing with it on the HTC Inc4G LTE
unfortunately I don't know how to make the plug-in or I'd make one and try it when my phone comes back from Sonic.
Click to expand...
Click to collapse
I used it on my Sprint HTC One, but I think it was only for hboot 1.44
sofla2 said:
I used it on my Sprint HTC One, but I think it was only for hboot 1.44
Click to expand...
Click to collapse
it has to be made for that specific phone and hboot.
otherwise you're asking for a brick
actually anytime you flash hboot you're risking a brick..
but we'd need someone to edit our current hbot and make a patch for this phone and this hboot.
andybones said:
it has to be made for that specific phone and hboot.
otherwise you're asking for a brick
actually anytime you flash hboot you're risking a brick..
but we'd need someone to edit our current hbot and make a patch for this phone and this hboot.
Click to expand...
Click to collapse
Agreed any time you flash hboot you want to pray to your god that there's no power outages, the laptop battery will last, no one will trip on any cord between the computer and phone, cross your fingers and hold your breath. This one was pulled from my phone and modified so it is 1.54 for vzw.
-- Edit --
It is also noted if for any reason you s-on with a custom hboot you brick.
jmstumme said:
Agreed any time you flash hboot you want to pray to your god that there's no power outages, the laptop battery will last, no one will trip on any cord between the computer and phone, cross your fingers and hold your breath. This one was pulled from my phone and modified so it is 1.54 for vzw.
-- Edit --
It is also noted if for any reason you s-on with a custom hboot you brick.
Click to expand...
Click to collapse
always ruu before you s-on for warranty purposes, most people do not need a custom bootloader unless it is part of an exploit
Updated with screenshots and videos
123421342 said:
always ruu before you s-on for warranty purposes, most people do not need a custom bootloader unless it is part of an exploit
Click to expand...
Click to collapse
So it works then?
PapaSmurf6768 said:
So it works then?
Click to expand...
Click to collapse
Works for me, I would like some testers before general. Release thought.
Sent from my HTC6500LVW using Tapatalk 2
PapaSmurf6768 said:
So it works then?
Click to expand...
Click to collapse
I don't know how that relates to my comment. I was just letting people know there is no reason to flash a bootloader because of the HUGE risk of hard, hard brick and no benefits unless you are a hacker/developer. I am not unlocked but I would not try this anyway, no offense. What benefits does this carry? According to your pictures, this removed s-off and also locked the bootloader. Unless this removes all of those checks, it is stupid because we have no way to unlock.
123421342 said:
I don't know how that relates to my comment. I was just letting people know there is no reason to flash a bootloader because of the HUGE risk of hard, hard brick and no benefits unless you are a hacker/developer. I am not unlocked but I would not try this anyway, no offense. What benefits does this carry? According to your pictures, this removed s-off and also locked the bootloader. Unless this removes all of those checks, it is stupid because we have no way to unlock.
Click to expand...
Click to collapse
Misquote, sorry. Meant to quote OP's post.
123421342 said:
I don't know how that relates to my comment. I was just letting people know there is no reason to flash a bootloader because of the HUGE risk of hard, hard brick and no benefits unless you are a hacker/developer. I am not unlocked but I would not try this anyway, no offense. What benefits does this carry? According to your pictures, this removed s-off and also locked the bootloader. Unless this removes all of those checks, it is stupid because we have no way to unlock.
Click to expand...
Click to collapse
If you look closely there are a few extra spaces in those lines. Basically it makes it look like its s-on and locked. I've found that it's easier to walk into a verizon store and get help when they dont think you've unlocked. It also removed the nag string on the boot splash when you flash a custom rom. I've been using something like this on my rezound for over a year and from the ppl in that forum there was a want for it. Yes hboot is a very dangerous part if you don't know what your flashing. If it makes anyone feel better they can do a binary compare of this hboot with an original hboot and see that only the strings were manipulated.
Basically it was something I wanted so I did it for this phone. If others want to use it that is fine too, I just don't want to release something that could potentially brick based off of my mistakes, but it's been working fine for me for over a day.
jmstumme said:
If you look closely there are a few extra spaces in those lines. Basically it makes it look like its s-on and locked. I've found that it's easier to walk into a verizon store and get help when they dont think you've unlocked. It also removed the nag string on the boot splash when you flash a custom rom. I've been using something like this on my rezound for over a year and from the ppl in that forum there was a want for it. Yes hboot is a very dangerous part if you don't know what your flashing. If it makes anyone feel better they can do a binary compare of this hboot with an original hboot and see that only the strings were manipulated.
Basically it was something I wanted so I did it for this phone. If others want to use it that is fine too, I just don't want to release something that could potentially brick based off of my mistakes, but it's been working fine for me for over a day.
Click to expand...
Click to collapse
Sounds good, thanks for this. I won't flash it now because I don't need to risk it but if I ever need to bring the phone to Verizon then I'll keep this in mind.
jmstumme said:
If you look closely there are a few extra spaces in those lines. Basically it makes it look like its s-on and locked. I've found that it's easier to walk into a verizon store and get help when they dont think you've unlocked. It also removed the nag string on the boot splash when you flash a custom rom. I've been using something like this on my rezound for over a year and from the ppl in that forum there was a want for it. Yes hboot is a very dangerous part if you don't know what your flashing. If it makes anyone feel better they can do a binary compare of this hboot with an original hboot and see that only the strings were manipulated.
Basically it was something I wanted so I did it for this phone. If others want to use it that is fine too, I just don't want to release something that could potentially brick based off of my mistakes, but it's been working fine for me for over a day.
Click to expand...
Click to collapse
Oh okay this is a good idea but risky. May be good for people sending it in but it can't fool command line right?
Sent from my HTC6500LVW using xda app-developers app
123421342 said:
Oh okay this is a good idea but risky. May be good for people sending it in but it can't fool command line right?
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
From what I seen in the rest of the hboot no, it looks like it's obvious that its custom, s-off, and unlocked. This should also not be used for insurance fraud in any form or fashion. This is more or less to get people to not freak out and for people that like the stock look. As far as risk goes, having an s-off phone is dangerous since you can access the raw devices.
Looks nice!
jmstumme said:
From what I seen in the rest of the hboot no, it looks like it's obvious that its custom, s-off, and unlocked. This should also not be used for insurance fraud in any form or fashion. This is more or less to get people to not freak out and for people that like the stock look. As far as risk goes, having an s-off phone is dangerous since you can access the raw devices.
Click to expand...
Click to collapse
---------- Post added at 03:06 PM ---------- Previous post was at 02:52 PM ----------
Is there an RUU for our phones that, when flashed, would bring us right back to factory untouched condition?
jmstumme said:
This should also not be used for insurance fraud in any form or fashion.
Click to expand...
Click to collapse
godhamba said:
Looks nice!
---------- Post added at 03:06 PM ---------- Previous post was at 02:52 PM ----------
Is there an RUU for our phones that, when flashed, would bring us right back to factory untouched condition?
Click to expand...
Click to collapse
Looks like this one should work
http://forum.xda-developers.com/showthread.php?t=2437436
Otherwise I still have the original hboot from my phone

Need help restore to stock

The guy that was using this phone said he hit factory reset, When i got the phone, it was in bootloop. I couldn't get in TWRP so i re-flashed that via hboot and was able to get into TWRP, but if I wipe Data, the phone resets. So basically since all roms wipe data pertty much,m I cant flash a custom rom. I can get into TWRP/Hboot but not much else. Anyone have any ideas how I can get this back to stock, it was HTC Dev unlocked at one point. But now I dont know whats going on with it. Its going to another user so i dont care if if all gets wiped, i just need a working phone.
oh I also was going to fastboot flash an encrypted RUU from another thread in her, but it says i need to fastboot oem rebootRUU, when i do that though, the phone reboots, then goes into its usual reboot routine
please help!
krayzee said:
The guy that was using this phone said he hit factory reset, When i got the phone, it was in bootloop. I couldn't get in TWRP so i re-flashed that via hboot and was able to get into TWRP, but if I wipe Data, the phone resets. So basically since all roms wipe data pertty much,m I cant flash a custom rom. I can get into TWRP/Hboot but not much else. Anyone have any ideas how I can get this back to stock, it was HTC Dev unlocked at one point. But now I dont know whats going on with it. Its going to another user so i dont care if if all gets wiped, i just need a working phone.
oh I also was going to fastboot flash an encrypted RUU from another thread in her, but it says i need to fastboot oem rebootRUU, when i do that though, the phone reboots, then goes into its usual reboot routine
please help!
Click to expand...
Click to collapse
I'd send to Sonic see if he can just S-OFF it for you. He may not be able to but I have no idea. That would be my first thought to do.
Other than than, since you are S-ON, you cannot flash the provided RUU, figure out a way to use that ruuveal tool.
If I knew how I'd be uploading it for you by now.
andybones said:
I'd send to Sonic see if he can just S-OFF it for you. He may not be able to but I have no idea. That would be my first thought to do.
Other than than, since you are S-ON, you cannot flash the provided RUU, figure out a way to use that ruuveal tool.
If I knew how I'd be uploading it for you by now.
Click to expand...
Click to collapse
If I'm not mistaken and I don't think I am....
That RUU will not do anyone that is still S-on any good.
In order to flash an RUU while S-on, it must be signed using HTCs signature.
So while it wasnt that difficult to encrypt it, its fairly useless for most people right now.
So I see no need to upload it at this point and cause any further confusion.
Sent from my HTC6435LVW using Tapatalk 4
santod040 said:
If I'm not mistaken and I don't think I am....
That RUU will not do anyone that is still S-on any good.
In order to flash an RUU while S-on, it must be signed using HTCs signature.
So while it wasnt that difficult to encrypt it, its fairly useless for most people right now.
So I see no need to upload it at this point and cause any further confusion.
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
My apologies.
It was to my understanding that you could use the "ruuveal" tool mentioned in the OP of that thread to encrypt the file and it would work for S-ON users. Not really sure why he'd say to use the tool and that it would work.. if it wouldn't.
Just my impression, again sorry if I am wrong.
andybones said:
My apologies.
It was to my understanding that you could use the "ruuveal" tool mentioned in the OP of that thread to encrypt the file and it would work for S-ON users. Not really sure why he'd say to use the tool and that it would work.. if it wouldn't.
Just my impression, again sorry if I am wrong.
Click to expand...
Click to collapse
No worries...I didn't understand why the OP states that either to be honest.
I was gonna mention it in his thread sooner but since the decrypted one wasn't even up yet when I thought about it, I figured it didn't matter much.
But yeah, as far as I know, it wouldn't work while s-on.
Sent from my HTC6435LVW using Tapatalk 4
santod040 said:
No worries...I didn't understand why the OP states that either to be honest.
I was gonna mention it in his thread sooner but since the decrypted one wasn't even up yet when I thought about it, I figured it didn't matter much.
But yeah, as far as I know, it wouldn't work while s-on.
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
did someone flash a gsm rom on it per chance? if thats the case,its not dead,but you will need to wait for a signed ruu. or send it to sonic so he can s-off it,and then you can run the unsinged one

Other person's nandroid?

I have found a nandroid backup that is compatible with my device. Do I flash the .zip like a custom ROM? I tried extracting the folder to TWRP/BACKUPS/*number*/ but when I go to recovery and restore, it will not see the folder. What do I do?
Sent from my HTC One_M8 using XDA Free mobile app
TWRP expects the nandroid to be in a specific folder and the one you got probably has the incorrect device ID.
Go into TWRP > backup and make a nandroid only of your recovery.
Then go to /sdcard/TWRP/Backup and inside you should see another folder named with your phones device ID.
Open it and delete the contents.
Then copy the contents of the nandroid you want to restore into that folder.
When you go back to TWRP > Restore, it now should find the nandroid - IF that nandroid was made in a compatible TWRP version. If it was made in CWM you would have to use that recovery.
Kinda risky what you are trying to do unless you know exactly how that nandroid was created.
Better to flash a RUU, IMHO.
You say it's risky? Would this possibly brick my phone? I don't care if it won't boot up or soft bricked after this but do you recommend doing this or not?
Sent from my HTC One_M8 using XDA Free mobile app
I don't know....
Do you trust the source of the nandroid?
Do you know what exactly the person was running at the time?
Do you know with which recovery and version thereof it was created and if that is compatible with your recovery?
I wouldn't do it. Flash a RUU if you want to go back to stock.
a nandroid won't brick your device ! And there are no sense ruu files ... at least no carrier branded ones. And when you download the nand and check the recovery.log you can read all info.
You think i keep a thread up that will brick devices ?
Restoring a nandroid to get back to stock is very safe !
Mr Hofs said:
Dude a nandroid won't brick your device ! And there are no sense ruu files ...
Click to expand...
Click to collapse
Errr, I have the RUU for the AT&T M8... I used it to restore one of my M8's to stock. When I upgraded it to the VIper 2.0 rom, the dual camera kept giving me a blocked warning. So I found the RUU for the phone and restored it to 4.4.2 Stock rom. But since I own 2 M8's I had one set up the way I like, so I just transfered the file to the second M8 and restore it to the phone. Worked like a charm. Funny how I have 2 M8's, had them both on Viper 2.1.0. One gives the dual camera warning, one doesn't. So I restore the one with the warning to stock, and the warning disappeared..
Yeah but what about people with a s-on device and a specific carrier..
Where are those ruu files ? There aren't any.....there is a very small selection of ruu files that can help a small group of people ! That's my point here. And who said he has a AT&T ..... Check my thread and check all the cid and main numbers then give me the links to the ruu files that are compatible with the nands i am hosting there.....get my point ?
Mr Hofs said:
a nandroid won't brick your device ! And there are no sense ruu files ... at least no carrier branded ones. And when you download the nand and check the recovery.log you can read all info.
You think i keep a thread up that will brick devices ?
Restoring a nandroid to get back to stock is very safe !
Click to expand...
Click to collapse
Hey mate! No reason to get offended! I did not mean to question your integrity or something and much less to insult you. I did not and still do not have any idea where the OP got the nandroid from! He never referenced it! Could have been from a friend's phone created with who knows what! Could have been from God knows what shady website...
That's why I asked him: Do you trust the source?
How am I to know it's you?
Ah well i am not offended. But i don't think a nand will likely brick the phone as it doesn't flash a firmware or such....it's actually only software so it's pretty harmless and easy to recover from
Mr Hofs said:
Ah well i am not offended. But i don't think a nand will likely brick the phone as it doesn't flash a firmware or such....it's actually only software so it's pretty harmless and easy to recover from
Click to expand...
Click to collapse
I never said that, OP asked that!
But I'm glad we're square :good:
Mr Hofs said:
Yeah but what about people with a s-on device and a specific carrier..
Where are those ruu files ? There aren't any.....there is a very small selection of ruu files that can help a small group of people ! That's my point here. And who said he has a AT&T ..... Check my thread and check all the cid and main numbers then give me the links to the ruu files that are compatible with the nands i am hosting there.....get my point ?
Click to expand...
Click to collapse
I am sorry for getting you mad, but I don't lie. The RUU file is here on XDA, like all the wise guys say
"Do a search"
I did, I downloaded it and installed in on my M8. ONly carrier I found was for AT&T, the OP didn't say
berndblb said:
I wouldn't do it. Flash a RUU if you want to go back to stock.
Click to expand...
Click to collapse
You did. So I was letting him know there was a RUU for AT&T on XDA. He didn't mention what carrier he was with. Since that was the only RUU I found for the M8, I suggested it.
Most of the rest of you stuff makes no sense.
Mr Hofs said:
Where are those ruu files ? There aren't any....
Click to expand...
Click to collapse
Wait, didn't you just tell him to:
berndblb said:
Flash a RUU if you want to go back to stock.
Click to expand...
Click to collapse
HUH You tell him to flash one in one breath, then state there is none in another. But IF he is on AT&T, I know there is one. I am not going to search for you, but if I run across it, I will drop a link maybe later.
---------- Post added at 05:57 AM ---------- Previous post was at 05:10 AM ----------
http://forum.xda-developers.com/showthread.php?t=2757462
Sent from my AT&T HTC One M8, running the ViperOne M8 ROM via Tapatalk.
Ugh....this is exactly why i want to stop posting on xda and withdraw from it completely. The main problem is that people flash things without knowing what it is....afterwards its "it didn't work" what now ? You can link a ruu and many people just execute it.
I'm not mad, i am misinterpreted.....i am making a point that's all.
Thanks and cheers. I will stop responding as it's the second time i believe you make me go off topic.
But flashing a nandroid backup that it's origins are unknown is like you said, unwise and could cause more problems than what it is worth. But not fatal, that I agree with. I also agree that sometimes posting here can lead to a whole lot of confusion, specially for beginners in flashing roms. Good thing about this is that this is one more area they can visit to get a link to return to stock before they return the phone for repair. So it wasn't all in vain. Sit, drink a beer (or coffee) relax and try to have a nice day.
Sent from my AT&T HTC One M8, running the ViperOne M8 ROM via Tapatalk.
Mr Hofs said:
Where are those ruu files ? There aren't any.....there is a very small selection of ruu files that can help a small group of people ! That's my point here. And who said he has a AT&T ..... Check my thread and check all the cid and main numbers then give me the links to the ruu files that are compatible with the nands i am hosting there.....get my point ?
Click to expand...
Click to collapse
If that was your point, its not what you wrote:
Mr Hofs said:
And there are no sense ruu files ... at least no carrier branded ones.
Click to expand...
Click to collapse
HTC posted the RUU for AT&T quite some time ago: http://www.htc.com/us/support/htc-one-m8-att/news/
Folks here keep saying "there are no RUUs", "HTC doesn't release RUUs anymore" and its simply not correct to make these statements as being generalized for all versions and all instances; although it seems to be true for a great many versions. If anything, this device is missing a good index of OTAs, RUUs, etc. by CID.
Not trying to pick a fight or anything, just want to prevent any misinformation.
redpoint73 said:
If that was your point, its not what you wrote:
HTC posted the RUU for AT&T quite some time ago: http://www.htc.com/us/support/htc-one-m8-att/news/
Folks here keep saying "there are no RUUs", "HTC doesn't release RUUs anymore" and its simply not correct to make these statements as being generalized for all versions and all instances; although it seems to be true for a great many versions. If anything, this device is missing a good index of OTAs, RUUs, etc. by CID.
Not trying to pick a fight or anything, just want to prevent any misinformation.
Click to expand...
Click to collapse
I haven't visited this thread in a while because my problem was resolved but i had a question. I want to accept an OTA. I'm fairly sure I know how to do this (I have a stock NAND, recovery, and i know i have to relock my bootloader) this will update my firmware to 2.22.xx.x After this is done i can re unlock my bootloader right? Also would i be able to restore one of my TWRP backups or will restoring replace my firmware with the old one that i had when the backup was made?
Restoring a full backup after an ota will replace your OS so that's not an option because you don't want to go back to your old (before ota) situation it will not replace the firmware. Only restore data ! And no need to relock the bootloader for an ota.....totally unnecessary !
redpoint73 said:
If that was your point, its not what you wrote:
HTC posted the RUU for AT&T quite some time ago: http://www.htc.com/us/support/htc-one-m8-att/news/
Folks here keep saying "there are no RUUs", "HTC doesn't release RUUs anymore" and its simply not correct to make these statements as being generalized for all versions and all instances; although it seems to be true for a great many versions. If anything, this device is missing a good index of OTAs, RUUs, etc. by CID.
Not trying to pick a fight or anything, just want to prevent any misinformation.
Click to expand...
Click to collapse
Mr Hofs said:
Restoring a full backup after an ota will replace your OS so that's not an option because you don't want to go back to your old (before ota) situation it will not replace the firmware. Only restore data ! And no need to relock the bootloader for an ota.....totally unnecessary !
Click to expand...
Click to collapse
Thanks for the reply! So bootloader can stay unlocked? In all the threads I checked you have to be relocked by doing "fastboot oem lock" but ok I'll take your word for it! Also you say that restoring isn't good so I'll have to stick with reflashing ROMs from scratch?
I think we are mixing things up. If you are already running the latest based roms why would you update ?
Why would you update to the 2.22 or higher base and then go back to a 1.54 based rom ?
Mr Hofs said:
I think we are mixing things up. If you are already running the latest based roms why would you update ?
Why would you update to the 2.22 or higher base and then go back to a 1.54 based rom ?
Click to expand...
Click to collapse
lol I'm just glad to see that your name is also Bernd :good:
Seems like you're a "troll" with 2 different IDs on here :angel: some of these guys didn't just misquote you, but completely misidentified you! :silly:
BerndM14 said:
lol I'm just glad to see that your name is also Bernd :good:
Seems like you're a "troll" with 2 different IDs on here :angel: some of these guys didn't just misquote you, but completely misidentified you! :silly:
Click to expand...
Click to collapse
Haha yeah i didnt even respond to that quote error. Not worth the hassle mate

Rooted, ROM'd, and wondering!

I've just finished rooting and installed a custom ROM on my device, but now I'm looking into S-Off. My question is, how?
I did this ROM: http://forum.xda-developers.com/showthread.php?t=2706391
and now I don't have Wi-Fi, which apparently means that my firmware needs to be updated.
How, exactly, does one do that when you're no longer on the service provider it was on?
I'm on T-Mobile now, it was on AT&T. The phone is an AT&T HTC One M8.
I've got the files for Firewater, but I'm not 100% sure how to go about it, other than following tutorials I've found. Anyway, if someone could assist me in this search, it would be greatly appreciated.
Chances are firewater is not going to work, you'll need to use Sunshine S-off (pay 25$), S-off jas nothing to do with carrier
Sunshine: http://theroot.ninja
Firewater instructions: http://firewater-soff.com/instructions/
If I try Firewater, is there a chance to royally mess up my work? I.E. brick me, or will it error out beforehand?
firewater does NOT work. and will never work again. You can own the files but they won't work as it has has to establish a connection to the s-off server which is offline. sunshine is the one and only way. you can read that in the s-off thread here on xda and on their website !
and also questions belong in the Q&A section so please use that board the next time instead of the general subforum.
good luck with sunshine
Fubukiyo said:
I've just finished rooting and installed a custom ROM on my device, but now I'm looking into S-Off. My question is, how?
I did this ROM: http://forum.xda-developers.com/showthread.php?t=2706391
and now I don't have Wi-Fi, which apparently means that my firmware needs to be updated.
How, exactly, does one do that when you're no longer on the service provider it was on?
I'm on T-Mobile now, it was on AT&T. The phone is an AT&T HTC One M8.
I've got the files for Firewater, but I'm not 100% sure how to go about it, other than following tutorials I've found. Anyway, if someone could assist me in this search, it would be greatly appreciated.
Click to expand...
Click to collapse
Theirs a AT&T RUU here >>link removed by request
that will let you flash some roms here, not all
You'll have to relock your bootloader to flash it - fastboot oem lock -
and when your finished updateing unlock the bootloader and flash TWRP and root
Mr Hofs said:
firewater does NOT work. and will never work again. You can own the files but they won't work as it has has to establish a connection to the s-off server which is offline. sunshine is the one and only way. you can read that in the s-off thread here on xda and on their website !
and also questions belong in the Q&A section so please use that board the next time instead of the general subforum.
good luck with sunshine
Click to expand...
Click to collapse
Ah, see, this is the info that I couldn't find at all. I had no idea it was server-related, so it wouldn't work. I thought all the files were local, that's why I was investigating. Well, as long as Sunshine will work and not mess anything up, I guess that's what I'm going to have to do. Even though there's another ROM on my phone, I should still be able to use Sunshine and get the firmware updated without any issues, yeah? I would just like to get confirmation from someone who knows my exact situation and not search the forums to a situation "Similar" to mine and eff up my phone.
Fubukiyo said:
Ah, see, this is the info that I couldn't find at all. I had no idea it was server-related, so it wouldn't work. I thought all the files were local, that's why I was investigating. Well, as long as Sunshine will work and not mess anything up, I guess that's what I'm going to have to do. Even though there's another ROM on my phone, I should still be able to use Sunshine and get the firmware updated without any issues, yeah? I would just like to get confirmation from someone who knows my exact situation and not search the forums to a situation "Similar" to mine and eff up my phone.
Click to expand...
Click to collapse
S-OFF means do as you like, change firmwares, convert to GPE and back to sense. S-OFF is freedom
Okay, here's where I'm at, if anyone would inform me in the direction I should take...
I've unlocked the bootloader, flashed a ROM, and rooted. Wi-Fi doesn't work because I need the newer firmware on the device.
In order to get the newer firmware, I need to have S-Off. I don't. Sunshine doesn't work because the ROM I have flashed is a 5.0.1 version.
http://forum.xda-developers.com/showthread.php?t=2706391 If it helps.
Can I go digging to find a KitKat-based ROM and see if Sunshine will work then, or do I need to go through the BS to flash stock everything on my phone and THEN run Sunshine? I'd really like some advice before I royally mess something up.
Thanks in advance!
Edit: I found this and it looks like something that might work. Flash InsertCoin, download and pay for Sunshine, S-Off, flash firmware, go back to SkyDragon?
http://htc-one.wonderhowto.com/how-...-one-m8-install-custom-firmware-mods-0154461/
You simple need the stockest rom you find.. Best is restore your backup ..make it root and than do s off.. Or flash the rooted stock of mike s thread not arhd ..
Alex-V said:
You simple need the stockest rom you find.. Best is restore your backup ..make it root and than do s off.. Or flash the rooted stock of mike s thread not arhd ..
Click to expand...
Click to collapse
Forgive me for asking, but I've searched... Where is this rooted stock one you're talking about?
All right, I've flashed back to as stock as I can find, but it's still not allowing Sunshine to be installed.
However, I've stumbled upon something saying that if the Recovery is fastboot booted, it acts as though the device is S-Off? If I run the recovery in such a manner, could I possibly flash a new Firmware on there like that?
Fubukiyo said:
Forgive me for asking, but I've searched... Where is this rooted stock one you're talking about?
All right, I've flashed back to as stock as I can find, but it's still not allowing Sunshine to be installed.
However, I've stumbled upon something saying that if the Recovery is fastboot booted, it acts as though the device is S-Off? If I run the recovery in such a manner, could I possibly flash a new Firmware on there like that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2694994
I did it with that one..
Okay, here's an update:
I flashed that ROM you showed me, Alex, and then used Sunshine to S-Off my M8. That worked. I paid for it, all is well.
Flashed the Viper ROM, but didn't have Wi-Fi. So, I went back to SkyDragon, same thing.
I flashed firmware 4.28.401.9 (I think. I did typed that from memory..) but I still have no Wi-Fi.
I'm going to try to flash the GPE firmware now. I'll edit once I get it up and running!
Thanks so much guys! I really appreciate your help!
Fubukiyo said:
Okay, here's an update:
I flashed that ROM you showed me, Alex, and then used Sunshine to S-Off my M8. That worked. I paid for it, all is well.
Flashed the Viper ROM, but didn't have Wi-Fi. So, I went back to SkyDragon, same thing.
I flashed firmware 4.28.401.9 (I think. I did typed that from memory..) but I still have no Wi-Fi.
I'm going to try to flash the GPE firmware now. I'll edit once I get it up and running!
Thanks so much guys! I really appreciate your help!
Click to expand...
Click to collapse
If your wifi isn't working with ViperOne, then the firmware didn't flash correctly. Go to your bootloader/hboot and check the readout there. What it says under OS is your firmware version. If it is blank it is because of your recovery. TWRP 2.8.0.3 is recommended. You can also tell by the hboot number. 3.19 = 4.4.4 firmware
xunholyx said:
If your wifi isn't working with ViperOne, then the firmware didn't flash correctly. Go to your bootloader/hboot and check the readout there. What it says under OS is your firmware version. If it is blank it is because of your recovery. TWRP 2.8.0.3 is the recommended recovery to use with ViperOne. You can also tell by the hboot number. 3.19 = 4.4.4 firmware
Click to expand...
Click to collapse
That's awesome to know. I literally just flashed the GPE firmware, and I think I partitioned properly. (no errors while installing) It's currently doing the first boot.
Flashing that GPE firmware was nerve-racking. It went sooo slow. Here's hoping it goes through! UPDATES TO COME! I'm excited.
UPDATE:
HOLY HNNNNNNNNNNNNNG IT WORKED.
Good LORD I CAN FINALLY DOWNLOAD MY UPDATES.
Please excuse the caps, I'm effing excited right now. THANKS SO MUCH EVERYONE.
Nice that you have it working.. Don't forget.. If you want to go back to sense you need the sense firmware.. As the partitions are a bit different.. Btw I'm very happy ? with gpe 5
Alex-V said:
Nice that you have it working.. Don't forget.. If you want to go back to sense you need the sense firmware.. As the partitions are a bit different.. Btw I'm very happy ? with gpe 5
Click to expand...
Click to collapse
Right at this point, I don't care to go back to Sense firmware. I'm spoiled by the bright look of SkyDragon, so this is where I'm staying!

[Q] I'm screaming for help with my M9

Ok so real quick….I'm not tech savvy. I usually get the new HTC One, watch a youtube tutorial, and install ViperROM. This time around I get to the finish line and I keep getting the same "set_perm failed" …..I tried twrp hima 2.8.6.4 …still the same problem. I'm ready to give up. Please help me
We need more details.. Is your phone s-off? Also did you flash the correct firmware? And is your bootloader unlocked.
Sent from my HTC One M9 using XDA Free mobile app
NjEcTi0N said:
Ok so real quick….I'm not tech savvy. I usually get the new HTC One, watch a youtube tutorial, and install ViperROM. This time around I get to the finish line and I keep getting the same "set_perm failed" …..I tried twrp hima 2.8.6.4 …still the same problem. I'm ready to give up. Please help me
Click to expand...
Click to collapse
What exactly is "the finish line"? Like @bigp951 said, we need more details. Please list everything you've done to this point and exactly what you're doing that returns that error.
I'm no expert but the process i used was.
- Get phone, Unlock bootloader via htcdev, (hadnt realise the sunshine apk does both unlocking bootloader and s-off at the time >< doh!), then s-off using sunshine, flash custom recovery via fastboot, flash superSU and install superSU apk for root, flash 1.40.401.x firmware with fastboot, flash viper rom (i had to do this twice as the first time an error came up which was helpfully listed in the troubleshooting section of the dev's post for viper, boom, it was all done. Backed up for safety
hope that helps you get to the source of the error.
when you say you flashed supersu and then installed supersu apk, what does that mean? I ask because when you flash the beta-superSu it installs the apk for you. But then again you had to be rooted to get s-off (someone correct me if I am wrong). Also, did you check the md5 before you tried to flash? Did you file a ticket with team viper? What was the error that showed up on the first failed attempt? Did you post on the viperonem9 thread and ask them for help? what is your cid and mid? supercid may help... and what is the current state of the phone? Is it still working?? Can you go into recovery? Still lots of questions.
If you want a clean slate to start over with find the CORRECT RUU and run it. Then you will be stock all over again (disclaimer--Find the RUU thread and follow instructions completely).
Obviously I am no expert either. I just run through the troubleshooting list when problems arise. But I try to help or point you in the direction of someone who can.
EDIT- there is also a newer official version of twrp for the m9. As @jollywhitefoot asked, you did not state what the finish line is nor what you were doing to return the error. If you installed the rom and made a backup than it sounds like the phone was working...
bigp951 said:
when you say you flashed supersu and then installed supersu apk, what does that mean? I ask because when you flash the beta-superSu it installs the apk for you. But then again you had to be rooted to get s-off (someone correct me if I am wrong). Also, did you check the md5 before you tried to flash? Did you file a ticket with team viper? What was the error that showed up on the first failed attempt? Did you post on the viperonem9 thread and ask them for help? what is your cid and mid? supercid may help... and what is the current state of the phone? Is it still working?? Can you go into recovery? Still lots of questions.
If you want a clean slate to start over with find the CORRECT RUU and run it. Then you will be stock all over again (disclaimer--Find the RUU thread and follow instructions completely).
Obviously I am no expert either. I just run through the troubleshooting list when problems arise. But I try to help or point you in the direction of someone who can.
EDIT- there is also a newer official version of twrp for the m9. As @jollywhitefoot asked, you did not state what the finish line is nor what you were doing to return the error. If you installed the rom and made a backup than it sounds like the phone was working...
Click to expand...
Click to collapse
Seems like this was a waste of time drive by. For someone "screaming for help" you would think they would reply when someone tries to help them.
maybe he's asleep...lol
jollywhitefoot said:
Seems like this was a waste of time drive by. For someone "screaming for help" you would think they would reply when someone tries to help them.
Click to expand...
Click to collapse
yeah, I know what you mean they ask a question and disappear for 2 days LOL
or he's thrown the phone under a bus and hates us all!!!! >< either way, there is a lot of helpful tips and tricks to be found in these forums. I think as mentioned above a good idea may be to try to return fully to stock and start again.... carefully following each step to the letter.
tomorio said:
or he's thrown the phone under a bus and hates us all!!!!
Click to expand...
Click to collapse
Is that an "uh-oh" moment? lol gotta love that uh-oh protection
bigp951 said:
Is that an "uh-oh" moment? lol gotta love that uh-oh protection
Click to expand...
Click to collapse
RIP OP

Categories

Resources