yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] cj chitwood:
No, but thanks for suggesting it.

I was going to say that root is root, and recovery should have nought to do with it, however in thinking about it, the adb daemon that runs during recovery mode operation is not necessarily the same executable file the phone runs during normal operation, is it? So that would imply the possibility that in recovery mode, one could have access otherwise not had. However, I agree with etn40ff -- I do doubt I'll have any more access to the partition's filesystem with recovery's adb than with the phone's normal adb.

I will try this later tonight then, after I get my daughter to sleep. It's like an hour past her bedtime >mybad< :rolleyes:

Assuming it fails... I wonder if, on that particular filesystem level, RW/RO is determined by the same bit that determines S-OFF itself...
[T-Mobile myTouch 4G Slide] thrice43:
I should have thought harder when I posted that. Referring to my previous reply, access to block devices are restricted when in Android, but can posibly be made writable temporarily while android is running by exploiting the kernel. This may be done by inserting a module "wpthis.ko" modified and crosscompiled for mt4gs instead of the G2, which would give enough of a window to change bootloaders within that timeframe.
[T-Mobile myTouch 4G Slide] cj chitwood:
Okay, sorry for the delay in response...

I tried using dd to write clockworkmod manually as described, and fail. Write claimed to be successful, but in the end (unless CWM looks an awful lot like stock) it failed.

I looked at that module. I understand some stuff in it, but I'm far from an experienced programmer. I would assume that it should work, aside from possibly some byte numbers being different, memory locations, etc. It certainly is something I could have tackled before (1) marriage and (2) having a kid. Who I just heard whimper on the monitor, might have to go take care of her.

so cutting this short, I will say I don't know enough about this phone to confidently risk insmodding that code.

I'm with you re:revolutionary. I can't blame someone for not wanting to give away their secrets when they're getting money for them, but if you're offering a free service, it stands to reason you get some gain somewhere. It's possible they don't. Either way, I never heard of them.

I have a coworker who when I mentioned that rev was the only way anyone seemed to know of who had a working root method for my phone, he just laughed and made a comment about how it was funny they got a foothold on the only phone that had a captive audience for them (e.g. nobody else was interested in rooting). According to him, Rev got basically booed away from all the other platforms. I don't recall him saying why.

I have nothing against them, but understandably I don't know them and never even heard of them until I got my MT4GS: I had a G1 before this, which I rooted the old fashioned downgrade-and-exploit way. I remember it involved RC29. Once I rooted it though, I never followed the scene anywhere else but the G1, and none of this stuff was necessary. I feel like I've missed out, but at the same time, having a wife and kid takes up a lot of my time I'm not at work, and if I spend that time on my phone, wife gets angry and kid feels left out.

Anyway, my whole reason for not doing rev's method is that it requires me to provide my phone's serial number -- a unique identifier -- to a group of people I've never heard of, whose seeming sole purpose on the Interwebs is to crack devices of such type.

