yashsingh1/xdaforums huggingface dataset:
[myTouch 4G Android Development] :
You can download it but you wont have calling, texting, mms or any kind of service. I think they are looking into a fix
[myTouch 4G Android Development] zFr3eak:
pm me with gtalk address.
[myTouch 4G Android Development] zFr3eak:
ok guys,

we made a deal. cause i just work on get the device problems done and we think i should help bryan on bugfixing we decided to work now 2 or 3 weeks completly on the rom. it mean that we will not release a update. we will work so long on it to get a daily driver for you and then release a big update. i think this is the best way.

please dont see this that we are not able to make constantly updates or we want to hold the project on. it will just save you time with flashing small updates every 5 days. The project is still completly supported and we work evrey free min on it. please keep the threads allive, we will need for each device a few testers for resizing things and yeah that's it. for sure i will constantly write here what we do, what we got, what we will do and things like that. see it to a step to a daily driver.

Thats all from sbryan and mine side.

and i also want to tell you that we have a new team member. so say hello to dansta34. he will be one who help us a lot with resizing he allready got many widgets done.

Cheers
[myTouch 4G Android Development] Useless_Alias:
Good news. Update is appreciated. Ive head off flashing the latest after hearing the radios weren't working. Get that working and I'll be active with it. Any news on getting T-Mo wifi calling app working?

-Now I reside in your browser cache licking your cookies before you use them again. Don't forget to thank me for that.-
[myTouch 4G Android Development] zFr3eak:
it wasnt a radio problem. is allready fixt.
[myTouch 4G Android Development] Undeadk9:
I might need to try this ROM
[myTouch 4G Android Development] bigwillyg:
Hmmmm... This thread has been very quiet lately. Any updates?
[myTouch 4G Android Development] zFr3eak:
well we still work on resizing and those things. we allready got much done and figured many things out :P
[myTouch 4G Android Development] Undeadk9:
The Rom is promising but still needs work. But for a tablet OS to be running on glacier in general is awesome.
[myTouch 4G Android Development] zFr3eak:
Conclusion

After hours and hours of hard work, the BeatMod team has decided to put this (Flyer) project on hold. We will be focusing more on better projects (like Bliss 35). I hope you understand that we aren't letting this project go, just setting it aside due to it's complications. Thanks

-zFr3eak
[Thunderbolt Android Development] Shadowmite:
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.
[Thunderbolt Android Development] 760hacker:
Sweet thanks
[Thunderbolt Android Development] whewstoosae:
Thank you sir, I shall try this soon.
[Thunderbolt Android Development] jcase:
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)
[Thunderbolt Android Development] Shadowmite:
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.
[Thunderbolt Android Development] jcase:
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).
[Thunderbolt Android Development] scuccia:
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.
[Thunderbolt Android Development] Pithism:
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
[Thunderbolt Android Development] scotty1223:
excellent! i personally would love a permanent s-off patch. ill be watching this thread,thank you kind sir. :cool:
[Thunderbolt Android Development] topsite:
thanks,Shadowmite
[Thunderbolt Android Development] rhcp011235:
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!
[Thunderbolt Android Development] nemanracing:
Thanks shadowmite. I followed your work way back in the 6600 days...
[Thunderbolt Android Development] scotty1223:
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 :D
[Thunderbolt Android Development] Shadowmite:
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.
[Thunderbolt Android Development] scotty1223:
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 :cool:
[Thunderbolt Android Development] Shadowmite:
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.
[Thunderbolt Android Development] nemesys504:
Is revolutionary working on root for the thunderbolt? Will it give us true s-off?
[Thunderbolt Android Development] scotty1223:
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 :D
[Thunderbolt Android Development] scotty1223:
next question: if one installed a stock recovery,and accepted an OTA... would this prevent hboot from being overwritten there as well?
[Thunderbolt Android Development] Shadowmite:
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.
[Thunderbolt Android Development] scotty1223:
that totally rocks. you have made this device soooo much safer for all the new rooters. hopefully jcase swaps it out for the old eng hboot in the exploits file(and maybe provides an mr2 upgrade) until your root comes out. new rooters will then have it like it or not :D

thanks again for the info and the fast response :cool:
[Thunderbolt Android Development] scotty1223:
for those wondering if you should flash this,yes,you should.

