yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] randomjon:
thanks OP, the application works seemlessly, im still trying to get the browser to play it though.:(
[EVO 4G Android Development] fmedina2:
I believe my phone is installing the original flash on its own. Last night Hulu worked flawlessly, but today I had to re-install the edited flash.
[EVO 4G Android Development] ISSMER:
Go to the market and see if the app is set to automatically download..
[EVO 4G Android Development] akarol:
I have typed about:debug and about:config on the URL bar and pressed GO and I still don't see an UAstring setting option on my phone. Can anyone else confirm the same experience? The Hulu app has been working fine but I'd like to use the browser if I can get full screen with a double tap.

Also, anyone experiencing the app not turning itself off from tuning in the background when exiting it? I have to manually kill it each time with SystemUpdate in order to kill the sound and prevent a huge battery drain.

Finally, I kept seeing the Flash app ask to be update on the android Market and I decided to try an update it. Obviously the app failed to update and now it is remaining on my market list as Free. Any way to get it off completely?
[EVO 4G Android Development] chipsa964:
I have the flash-fixed installed but Hulu is telling me that I need flash player 10.0 or higher. Any way to get them to realize I DO have it installed? :-p
[EVO 4G Android Development] fitzbarrientos:
It is about:debug, and after you press enter you need to hit the MENU button, then scroll all the way down until you see UAstring.
[EVO 4G Android Development] slyder33:
been looking for this forever! Perfect! Thank you!!!!!!!:D
[EVO 4G Android Development] squick:
Works fine fine on ava v9 but, if you back out of a show that is playing, it keeps playing. How in the hell do you get back to the show playing to turn it off. I did the fix, tested it and when I hit the back button the sound was still going. I went back to Hulu and it doesn't have an opption for now playing. If you go back to the same show it just restarts over top of the one playing.
[EVO 4G Android Development] squick:
I just uninstalled hulu that came with ava v9 and tried ti install the .apk file and it isn't installing. the download is bad. when I click the link HULU.APK, the download is instantanious, like theres nothing to the download. I think that is why it wont reinstall. Does someone have a good link?
[EVO 4G Android Development] Laterz.iphone:
I flashed by following instructions, but video keeps playing after i exit.. is there something i missed? also you have 5 files.. i only used 3 of them, what do i do with the others.. was i suppose to flash or install the other files as well? Any help would ben appreciated. Thanks guys~ Im running netarchy's burnt droid on my Evo. Thanks.
[EVO 4G Android Development] GadgetMonger:
Use the back button in the app itself. If you use the back button on your phone you'll need to use a task manager or kill the app via settings / application / manage application. The reason being that the app is still a beta.
[EVO 4G Android Development] Laterz.iphone:
Cant find back button, but Seems to be much better on website. Thanks.
[EVO 4G Android Development] GadgetMonger:
There should be a little back arrow bottom left right below the viewing screen.
[EVO 4G Android Development] Berlin3r:
Can't reinstall Flash

I followed all the instructions with a problem until I reach 7, which requires me to reinstall flash. When I try to download it from market, I get the "package file was not signed correctly" error. Should I look for an older version of flash? I've been using CM 6.
[EVO 4G Android Development] Black SER:
Time to fix the demon voices

9. Reboot into recovery and flash the hulufix.zip

When i go into recovery it's telling me that its a bad file

Build RA-evo-v1.8.0

Install from sdcard

finding update package....

opening update package....

E:Can't open /sdcard/hulufix.zip (bad)

Installation aborted

App seems to open just fine, but getting the demon voices Thanks
[EVO 4G Android Development] Black SER:
bump... bump!
[EVO 4G Android Development] dcharleyultra:
This guide worked for me.

My specs:

Phone: Evo 4G

Carrier: Sprint

ROM: Azrael 3.1 - 1/5/11

Kernal: Netarchy 4.3 CFS more HAVS no SBC universal

Buttonized Power Control Widget v1
[EVO 4G Android Development] bobbysuavey:
Awesome!

Works great! I use the full website because I cant get the app to go landscape, but with the full site if you tap full screen on the video player it will launch portrait. I didnt have to flash the fix or anything. Audio seems just a little un-synced at some times, but I sure as hell ain't complaining. Video quality is better than expected.

Thanks man!

EVO on 2.2

Calkulin's ROM. (best ROM i've seen by the way.)
[EVO 4G Android Development] teeism:
Nice! Thanks OP.
[EVO 4G Android Development] unamusedpunk:
Followed exact directions without a hitch, yet my EVO won't place the videos in Landscape mode rendering hulu useless.
[EVO 4G Android Development] dcharleyultra:
Are you using the hulu app or the website?