My whole reason for not doing the HTC method is lack of the commands in HBOOT needed to aquire the identifier token (I have no problem with the device's manufacturer identifying the device). Were there another way, I'd do that.
[T-Mobile myTouch 4G Slide] Blue6IX:
Principle seems sound - if I could get to that code I would take a stab at it sometime next week when I finish with the couple of things i'm wrapping up now. At least look it over and see what I can find.

----

Came to this thread to drop this link off:

http://xdaforums.com/showthread.php?t=794638

The Android Flasher utility may be helpful to look at.

Lots of HTC devices as the supported list of devices - and the Sensation is one of them. Given that the Sensation is very similar (but not the same as!) the doubleshot, this might be a good utility to look at for what you are trying to do.

Happened to come across it and thought it might help.

I wouldn't recommend just downloading and using it, definitely look it over and determine if something disastrously bad will happen first - but this thread has gotten technical enough where that should be a given - right?
[T-Mobile myTouch 4G Slide] thrice43:
Thnx for heads up. This engineering bootloader deficiency is honestly making me want to go back to the G2. Not that I don't appreciate the devs or anything... I just feel that the G2 really made me research more about unix, android, and stuff.

I mean like wtf happened? Out of nowhere cm7 drops on the doubleshot, we are told there will be no developments/updates on cm7 cuz cm9 will be coming soon, and then so much time passes with few developments that it almost would've been worth it to get cm7 %100 stable back when it first came out.
[T-Mobile myTouch 4G Slide] Blue6IX:
Are you still on the 1.44.0007 hboot that's S-ON?
[T-Mobile myTouch 4G Slide] Blue6IX:
http://xdaforums.com/showpost.php?p=17384086&postcount=4

Summary of some of what was found here + other
[T-Mobile myTouch 4G Slide] thrice43:
sh!t. Thanks for thanking me Blue6ix! That's a first
[T-Mobile myTouch 4G Slide] thrice43:
Hey I figured out how to get all the engineering bootloader functions, including the omeapiwlanmac to change mac address. Just "dd if..." this hboot for sensation http://cmw.22aaf3.com/pyramid/hboot/pyramid.hboot-1.17.2008.zip then reboot to fastboot run "fastboot oem oemeapiwlanmac xx:xx:xx:xx:xx". Then I rebooted back hboot and restored the 1.44.0006 hboot, then restored nandroid. The mac address change stuck! I'm not sure if we can just keep using the sensation hboot like it meant for doubleshot. Testing that now!
[T-Mobile myTouch 4G Slide] Etn40ff:
You are a daredevil.

Since it boots to hboot you may be able to keep it. The only catch might come from the partitions: I think the two phone have different partition layout. You should be good to go if you reflash recovery and the rom after flashing hboot

Good luck
[T-Mobile myTouch 4G Slide] Blue6IX:
I think it's time for me to look into writing a custom bootloader then - that's the first though that comes to mind after reading that.

----

I don't think they are very dissimilar, in fact may very well be the same.

In the last post of my dev ref, I have some scratch notes and one of the links in that post is to a full map of the sensation partition structure. Everything we know so far about ours matches - names and block locations anyway.

Once we finish mapping ours, we may very well find that we can flash more then just their hboot.

Now, radio, hboot and some others I can't think of all have to agree on s-on or off status or the device refuses to boot, it simply will not load hboot or anything else. Technically a brick - if thrice was s-on this would've probably bricked his phone...rev disables most or all of that check so he got away with it.

I def have more to play with tonight now.
[T-Mobile myTouch 4G Slide] thrice43:
I don't think partition layouts differ much, radio, boot, hboot are in the same mmcblks as sensations. But yah. I was just like f*ck it, and ran "dd if" after finding that they haave similar partition layout. Here's the thing tho, if u run the "dd if.." command from within cm7, like I did, and reboot to bootloader, everything is in working order until you try to boot into cm7. The only way to get cm7 to boot while maintaining sensation's hboot is to nandroid restore, and when it does boot it'll freeze eventually. I had to restore original hboot after running the fastboot commands available in sensation_hboot.img used to permanently change the phones mac address.

Upon seeing the list of commands available in sensation's engineering hboot using "fastboot oem ?" compared to what's available in doubleshot's 1.44.0006 hboot, I'm not so sure if 1.44.0006 hboot is an engineering hboot; but rather just an "s-off bootloader" that happened to ship with some devices.

Edit:

Blue6ix, if you're planning on writing a bootloader I'd truly be delighted to watch it all come to fruition.

You know, what's interesting is that at the top of fastboot/hboot screen it still says doubleshot even with a sensation bootloader, just a different hboot version and etc
[T-Mobile myTouch 4G Slide] Etn40ff:
thrice43: did you try to install a rom from scratch?
[T-Mobile myTouch 4G Slide] Blue6IX:
well, given the list of commands that you used from the sensations hboot, I don't think it would be too big of a project to hexedit them in for S-OFF devices, given what i've learned recently.

The next step in looking into the s-off process is to strip the hboot down in hex and see what I can learn, and we know that being s-off gives you a lot of freedom and forgiveness. I think that the rev method basically disables all crc/signature checks for files, so you don't get bricked when the radio, hboot and others don't agree on sig checks/crc checks.

If everything doesn't check out you won't even get to hboot when you try to power up on an s-on device - but the rev method definitely worked some special magic on our devices.

It's still gonna take me a few hours to get my head back in the game, but that's kinda where i'm at right now - absorbing all this is a lot to take in but making progress daily so we'll see where we end up.

I have no worries about it working on an s-off device, and i'm positive it'll brick an s-on device, so that's kinda where it sits right now.
[T-Mobile myTouch 4G Slide] thrice43:
I checked "hexdump -C hbootsensation.img > hbootsens.txt", "hexdump -C hboot.img > hboot.txt", "diff hbootsens.txt hboot.txt", seems like quite a bit of a difference in hexdump but I'm not sure as to what you'd consider a lot lol
[T-Mobile myTouch 4G Slide] thrice43:
Having a true engineering hboot is most definitely going to make things a whole lot more interesting on this device. I was looking into the commands in the command list, http://bit.ly/A2gBLB, about serial link, blah blah. That really interesting about hexediting the hboot file. How would one pinpoint the bit(s) to change?
[T-Mobile myTouch 4G Slide] Blue6IX:
Slow, tedious going is how to hexedit...

In the program I'm using it shows the hex on one side and a column on the other for what they represent.

I've been using hxd, mainly because it has a portable version and I have it installed to a flash drive so I can just pop it in any windows computer and continue my work wherever I am.

Finding out what bits to change is a matter of trial, lots of error, and limited successes - so dev as usual but on a harder level because there really aren't any guides I've found on it. Mostly a matter of making it up as I go.

Loading each hboot into the hex editor and trying to determine what bits represent what functions, and then how to add them to a new file.

I just spent the last 12 hours poring through the hboots I have, which are all of them to my knowledge for this device - I need to take a break now because my brain literally hurts.

When I get back to it I'll grab the sensation hboot you used and see what I can glean from that.

It's raining here, so it's a great time to take a nice walk in the woods and not run into other people, sort out my thoughts and unravel some of the numbers in my head.

My net connection is blocked up with some files I'm trying to get, in the home stretch on that and should be able to start using it again by the time I get back, it's cumbersome to add links through the xda premium app.

The files I'm downloading are for a native linux install on my nook color - know of any linux hex editors I could use?

I'll be back in a few hours and go from there.
[T-Mobile myTouch 4G Slide] thrice43:
Do u think it'll be more efficient if you write a shell script that'll just literally find diffs, flick a bit in the range of diffs of hboots, log it, adb push, dd if, adb reboot-bootloader, sleep x, test if working correctly..... repeat ?
[T-Mobile myTouch 4G Slide] Blue6IX:
That's a good idea, but you're halfway home - I wouldn't want to automatically flash to the device and reboot...if it didn't work your phone wouldn't boot.

The only option at that point would be download mode or HTC factory fix - and HTC would be unlikely to fix it at the factory for this issue.

For S-OFF devices this is of much less concern, but i'd hate to end up there by accident.

Also - I feel that doing it by hand is an important step in learning the file and it's structure as intimately as needed to work with it as effectively as i'd like.

Right now I think (at least to me) immersion is more important then speed - I came to terms a long time ago with the time it takes to do this kind of stuff one agonizingly slow step at a time in order to get the results all around that I want.

Accuracy is more important then speed, but the more you do it the faster you get - the principle of not using cheat codes until you beat the game really does apply.

I am determined and committed to solving this issue - a custom hboot and S-ON to S-OFF on 1.45.0013 starting hboot is my goal and will happen.
[T-Mobile myTouch 4G Slide] cj chitwood:
Yes, nothing has changed.

Sorry so long on the reply; I've been ... discouraged... from using the computer in my disposable time for the past few weeks.

Edit: And I see now much has been going on in my absence. Kudos to you lot for keeping up with it.
[T-Mobile myTouch 4G Slide] Blue6IX:
:oSorry wrong thread - too many tabs open:o
[Droid 2 Global General] Ballard540:
Ok here it is as best as I can remember.

Droid 2 Global rooted about 6 months ago. I installed liberty at the time. It was my girlfriends. She used that for a while and is now using the DINC 2.

So for the past 4 months it has been turned off and not used since she got the new HTC. So now we need to use the phone but I can not turn it on. First thought was dead battery. I put it into a working D2 and it turned right on. Ok first sign this is not gonna be good. So I went ahead and charged it. Got that done put it back in the phone. Still nothing. The side LED lights up when plugged in. but nothing else will happen.

I have tried plenty of key combos with nothing working at all. Nothing. I know all about RSD lite and how to use it. But the key to using it is being able to power the phone on which I can not.

Before you ask the phone HAS NOT been damaged or wet. It is in the exact condition it was when we turned it off and laid it in the drawer. Which is what is so weird it was working fine the day we stopped using it.

Thank you all ahead of time.
[Droid 2 Global General] Gasai Yuno:
I'd say it's a warranty claim case.

Did you try removing the SIM and SD cards from the phone prior to powering it up? Also, just checking, while turning it on you tried holding the lock/power button pressed for 2-5 seconds, right?
[Droid 2 Global General] Ballard540:
Yes I tried to power it on that way with no luck.

There is no luck of filing anything on warranty :/ this phone has been off the account for months and has been rooted so all warranty void.
[Droid 2 Global General] Gasai Yuno:
Well, if it doesn't even power up, they cannot really determine that it was rooted or anything (especially if you go the Asurion route).
[Droid 2 Global General] Ballard540:
Well I carry asurion on all my phones. But won't it look a little fishy if all of a sudden I add this D2 to my plan again then file a insurance claim....
[Droid 2 Global General] Gasai Yuno:
I doubt Asurion cares if your phone is at all activated. They aren't Verizon.
[Droid 2 Global General] Ballard540:
Ok. So normally you start your claim with asurion on the verizon website. Since this phone is not activated how will I go about filing a claim with them since this phone is out of service....
[HTC Wildfire S] bonesy:
First thanks to the guys on the sensation forum who worked this out,I wouldnt have tried otherwise!Big big props to ratykat and brokenwall.

ORANGE USERS ONLY

You have to Edit your build.prop to have this line rild.libpath=/system/lib/librilswitch.so Then flash the zip file through recovery, Turn on your WIFI and open the app wait a minute and Voila
[HTC Wildfire S] Tuoni:
What about Virgin, who now use Orange's network in addition to their own? Would it work for me?
[HTC Wildfire S] jaketame:
Exactly what I have been looking for.

Originally tired on ARHD 3.6.0 ICS on Sensation XE following the original guide however was unable to amend default.prop thus caused issues with the libs.

Currently VI 3.5.0 now so will test this after a backup and keep you posted.
[HTC Wildfire S] simonx2x:
Has anyone tested this on ICS?

Wont flash succesfully for me.
[HTC Wildfire S] Narcof:
I tried it out on UK Wildfire S running CM7 on Orange network, the phone ran really slow after installing it even after multiple reboots, and was unable to connect to the Orange network at all when I turned off the WiFi, just 'No Signal'.
[HTC Wildfire S] MikeDVH:
Hi,

When you say "You have to Edit your build.prop to have this line", do you mean that you just add that line as a new line to the build.prop, or do you change an existing line? :confused:

I'm kinda new at this so please excuse my ignorance!

Thanks,

Mike

:):):)