ive tested it as extensively as i can and its working great. ive flashed other hboots,and whole ruus and it always blocks them. i even rolled back to 1.12.605.6 and accepted the OTA to 1.70.605.0. :eek:
[Thunderbolt Android Development] JBO1018:
So you took the MR2 OTA and it installed everything but it didn't let it flash the s-on hboot? That is awesome if that's the case. I will definitely be switching to this.

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] scotty1223:
I applied the 1.70.605.0 pg05img in its entirety in hboot,and this blocked the hboot flash.

I applied the 1.12.605.6 pg05img in its entirety and this blocked the hboot flash. I then let it ota to 1.70.605.0 and still s-off. :)
[Thunderbolt Android Development] jcase:
Hit me on irc if you have time.
[Thunderbolt Android Development] JBO1018:
That is great. So how do I apply this? Just a CWM .zip?

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] scotty1223:
in hboot,just like a radio,if you have ever done that.

1)download

2) take the PG05IMG out of the zip you downloaded

3)move it to sd card

4)boot to hboot,select yest to update

5)reboot and delete PG05IMG from sd card
[Thunderbolt Android Development] JBO1018:
Oh yeah done it plenty of times just wanted to be sure cuz messing up your hboot is baaaad news lol. Thanks!

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] perfoliate:
Can someone post an md5sum for this? Thanks in advance :)
[Thunderbolt Android Development] scotty1223:
edited for bein a jackass :)

ca29b7fc8b0f96d54c378c18a5d0b26e is the md5 for the file inside the file,the one that you will actually flash. if you check the md5 of the intire download it will be different.
[Thunderbolt Android Development] perfoliate:
Oh thanks, I hadn't downloaded it yet, i was just thinking proactively about it before I downloaded and flashed it. Didnt want to get a bad flash on this one, much thanks :)
[Thunderbolt Android Development] scotty1223:
No prollem... you are good to be cautious. The bootloader is indeed one you don't want to eff up! :eek:
[Thunderbolt Android Development] snicklet:
You're still a jagg for hammering away at the dude for asking a simple question but instead you had try and make him look stupid for asking.
[Thunderbolt Android Development] scotty1223:
youre right,it hadnt occured maybe he hadnt downloaded yet. im just soooo used to 95% of the people in this forum wanting to be spoonfed rather than search a lil for an answer.

again,perfoliate,sorry for the harshness of the first response(and i should have included this apology in the 2nd one)
[Thunderbolt Android Development] perfoliate:
It's all good, it did come off a bit harsh but eh, who cares I've got thick skin. No need for me to get all worked up like some. I felt redeemed after your second response scotty1223. Things are just a little edgy around these parts, and people take comments too seriously its easy to misjudge someones intentions through text. Thanks again op for this and the help.;)
[Thunderbolt Android Development] scotty1223:
cool,did you flash it yet? :)
[Thunderbolt Android Development] perfoliate:
Yep and everything went as planned...:D
[Thunderbolt Android Development] EEdaesung:
Great win.

tbolt ^_^_^
[Thunderbolt Android Development] JBO1018:
Nevermind sorry.

Sent from my HTC Thunderbolt
[Thunderbolt Android Development] Shadowmite:
Note: first post updated with commands to re-flash hboot if you want to return to stock or another...
[Thunderbolt Android Development] mbaker5408:
Not sure how to go about this but I vote for STICKY here....
[Thunderbolt Android Development] marcogiudice:
Has anyone successfully re flash back to the original eng hboot that jcase give to us using shadowmite's fastboot cmds. I tired everything and it would fail on the 2nd c.d.. Any ideas? Shadowmite can you please post any alternative way to get the first bootloader that we all had before flashing your patch. For peace of mine thanks.. Or am I stuck with permanent unlocked bootloader
[Thunderbolt Android Development] marcogiudice:
I'm an asshole an desperately need help. I flashed wrong hboot and now I'm stuck.. it would only stay in bootloader with s on and security warning.. finally I got the downgrade pg05.img to work from root process. And can't flash no other stock ruu's. Can soneone please help me! email marcogiudice79@gmail.com please... Help a fellow brother in need
[Thunderbolt Android Development] scotty1223:
i did it and it worked fine. whaT hboot did you try and use? id reccomend using the hbooteng.nb0 from the exploits file when you rooted.

i did an extemely noob-oriented writeup on android forums check it out if you have used ADB to root,but are not that familiar with it,or with running fastboot commands. if theres a demand,i guess i could edit this post and copy/paste the whole thing here.

also heres what you should see when you do this(red are my inputs):

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Scott>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HT126S005970 device

