yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] edbica2000:
1. If I make upgrade to froyo with odin can i make the same steps to downgrade him to 2.1? (because title say downgrade from official froyo who means from kies).

2. I have problems with camera (not open) and with scroll bar (not open) after i make download and install thetering from market:((

I reinstall camera but problems stiil there. That is the final choice (downgrade-upgrade again from kies) to try something before to send to service.
[Galaxy S I9000 General] ce300:
I have problem. In downloading mode computer not regonize phone. HELP.
[Galaxy S I9000 General] JJEgan:
Open Kies and let it run in the background connect phone see if it finds drivers .

jje
[Galaxy S I9000 General] keepcalm:
Thank you so much for this post, saved me hours of searching.
[Desire General] rockingx10:
Hello guys. My phone just came from repair cuz I think I bricked it and sent it to telus and they sent me the phone with 2.2 on it. I used revoked root and brick the phone. So my question is can I delete all the files that's in memory card and put it on my phone? Cuz there is leedroid file on my sd card or it doesn't matter? I can just put my memory card on phone without deleting anything. Pleasse let me know. Cuz I don't want my phone bricked again. So is it safe to put sd card on phone or delete all files and put it on phone
[Desire General] rockingx10:
Anyone?
[Desire General] rockingx10:
Wow can't believe people in desire forum here is soo ignorants
[Touch Pro2 CDMA] minikirchner:
Hey guys. I have the new XDAndroid 11/8 update and it seems to working great. I have had an issue that started before that update and it is pretty bad. Every time I make a call, it says dialing, the 3G logo disappears and then it says call ended and the 3G icon comes back. The whole time, the bars for my service are bouncing between none and full. It has the same problem with text messaging. Data seems to be working fine. I can get on the marketplace and get emails and such. It just started randomly and I don't know what may have caused it. Thanks for any help you can give.

I have a Sprint HTC Touch Pro 2 activated on Boost Mobile.

It does the same thing in Windows Mobile so maybe it's an issue with Boost Mobile or a hardware issue? I go to text or call and the service will bounce between full bars and none and sometimes it will switch to roaming mode.
[Fascinate General] jrobinsky:
So when I install "Super Clean ROM" by JT, my phone does not vibrate when I get a text message, only when I get calls. Any ideas what causes this and how I can fix this?
[Fascinate General] CouchSpud:
I don't have an idea to fix your problem, but I do have an idea of where you should have posted this.

General section.
[Fascinate General] jrobinsky:
well The rom was developed by JT so i figured this was the right section for it, i can never tell.
[Fascinate General] Not_So_There:
The super clean rom installs a replacement for the mms/text program. By default the vibrate setting is not turned on in its notification settings.
[Fascinate General] jrobinsky:
oh god its that simple? lol jeeze thanks
[Fascinate General] TheBadBen:
Ask the question in JT's thread maybe? I'm not trying to be a smartass here. If you start a thread with a question, then according to the rules, it does not belong in the development forum. If you have a specific question about a ROM, why not put it in a thread that you know the dev will read?
[Fascinate General] jrobinsky:
sorry, i guess im not too bright. I just created a thread and hoped someone would help me.
[G2 and Desire Z General] Ssantos6981:
The most I ever had was about 1.3 free. I was hoping for something like the galaxy where the onboard mem could be used for whatever. Where is the extra 2.xxgb of space?
[G2 and Desire Z General] dilfatx:
You a little late with this... Search the forum.
[G2 and Desire Z General] Ssantos6981:
Can't search through xda app. Would be a great feature though. Figured if someone would spend the time to tell me to search they would just give the update. Maybe I will turn on my computer and check it out. Not that important though, have plenty of sd space still.

Sent from my T-Mobile G2
[G2 and Desire Z General] Bishybob:
From the main screen hit the"more" tab on the far right and the search option is in there.

People have discussed the issue until blue in the face. If you do a search you'll see thousands of posts about it. The general consensus is that the space is there, just not partitioned. It is being reserved for future updates, etc. There's more detail but that's the gist of it.
[Captivate Q&A, Help & Troubleshooting] jj8811:
I'm not sure if this would be considered "bricked" or not so I'm not sure what to search for in the forums, so sorry if this has been asked to death here already.

For some reason today, my phone wouldn't install apps successfully anymore, so I turned it off to reboot in hopes that it would solve the problem. But ever since, I'll turn t on, and it'll take me as far as the galaxy logo, and then just shut off again. I've tried taking out the battery, the sim card, etc. and it still won't work.

Any help? I've had the phone for almost two months now, so I can't exchange it, so I'm hoping it's not just dead. The green charge icon still shows up when I plug it into my charger, so I don't think it's completely dead...
[Captivate Q&A, Help & Troubleshooting] mcord11758:
Have you rooted your phone? Have you flashed any roms? If not at&t will replace under warranty. If you have tell me what you have done.

Captivate

Cog 2.2
[Desire HD Android Development] sfjuocekr:
[GUIDE] Root, flash a custom recovery and/or S-OFF your Desire HD the "easy" way!

PLEASE DO NOT HOST MY FILES ELSEWHERE ALSO REPORT ERRORS ABOUT IT HERE AND NOT IN ANY OTHER THREADS!

UPDATE: Uploaded a new version with a temporary fix for if not working properly on the latest OTA?

!!!WARNING!!!

ONLY flash the bootloader (HBOOT) aka "S-OFF" if you understand what it is, what it does, what it can do and how it can brick your phone if flashing it fails.

I can not be held responsible if your phone bricks, makes nukes drop from the sky and/or makes your wife pregnant.

Assuming you have the Android SDK (adb) in working order, some basic knowledge of how to use it and experience using the console for those cases something does go tits up.

=====

Requirements: Android Terminal Emulator (from market), the archive attached to this post and a way to extract it to your SD card (file manager, PC, etc).

VISIONairy+ r12 (or higher) is as of v0.5 ONLY needed for rooting your phone, if you already have root you can skip this!

Download and extract the archive to the root of your SD card and read the included instructions (RTFM.txt).

If the first and second MD5 sums match, HBOOT is flashed correctly.

If the first and third MD5 sums match, HBOOT is not flashed at all and your phone still works like nothing happened.

If the first does not match second or third, something went wrong and you should NOT reboot your phone but seek help on the forums here!

In the last case, you could first try the hboot script again if that doesn't work something went awfully wrong and you should report back here ASAP but whatever you do ... DO NOT TURN OFF YOUR PHONE

=====

Credits goto all who made this possible: Scotty, tmzt (eMMC write), Paul (MoDaCo) (VISIONairy+ root) and adwinp (first working S-OFF post).

(If I left some person out of it just sent me a message and I will correct it)
[Desire HD Android Development] sfjuocekr:
CHANGELOG (new to old):

Revised scripts.

Failproof way of making kernel module.

Added check to see if the kernel module actually loaded correctly.

Reworked the scripts, more fail and fool proof :)

Updated the check script to check the kernel module first.

Added scripts to flash/restore recovery.

Got rid of not found errors for good?

Reflected the error message from loading the module is actually ok, polished the first post and RTFM.

Changed the way md5sum is invoked, now trough busybox and this should work for people who had problems with "md5sum: not found".

Fixed a major typo.

Updated with versioning, corrected some textual output and added some extra info to RTFM.

Cleaned up the first post.

Changed hboot script to reflect the original MD5 sum.

Removed recovery, get it yourself.

Revised scripts to be more fail proof.

TODO:

Polish textual output properly.

Proper check to see if kernel module loaded or is loaded already.
[Desire HD Android Development] Thyrus:
Good morning :)

