yashsingh1/xdaforums huggingface dataset:
[Sprint HTC EVO 4G LTE] OstrichSak:
Just a heads up to anyone who finds this thread searching for the same thing... this link worked perfectly for me. I downloaded it to the phone and then clicked it to run like a regular apk and didn't even need to go through the steps the OP lists and it worked fine for me on a rooted Evo LTE on the stock ROM. I've got my 3D Gallery back! :cool:
[AT&T, Rogers HTC One X, Telstra One XL] meo0o0111:
Hello. I recently purchased an HTC one X. It has AT&T and I was wondering why there are two different HTC one X forums. I am also double checking that this is the correct for for me to look for instructions to root my phone. Thanks in advance for the help.
[AT&T, Rogers HTC One X, Telstra One XL] Pirateghost:
its really not that confusing.

there are essentially 2 different One X's

INTERNATIONAL VERSION which has QUAD CORE

LTE VERSION (at&t, Rogers, Telstra, etc) which has a DUAL CORE

COMPLETELY different phones....

if your phone says AT&T up by the earpiece, you are in the right forum. check the stickies in these very forums....
[LG Optimus 2x] cookieyeah1:
i'm now using the cm7 built by temasek.

A serious problem is that my pc can‘t read my o2x phone when i use that rom.

however,,if i replace the stock kernel with an etana one or use other rom like cm9 or v20q,everthing works well......

and the miui also has the same problem...

i'd like to use a stock rom and i also want to have it read by my pc..

how should i do with this problem?is there anyone having the same problem?
[LG Optimus 2x] LarsPT:
Why would you want to use stock ROM?

I have done benchmark before and after flashing vadonka's kernel and specially I/O write speed improves drastically. You have non-OC'ed versions, so I don't really understand what you have got to lose.
[LG Optimus 2x] cookieyeah1:
Maybe vadonka's kernel is great. ..but i do think the launcherpro works better on the stock kernel than on the etana. ...also the boot time increases after flashing the etana
[LG Optimus 2x] aragorn7:
If what you are trying to do is to push files to your phone from your pc, then try following the tip from XDA-TV. It worked well for me.

http://youtu.be/UI70UYug_zQ
[Huawei Ideos X5 U8800] typci:
Anyway, I was using Miui V3 2.4.20 [2.6.35], and Google maps wasn't very happy with it. So I decided it was time to move on to the .32 kernal version, since the developer was going that way too. Downloaded a stock rom with .32 kernal, went to the pink screen and flashed, and then boot loop.

Luckily, I'm awesome, so my phone won't die on me. Tried flashing some roms through clockwork, no bootloop, just stuck at huawei logo. Tried flashing some stock roms, and at about 98% done flashing it goes error. Some parts get flashed causing my recovery reverts to stock, but I'm still stuck at the huawei logo.

Also, in clockworkmod I get errors mounting data and emmc, so that might be a problem. Other partitions mount fine.

I'm sure I'll find a solution eventually, so there's no rush. I've been in similar situations before. Just wanted to see what other people had used for similar situations. So if you know of something that would help, please let me know.

Found these through search (I'll do a better search again later), i will try them tomorrow:

http://xdaforums.com/showpost.php?p=18944228&postcount=4

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

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

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

http://xdaforums.com/showthread.php?t=1011527
[Huawei Ideos X5 U8800] typci:
After reading a lot of threads, attempting to flash a lot of roms (stock and others), replacing all kinds of images, and offering a sacrifice to the cellphone gods, still at the same problem:

To reiterate problem:

1) Stuck/reboots at Huawei logo

2) Flashing stock roms via pink screen never finish installing, get error message at ~95% finished (During install, unpacks fine)

3) Flashing roms via recovery say they installed, but still boot problem

4) This problem occurred while trying to downgrade from .35 to .32

My next step is to try using Linux to put the Dload folder on the internal SD card and try installing from there. I have a feeling it is related to the partitions having problems. I used both the "get back pink screen" and "data partition resize," maybe something went wrong with them that only appeared when I tried to go back to stock. I'll find out more when I install linux and can see if the partitions are OK or not.

I've always wanted to try linux, and now that my phone is broke I have found the motivation to do so. So a word of advice for people for people wanting to try linux but are too lazy to download the linux file: Soft-brick your phone, it gives you motivation.

UPDATE: I'm pretty sure my partition table is broke pretty bad. In adb shell, df gives me:

Filesystem Size Used Free

