About hboot - Droid Eris Android Development

Okay so im willing to bet that this has already been covered but im new here.
What if, in theory, it was possible to create a higher hboot version than 1.49 and put it into a ROM. Would it require signing? and would that even be possible?
I tried putting the v3 leak hboot file into the OTA update.zip and it failed the verification test.
But any ideas?

You answered your own question, it wont pass verification.

Okay..
but would it be possible to create a higher version than 1.49 and put it into a file?

I'm guessing no (i dont know for sure) but as far as I know the devs tried everything they could think of and I remember them talking about replacing hboot but it failing.
I sadly dont see root at the end of the tunnel for leakers.

Yeah i figured they probably tried something like that already. oh well, maybe that exploit will pull through

It is not possible for us to replace/update the HBOOT version because we could not resign the file for it to pass verification.

Is there another device with a higher hboot version than our own that has been rooted? If so could we install that hboot on our device
-------------------------------------
Sent via the XDA Tapatalk App

ahjee said:
Is there another device with a higher hboot version than our own that has been rooted? If so could we install that hboot on our device
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
This doesn't work that way.
It would have to be a signed image, for the eris, with an engineering bootloader.
or
A root exploit.

Makes sense, im still new to all this. I more or less lurk and wait to enjoy fruits of your labor. I Should just keep quiet like i have Nd let you ill developers work your magic.
Excited in this exploit though, i read about it but am not savvy enough to contribute, good luck to those working on it and much appreciated no matter the turn out
-------------------------------------
Sent via the XDA Tapatalk App

No need to stay quiet. Asking questions is how you learn and who knows...you may just spit something out that noone else has really thought of...

Good to see a positive vibe.

So how are these packages signed.....any chance of signiong up to be a developer with google and maybe being able to sign them ourselves?

ssgtob1 said:
So how are these packages signed.....any chance of signiong up to be a developer with google and maybe being able to sign them ourselves?
Click to expand...
Click to collapse
They are signed using RSA and an SHA1 hash to ensure validity. So we can sign up to be a developer but that doesn't get us either of HTC's keys.

Related

HBOOT Driver Installation