---------- Post added at 12:16 PM ---------- Previous post was at 12:02 PM ----------

Just worked this out!

Sorry! :silly:
[HTC Wildfire S] bardbank:
No signal boost

Hi

I have rooted my wildfire s and gone through the process of modifying build.prop and flashing the signal boost

zip file. The result is a red house that never goes green. My Blackberry works fine on uma.

I placed a new rild.libpath line in my build.prop file was this correct or should I have modified an existing line?

cheers

Mike
[HTC Wildfire S] mugglesquop:
anyone got this working? just want to check before i try it...
[AT&T Samsung Galaxy S II SGH-I777] justinblaine23:
So I've been looking through the i9100 forums for themes and many are "universal" for all Roms..I was wondering if that's possible on our version of the gs2?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Got links? Probably using vrtheme or similar - these MIGHT work on our device as is.
[AT&T Samsung Galaxy S II SGH-I777] justinblaine23:
Yes its vr (unsure the exact importance) ill try to find a link and post as edit

EDIT:

http://xdaforums.com/showthread.php?t=1358110

That's one of a few I've seen ...thanks for the reply...you always are really helpful!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
The themer in that case doesn't seem to know what he's doing - vrtheme can do some theming universally, but the jkay customizations are NOT portable.
[AT&T Samsung Galaxy S II SGH-I777] jivy26:
Ill talk with them and see if they mind me bringing it over to i777
[AT&T Samsung Galaxy S II SGH-I777] avidmovies:
Hm if we could have these vrthemes that would be awesome!