/dev 173M 64K 172M

/system 203M 200M 2M

/cache 127M 4M 123M

and that's it. No /HWUserData, /.cust_backup, /mnt/asec, /mnt/obb, or /data.

Would someone be as kind as to tell me how to fix the partition table? I've got a soldering iron, duct tape and super glue. Also, I'm not afraid to buy a "box" to do some Jtag stuff.
[Huawei Ideos X5 U8800] typci:
Anybody know what Blefish uses to format the phone memory? I read on his tumbler page and his github that he has altered the partition table (he split the /hwuserdata into three sections, which means he has the ability to create partitions) If I can get that tool, then I have a plan:

0) If my understanding is correct, the updates don't install because the needed partitions are missing, which causes an error. I guess the updates won't create partitions, just alter them.

1) Use the tool blefish used to setup the partition table as described in this thread: http://xdaforums.com/showthread.php?t=1504488

2) Once the partitions are back, i should at least be able to get the blue screen, if I'm good, then I can put all right files in /dev/sdb1, which will get me the pink screen.

3) Using the blue/pink screen, I can install stock firmware, which should correct any problems that the partition table has. Maybe even install android.

4) Do the happy dance

5) ???

6) Profit

I've done my homework, searched the forums, made a plan, and cleaned my room. Someone please give me some feedback and at least let me know if I'm heading in the right direction.
[Huawei Ideos X5 U8800] Blefish:
I am using fdisk, the main partitioning tool for MBR table. You can check the table by doing fdisk /dev/block/mmcblk0 and then "p" which should print the current partition table. From there, you can also modify the partitions.
[Huawei Ideos X5 U8800] typci:
Awesome. I used to use fdisk back in the dos days, so I just need to brush up on my skills and learn the adb specifics. I really need to take the time to go learn all the commands associated with adb.

INTERESTING UPDATE: If I flash a rom with locked boot loader, I still get the pink screen but it doesn't work, i.e. I can't access the image folder via windows. If I flash a rom without a locked boot loader, pink screen works. Granted none of these roms actually fully flash, I still get the error near the end.

Fdisk = Permission denied, su = permission denied. Rooted boot image prevents me from getting into recovery, which means adb won't work. Any other way to get root? I'll try flashing a custom rom when I can get clockworkmod working again. For some reason I can't get recovery to load via vol+ & power.

Also something weird is going on. When it boots, it reboots once, then goes to stock recovery, tries to do a factory reset, gets errors on formating. Also in windows two removable disks appear, but I can access them. I take it that they represent the internal SD card and maybe the pink screen image folder partition. Tomorrow I'll try linux and see what happens.
[Huawei Ideos X5 U8800] typci:
UPDATE:

1) I can't use FDISK because SU won't work. I'm not sure how SU/root works on a software/partition bricked phone.

2) Rooted boot.img won't boot into recovery. SuperOneClick won't work because it can't find the data partition (probably because I don't have one).

3) I was going to try flashing a custom rom but for some reason I can't get clockworkmod working again. The phone will boot into stock recovery on it's own, after a couple of reboots. However, if I change the boot.img or recovery.img to anything else, it gets stuck at huawei logo or boot loop.

4) Unbuntu LiveCD won't work (says it can't find the kernal) even though I used the installer from the website and tried it both via cd and flash drive. Working on installing a dual-boot system now.

I'm really striking out here. Couple of questions if anyone would care to answer.

1) Besides recovery, how else can I establish an adb connection? Pink screen and huawei logo give me device not found.

2) Is there a root exploit available that doesn't require a data partition or is there a root exploit I can modify so it doesn't require a data partition? It's OK if it's a manual exploit, while I'm new with android/adb, I got plenty of experience with command prompt input from back in the dos days.

Also learned there is a HuaWei office in my town. Don't know what they do there, but if I don't make any progress after I couple more days, I'll go find out.
[Huawei Ideos X5 U8800] Blefish:
On pink screen, your device is just like any other mass storage device. So you can still use fdisk on ubuntu with the correct /dev/sdX path. You can also format the data/system/cache using other tools if you need to.
[Huawei Ideos X5 U8800] typci:
Sweet, so I just need to get Unbuntu working. I still can't figure out why the live CD/flash drive didn't work. Oh, well. When I get off of work I'll get to installing the dual-boot system. Thanks for your help.
[Huawei Ideos X5 U8800] JaymzBond:
i actually understood nothing from your posts but i would like to congratulate you for being a user who does research before asking ppl something

