yashsingh1/xdaforums huggingface dataset:
[HD2 General] jehanwalsh:
When trying to browse using a Wi-Fi network, it says:

-----------------------------------------------------

ERROR

Could not locate remote server

You tried to access the address

ht-tp://bbc.co.-uk/, which is currently unavaliable. Please make sure that the web address (URL) is correctly spelled and punctuated, then try reloading the page

Make sure your internet connection is active and check whether other applications that rely on the same connection are working.

--------------------------------------------------------
​

When browsing with GSM, 3G OR HSDPA it's fine.

It is not my Wi-Fi settings as it does this on every Wi-Fi network I try, including public networks in Starbucks, McDonalds etc..

Any suggestions?
[Touch Diamond, MDA Compact IV Themes and Apps] cyanbird:
i want to use bluetooth headset to listen music..

but the system default is windows media player...

how to set or use other players to listen music when i use the bt headset??

As the windows media player has many problems...

thank you!!!
[Touch Diamond, MDA Compact IV Themes and Apps] cyanbird:
anyone can tell me ..how to change the default player from windows media player to

pocket music player??
[Touch Diamond, MDA Compact IV Themes and Apps] cyanbird:
anyone can help??
[Touch Diamond, MDA Compact IV Themes and Apps] mointernet:
Teksoft BlueMusic

As I know ，most of players can not support the bluetooth except windows media player. Some functions can not be achieved by Bluetooth controller.

Try to google for “Bluetooth player for ppc” maybe find the one that you need.

Teksoft BlueMusic
[Touch Diamond, MDA Compact IV Themes and Apps] cyanbird:
thx for help first!

but my problem is when i use bt headset to control and start..

the windows media player will pop out..

i want to change it to for example ...pocket music player...

how to do it???? as windows media is so trouble in making the playlist and it will be deleted

after u closed the program!!
[Touch Diamond, MDA Compact IV Themes and Apps] kiobeed:
try to use this app:rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] cyanbird:
thx!!!

but not in this case...
[Touch Diamond, MDA Compact IV Themes and Apps] svcat:
select (tap and hold) any mp3 file in Resco Explorer, then:

open -> open with -> select "pocket music player" -> x - "always use this program to open this file type"
[EVO 4G Android Development] forumsid987:
I think this thread can eventually turn into a sticky. I am going to ask all the common / newbie questions relating to the post by toast that is quoted below. Please contribute clear answers in the thread and I'll include them here at the top:

Q: What does RUU stand for?

A: ROM Upgrade Utility. It is used when a new ROM is available by your carrier. Don't use this since it will nullify your root.

Q: Where can I find photos of the root process?

A: Right Here, thanks to pingpongboss

Q: Where can I find the details and download locations of the custom roms available?

A: ???

Q: What is a custom recovery?

A: ???

Q: What is a recovery partition?

A: ????

Q: What things are we not able to do since we don't have the ability to

A:

1) You cannot remove unwanted applications inside of android that couldn't normally be removed. You must remove them prior to boot.

2) ???

Q: What are all those code snipbits?

A: ??

Q: What is the point of the "recovery instructions"?

A: ??
[EVO 4G Android Development] pingpongboss:
Pics of the rooting process: http://androidforums.com/htc-evo-4g/90122-root-out.html
[EVO 4G Android Development] forumsid987:
Phenomenal. Added to the original post. Could you please help with some of the other questions if possible?

Thanks
[EVO 4G Android Development] pingpongboss:
Where to find custom roms: in this subforum xD

the rest of the questions I don't know how to answer correctly. Custom recovery lets you flash custom roms and make nandroid backups?
[EVO 4G Android Development] flipzmode:
In order top to bottom:

As they become available you will find them in this forum. I will release a fresh rom for evo once I can test on my own device. It will be posted here, as well as at http://geekfor.me like always.

The green and black screen that you see that lets you flash a custom rom and create a nandroid backup, that is a custom recovery. The problem is because of NAND protection we can't currently flash that recovery and have it stick. That's why you have to run the bat/sh script each time, to load it manually.

It's the partition that the recovery resides on (the part of the internal storage memory).

Aside from not writing to system while booted (which was answered already) all that means is that instead of being able to boot directly in to the custom recovery view power button + home button or volume down, you need to run that script to get in to recovery. That's the only thing not being able to load the custom recovery means.