What recovery.img are you flashing in the process btw?! care to let us know?

since you take a backup of the original bootloader, maybe it would be handy to create a "revert" script also, where you flash back the original recovery and original bootloader :) in the event that we may need to you know...

the script would then go like this

dd if=/sdcard/DHD/hboot_orig.bin of=/dev/block/mmcblk0p18
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_check.nb0

dd if=/sdcard/DHD/recovery_orig.bin of=/dev/block/mmcblk0p21

md5sum /sdcard/DHD/hboot_orig.bin
md5sum /sdcard/DHD/hboot_check.nb0

at least thats what i think... unless the file .nb0 and .bin matters in the if=-- of--- command:)
[Desire HD Android Development] afrcom15:
EDIT**

Read and check everything at least 4 times, ask before you reboot your DHD if unsure about absolutely anything. This process worked for me after some stupidity on my part.

Again, this works but CHECK everything step of the way.
[Desire HD Android Development] 50chickens:
did that happen using this guys script? or another way?

im holding off flashing hboot till things are a bit more settled. its hard to resist though.
[Desire HD Android Development] Thyrus:
i have modified the script used by sfjuocekr (so that it doesnt flash the recovery, as I see no point in that at the moment) and would rather flash from fastboot

and the script works and I can confirm s-off success
[Desire HD Android Development] madindehead:
I think it's safer doing it via the VISIONary method. That's how I.did mine, and zero issues. I don't like how this says don't reboot if the checksums don't match. That's just asking for trouble.
[Desire HD Android Development] dr.m0x:
Yeah too many people rush into dangerous stuff like flashing to hboot without understanding the risks properly. I was one of those people. I am very lucky that my flash went smoothly. Feel for you.
[Desire HD Android Development] Thyrus:
actually, thats BS, excuse my french.