and I gladly give you a bump
[Huawei Ideos X5 U8800] typci:
Thanks. Unfortunately the project is on hold for a couple of days. My electric motorcycle has been having some problems and I've been repairing it. Also, I think I found out why linux wasn't working. Apparently the "alternative" downloads aren't useable as a live CD, which is why the kernal wasn't there. Anyway, it's been a great learning experience. Maybe after I "break" my phone enough times I'll learn enough to become a developer.
[Huawei Ideos X5 U8800] Blefish:
It could be that the data partition (originally mmcblk0p13) got wiped out and now mmcblk0p13 is internal sd card. Here's the original partition table:

Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
1 heads, 16 sectors/track, 483328 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 30721 245760 b Win95 FAT32 CUST
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 30721 30783 500 4d Unknown SBL1
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 30783 31158 3000 46 Unknown TZ
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 31158 483328 3617363+ 5 Extended EBR
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 32769 34304 12288 59 Unknown OEMINFO/BOOTLOADER IMAGES
/dev/block/mmcblk0p6 40961 57600 133120 4c Unknown CACHE
/dev/block/mmcblk0p7 65537 65599 500 5a Unknown MISC
/dev/block/mmcblk0p8 73729 74112 3072 58 Unknown FSG?
/dev/block/mmcblk0p9 81921 82795 7000 50 Unknown ADSP
/dev/block/mmcblk0p10 90113 90496 3072 4a Unknown MODEM_ST1
/dev/block/mmcblk0p11 98305 98688 3072 4b Unknown MODEM_ST2
/dev/block/mmcblk0p12 106497 134656 225280 83 Linux SYSTEM
/dev/block/mmcblk0p13 139265 216064 614400 83 Linux USERDATA
/dev/block/mmcblk0p14 221185 483328 2097152 69 Unknown INTERNAL_SD

The sdb6 is indeed cache, and it is used for recovery communication between Android.

If everything would be ok, it would mount sdb1, sdb6, sdb12, sdb13 and sdb14 inside Ubuntu, so it seems that something is wrong at the end.

If you have 14 partitions, use disk utility from Ubuntu and try manually formatting the 13 for ext4 and 14 for vfat. Taking ownership is not needed, it should work either way.
[Huawei Ideos X5 U8800] typci:
Blefish, thanks for the help. Got unbuntu up and working along with fdisk and identified the phone.

I have 13 partitions (including one empty one) , not 14. Here's the print out:

ubuntu@ubuntu:~$ sudo fdisk /dev/sde

omitting empty partition (13)

Command (m for help): p

Disk /dev/sde: 3959 MB, 3959422976 bytes

1 heads, 62 sectors/track, 124729 cylinders, total 7733248 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

/dev/sde1 1 491520 245760 b W95 FAT32

/dev/sde2 * 491521 492520 500 4d QNX4.x

/dev/sde3 492521 498520 3000 46 Unknown

/dev/sde4 498521 7733247 3617363+ 5 Extended

/dev/sde5 524288 548863 12288 59 Unknown

/dev/sde6 655360 921599 133120 4c Unknown

/dev/sde7 1048576 1049575 500 5a Unknown

/dev/sde8 1179648 1185791 3072 58 Unknown

/dev/sde9 1310720 1324719 7000 50 OnTrack DM

/dev/sde10 1441792 1447935 3072 4a Unknown

/dev/sde11 1572864 1579007 3072 4b Unknown

/dev/sde12 1703936 2154495 225280 83 Linux

Comparing with your partition table I see two differences:

1) the ending block of sde1 is 491520 on mine and on the original it is 30721, however the blocks are the same, so that is probably not a problem

2) sde13 is empty, and sde14 is missing.

This actually makes sense. When I was using MIUI, I reduced the size of the internal sd to near zero, since MIUI could only either the internal or external sd, not both. After trying to downgrade, I had a problem, so I tried to restore the internal sd card back to stock size, just to bring my phone back to stock. Something must have gone when I did that.

So if I understand the problem correctly, to fix this I need to:

1) Split sde13 into 2 partitions

2) Format sde13 to ext4 and sde14 to vfat

3) Try installing adroid again

Do I need to name the partitions a certain name or do anything else?

In the mean time I'll be looking into how to use disk utility and fdisk to deal with sde13 and sde14.
[Huawei Ideos X5 U8800] typci:
Had an idea that I only need sde13 (data) to get things working again, the system shouldn't need sde14 (internal sd) to work.