The website goes into landscape mode.

Swyped from my Evo 4G using Tapatalk
[EVO 4G Android Development] detcup4evr:
Just Tried it and Now upon going to the Hulu Site it tells me I need Flash 10.0.32 or higher and the app just gives my a blue puzzle piece. Any thoughts?

Note: I am running latest Stock Sprint Rom

***UPDATE***

Followed Directions on the Last post of this Thread. Much eaiser to just update a file with Root Explorer.

http://xdaforums.com/showthread.php?t=802133&highlight=hulu&page=17
[Vibrant Q&A, Help & Troubleshooting] ihowil:
Sorry for this funny question but from what I think unlocked phone can not be locked again (not iphone). One of my friend keep saying he got locked after couples day using unlocked phone. Could be? :confused:

Thank you.
[Vibrant Q&A, Help & Troubleshooting] MacGuy2006:
Hm, you might be onto something.

I had unlocked my Vibrant using an AT&T SIM a few weeks ago (code provided by T-Mobile), but when I was on vacation in Central America last week, I tried a local SIM and it asked me for an unlock code again.

I never did bother trying to unlock it again, but it was kind of weird. Will test it again with AT&T when I get a chance.
[Vibrant Q&A, Help & Troubleshooting] brad4444:
I travel to canada once a week and switch my Tmobile sim to a rogers sim. Has been working for almost 2 months now. Tmobile provided code.
[Vibrant Q&A, Help & Troubleshooting] rhcp011235:
Just re-enter your orig unlock code again
[Vibrant Q&A, Help & Troubleshooting] techspy:
I had similar issues some time ago and posted a question about it but no one responded. I have sinced re-flashed the stock rom again (2nd time) and I have not seen the issue again. It would usually pop up after having to force reboot the phone or do a battery pull after an app hung. I was beginning to think it was related to being rooted and an issue with the mount rw-read only. The first thing I did after the re-flash was to unlock, then did the root etc. It has not come back. One possibly related thing is that sometimes when I have to reboot, it shows missed called after it boots. These are calls that were from a day or 2 before. Its almost like some info isn't being "committed" when a force reboot is done.

Fortunatly it seems that it is just a matter of entering teh unlock code again. Just really strange though...I have always been told that once it is unlocked, it is always unlocked.
[Vibrant Q&A, Help & Troubleshooting] techspy:
Well, it happened again yesterday. Phone was acting wierd, lagging, apps hanging, so I rebooted and got the sim unlock screen again. Entered the code and it unlocked ok.

Very annoying....
[Vibrant Q&A, Help & Troubleshooting] GuestK0080:
My previous Vibrant that I had unlocked re-locked itself somehow as well. I noticed this after I had re-flashed the JFD firmware with ODIN. I popped my AT&T sim and was prompted for the unlock code (again). Which I then entered but unfortunately it didn't take. What's up with that?

I checked my nv_data.bin once again and the code was still the same. I could never get the thing to unlock again though either with the unlock or unfreeze code. It didn't appear to be frozen either; if it was it didn't indicate that.

While flashing via ODIN I never even checked the box related to "efs". I just reloaded the JFD/stock firmware which worked fine. I can't explain it. All I know is I haven't unlocked this new phone yet. I have the code but I will worry about it when the time is come that I need another network to use.

I did notice on the samfirmware.com site they mention to "check your simlock" before flashing a new firmware. Anyone know what that means other than something obvious?
[Vibrant Q&A, Help & Troubleshooting] omegacell:
This just happened for the second time to me on two different vibrants from TMO. Is the consensus that the phone needs to be reflashed?
[Vibrant Q&A, Help & Troubleshooting] techspy:
FYI, I have flashed mine twice back to the stock rom and it continues to happen. Also, I opened a ticket with Samsung and even got an RMA to send it in so they could "reflash it". I never sent it in because I knew that would not fix it.

Again, this seems to happen when the phone starts to lag or apps start to hang and I reboot. This has got to be related. I wonder if anyone has had it re-lock while running a lag fix? FYI, Mine is the stock rom rooted and thats it. I wonder if this is only happening on rooted phones?

It really scares me that there is at least one account of it not unlocking with the correct code after it re-locks.

Really would like to find out a solution for this.
[Vibrant Q&A, Help & Troubleshooting] tjhart85:
I've read that this happens with a lot of Samsung phones, they'll just randomly lock.

Sometimes it appears to make sense (after a ROM flash .... even an official one), sometimes it doesn't. Sometimes it'll only unlock for the SIM you put in, but when you put another in, it'll lock again.

Just make sure you keep your code & have it ready to enter at any given time. Seems to be a Samsung glitch (like the many others we have to deal with).
[Vibrant Q&A, Help & Troubleshooting] GuestK0080:
Yeah same here. When my old vibrant relocked i could never get it unlocked again with the same code. I also highly recommend if your phone is rooted to make a backup copy of /efs which is where that nvram data is stored.
[Vibrant Q&A, Help & Troubleshooting] IrieBro:
Surprised Here Too!

I went out of my way to go to an AT&T store. Then I read a thread here about proving Vibrants are unlocked. Pissed! :mad: Now you're telling me that it may never un-lock again?

"Open the dialer and key in *#7465625#. For an UNLOCKED Vibrant you should get the following result: Network Lock [OFF], Network Subset Lock [OFF], SP Lock [OFF] CP Lock [OFF], press OK to exit that menu"
[Vibrant Q&A, Help & Troubleshooting] tjhart85:
They don't come unlocked, you have to unlock them.

I unlocked my vibrant & what you wrote above is what I see.
[Desire Q&A, Help & Troubleshooting] popepope:
Hello,

I have the following problem on my desire and would appreciate your help.

I used to have 2.1 and just upgraded to Paul's 2.2 r8 version. There were some strange restarts so I decided to start from scratch, create the gold card again, root, etc etc.

I used the unlocker.com as a guide to do all those and here is what happens when I try to root the phone. I also want to mention that right now the phone doesnt boot up and I am stuck in the "triangle" screen, but this one looks different than the one that I knew with the triangle in the middle; it just says htc in the middle and there are 4 small triangles in the corners.

I run the step 1 batch file from unlocker and there are no errors; however, there is a progress bar on the phone's screen that is normally green and for a quick second it turns red and then back to green. I was able to see that this happens when the radio is being written (as per the progress in cmd).

When I pull the cable to the pc off, it gets to a RUU white "screen" and there isnt any button that will have an effect; once I plug back the cable it goes back to the triangles screen with htc in the middle.

ADB is not working even though I reinstalled the drivers, etc. only fastboot works. (by working I mean that the device doesnt show in adb, but it shows in fastboot)

Bootloader is 0.80 and the version that I get using fastboot is 1.21.405.1

Any clue on how to access recovery and just flash a ROM that will be fine? Must be something related to the recent rom upgrade to Paul's r8 Froyo I guess, but I dont know where I messed it up.

Thanks a ton guys and sorry for the long post but it is a strange one and tried to explain somehow the symptoms.
[Desire Q&A, Help & Troubleshooting] Vorbeth:
Re-install using a RUU (Can be done from fastboot screen I think), then use unrEVOked to root, no messing with batch files.
[Desire Q&A, Help & Troubleshooting] popepope:
Hi again,

I tried running different RUUs, both 2.1 and 2.2, but I get the same error at the end of the install wizard: Error 110: file open error (The rom update utility cannot open the requested files or the files are damaged...)

The thing is that the install wizard seems to go through all the steps (checking signature, updating system, radio, recovery, etc.) and only at the end this error comes up.

One other aspect is that again the progress bar on the phone screen is green but flashes red when the radio is being written on the phone (as per the install wizard); then it goes back green when writing recovery, system, etc and there is another triangle with ! showing up on the right side of the progress bar (is not there when it starts).

The info showing up in the RUU "menu" on the phone (the only one I can see when the phone is not plugged to the pc) is showing a bootloader version of .9x after RUUing the froyo's and changes back to .8x after using the 2.1 RUUs. The only thing that remains the same is the radio version that still shows 4.06.00.02_2 irrespectible of the RUU that I try to install (2.1 or 2.2), hence I believe that there is something wrong around the radio part. I remember that Paul mentioned on the thread where I got the r8 froyo pre-baked zip file originally that it includes a radio version 5.10.x while the froyo RUUs that I tried to flash are having 5.09.x, maybe this is the problem as it might be that one cant flash an older RUU than what the phone has, but its strange since the bootloader is "upgraded" and downgraded without problems.

Any other suggestions on what can I do further? (right now I only have access to the RUU menu when I turn on the phone and to fastboot commands in cmd...the phone doesnt start so I cant access anything else as per my current understanding).

Thanks again for the help guys!
[Desire Q&A, Help & Troubleshooting] laupc:
So you can acces hboot and bootloader only??

And when you tried to enter to recovery get stuck on htc logo screen??

Volume up/down button work ok?
[Desire Q&A, Help & Troubleshooting] popepope:
nope, buttons are not working at all, only power up when the phone is off.

here is the sequence providing the phone is off and has a valid gold card in it (I dont get the CID error); doesnt matter if the cable is connected to the pc or not:

1. push power button, phone starts up to a screen showing the following: HTC in the middle (with some water shade under it) and the 4 small triangles in the screen corners (they have a ! mark inside).

- any combination of power + back or + vol down dont start the phone

- when I first rooted the phone having 2.1 there was just 1 triangle (bigger) with the same ! mark in the middle of the screen, that's it and of course all the hboot and recovery menus were ok

2. plug cable to pc and run RUU.... .exe, install starts on pc and also on phone there is a green progress bar under "HTC". bar goes red for a second when the pc app shows something like writing radio. bar gets back to green when the pc apps writes system, bootloader, etc., but there is another small triangle showing up at the end of the progress bar on the phone.

3. error shows on the pc app, error 130 above, then the phone shuts down and if restarted it gets back to the same triangle screen with htc in the middle like it was before the ruu attempt.

- if when I power up the phone (after pulling up the battery) and then remove the pc cable, the screen changes into a white background one with something that I would call a RUU menu; looks just like the one that you get when you power up pressing "back" on the phone, but only with RUU as an option (like you have in the oter Recovery, Restart, etc etc and you navigate with vol up/down and select with power). here no button works, or any buttons combination.

- the screen changes back to the "triangles" one as soon as I plug the pc cable into the phone and switches back again and so on when I pull out the cable from the phone.

- te bootloader version that I can see on the RUU "menu" when I plug out the cable is changing acording to the RUU that I try to write and it goes above 0.8xx and comes back under it easily...the firmware version and radio remain the same though (radio is 4.06.xx, firmware 1.21.xx)

- via cable I can use only fastboot command in cmd, as adb doesnt list the device (I tried reinstalling the drivers). firmware in fastboot is the same as the one that the pc app "sees" on the phone when trying to install the RUU, and the device shows up using fastboot command

That's it...kind of strange, at least to my knowledge at the moment.

And to ask to your questions I dont have access to recovery and not to hboot I believe, only to that one showing RUU as the only option...
[Desire Q&A, Help & Troubleshooting] forelli:
Those 4 triangles in each corners look familiar to me. You forgot to give the most important information: HBOOT, radio, etc.

A few minutes on Google gave me this: Google is your best friend. Keywords were: htc desire triangle corner error. Here is the link to the search page: Google is your friend
[Desire Q&A, Help & Troubleshooting] popepope:
it's not a triangle in the corner...there are more but that's not the point.

hboot is above 0.80xx and radio 4.06xx, but again, as mentioned the hboot version changes depending on the RUU that I try to write, radio and firmware not.

thanks for the link though, added a reply maybe something happened in the mean time...

and btw, google is everybody's friend :)
[Desire Q&A, Help & Troubleshooting] forelli:
I think you miss something here: if I recall properly, those 4 triangles in ALL for corners appear when you try to root a SLCD Desire with a AMOLED rom, thus 'killing' your screen. Try the downgrade HBOOT 0.83-0.92 to HBOOT 0.80 root method and you'll safe. You have to root your phone according to the HBOOT and downgrade it if you need to.
[Desire Q&A, Help & Troubleshooting] popepope:
hmm...the thing is that i rooted the phone before with the same approach as I had now, so same rom and it behaves different now versus the first time; but it worked then so not sure if it is related to the amoled vs slcd screens.

I am already on hboot 0.80xx so the downgrade wont help, right? i am not able to access hboot menu irrespectible of the bootloader version that I see in the RUU menu (I mentioned that based on the RUU that I try to write the hboot version changes up and then also down just by attempting to write a RUU). plus, adb comms are not working, only fastboot...

i think the amoled vs slcd issue was that the screen is not working, but the phone is booting up, etc.

would appreciate some more help pls
[Desire Q&A, Help & Troubleshooting] cr1960:
I have read other posts here about the 4 triangle thing - never saw how any of them turned out though. I'm not having a crack at you here for not searching, but have you had a look here to see whether you can find someone who has had similar problems? With so many members, you can almost bet that someone else has had the same problem as you in the past....

Good luck in getting things sorted.
[Desire Q&A, Help & Troubleshooting] popepope:
tried to contact via PM the users having the same problem, but no reply as of now. will post the solution when found for sure, but at the moment I still cannot get adb functionality, so completely out of ideas, waiting for others :)
[Desire Q&A, Help & Troubleshooting] screamopilla:
Hey Popepope - did you manage to fix this issue? I have exactly the same problem as you have described, and I can see the boot screen after removing the cable following the RUU error and it says "Radio_V2 - Fail-PU". I get the same red progress bar when it is updating the radio. Something is clearly broken here...did you manage to fix yours or did you send off for a replacement?
[Desire Q&A, Help & Troubleshooting] shockem:
Is your screen a SLCD one or a Amoled one? If it is a SLCD one, flash a SLCD RUU. If its a Amoled one then PM me and ill see if I can help you with a problem as I ran a Tuition a few days ago. As you say that the error you get at the end is dew to a damaged file or something, can you try downloading the RUU from a mirror? Again if you need a mirror, pm me and ill post on on my dropbox. The method I used for flashing Ruin was much better and easier so you can hope to find a fix. Pm me. Good Luck anyway!
[Desire Q&A, Help & Troubleshooting] screamopilla:
I managed to fix the issue by leaving the phone to charge overnight, running the same RUU that failed before on a full battery and it worked! I now have a working phone :)

I ran the update on win 7 64 so it shouldnt matter what operating system you use - if you have the same issue as I did just make sure the battery is fully charged before running the RUU. Still having reboot loop issues though :E
[Desire Q&A, Help & Troubleshooting] arifdreamworldera:
Hey Popepope did your problem solve i have the same 4 triangle each side with HTC logo in middle tried most i can but didn't find solution here is the screenshot i had attached
[HD2 General] Paten:
This just raises the question of why didn't you just wait until you had the tutorial written before creating this thread?:confused:
[HD2 General] Snarksneeze:
Sorry, I accidentally submitted my first post instead of previewing it. Had to work fast before I looked like a complete idiot. Guess I wasn't fast enough, eh? ;)
[HD2 General] papeshfoo:
Thank you for this post, Ive been wanting to do this for a while but the other threads were very confusing to me...
[HD2 General] אםזגםנש:
sound dll of 2.13.xxx.xx problem

hi i have the tmous rom 2.13.xxx.xx when i run android i have the robotic voice, i understand that the sound dll is different than the 2.10.xxx.xx and this is the couse.

is there any solution??
[HD2 General] szfjcr:
Did you ever try android on a stock rom? will any of these android set ups work in stock tmous rom?
[HD2 General] Snarksneeze:
I actually had a custom ROM installed on my HD2 that caused the "robot voice". This ROM: {ROM}13Sep Omega WM6.5.x24634 Base3.04 manila2018#XT+Dinik+GTX+MaxSense+Black#Android is the only one I've been able to get a decent run of Android on.

We really, really need more than one option when it comes to ROMs that give Android good support, so if anyone else knows of one, this is a good thread to link it to.
[HD2 General] Snarksneeze:
I tried two different stocks: The one my phone came with way back in June and the new one at tmobile.com/wm_update. I was able to make calls, but the other person couldn't hear me.

I would recommend the ROM I linked to in the post just before this one; it's working great for me so far!
[HD2 General] אםזגםנש:
gonna try it thanks
[HD2 General] dementievafan:
for some reason i cant get it to reboot into android, it keeps going back to the stock windows rom, anyone know how to solve this? thanks in advance
[HD2 General] Snarksneeze:
You might want to check this out: http://xdaforums.com/showthread.php?t=723200
[HD2 General] dementievafan:
hmm so that is the only way to do it currently? what is the logic behind not being able to put android directly on the phone's memory?

thanks again