seems that someone has obtained to have s-off on desire ! have a look at this . maybe the n1 would be the next (i hope).
It's not needed on the N1, S-OFF for the Desire is the same as the N1 with an unlocked bootloader.
yeah, but with an s-off hboot we could relock the bootloader.
100% completely irrelevant on the N1.
Also, you can't re-lock the boot loader, it is permanent, per the warning you were given when you did it.
What if I want to reflash the unlocked splash screen with the locked one for cosmetic reasons (to hide the lock)? It is a little bit relevant.
G0belet said:
What if I want to reflash the unlocked splash screen with the locked one for cosmetic reasons (to hide the lock)? It is a little bit relevant.
Click to expand...
Click to collapse
That is something I had thought about doing, I must admit.
I didn't try it, but looked for it for completely another reasons (changing the splash screen). Looks like you can't flash "splash1" partition on Nexus, it fails. If you want - you can download splash1.img from any resolution-compatible device (EVO, for example), and try to flash.
Even with S-OFF:
Code:
C:\Users\Rusty\Desktop>fastboot flash splash1 evosplash1.rgb565
< waiting for device >
sending 'splash1' (750 KB)... OKAY [ 0.166s]
writing 'splash1'... FAILED (remote: not allowed)
finished. total time: 0.237s
That answers that then.
I never tried to downgrade my HBOOT but if I'm not mistaken, there's a way to flash mtd1 if my memory serves, and before upgrading you see the HTC logo instead of the Nexus One logo. Again I never had to downgrade my HBOOT but I think there might be a way to see how that img file works, and see if we can change the splash. That's a wild guess at this point.
EDIT: I mean mtd0. Can't we dump it to see what's in it?
The new G2 permroot procedure seems to involve running some sort of kernel module which then allows you to reflash HBOOT with an engineering bootloader and get S-OFF. If you subsequently restore to stock using PC10IMG.zip, the stock bootloader relocks to S-ON.
Would this not be theoretically possible with the N1? There are Nexus One units out there with an engineering bootloader that can go to S-OFF without a permanent watermark. If the ENG HBOOT can be flashed from inside the OS, it could be a way to get S-OFF reversibly.
The ENG HBOOT on the Nexus One is larger than the SHIP one, so apparently it's a no go.
G0belet said:
I never tried to downgrade my HBOOT but if I'm not mistaken, there's a way to flash mtd1 if my memory serves, and before upgrading you see the HTC logo instead of the Nexus One logo. Again I never had to downgrade my HBOOT but I think there might be a way to see how that img file works, and see if we can change the splash. That's a wild guess at this point.
EDIT: I mean mtd0. Can't we dump it to see what's in it?
Click to expand...
Click to collapse
You have HBOOT images (FRG83 and KO-KR FRF91 came with HBOOT 0.35 update, for example), so you don't need to try to dump them. Nobody invested time in hacking them, I believe, because it's not a priority work.
You can customize the partition sizes through command line, but it doesn't override things for fastboot itself - making it impossible to update HBOOT with Eng HBOOT, which is larger and doesn't fit on the HBOOT partition.
I'm not sure MTD0 flashed to MISC partition does anything to HBOOT itself. If it does - it might be possible to flash Desire S-OFF HBOOT on Nexus and deal with the differently partitioned ROM (or revert back to Nexus partitioning with command line override method). Anyway, it won't really bring Nexus back to stock, so it misses the point for all those that want to have their bootloader relocked. Even with substituted splash1 to match locked Nexus, going into bootloader will show a version Nexus doesn't have. Flashing back Nexus HBOOT will return the "unlocked" sign, since it wouldn't be locked.
And it looks like Desire HBOOT is still within the smaller partition size and doesn't enlarge it to fit Nexus Eng SPL.
Jack_R1 said:
I'm not sure MTD0 flashed to MISC partition does anything to HBOOT itself. If it does - it might be possible to flash Desire S-OFF HBOOT on Nexus and deal with the differently partitioned ROM (or revert back to Nexus partitioning with command line override method). Anyway, it won't really bring Nexus back to stock, so it misses the point for all those that want to have their bootloader relocked. Even with substituted splash1 to match locked Nexus, going into bootloader will show a version Nexus doesn't have. Flashing back Nexus HBOOT will return the "unlocked" sign, since it wouldn't be locked.
And it looks like Desire HBOOT is still within the smaller partition size and doesn't enlarge it to fit Nexus Eng SPL.
Click to expand...
Click to collapse
I checked, turns out mtd0 contains UART settings and the phone's CID... I can't see anything about logos and such.
Still, I think we could have a modified HBOOT with extended commands, making flashing splash0 and splash1 doable. And if we flash HBOOT back to the stock one through flash_image, it won't flash the splash screens again, so the splash change will stick. If you flash the one without a lock (splash0 I imagine) over splash1, and go back to stock HBOOT, won't it just stick?
This is just thinking here. Still, we need some kind of ENG HBOOT, or at least backport some functions of the ENG HBOOT to the SHIP one to allow splash screen flashing.
Also, the goal here is not necessarily to go back to stock and relock the bootloader in any way. It's mostly because the lock bugs me, and if there was a way to hide it, I'd gladly do it. I don't care about my bootloader not being the same anymore, or my phone not being stock I just like the clean look of the Nexus logo without the lock.
There is only one splash partition, there is no splash0 on those phones, AFAIK.
The thing is very simple: playing with HBOOT isn't safe - which means, if you flash a wrong one, your phone is done. Devs don't bother working on it, and rightfully so - when they have tasks of much higher priority, like G2's eMMC, they don't bother working on something that works already. I'm not going to be the one that tries flashing Desire HBOOT without certain knowledge, what will it do to Nexus - I don't live in Nexus-supported country. If you have a spare Nexus and are willing to exercise its warranty - flash Desire Eng HBOOT and see if it works.
I thought spcustom was basically splash1 with the lock, but turns out it's the screen that shows when you "fastboot oem unlock".
This is the bottom 768000 bytes of spcustom.img I found in a PASSIMG (most of you know that screen already though):
Maybe HBOOT actually adds the lock at the bottom of the screen. Or HBOOT composites the bottom part of spcustom and splash1. Can't say, I'm no engineer.
I actually know it's dangerous to do all this, and once again it's just a thinktank. I'm just trying to locate anything that could help more knowledgeable people to start working on this.
cmstlist said:
The new G2 permroot procedure seems to involve running some sort of kernel module which then allows you to reflash HBOOT with an engineering bootloader and get S-OFF. If you subsequently restore to stock using PC10IMG.zip, the stock bootloader relocks to S-ON.
Would this not be theoretically possible with the N1? There are Nexus One units out there with an engineering bootloader that can go to S-OFF without a permanent watermark. If the ENG HBOOT can be flashed from inside the OS, it could be a way to get S-OFF reversibly.
Click to expand...
Click to collapse
What it does is toggles power to the mmc and then force it to reinitialize as if suspended to disable the write-protect of the emmc. The N1 doesn't use emmc though so I think the protection of the hboot is done in some other way.
Rusty! said:
The ENG HBOOT on the Nexus One is larger than the SHIP one, so apparently it's a no go.
Click to expand...
Click to collapse
From what I've heard, the hboot partition on the retail N1s is actually the same size as the eng hboot. Open the eng hboot in a hex-editor and you'll see there is quite a lot of padding at the end and various other places. It might fit.
i read in general or q/a that someone did a warranty on there n1 and got it back a lock bootloader again, they had it unlocked. this was some ways back.. but there is a way to relock it, as there is some cases with ppl that have a unlock boot still get warranty and get it back with a lock boot...
Jack_R1 said:
There is only one splash partition, there is no splash0 on those phones, AFAIK.
The thing is very simple: playing with HBOOT isn't safe - which means, if you flash a wrong one, your phone is done. Devs don't bother working on it, and rightfully so - when they have tasks of much higher priority, like G2's eMMC, they don't bother working on something that works already. I'm not going to be the one that tries flashing Desire HBOOT without certain knowledge, what will it do to Nexus - I don't live in Nexus-supported country. If you have a spare Nexus and are willing to exercise its warranty - flash Desire Eng HBOOT and see if it works.
Click to expand...
Click to collapse
Yes, it isn't safe to muck around with HBOOT.
I bricked my desire by flashing a corrupt HBOOT patch, but it was my fault for not checking the md5.
And I would do it again. (But a checked file ;-))
Related
This has been in progress for a while. If you follow the G2 forums, then you'll know that there have been big problems with G2 phones that have been unlocked via unlock codes, with those unlocked phones then not being able to find a network at all.
It looks like the guys on #G2ROOT have cracked S-OFF for radio. This is *not* the same as the current S-OFF that we have from HBOOT. Apparently it should help to prevent semi-bricking via incorrect flashing of older ROMs.
The article in the Wiki explains all. Documentation about the procedures should be coming soon. We will of course have to make sure it's fine on the DZ too :
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
nice gives all those "bricked" g2's hope
Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.
DanWilson said:
Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.
Click to expand...
Click to collapse
I imagine it'll still be possible to reverse it. From a scan of the IRC logs (though of course I might have missed important stuff), it looks like you just need to write the correct data to the right area of a partition to get the radio S-OFF. So surely you can un-do that by writing the previous data ?
Documentation on this is now up, see http://forum.xda-developers.com/showthread.php?t=855764
Bear in mind that the instructions are for the G2 right now, so if you try this out on a DZ there's a high chance of a permanent brick ! But hopefully someone will sort out a verified method for the DZ soon
I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.
Lennyuk said:
I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.
Click to expand...
Click to collapse
But when an easier way to do it comes along (which is being worked on, I believe), a full S-OFF will be a lot safer, because then it won't be so easy to brick your phone by simply flashing an old RUU.
steviewevie said:
But when an easier way to do it comes along (which is being worked on, I believe), a full S-OFF will be a lot safer, because then it won't be so easy to brick your phone by simply flashing an old RUU.
Click to expand...
Click to collapse
people should not be flashing an old RUU anyway!
anyone who is silly enough to do that gets a brick for a reason.
Always either flash the latest ruu, or restore a nandroid of stock and flash an ota it offers, these are the safest ways.
You will get more bricks from people doing radio s-off than the s-off + ruu method gives.
Lennyuk said:
I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.
Click to expand...
Click to collapse
You're an ass-talker. You talk through your ass, blow hot air, and have no idea what you're talking about.
1) it is SAFER,
2) it is EASIER to come back from,
3) it is SAFER.
Why is it safer? Because it does NOT require writing the hboot or radio! You can blow p7 out and android will still boot, which means that you have the opportunity to fix it if something goes wrong.
A bad flash of the radio or hboot and you're dead.
For those who might not have seen it yet, there's now a fully documented procedure on how to do this to your DZ (and yes, it's been tested on the DZ too).
As has been said, this is a safer method to get S-OFF (letting you flash custom ROMs) than the previous method of putting on an engineering hboot.
See http://forum.xda-developers.com/showthread.php?t=857390
DanWilson said:
Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.
Click to expand...
Click to collapse
all i do for warrenty with modded phones is feed 12-20 volts ( from a wall adapter) into the battery contacts and tost the main board and bring it back as dead they send me a new one no questions asked cause the phone is dead...even did this with a htc ppc6800 that i smashed the screen in and thay warrenteyed it no prob....this is on bell in canada....
666
I was following your discussion on bricking because of flashing ruus but for some reason it doesn't apply to me. I had an Asian WWE 1.34.707.5 (shipped with my phone) then I flashed it with Asian WWE 1.34.707.3 RUU and it didn't brick my phone.
Hi all,
today i discovered something strange and i like to get your opinion on that:
I am not able to do s-off things in fastboot even if i have s-off!
Situation:
Phone: Desire Z
HBOOT: stock 0.85.0005
FW: 1.34..
Rooted: did root, supercid and s-off via gfree and verified via gfree_verify - even hboot showes up S-OFF
ROM: GingerVillain 1.5
Recovery: ClockworkMod 3.0.0.5
Problem:
First of all, i myself have no problem, but i started experimenting after a friend semi-bricked his desire z with same setup.
I did a nandroid backup and when i boot into hboot and do a 'fastboot flash recovery recovery.img' (with my nandroid recovery.img) i always get a remote: not allowed.
Now from my point of view this should only happen if I have a S-ON and should be impossible with S-OFF ?! Even using 'fastboot oem rebootRUU' does not change anything.
The thing that concerns me about that is: If something destroys both system and recovery, your pretty much screwed + bricked because hboot is not allowed to write to something other then cache and all of this basic stuff doesn't work:
- flash recovery with CW
- flash a complete zip
- flash an other hboot
- RUU
When I rooted my phone i have read everywhere that eng-hboots are not necessary any longer. But it appears that they are the only thing that helps and you have to install them as long as you have a working ROM.
Any thoughts on that issue / can you reproduce this / are fastboot actions logged anywhere?
You need a ENG. HBoot to use fastboot commands, doesn't matter if your s-off.
yeah, i came to the same conclusion..
is there any chance to flash a eng-hboot from a bricked 0.85.0005? i did some experimentation with a goldcard, but at least remote commands didn't change in behaviour..
I think being full-bricked when something goes wrong and not having an eng-hboot already installed is not an acceptable solution for most people here
DragonTEC said:
yeah, i came to the same conclusion..
is there any chance to flash a eng-hboot from a bricked 0.85.0005?
Click to expand...
Click to collapse
maybe thru a modified PC10IMG.zip
I think being full-bricked when something goes wrong and not having an eng-hboot already installed is not an acceptable solution for most people here
Click to expand...
Click to collapse
My thoughts exactly, its kind of a safety if you can't boot into android.
i'm not sure if a PC10IMG.zip will help at all.. my friend tried flashing both 1.34 and 1.72 RUU ROMs as PC10IMG and this didn't change anything.. in fact, the 1.72 even didn' install the new .00008 hbott, so i thing there is some heavy write protection in the hboot making it more or less useless..
what i can imagine that works is aa gokldcard with sppimg.zip, but i haven't yet found one for the desire z..
i have the feeling that this is a huge problem because with a short research i have found at least 3 threads of people having bricked their phone exactly this way and are now stuck.. some of the experts here might pay attention to this problem and in my opinion you should also consider removing the 'a eng-hboot is not needed, don't use it' advice from the rooting section of the wiki..
So what exactly is your problem.
You destroyed recovery and system?
If yes, and you used gfree to get Super-CID just install an PC10IMG that has a version higher or equal to the main version in you misc partition. And then do the whole downgrading, rooting, flashing recovery again.
If you are not Super-CID you might need a goldcard in addition if the CID of the phone is not supported by the PC10IMG that you whant to install.
have fun Guhl
It is almost impossible to brick this phone. The only possible way might be a failed copy of the eng-hboot and this is why the warning is and stays in the wiki.
Sent from my HTC Vision using XDA App
I thought so, too, but when flashing a newer original RUU using the PC10IMG.zip, the flash process runs okay, but after the restart nothing (still hangs in HTC screen, no new hboot) changes so apparently no changes are made..
So from my point of view the phone is more or less bricked.. i guess maybe some custome PC10IMG with an eng-hboot might change this, but i only found one for the G2 and wasn't able to find one for the DZ.. Thats why I thing that removing the 'UNNECESSARY' advice is justified (of course i don't want the warning advice that this can brick the phone to be removed)..
Well my phone was rooted my a friend's friend a while ago. Now I want to flash a new radio because my gps is acting up, but want to make sure that I have everything set-up correctly before I do so.What settings have to be "unlocked" or so in order to achieve this?
Any tips and things I should watch out for regarding flashing a new radio would be greatly appreciated.
hey the way you would make sure your s-off and all the things you need before bfore starting is to check h-boot. to do this turn your phone and hold the voume down and power button at the same time you will get to a white screen with androids on skateboards. there at the top you see your h-boot at the top it should say these 2 things 1 is h-boot s-off of course and the other important one is 2 your phone has a enganiering h-boot that lets your phone be able to flash different roms from different carrier brand roms like the desire rom on a g2 and vise versa and also radios. and things to watch out for is make sure your dowloadig a safe file before flashing and to make sure you download a backup of the radio that you have just in case something ffffffsss up if you know what i mean. just put the file on the root of your sdcard and get into your h-boot menu and the h-boot will pick up the file and you just press up to select upgrade and you should be fine. to check which or if it stuck you can check this in your menu ,settings , about phone and under your software info youll see baseband version and it should show the new radio you flashed. any questions feel free to ask my friend ok ;-)
As stated above, check your bootloader. If the first line ends in S-ON, you will need to obtain S-OFF using one of the guides (I suggest looking at the Wiki). If the first line ends in SHIP S-OFF, you have S-OFF through gfree. If the first line ends in ENG S-OFF, you have S-OFF through the engineering bootloader (and maybe gfree as well---you can check out the Wiki for an app on how verify whether or not gfree was used).
Regardless, if you have S-OFF through either method, you can flash a new radio. Unlike what the post above stated, you do not need the engineering HBOOT to flash a radio (or custom ROMs for that matter). The engineering HBOOT simply allows you to use fastboot to flash partitions on your phone while in the bootloader. If you do not have the engineering HBOOT, you can flash the radio through the PC10IMG.zip update method (there is a thread in the dev section).
Thanks for giving the full info i knew i forgot i did use gfree and it unlocked and all the good stuff i thought that included for you to be able to flash radios and any branded roms thanks
Sent from my HTC Vision using Tapatalk
Thanks guys! Yes, I checked and I have s-off. Great!
When I get on my pc I'll "thank" both your useful posts.
So which is the safest route to take to flash a radio? Through h-boot?
EDIT: Already flashed the radio, thanks guys.
Sent from my HTC Vision using XDA App
Download the radio zip bag.put it into SDcard root.rename it to "PC10IMG.zip".then goto h-boot and g2 will auto flash it.
No problem I just had to flash back to the stock radio wasn't getting the best service with the new updated desire radio glad everything was figured out
Sent from my HTC Vision using Tapatalk
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
UPDATE 8/1/2011: This has been updated to now block normal hboot flashing to make it much safer. It's still wise to not arbitrarily flash things but you should rest a little more at ease now.
Thread update (not a new version):
Here is the commands to re-flash hboot after installing this:
"fastboot oem mw 8d08ac54 1 31302E30"
"fastboot flash hboot whateverhbootfile.nb0"
where whateverhbootfile.nb0 is in your path, you can get this file by unzipping the PG05IMG.zip with a hboot in it
(BE CAREFUL WITH THIS, YOUR PHONE WILL FLASH TETRIS.EXE AS A BOOTLOADER IF YOU ASK IT TO)
Enjoy.
Sweet thanks
Sent from my ADR6400L using XDA Premium App
Thank you sir, I shall try this soon.
This is not newer than the ENG, its actually the same version number. The ENG one came from a 1.12.605.6 eng ruu (same as shipping)
Will this block hboot flashing like the alpharevx one (please say yes)
Shadowmite said:
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
Enjoy.
Click to expand...
Click to collapse
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Shadowmite said:
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Click to expand...
Click to collapse
I ended up not releasing the older one, as I had both (im not sure if joshua was given both or not).
Once you add blocking hboot flash (artificially high version number does it i think??) would it be ok to place in my guide until (if/when) yall release a package? (I intend to remove mine once a reliable "auto" is out).
Flashed for fun and it works great.
Having another method of root may not mean much to Tbolt owners now but it will once devices start shipping with GB.
Great to have you guys working on this.
so this a a way to root in the future for GB owners? just want to make sure so i dont flash if i dont need to because i am already rooted
Shadowmite said:
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Click to expand...
Click to collapse
excellent! i personally would love a permanent s-off patch. ill be watching this thread,thank you kind sir.
thanks,Shadowmite
Shadowmite said:
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
Enjoy.
Click to expand...
Click to collapse
Hey,
Might you guys post your IDB of this hboot? or send it to me via PM? or somehow. Id love to see the breakdown of the file you guys reversed.
and what patches. Thanks!
Thanks shadowmite. I followed your work way back in the 6600 days...
Sent from my ADR6400L using Tapatalk
running it now,no issues. used it to flash a recovery,and change my radios. also verified it has the same available fastboot commands.
feel free let me know if you need any kind of feedback,or help with testing. id be more thaN happy to help test a permanent patch
Ok, updated main post with new updated hboot. Now patched to block normal hboot flashes which should make it a lot safer. To test, flash the update, then try flashing it again. The second one should not take.
yes! thank you kind sir. so,if im understanding correctly,it will prevent the flash of any other hboot,including the original engineering one?
downloaded and about to flash
scotty1223 said:
yes! thank you kind sir. so,if im understanding correctly,it will prevent the flash of any other hboot,including the original engineering one?
downloaded and about to flash
Click to expand...
Click to collapse
Correct. I figure eventually someone might need to flash back to a original and ill eventually toss up instructions how to do this. For now, this should block everything we've seen for the device to date.
Is revolutionary working on root for the thunderbolt? Will it give us true s-off?
from the first post,no it will not give us true s-off. im running it now,tried flashing the stock s-on hboot and the old eng hboot and it blocked them both
next question: if one installed a stock recovery,and accepted an OTA... would this prevent hboot from being overwritten there as well?
Yes it should always block hboot unless they do something purposeful to overcome the block method. I'll post a command in the first post sometime next week that will allow you to overwrite hboot should you want to.
HAHAHAHAHAHAHAHAHAHAHAHAHA ohhhhhh sooo late.....I'm surprised that they even bothered with our phone!
http://www.xda-developers.com/andro...cha-aria-droid-incredible-status-t-mobile-g2/
http://www.htcdev.com/bootloader/
It's nice of them though!
It's still a big deal. Even though AlphaRevX/Revolutionary have been pretty reliable, there's always a risk of bricking the device when using them. It also shows they were serious about their commitment to no longer lock bootloaders and increases the chances of me buying an HTC phone in the future.
Oh I would totally buy another HTC phone...very well built phones! And I did say that it was nice of them....I am glad that they are following through with their word. I just am pretty surprised that they actually bothered with the Aria....
does this affect S-OFF / S-On NAND-lock etc?
I believe the phone will still be S-ON that's why revolutionary.io is still the best bet
Has anyone tried this yet?
Sent from my Liberty using XDA App
I tried this out on my spare Aria. After unlocking it, the phone still says "S-ON" on the HBOOT screen -- HOWEVER -- I was able to install CWM using this method, and after installing a rooted ROM, I was able to write to the system partition while booted. In other words, even though it still says S-ON, it appears to actually be S-OFF.
I think that with HTCdev bootloader unlock you can't flash radios or hboots.
You can write to the system partition, root, change rom, flash recovery but it's not S-OFF.
drumist said:
It's still a big deal. Even though AlphaRevX/Revolutionary have been pretty reliable, there's always a risk of bricking the device when using them.
Click to expand...
Click to collapse
Bull****. There is as much risk using HTC's unlock scheme as there is using Revolutionary.
Further, HTC's unlock scheme is gimped - not flashing custom roms completely in CWM, you need to use fastboot to flash the boot image. The radio partition is locked, and it's definitely not S-OFF.
Revolutionary is the far better way to go, no matter how you look at it.
attn1 said:
Further, HTC's unlock scheme is gimped - not flashing custom roms completely in CWM, you need to use fastboot to flash the boot image.
Click to expand...
Click to collapse
Are you sure about that? I have two Arias, one with S-OFF via AlphaRevX and another that I upgraded to HBOOT 1.03 and unlocked using HTC's tool. Using your build of CWM 5.0.2.3 on both. I installed CM7 on both phones and I don't notice any problems with the phone that was unlocked with HTC's tool.
I did a nandroid backup on both phones, and the boot.img from both backups have an identical MD5 hash. Seems like CWM is able to flash the boot image just fine. Am I missing something?
You cannot fash splash screen with HTCDev method. It is not truely S-Off.
Sent from my HTC ThunderBolt using XDA Premium App
oneders65 said:
You cannot fash splash screen with HTCDev method. It is not truely S-Off.
Click to expand...
Click to collapse
My phone shows a CM7 splash screen.
Now I'm wondering, does it matter that I had S-OFF on this phone at one point in time (via AlphaRevX) before returning it to HBOOT 1.02 w/ S-ON using this method? I'm wondering if the reason these things are still writable on my device is because the process of "reverting" to HBOOT 1.02 didn't actually remove S-OFF from my device (even though it says S-ON on the HBOOT screen).
---------- Post added at 06:03 AM ---------- Previous post was at 05:33 AM ----------
If I re-lock the phone (fastboot oem lock), then I definitely lose the ability to write to the system partition while booted, so I don't think that was it. I'm definitely confused.
drumist said:
Are you sure about that? I have two Arias, one with S-OFF via AlphaRevX and another that I upgraded to HBOOT 1.03 and unlocked using HTC's tool. Using your build of CWM 5.0.2.3 on both. I installed CM7 on both phones and I don't notice any problems with the phone that was unlocked with HTC's tool.
I did a nandroid backup on both phones, and the boot.img from both backups have an identical MD5 hash. Seems like CWM is able to flash the boot image just fine. Am I missing something?
Click to expand...
Click to collapse
Did you already have CM7 on it? Wipe data and flash a sense ROM and see what happens.
attn1 said:
Did you already have CM7 on it? Wipe data and flash a sense ROM and see what happens.
Click to expand...
Click to collapse
I had run the AT&T 2.2.2 RUU on the device before I upgraded to the 1.03 HBOOT, so it had the boot image from the 2.2.2 RUU on it before I did the HTC unlock.
CM7, CM6, and Liberated 2.2.2 all work fine. Boots, shows appropriate splash screen, and as far as I can tell there aren't any issues although I haven't really used it much beyond just booting it up and testing a few things.
drumist said:
I had run the AT&T 2.2.2 RUU on the device before I upgraded to the 1.03 HBOOT, so it had the boot image from the 2.2.2 RUU on it before I did the HTC unlock.
CM7, CM6, and Liberated 2.2.2 all work fine. Boots, shows appropriate splash screen, and as far as I can tell there aren't any issues although I haven't really used it much beyond just booting it up and testing a few things.
Click to expand...
Click to collapse
Splash screen, not boot animation.
Displays before the rom or recovery boots.
Default splash screen is white with green HTC letters...
I'm gonna switch my phone over to this and see if I lose any functionality...
Edit: Well, can't flash splash screens.. but I can change stuff in system and it stays with a reboot, even though it says S-ON..
drumist said:
I had run the AT&T 2.2.2 RUU on the device before I upgraded to the 1.03 HBOOT, so it had the boot image from the 2.2.2 RUU on it before I did the HTC unlock.
CM7, CM6, and Liberated 2.2.2 all work fine. Boots, shows appropriate splash screen, and as far as I can tell there aren't any issues although I haven't really used it much beyond just booting it up and testing a few things.
Click to expand...
Click to collapse
I think you mean boot animation and not splash screen. The splash screen is the white screen with HTC that displays before the CM7 boot animation begins.
Your Hboot says S-ON or S-OFF?
attn1 said:
I think you mean boot animation and not splash screen. The splash screen is the white screen with HTC that displays before the CM7 boot animation begins.
Your Hboot says S-ON or S-OFF?
Click to expand...
Click to collapse
Sorry, yes. I have not tried to replace the splash screen.
The HBOOT says S-ON but has the text "unlocked" at the top line (after using the HTCdev unlock).
drumist said:
Sorry, yes. I have not tried to replace the splash screen.
The HBOOT says S-ON but has the text "unlocked" at the top line (after using the HTCdev unlock).
Click to expand...
Click to collapse
Well I just had to test it. You're correct. On Aria, the unlocked bootloader, while not complete S-OFF, allows full rom flashing from recovery. Awesome. This is all most users would need. It doesn't work as well on Inspire.
I still think the revolutionary way is more complete and *easier*.