Hi everyone, need some help.
Just updated hboot from 6.98.0002 to 7.00.2002 and now I have *Locked*
7.00.2002 S-OFF and stuck at HTC logo...
So is there any way to get back to 6.98?
Loki14 said:
Hi everyone, need some help.
Just updated hboot from 6.98.0002 to 7.00.2002 and now I have *Locked*
7.00.2002 S-OFF and stuck at HTC logo...
So is there any way to get back to 6.98?
Click to expand...
Click to collapse
7.00.002 ??!!
That's the first time i've come across that hboot version! Can you give some more details regarding how you got this hboot version?
And you say you have S-Off, with *Locked* ?? You're turning my world upside down man... either you're confused, or I am!!
Loki14 said:
Hi everyone, need some help.
Just updated hboot from 6.98.0002 to 7.00.2002 and now I have *Locked*
7.00.2002 S-OFF and stuck at HTC logo...
So is there any way to get back to 6.98?
Click to expand...
Click to collapse
*removed due to epic *donthaveaclueness* lol gonna read up a bit i guess
Here it is)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Saga s-off locked, 7.00.2002)
Отправлено с моего Desire S
Loki14 said:
Here it is)
Saga s-off locked, 7.00.2002)
Отправлено с моего Desire S
Click to expand...
Click to collapse
Awesome!! I'm thoroughly confused now!
This is new to me! Anybody have a clue what's up with this development?
@OP, please, please tell me how'd you manage to do this?
enigmaamit said:
@OP, please, please tell me how'd you manage to do this?
Click to expand...
Click to collapse
So, I used to have 6.98 revolutionary s-off.I downloaded hboot 7.00.2002 from 4pda forum. Flashed it through fastboot,that's all)
Отправлено с моего Desire S
enigmaamit said:
Awesome!! I'm thoroughly confused now!
This is new to me! Anybody have a clue what's up with this development?
@OP, please, please tell me how'd you manage to do this?
Click to expand...
Click to collapse
The only thing running through my mind is sense ICS build but it seems far fetched.
BTW, that bug is getting to me!!
dan-fish said:
The only thing running through my mind is sense ICS build but it seems far fetched.
BTW, that bug is getting to me!!
Click to expand...
Click to collapse
LoL!! Ya, ben_pyett also PM'ed me about the bug!
BTW, what's stranger than the hboot version, is that he has a Locked bootloader, while being S-Off! What's up with that?
Has his phone mutated??!!
I guess it is modified version of 2.00.2002 which has written *LOCKED* on top of it too (see here) so it is not a concern.
But better download and flash 2.00.2002 from the development thread here - it is tested and considered harmless unlike yours...
Or even better - use 0.98.2000 - you will get your full cache size with it, not like with the new one
amidabuddha said:
I guess it is modified version of 2.00.2002 which has written *LOCKED* on top of it too (see here) so it is not a concern.
But better download and flash 2.00.2002 from the development thread here - it is tested and considered harmless unlike yours...
Or even better - use 0.98.2000 - you will get your full cache size with it, not like with the new one
Click to expand...
Click to collapse
But how is an S-off phone Locked?? What is locked, if the phone is S-off??!!
enigmaamit said:
But how is an S-off phone Locked?? What is locked, if the phone is S-off??!!
Click to expand...
Click to collapse
I have tried to enter this field some time ago.
basically there are a bunch of guys who managed to make a reverse engineering on the bootloader files - this caused the birth of bootloaders for Desire S with versions 6.98.1000 and 6.98.1002. One of them had AlpharevX written on top, the other one had Revolutionary if my memory recalls me right. They had the engineering abilities in the form of Security OFF, more fastboot subcommands and protection from overwriting.
Then the 2.00.2002 appeared in the forums, clearly not a product of the Revolutionary team. But in each case (it can be an official leak or modified by another hacker) the guy who did it just has not replaced the top text (the particular string of code) with his custom one. So it remained *LOCKED* just like the stock 2.00.0002 bootloader, but with Eng abilities...
And now we see its clone here, but I cannot say what difference or benefits can it bring over the classic 2.00.2002 one...
@enigmaamit - Don't fry your brain with all this crap Anyone who s-off's via Revolutionary or XTC Clip and updates to hboot 2.00.2002 gets this. The "LOCKED" indicates the bootloader is not unlocked via HTC Dev.com but in our case, the security has been turned off, so the lock is useless. The lock can be easily bypassed, so it's possible to flash stuff with an S-On phone too, but since the security flag gives a security error if anything not signed by HTC is flashed, and prevents the phone from booting, the security needs to be turned off.
@Others - A google search told me that this is a bootloader released on a Russian forum. Nothing to get excited about, definitely not ICS related
@enigmaamit, again - Seriously, remove that bug. You clearly placed it there to "bug" us, you've fulfilled your purpose. I almost smashed my monitor with a magazine when i first saw it
shrome99 said:
@enigmaamit, again - Seriously, remove that bug. You clearly placed it there to "bug" us, you've fulfilled your purpose. I almost smashed my monitor with a magazine when i first saw it
Click to expand...
Click to collapse
Not happening!! I'm enjoying this too much!!
---------- Post added at 10:41 PM ---------- Previous post was at 10:25 PM ----------
shrome99 said:
@enigmaamit - Don't fry your brain with all this crap Anyone who s-off's via Revolutionary or XTC Clip and updates to hboot 2.00.2002 gets this. The "LOCKED" indicates the bootloader is not unlocked via HTC Dev.com but in our case, the security has been turned off, so the lock is useless. The lock can be easily bypassed, so it's possible to flash stuff with an S-On phone too, but since the security flag gives a security error if anything not signed by HTC is flashed, and prevents the phone from booting, the security needs to be turned off.
Click to expand...
Click to collapse
Thank you for that insight... things are complicated enough with all the S-on, S-off, HTCDevil Unlock, RUU, Misc_version, CID, Goldcard, the infamous pain-in-the-rhetorical eMMC f***k-up and what not... and now this... Ughhh!! Things just keep getting more and more mysterious with each passing week! Sometimes i just feel like migrating to a Samsung, load up Odin, and forget about this non-sense!!
You kidding me??? Samsung is simple? The ROMs are baseband specific, and the wrong baseband causes issues, that's the reason why everyone is asking "What Radio is compatible with this ROM"? Also, i told you not to fry your brain with this crap, you have no reason whatsoever to have to know this. Ignorance is bliss......
Also, if you're like, you could never give up HTC Sense, so you must deal with this non-sense
Guys S-OFF/S-ON and LOCKED/UNLOCKED/RELOCKED are two different things. I have a phone that is s-offed with xtc clip. I flashed the latest RUU and I have the 2.** hboot and I'm LOCKED but yet still S-OFF.
EDIT: But the way, is this "full cache" thing is really important? I mean I can see that I always has like 90% of cache free anyway.
Sent from my HTC Desire S
shrome99 said:
You kidding me??? Samsung is simple? The ROMs are baseband specific, and the wrong baseband causes issues, that's the reason why everyone is asking "What Radio is compatible with this ROM"? Also, i told you not to fry your brain with this crap, you have no reason whatsoever to have to know this. Ignorance is bliss......
Also, if you're like, you could never give up HTC Sense, so you must deal with this non-sense
Click to expand...
Click to collapse
IMO nothing is simple in the world till you learnt. I M using Samsung and believe me its so simple for flashing anything. I owned DS little while ago. this is my first Htc phone. currently reading stickies. Simply I found little hard, coz I don't know much about RUU, Locked boot loader etc.
dmatik said:
EDIT: But the way, is this "full cache" thing is really important? I mean I can see that I always has like 90% of cache free anyway.
Click to expand...
Click to collapse
You are absolutely right. But why waste 150 MB? And for the record - I had the famous "Error: cannot mount cache" only once (not "fried" eMMC luckily), when I was using the new 2.00.2002 bootloader close to the date of its release. I am on 0.98.2000 since and had never encountered this issue again. And I have done quite some flashing...
amidabuddha said:
You are absolutely right. But why waste 150 MB? And for the record - I had the famous "Error: cannot mount cache" only once (not "fried" eMMC luckily), when I was using the new 2.00.2002 bootloader close to the date of its release. I am on 0.98.2000 since and had never encountered this issue again. And I have done quite some flashing...
Click to expand...
Click to collapse
Yep, flashed today the 0.98.2000 ENG hboot. To save some space for the cache
Sent from my HTC Desire S
shrome99 said:
You kidding me??? Samsung is simple? The ROMs are baseband specific, and the wrong baseband causes issues, that's the reason why everyone is asking "What Radio is compatible with this ROM"? Also, i told you not to fry your brain with this crap, you have no reason whatsoever to have to know this. Ignorance is bliss......
Also, if you're like, you could never give up HTC Sense, so you must deal with this non-sense
Click to expand...
Click to collapse
yeah samsung is not simple. Installing a custom ROM was a pain on a friends S2 because there seemed to be a million ways to do it. At least with the Desire S it was clear what needed to be done.
dan-fish said:
yeah samsung is not simple. Installing a custom ROM was a pain on a friends S2 because there seemed to be a million ways to do it. At least with the Desire S it was clear what needed to be done.
Click to expand...
Click to collapse
It is as simple as eating cake
Sent from my GT-I9100 using Tapatalk
Related
Hi all I updated to the OTA 3.29 though sprint this is what I did....
I was rooted but the update unrooted which we all know we were told that.
So I ran this method 1st with the org stock 3.26... http://forum.xda-developers.com/showthread.php?t=780141 that was rooted via unrEVOked 3.21: one-click root for Froyo, no downgrading...
then ran the 3.26 ruu to get the phone back to stock everything when k...
then I did the ota 3.29 update the phone now has the new radio 2.15.00.09.01, hboot 0.97 and prl 1.77. (NICE)
After that I ran this... How to Unroot the EVO in 2 STEPS http://forum.xda-developers.com/showthread.php?t=776477, it rooted the phone again... (NICE IT WORKS)
But then I said ok I want to start over just to see if something goes wrong with the phone I will be able to go back to unroot to bring the phone to sprint for repair or replacement and to my surprise (BIG NOPE )
When I try to run http://forum.xda-developers.com/showthread.php?t=780141 go turn S-OFF back to S-ON it FAILS...
I know the Devs will fix this soon but I just wanted to let everyone know just in case you are thinking of rooting your phone after the NEW OTA 3.29 update that once you root u cant go back.....
Y would you do this..... Never take an over the air update. It has been stated time and time again
S-Off and S-On is tied to the radio and Hboot. Unrevoked will get it fixed shortly. Otherwise its probably downgrade radio and hboot time.
James
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice.
10char
RED!!!!!!!!
rutter9 said:
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
b0ricua said:
FACEPALM!!!
Click to expand...
Click to collapse
LMAO !!! When there's nothing else to say...
bigj225 said:
Y would you do this..... Never take an over the air update. It has been stated time and time again
Click to expand...
Click to collapse
Agree, but if you look at the root and other threads you'll see an amazing number of folks determined to do OTA's.
This is a good link to show just one of the things that can "break" if you use OTA and give the unrevoked team heads up for future on the S-On issue.
This link is good guide http://forum.xda-developers.com/showthread.php?t=790394 on how to do the OTA and get back to root after your break things. I've suggested he add Amon RA as well as Clockwork and pointed out this thread.
Again don't agree with the OTA approach...but these threads/links are useful.
Jim
awjs said:
Hi all I updated to the OTA 3.29 though sprint this is what I did....
I was rooted but the update unrooted which we all know we were told that.
So I ran this method 1st with the org stock 3.26... http://forum.xda-developers.com/showthread.php?t=780141 that was rooted via unrEVOked 3.21: one-click root for Froyo, no downgrading...
then ran the 3.26 ruu to get the phone back to stock everything when k...
then I did the ota 3.29 update the phone now has the new radio 2.15.00.09.01, hboot 0.97 and prl 1.77. (NICE)
After that I ran this... How to Unroot the EVO in 2 STEPS http://forum.xda-developers.com/showthread.php?t=776477, it rooted the phone again... (NICE IT WORKS)
But then I said ok I want to start over just to see if something goes wrong with the phone I will be able to go back to unroot to bring the phone to sprint for repair or replacement and to my surprise (BIG NOPE )
When I try to run http://forum.xda-developers.com/showthread.php?t=780141 go turn S-OFF back to S-ON it FAILS...
I know the Devs will fix this soon but I just wanted to let everyone know just in case you are thinking of rooting your phone after the NEW OTA 3.29 update that once you root u cant go back.....
Click to expand...
Click to collapse
Grab the latest S-ON too from http://unrevoked.com/forever
I think you're using an older version that doesn't support your current radio. There's another way we can take you to S-ON as well if that doesn't work.
rutter9 said:
Click to expand...
Click to collapse
hahahahahahahaha
mmastrac said:
Grab the latest S-ON too from http://unrevoked.com/forever
I think you're using an older version that doesn't support your current radio. There's another way we can take you to S-ON as well if that doesn't work.
Click to expand...
Click to collapse
Is the new 2.15.00.09.01 radio supported? It's not in the list.
Is it possible to downgrade the radio?
and why? Too much time on your hands?
Facepalm!!!!!!!!!!!
K 1st thing if you look at my join date to all the rest of you fu..k heads you can see that I have been doing this longer....
2nd I always do different steps to see what gets broken and what works because that how we check and get things fixed around here...
So excuse me if all I wanted to do is to help and tell the so many people that ran the simple unrevoke tool that if they do it they will not be able to unroot until its fixed...
And by the way I fixed it and thats what I all waus try to do but you can all fu..k off if this is the way you are all going to be
SORRY FOR TRYING TO HELP
I'm confused... you tried to unroot a phone that wasn't rooted? Maybe you linked the wrong thread in the 6th line of your post?
I think the people poking fun at you thought you had run the OTA and lost root.
firewalkwithme said:
I'm confused... you tried to unroot a phone that wasn't rooted? Maybe you linked the wrong thread in the 6th line of your post?
I think the people poking fun at you thought you had run the OTA and lost root.
Click to expand...
Click to collapse
yes the phone was rooted via unrevoked and it all works fine..
[GUIDE] How to Unroot the EVO in 2 STEPS & [GUIDE] One Click How to Root the EVO with Unrevoked 3.21 Two very good guides by djR3Z....
The new update has a different radio 2.15....9, prl 1.77, and software # meaning 3.29..
I did loose root but with the new update you can use the One Click How to Root the EVO with Unrevoked 3.21 and the phone will be rooted again thats good think I can even flash a custom... The issue that I was trying to let people be aware of is that is they update and use the unrevoked 3.21 to root the phone they wont be able to go back to unrooted just by using the How to Unroot the EVO in 2 STEPS... Thats all I was trying to do...
FOR ALL YOU HATERS I DID FIX IT AND I NOW KNOW WHAT TO DO TO FIX IT BUT YOU CAN ALL WAIT FOR UNREVOKED TO FIX THE TOOL TO WORK WITH THE NEW HBOOT AND RADIO....
This is y I dont post alot because you all never have good **** to say.... all we here is omg there is a new update and the devs are takeing so long to get it to us and when someone tries to give some good info you all talk ****...
awjs said:
FOR ALL YOU HATERS I DID FIX IT AND I NOW KNOW WHAT TO DO TO FIX IT BUT YOU CAN ALL WAIT FOR UNREVOKED TO FIX THE TOOL TO WORK WITH THE NEW HBOOT AND RADIO....
Click to expand...
Click to collapse
Congrats!!!!!!!!
awjs said:
yes the phone was rooted via unrevoked and it all works fine..
[GUIDE] How to Unroot the EVO in 2 STEPS & [GUIDE] One Click How to Root the EVO with Unrevoked 3.21 Two very good guides by djR3Z....
The new update has a different radio 2.15....9, prl 1.77, and software # meaning 3.29..
I did loose root but with the new update you can use the One Click How to Root the EVO with Unrevoked 3.21 and the phone will be rooted again thats good think I can even flash a custom... The issue that I was trying to let people be aware of is that is they update and use the unrevoked 3.21 to root the phone they wont be able to go back to unrooted just by using the How to Unroot the EVO in 2 STEPS... Thats all I was trying to do...
FOR ALL YOU HATERS I DID FIX IT AND I NOW KNOW WHAT TO DO TO FIX IT BUT YOU CAN ALL WAIT FOR UNREVOKED TO FIX THE TOOL TO WORK WITH THE NEW HBOOT AND RADIO....
This is y I dont post alot because you all never have good **** to say.... all we here is omg there is a new update and the devs are takeing so long to get it to us and when someone tries to give some good info you all talk ****...
Click to expand...
Click to collapse
Don't hold other being jackasses against all of us. I really am curious as to how you fixed this. Please let us in on it.
mmastrac said:
Grab the latest S-ON too from http://unrevoked.com/forever
I think you're using an older version that doesn't support your current radio. There's another way we can take you to S-ON as well if that doesn't work.
Click to expand...
Click to collapse
+1 Not a really long wait..
SITH16 said:
Don't hold other being jackasses against all of us. I really am curious as to how you fixed this. Please let us in on it.
Click to expand...
Click to collapse
PM me and Ill send it to you....
awjs said:
PM me and Ill send it to you....
Click to expand...
Click to collapse
thats not fair.... lol i want to know too
I've been hearing a lot of hoopla about a new signed bootloader on the Thunderbolt and on other HTC models going forward. Can anyone clarify this for me?
How different is the Thunderbolt's level of protection from what was employed on the Desire HD / Z / G2? Is there anything that *won't* be possible in terms of custom ROMs on the Thunderbolt that was previously possible on other HTC devices? I'm not even in the USA but this question may ultimately be useful for the Incredible S, Desire S, etc.
We have s-off so u need not to worry bout a signed bootloader
Sent from my ADR6400L using XDA Premium App
Disaster avoided. Thank you TeamAndIRC
Aha okay, so a Thunderbolt with S-OFF is equally hackable to any prior HTC phone with S-OFF? Good to know.
Whereas Motorola phones don't seem to have any equivalent to S-OFF
All this talk of signed boot loaders is nonsense.... this is nothing new and some sites are creating drama so they can get add clicks on their site. Sad when they have to stir **** up for no reason.
I'm not sure of any phone besides the droid one and nexus that haven't had signed boot loaders. nonsense games to make money from android users clicking their adds.
R1lover said:
All this talk of signed boot loaders is nonsense.... this is nothing new and some sites are creating drama so they can get add clicks on their site. Sad when they have to stir **** up for no reason.
I'm not sure of any phone besides the droid one and nexus that haven't had signed boot loaders. nonsense games to make money from android users clicking their adds.
Click to expand...
Click to collapse
Hit me up on irc, I think there is some confusion. The bootloaders are checking for signatures on boot.img and recovery.img. Certainly different and new to HTC.
If they are not signed, you get this if you try to boot into recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and are locked out of using the recovery until you fix it, or set s-off, or worse if its your boot partition the phone won't boot into android until you RUU it.
They are certainly real, and new. To date only the thunderbolt, incredible s and the incredible 2 are the only known devices with them.
Wit the ENG hboot, you don't have to worry about this issue. It doesn't verify the signature (hence our need to use it).
- TeamAndIRC
And from my understanding, the only reason S-Off was achieved so quickly with the Thunderbolt is because its firmware is based on that of the Desire HD and still contained a known exploit. The Incredible S/2 firmware has patched this exploit, so another one will need to be found.
I really don't like the direction HTC is going. If this holds true, the Thunderbolt will probably be my last non-Nexus phone. Glad I decided to go with only a 1-year contract.
I guess my point was the incredible was the same way and is a year old now, so why is this considered new?
Sent from my ADR6400L using Tapatalk
I am by far non a crypto expert, but here is the best example I can provide, without having to do a restore on my own phone right now.
boot.img one is a HTC made thunderbolt kernel (not released) that can from a engineering device, and did not use signed images.
boot_signed.img one is the stock thunderbolt kernel that comes with the thunderbolt.
Same thing here but with stock recovery v/s unreleased dev recovery.
The release devices carry signatures, but not engineering devices.
Hope this helps some.
R1lover said:
I guess my point was the incredible was the same way and is a year old now, so why is this considered new?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Incredible did not carry signed images, check a stock ruu yourself.
stoli412 said:
And from my understanding, the only reason S-Off was achieved so quickly with the Thunderbolt is because its firmware is based on that of the Desire HD and still contained a known exploit. The Incredible S/2 firmware has patched this exploit, so another one will need to be found.
I really don't like the direction HTC is going. If this holds true, the Thunderbolt will probably be my last non-Nexus phone. Glad I decided to go with only a 1-year contract.
Click to expand...
Click to collapse
Not exactly, it did not contain the vulnerability as is, we had to introduct with with outdated firmware.
jcase said:
Incredible did not carry signed images, check a stock ruu yourself.
Click to expand...
Click to collapse
If you say so.... but I thought it was the same way.... we went through hell until they gained a full s=off.
R1lover said:
I guess my point was the incredible was the same way and is a year old now, so why is this considered new?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
To double check, I went and grabbed a incredible stock image.
The incredible has s-on ans nand locking as stock, but does not have signatures in boot/recovery and does not check for signatures.
Once you had root and nand unlock on the incredible, you could freely write to recovery without worry.
Hope this helps clear some confusion.
R1lover said:
If you say so.... but I thought it was the same way.... we went through hell until they gained a full s=off.
Click to expand...
Click to collapse
You guys needed s-off to maintain nand unlock (similar to our need for emmc unlock) at all times. Else you could only write to /system while in recovery.
I hope someone with a better grasp of this than I will chime in and explain it in better detail.
It's all good... you showed me the pudding... lol :beer
As long as I'm rooted with my current phone.. all is well lol I have another year to worry about locked down crap... until then... happy root!
cmstlist said:
Is there anything that *won't* be possible in terms of custom ROMs on the Thunderbolt that was previously possible on other HTC devices?
Click to expand...
Click to collapse
This is the question I would like to be answered...
Sent from my ADR6400L using XDA App
dclay89 said:
Is there anything that *won't* be possible in terms of custom ROMs on the Thunderbolt that was previously possible on other HTC devices?
This is the question I would like to be answered...
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Not as long as you keep s-off.
dclay89 said:
This is the question I would like to be answered...
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No... unless LTE radio and 3G/Voice simultaneous give us problems. Otherwise this phone is no different that its Cousin EVO or Desire HD. Eng S-OFF technically can be classified as a Developers Device Bootloader. With a developer bootloader, the possibilities are endless
This phone is fully *unlocked* just like all other HTC android phones (except for the Incredible S/2 YET)
andrew8806 said:
No... unless LTE radio and 3G/Voice simultaneous give us problems. Otherwise this phone is no different that its Cousin EVO or Desire HD. Eng S-OFF technically can be classified as a Developers Device Bootloader. With a developer bootloader, the possibilities are endless
This phone is fully *unlocked* just like all other HTC android phones (except for the Incredible S/2 YET)
Click to expand...
Click to collapse
So unless a Eng bootloader gets leaked for them it could be awhile before they get cracked if ever correct?
Sent from my ADR6400L using Tapatalk
If you are able to flash roms and kernel all in one with out having to use the fastboot method, i suggest you do not flash any updated RUU's
Everything in that ruu is included in all the new roms 2.20 and 2.23 bases, radio are found in the radio thread too. If you take the ruu, you are only setting your self back in development for S-Off and will create a headache for developers and users.
If you want the latest and greatest, then flash the new rooted roms we have in developers section and flash the radios too but i dont recommend anyone taking a updated RUU
XsMagical said:
If you are able to flash roms and kernel all in one with out having to use the fastboot method, i suggest you do not flash any updated RUU's
Everything in that ruu is included in all the new roms 2.20 and 2.23 bases, radio are found in the radio thread too. If you take the ruu, you are only setting your self back in development for S-Off and will create a headache for developers and users.
If you want the latest and greatest, then flash the new rooted roms we have in developers section and flash the radios too but i dont recommend anyone taking a updated RUU
Click to expand...
Click to collapse
or See my PSA thread
XsMagical said:
If you are able to flash roms and kernel all in one with out having to use the fastboot method, i suggest you do not flash any updated RUU's
Everything in that ruu is included in all the new roms 2.20 and 2.23 bases, radio are found in the radio thread too. If you take the ruu, you are only setting your self back in development for S-Off and will create a headache for developers and users.
If you want the latest and greatest, then flash the new rooted roms we have in developers section and flash the radios too but i dont recommend anyone taking a updated RUU
Click to expand...
Click to collapse
It's not that beneficial to flash a radio without the ril and we can't flash ril's on the 4.0.4 based roms without errors.
Sent from my HTC One XL using xda app-developers app
SkizzMcNizz said:
It's not that beneficial to flash a radio without the ril and we can't flash ril's on the 4.0.4 based roms without errors.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
You are very mistaken. Ril with matching radio on proper framework work perfect. I had been messing with radios, rils and different firmwares for quite a bit. If you know what you are doing, yes you can mix. A ruu will make no difference. All roms come with rils fyi
Sent from my Nocturnal'd ONE XL
SkizzMcNizz said:
It's not that beneficial to flash a radio without the ril and we can't flash ril's on the 4.0.4 based roms without errors.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Xs is right, look at all the proved reports of people gaining nearly a double in LTE and H+ Speeds in cleanroms forums and in a few others with 2.20 Radio over 1.85, 2.09, and 2.23
I think that's beneficial? i also noticed alot less battery drain and managed to work a full 8 hours with 100% brightness, web browsering, texting, and calls without plugging her up
P.S. oooh im a senior member now when did that happen?
XsMagical said:
If you are able to flash roms and kernel all in one with out having to use the fastboot method, i suggest you do not flash any updated RUU's
Everything in that ruu is included in all the new roms 2.20 and 2.23 bases, radio are found in the radio thread too. If you take the ruu, you are only setting your self back in development for S-Off and will create a headache for developers and users.
If you want the latest and greatest, then flash the new rooted roms we have in developers section and flash the radios too but i dont recommend anyone taking a updated RUU
Click to expand...
Click to collapse
Now you are very mistaken There are a lot of other partitions/firmware you get from installing a ruu that you don't get when you install a custom rom. It would be great if you guys could possibly make a firmware flash option like mike1986 and some of the other veteran devs do. Include the stuff that's beneficial, leave out (hboot) the stuff we don't want or need. Mike1986 swears by installing his firmware zips when there has been a significant change. With 24000 thanks and support for 11 or 12 devices hes probably one of the best Rom developers android has. Here Is a link to one of his firmware threads so you can see what I'm talking about. http://forum.xda-developers.com/showthread.php?t=1412618
Compare a dump from 4.03 and 4.04. We probably didnt need this with the 4.03 ruus. There are some nice fixes in the new 2.20. The rom image alone might not give us all of the benefits. I know it can be a little more work but the goal is the best running device possible right? 4.03 to 4.04 is a significant update. On the sensation not flashing the new firmware you would almost always take a performance and battery life hit. Not to mention strange random bugs.
Now that there are two different hboots in play we might have to stop including kernels etc in the roms... Have to be flashed separately. Include the other necessary firmware/partitions like mike1986 does as a separate package. Plenty of devices that are that way. We've just been lucky to be able to do it without soff. New phones are being shipped with new firmware. Once root is found then there will be a lot more new hboots flashing custom roms... You will have to change the way you do things. Its gonna get harder for rom devs when new revisions are out, its that simple.
How can you know that the new hboot will hinder s-off development? It could very well be the answer to s-off as far as anybody knows... HTC made changes.. They could have made a mistake.
Why firmware package like mike1986 does is better then full RUU: You get the advantages and leave out the disadvantages
1. It doesn't contain stock recovery
2. It doesn't contain stock, non rooted system
3. It doesn't contain secured boot.img
4. It wont wipe your data partition
5. It's much smaller
This is an example of the things that are in his firmware package..
adsp.img - updated [11.07.2012] - This is needed for 3.12.xxx.x/3.24.xxx.x/3.25.xxx.x/3.30.xxx.x/3.32.xxx.x/3.33.xxx.x based ROM to boot!
android-info.txt - updated [011.07.2012]
dzdata_4g.hdr - removed from the package [28.12.2011]
dzdata_4g.img - removed from the package [28.12.2011]
hboot_8x60_1.29.0000_20120302_signedbyaa.nb0 (with locked fastboot) - updated [11.07.2012]
pg2fs_spcustom.img - removed from the package [01.03.2012]
radio.img - updated [11.07.2012]
rpm.img - updated [11.07.2012]
sbl1.img - updated [20.01.2012]
sbl2.img - updated [22.02.2012]
sbl3.img - updated [20.01.2012]
tz.img - updated [11.07.2012]
AD8 said:
There are a lot of other partitions/firmware you get from installing a ruu that you don't get when you install a custom rom. It would be great if you guys could possibly make a firmware flash option like mike1986 and some of the other veteran devs do. Include the stuff that's beneficial, leave out (hboot) the stuff we don't want or need. Mike1986 swears by installing his firmware zips when there has been a significant change. With 24000 thanks and support for 11 or 12 devices hes probably one of the best Rom developers android has. Here Is a link to one of his firmware threads so you can see what I'm talking about. http://forum.xda-developers.com/showthread.php?t=1412618
Compare a dump from 4.03 and 4.04. We probably didnt need this with the 4.03 ruus. There are some nice fixes in the new 2.20. The rom image alone might not give us all of the benefits. I know it can be a little more work but the goal is the best running device possible right? 4.03 to 4.04 is a significant update. On the sensation not flashing the new firmware you would almost always take a performance and battery life hit. Not to mention strange random bugs.
Now that there are two different hboots in play we might have to stop including kernels etc in the roms... Have to be flashed separately. Include the other necessary firmware/partitions like mike1986 does as a separate package. Plenty of devices that are that way. We've just been lucky to be able to do it without soff. New phones are being shipped with new firmware. Once root is found then there will be a lot more new hboots flashing custom roms... You will have to change the way you do things. Its gonna get harder for rom devs when new revisions are out, its that simple. You shouldn't ask people not to flash something that could solve a lot of problems just because it makes your job harder.
How can you know that the new hboot will hinder s-off development? It could very well be the answer to s-off as far as anybody knows... HTC made changes.. They could have made a mistake.
Why firmware package like mike1986 does is better then full RUU: You get the advantages and leave out the disadvantages
1. It doesn't contain stock recovery
2. It doesn't contain stock, non rooted system
3. It doesn't contain secured boot.img
4. It wont wipe your data partition
5. It's much smaller
This is an example of the things that are in his firmware package..
adsp.img - updated [11.07.2012] - This is needed for 3.12.xxx.x/3.24.xxx.x/3.25.xxx.x/3.30.xxx.x/3.32.xxx.x/3.33.xxx.x based ROM to boot!
android-info.txt - updated [011.07.2012]
dzdata_4g.hdr - removed from the package [28.12.2011]
dzdata_4g.img - removed from the package [28.12.2011]
hboot_8x60_1.29.0000_20120302_signedbyaa.nb0 (with locked fastboot) - updated [11.07.2012]
pg2fs_spcustom.img - removed from the package [01.03.2012]
radio.img - updated [11.07.2012]
rpm.img - updated [11.07.2012]
sbl1.img - updated [20.01.2012]
sbl2.img - updated [22.02.2012]
sbl3.img - updated [20.01.2012]
tz.img - updated [11.07.2012]
Click to expand...
Click to collapse
This is what I did for the rezound, check my Sig
This was the only way for the rezound community to switch firmwares without radio issues
Sent from my HTC One X using Tapatalk 2
superchilpil said:
This is what I did for the rezound, check my Sig
This was the only way for the rezound community to switch firmwares without radio issues
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Cool so you agree that is important. a lot of people are having radio issues around here. Question is... i wonder if we can do this without s-off? There are a lot of things we can do without s-off with the hox that other devices cant.. only with the original hboot that is.
i am one of the lucky ones who took the new update. now yes.............there r a ton of improvements!!!! one of my favorites is the sms bubbles r back to a 3D look. not to mention how smooth, and snappier it is now!!!!! i wish i would have waited, but im not mad, ill b happy if im stuck like this 4 awhile!!! i still had my unlock token, si i have root, and options to flash roms, with exception to the boot.img, i cant flash any kernels, or splash screens right now, but im cool with it! hey........i look @ it like this, im helping a little by taking it, i sent beaups a log from my rooted firmware, he is working on a new root method, im good and i know eventually the loop holes will b found like always!
zounduser said:
i am one of the lucky ones who took the new update. now yes.............there r a ton of improvements!!!! one of my favorites is the sms bubbles r back to a 3D look. not to mention how smooth, and snappier it is now!!!!! i wish i would have waited, but im not mad, ill b happy if im stuck like this 4 awhile!!! i still had my unlock token, si i have root, and options to flash roms, with exception to the boot.img, i cant flash any kernels, or splash screens right now, but im cool with it! hey........i look @ it like this, im helping a little by taking it, i sent beaups a log from my rooted firmware, he is working on a new root method, im good and i know eventually the loop holes will b found like always!
Click to expand...
Click to collapse
you can still flash kernels through fastboot right? Just not included with the rom. So it takes an extra minute...well worth the fixes if you ask me.
AD8 said:
you can still flash kernels through fastboot right? Just not included with the rom. So it takes an extra minute...well worth the fixes if you ask me.
Click to expand...
Click to collapse
Nope. I cant flash boot.img through fastboot
Sent from my HTC One X using xda premium
Let me try again right now, but i tried once and it failed after checking hboot signature. Ill try again quick.
Sent from my HTC One X using xda premium
zounduser said:
Nope. I cant flash boot.img through fastboot
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
you should be able to. i just did it and i took the 2.20 update. This phone is the best it has ever been. Installed cleanrom 4.5 and it runs flawless. Cant wait for a rom based off of 2.20 with linkify removed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XsMagical said:
You are very mistaken. Ril with matching radio on proper framework work perfect. I had been messing with radios, rils and different firmwares for quite a bit. If you know what you are doing, yes you can mix. A ruu will make no difference. All roms come with rils fyi
Sent from my Nocturnal'd ONE XL
Click to expand...
Click to collapse
I'm saying that if we have the 1.85 ril and we flash the 2.20 radio then its not as good as having both the 2.20 radio and ril. It says in the radio thread not to flash any radios + ril's on 4.0.4 based roms. So unless we flash the 2.20 ruu then we won't have both the 2.20 radio and ril.
Sent from my HTC One XL using xda app-developers app
AD8 said:
you should be able to. i just did it and i took the update.
Click to expand...
Click to collapse
Yup it worked
Sent from my HTC One X using xda premium
I must have typed wrong before? This makes me happier? Not that hard to pull the boot.img out of a rom and flash it right after flashing the rom.
Sent from my HTC One X using xda premium
zounduser said:
I must have typed wrong before? This makes me happier? Not that hard to pull the boot.img out of a rom and flash it right after flashing the rom.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Once beaups or whoever gets us root on stock 2.20, kernels will have to be left out of roms or either have two versions of roms. This is why i think its a good time to look into the firmware package idea.. Since we are heading towards flashng seperate kernels anyway..and our phone has two different android versions now.... I wonder how big the bounty would have to be for the EVO people to help us out on the s-off...:crying:
AD8 said:
Cool so you agree that is important. a lot of people are having radio issues around here. Question is... i wonder if we can do this without s-off? There are a lot of things we can do without s-off with the hox that other devices cant.. only with the original hboot that is.
Click to expand...
Click to collapse
Yes I do agree, but without s off its pretty much impossible to do
Sent from my HTC One X using Tapatalk 2
superchilpil said:
Yes I do agree, but without s off its pretty much impossible to do
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Have you been around the hox forums for a while? we can do some amazing things with the original firmware. Really almost everything. members have flashed all kinds of partitions to our phone trying to get s-off. I think thats why s-off develoment slowed down for us...we really didnt need it. None of the older devices could do half the things we can with s-on. The new hboot fixes that though. One of XS's points. Someone will figure out how to ruu back to an older hboot through gold card or whatever i betcha.
AD8 said:
Have you been around the hox forums for a while? cant tell by your sig we can do some amazing things with the original firmware. Really almost everything. I think thats why s-off develoment slowed down for us...we really didnt need it. None of the older devices could do half the things we can with s-on. The new hboot fixes that though. One of XS's points. Someone will figure out how to ruu back to an older hboot through gold card or whatever i betcha.
Click to expand...
Click to collapse
I like your idea about the mike1986 method of flashing firmwares. You should let the developers know. That would be great for us who don't wanna ruu.
This tool will grant you Super CID on your HTC Device
Tested on the following devices:
HTC One M7_UL
HTC One X/XL Evita
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is a CID?
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from 3Mobile (3Mobile is the ‘carrier’), your phone will only accept 3Mobile ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
What is Super CID?
SuperCID : by CID unlocking your device the value of the CID is changed to SuperCID . This allows the flashing of ANY ROM/RUU to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
How to use the script?
Download the attached file
Extract the file
boot your phone into bootloader
Run the script and follow the on screen instructions
How do i get my phone into bootloader?
Power down the device
hold vol down and power at the same time
You can get the script and full CID guide here Click ME
one more for future use
So to say that my One is HTC_044 which is limited to RUU 1.29.707.16 flashing at the moment.
So, with S-Off, I can now flash any RUU available without any worry of bricking my One?
Sent from my HTC One using xda app-developers app
kelvintisw said:
So to say that my One is HTC_044 which is limited to RUU 1.29.707.16 flashing at the moment.
So, with S-Off, I can now flash any RUU available without any worry of bricking my One?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
In theory yes, I have not done it yet to my One but on my One X i had the AT&T Model and i was flashing HTC Asia RUU's no problem. The mount points do not change
XsMagical said:
In theory yes, I have not done it yet to my One but on my One X i had the AT&T Model and i was flashing HTC Asia RUU's no problem. The mount points do not change
Click to expand...
Click to collapse
I see!
Okay. Thanks for the quick advice!
its said I have supercid 11111111 now..however when I use command getprop ro.cid still says HTC_622...no idea why..wired
breadtreemike said:
its said I have supercid 11111111 now..however when I use command getprop ro.cid still says HTC_622...no idea why..wired
Click to expand...
Click to collapse
that is the rom reporting back from what is written, flash something like aosp and it will say something different.
breadtreemike said:
its said I have supercid 11111111 now..however when I use command getprop ro.cid still says HTC_622...no idea why..wired
Click to expand...
Click to collapse
follow this to have supercid in getprop ro cid
http://forum.xda-developers.com/showpost.php?p=42351491&postcount=35
XsMagical said:
that is the rom reporting back from what is written, flash something like aosp and it will say something different.
Click to expand...
Click to collapse
really?ya will wait for next update hope it will come something I wanna miss
---------- Post added at 01:09 AM ---------- Previous post was at 01:01 AM ----------
tjsooley said:
follow this to have supercid in getprop ro cid
http://forum.xda-developers.com/showpost.php?p=42351491&postcount=35
Click to expand...
Click to collapse
thx for sharing..will have a try
---------- Post added at 01:28 AM ---------- Previous post was at 01:09 AM ----------
tjsooley said:
follow this to have supercid in getprop ro cid
http://forum.xda-developers.com/showpost.php?p=42351491&postcount=35
Click to expand...
Click to collapse
hey man it works great here..thx for sharing..
Updated main op with guide from cyber6 be sure to give him thanks for the block info!
Maybe I'm being a bit daft but surely supercid needs root? So how dies you bootloader say locked not tampered?
Sent from my HTC One using xda app-developers app
Your the man XS...works easy...
tjsooley said:
follow this to have supercid in getprop ro cid
http://forum.xda-developers.com/showpost.php?p=42351491&postcount=35
Click to expand...
Click to collapse
You dont need that to run ruus. It is risky and could brick your phone if you mess up. I've personaly trried it without that 2nd method and it works fine. I am on ATT and installed Developer ruu with the fastboot supercid method. Getprop still show CWS__001. Only thing that is good for is changing data icons from 4.2 roms..
I can almost guarantee someone bricks their phone, just takes 1 wrong character..
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
ratykat said:
Maybe I'm being a bit daft but surely supercid needs root? So how dies you bootloader say locked not tampered?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
becase with s-off you can fix the tampered flag.
After super Cid 11111111 my phone, I can't receive any call, so I had return to my old Cid HTC_044, my phone was became normal, can receive call. How to solve this trouble, please help.
ntt2006 said:
After super Cid 11111111 my phone, I can't receive any call, so I had return to my old Cid HTC_044, my phone was became normal, can receive call. How to solve this trouble, please help.
Click to expand...
Click to collapse
Someone will figure out what is causing the issue soon enough but For now, just leave it as HTC__044. Change cid to 11111111 if you need to install an unsupported ruu. No benefit from just having supercid, you gotta use it to benefit.
ntt2006 said:
After super Cid 11111111 my phone, I can't receive any call, so I had return to my old Cid HTC_044, my phone was became normal, can receive call. How to solve this trouble, please help.
Click to expand...
Click to collapse
I come from hTC_044. No issue with super CID
Sent from my HTC One using xda premium
---------- Post added at 04:48 AM ---------- Previous post was at 04:37 AM ----------
I must follow this step for complete super CID? Anyone
Sent from my HTC One using Tapatalk 2
Will you get ota updates with developer ruu if you just change the first cid ?
There's a zip to change data icons in 4.2.2 already. I see no benefit in doing 2nd cid unless that's only way I can get ota.
Cuz I can do it but don't want to if I don't have to
Sent from my HTC One using XDA Premium HD app
ac3kill said:
Will you get ota updates with developer ruu if you just change the first cid ?
There's a zip to change data icons in 4.2.2 already. I see no benefit in doing 2nd cid unless that's only way I can get ota.
Cuz I can do it but don't want to if I don't have to
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
I'm testing this now. Downloading older dev edition ruu. going to install on my ATT one that has just the fastboot cid changed. Then check for OTA. Should know in about 30 minutes.
Which comes first? Unlocking bootloader or s-off? I have htc one 801s so is there any other requirments with that?
kenzhin said:
Which comes first? Unlocking bootloader or s-off? I have htc one 801s so is there any other requirments with that?
Click to expand...
Click to collapse
unlock bootloader first..
Are there anyways that you can s-off at 4.4.2? With 2.22hboot? If yes, is it possible to remove tampered also? And can you return to s-on with fastboot oem writesecureflag 3?
Try revone can't hurt
Sent from my One Mini using Tapatalk
cmvienneau said:
Try revone can't hurt
Sent from my One Mini using Tapatalk
Click to expand...
Click to collapse
I have tried revone. It gives error 1 instead of 2 when I use ./revone -P
Did ya try firewater?
Sent from my One Mini using Tapatalk
cmvienneau said:
Did ya try firewater?
Sent from my One Mini using Tapatalk
Click to expand...
Click to collapse
Does it work for one mini? Or it works for most of the htc?
cmvienneau said:
Did ya try firewater?
Sent from my One Mini using Tapatalk
Click to expand...
Click to collapse
Nope, it doesn't work either ;( I really want to s-off again. Anymore suggestions?
abzboi said:
Nope, it doesn't work either ;( I really want to s-off again. Anymore suggestions?
Click to expand...
Click to collapse
Try to downgrade the hboot to 2.21 that may give back the ability to S-OFF your One Mini
scotty2000 said:
Try to downgrade the hboot to 2.21 that may give back the ability to S-OFF your One Mini
Click to expand...
Click to collapse
Any guide on how to? If I s-off with hboot 2.21, can I upgrade it back to hboot 2.22 so it works?
Hey guys, maybe try Ramrunner to s-off.
abzboi said:
Any guide on how to? If I s-off with hboot 2.21, can I upgrade it back to hboot 2.22 so it works?
Click to expand...
Click to collapse
You need to have the Firmware.zip with the hboot 2.22 to upgrade again, you will find it in the OTA file for example.
You did not say anything about the rom / OTA version (cidnum) that is installed on your mini, but you will need the exact version from the CID, that is now displayed on your Mini !!! For example HTC__001 !
I do not have the hboot 2.22, but i did a firmware flash from hboot 2.21 to hboot 2.19 and back again to hboot 2.21 so I think it should work, but I am S-OFF already !!!
Maybe there is someone around here with experiance of hboot 2.22 and knows which kitkat version/OTA has the needet frimware.zip file.
I only know about the different hboots 2.19 and 2.21 because I flashed these to get my 4.4.2 update.
So be sure you have your version of files that you have now and want back after S-OFF
Try this
fastboot oem rebootRUU
fastboot flash zip firmware.zip (maybe there is a notice that you should do this a second time, then you net to type line 2 again!)
fastboot reboot
As I am not an expert, I don´t know for sure if that works, sorry
You really don't even need s-off? Only thing its good for is mess in **** up.lol
Sent from my One Mini using Tapatalk
cmvienneau said:
You really don't even need s-off? Only thing its good for is mess in **** up.lol
Sent from my One Mini using Tapatalk
Click to expand...
Click to collapse
I have stock AT&T rooted. Just took the ota and rooted. Not sure how I can extract the hboot now. But there are apps like busybox that I can't install because I'm not s-off
.
abzboi said:
I have stock AT&T rooted. Just took the ota and rooted. Not sure how I can extract the hboot now. But there are apps like busybox that I can't install because I'm not s-off
.
Click to expand...
Click to collapse
There are versions on play store of busy box that install from recovery. Maybe "busybox on the rails".
Sent from my HTC One mini using Xparent Green Tapatalk 2
Use a custom rom busy box is preinstalled
Sent from my One Mini using Tapatalk
abzboi said:
Are there anyways that you can s-off at 4.4.2? With 2.22hboot? If yes, is it possible to remove tampered also? And can you return to s-on with fastboot oem writesecureflag 3?
Click to expand...
Click to collapse
I can confirm rumrunner will work.
Sent from my HTC One mini using Tapatalk
cmvienneau said:
I can confirm rumrunner will work.
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
Yea, sorry for not telling you. I already s-off it with rumrunner. I just had to flash a different rom that has unsecured kernel. Thanks though. And also ty for ur ruu extracted files. I downloaded it and flashed the hboot then took the ruu back a while ago when my phone didn't work.
Ive been trying ages to s-off my rooted HTC One Mini (m4) just so I can removed the startup sound, and move some notification sounds into the system notification folder and do other things with the system and remove some bloatware. Here is my setup:
HTC one Mini (M4) Rooted
Stock ROM - Meteor Ireland
Version: 4.3 HTC sense Version 5.5
HBoot: 2.21 0000
Tried Fire Water looks like its going through motions and then says whelp phone is not supported DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS! ... if we are able to fix this issue, it will be announced ********** ********** bye bye.....sorry it didn't work out
Then I tried revone but that failed error = 1 after typing ./revone -P
im stuck now, dunno what to do/try - I dont really want to go down road of wiping/installing different rom if i can help it - phone is too good to brick!
andy_from_ireland said:
Ive been trying ages to s-off my rooted HTC One Mini (m4) just so I can removed the startup sound, and move some notification sounds into the system notification folder and do other things with the system and remove some bloatware. Here is my setup:
HTC one Mini (M4) Rooted
Stock ROM - Meteor Ireland
Version: 4.3 HTC sense Version 5.5
HBoot: 2.21 0000
Tried Fire Water looks like its going through motions and then says whelp phone is not supported DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS! ... if we are able to fix this issue, it will be announced ********** ********** bye bye.....sorry it didn't work out
Then I tried revone but that failed error = 1 after typing ./revone -P
im stuck now, dunno what to do/try - I dont really want to go down road of wiping/installing different rom if i can help it - phone is too good to brick!
Click to expand...
Click to collapse
Rumrunner will s-off your device even after 4.4.2 update.
Sent from my One Mini using Tapatalk
cmvienneau said:
Rumrunner will s-off your device even after 4.4.2 update.
Sent from my One Mini using Tapatalk
Click to expand...
Click to collapse
well what dya know tried rum runner (soju.exe) again today an got a whole lot of new words like 'hmm cap is on tighter than expected' (didnt get that yesterday when I tried it out) and I think (not sure until I try to right to system file later) that it might have done it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My custom kernel has selinux disabled so there's really no need for s-off.
Sent from my One Mini using Tapatalk