yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
While reading through this post, http://xdaforums.com/showthread.php?t=1819095&page=3, I see a similar behavior in my phone. If I am reading this correctly, my *regular* fstab file needs to be adjusted to include all of the entries that show up in the recovery fstab file? Do I have that right?

~ # ls /etc/*fstab*
ls /etc/*fstab*
/etc/fstab /etc/recovery.fstab
~ # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p2 /cache auto rw
/dev/block/mmcblk0p1 /data auto rw
/dev/block/mmcblk0p1 /datadata yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw

~ # cat /etc/recovery.fstab
cat /etc/recovery.fstab
# mount point fstype device [device2]

/misc mtd misc
/recovery mtd recovery
/boot mtd boot
/system yaffs2 system
/datadata yaffs2 datadata

/data ext4 /dev/block/mmcblk0p1 NULL
ext3
/cache ext4 /dev/block/mmcblk0p2 NULL
ext3
/emmc vfat /dev/block/mmcblk0p3

/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL
ext3

~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name

31 0 640 mtdblock0
31 1 4608 mtdblock1
31 2 3072 mtdblock2
31 3 253952 mtdblock3
31 4 640 mtdblock4
31 5 40960 mtdblock5
31 6 152576 mtdblock6
179 0 1955840 mmcblk0
179 1 1954816 mmcblk0p1

~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)

Anyone able to point me in the right direction here?
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
I'd say flash ruu. You have missing partitions. Whoever had the phone before you messed it up. Mtdblock0 isn't a block device and cannot be managed with parted. Once you try the ruu first (may need s-off to do it) let me know what happens next.

I wouldnt even bother messing with the fstab. The post your talking about is related to swapping the internal and external storage.
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
Hi Tiny, thanks for the assistance. I've been using your Cyanogen 10.1 on my own Dinc and love it. Thanks for your awesome work! :)

I did try flashing the most recent RUU yesterday from here: shipped-roms.com/index.php?category=android&model=Incredible -- 4.08.605.2, and it went through the motions as if it was working (completed without any errors), but it didnt actually do anything (oddly, it didn't create a log file in the ruu_lof directory either) that I noticed. I tried it one more time right now though, just to be safe, and it failed. This time, it log, and the last entry is <T182509><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>

</DEBUG></T182509>

I didn't think S-OFF would make much difference with the unlocked bootloader, but I'll read up on how to do it. In the meantime, any other ideas? And, again, thanks a lot, I appreciate it greatly.
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
Lifted this command from another thread as well:

~ # e2fsck -fy /dev/block/mmcblk0p1
e2fsck -fy /dev/block/mmcblk0p1
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p1: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p1: 14/122400 files (0.0% non-contiguous), 15903/488704 blocks

~ # e2fsck -fy /dev/block/mmcblk0
e2fsck -fy /dev/block/mmcblk0
e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # quit
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Youll need s-off to flash a downgrade ruu. If your ruu is an upgrade it should work without s-off though I recommend it anyway to make resolving the issue simpler.
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
Tiny, to achieve S-OFF, I am following Scotty's instructions here: http://androidforums.com/incredible...ot-unlock-downgrade-achieve-s-off-htcdev.html

I am having some difficulty on Step 4, getting an error regarding "is a directory". I noticed if I leave off the trailing slash can get the command to work and adb will push the file, but even so it fails in the next step. I will keep reading to thread to see if anyone else had similar troubles.

C:\Users\David\Downloads\ADB-Tools>adb push flash_image /data/local/
failed to copy 'flash_image' to '/data/local/': Is a directory

C:\Users\David\Downloads\ADB-Tools>adb push flash_image /data/local
1105 KB/s (76044 bytes in 0.067s)

C:\Users\David\Downloads\ADB-Tools>adb push mtd0.img /sdcard/
1556 KB/s (655360 bytes in 0.411s)

C:\Users\David\Downloads\ADB-Tools>adb shell
~ # chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
chmod: /data/local/flash_image: Not a directory

C:\Users\David\Downloads\ADB-Tools>adb shell
~ # cd /data/local
cd /data/local
/sbin/sh: cd: can't cd to /data/local
~ # cd /data
cd /data
/data # ls
ls
local
/data # cd local
cd local
/sbin/sh: cd: can't cd to local
/data # ls
ls
local

Any ideas on how to proceed?
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Try adb shell mkdir /data/local though that folder should exist. If you do just adb shell do you get a # or $ prompt?
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
The mkdir command executed without any errors, and I do have a # sign...indicating phone is rooted and has su perms if I understand correctly?

C:\Users\David\Downloads\ADB-Tools>adb shell mkdir /data/local

C:\Users\David\Downloads\ADB-Tools>adb shell
~ #
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
Made it through Steps 5 and 6 successfully, and on to Step 7...However, here we run into problems once again. I copied the Superuser and Unrevoked-Forever zip files to my sd card (which I know is good, because my laptop recognized it immediately and I can see all of the default folders the phone itself created), placed it in the phone, and booted to recovery.

CWM starts up, but launching it I am immediately greeted by the same set of errors as before:

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open/cache/recovery/last_log

Choosing "install zip from sd card --> choose zip from sdcard" gives me an error that states: "E:Can't mount /sdcard/". "choose zip from internal sdcard" gives me an error that states "E:Can't mount /emmc/"

I still have adb access, so do you know if there is a way to install the Unrevoked Forever zip file through an adb command instead perhaps?
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
There isn't a way to sideload AFAIK with the clockworkmod recovery version you have. Do you have a MicroSD card laying around? If you do you can push it to your device. That's how I'd recommend pushing it to your device. If you check around the dev forums there should be a clockworkmod 6 version that supports sideload though. The next step once S-OFFing will be to manually partition your system as in your first or second post I saw a 2GB single partition which isn't correct. Let me know when you're ready for that.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
So this is what parted /dev/block/mmcblk0 (your main mmc partition with /cache /data and /emmc) should look like:

~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext3
3 1007MB 8095MB 7088MB primary fat32 lba

Also. error mounting /sd-ext is fine. You don't have an ext2 or ext3 sdcard partition. That is fine. Error mounting /sdcard is different.

I'd suggest reading up on parted. If I find a helpful thread on parted and Android I'll let you know but it just takes a bit of searching which it sounds like you're quite capable of doing already.
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
Alright, I found the CWM 6 build you were referring to in the Dev forum, flashed it, booted to recovery, and attempted a sideload of unrevoked-forever.zip. Unfortunately, it was a no go, and generated errors:

C:\Users\David\Downloads\adb1031>adb sideload unrevoked-forever.zip

adb server is out of date. killing...

* daemon started successfully *

sending: 'unrevoked-forever.zip' 100%

failed to open device control: No such file or directory
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
E:Error in /tmp/update.zip
(Status 0)
Installation aborted

I'll do my homework and research the errors.

Meanwhile, you asked if I have a microSD card around...I have one in the phone, but Recovery won't mount it or read it. Interestingly, the phone will mount and read it when in Froyo.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Hey, go to the HBOOT menu and check if it has S-OFF. It might have it already. To get there hold volume down while turning on the phone. It will say S-OFF if it's S-OFF in the upper left of the screen.

That status 0 error is likely related to the update-binary in the zip. You're actually going to be best flashing that with the former recovery. After checking if you have S-OFF, we should try to fix the partitions next.

You never did mention the symptoms of your partition issues. If you can boot into a ROM, let me know the output of the mount command from a terminal emulator or mount from an adb shell.
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
Tiny, I apologize if I missed some information along the way that was important. I thought I was including all pertinent info, but without a firm grasp on the problem I may have missed some.

In HBOOT, the phone still shows S-ON. I can go back down to CWM 5.0.2.0, but that version does not have Sideload capability. Since I can't get the phone to read from the internal memory or external micro sd card while in Recovery, that was the reason for going up to CWM 6 and attempting to load unrevoked-forever.zip via Sideload.

When I get home, I will install Terminal Emulator, boot to Froyo, and let you know the results of the 'mount' command.

In the meantime, I will begin doing my research and learning about parted.
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
In Froyo, here is the output from a 'mount' command:

$ mount

mount

rootfs / rootfs ro,relatime 0 0

tmpfs /dev tmpfs rw,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0

/dev/block/mtdblock6 /data yaffs2 rw,nosuid,noatime,nodiratime 0 0

/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0

tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0

/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u

id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset

=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat

ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch

arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

This varies significantly from the 'mount' command run from Recovery:

~ # mount

mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)
[Droid Incredible Q&A, Help & Troubleshooting] DavidPhx:
Ok, comparing the two, and some research on the 'mount' command led to me to the following:

~ # mount /dev/block/mtdblock5 /cache
mount /dev/block/mtdblock5 /cache
~ # cd dev/block
cd dev/block
/dev/block # ls
ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform

/dev/block # mount /dev/block/mmcblk0p1 /sdcard
mount /dev/block/mmcblk0p1 /sdcard
/dev/block #

I was able to successfully mount the cache and sdcard partitions! This cleared up the CWM errors, and I was able to use the "Install zip from sdcard" option in CWM to finally load the superuser.zip and unrevoked-forever.zip files. Rebooted to hboot, and I am now S-OFF!
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Awesome, time to parted. Clearly from your information above I can tell a few things. 1. You have only one partition in mmcblk0. You should have 3. One for /data, one for /cache and one for /emmc. That will need to be fixed with parted. Secondly, the system seems to be falling back to the mtdblock partitions for /data and /cache. mtd should be /data/data and /system with /cache on mmcblk. Also, it doesn't seem to be recognizing your sdcard at all as that shows up as mmcblk1p1. Your sdcard is formatted as FAT or FAT32 correct?

Anyway, in recovery do the following

#parted /dev/block/mmcblk0

(parted) print

That should show you what partitions you have. Take note of the value for end for the last listed partition (you will only have one) What you'll want to do now is delete it.

(parted) rm 1

If prompted type i for ignore.

Now time to re-create them

(parted) mkpartfs primary ext3 8192B 797MB
(parted) mkpartfs primary ext3 797MB 1007MB
(parted) mkpartfs primary fat32 1007MB "end-size from the print step" - without the quotes

If you're unsure or confused, hold off on the rm and mkpartfs steps or do them one at a time with a print in between to list the current setup.
[Micromax A110] akashvfx:
Can anybody beat this score, i am on jetmode v6 rom one more Screenshot link http://db.tt/r0YgCmRm
[Micromax A110] nagendhra.sudheer2:
Canvas 2 running MIUI V5
[Micromax A110] poran123:
can you share your rom
[Micromax A110] nagendhra.sudheer2:
Here is the patch

https://docs.google.com/file/d/0B5RySEwn9rJacXNkUWdIWG5zT3c/edit?usp=docslist_api
[Micromax A110] poran123:
Need permission
[Micromax A110] nagendhra.sudheer2:
Sorry here is 4shared link

http://www.4shared.com/zip/bDqXjvLy/best_8_9_2013.html
[Micromax A110] poran123:
thanks
[Micromax A110] mmxandy:
Grand score

here is my grand v3 score..
[Micromax A110] justmpm:
There is already a benchmark thead for this device: http://xdaforums.com/showthread.php?t=2166645
[Sony Xperia ZL] zombiej79:
Using dual recovery and having a battery issue plugged in all night says 14% rebooted and jumped to 45% is there a fix?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] obiesoft:
Hi people, first of all i want to thank you guys because this is the number one resource for XDA's. I always come here and i have an idea. I had a sony clie which i sold to get the XDA in london. With my sony clie, i could turn on the camera and connect it with my computer via an app so that when it locks the ip and the camera is on, i can have the clie downstairs and view what it sees on my computer screen. Is there an app that does the same for the XDA? cause i usually attach my clie to my TAMIYA RC car and drive looking from my screen, it is fun. Replies will be appreciated. Thank you. :P
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] hdubli:
Hi!!!!

Use Pocket controller....or Parys PTvnc...
[Samsung Galaxy Mega] wtjra70:
Hey all after this weekends leaks of the 6.3 on AT&T. It's been announced this morning, the 5.8 & 6.3 are definitely coming to the USA carriers except for Big Red, and T-Mobile. Any one State side planning on getting the SGM?

http://www.slashgear.com/samsung-galaxy-mega-arriving-in-the-us-this-month-19294101/
[Samsung Galaxy Mega] fixit35:
Yea i am hoping we can use the modem radio on i9205
[Samsung Galaxy Mega] kris:
I'll be walking in to the AT&T store with my unlocked version in hand just to show off that I have it already. LOL!! Then I'll walk out with the AT&T LTE version and promptly sell my i9205 on Swappa or Ebay.
[Samsung Galaxy Mega] carhigh:
My ATT guy just text me today they have them in and go on sale Friday.
[Samsung Galaxy Mega] natienn:
any word on the non contract price for the 6.3
[Samsung Galaxy Mega] madgalaxy:
Anyone seen non-contract pricing?
[Samsung Galaxy Mega] natienn:
$499 =[
[Samsung Galaxy Mega] inconceeeivable:
I'm seriously considering getting one of these. I hate TouchWiz, but I miss the screen real estate and battery life of my Note 2.

I hear it's $150 from ATT? I wonder how much from Amazon?
[Samsung Galaxy Mega] gubbilo144:
Does anyone know if at&t is getting black and white version of the samsung galaxy mega 6. 3.I have the note 1 and 2 and probably going to pick up the mega friday,then the note 3 when available. I wish they would of made the note 3 at least 6 or 6.3 inch screen.I'm not to crazy with the megas specks or it doesn't seem to be getting any rom development going on with the international version ,but that 6.3 screen is hard to pass up!!
[Samsung Galaxy Mega] natienn:
According to this article both black and white available from at&t, which is available the 23rd is not told. I want my white mega.

http://androidandme.com/2013/08/dev...hits-us-shores-on-att-sprint-and-us-cellular/
[Samsung Galaxy Mega] dparrothead1:
Just talked to ATT and it will be available tomorrow and should be $149 on two year contract.

While the specs aren't great, I always keep in mind that my wife's old single core Infuse is rockin 4.3. And now that the 6.3 is in the US, I believe the development will come. At least I hope so.:D
[Samsung Galaxy Mega] fixit35:
Went live on at&t looks like same chip Qualcomm MSM8930

http://www.att.com/shop/wireless/devices/samsung/galaxy-mega-nova-black.html#fbid=8bIkSMeZCtJ
[Samsung Galaxy Mega] natienn:
no white mega available online? maybe at the store =0(
[Samsung Galaxy Mega] Go1deneye:
I just picked mine up in store. No white version available at this time. This thing is pretty slick. Screen is awesome. BTW I'm coming from a Note 2.
[Samsung Galaxy Mega] Techngro:
Does anyone know whether the AT&T version will work on any of T-Mobile's bands? I might think about getting one if I can use it on t-Mobile.
[Samsung Galaxy Mega] dparrothead1:
Is it an 8gb? Looks like that is all they are offering. I placed my order this morning.

Wonder if XDA will start a new thread or lump it all together in this one.
[Samsung Galaxy Mega] Go1deneye:
Mine is showing 16GB internal storage. I purchased it in a corporate AT&T store.
[Samsung Galaxy Mega] natienn:
Mine is 16gb as well, no white in store I went to. But im loving this thing coming fom lg optimus g pro
[Samsung Galaxy Mega] Go1deneye:
This this is great so far. I'm coming from the Note 2.....yes I know the inner specs are better, but I never used the S-Pen. I'd rather have this screen landscape to use, "so much room for activities (random Stepbrothers reference)."

---------- Post added at 12:37 PM ---------- Previous post was at 12:27 PM ----------

Coming from a Note 2 I noticed there is a significant amount of bloat apps on here. Was an easy fix though, i just disabled a bunch of apps and am now running Nova. Its snappy and fast.
[Samsung Galaxy Mega] dparrothead1:
Any of you folks rooted yet?
[Samsung Galaxy Mega] curgervending:
AT&T and T-Mobile both use the same bands for LTE (1700/2100) and HSPA+ (1900). So the AT&T version should work on T-Mobile's network.

The problem?

1 - I'm sure the AT&T version of the phone is automatically locked to AT&T's network (I'd be surprised if it wasn't).

2 - AT&T more than likely won't unlock it for you when you purchase it (I'd be surprised if they did).

3 - I think it's illegal for you to unlock the phone yourself. It used to be legal but the statute that allowed it to be legal expired at the beginning of this year. So now, it's illegal to unlock a carrier-branded phone yourself (until they get that antiquated law changed). You have to ask the carrier to unlock it for you and it's at their discretion to do so. I'm sure people are ignoring that law and unlocking phones anyway but just so you know it's supposedly illegal (it doesn't make much sense but that's our antiquated law).
[Samsung Galaxy Mega] Go1deneye:
not yet. I will once I play around with it stock for awhile.
[Samsung Galaxy Mega] fixit35:
What baseband and build number is on the at&t mega... I have the i9205 and want to try its modem radio when available. it looks like same specs
[Samsung Galaxy Mega] natienn:
Here is the info
[Samsung Galaxy Mega] gubbilo144:
Root

Has anyone rooted the at&t galaxy mega yet.If yes do u have a link were u got it from,or know how to,any help would be appreciated, thanks
[Samsung Galaxy Mega] dparrothead1:
http://geeksworkshop.info/how-to-root-samsung-galaxy-mega/
[Samsung Galaxy Mega] latinohot:
unable to root with that link,

anyone else successful?

Also, when will it have its own forum page?
[Samsung Galaxy Mega] kwed73:
I talked to an att rep and they told me if the phone is bought at retail price they would unlock it for you.
[Samsung Galaxy Mega] curgervending:
That's great. Since (in this particular case) the purpose for unlocking the phone is to use it on T-Mobile, do you know if AT&T will allow anyone to buy the phone at retail without opening up an AT&T account?

If yes, great. If not, then we either have to wait until someone is selling an unlocked version (Ebay?) or open an AT&T account, buy the phone, have them unlock it, close the AT&T account, then use the unlocked phone on T-Mobile (sounds like a lot of work and possibly early termination fee just to get this phone to use on T-Mobile).

The other option is to just switch to AT&T but some of us are with T-Mobile because of the price of their plans. AT&T equivalent plans are much more expensive (at least the ones I compared).
[Samsung Galaxy Mega] AkumaMax:
Well After a long time standing in android since the HTC aria dropped. I moved onto a Dell Streak 5 and was waiting on possibly getting a Samsung Note 2 I have decided to once again have the new cool toy. Since ATT anounced this phone I will be going to my local ATT store this week to purchase one. I know the Note 2 is a little better here and there but it is the size I really like(thats what she said):o. Anyway I can't wait to get back into the android scene my Back up phone for the past 4 months was an Iphone4 and good god is it awful.
[Samsung Galaxy Mega] bigfau:
This will not work. I will try again when I return home from work.
[Samsung Galaxy Mega] natienn:
Not with the note 3 being announced today with better specs and around same size screen plus the s pen
[Samsung Galaxy Mega] pa49:
Mega in hand

Did a deal with a guy locally from a well known list site!!

8 day old 16Gb mega on hand, ex AT&T, unlocked, I'm using it on T-mob and the lovely little 4GLTE icon pops up a treat. I'm loving this!
[AT&T, Rogers HTC One X, Telstra One XL] Sun0727:
Hi everyone ！

I like CleanROM 5.1 very much . But now, I can‘t find it. I have searched it in Google and scott’s Home. But what can I find only CleanROM 6.5 .Could you please tell me where can I download the Rom . Thanks (I am a Chinese,so my English is not very good:) I hope you can understand me:laugh:)
[AT&T, Rogers HTC One X, Telstra One XL] exad:
If it's not on his site it would mean he probably no longer wants it distributed.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yep the ROM has been discontinued.

Sent from my Evita