So I went to disk utility, found Qualcomm MMC storage and tried to format the free 2.9GB at the end. Got an error:

Error creating partition: helper exited with exit code 1: In part_add_partition: device_file=/dev/sde, start=1103101952, size=2856000000, type=0x83

Entering MS-DOS parser (offset=0, size=3959422976)

MSDOS_MAGIC found

looking at part 0 (offset 512, size 251658240, type 0x0b)

new part entry

looking at part 1 (offset 251658752, size 512000, type 0x4d)

new part entry

looking at part 2 (offset 252170752, size 3072000, type 0x46)

new part entry

looking at part 3 (offset 255242752, size 3704180224, type 0x05)

Entering MS-DOS extended parser (offset=255242752, size=3704180224)

readfrom = 255242752

MSDOS_MAGIC found

readfrom = 255243264

MSDOS_MAGIC found

readfrom = 255243776

MSDOS_MAGIC found

readfrom = 255244288

MSDOS_MAGIC found

readfrom = 255244800

MSDOS_MAGIC found

readfrom = 255245312

MSDOS_MAGIC found

readfrom = 255245824

MSDOS_MAGIC found

readfrom = 255246336

MSDOS_MAGIC found

readfrom = 1140842496

No MSDOS_MAGIC found

Exiting MS-DOS extended parser

Exiting MS-DOS parser

MSDOS partition table detected

containing partition table scheme = 1

got it

Error: Invalid partition table on /dev/sde -- wrong signature 0.

ped_disk_new() failed

So, my partition table is corrupt? I'll need to figure out how to fix this.
[Huawei Ideos X5 U8800] typci:
Here's some options I've found:

http://xdaforums.com/showpost.php?p=21572216&postcount=12

ksatta mentions a couple of ideas:

1) If someone backed up their phone using dd, I could use that to restore my phone.

Here's a link on how to do it: http://linuxpoison.blogspot.com/2009/04/creating-backuprestore-images-using-dd.html

dd if=/dev/sdX | gzip > /home/sdX.bin.gz

where sdX is the U8800

2) I could clone someone's partition table. If someone could give me a copy of their MBR that should work.

Here's a link on how to do it: http://embraceubuntu.com/2005/10/20/backing-up-the-mbr/

Create a backup of your MBR by doing a:

dd if=/dev/sdX of=MBR-backup bs=512 count=1

That should read “create a disk dump of the input file, which is /dev/sdx (change to hda, or hdb or sda, depending on where the MBR is on your computer), and save it in the output-file MBR-backup in the directory from where the command is issued. Backup the first sector only, while you are at it”.

3) gparted - it's some kind of partition tool. Might be able to use it to fix the error. Not sure how to use it though.

For now I'm going to look into gparted for Ubuntu. If someone can help me out with a dd backup or cloning the partition table that would be awesome.

UPDATE: For people following this thread, and to keep me more organized, I'll start adding more of the important resources I find. They may one day help you fix your phone.

https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/434463

Seems a guy fixed his the same error with gparted. However it wasn't on a phone. Also I'm seem a lot of people refer to sfdisk. I'll need to learn more about it.

https://answers.launchpad.net/ubuntu/+question/113539

"I got an answer in a forum, which looks easy.

Do a

sudo fdisk /dev/sda

then type

w

to write partition table, without any modification of it.

The signature should be fixed."

Is this safe to do to my phone? I know I'll have to write the MBR eventually, but I have to get it right the first time. If I screw up, I may not be able to connect to ubuntu anymore. Anyway, the guy said it fixed the error with his harddrive, so it's worth a try.

http://www.thegeekstuff.com/2010/09/linux-fdisk/

How to use fdisk, in case anyone needs to know

So my new plan is to:

1) dd Backup and MBR backup - in case I break it worse than it is

2) try to fix with fdisk w or gparted
[Huawei Ideos X5 U8800] Blefish:
I think the change in start and end is caused by Ubuntu using cylinders/sectors/blocks. Should not too much difference though.

Using MBR restore would not work here, as it restores the main 4 partitions list. MBR uses EBR aswell, which is located at the beginning of every extended partition. So we would have to copy the EBR of every partition.

I'd suggest deleting sde13, adding sde13 and sde14.

When adding sde13, note that starting block should be at the end of sde12, so simply insert last block of sde12 there. If it gives error, simply press enter as it automatically finds free block after the last one. End block could be for example +500M so fdisk automatically finds the correct end block. Do the same for sde14, but note the start block again. sde14 end block should be the last block there is on the card.

After you've done that, do w to write and if it tells you to restart or something, unplug the phone, take out the battery and restart to pink screen again. Then try to use disk utility again or gparted (have not tested this) to reformat sde13 and sde14 to ext4 and vfat.

You should be safe until you don't mess with the primary partitions, especially the mmcblk0p2 and mmcblk0p3.
[Huawei Ideos X5 U8800] typci:
Thanks again for the reply, Blefish. I may have just fixed it. I'll know soon enough.

I did two things:

1) sudo fdisk /dev/sde12 followed by w

2) sudo fdisk /dev/sde followed by w

After that it enabled me to add the 13 and 14 partition. I used disk utility so I didn't have to worry about the blocks. Afterwards they mounted in ubuntu like they should.

UPDATE: Not quite fixed, but the rom installed without error. So I think the partition problem is fixed.

Now I just have a boot loop. I'll go back to ubuntu, clear the cache, and try installing from the internal sdcard

2nd UPDATE: Stock recovery gives and error about mounting the cache partition. However CWM mounts it fine. My partition problems may not be over.

3rd UPDATE: genokolar's "Custom you partition" file to return to stock file deletes my partition 13 and 14. Had 13 and 14 back working, used the file as per instructions, afterwards ubuntu drive utililty shows 13 and 14 as "free." So that is where part of my problem comes from.

4th UPDATE: Fixed the problem with stock recovery. Turns out froyo doesn't like ext4 partitions. Changed cache partition to ext3, no more error.
[Huawei Ideos X5 U8800] typci:
Here are some exerts from the CMW log when I tried to flash cyanongen. Can anyone tell me if any of these errors are problems, and if they are what they mean?

W:Unable to get recovery.fstab info for /datadata during fstab generation!

W:Unable to get recovery.fstab info for /sd-ext during fstab generation!

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

failed to open /sys/class/android_usb/android0/state: No such file or directory

-- Installing: /sdcard/CM7-070512.zip

Finding update package...

I:Update location: /sdcard/CM7-070512.zip

Opening update package...

Installing update...

unmount of /system failed; no such volume

package_extract_file: no backup_initd.sh in package

set_perm: chown of /tmp/backup_initd.sh to 0 0 failed: No such file or directory

set_perm: chmod of /tmp/backup_initd.sh to 777 failed: No such file or directory

about to run program [/tmp/backup_initd.sh] with 2 args

run_program: execv failed: No such file or directory

run_program: child exited with status 1

Pass 5: Checking group summary information

/dev/block/mmcblk0p12: 11/56448 files (0.0% non-contiguous), 7142/225280 blocks

mount: failed to mount /dev/block/mmcblk0p12 at /system: Invalid argument

set_perm: chown of 0750 to 0 2000 failed: No such file or directory

set_perm: chmod of 0750 to 755 failed: No such file or directory

set_perm: chown of /system/etc/init.qcom.post_boot.sh to 0 2000 failed: No such file or directory

set_perm: chmod of /system/etc/init.qcom.post_boot.sh to 555 failed: No such file or directory

set_perm: chown of /system/xbin/apply_firewall to 0 0 failed: No such file or directory

set_perm: chmod of /system/xbin/apply_firewall to 6755 failed: No such file or directory

set_perm: chown of /system/xbin/apply_theme to 0 0 failed: No such file or directory

set_perm: chmod of /system/xbin/apply_theme to 6755 failed: No such file or directory

set_perm: chown of /system/xbin/dumplog to 0 0 failed: No such file or directory

set_perm: chmod of /system/xbin/dumplog to 6755 failed: No such file or directory

set_perm: chown of /system/xbin/mv2sd to 0 0 failed: No such file or directory

set_perm: chmod of /system/xbin/mv2sd to 6755 failed: No such file or directory

set_perm: chown of /system/xbin/ota to 0 0 failed: No such file or directory

set_perm: chmod of /system/xbin/ota to 6755 failed: No such file or directory

Updating BOOT Image...

about to run program [/tmp/backup_initd.sh] with 2 args

run_program: execv failed: No such file or directory

run_program: child exited with status 1

Installation complete!script result was [Installation complete!]

Install from sdcard complete.

failed to open /sys/class/android_usb/android0/state: No such file or directory