Database Info

[Q] root or not to root

dmd64 1.6 firmware refurbed mt3g 1.33.0007 made gold card (kingston 2g) after sandisk2g have adb cant root
everytime i try to downgrade to 1.5 the sappimg either version to old or it simply wont recognize img and offer update. The closest ive gotten was getting a message that said wrong signature. Please someone help me downgrade so i can root
ps tried perfect spl fix

( signature fail)
i hate this word this word by HTC Bluffing eng they made a devices daid verry fast to take our money this company made by a group of lovers of money they dont care about you or me or any one
goodbye HTC
welcome chinese Huawei and ZTE ( they will give Htc verry big lesson verry soon)
i hate HTC

I have issues with HTC...but they stem from my provider. I found the best way is to use "universal androot" rooted both my hero's and have been testing various roms and updates with great success. Maybe give that a try before throwing in the towel.

ummm maybay
am i crazy, I might have lost my mind. I downloaded an app universal androot copied it to goldcard and ran the app. "woot root access gained" Then i ran the terminal app and typed su enter a# sign appeared as far as i know that means i have gained root, is this true can anyone shed light on the fact that it all seemed to easy after everything i have tried.

^ Sounds like you did it It only took me a few seconds, and it tested positive

mmmm....
xda is right up there with too much horsepower,my bangin girlfriend, and free money
I love you guys

Is it me or does the name of the thread imply an entire different topic? Idk.. I thought this thread is about something like "root or not? what do you say? what do I get, should I or shouldn't I?"
Sry, but I think it's a bit misleading.. But great it worked out for you anyway

Danielwhite28 said:
am i crazy, I might have lost my mind. I downloaded an app universal androot copied it to goldcard and ran the app. "woot root access gained" Then i ran the terminal app and typed su enter a# sign appeared as far as i know that means i have gained root, is this true can anyone shed light on the fact that it all seemed to easy after everything i have tried.
Click to expand...
Click to collapse
never install any thing inside gold card just use another sdcard and format it fat 32
and do what you want with his HTC (dirty devices)

Incredible S Full Root Successful

Ok im not sure if many people have done this yet but i managed to unlock the security of my phone and manage a full root on my INCS..
basically i followed all the steps mentioned in the alpharevx q and a thread...but made a few changes....instaed of using the optus rom i used the htc_wwe rom...and while making a gold card i noticed that instead of using mmc1 or mmc0 it worked with mmc 2 which i figured out thanks to gold card helper which can be downloaded using the market...also another tip while using the CID, instead of typing it you can simply copy it in cmd, that way it prevents mistakes( also im sure many must be knowing how to do this so i guess its redundant to mention it but what the heck )
p.s. alpharevx does not work with the native asian rom hence i had to use the other one...although its in beta stage it worked perfectly on my phone
anyways if anyone needs help lemme know

This is great! Some of these methods might be used to crack the Sensation's Bootloader, I'm going to go pass this along to the eager minds of the sensation forum, see if they can get anything out of it! Congratulations!

how do I root and S-off my incredible s?

install a rooted rom for you phone

[Q] Phone hangs during use - sometimes fails to mount /system or /data

This has been ongoing for a few weeks now. Desire S is currently running Endymion 2.2, but the same thing happened on Cyanogen and Stock roms. Phone will work fine for up to a day, then will completely freeze up during use (has happened in Browser, while entering text, and once just on the lockscreen). During the hang the touchscreen won't respond, connecting USB has no effect (no LED and ADB Devices lists nothing), the 4 buttons give haptic feedback for about 5 seconds after the hang, then nothing. Holding volume+power has no effect, but usually after about 10-20 tries or 15 minutes of doing nothing the phone will return to HTC boot screen, and sit there until I power it off and then remove the battery.
When using clockworkmod, half the time either /system or /data is not mountable (this only happoccasionally get "error mounting /cache/recovery/log"). When this is the case, formatting/factoryreset sometimes gives the "can't mount /data" error, and sometimes works.
Since switching to 4EXT the partitions are always mountable from recovery, but rebooting causes the phone to hang immediately after booting.
Current setup (which at the moment is hanging at the lockscreen)
HBOOT-6.98.2000 (PG88100000)
4EXT Recovery v2.2.7 RC5 (/system /cache and /data all ext4)
Endymion 2.2
tldr: is it possible for /system or /data to break during normal use and sometimes be unmountable? If yes, then can this be prevented? If no, any other suggestions as to what could be going on?

Reads the posts in the eMMC section at the bottom of the index thread, see end if my Sig for link
Swyped from my Desire S using XDA Premium