The checksum is an extra security measure implemented to verify that the data flashed and the data that should have been flashed remain integrity. this way, you can verify in 2 steps:

1. The file you downloaded is not currupted in any way

2. The file (bootloader) flashed has flashed correctly, prior to reboot.

so actually, it is something ON TOP of the usual scripts seen here to ensure you dont brick. I need to side with the creator here.
[Desire HD Android Development] insty:
Take it back to the shop saying it died and get a replacement :3?
[Desire HD Android Development] keemyb:
Well I used this method and the checksums returned were both "not found" and everything started force closing, I started to accept the fact that my phone could be bricked, but on reboot I was fine!
[Desire HD Android Development] panyan:
does this work as reliably as the first method?
[Desire HD Android Development] Thyrus:
i modified the scripts and included 2 more tests as well as deleted the flash of the recovery.

I can confirm the pricinple works fine, but i didnt see the point of flashing the recovery i must say. as I will fastboot flash the recovery when we have a "proper" one :)
[Desire HD Android Development] dlads:
I've done the permaroot and deleted visionary, so when my phone boots up now it is rooted and i have access to setcpu and such and i can change it, like the sliders, i can also use other rooted programs too.

What benefits do i stand to receive if i perform this s - off root? please.

And from what i've said am i set to do this?

Thanks.
[Desire HD Android Development] ainmosni:
S-Off is needed for a custom recovery image and custom roms. Essentially it turns off the MMC write protection and signature checking permanently.
[Desire HD Android Development] AndyCr15:
Where can the modified script be found?

There seems to be little take up on this so far, I guess because it's so risky still?
[Desire HD Android Development] Thyrus:
Andy,

I have composed a comprehensive how-to in german for my "home-forum" after testing it.... so not sure how useful it would be for you non-german speaking ppl. but here is the link for convenience

http://www.android-hilfe.de/root-hacking-modding-fuer-htc-desire-hd/53959-guide-permant-root-mit-austauschen-des-bootloaders-visionary.html

you can manually edit the script from the creator here and delete THIS line

dd if=/sdcard/DHD/recovery.img of=/dev/block/mmcblk0p21

to avoid flashing the recovery
[Desire HD Android Development] afrcom15:
Here's an update on my sorry situation

CPW say send it direct to HTC, there gonna know aren't they. Phone is completely dead, no options left I'm afraid.
[Desire HD Android Development] Evostance:
a) Send it to HTC, they fix it for free

b) Send it to HTC, they fix it and charge you

c) Send it to HTC, they say they won't fix it
[Desire HD Android Development] Doktaphex:
Statutory consumer rights may come into play here my boy. I know that you broke it, but if you're comfortable with lying to them then I suggest you bring this up:

The retailer’s obligations

If there is an obvious fault with the item at any time within the first 6 months and it has not been caused by wear and tear or misuse, your first port of call must be the shop you bought it from. They have the responsibility to put the matter right, and should not evade this responsibility by referring you to the manufacturer in the context of a guarantee or warranty.

EDIT: This is one of the main reasons I take out insurance on my phones. If it breaks, tell them you lost it. Technically still lying but I'm paying for the privilege of that lie, and I have never had to lie to them.
[Desire HD Android Development] Stanimir Komitov:
2.6.32.21 with kernel 0.0.1; 4.4.0 (GCC).

Unfortunately I'm not sure how to do that - invoking the hboot. Sorry for the stupid question.
[Desire HD Android Development] sfjuocekr:
Well do you still have the module from your previous root? If so you can insmod that the same way you did in that tutorial.

With invoking the hboot script I meant:

sh /sdcard/DHD/hboot