I am trying to get to the drivers installed and I am doing what the instructions say, "Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.", but all it does is boot normal, but really fast. Am I doing something wrong, other than being a noob?
I am not rooted
htc EVO 4g
v2.3.3 ota
you need to pull out the battery first. or disable fastboot in the settings.
civicboy1791 said:
I am trying to get to the drivers installed and I am doing what the instructions say, "Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.", but all it does is boot normal, but really fast. Am I doing something wrong, other than being a noob?
I am not rooted
htc EVO 4g
v2.3.3 ota
Click to expand...
Click to collapse
Yea, you have fastboot mode enabled, which you can turn off in menu>settings>power management, or something to that nature. What exactly are you trying to install the hboot drivers for? I only ask, because if it is so you can use Unrevoked, I just wanted to give you a heads up that it won't be working for you, and I'd avoid trying it. Unrevoked won't work for the 2.3.3 OTA. If it is for other reasons, then carry on!
k2buckley said:
Yea, you have fastboot mode enabled, which you can turn off in menu>settings>power management, or something to that nature. What exactly are you trying to install the hboot drivers for? I only ask, because if it is so you can use Unrevoked, I just wanted to give you a heads up that it won't be working for you, and I'd avoid trying it. Unrevoked won't work for the 2.3.3 OTA. If it is for other reasons, then carry on!
Click to expand...
Click to collapse
Well I was trying to get one step ahead by getting ready to root when Unrevoked gets it figured out. On their site it says to install the drivers for windows users. I guess it is safe to say I am completely wrong about this one?
civicboy1791 said:
Well I was trying to get one step ahead by getting ready to root when Unrevoked gets it figured out. On their site it says to install the drivers for windows users. I guess it is safe to say I am completely wrong about this one?
Click to expand...
Click to collapse
Well, you DO need to have the hboot drivers installed for Unrevoked to work, if you're using windows. The problem is that Unrevoked is not yet updated to work with the 2.3.3 OTA. There is currently no root method for ya. The only hope you'd have for right now, is if your phone had been rooted prior to you having it, and your bootloader is still S-off. Other than that, you're going to need to wait until unrevoked gets updated to work with the OTA. I also wouldn't be surprised if when there is an Updated method to work with the new hboot 2.16, that there is a different set of modified hboot drivers that will need to be used (speculation, but wouldn't be surprised). That would mean you'd just need to install them again.
I would just sit tight and wait for the updated Unrevoked to drop, and see if there is anything that changes with their instructions or downloads.
k2buckley said:
Well, you DO need to have the hboot drivers installed for Unrevoked to work, if you're using windows. The problem is that Unrevoked is not yet updated to work with the 2.3.3 OTA. There is currently no root method for ya. The only hope you'd have for right now, is if your phone had been rooted prior to you having it, and your bootloader is still S-off. Other than that, you're going to need to wait until unrevoked gets updated to work with the OTA. I also wouldn't be surprised if when there is an Updated method to work with the new hboot 2.16, that there is a different set of modified hboot drivers that will need to be used (speculation, but wouldn't be surprised). That would mean you'd just need to install them again.
I would just sit tight and wait for the updated Unrevoked to drop, and see if there is anything that changes with their instructions or downloads.
Click to expand...
Click to collapse
Looks like I am sitting tight... Thank you for all the input!
civicboy1791 said:
Looks like I am sitting tight... Thank you for all the input!
Click to expand...
Click to collapse
You're welcome. I always feel bad for the owner of an unrooted evo, hopefully you won't need to wait too long! If I were you, I'd probably be looking all over craigslist, hoping to get lucky and find one that's still on Froyo, and try to trade up!
k2buckley said:
You're welcome. I always feel bad for the owner of an unrooted evo, hopefully you won't need to wait too long! If I were you, I'd probably be looking all over craigslist, hoping to get lucky and find one that's still on Froyo, and try to trade up!
Click to expand...
Click to collapse
I was considering doing the root before the ota 2.3.3 but wasn't comfortable with it yet, now i pretty much have the procedure memorized, but somehow missed the part about not doing the ota's. Lesson learned. And i didn't even think about Craigslist, going there now...
civicboy1791 said:
I am trying to get to the drivers installed and I am doing what the instructions say, "Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.", but all it does is boot normal, but really fast. Am I doing something wrong, other than being a noob?
I am not rooted
htc EVO 4g
v2.3.3 ota
Click to expand...
Click to collapse
You have to be rooted first
Sent from my PC36100 using XDA Premium App
fnkyscotty said:
You have to be rooted first
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
como?
The message you have entered is too short. Please lengthen your message to at least 10 characters.
civicboy1791 said:
I was considering doing the root before the ota 2.3.3 but wasn't comfortable with it yet, now i pretty much have the procedure memorized, but somehow missed the part about not doing the ota's. Lesson learned. And i didn't even think about Craigslist, going there now...
Click to expand...
Click to collapse
Also, I have no idea how true it is...but I've heard a couple people report that they had success in going to a Sprint store, and convincing one of the techs there to downgrade the phone back to Froyo. Again, that's just hearsay, but I wouldn't be surprised if Sprint had the capabilities to downgrade the system (we currently can't downgrade). If that is at all true, and you were able to get them to downgrade ya, then you could root using unrevoked.
k2buckley said:
como?
The message you have entered is too short. Please lengthen your message to at least 10 characters.
Click to expand...
Click to collapse
HA! nice lol
k2buckley said:
Also, I have no idea how true it is...but I've heard a couple people report that they had success in going to a Sprint store, and convincing one of the techs there to downgrade the phone back to Froyo. Again, that's just hearsay, but I wouldn't be surprised if Sprint had the capabilities to downgrade the system (we currently can't downgrade). If that is at all true, and you were able to get them to downgrade ya, then you could root using unrevoked.
Click to expand...
Click to collapse
Calling now, let you know what they say
negative - they say it is not possible...
civicboy1791 said:
negative - they say it is not possible...
Click to expand...
Click to collapse
Damn, that's too bad. I wonder if it is actually possible, but they're instructed to not do it....either that or the person who reported it before was full of it! He did say it took some convincing though, and he gave a few reasons as to why he wanted to do it (ie. with the GB OTA netflix didnt work, it borked wireless N wifi, the compass no longer worked, phantom voicemail icons, etc) he complained of all those valid things, and got the guy to do it. At least that's what he said.
k2buckley said:
Damn, that's too bad. I wonder if it is actually possible, but they're instructed to not do it....either that or the person who reported it before was full of it! He did say it took some convincing though, and he gave a few reasons as to why he wanted to do it (ie. with the GB OTA netflix didnt work, it borked wireless N wifi, the compass no longer worked, phantom voicemail icons, etc) he complained of all those valid things, and got the guy to do it. At least that's what he said.
Click to expand...
Click to collapse
Well I just got my netflix working
Sent from my htc EVO