It would probably be less work for themes in the long run too, imo.
[AT&T Samsung Galaxy S II SGH-I777] justinblaine23:
Yea that was just one example I didn't read too far into it, thanks jivy, I'd help out but I'm not that knowledgeable yet...trying to learn...lol :)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
It is interesting, vrtheme has existed for a while but this is the first time I've seen themes based on it.

Haven't tested yet, but this one should be truly universal and may work on UCKH7/UCKK6 based firmwares:

http://xdaforums.com/showthread.php?t=1429588

This one may work too:

http://xdaforums.com/showthread.php?t=1154252

The one linked above isn't universal any more due to including JKay - it will only work on firmwares supported by that version of JKay.
[AT&T Samsung Galaxy S II SGH-I777] avidmovies:
I'll try flashing Noed DarkBlueGray VRTheme once I take a nandroid backup and report back in a bit.

Looks like its "most" compatible with jkay 13.4.1, whereas icscrewed is still on 13.3.9, but I'll see how it goes.

EDIT: see below post. good stuff.
[AT&T Samsung Galaxy S II SGH-I777] avidmovies:
Did Nandroid backup.

Wiped cache & dalvik for good measure.

Mounted /data & /system.

Flashed zip twice.

No errors at all, worked beautifully.

Personally I didn't really like the look of the theme, so I restored back :p