Code snipbits?

Um, because how else would you know how to get in to recovery so that you can flash a rom / create a backup / etc?? :)
[EVO 4G Android Development] TheBiles:
Is there any chance of fixing that recovery issue? Having to run the script to access it each time is going to get old fast.

-------------------------------------

Sent via the XDA Tapatalk App
[EVO 4G Android Development] MrDSL:
In the rooting instructions it keeps mentioning just plug phone into usb port on a pc and in shell do this.

I am on windows 7..what shell?
[EVO 4G Android Development] joeykrim:
maybe change the thread title to FAQ on how to root rather than elaboration, might attract more attention.

i was going to answer the questions which haven't been answered but flipzmode did a great job and the 1st post hasn't been updated. once the 1st post has been updated i'll check back and add more detailed if there is anything left to help with!

good question, this would be good to add to the guide above.

the shell on windows 7 means the command prompt. never used win 7 but on win xp and vista, start->run->cmd

and it pops open the command prompt, navigate to where you extracted the zip file contents to, cd c:\evo-root\ . then run the .bat file by typing recovery-windows.bat .

on linux the terminal interface is called a shell because it actually brings up a shell binary, /bin/sh or /bin/bash . google these binaries for more detailed information. on windows the shell, is basically the command line which is now emulated in windows, where back in the days of DOS it was the actual system with windows loaded on top as a GUI...

sorry prob too much information!
[EVO 4G Android Development] forceOnature:
Is there an alternative to reboot recovery that does not require ADB?
[EVO 4G Android Development] joeykrim:
an alternative way to reboot into recovery without using adb?

boot into the bootloader and select recovery? use the quick boot GUI to reboot directly into recovery? use connectbot and connect localhost, type reboot recovery?

you'll be needing ADB for a good chunk of the custom recovery process in order to load this Froyo ROM.

adb isnt too bad, just dive in and we're all here to help!
[EVO 4G Android Development] a5ehren:
Start -> Accessories -> Right-Click on "Command Prompt" -> select "Run as Administrator".

If you don't need to run as admin, you can do

Start -> type cmd -> Enter

and it'll come up.
[EVO 4G Android Development] nicholasbithell:
Anyone have some solid "Adb on Mac" instructions? LIke how to get it going on a mac... Just switched from PC... Thanks
[EVO 4G Android Development] JustinChase:
I believe Start -> type cmd -> Shift+Enter will run as admin also.
[EVO 4G Android Development] PlankLongBeard:
Simply put im on a mac and a windows at the same time.. I cannot get the bat to run correctly I see it run but it looks like a fc and then it closes.. On the mac I get asked for this..

sudo: ./adb-mac: command not found

sudo: ./adb-mac: command not found

new-host:~ GodDriven$ sudo: ./adb-mac: command not found

Please help?
[Hero CDMA Themes and Apps] scirio:
but where the fugg is "su".

I pushed superuser.apk no prblem but were is this extensionless su app??

Reason:

I rooted my gf's hero and need to run titanium to backup all her apps before I flash Fresh 2.1.2 to it. After lots of searching I se I need to put SU on it. Can soeone shed some light...?
[Hero CDMA Themes and Apps] mrchu001:
hmm.. you could just use another backup program that doesnt need root. i personally use astro to back up my apps.

assuming that just pushing superuser.apk works, then you should get a prompt when you try to use titanium back up that asks for root access.
[Hero CDMA Themes and Apps] reedsw:
su should be in /system/bin and I believe /system/xbin. I had to cp su /system/xbin for Metamorph to work a while ago...

adb shell
cd /system/bin
ls

see if su is in this folder. if it is then

cp su /system/xbin

But wait till someone else confirms this...

Also, if you are getting the black super user request screen make sure that you have USB Debugging turned on. Settings>Applications>Development>USB Debugging Mode
[Hero CDMA Themes and Apps] azyouthinkeyeiz:
"su" is not an app.. "su" is command for "super user"..

"su" is root access.. If the rom you are using is not rooted it will never have "su".. Because the rom will not allow sudo access

*search for appsaver to get the apps from an unrooted rom..
[Hero CDMA Themes and Apps] Kcarpenter:
Have to kind of disagree with you here.

he is refering to the SU file that lives in //bin/