Regarding the leaked Gingerbread update and semi-bricks

Well for people who had a brick caused by VISIONary that was fixed by flashing the leaked Gingerbread update, I think I have an idea that might work on rooting it.
Why not replace the stock bootloader and recoveries that come in the PC10IMG.zip file with Clockworkmod recovery and the Engineering SPL. That way you can have S-OFF, which allows you to use to use Gingerbreak to root and CWM recovery which allows you to flash a different ROM on the G2.
Does this make sense, or did someone already try this and failed? I got the idea from the method I used to root my G1.
teh5abiking said:
Well for people who had a brick caused by VISIONary that was fixed by flashing the leaked Gingerbread update, I think I have an idea that might work on rooting it.
Why not replace the stock bootloader and recoveries with Clockworkmod recovery and the Engineering SPL. That way you can have S-OFF, which allows you to use to use Gingerbreak to root and CWM recovery which allows you to flash a different ROM on the G2.
Does this make sense, or did someone already try this and failed? I got the idea from the method I used to root my G1.
Click to expand...
Click to collapse
Best bet to find out if this would work or not is to ask the guys over at #G2ROOT irc.
And this doesn't really belong in the dev section, should be in Q&A
CRAP!!! I hit the wrong link! Sorry, moving my post.
And where's the link to the #G2ROOT IRC channel?
If I'm not mistaken, there's no way to get thoes items on the phone as the package won't pass signatue validation.
If we had thoes items, then we wouldn't need to root the leak rom, we could simply bypass it by flashing a new pre-rooted rom..
Perhaps you misunderstood how the process works?
Sent from my HTC Vision using XDA Premium App
teh5abiking said:
CRAP!!! I hit the wrong link! Sorry, moving my post.
And where's the link to the #G2ROOT IRC channel?
Click to expand...
Click to collapse
Can't provide a link, just use your preferred IRC client
wilnotdie said:
If I'm not mistaken, there's no way to get thoes items on the phone as the package won't pass signatue validation.
If we had thoes items, then we wouldn't need to root the leak rom, we could simply bypass it by flashing a new pre-rooted rom..
Perhaps you misunderstood how the process works?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
perhaps i have, but what exactly is hindering the problem? did htc patch the hole in the firmware that allowed scotty2 to powercycle the eMMC chip?
Do u know what an md5 sum is? If anything is modified, even ONE BYTE, the sum changes. That is how u know if a file is corrupted/tampered. Signature verification is the same thing different name. The fact that you can't change the recovery because its not rooted means that you cannot bypass the sig verification. End of story. This idea will never work.
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
Do u know what an md5 sum is? If anything is modified, even ONE BYTE, the sum changes. That is how u know if a file is corrupted/tampered. Signature verification is the same thing different name. The fact that you can't change the recovery because its not rooted means that you cannot bypass the sig verification. End of story. This idea will never work.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
ouch. . .
no need to be harsh.
xsteven77x said:
Do u know what an md5 sum is? If anything is modified, even ONE BYTE, the sum changes. That is how u know if a file is corrupted/tampered. Signature verification is the same thing different name. The fact that you can't change the recovery because its not rooted means that you cannot bypass the sig verification. End of story. This idea will never work.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Signature verification is not the "same thing different name" -- look up public key cryptography for more information.
teh5abiking said:
perhaps i have, but what exactly is hindering the problem? did htc patch the hole in the firmware that allowed scotty2 to powercycle the eMMC chip?
Click to expand...
Click to collapse
Pretty much yes. I don't remember the exact details....but it was the hole that allowed temp root, which than allowed us to modify the hboot. Giving us s-off, in turn allowing us full access...I think you get the picture.
Or someone please correct me if I'm wrong. Its been a long time since thoes days
Sent from my HTC Vision using XDA Premium App
You seek Irc.Freenode.net, #G2Root. While you're at it, drop into #Msid and #cyanogenmod ;-)
Sent via Tapatalk on CyanogenMod 7.1.0-RC1 on Vision