If you want my opinion, be drastic about your approach to this. Start from the ground up, that way you will be able to more or less narrow down the problem you are experiencing.
1. Change your HBOOT to 0.98.2000 (As you are using the revolutionary HBOOT, you will need to change this using a different method).
1a. Download HBOOT 0.98.2000 from this thread.
1b. Taken from this thread, use this method to change your HBOOT using adb. If you don't know how to use adb .. >_<.
Copy the hboot.img to your SDCARD.
In adb type:
adb devices
adb shell
su (doesn't matter if it says /system/sbin/su not found)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18​
2. Format all your partitions again using your recovery.
3. Re-install a FRESH ROM, try to avoid backups.​
Don't care if anyone thinks differently, this is just what I would do if I was having this problem.

Totally agree with the above post.
But I would suggest even more drastic approach. Restore to complete Stock and S-ON. There are Guides here how to do this. Then do a testing for a couple of days, maybe a week. At the moment when (if) this problem appears again run to your provider and insist a replacement.
IMO this way you will spare yourself a lot of nerves and troubles in future.

ben_pyett said:
Reads the posts in the eMMC section at the bottom of the index thread
Click to expand...
Click to collapse
sorry, didn't mention this in op - checked for eMMC issues when it first started happening and everything seemed okay, so I'm confident it's not a hardware fault. Not sure if there is a different problem that can result in similar, but sporadic, results.
Going to S-ON and try stock rom again and see how it goes.
Thanks guys

I checked mine and was also confident i had an ok emmc but alas, if you have the bad chip, you have a bad chip.
It may manifest it's self in different ways but eventually it's more than likely to fail. You would be wise to proceed with that caveat.
Sent from my HTC Desire

psimyn, how did it go? Also is it a telstra branded handset?

Sorry for the slow reply, finally got a response from the seller.
Handset was unbranded, bought from HK. The seller requested $40 for shipping both ways, which was apparently going to be refunded if the phone was covered by warranty.
Instead, I got an email yesterday claiming that the phone suffered a "software corruption" and that I had to pay an additional $45 for Labour and Administration. When I asked why the response was "I am just explaining to you that the labour cost and all administration are $45".
For now I just want the damn thing back, so it's been paid and they will hopefully send it today.

Unlock for other networks?

Hi,
I dont have this phone yet, I want to buy 2nd hand off some guy, but he says its locked on another network, I have myself experiences with other android phones, just wanted to ask, as I could not find any guide in this section, how to unlock the phone to other networks?

any phone service shop will unlock the phone normally charge about £10

Taysider said:
any phone service shop will unlock the phone normally charge about £10
Click to expand...
Click to collapse
Thats true, but I dont want to pay for something I could possibly do home by myself, right? I have successfully unlocked my own SGS2 to other networks in 5 minutes... So I just wanted to know, if there is known procedure for this phone either

Desire S doesn't have a way for free SIM unlock (yet).

Jack_R1 said:
Desire S doesn't have a way for free SIM unlock (yet).
Click to expand...
Click to collapse
That explains why I could not find anything:cyclops:

There might be a way, but I'm afraid of trying it, or even suggesting it. Only someone with JTAG box, or someone that can exchange the phone by warranty easily and doesn't mind it, can try such a way. But it's in my head for some time, so I'll write it, maybe it'll be useful for something, who knows.
Desire S happens to be a very close relative of Desire HD, Desire Z and MyTouch 4G. One thing that makes it a bit different from those phones is that it never had Froyo to begin with, and started its life with Gingerbread.
On all of the "cousin" phones, there's a special tool, called "gfree". This tool is very powerful in what it gives - complete and real S-OFF (unlike this phone, which gains S-OFF by editing a bootloader to skip reading the security flag, gfree changes the actual security flag), SIM unlock, etc. It's a very complicated, powerful tool, that was written for 1.5 months by cooperation of some of the best brains in the "phone hacking industry". If anyone wants to - the partial chat log of the IRC channel is available on the net to read, and for technically inclined it's a very interesting read.
gfree can't run on Desire S, since it has no Froyo, and it has too advanced bootloader that prevents it from doing what it does.
What I'm pointing to is: if anyone could flash old DHD Froyo build on Desire S, including older bootloader, and actually make it boot - gfree could be able to run and do what it does, turning Desire S into SIM unlocked and true S-OFF phone. Of course, since flashing non-original bootloader is involved, it's a VERY risky task that can lead to a bricked and non-functional phone. I hex-compared DHD and DS bootloaders of the same version once, and saw almost complete match, but it wasn't 100% complete, and I can't be 100% sure that they're identical.

I can confirm that the S-OFF flag resides at the same offset on Desire S. Not sure about the SIM lock since my device doesn't have such, so cannot compare. But the method should work if you do it manually - dump the mmcblk0p7 partition, hex edit according to the data that you can find in the gfree source code and flash back. But if you are not familiar with such operations I would not recommend messing with this stuff, better use xtc clip
Sent from my HTC Desire S

Hmm, you just gave me an idea. If gfree source was modified to make it skip the whole eMMC-powercycling procedure (useful for S-OFF-ing from scratch, but not working since the binary driver doesn't seem to load under GB) till the point where it actually writes the S-OFF and SIM-lock flags (remarked "// Guhl's part7 patch/backup code"), then it could be run under existing S-OFF on DS, turning it into permanent S-OFF and SIM-unlocking it. I have no SIM lock either, so I can't test it, but having a permanent S-OFF is a good bonus.
Worth the try?
I might try to compile and run it, just need to install some Linux VM, since my old VM is gone for a long while, the last thing I did with it was modifying Enomther's code for Nexus One, at CM6 times .

For S-OFF it is pretty simple and can be done manually (although I never tested but it is there).
Dump mmcblk0p7 with dd, open it with HxD, browse to offset 0xa00 and change the value from 01 to 00. Then dd back and you should have permanent S-OFF.
CID can be found at offset 0x200. Just replace the HTC__XXX with 11111111
For the SIM unlock the range 0x80000 to 0x82ff0 should be modified as follows
offset............................value
0x80000..........................78
0x80001..........................56
0x80002..........................f3
0x80003..........................c9
0x80004 to 0x807fb.....all zeroes
0x807fc...........................49
0x807fd...........................53
0x807fe...........................f4
0x807ff............................7d
0x80800 to 0x82ff0......all zeroes
This will disable a microprogramm used for SIM lock related connection to the carrier.
This can be done manually on a rooted device. But I doubt there will be testers available and I personally do not need to do this since I am OK with the "fake" S-OFF. But if somebody is eager to try please share the outcome. Backup the dumped partition just in case!
BTW for me is much more interesting how to get rid of the RELOCKED flag, Do you have any info on this subject Jack? I know Wildfore S got a solution but it not sutable for emmc devices unfortunately...

amidabuddha said:
BTW for me is much more interesting how to get rid of the RELOCKED flag, Do you have any info on this subject Jack? I know Wildfore S got a solution but it not sutable for emmc devices unfortunately...
Click to expand...
Click to collapse
"RELOCKED" flag only appears if you don't flash RUU after relocking, doesn't it? In this case it's not very useful to have anything specific for it, especially that HTC database already contains the record of unlocking.
In any case, I have no idea where to find it, but it could reside on the same /misc partition, and if someone would be willing to unlock and relock the phone, dd-dumping partition 7 under temp root before and after the relocking - the results can be analyzed, and this flag could be taken care of, if found.

Jack_R1 said:
"RELOCKED" flag only appears if you don't flash RUU after relocking, doesn't it?
Click to expand...
Click to collapse
Sort of. It disappears when downgrading to a hboot version that is not supported by htcdev.com, but if you do an OTA update it comes back. It is not on the misc partition and I looked through a complete emmc dump to find some trace but HTC guys did hide it well this time. I think that it is on the same partition mmcblk0p7 because this is one of the 2 partition not getting overwritten by the RUU (the other one contains basic info such as MAC address etc.) Unfortunately I have no "clean" dump to compare with. And if this can be disabled then HTC will never prove that the unlocktocken was actually applied on the device even if there were a request for one at their website...so no evidence for warranty void

I see. I can have a clean dump - my wife's phone was rooted using Revolutionary, and was never HTC-unlocked. I'll try to take it tomorrow and post it for you to hex-compare. In addition, I'll try to create the mini-gfree tool, to hopefully give people means for simple SIM-unlock (true S-OFF is less important for most, I guess).

Just thought of something. Till I take a hex dump of partition 7 from my wife's phone, you might have use for the attached file. It's a full partition 7 backup from my MT4G by gfree, before any flags were altered. MT4G's latest bootloader also supports unlocking, most likely using the same encoding for it.

I used the easy way out and compiled Android binary using NDK. Works.
Ok, tested it on my wife's phone with Eng HBOOT 0.98.2000
Good news: it doesn't kill the phone.
Bad news: partition 7 is write-protected even under S-OFF HBOOT. I guess the eMMC powercycling is required, since it's still being protected by radio. That also answers the "RELOCKED" status bit question.
Oh well, pity. Anyone feels like creating a Froyo super-barebones ROM for the phone? It would only need to boot the kernel and run ADB daemon...

Damn, I knew this was the right answer. Started looking at what they do in DHD section, quickly found this:
http://forum.xda-developers.com/showthread.php?p=20950143&highlight=attn1#post20950143
They do EXACTLY what I suggested.
This means that -
1) Newer HBOOT doesn't prevent gfree from functioning.
2) If the same CWM recovery, based on old kernel, can be booted on DS and can mount the partitions - gfree can successfully run in it, providing SuperCID and SIM unlock, and possibly S-OFF even for HTCDev-unlocked phones (since they can flash recovery, which is enough for gfree).
Now, can I get some hand in finding that old recovery they use (Froyo kernel)? Even if it is for DHD? I hope it'll mount the partitions and have ADB, that will be enough.
[edit] OK, downloading AAHK, hopefully the CWM in question will be found there.
[edit2] Damn x2. Doesn't work "as is" - none of Froyo-based CWM recoveries boot to the point where adb daemon is running. I guess there's no choice but to compile this thing from sources - no way around creating a booting Froyo kernel for DS. Shouldn't be too hard for someone who knows what he's doing, unfortunately I'm not that "someone", since I didn't work with kernels before
[edit3] Or another option, which I'm not sure why it wasn't done till now: since the failing module is wpthis.ko and it fails on something really non-important (missing link for one of the libgcc procedures), but its source is out there - it needs to be compiled against Gingerbread kernel to be made compatible. And maybe it'll be enough to make it work under Gingerbread.