Which is technically "executable" when setting suid bits.

But you are correct in that the rom should have that. And if it doesn't...she's not rooted...and you'll need more than just SU eventually...you should go ahead and get busy box installed for TIbackup to use.
[Hero CDMA Themes and Apps] azyouthinkeyeiz:
The su file that lives in //bin/ allows the rom to interact with busybox and supermissions.. It is not an APP just a directory file.. That's like saying on a PC that the DLL files for each program is a program.. It does "execute" but there is not a single file on your computer that isn't "executable" in someway.. I was just saying in layman's terms that he can't do what he wants..

You can't just install that on a Sprint Rom.. He cannot just push busybox into his rom because it is lacking the su file.. And it cannot interact with the Sprint Rom even if you did get it installed somehow...

Yes he rooted the phone, but the ROM is still locked in by sprint until you flash a custom rom.. You have to repackage the rom and reflash it to get those parts into the rom.. Which would not help this guy with what he wants..

*again.. Search for appsaver.. it is the easiest solution for you OP
[Hero CDMA Themes and Apps] scirio:
I knew it wasn't an "app" but I also figured you guys were smart enough not to hassle me about symantics ;)

Ended up just flashing Fresh 2.1.2 and to hell with her apps.
[Hero CDMA Themes and Apps] Kcarpenter:
I tell ya what, every time I wipe my wifes phone and wipe out that "My Days" app. She wants to kill me. You'd think she has that schedule memorized...lord knows I do. :mad:
[EVO 4G General] maejrep:
Breaking this discussion off from the EVO root thread, as it's a separate beast entirely.. :)

True, but truth be told, there's a separate ENG SPL, which would actually fix the NAND protection by default, if it would flash. But because it's an older release than what came on the phone, it won't let you flash it (even tried with a goldcard, and no go). This version matches the stock version, which means it can be flashed back and forth with no complaints.

Firmware, yes (aka radio). But it's actually the bootloader (aka hboot) that sends a command to the radio to say lock it or unlock it. There's even a linux API in the "mtd" driver to allow an ioctl() call to unlock a NAND ... IF it's supported (the source code we have shows that the msm_nand_unlock() code is missing, thus it's not supported). When booting into Android, hboot says "lock NAND", and when booting to recovery, it says "unlock". When it's locked, you get a "not enough memory" error when trying to do any writes to the /system partition (even after remounting it as read-write).

The fixes are ..

1) ENG hboot. I've tried unsuccessfully to flash just the hboot.img from the engineering RUU, using our custom recovery ... it goes through the motions like it's supposed to (writes hboot.img into a section of the nand, sets a flag in the bootloader, then reboots; then the bootloader finishes the flash and reboots again back to recovery), but it doesn't take effect .. seems as if it's doing some kind of version check and it fails that version check, so it rejects the hboot.img update.

2) reverse engineer the msm_nand_unlock() API by disassembling hboot and seeing what it does to lock/unlock the NAND, then try to do the same thing from Android. In theory, that would allow it to unlock the NAND from userspace.

I haven't given up on either of these options, I just haven't had the time necessary to devote to it yet.
[EVO 4G General] theillustratedlife:
Also from that thread:
[EVO 4G General] maejrep:
I've gone over it in IDA for a couple hours now ;) It may well be that simple, but it's not just the "0.79.0000" version part, since I did try changing that and it didn't help. But it could be a different version that's read from some other byte in the image. Like I said, still investigating.. :x
[EVO 4G General] Aphax:
I just wanted to point out that a HTC Desire demo model was found to have S-OFF and had its NAND unlocked, while having the same SPL as normal locked Desires. The S-OFF was triggered by the SuperCID (1111111) I believe which is set somewhere in the radio and also in the 'misc' nand partition (but just changing the CID there had no effect).. not sure if this is helpful but I felt like mentioning it since I guess the NAND locking is similar on both devices. Also I may have gotten some details wrong here since I'm not really involved in mobile phone hackery, but would really love to have a completely unlocked phone :)
[EVO 4G General] joeykrim:
to clarify, when booting into the bootloader with the userdebug RUU PC36IMG.zip, hboot says unlock NAND and this only applies to /system and the location for hboot.img (SPL?) currently? /recovery remains locked.

you said you're able to flash the engineering hboot.img from recovery? to flash it, you're using the flash_image binary loaded by the EVO-recovery.zip?

i know this is explained above but not 100% clear on how the userdebug RUU PC36IMG.zip unlocks /system and the location for hboot.img ?

sorry if the questions are n00bish, still tryin to get up to speed and its hard w/o the actual phone!
[EVO 4G General] maejrep:
The "userdebug" part of it doesn't matter: even the stock ROM has its system partition unlocked *while in recovery*. But because the stock recovery has adb disabled, there's not much we can do with it, and because the stock recovery requires HTC-signed update.zip's only, we can't flash anything with it. So whenever the bootloader (hboot) starts loading recovery, as part of that, it tells the radio to unlock the system partition. We just happen to have a userdebug RUU that gives us adb & root while in recovery, thus we can leverage the unlocked /system partition where with the stock recovery we can't.

I'm able to *attempt* to flash it, via an update.zip, which has has update-script that says "flash hboot with hboot.img". It is *not* the standard flash_image, because you can't flash the bootloader from something that comes after the bootloader. The bootloader doesn't live in any of the mtd partitions that are accessible from linux kernel space. Basically how it flashes firmware (that includes both hboot and radio images) is it trashes the /cache mtd partition, and shoves the hboot.img (or radio.img) data into the section of NAND that should be the cache partition. Then it reboots. The radio/bootloader sees the special magic header in the cache partition, and understands that it has to take that data and flash it over its current hboot. That step is what is currently failing (with no log or explanation why, yet). Regardless of success or failure, it will reboot back to recovery, because the last step is that recovery has to reformat the /cache partition to make it usable again.

The userdebug RUU does not unlock /system. /system is unlocked automatically by the radio and bootloader any time you enter recovery: whether it is on a stock ROM or a userdebug ROM. We simply can't use that to our advantage when using the stock (locked down) recovery, because that recovery only gives us access to certain things. In that sense, it works similar to how /system used to work on older Android devices: Android used to have full access to the /system partition, but couldn't be utilized until it was unlocked by having access to something else (e.g., "root" access). Back then, once you became root, you had the keys to the kingdom: you could delete apps, add apps, reconfigure the system, flash a new recovery image, etc ... and at that point, root could never be taken away from you, because you would just have a rooted recovery image that would let you take over the next system image.