Attached screenshots for reference.

This could be verrrry nice, it would instantly increase the amount of themes we have :D
[AT&T Samsung Galaxy S II SGH-I777] justinblaine23:
Awesome! I wasn't too impressed with the theme itsself but I loved the idea of universal (or partially anyway) themes...I appreciate testing it out...are you on icsscrewed?
[AT&T Samsung Galaxy S II SGH-I777] avidmovies:
Yes I am, haven't been on unnamed since the 1.x days. Though I'm sure if gtg added jkay, it could also work there
[AT&T Samsung Galaxy S II SGH-I777] justinblaine23:
Anybody tried metamorph? From the second link entropy posted? Its a free app in market that is supposed to allow you to theme your own images..
[AT&T Samsung Galaxy S II SGH-I777] avidmovies:
I've tried it, but while on unnamed. I'll check it out again if i find a good theme worth the effort :p
[AT&T Samsung Galaxy S II SGH-I777] justinblaine23:
ok, so is there a thread or explanation on how to use it? I'm running a hellraised ROM so I was considering installing one of the themes and using metamorph.

So i've looked around and found how to use it, but after i download a theme it doesn't give me the chance to install it, it comes out as a bunch of .apks....

Where did you get the theme you used for unnamed? and do you know what version? I tried criskelo (i9100 hellraised), unnamed and shostock and it ends up with the same symptoms.

Edit: Nevermind, it finally worked after completely wiping cache/dalvik running the kernel cleaning script ( i had recently tried miui...) and updating to entropy's newest kernel..was running the original kernel in hellraiser so it was an older one...maybe that caused the problem? Anyways thanks for the help
[AT&T Samsung Galaxy S II SGH-I777] dully79:
Thanks for the interest in my theme but with respect your wrong.

I haven't included jkay mod, just the images that jkay mod uses, this way I could keep the theme as universal as possible. The images will be pushed into your framework/systemui but if there not called they won't be used and shouldn't cause any problems.

Hope this helps,

Regards.:)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
You state in your listed features:

"CRT on/off screen(enable via Jkay deluxe settings)" indicating that you are including JKay's theme elements. If you weren't including JKay's theme elements, this would say "Flash over JKay theme".

And in the ChangeLog

"updated Jkay to 13.4.1"

Now, if you updated JKay to 13.4.1 - that means you've included JKay, and thus are not a universal theme.
[AT&T Samsung Galaxy S II SGH-I777] dully79:
Where does it say that?

Were you reading the wrong thread lol.;)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
http://xdaforums.com/showthread.php?t=1358110 - the one linked above my post by justinblaine23

Why are you talking about mariolcela's thread anyway?
[AT&T Samsung Galaxy S II SGH-I777] tysj:
Confusing turn of events???

He's talking about his thread which you linked (2nd link): http://xdaforums.com/showthread.php?t=1154252. Which is why he quoted you:
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Which I said "this one may work" to.

When I said "linked above" I was talking about the one that was linked above my post by someone else.
[AT&T Samsung Galaxy S II SGH-I777] dully79:
Haha lost in translation, your English is different to my English lol.

You meant the link above your post.......

Not the link above your comment.

At least were clear as mud.

Have a nice day.:)
[AT&T Samsung Galaxy S II SGH-I777] JohnMcW:
No Luck

Hmm, I tried both themes from post 8 with no luck, multiple tries, with wiping cache. I have UnNamed 2.2.1 rom on my phone.

Would make theming easier if it worked. :rolleyes: