yashsingh1/xdaforums huggingface dataset:
[Xoom Q&A, Help & Troubleshooting] gqstatus0685:
No source for HC yet.
[Xoom Q&A, Help & Troubleshooting] PMDColeslaw:
Ahh, that would make sense... I forgoot that was still not released. I have been on the stock rooted rom since I got it, lol.
[Xoom Q&A, Help & Troubleshooting] dean_fx:
Not entirely true...

http://developer.android.com/sdk/android-3.2.html
[Xoom Q&A, Help & Troubleshooting] zehkaiser:
An API and source code are very different.
[Xoom Q&A, Help & Troubleshooting] rockhumper:
What he said...
[Xoom Q&A, Help & Troubleshooting] gqstatus0685:
That's the SDK not the Source.
[Xoom Q&A, Help & Troubleshooting] dean_fx:
After the first 2 people said it, i think the point was made ;-)
[Xoom Q&A, Help & Troubleshooting] brandogg:
It's only been said correctly once though. It's the SDK, not an API.
[Vibrant Q&A, Help & Troubleshooting] Weens9:
Hey folks. I recently bought a used Bell Vibrant from someone who believed it was bricked beyond repair. At the time, it would boot to the glowing "S" screen, then hang and die. I figured it was a simple fix, even for a guy with little-to-no Android experience.

I got it into download mode, connected with Odin3, used the stock JFD from T-Mo, and followed the instructions. Everything looked to run well, Odin says "Pass!".

Problem now is that the phone will only boot to the Vibrant screen, hang, then die. I can still access download mode, so I tried redoing the whole process and seeing what would happen, nothing changes. Am I missing a step in the process? Is there Bell firmware out there, or should I be good with T-Mo?

Thanks for helping a first timer.
[Vibrant Q&A, Help & Troubleshooting] explodingboy70:
The bell vibrant is i9000m therefore the jfd firmware will not work. Head over the the i9000 general section and you'll find info for that phone. Or check out samfirmware.com i9000 section for the stock firmware for i9000m
[Vibrant Q&A, Help & Troubleshooting] Weens9:
Thanks, worked perfectly! I've got it booting up fine now.

One last issue- it doesn't want to recognize my SIM now. When I did the reflash using Odin, I just ran with the PIT and PDA, nothing else. Should I try the phone and CSC?
[Vibrant Q&A, Help & Troubleshooting] explodingboy70:
CSC shouldn't matter. Are you using a T-Mobile sim? May need to be unlocked.
[Vibrant Q&A, Help & Troubleshooting] Weens9:
Bell SIM, Canadian. Phone was Bell stock, but I guess this means I've flashed T-Mo and probably need to unlock?
[HTC Sensation] Steve0007:
Unlock Boatloader is officially launched

This is not S-OFF

The strange thing here is that you can get root with this unlock even tho your device will remain S-ON

http://www.htcdev.com/bootloader/unlock-instructions
[HTC Sensation] xtcislove:
Seems very pointless in the DEV section for me... We already have unlocked bootloader´s and S-Off here....

and this is not for the DEV section :D We dont like theire method here! We have revolutionary

and this has nothing to do in this section
[HTC Sensation] GideonX:
Going to disagree. It's another method to unlock, although not really s-off. Cwm and roms can still benefit.

Sent from my HTC Sensation 4G
[HTC Sensation] jmwils3:
not trying to start a war, but i really am confused: HOW will this help those of us here in the dev section? is there any benefit to using their official tool, which is guaranteed to void any and all warranties for us if we DO use them? given that rather large caveat to use, why would anyone voluntarily use this? what could we gain that Im not seeing? I'd honestly like to know, i saw their anouncement yesterday, and looked into it, but didnt know what to make of it myself. I hope someone more knowledgeable than myself can answer this for all of us.
[HTC Sensation] GideonX:
Warranty paranoia again.

Unlocking via htc does not void your warranty completely. No one is going to deny your warranty if what caused it was not related to the unlocking.

For example, if your digitizer fails, no one will deny you warranty on it because you unlocked via htc as that was not the cause. If you decided to drop it and went looking for a warranty exchange, that's another story. Make sense?

As stable as revolutionary dev release is, some people just want an htc official method. Wasn't that what thousands of users petitioned for?

Either way, I think it has a place here.

Sent from my HTC Sensation 4G
[HTC Sensation] Steve0007:
I have followed the HTC instructions and got HBOOT UNLOCK and still S-OFF thanks to revolutionary.

But HTC only unlock the Boatloader (not the S-ON)
[HTC Sensation] eyegor:
Wasnt this released mid-august?
[HTC Sensation] M-M-C:
some guys are searching for an unlocked hboot 1.18.

since you got it with the official htc method, could you dump it for us?

http://xdaforums.com/showthread.php?t=1231998&page=2
[HTC Sensation] dipje:
I think the whole point is this is the _development_ section. Here we discuss and help each other _making_ methods. Since this method is completely done (HTC official) it has no place in the development section, but rather in the standard (q&a?) section.

this method requires no development, it is done. Read the 'iron fist' post by the mods to see what should go in development and not.
[HTC Sensation] GideonX:
While we're fisting, we may as well get the Evo 3D thread in the right place too.

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

Strange, they don't care as much as us Sensation users on whether or not it belongs in dev. They do however share the same warranty paranoia, crazy!
[HTC Sensation] Docmjldds:
+1 to this from a prior Nexus One user. On the Nexus One, we never had S-OFF. We ALWAYS had S-ON and the unlocked bootloader with the unlocked icon one would see when first booting up. The Nexus One had root. We had a ton of developers back in the day putting out all sorts of ROMs and not just Sense versions. Yes, I know that once CM7 gets past Alpha, we should see MIUI as well as CM7 variants along with Sense. But ONLY having an unlocked bootloader did not stop development with S-ON. BUT....more important...MY Nexus had bad Nand memory issues causing over 85MB of bad memory in the /Data partition, and some more bad Nand in /Cache as well as /System. I submitted my unlocked Nexus ONE to HTC. The warranty with regards to the bad Nand was covered. Unlocking the bootloader did NOT affect my warranty since it did NOT cause the bad Nand. Too much hysteria regarding methods of unlocking and I am proof positive this is hysteria is exactly that. Will HTC state this policy in public. Nope. But they did honor the warranty and they full well knew my Nexus One was unlocked.

Last question for all....what can the Sensation do right now with our Revolutionary S-Off that a Sensation with a fully rooted but S-ON unlocked bootloader cannot do. I ask only because this exact issue about S-ON vs S-OFF and unlocked bootloaders was asked by me long before the Revolutionary means was finally posted. I was inundated with the fact that the Sensation was locked down more by hardware and higher Security and just unlocking the bootloader would not really gain anything.

Waiting to be bombarded with opinions. Would rather see facts presented please.
[HTC Sensation] eyegor:
Does an unlocked bootloader, but with S-ON enable us to utilize commands such as "fastboot flash ....." ?
[HTC Sensation] banesi:
Well, I'll tell you what I have done, my Sensation was S-OFF-ed using Revolutionary method but since I like more official things than actual hacks I wanted to go htc way so I flashed latest 2.3.4 RUU (I've Super CID my phone, just in case) than I unlocked it using htc unlocker so now I have UNLOCKED and S-OFF on my bootloader screen, flash recoveries as well as ROM's works without any problems. I didn't tested flash radio yet 'cause there's nothing newer than this one I already have.

Just some interesting note regarding this htc unlocking procedure, on last screen on a phone, when it actually finally asks you to unlock by pressing POWER button actually nothing happens, to exit and reboot this screen you have to choose second option, like what you will choose if you change your mind and decided to not unlock. This is a problem with a POWER button many people have after updating on 2.3.4. Your phone will be unlocked anyway.
[HTC Sensation] eyegor:
I see. This could be due to the fact that you did not set the security flag back to three after flashing the RUU.

Does the website ask you for the serial number/imei or anything like that?
[HTC Sensation] Docmjldds:
It should. But I base that on my Nexus One which only has the unlocked bootloader.
[HTC Sensation] Steve0007:
I confirm, pressing the Power to yes does not react but i aslso confirm that it works as i have now HB 1.18 UNLOCK and i am also S-OFF (using previously revolutionary S-OFF instructions)
[HTC Sensation] GabrielSousa:
has anyone here use the htc unlock ?
[HTC Sensation] GabrielSousa:
can you post here the hboot 1.18.0000 unlocked ?

adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
[HTC Sensation] Steve0007:
1.18 hboot 1.18 UNLOCK posted HERE :)

Other ways:

a) extract the firware from Official 1.45.XXX.XX Rom and flash the necessary firware components (this is what I did)

b) flash official 1.45.XXX.XX Rom, S-OFF it with revolutionary solution and then follow official HTC Unlock Boatloader instructions...
[HTC Sensation] GabrielSousa:
thanks a lot
[HTC Sensation] Steve0007:
Do you have 1.18 UNLOCK now ?
[HTC Sensation] GabrielSousa:
this version is locked :(
[HTC Sensation] Steve0007:
Follow HTC Instructions to get it unlocked, i guess it is related to each device.

I can confirm you that mine is 1.18 and is UNLOCKed
[HTC Sensation] GabrielSousa:
ok, thanks a lot ;)
[HTC Sensation] eyegor:
Why bother getting it to say unlocked if you used revolutionary on it anyway?
[HTC Sensation] Steve0007:
and even it it says UNLOCK as you are S-OFF you can do anything (like if it was UNLOCKed).
[HTC Sensation] joemm:
OCD.....much?
[HTC Sensation] GabrielSousa:
whats your CID ?
[HTC Sensation] Steve0007:
11111111111111
[HTC Sensation] GideonX:
Yes, you can issue fastboot commands.
[HTC Sensation] GabrielSousa:
like mine :(
[HTC Sensation] jntdroid:
I did this yesterday, posted a few dumb (but figured them out) questions here before this thread was up.

Anyway, they send you a .bin file that you flash, and it's based on the token on your phone, so I would imagine it's device specific. Just speculatin' though...
[HTC Sensation] jntdroid:
And to those questioning the benefit of this since we have Revolutionary... well, since we have Revolutionary, there's not a HUGE benefit.... right now. But any future OTA that patches root will render Revolutionary temporarily useless - while an unlocked bootloader won't be affected at all.

However, it's easier/faster to flash a custom recovery now than it was with Revolutionary (which is not an unlocked bootloader - it's just a "hijacked" bootloader with S-Off). Don't have to worry about s-off or anything, simply fastboot that image in there and you're good to go...
[HTC Sensation] ieftm:
Not true. Revolutionary sets radio s-off. And that is permanent. Even if you switch to a full stock ROM + locked hboot, signature checking is still disabled.

Bull****. Our (patched) HBOOT is SHIP hboot with FULL fastboot features. Erase/flash/boot any partition you want. The same is not true for a htc unlocked hboot. There's nothing hijacked about it.

So faster / easier? Huh? You on crack? ;)
[HTC Sensation] jntdroid:
Well I'm still learning this stuff so I probably spoke too soon on a couple of those - my bad on that. I thought an OTA could change it, but had I thought a bit longer I would've realized that each time I returned to stock after Revolutionary I had to manually do writesecureflag 3... so, duh...

However, it's still faster for me to get from a pure stock (unlocked) phone to one with cwm/root if it's unlocked vs Revolutionary (not that Revolutionary is slow by any means).

adb reboot bootloader

fastboot flash recovery recovery.img

reboot into recovery and flash root .zip or custom rom

voila

That's definitely faster than Revolutionary... again not that Revolutionary is slow by any means. Unless you're one of the lucky ones (like myself) that had to reboot the phone and re-run Revolutionary after each fastboot reboot caused the communications error. :p
[HTC Sensation] ieftm:
Phones don't come stock unlocked. You would still have to follow the HTC procedure to actually get the bootloader unlocked (and only that).

That is just as fast as running revolutionary, whereas revolutionary is less effort (as everything is automated).

Hell, it even downloads and flashes recovery.

[/quote]

Again, you're going by the premise that your bootloader is already unlocked. Revolutionary does the above automatically if you already have S-OFF (after setting S-OFF the first time, or if you re-run it later on under full boot, it will download and flash recovery).

It also still provides the ability to do the above flashing (over fastboot) manually. I think you're confused.

As an aside, you only get 'communications error' if there's either a program disrupting USB communications, or your entire setup plainly sucks ;)
[HTC Sensation] jntdroid:
True... but only once. Yes, theoretically one would only have to run Revolutionary once as well. I guess I just have a more permanent mindset with HTC's bootloader unlock, and not so much with Revolutionary (if you decided to return to stock, or something along those lines) - which, I guess, probably isn't a truly accurate way of thinking, at least for comparison's sake!

It's definitely less effort... which is why your product is so great - everybody can use it.

Didn't mean to imply that it didn't...

Trust me, I've run through the gamut of what could be causing it (only happens on my laptop). No other adb processes were interfering, never have usb communication issues with other software, etc. So who knows... maybe it does plainly suck. :) Though I have a pretty simple/clean setup... who knows. But, fwiw, if you look through this thread (and others), I'm definitely not alone. It actually is working when it does it, and it does it at the exact same spots each time, you just have to reboot the phone and run it again, and it moves on to the next step.

Listen, I in no way meant to put down Revolutionary - it's awesome, I've used it like crazy, donated to you guys, etc. If I came across, in any way, as putting down Revolutionary as an inferior method to HTC's unlock (which is a whole other animal that most shouldn't touch), I did not mean to at all, and don't think that honestly.
[HTC Sensation] sn0warmy:
How many times do you have to say the same thing?
[HTC Sensation] j_r0dd:
revolutionary ftmfw!
[HTC Sensation] Steve0007:
screenshot added in first post to show UNLOCK with hboot 1.18
[HTC Sensation] puiutzuusa:
Hi, can you please specify the order: was it S-OFF first with revolutionary or after the HTC metod?
[HTC Sensation] jntdroid:
shouldn't matter - but I think he was saying he could still use Revolutionary for S-Off after using HTC's bootloader unlock
[HTC Sensation] puiutzuusa:
Ok, thanks
[HTC Sensation] dipje:
Don't the unlocked HTC bootloader and S-OFF-revolutionary do the same thing?

I have an official HTC 1.18 unlocked hboot, and was able to flash the latest 5.x CWM recovery without problems. Flashed the latest superuser-package and done, rooted stock ROM thanks to HTC.

If you first unlock with HTC's unlock tool, and then run revolutionary, you'll just undo the work the HTC-unlock tool did, because your entire hboot gets overwritten as far as I see. Pick on of the two methods, both doesn't do anything :).
[HTC Sensation] Steve0007:
right, but you can just flash hboot 1.18 after revolutionary and do the htc unlock bootloader to get the unlocked 1.18 hboot
[HTC Sensation] jntdroid:
I don't believe Revolutionary "undoes" HTC's unlock, b/c it's impossible to get any hboot to say "locked" once you do HTC's method. It seems as if HTC's unlock is something "above" the hboot - but I don't understand it completely yet.
[HTC Sensation] taney:
I second that! I went from N1 to Sensation 4G. I like the sensation but I still truly love the N1!

The N1 is solid and has been for a long time WITHOUT S-Off. I barely installed BlackRose S-off on it to modify the MTD partition but other than that, there was no need for S-off and I did everything I needed.

S-Off for the Sensation does makes things a lot easier because modifying the radio is within reach. Therefore, it's great that we have S-off but we can do without as well.

---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------

Actually, this might be possible. I unlocked my N1's bootloader before I installed a custom HBoot to do S-off. The "lock" is gone but it's still "unlocked" somewhere in the phone's radio. When we are able to unlock the radio, that's when we can "undo" the bootloader unlock (at least that's how it is for the N1).
[TouchPad Development] thaddyusmaximus:
I wanted to start a bounty for getting adhoc support for the HP touchpad. I actually prefer the WebOS vs. Honeycomb (I own the Asus Transformer and the Touchpad) due to some many bugs in Honeycomb. Any developers out there want to make some money, here's your chance.

I'm willing to chip in $50, half the cost of what I paid for the tablet just to get ad-hoc support.

I will update the bounty in the title each day if people chip in.

Dear mod,

Please close this thread as I shall be moving it over to Precentral.net
[TouchPad Development] kevina90:
http://www.webos-internals.org/wiki/Ad-Hoc_Networking
[TouchPad Development] thaddyusmaximus:
Here's the quote from the discussion thread from the wiki:

"It seems the HP Touchpad uses wpa_supplicant, similar to Android, rather than wifidriver, as the previous did. Any workarounds? Breakingspell 05:11, 23 August 2011 (UTC)?
[TouchPad Development] NissanNick:
Noob alert!! What is Adhoc?
[TouchPad Development] homer169:
http://en.m.wikipedia.org/wiki/Wireless_ad_hoc_network
[TouchPad Development] ericdabbs:
[Q] Ad-hoc patch for wifi tethering?

Is there an ad-hoc patch for wifi tethering in the works for the Touchpad? I tried searching on preware and could not find any.

Since the wifi-tether apps on android market use ad-hoc mode instead of infrastructure mode, the touchpad cannot see the wifi connection on my Photon 4g phone.
[TouchPad Development] knownboyofno:
Do you know where the file is on the Touchpad?
[TouchPad Development] thaddyusmaximus:
I'm not sure on the Touchpad. But on Android it is in /system/bin.

Edit: I found a thread stating the location is @ /etc/. The thread is trying to get connected to corporate wifi networks.
[TouchPad Development] thaddyusmaximus:
This is what this thread is for. It's to get a developer to make a adhoc patch as none exists for WebOS on the Touchpad as of yet.
[TouchPad Development] Dees_Troy:
Not always true. Android wireless tether on my rooted Evo 3D gives me infrastructure mode.
[TouchPad Development] Rakeesh_j:
It depends on your phone. Most newer phones are indeed capable of running in infrastructure mode.
[TouchPad Development] ericdabbs:
Posted on precentral.net since that is where a lot of webOS development occurs and of course that is where a lot of the patches on preware come from.

http://forums.precentral.net/webos-patches/259326-patch-request-connecting-ad-hoc-wi-fi.html
[TouchPad Development] lane32x:
Do you have an android phone that you would like this to tether with? This is why I wanted Ad-Hoc support on the touchpad.

Last night I played around with the Wifi Tether app and found out that if I select "Change Device-Profile" to a different phone model (Samsung Fascinate, for example), you can then "Change Setup-Method" to "Softap for Samsung (master) " and this will allow the Touchpad to find your phone's wifi tether.

If this isn't useful for you, well...hopefully it will help somebody out.
[TouchPad Development] NissanNick:
Well Tether works great on my Epic 4g. It is rooted running stock rom. I used it with my TP the other day for about 6hrs and no problem at all. Youtube, Facebook and everything else worked great.
[TouchPad Development] thaddyusmaximus:
I have a Nokia N8 Phone. I use the JoikuSpot App to create a hotspot. Unfortunately for me, it's an ad-hoc network.
[TouchPad Development] thaddyusmaximus:
It seems like i should move this thread over to precentral. Precentral seems to be more popular for dev work on the touchpad.
[TouchPad Development] easyski:
yes, on android there is a way to change your tether to infrastructure mode but unfortunately not all phones support infrastructure tethering due to hardware limitations; such as the original droid and many other android phones
[TouchPad Development] jdbuckeye2009:
The new beta (3.1 i think) of Wifi Tether for Root supports infrastructure mode. I'm using it with my Droid Charge, which is unsupported, but I just changed my device settings in the app to Samsung Fascinate, and it worked fine.
[TouchPad Development] easyski:
Your Droid Charge isn't "unsupported" it has the available hardware to use infrastructure mode.

Unfortunately, as we have already established, there are many phones that allow you to broadcast in infrastructure mode (if you have the right program/right profile) but there are many phones such as the droid 1 and incredible 1 that do NOT have the hardware required to run infrastructure mode no matter what our wifi tether's profile is set to.
[TouchPad Development] Ion4:
This works on my Motorola photon... i was VARY mad that i could not tether with out paying the $30 for tethering... so i downloaded this and tested EVERY SETTING I COULD!! but this worked for me!!! and so far on 3 other Android phones..

http://code.google.com/p/android-wifi-tether/downloads/list

wifi_tether_v3_1-beta6.apk

Install it

Run it

Menu-Settings

Change Device-Profile

Select: Samsung Galaxy S

Change Setup-Method

Select NetD (Master)

Back to main screen

Click start tethering... now you will get 2-5 pop ups with errors DONT WORRY just look for the network and disregard the errors on the phone :)

And now you are good to go. I have used this on my Photon (MoPho) running STOCK rom with root.

Have fun tethering. let me know if it works for you!
[TouchPad Development] Rudementry:
I love you.
[TouchPad Development] chris heath:
I've noticed it works, but it won't work with 4g. Its just keeps scanning, but won't connect. Any ideas?
[TouchPad Development] MXFrodo195:
That's weird. It works perfectly on my incredible 1 running CM7? No issues at all. Doesn't work on my revo though.

Little Buddy Sr.
[TouchPad Development] chris heath:
I'll keep trying, but won't complain. 3g is better than no g. Lol

**edit**

tried again. As soon as I start it it says data connection to 4g lost. Hmmm. Not sure, but this is a great start
[TouchPad Development] dahauss:
we need an adhoc patch... The kernel I use on the EVO does not support WiFi tether. I'm running the BNICE v8 auto bump kernel. Any way to get it working with this kernel? Stock works fine.
[TouchPad Development] yuugotserved:
anyone with the triumph get this to work? i tried numerous profile settings and they didn't work :(
[TouchPad Development] rkn5555:
lane32x' thanks ! Your advice about changing device worked on my WiFi tether

you should get the 50 dollar bounty from the op
[TouchPad Development] gill_za:
not everyone has android phones. that does not solve everyones problem. ad-hoc mode needs to be activated in webos itself...
[TouchPad Development] Palmetto_X:
I can get Wifi tether to work

I am on CM7, Captivate SGH-I897
[TouchPad Development] gill_za:
Galaxy S phones with CM7 create infrastructure connection... We are talking about Ad-Hoc here.
[TouchPad Development] Ion4:
Yep I tried everything to get ad-hoc on the touchpad to work... changed the mtu... changed the IP settings and nothing... so that's when I started to mess around with the settings on wifi tethering beta 5 and found that the settings I used was the only way on Motorola Photon... just happy it worked for you I don't know why of gives you a ton of errors then just starts working but it works so I'm happy ;-)