Related
Hi everyone,
My phone is magic (TIM).After I flashed the new radio(6.35.10.18) and SPL(1.76.2007), I don't know why my ENG S turned ON automatically, and I can't solve it (even if I reflash the SPL in recovery).
Also there is a more serious problem, After I flashed any new ROM such as SuperHero, Eclaire, Villian,Robomix v0.1 and rebooted it, it keeps frozen at the first boot screen(splash screen). At last I tried to use a CM ROM, it can be started finally!
I'm very confused, the CM ROM is Android 1.5, so does it mean that I can only use the ROM with 1.5 for now? Cannot be!^%%$#@@!%$...
You used a CM rom with a 6.35 radio and 1.76 spl? And can't use the roms that require the new radio and spl? I'm pretty sure you DIDNT FLASH the new radio and spl.
Yes, I did! I pressed BACK+POWER to boot into fastboot model, it displays 1.76 and 6.35 with ENG S-ON!
That's so strange that you can use a CM rom with that radio and SPL. Switching to S-OFF won't make much of a difference for this situation (correct me if I'm wrong)
Did you flash a new recovery when you updated your radiospl
Sigh... Wrong forum... But this is not that common of a problem...
http://forum.xda-developers.com/showthread.php?t=643291
KAwAtA said:
That's so strange that you can use a CM rom with that radio and SPL. Switching to S-OFF won't make much of a difference for this situation (correct me if I'm wrong)
Did you flash a new recovery when you updated your radiospl
Click to expand...
Click to collapse
er...it's CursorSense32A-1.2.6.1 and recovery 1.6.2(the hero version)
Wow, you're using cursor sense? that would've been nicer to know rather than CyanogenMod
xaueious said:
Sigh... Wrong forum... But this is not that common of a problem...
http://forum.xda-developers.com/showthread.php?t=643291
Click to expand...
Click to collapse
I don't get it, how does that help his problem? I know he wants to change to S-OFF but the main problem is his roms don't load up. But like the other guy, I notice that they can only use CursorSense soo im not sure
Show me step by step on how you flashed the ENG 1.76.2007 SPL (although this shouldnt affect it at all)
pyee0124 said:
You should still be able to flash custom ROMS regardless of S-ON. One of the other things you should try is formatting your SD card again.. Try a full FAT32, then try partitioning afterwards. I found that I could only boot Ahmgsk with FAT32/Swap/Ext2.
Click to expand...
Click to collapse
Do you have any swap/ext partitions?
First I flashed Engineering SPL 1.33.2010 in recovery, and reboot into fastboot, I saw I'm ENG S-OFF at that moment, so I flashed new SPL and radio then. Maybe the problem comes with the old incompatible recovery, after I reboot my phone this time, it beame bootlooping(see my thread posted:http://forum.xda-developers.com/showthread.php?t=658220), I was almost thought it was bricked! But luckily the phone fixed itself(I thought), I could enter fastboot, at that time I noticed that my ENG changed S-ON.
That's my whole story, hope it can help you to help me fix the problem.
I have a ext3 partition but in order to protect my TF card I didn't partition a swap
Sorry man, hope someone else can help you. I just dont even understand how you got an S-ON SPL if you followed the thread ppl provided in the other one cause an ENG SPL was provided. Dunno how you got perfect, and I am completely not sure why you can't flash other new radio Roms. Hopefully someone else can help
It doesn't matter bro, I'll find another way to solve it, still thank you!
Damn it do I have to spell out everything? I even linked to the thread. All you had to do was read -_-
1)
You just need to run the following command to get S-OFF again:
fastboot oem enableqxdm 0
That was the title of the thread.
2)
Dude you sound clueless about your ROMs. Cyanogenmod has been 1.6 since forever, but there's no way that run actually boots properly with new radio. Plus Cyanogenmod doesn't even boot on 32A Magics without a kernel port, which I doubt you flashed.
Do yourself a favor and get your lazy ass to Cyanogenmod irc and ask there. It isn't just a matter of getting your phone working. If you are flashing ROMs you need to know what the hell's going on.
http://www.cyanogenmod.com/irc
xaueious said:
Damn it do I have to spell out everything? I even linked to the thread. All you had to do was read -_-
1)
You just need to run the following command to get S-OFF again:
fastboot oem enableqxdm 0
That was the title of the thread.
2)
Dude you sound clueless about your ROMs. Cyanogenmod has been 1.6 since forever, but there's no way that run actually boots properly with new radio. Plus Cyanogenmod doesn't even boot on 32A Magics without a kernel port, which I doubt you flashed.
Do yourself a favor and get your lazy ass to Cyanogenmod irc and ask there. It isn't just a matter of getting your phone working. If you are flashing ROMs you need to know what the hell's going on.
http://www.cyanogenmod.com/irc
Click to expand...
Click to collapse
Um he made an error and he said it was CursorSense, not CM.
Second, doesn't fastboot oem enableqxdm 0 fix sd card problems? I've never heard of that turning S to OFF, interesting.......
xaueious said:
fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.
Click to expand...
Click to collapse
and after reading that thread, I read that you posted this command for sd card problems. Please point out where He is supposed to read, I'm either blind or you're wrong (Seeing as how you missed his CursorSense mistake and stating that the title of the other thread is fastboot oem enableqxdm 0, lol, I don't think I'm blind)
Sorry if I sound like a douchebag here but seriously, you although this guy posted in the wrong section *sigh*, if you wanna be a douche, at least read over his problems properly. You're not helping at all right now and again, he made a mistake about cyanogenmod which was already cleared up and you failed to read that. You should really, get your lazy ass to read this thread more clearly (LOL I don't evne know if that made sense, its 3am and since u live in toronto, oh same time there i assume!) But yeah, if you wanna be a douche, you gotta at least be right or something. But whatever, I just find it totally ridiculous how you're flaming this guy. But if I'm wrong, then go for it and flame me! I haven't seen anything helpful from you here
KAwAtA said:
Second, doesn't fastboot oem enableqxdm 0 fix sd card problems? I've never heard of that turning S to OFF, interesting.......
Click to expand...
Click to collapse
I think so too, it's a forum to discuss about technic, not complain.
I have the same situation as you, the ENG SPL changed from S-OFF to S-ON.
Also, can't boot any 2.0/2.1 roms.
I did a lot of flash and try to fix the SPL to S-OFF, but no luck. Such as:
Flash ENG SPL 1.76.2007 again and again;
Flash back to 3.22 radio and 1.33 SPL, then flash the 1.33 ENG SPL;
Flash the device from 3.22 radio and 1.33 SP to 6.35 radio and 1.76 SPL;
A month after, I noticed that my phone can't turn on the Bluetooth. The Bluetooth only can be turned on while first time I boot up the phone, when you disable it and try to enable again, no go...
I send the phone back to HTC for repair, and HTC said that my motherboard was damaged...
I notice more and more people have the same issue as me (and you), I am afraid that some of the 2.1 rom might have some wrong drivers that make my phone go wrong.. (because I didn't flash any rom, I only restart my phone while my phone can't boot and SPL changed to S-ON....)
Be careful everyone, hope my finding is wrong..
I've seen the oem command fix the S-ON to S-OFF before, which is why I posted it. Sd card disabling and s-on happen together in those cases.
Come to think of it, the time I got S-ON too was with battery pull and hard rebooting. Maybe S-ON is activated with memory debugging as a flash corruption protection scheme.
littlestrong try checking the integrity of your file system and reflashing your ROM entirely. Sometimes flash just wears out.
There's also the issue of flashing the radio and spl from recovery, as sometimes it causes issues. The best way is to do it with fastboot. I know your SPL is locked so you can't do that though. Your best bet was the oem command with 1.76 HBOOT versions. Other than that it would be playing with serial cables and JTAG.
So you mean mabe the currupted ROM makes S-ON, and my system files have been destoried. But I've flashed many ROMs, none of them works. I can only do is to run the command "fastboot erase system -w" before flash to give my phone a most CLEAN status.
Second, can oem commands flash SPL and recovery? May you tell me how?
nabor said:
So you mean mabe the currupted ROM makes S-ON, and my system files have been destoried. But I've flashed many ROMs, none of them works. I can only do is to run the command "fastboot erase system -w" before flash to give my phone a most CLEAN status.
Second, can oem commands flash SPL and recovery? May you tell me how?
Click to expand...
Click to collapse
I've never heard of "oem" commands flashing spl/radio/rec. But you can give the command he gave you a try
The best way would be to use fastboot commands. I don't think a corrupted rom makes it S-ON. I got S-OFF as soon as I flashed my eng spl
O.K. thanks. Got it, seems no solutions yet. I think I should learn the kernel first, it is fundamentally to know how a ROM, a system works!
And sorry for my poor English, I fund I missed a "y" above in "mabe"
can somebody tell me, how in this case I can install a new SPL, or recovery?
Mod. edit: not dev related, moved to general
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 ;-))
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)..
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.
Hey im working on my friends inc and i need help
He has
Locked s-on
hboot - 1.02.0000
radio 2.15.10.12.20
I used the Ruu on the HTC dev site and it only took like 1 minute. They say it goes to 4.08.405.2 , but afterwards i check and it's still on 4.08.405.15
I go to fastboot and type "fastboot oem get identifier token" like it says on htcdev
and i get out
...INFO[ERR] Command error !!!
fastboot devices worked though.
Can someone help me out fast?
Thanks,
I think it might be that that Ruu downgraded me to 1.02 hboot from 1.07
...
is there a way for me to get the 1.07 hboot back .. it looks like i never need to run their ruu and now i'm set back
and pissed, and angry.
Any help would be greatly apreciated.
Why can i no has unlock token? UGhh HALP
RoryHe said:
I think it might be that that Ruu downgraded me to 1.02 hboot from 1.07
...
is there a way for me to get the 1.07 hboot back .. it looks like i never need to run their ruu and now i'm set back
and pissed, and angry.
Any help would be greatly apreciated.
Why can i no has unlock token? UGhh HALP
Click to expand...
Click to collapse
Yes flash this ruu thru hboot http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip. It must be named exactly PB31IMG.zip and be on the root of your sdcard in no folders. However if the last ruu you did only took a second, chances are it didnt flash right anyways. Also are you s-off? You can only downgrade hboot versions if you are. But really it shoukdbt natter, both 1.02 and 1.07 are unlockable.
cmlusco said:
Yes flash this ruu thru hboot http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip. It must be named exactly PB31IMG.zip and be on the root of your sdcard in no folders. However if the last ruu you did only took a second, chances are it didnt flash right anyways. Also are you s-off? You can only downgrade hboot versions if you are. But really it shoukdbt natter, both 1.02 and 1.07 are unlockable.
Click to expand...
Click to collapse
Not s off, I'll try that thanks. Idk the phone was on [email protected] and I tried to go to 4.08.605.2 an upgrade right. Didn't work and won't let me get I'd token.
Uh heh
It was either a driver problem
or
i typed in the command wrong
it's suppose to be
"fastboot oem get_identifier_token"
/facepalm took me so much time on this well i hope if someone gets the same thing they can see this and remember to type the command in right