C:\Users\Scott>[COLOR="red"]cd c:\android-sdk-windows\flashables[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\android-sdk-windows\flashables>[COLOR="red"]fastboot devices[/COLOR]
HT126S005970 fastboot

c:\android-sdk-windows\flashables>[COLOR="red"]fastboot oem mw 8d08ac54 1 31302E30[/COLOR]
...
OKAY [ 0.006s]
finished. total time: 0.006s

c:\android-sdk-windows\flashables>[COLOR="red"]fastboot flash hboot hbooteng.nb0[/COLOR]
sending 'hboot' (1024 KB)...
OKAY [ 0.183s]
writing 'hboot'...
OKAY [ 0.219s]
finished. total time: 0.403s

c:\android-sdk-windows\flashables>

make sure youre running the commands in fastoot

make sure you have put hbooteng.nb0 into whatever directory you push files from and changed to that directory.

do you need to return to stock,or just making sure it will work?

EDIT i wont pretend i have a clue how this actually works,but as an afterthot,keep in mind that fastboot flashing may be the only way that we can overwrite this if we want it to continue doing the excellent job its doing. ive OTAed,and flashed all kinds of stuff over it and it always blocks it. the commands may seem a little confusing,but altering things so that it could be overwritten in another manner may make it not as bulletproof when it comes to blocking other hboot flashing.dont worry,well help you get back to the original s-off eng bootloader if you need to(tho i personally like being "stuck" with the permanent one :D)
[Thunderbolt Android Development] scotty1223:
since you have a SECURITY WARNING i assume you have an unbootable phone?

no offense,but preventing this situation is prolly the main reason to HAVE the permanent s-off,im not sure HOW you goofed it up. i hope others at least gain some knowledge from this post that you should not be messing with bootloaders without good reason and without knowing what youre doing.

have you tried to flash the MR2 RUU ? if so,im afraid,my friend,that you might stuck until new RUUs come out.

hopefully shadowmite or someone at andirc chat can help you,as im not sure what you can do with an s-on bootloader and no working rom.
[Thunderbolt Android Development] marcogiudice:
shadowmite lead me to get the latest ota and extract the rom.zip from it and rename it... so now im on stock ota 1.70.xxx.x with s-on still... now my problem is that when i go to do the root process when i get to the step that i downgrade the ruu, in hboot i get the main version is older or newer, cant remember.... but anyway so what should i do from here???? please help my dum ass out :rolleyes:
[Thunderbolt Android Development] scotty1223:
i replied to your PM,please put further questions at the end of the root thread,myself and others will help you there.

lets try and keep this thread for the discussion and info about this bootloader.

glad you got your phone up and running. :)
[Thunderbolt Android Development] marcogiudice:
Sorry ill keep it in here.. anyway I re downloaded the exploit and checked the md5sum both with computer program and while going thru the root process with adb and they all match and the misc.img is being pushed correctly and I'm still getting version is older in hboot. Now I'm stuck on this crappy 1.70.xxx.x. please tell there's another way around it.
[Thunderbolt Android Development] marcogiudice:
I just want to give a big thanks to shadowmite and scotty1223

Shadowmite for his work and this patched bootloader for our thunderbolts and for him informing me to pull the rom.zip from the 1.70.605.0 ruu to get me back and running from a security warning locked bootloader... thank you very much!

Then SCOTTY1223 for leading me the rest of way and being a real team player and gentleman and scholar... willing to test and actually helping people out on this forum without the belittlement and ignorance i tend to see around this forum... everyone give a round of applause to both gentleman!

moral of story is, even as bad as i effed up i was able to pull out and get back to ROOTED staus.... BY

1. pulling rom.zip from latest ota as of today 8/11 "RUU 1.70.605.0"

which will get to back to hboot 1.04.0000 and stock firmware 1.70.605.0

2.then processing back to the root process from step one http://xdaforums.com/showthread.php?t=996616

And without incident you should make it thru root process and be back to normal...

*** for me i kept getting main version is older when doing the downgrade ruu**

the cause of this is the misc.img isnt being pushed correctly thru adb or somehow getting corrupt..

so for me, the fix was deleting all old exploits .img from the my android sdk dir and re downloading them and adding them back to my sdk dir then changing usb port and i pushed it multiply times for good measures and finally it let me downgrade then continue on with root process and the next steps will get you s-off with hbooteng.nb0 and MR2 ruu

SO even after bad flash of a s-on hboot you can get back to normal!.... thanks again SHADOWMITE and big big thanks to you SCOTTY1223