Now that /system is completely locked while not booted in recovery (and "recovery" partition isn't writable, period), having root access means less, because you can't write to /system from Android (or to recovery while in recovery). If we find a way to unlock the NAND, we'll essentially be able to regain those keys to the kingdom. Flashing an engineering SPL would just be the easiest way (once we find out how to make it accept the image), definitely not the only way.
[EVO 4G General] Neotelos_com:
Thread bump, I was sad it got buried as you can see here...

http://xdaforums.com/showthread.php?p=6705148#post6705148
[EVO 4G General] timothydonohue:
dumb question here, but if the flash hboot hboot.img isn't working, wouldn't that imply that there is something left over from the original/stock hboot.img that simply isn't being overwritten? wouldn't was isn't being overwritten be the bit telling everything else to lock up the house later? can that be determined, and either overwritten with an empty bit, or a 'leave the door open' code?

just throwing things out there, because i have no idea what i'm talking about
[EVO 4G General] theillustratedlife:
How does the Qik update work? It comes preinstalled in the system partition, but there's a Market update available for it.

It looks like there's an APK in both app folders:

#in /system/app
-rw-r--r-- root root 815870 2010-04-28 22:51 Sprint_Qik.apk

#in /data/app
-rw-r--r-- system system 4514646 2010-06-04 15:24 com.qikffc.android.apk

Is the new APK telling Launcher to ignore the old APK? I tried looking in com.qikffc.android.apk/AndroidManifest.xml, but it seems to be encoded in something other than text/xml.

I was hopeful that this would be a clue to defeating NAND protection from userland, but the presense of Sprint_Qik makes me think they've left /system alone and tweaked something on /data to hide the old build.
[EVO 4G General] Neotelos_com:
Are you able to get just the custom recovery onto any ROM without breaking it?

Usermode root with nand access would be great, but right now I'm looking for a custom recovery mode on an official ROM at minimal.
[EVO 4G General] Neotelos_com:
Pretty much that's how it works.
[EVO 4G General] Neotelos_com:
Someone PLEASE sticky this, I personally find this very important that a solution be found!
[EVO 4G General] shep211:
1+ This is a must.
[EVO 4G General] bcnice20:
+1 as well this definitely should be #1 priority at the moment once we unlock nand where golden
[EVO 4G General] Shidell:
I also agree, this thread needs to be sticky.

Is this accurate (for the EVO? For Android devices in general?):

mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"

I'm still working out the details of how the Android system works, but what I'm getting lost on is how current root status happens. Using toast/maejrep's method, we're pushing a custom Recovery.img--which is either flashed by the script, or flashed automatically by Android upon shut down.

(This is assuming that Android always flashes a copy of Recovery.img from the /system partition as a safeguard, ensuring upon reboot things are as expected.)

We then have full access to Boot, Recovery, and System (via Recovery). Right now we're flashing a custom Boot.img (with custom Kernel) as well as a custom System, correct? What happens to the Recovery that we're currently in after a reboot that we lose it?

I don't understand is why Recovery isn't sticking. Does the system try to re-flash Recovery.img from /System upon every reboot, and our accessible Recovery is being replaced by the default Recovery.img simply because we've overlooked it?

Additionally, assuming we have access to Recovery, we should have full access to Boot and System (as we do now), so we'd be able to flash custom Boot/Kernel, OS/ROM/System, and stick with a solid Recovery image to handle flashing in the future.

Where are we/I getting tripped up? I don't understand why Recovery isn't sticking? And if Recovery does stick, isn't that all we truly need (given the adb/ENG build) to fully unlock the EVO?
[EVO 4G General] Neotelos_com:
The Evo's system is actually #4
[EVO 4G General] Neotelos_com:
I don't know much about kitchens, etc per say but I do know about filesystems and modding.

I am right now trying to get one step further with a stock ROM that includes system changes and a custom recovery. I can't make any promises but ask for you to wish me luck! :)

This will be the next best thing to user-mode NAND access.
[EVO 4G General] Stericson:
Post has been stickied.
[EVO 4G General] MagnusRagnarok:
indeed

accent on MUST:D

Time to start warming up the new flashing machine and get used to not sleeping for nights at a time again...........:D

GO NANDROID SUCCES. seriously though crossies here.

Score....
[EVO 4G General] joeavery2:
Would it be possible to bootloader unlock the same way they did with the Nexus? windows-fastboot oem unlock?
[EVO 4G General] shwan_3:
lol, yes if you were supercid
[EVO 4G General] Neotelos_com:
I haven't gotten much of responses from toast, but I am currently working on a stock ROM (update) that will keep toasts custom recovery.

I'll work on stripping out some files when/if I get this working. :)

EDIT: Got it to flash my custom update it seems but now it just boots right to the bootloader :(

EDIT #2: I made some stupid mistakes, trying again...lol
[EVO 4G General] joeykrim:
what does this have to do with this thread, unlocking NAND partition? have you developed a method to allow writing to /system while in normal android mode?

i know originally, maejrep didn't have time necessary to devote to the two methods he puts forth.

is there anyway we can help with these? im still beginning with the HTC architecture structure.

are there examples from other phone's your referencing? certain files you'r experimenting with? is there anyway we can help out with this process?
[EVO 4G General] Shidell:
Has anyone considered what I posted as far as flashing the Recovery to make it sticky? I still don't understand why Recovery needs to be "re-flashed" every time we want to use it--is it because Recovery is flashed from /System during shut-down?

I'm about to start digging in myself, but if someone who has a better understanding could comment, I'd appreciate it.
[EVO 4G General] joeykrim:
system is not flashing recovery on shutdown.

we don't have write access to the recovery partition. therefore we can't load a custom recovery permanently.

the EVO-recovery.zip file toast created and post, temporary loads a custom recovery onto the phone. you reboot and its gone again. its a temporary patch until we can get write access to /recovery and permanently load a custom recovery.
[EVO 4G General] Shidell:
Thanks Joey. I'll keep investigating.
[EVO 4G General] bcnice20:
http://xdaforums.com/showthread.php?t=696550

Saw this over on the desire forums when your in recover mode if your hold down volume up and down at same time then hit power button it brings you into this blue recovery mode could this be of any use