Jack_R1 said:
Bad news: partition 7 is write-protected even under S-OFF HBOOT
Click to expand...
Click to collapse
Yep it seems it needs a true Radio S-OFF. Since it is only a one bit change something else comes in mind. There is a fastboot command thjat can write directly to the emmc and may change the flag despite the write protection:
Code:
fastboot oem mb [offset] [bitsize] [value]
[I]example[/I]: fastboot oem mb 9C068490 1 30 [I]{that can be found on downgrade guides for some devices, but maybe it requires Froyo as well...}[/I]
I guess the right offset can be found from a complete emmc dump.
I believe your logic about the gfree tool is absolutely right, but I have no idea what the eMMC powercycling does and how to make it on the Desire S. Maybe someone more knowledgeable will solve this easily but this device is quite old and there are more attractive targets that the devs are focusing on (like the One X).
Btw, thanks for the partition, a have looked through it but nothing came out (except that the star is one sector shorter (useless info ) Anyway I would like to ask you to remove the attachment since it has some sensitive info

Afraid that I can't add anything 'knowledgeable'
but my device was made s-off via xtc clip so fully unlocked, networked, Sim, hboot etc
So if a dump of any of my partitions could be useful then let me know
Sywepd form my DsereiS

Yes, I believe that comparing your partition 7 with the original one can confirm the locations and changes required.
Amidabuddha, the attachment is removed. Thank you. Since you have a full eMMC dump, could you please look up the address of the secuflag for me? I'll try the fastboot command.
I already have Ubuntu VM running, I just need a good tutorial for setting up the system for compiling a Sense kernel - all tutorials focus on AOSP/CM. If anyone has anything to suggest, I'll be grateful. Otherwise I guess I'll try to break my own teeth on that... And if it'll succeed, I'll try to recompile wpthis.ko (the kernel module that powercycles the eMMC), linking it to Gingerbread kernel and hoping that it can run with this kernel.
The eMMC powercycling achieves one interesting thing: since eMMC write protection flags are set by PBL or baseband (not sure which of them), once set - they'll protect the partitions. When eMMC is powercycled, all the flags are cleared - but the system doesn't know it, and they're not set again, which effectively disables write protection, allowing to write to protected areas - one of them being security flag, that opens the access for good.

If you could give me the exact command to dump that partition I'll then have a go
Sywepd form my DsereiS

@Ben
Thank you for this suggestion! I already have a dump from an xtc clip unlocked device, thanks to a fellow user here but I think it will be usefull to have more sources to compare. The dump is made by dd, connect to PC and type in cmd:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/part7.img
the same can be done in a terminal emulator directly on your device. Send me the file by PM, since your IMEI is there (you are warned, and it is your call )
@Jack
The command should be:
Code:
fastboot oem mb 02E74200 1 00
I hope that oem commands grant write access, but in worst case it will give an error
As per the kernel use the CM guide with a clean source downloaded from htcdev.com. The commands are the same. For the config just see in the /arch/arm/configs folder of the source for saga_defconfig or similar
You can check the second part of this guide as well. Starting from Downloading a prebuilt gcc
When you have the zImage there you can pack it in a stock boot.img from any RUU using the Alternative method from this guide

[Q] HTC One X Att Unique Issue (Soft Bricked+More)

About a year ago I installed Cyanogenmod 10.2 (bootloader unlocked, S-off, custom recovery - TWRP), everything worked great until about 2 weeks ago. I noticed that certain apps/data were getting corrupted/deleteing themselves. Finally a couple days ago it just stopped booting to the OS. I can still access hBoot and TWRP recovery, still mount most of it and access via USB/PC, but my E: /data partition will not mount.
I have been doing research the past couple days, trying multiple things, but I'm worried about trying somethings in fear of making it worse. I have basic knowledge, but no expert. Here are my current software specs:
HTC One X (ATT Version)
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL (Somehow this changed itself back ok)
HBOOT-1.14.002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
TWRP version 2.3.3.1
I have tried running the RUU, but its not detecting the phone, and I also read this is dangerous is you don't have S-Off. Is there a way to delete the /data partition and remake it? I have backed up all relevant data so I can do whatever needs to be done.
Oddly "fastboot devices" is not detecting my phone and I'm getting a windows popup saying its malfunctioned, yet I can boot into TWRP and mount it and transfer files just fine (except the un-mountable /data partition).
I have no clue where to start, and what order things need to be done in, with which version numbers. If anyone can help I would truly appreciate it! :crying: I am tempted to run it over in my car (several times) and have insurance replace it (so they can't tell I voided the warranty, lol ) if I cant get it working. I would be glad to supply any other info you might need about my situation,
Thanks in advance for your time and effort, this is such a great community. -- Eclipsys

I think it would be wise u don't run it over. Haha..anyways..sounds to me like your SD cards got corrupted.
---------- Post added at 12:42 AM ---------- Previous post was at 12:40 AM ----------
Are u saying that u somehow lost s off?

Definitely don't run any RUU while you're s-on, that'll brick the phone. What OS are you running on your PC?
Sent from my Evita

I've been trying to get my One X working for a couple days now. I'm using Windows 8. It seems like my 2 biggest issues is 1: That my /data won't mount, its corrupted somehow, and 2: when in fast boot it wont connect to the computer, so I have no access to adb which is a huge issue. As for the S-On, yeah, somehow I lost it, but that could be fixed if I could get windows fastboot working.
I have tried different cables, its not that (In TWRP I can mount it and access my files, so I know its possible to get to the OS). I have installed and re-installed (several times) HTC Sync. When I plug in the USB cable it makes the chime sound, and shows the popup saying that the device plugged in is malfunctioning and Windows does not recognize it. I was recently reading that some people have had problems with the Sync base driver and suggested downloading the Windows 7 driver and using that, also no success. In the Device Manager it shows the phone with the error Code 10.
Quote from Microsoft website -- "The Code 10 error pertains mainly to hardware and device driver issues or to compatibility issues between hardware drivers and additional software that is installed in Windows."
It suggests a couple possible fixes, one being editing the registry, which I'm about to try, even though I doubt it will work. After that I will try running adb on my Ubuntu PC, but in all honesty, I'm just taking shots in the dark.
As for the corrupt partition, I have the feeling that if I can get it back in working order I should then be able to use a backup to get it booting to OS. As far as I know the /data partition is on the sd-card with all the other partitions so that leads me to believe that its not the whole sd-card that's corrupt, somehow just that part...?
I have no idea how it got this messed up. But if anyone has suggestions or experience with either of these matters, I'm listening.

The corrupt data partition is going to be a bit of a hurdle to get over I think. If it is actually corrupt (which it looks to be) there's not really a lot you can do. As far as getting your fastboot connection working, there's a drivers thread in our General Section, you might need to scroll down a bit but it's there.
Sent from my Evita

No luck with alternate drivers, but I do have it working on Ubuntu, so a minor win. What I'm looking into now is using the adb shell (BusyBox) to possibly use fdisk to format the partitions and then reset them up. EDIT: Not going to work, virtual partitions inside virtual partitions... I paid for the insurance so getting a new one is really only going to cost me a week without a cell, but its more of not wanting to admit defeat, lol.
Anyways, still looking for an alternative. Cant flash an OS or a backup until it is seeing a /data partition. All ideas are welcome.
I did see a program written by someone called Nocturnal that is supposed to fix corrupted sd-cards, but it seems all his download links are '404'. - If you have it or know where I can get it, message me.

Unfortunately I think the insurance might be your only option. Nocturnal's fix is for the sd card only, which is completely separate to the/data partition.
Sent from my Evita

Did you remedy it,or are you sending it in?