[WIP]Temp-root Gingerbread EVOs

my evo is rooted already and i havent paid much atention since i got my 3d but was there an HBOOT update in the GB OTA as compared to the last Froyo 3.70?
If there wasnt, anyone should be able to a simple downgrade with a previous RUU and then use any of the working root methods for froyo.
just a thought i had while being bored.
Nope, new bootloader is locked. Cant downgrade.
EVOlvedAndroid said:
Nope, new bootloader is locked. Cant downgrade.
Click to expand...
Click to collapse
so there was a bootloader update?
I really don't even know what to say anymore. I give up. Someone else can do it.
github said:
I really don't even know what to say anymore. I give up. Someone else can do it.
Click to expand...
Click to collapse
+1 thats all i have to say about that
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.
firket2000 said:
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.
Click to expand...
Click to collapse
yes, but you're not tricking the bootloader. the bootloader remains the same. the sys image is all you are changing and the signatures should remain intact if it is pulled out of a froyo ruu. for that matter even try placing a rooted OTA sys image in it. this would not gain s-off but you could run a shell root and su if it would work.
t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
As far as I understand, the new bootloader won't allow for downgrading or flashing anything that doesn't match HTCs signature....so modifying files is out of the question....
Sent from my PC36100 using XDA App
t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
Can't do that, it would break HTC's signature and the bootloader would not accept it
I need to save this response in a text file so I can just copy and paste it every day.
You can't modify the contents of a RUU provided by HTC on an S-ON HBOOT. The zip is signed by HTC with their private key. The HBOOT has the public key. Changing just 1 bit on the zip will invalidate the private key and HBOOT won't allow it to flash. This is the reason for wanting S-OFF, so you can flash anything via HBOOT (Recovery, for example) without any signature checks.
You also can't downgrade the HBOOT, as it will give you an error about an earlier version.
All the obvious ideas have been tried, over and over again over the past few months since the new update hit.
If you are still confused, please see this article on Wikipedia about Public Key Cryptography.
Don't forget to add that goldcards and battery pull microsd swaps do not work either.
Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.
There's been all types of shenanigans occurring trying to root this thing. Including physically planting in the ground. No root from that either. Appreciate where you're coming from and trying to help and all though
jjones1983 said:
Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.
Click to expand...
Click to collapse
Its being worked on right now so no worries
Sent from my PC36100 using XDA App
I'm rooted but jw is there any news on when that source will be out?
My stupid friends at work wouldn't let me root their froyo and now want to pay me to root their gb I don't even want $ .
Sent from my PC36100 using XDA App

Root you EVO GB with Revolutionary: S-OFF & Recovery Tool 0.4pre1 UPDATED!