after you insmod the module you previously used.
[Desire HD Android Development] Stanimir Komitov:
Yeah, it's still there. By insmod you mean replacing the hboot from the tutorial with the one from the DHD folder or something else? Thanks a million for the help!
[Desire HD Android Development] sfjuocekr:
No the module is the .ko file.

What you need todo is this:

Locate the .ko file or copy it to the DHD folder from my archive.

Then insmod it like this:

su

insmod <location of .ko file>

Example:

insmod /sdcard/DHD/wpt.ko

After that it will tell you function not implemented and you can continue:

sh /sdcard/DHD/hboot
[Desire HD Android Development] Stanimir Komitov:
It returned again "exec format error" after the insmod command. I did as you suggested:

su

Insmod /sdcard/wpx.ko
[Desire HD Android Development] sfjuocekr:
And are you 100% sure that module worked before? And are you 100% sure no options are checked in VISIONairy+ like auto temp root on boot and auto r/w on boot?

edit: the exec format error means that it was not for the current kernel and you can edit the module with a hexeditor to fix this.

Or you can do this uninstall and reinstall VISIONairy+ then do this in terminal:

su

rm /data/local/wpthis-lovinglymadeforyoubymodaco.ko

Now perform the permroot using VISIONairy+ again and it should place the correct module in /data/local afterwards the hboot script should work:

su

sh /sdcard/DHD/hboot

Assuming you already did check and backup earlier.
[Desire HD Android Development] Stanimir Komitov:
Absolutely. I was able to remount with adb before to remove the system aps. No options were chechked in Visionary, 100%. The exact steps were followed for both guides. I've changed my sd card today with 16gb, but its content was 1:1 copied, aftet that I went through this guide. I doubt that this can have an impact.

Edit: yes, check and backup are performed. Will try your hint on my pc.
[Desire HD Android Development] sfjuocekr:
Could you please attach the wpx.ko file you used and attach a screenshot (ShootMe on market) from the cat /proc/version output?
[Desire HD Android Development] Stanimir Komitov:
it returned now "operation not permitted". The .ko file was successfuly removed and reboot followed after the permroot in Visionary. I'll attach the files requested when i get home.
[Desire HD Android Development] sfjuocekr:
If you get operation not permitted you are not root so invoke su first ;)
[Desire HD Android Development] Stanimir Komitov:
pff, correct :) but still the "exec format error" comes out with su.

I took 2 screenshots, but the xda app refuses to attach them. Will send them in a while.
[Desire HD Android Development] sfjuocekr:
I have updated the first post with a new version that is abit more fail/fool proof.

Be aware that I have no DHD at hand right now to test it fully, I did syntax check to the best of my ability. So there might be problems with it, but those should not be vital into destroying the world or your phone.

If any problems arise please report them back for me to fix those issues as soon as possible.

For those people who can not wait for a fix I have added the v0.4 version to this post, which should work fine.
[Desire HD Android Development] Stanimir Komitov:
as requested...Thanks once again!

edit: the 3rd snapshot is when trying to sh /sdcard/DHD/check with v0.5.

I've tried placing the wpx.ko file in the root of the SD card and in the DHD folder.

Same output.
[Desire HD Android Development] sfjuocekr:
Thanks for pointing out the error in my script, use 0.4 for now until I fix it ... cooking diner atm :p

But you should already have the S-OFF bootloader? You must have used fastboot to flash that OC kernel and then mounted system r/w to copy the wireless module?
[Desire HD Android Development] Stanimir Komitov:
:)

Correct. Yes, indeed i've used fastboot to put clockwork.img and then flashed this OC kernel, however I'm not able to overclock more than 1 GHz. I'm not sure if went successful, but this is different story. Stil, I expected to have adb remount permissions.

edit: 1.5 GHz is now working, strange though...
[Desire HD Android Development] toddyc:
If i do a factory reset from the bootloader will i loose root and s-off ?
[Desire HD Android Development] zeyon:
yes I think the probleme come to version of my Hboot 0.85.0004, the root and the s-off are for the hboot 0.85.2007
[Desire HD Android Development] sfjuocekr:
If you used fastboot to flash clockwork and the kernel your bootloader is already S-OFF.
[Desire HD Android Development] sfjuocekr:
No factory reset will clear userdata and cache not system.
[Desire HD Android Development] sfjuocekr:
No it should not be a problem really, depending on the kernel used.

Can you post the output after manually loading the module? And the output of:

dmesg |tail

after loading the module?
[Desire HD Android Development] zeyon:
I don't understand "charge the module" dmesg |tail