p.s. i hope this will teach and guide everyone... i made the mistake for yous and made it out ok due to good teachers in this forum
[Thunderbolt Android Development] scotty1223:
Awesome :cool: glad you got everything worked out and back to normal. :)
[Thunderbolt Android Development] marcogiudice:
yes thanks to you... truthfully i deleted everything in sdk and redownloaded and started clean and added new exploits to dir and changed ports and finally got hbooteng.nb0 md5sum to check out in adb.. all your recommendations..

so thanks agains to thank you a million :)
[Thunderbolt Android Development] a1exus:
how can I see what HBOOT version I have now? where can I see it?
[Thunderbolt Android Development] scotty1223:
Turn your phone off,power on while holding volume down. This is hboot. The version number,etc. Is at the top. :)
[Thunderbolt Android Development] scotty1223:
Are there any differences between this patched hboot and the version that comes with the new revolutionary root method?
[Thunderbolt Android Development] marcogiudice:
good question, id like to know the same?
[Thunderbolt Android Development] a1exus:
looks like I already have latest 1.04...
[Thunderbolt Android Development] Veridor:
I was wondering the same. I rooted using the old method, but am conflicted as to whether to manually flash this hboot, or re-root using the revolutionary method.
[Thunderbolt Android Development] Shadowmite:
they are the same other than a version number change. no need to switch.
[Thunderbolt Android Development] scotty1223:
shadowmite,thanks for the info,thats the answer i expected. i did unroot and reroot with the new revolutionary tool(in my usual fasion,in case folks had questions) and it was truly easy. you guys have done an amazing,fantastic job. thanks for coming up with it.

veridor,since youre allready rooted,just flash this.

a1exus im confused... do you have the permanent patched 1.04.0000? if so than youre good,no need to do anything. if youre rooted and s-off with the old eng bootloader(1.04.2000) or the original non permanent,patched 1.04.0000,then id flash this :)
[Thunderbolt Android Development] Veridor:
Done. Thanks for posting this.
[Thunderbolt Android Development] a1exus:
i still dont understand

what this is?/whats that for?

do i need to upgrade my existing 1.04?
[Thunderbolt Android Development] scotty1223:
did you read the whole thread? :confused: i think its pretty straightforward what the advantages are.

this is an hboot that blocks other hboots from being flashed/the purpose is to prevent accidental overwriting from flashing RUUs,or accepting OTAs. it will always preserve your "S-OFF" status.

again,there are 3 different "1.04" hboots you can have. just saying you have a "1.04" does not tell me what you have.

how about this: if you have

not

allready flashed the permanent hboot from this thread,then it is my personal opinion,that: "yes you should upgrade it"
[Thunderbolt Android Development] sidsixseven:
Just to confirm, the Revolutionary rooting method that was released will leave the user with a bootloader that blocks updates to the bootloader, correct?

If so, any plans to include an unroot in the final release?

I'm on the Rescue Squad over on the TB forums and this is obviously the root method of the future. I'm just trying to figure out how we are going to instruct people to unroot in the safest way.

In my mind, the bootloader blocking is a mixed blessing. Better in all ways except unroot, which is significantly more complicated for the average Joe.

Sent courtesy of SID 6.7 and Tapatalk
[Thunderbolt Android Development] scotty1223:
correct(i have tested ;))

while im not on the unrevoked/alpharev team and cant speak for them,its not likely theyd release something so permanent without intents to release a way to put it back.prolly a tool much like the s-on tool from unrevoked for the radio s-off on the inc and evo. all thats needed is for the tool to run a couple commands in fastboot,and have the bootloaders "on file" that you would need to return to. im personally hoping that the option to undo the permanent patch hboot will leave the user with the original eng 1.04.2000 hboot,wich is easily over written,as this would take care of a wide range of possibilities. a user could flash a back to stock ruu,or simply flash their needed bootloader in hboot or fastboot dep on their desires and skill level.

keep in mind this is a developer preview. id steer folks away from using it if they think they may need to unroot to stock and s-on in the next couple weeks.

i have been encourageing everyone to upgrade to the hboot in this thread. most everyone that is rooted currently used the manual method,and have adb setup,so its just a few more steps to remove it with the original fastboot directions. i posted a very "noob friendly" remove perm hboot guide on android forums if youre interested :)
[Thunderbolt Android Development] sidsixseven:
Agree on all points. Do you have a link handy to your guide? And with your permission, do you mind if I repost it (with credit, of course) or link to it?

I was planning on writing something up, but why reinvent the wheel? :)

Sent courtesy of SID 6.7 and Tapatalk