Revolutionary 0.4pre is live! Support all GB roms, new devices: Thunderbolt, Evo 4G, MT4GS, Evo 3D GSM! revolutionary.io #Revolutionary http://revolutionary.io/
Common Problems & Questions
Why do you need my serial number?
We use your serial number to generate your unique beta key to use revolutionary.
Why do I need a beta key?
We introduced the beta key mechanism so that if problems/bricks occur we can stop generating beta keys to prevent more people being affected.
I don't want to give you my serial number!
That's fine, stable releases will not require a beta key, however there may be significant time between a beta and the subsequent stable release.
Does Revolutionary give me root?
No. You will need to flash this zipfile from recovery.
What does this do, then?
revolutionary will give you S-OFF either by a patched HBOOT or setting the secureflag to off on the device itself. This behaviour will depending on your particular device. Optionally it will also replace the stock Android recovery with a custom one, which adds many features including “nandroid” backups, the ability to use custom ROMs, and a greater amount of flexibility and customization of your Android phone.
Does this permanently unlock the NAND flash on my phone?
Yes. The default configuration of this tool disables the phone's security, which also disables the NAND locks placed on the storage by the bootloader.
Are any drivers required?
On Linux, the program is self-contained. For Windows users, please install the fastboot drivers available here.
I'm running Linux and it won't detect my device!
Either run the program with root permissions, or add appropriate udev rules to the file /etc/rules.d/51-android.rules. Instructions are available at the Android Developers website.
The program hangs when “waiting for the system to settle.” -OR- the program says “Communications with phone unexpectedly interrupted.”
Uninstall any programs that may connect to the phone over USB and automatically sync. Specifically, we have had interference from HTC Sync and Doubletwist in the past; other programs may also cause trouble. Try reinstalling the drivers, if all else fails (or use Linux, which has a 99% less sucky USB stack).
Titanium Backup says that I'm not rooted, even though I ran Revolutionary and flashed the root zip from recovery.
Install Busybox from the Market to fix this.
Will you release the source code?
At this time, we are not disclosing the vulnerability we have exploited.
That doesn't seem fair! Android is about open source.
In some senses, we agree; but at times, a tradeoff needs to be made. Releasing the source code for this, we believe, would compromise the greater ability to unlock devices like these in the future. Given the choice between sacrificing the liberty of running code on our handsets and the liberty of reading the code by which we unlock it, we feel that the millions of handsets are more important. It is unfortunate that we must make such a choice, and we look forward to the day in the future that no such decision need be made.
Where can I get support?
As an experiment, we'd like to redirect users to our IRC channel for support. If you have an IRC client already, connect to irc.freenode.net, channel #revolutionary – if you don't, then that's OK; you can use Freenode's web IRC client. We'd love to hear from you!
Credits
Revolutionary was brought to you by (in no particular order):
Ryan Pearl
Joshua Wise
Eric Smaxwill
Matthew Fogle
Matt Mastracci
Koush Dutta
Michael Sullivan
Adam Glasgall
Kenny Millington
Sen Verbrugge
The mysterious 0xf4b
Nice.
Not permanent yet though?
mattykinsx said:
Nice.
Not permanent yet though?
Click to expand...
Click to collapse
S off I believe?
Sent from my PC36100 using Tapatalk
RileyGrant said:
S off I believe?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hmm?
I'm just noting that it doesn't list it under the "permanent" phone list.
I'm not at my house computer but when I get back I will be testing this out. My Asurion phone will play guinea pig. I have much faith. ::excited::
2.3.3 4.24 2.16.0001 (>.<)
It works gents. S-Off on my 2.3.3 and now flashing RA.
burtzacarach said:
I'm not at my house computer but when I get back I will be testing this out. My Asurion phone will play guinea pig. I have much faith. ::excited::
2.3.3 4.24 2.16.0001 (>.<)
Click to expand...
Click to collapse
How much do you pay when you file a claim with asurion? Oh yeah and rock on..now I know I can have root if I ever go stock
I'm starting the process right now, I'll let you guys know how it goes.
[email protected]:~/Downloads$ ./revolutionary
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre1 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: PC36100 (supersonic-2.16.0001, Android: 2.3.3, ROM version: 4.24.651.1)
This is a beta release and requires a beta release key.
Please visit: http://revolutionary.io for more information.
Enter beta key [ serial: HT16EHL00229 ]: n7dgEzmKSqXqogJM
Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so.. Root acquired!
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Waiting for fastboot...
Does this work for the Japanese EVOs?
Edit: Nope. Japanese EVO's won't upgrade to Gingerbread and stay with hboot 2.15.
delete.......
mxl180 said:
how do i install the RA custom recover?
Click to expand...
Click to collapse
After you're s-off, Put this file on the root of your sdcard and go into the bootloader and accept the update.
http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
worked for me, very fast.
themadmen said:
I'm starting the process right now, I'll let you guys know how it goes.
Click to expand...
Click to collapse
Done with the process everything was easy and now i have Root.
themadmen said:
Done with the process everything was easy and now i have Root.
Click to expand...
Click to collapse
I don't think you have enough smilies.
mine program still says its waiting for device can i connected my evo to usb and put it in usb debugging and still no go am i doing something wrong or what?
kidram said:
mine program still says its waiting for device can i connected my evo to usb and put it in usb debugging and still no go am i doing something wrong or what?
Click to expand...
Click to collapse
that happened to me.. try switching to different USB ports, that worked for me.
Nice!! Glad all the flashaholics can come out and play! Good to see the poor souls stuck on Sense finally get Root again. Maybe now some of you won't take the OTA anymore lol
My Evo > Your iPhone - All day long! (XDA Premium App)
Hi. I recently received a refurb EVO and the version shows 2.15.00.05.02. Does it mean that I have a japanese EVO? Why do I have this version?
myriam53 said:
Hi. I recently received a refurb EVO and the version shows 2.15.00.05.02. Does it mean that I have a japanese EVO? Why do I have this version?
Click to expand...
Click to collapse
Ughhh.... Are you in japan?
Sent from my PC36100 using XDA App