How ti charge this module?

My kernel version is 2.6.31.21-g198e6de
[Desire HD Android Development] cturbos:
to the op

why do i get this:(Exec format error) and the first and third #s correct but never the first and second.everything else is OK.

thank you
[Desire HD Android Development] sfjuocekr:
That kernel version should work with VISIONairy+, why it crashes I don't know thats a question for Paul.

To load the module manually I can not explain right now, we are playing CIV5 atm will help when Im done with that.

It's because the module failed to load correctly, did the permroot work for you?

Please post the output of:

cat /proc/version
[Desire HD Android Development] cturbos:
l/v 2.6.32.21-gf3f553d (htc-kernel@and18-2) gcc version 4.4.0 (GCC) #13:24:11 CST 2010.

thank you, and yes the permroot working fine.
[Desire HD Android Development] sfjuocekr:
@cturbos:

Try the "wp_gf3f553d.ko" file attached to this post, put it into the DHD folder and in a terminal do this:

su

insmod /sdcard/DHD/wp_gf3f553d.ko

@zeyon:

Try the "wp_g198e6de.ko" file attached to this post, put it into the DHD folder and in a terminal do this:

su

insmod /sdcard/DHD/wp_g198e6de.ko

Does it say function not implemented now?

dmesg |tail

Should show deferred resume complete, if that is true you can continue with:

sh /sdcard/DHD/check

Just ignore the error the hboot script throws at you about the module loading, you just did it manual.
[Desire HD Android Development] sfjuocekr:
Will post v0.5 tomorrow after some further testing on a DHD, I'm too sleepy right now :p

I will add a more automated process of checking the kernel module that will update with the right string to get rid of the exec format errors. As it seems using the kernel module left behind from the VISIONairy+ root doesn't work for some people.
[Desire HD Android Development] 50chickens:
btw, you should put in a test for /system being rw

the first time i did it i forgot to put mount /system rw after reboot and when i tried to run /sdcard/DHD/hboot i got the exec format error. i had to uninstall 'permroot' and then reboot and then re-permroot with the option checked. after that everything worked ok.
[Desire HD Android Development] :
the system doesnt have to be RW, nothing is written to the system partition. the exec error is a failure of a different kind (when insmod cannot be completed for whatever reason)
[Desire HD Android Development] ccombe:
followed the instructions letter by letter - worked perfectly first time...

now what to do with the new found access? :)

I am not into this kind of stuff but since I follow instructions and everything has worked so far I am keen to find out what else I can get my hands on...

excellent instructions..
[Desire HD Android Development] cturbos:
OP

thank you very much indeed,you made my day.;)

works very good,do i need Clockwork mod recovery?

thanks again
[Desire HD Android Development] tihobuf:
If the first and second MD5 sums match, HBOOT is flashed correctly.

If the first and third MD5 sums match, HBOOT is not flashed at all and your phone still works like nothing happened.

If the first does not match second or third, something went wrong and you should NOT reboot your phone but seek help on the forums here!

In the last case, you could first try the hboot script again if that doesn't work try the restore script to restore back to original.

If that doesn't work something went awfully wrong and you should report back here ASAP but whatever you do ... DO NOT TURN OFF YOUR PHONE

I have tried but keep getting mismatch MD5 sum 1st and 3rd second is one which is correct :( any help to make it work.

Have restored factory settings, formatted SD card, tried scripts again still no luck. Kernel 2.6.32.21-gf3f553d htc-kernel@and18-2 #1

Build: 1.32.405.6
[Desire HD Android Development] superdaddy:
sh: Can't open /sdcard/DHD/check

can someone help here please.
[Desire HD Android Development] sfjuocekr:
You can use the same instructions I wrote some posts back, download the module attached to that post which matches your kernel gf3f553d.

I'll change how we handle the module in version 0.5 to get rid of this error.
[Desire HD Android Development] sfjuocekr:
You extracted the files to the wrong location, check the root of your sdcard if it has a DHD folder with some files in it.
[Desire HD Android Development] sfjuocekr:
I'm changing the way the module is used soonish when I get a DHD to test on.

Maybe if you check the mount system rw option it loads correctly but then again the exact same module is used in my scripts so it should work too.
[Desire HD Android Development] superdaddy:
Edit.. sorted.
[Desire HD Android Development] sfjuocekr:
You don't need CWM yet, but it is a nice addition if you want to start testing ROM's right now.