Download now Android 4.4 KitKat Sense5.5 stock Ruu.exe files

Now you can download the latest stock Android 4.4 KitKat with Sense 5.5 RUU.exe files on:
http://androidruu.com/?developer=M7
Greetz
There's already a specific thread for M7 RUU's.
http://forum.xda-developers.com/showthread.php?t=2428276
herwegan said:
There's already a specific thread for M7 RUU's.
http://forum.xda-developers.com/showthread.php?t=2428276
Click to expand...
Click to collapse
But there are no Android 4.4 KitKat RUU.exe files on.
i've already told it crushalot, i'm sure he'll add them asap. further i've already provided the link you offer here in his thread, so no reason for another RUU thread
I have send them a message to about a week ago but there is no respons.
Sent from my HTC One using xda app-developers app
Justin2003 said:
I have send them a message to about a week ago but there is no respons.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the link man. Some people get way to butt-hurt around here lol.
Sent from my HTC One using xda app-developers app
Thanks for link noticed that there is a ruu.exe for O2 UK do I still need to down grade hboot to use the .exe
You do not have to downgrade the hboot.
Sent from my HTC One using xda app-developers app
Justin2003 said:
I have send them a message to about a week ago but there is no respons.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
troby86 said:
Thanks for the link man. Some people get way to butt-hurt around here lol.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
lol man, it's not that i want to steal his "thanks" or something. i just think it's better to keep the forum clean and keep the equal stuff together in one thread, so it's better to find for everyone. and if there's already a specific and usualy well maintained thread for this topic. so i think it's best to just post the link there (@justin2003) and not open up a new thread (just to get attention/thanks or whatever the reason was).
people that are looking out for 4.19 RUUs will search in the RUU thread and find the link and thank you. and as soon as crushalot has some time to add it, he'll do it. that's it.
Until the RUU thread gets updated, this thread is fine.
I'm a little concerned with the community spirit shown here. @Justin2003 has done nothing wrong, by posting this, he even stated that he PM'd @crushalot but with no response.
..(just to get attention/thanks or whatever the reason was)..
Click to expand...
Click to collapse
This is a little concerning, just because someone posts something doesn't mean they're hunting for thanks (which are worthless, just look at mine ) or attention (this is the internet, who cares ).
Save the hate for the iPhone crowd.
Andy said:
Until the RUU thread gets updated, this thread is fine.
I'm a little concerned with the community spirit shown here. @Justin2003 has done nothing wrong, by posting this, he even stated that he PM'd @crushalot but with no response.
This is a little concerning, just because someone posts something doesn't mean they're hunting for thanks (which are worthless, just look at mine ) or attention (this is the internet, who cares ).
Save the hate for the iPhone crowd.
Click to expand...
Click to collapse
Nothing to be concerned about! i just thought to do the right thing by indicating to keep the forum clean based on my own experiences with thread openings.. not all mods think the way you do but nvm, let's stop here.
Cheers
herwegan said:
lol man, it's not that i want to steal his "thanks" or something. i just think it's better to keep the forum clean and keep the equal stuff together in one thread, so it's better to find for everyone. and if there's already a specific and usualy well maintained thread for this topic. so i think it's best to just post the link there (@justin2003) and not open up a new thread (just to get attention/thanks or whatever the reason was).
people that are looking out for 4.19 RUUs will search in the RUU thread and find the link and thank you. and as soon as crushalot has some time to add it, he'll do it. that's it.
Click to expand...
Click to collapse
Look at Bugsy Lawsons RUU thread...all download links are removed. I think, the thread can also be removed. It´s better to have one more chance for a download, if something like this happens again.
Sorry everyone, I can't dedicate nearly as much time to the threads I used too due to a new demanding job with no access to post during the day and more family duties in the evening.
I will work on downloading the updated RUU files and get them posted on my site and on the collection thread I started.
I am not purposely trying to ignore anyone, but I get at least 20 support request emails and 5-6 PM's per day and as I stated I just don't have the time to answer them all.
Thanks to Justin2003 for creating the thread with the links.
I do not need attentions or thanks but i know that there are a lot of people who wants back to stock without first s-off the phone to downgrade the hboot.
Sent from my HTC One using xda app-developers app
Thank you Justin, the official RUU helped me restoring the device in pseudo original state (still unlocked, with supercid and S-off ofcouse) but without having to mess with reconstructed, dumped and/or skeletonized ROMs.
Sorry for the noobish question but after reading through the myriad of "Help Me!" threads, I've gotten a bit confused on what can/can't be used with all the different security & lock states. If I'm S-OFF w/ unlocked bootloader, can I run the ruu.exe? Or am I better off waiting for a decrypted ruu.zip?
As far as I understand it, I believe I can pretty much run anything w/ S-OFF and it's up to me to make sure that what I run is compatible with my device, lest I risk bricking it. Is that an accurate assessment? Are there any avenues to restore that cannot or should not be used while S-OFF? Are there any that would require relocking the bootloader while S-OFF?
Sent from my HTC One using xda app-developers app
sharksfan7 said:
Sorry for the noobish question but after reading through the myriad of "Help Me!" threads, I've gotten a bit confused on what can/can't be used with all the different security & lock states. If I'm S-OFF w/ unlocked bootloader, can I run the ruu.exe? Or am I better off waiting for a decrypted ruu.zip?
As far as I understand it, I believe I can pretty much run anything w/ S-OFF and it's up to me to make sure that what I run is compatible with my device, lest I risk bricking it. Is that an accurate assessment? Are there any avenues to restore that cannot or should not be used while S-OFF? Are there any that would require relocking the bootloader while S-OFF?
Click to expand...
Click to collapse
You understand correctly.
You can do anything. With great power comes great responsibility.
Occasionally an RUU won't work because your HBOOT is incompatible or your HTC drivers aren't current or your CID or MID is incompatible. Generally you can fix these things and try again.
The two most common things that brick phones are a failed HBOOT flash or trying to S-ON with a non-stock HBOOT.
Justin2003 said:
Now you can download the latest stock Android 4.4 KitKat with Sense 5.5 RUU.exe files on:
Click to expand...
Click to collapse
Thanks for this link.
(downloading right now)
Sorry for the noob question but I'm facing a bug with my HTC One running 4.3, so I want to try 4.4.2.
My phone is rooted/unlocked and I've installed CWM recovery. All of which I want to keep !!
OTA 4.4.2 update would not install due to CWM recovery.
Will this .exe file allow me tu upgrade to 4.4.2 without the need to remove CWM recovery and SuperUser ?
Thanks for your help here.
Sounds like what you want can be accomplished by either reverting to a stock recovery and accepting the OTA before putting CWM back, or just flashing a 4.4.2 ROM in your custom recovery- either way this discussion probably doesn't belong in this thread.
Note flashing Kit Kat manually requires a compatible recovery and S-OFF, I believe.
The OTA should preserve your settings and data.
You may or may not be able to keep your settings and data intact if you go the manual route.
If you do an RUU you *definitely* won't be able to keep data:
Real, complete, signed RUU's from HTC rewrite everything. The erase your pictures, they install a stock recovery, they touch every partition.
(There are some firmware-only and other hybrid packages posted various places in this forum that behave like RUU's but are more selective in which partitions are touched.)
Merely flashing a ROM only really touches /system (it also touches /boot and /cache technically). Depending on how stable the result is, you may also choose to erase /data in a separate action.
To clear up a point about terminology, root access is something that is usually baked into the ROM you are flashing. RUU always leaves you with a stock, unooted ROM. Flashing almost any custom ROM automatically gives you root as a side benefit. Root is not the same as S-OFF.
Anyway, you probably don't need an RUU unless you get into serious trouble. Until then, you might want to ask for more help over in Q&A...
Sent from my HTC One using xda app-developers app

Categories

Resources