yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Vampir1c:
Hello, I would like to start by thanking all of you amazing people that made all these ROMs possible. I'm about to be a new HD2 owner (TMOUS model) and have been studying up on the stuff on flashing the ROM, reading the FAQs, Q&As, etc. However I have a question regarding Android ROMs. Can I use any Android ROM on a TMOUS? Or would it have to be stated by the OP if it can? Or is there a way that I'm just not familiar with such as the radio versions? I would like to use the Nexus One Android rom on my phone just as a heads up. Thanks again!
[HD2 Android Q&A, Help & Troubleshooting and Genera] JonSolo:
Any Android build can be used on TMOUS although several out there right now have all the fixes in place to make things like MMS, Visual Voicemail, and My Account working properly.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Vampir1c:
Thank you so much!
[XPERIA X10 Q&A, Help & Troubleshooting] imgladuhateme555:
After I updated to Nordic 2.1 and used v002 optimizer, I noticed I was getting awesome battery life. For the past few days I've used my phone minimally with sim card in, GV on, etc, but with minimal use to see just how good the battery life is now. Before, with 1.6, I was getting 2 days absolute maximum, even with minimal usage. Now I've gotten this: http://imgur.com/xNjaz.jpg (with 10% battery remaining).

Anyone else gotten better or comparable results? Personally, I think this is excellent, especially compared to having to charge nightly with 1.6 when I actually put it to some use. I think I could do some browsing, texting, calling, and stuff and not have to worry that if I forget to charge one night, it would die early on the next day now.
[XPERIA X10 Q&A, Help & Troubleshooting] rkanwar:
Wat did u do to get this amazing result
[XPERIA X10 Q&A, Help & Troubleshooting] imgladuhateme555:
Flashed the Nordic 2.1 rom and ran optimizer v002 (http://xdaforums.com/showthread.php?t=829660).
[XPERIA X10 Q&A, Help & Troubleshooting] sidneylopsides:
Ive noticed my battery is better too, I use mine quite heavily, take it off charge about 8am and would top up the charge about 2pm. This last week ive not needed to top up the charge, the other day I got home from work with 71% left, which for me was amazing!

It seems they changed the standby power consumption.
[General Questions and Answers] gsalgado:
Hi there,

I've got a G1 running eclair and as expected it rarely has more than a few hundred KB memory free. I've noticed I can free quite a bit of memory by disabling the soft keyboard, but that doesn't seem to "stick" and the soft keyboard gets re-enabled all the time. Is there any way to make that stick? I'm willing to write an app if that's what it takes...

Cheers,

Guilherme
[General Questions and Answers] gsalgado:
One idea I had right after posting this is to write an app that registers itself as a soft keyboard and then use that as the input method.
[General Questions and Answers] gsalgado:
There's a sample soft keyboard included in the sdk. I'll just use that instead of the regular keyboard and see if it saves some memory. If it doesn't then I'll rip off as much code as I can until it does.
[Desire General] Magpies12345:
Need some pointers from anyone that may be able to help out... I'm a first time rooter/modder, and have successfully rooted and modded my Desire, but for the life of me can't seem to be able to partition my SD card - I thought that would have been the simplest part!

Here's the guff;

PC running Vista

HTC Desire

32GB SanDisk (a real one purchased from play dot com)

Rooted using Unrevoked

Running ClockworkMod 2.5.0.7

Running CyanogenMod 6.1.0 RC1 Desire

All working perfectly, no issues.

Then I got to the point where I need to partition the SD card with an ext partition to allow for a2sd. I've now spent four 2AM nights trawling and googling through the intermaweb trying to figure out how to do this with no luck.

I have had the card for a few months and have been using almost the whole 30GB of the card for storage on and off (transferring to and from in Vista), but I also recently ran verification tests to confirm that there are no bad sectors/issues with the SD.

I have unsuccessfully tried all of the following methods to partition the SD;

ROM Manager --> Partition SD Card --> 512MB ext, 32MD swap and the rest fat, along with a number of other combinations. I am using the premium version 2.5.0.7... ROM Manager goes through the process, looks like it's done it's thing and then reboots, but then doesn't actually create the partitions!

GParted Live CD. I boot using the live CD, but no matter what, the SD just doesn't seem to show up here for some reason - I'm not really sure exactly what state I should be putting the phone in to make it work here??

Android Device Bridge (ADB) using the console manager thing. I get issues with parted, but I think that was because it was needing the Amon-Ra recovery?

Amon-Ra recovery. I couldn't find the proper recovery to use, didn't know what to do with it, and then wasn't sure if I should be getting rid of ClockworkMod, so didn't manage to use this either!

The 'Quick System Info' app confirms the status as:

SD Card Storage: total 29.2GB, free 29.2GB

A2SD storage: "information not available"

Internal storage: total 148MB, free 44.48MB

System storage: total 250MB, 132MB

System cache: 40MB, 38.7MB

Any help would be super-duper appreciated, so thanks in advance for your responses!
[Desire General] Magpies12345:
I just installed a couple of apps (angry birds/XDA) and rebooted, now Quick System Info says:
[Desire General] vpraveenis:
I had faced similar issues as well. I finally used ubuntu live cd that is a free to download bootable iso image and used gparted that is available in that.

gparted live cd did not detect my SD but it did in ubuntu. You can also use it to mount and see the contents of SD and resize if required. I recommend you download it.
[Desire General] ix9:
I used MiniTool Partition Wizard Home Edition to part my SD card.....

... actually setting up A2SD on CM6.0.1 alludes me....
[Desire General] Wickedkitten:
I can't remember if cyanogen actually supports a2sd+ or not but make your fat32 partition FIRST then just make your ext3 and swap in ROM Manager
[Desire General] Magpies12345:
Thanks for the replies! - will give the ideas a try next week when get home...
[Desire General] ix9:
Any luck with this?

I _still_ can't get A2SD working with CM6.1 :(
[Desire General] Magpies12345:
As Gparted live cd was not detecting my SD, I followed vpraveenis' suggestion and used Ubuntu live cd and the Gparted that comes with that - this finally picked up my SD where the Gparted live CD wouldn't.

It showed me that the 'partition SD card' option in ROM manager was actually working, as the SD card was already partitioned with a fat32, 512mb ext and 32mb swap.

I repartitioned it using the Ubuntu live cd Gparted with fat32, 1024mb ext4 and 32mb swap just to see it anything different happened. Same issue. a2sd didn't work.

bugmenot (cyanogen forum) advised that installing Darktremor A2SD fixed their issues so I tried that - this also didn't seem to make any difference.

Looking around now, there seems to be a number of users asking the same question and not getting anywhere.

Could this be a cyanogen mod issue? My understanding is that a2sd is included in 6.1CR1, so it should be working.

I'm currently trying to sort out some of the latest nightly builds so see if I have any luck there. Any other insights would be appreciated.
[Desire General] nulry:
i faced the same problems with you, but i have solved it.

First, you need to download the unvoked 3.14 << which is the older version

then dl the RA-Desire-Recovery

Using the unvoked 3.14 to custom the RA-desire recovery. (connect the phone to computer)

then boot into the recovery by holding vol - and power and partition here.

Finished~~~~
[EVO 4G Android Development] zikronix:
reserved....
[EVO 4G Android Development] zikronix:
bump for the night krew
[EVO 4G Android Development] chubbzlou:
When I flash via recovery everything completes but when it boots it hangs on the HTC logo screen.

Is this why when I flash it hangs?
[EVO 4G Android Development] xHausx:
what does 'cat /proc/mtd' show?
[EVO 4G Android Development] chubbzlou:
I never cat will do in a little while. Should I flash and when it hangs on the HTC logo do I run the cat to get the info?
[EVO 4G Android Development] xHausx:
you can try there or while in the recover
[EVO 4G Android Development] chubbzlou:
Ok I'll let you guys know.
[EVO 4G Android Development] TrevE:
Devs - Could it be possible that somehow the partitions need to be changed in recovery.img? I found the following:

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

Looks like boot.img and recovery.img both can have offsets/partition sizes set by specifying addition kernel parms when its made with mkbootimg. Is it possible whatever the "default" recovery.img structure is borked somehow with this hardware?

If this helps, this seems to be the MTD layout from a working boot on 2.02 on 003:

<5>[ 5.696319] Creating 7 MTD partitions on "msm_nand":

<5>[ 5.696411] 0x00003f300000-0x00003ff00000 : "wimax"

<5>[ 5.705780] 0x00003ff00000-0x000040000000 : "misc"

<5>[ 5.707000] 0x000004340000-0x0000047c0000 : "recovery"

<5>[ 5.710510] 0x0000047c0000-0x000004b00000 : "boot"

<5>[ 5.713043] 0x000004b00000-0x00001a900000 : "system"

<5>[ 5.951934] 0x00001a900000-0x000024900000 : "cache"
[EVO 4G Android Development] chubbzlou:
This is what I got while in recovery before I flashed

dev: size erasesize name

mtd0: 00600000 00020000 "wimax"

mtd1: 00080000 00020000 "misc"

mtd2: 00240000 00020000 "recovery"

mtd3: 001a0000 00020000 "boot"

mtd4: 0af00000 00020000 "system"

mtd5: 05000000 00020000 "cache"

mtd6: 0d500000 00020000 "userdata"
[EVO 4G Android Development] zikronix:
working values on an older 003 evo with 076.2000

<5>[ 3.319244] Creating 7 MTD partitions on "msm_nand":

<5>[ 3.319366] 0x00003f360000-0x00003ff60000 : "wimax"

<5>[ 3.333801] 0x00003ff60000-0x000040000000 : "misc"

<5>[ 3.334991] 0x000004240000-0x000004740000 : "recovery"

<5>[ 3.341033] 0x000004740000-0x0000049c0000 : "boot"

<5>[ 3.344421] 0x0000049c0000-0x00001a7c0000 : "system"

<5>[ 3.852111] 0x00001a7c0000-0x0000247c0000 : "cache"

<5>[ 4.036437] 0x0000247c0000-0x00003f360000 : "userdata"

sorry took so long dmesg was all over the place lol

device said i was offline and online at the same time....****ing nexus of the universe.
[EVO 4G Android Development] xHausx:
TrevE are you sure those mtd values are correct? I was expecting something along the lines of:

dev: size erasesize name

mtd0: 00c00000 00020000 "wimax"

mtd1: 000a0000 00020000 "misc"

mtd2: 00500000 00020000 "recovery"

mtd3: 00280000 00020000 "boot"

mtd4: 15e00000 00020000 "system"

mtd5: 0a000000 00020000 "cache"

mtd6: 1aba0000 00020000 "userdata"

I believe most evo roms have a boot.img offset of 20000, I could ber mistaken though
[EVO 4G Android Development] TrevE:
yes i just ran it again. This is on my new 003 phone with 2.02 hboot and s-off.

$ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"

im guessing this and the MTD offsets being different is part of the reason we only see half of the space in recovery leading to nothing flashing properly
[EVO 4G Android Development] xHausx:
What does your bootloader look like? Can you tell us what the top 3 or 4 lines say
[EVO 4G Android Development] BonkyMoon:
I have a white evo with hardware 0003 and hboot 2.02.

I initially rooted with http://xdaforums.com/showthread.php?t=838448

The part where it flashes the recovery image never succeeds it and I come up with the stock recovery screen. What's interesting is that if I run the recovery-windows.bat from http://link.geekfor.me/evorecovery while in the stock recovery, it actually loads a working recovery image, allowing me to flash roms and everything else. It doesn't keep though, and upon reboot I lose that recovery. Whatever I flash to sticks, though.
[EVO 4G Android Development] helioXverse:
cat /proc/partitionsajor minor #blocks name

7 0 16664 loop0

31 0 12288 mtdblock0

31 1 640 mtdblock1

31 2 4608 mtdblock2

31 3 3072 mtdblock3

31 4 358400 mtdblock4

31 5 163840 mtdblock5

31 6 437888 mtdblock6

179 0 7761920 mmcblk0

179 1 6261718 mmcblk0p1

179 2 1000000 mmcblk0p2

179 3 500201 mmcblk0p3

254 0 16663 dm-0

cat /proc/mtdev: size erasesize name

mtd0: 00c00000 00020000 "wimax"

mtd1: 000a0000 00020000 "misc"

mtd2: 00480000 00020000 "recovery"

mtd3: 00300000 00020000 "boot"

mtd4: 15e00000 00020000 "system"

mtd5: 0a000000 00020000 "cache"

mtd6: 1aba0000 00020000 "userdata"

Here is what I show, for what it's worth. Hardware version 003, Rooted, s-off, 2.02 hboot. This is while os is up. I can run it from recovery in the am if you like. I have had no problems flashing roms, though.

Sent from my HTC SuperSonic 4G using the XDA app.
[EVO 4G Android Development] chubbzlou:
supersonic evt2-3 ship s-off

hboot-2.02.0000

microp-041f

touch panel-atmelc03_16ac

radio-2.15.00.09.01

Oct 14 2010,19:14:47
[EVO 4G Android Development] chubbzlou:
TrevE

I was curious and I ran cat /proc/mtd in recovery and not in recovery

cat /proc/mtd not in recovery

dev: size erasesize name

mtd0: 00c00000 00040000 "wimax"

mtd1: 00100000 00040000 "misc"

mtd2: 00480000 00040000 "recovery"

mtd3: 00340000 00040000 "boot"

mtd4: 15e00000 00040000 "system"

mtd5: 0a000000 00040000 "cache"

mtd6: 1aa00000 00040000 "userdata"

cat /proc/mtd in recovery

mtd0: 00600000 00020000 "wimax"

mtd1: 00080000 00020000 "misc"

mtd2: 00240000 00020000 "recovery"

mtd3: 001a0000 00020000 "boot"

mtd4: 0af00000 00020000 "system"

mtd5: 05000000 00020000 "cache"

mtd6: 0d500000 00020000 "userdata"

Don't know why it would be different.
[EVO 4G Android Development] xHausx:
Ok. Starting to make sense now. It looks like they are using different partition tables

edit: meant block sizes not partition tables :)
[EVO 4G Android Development] chubbzlou:
Could be the reason why flash say complete but when it boots up it hangs due too the boot up looking at the first partition table. So amon or clockwork recovery needs to be updated for our evo?
[EVO 4G Android Development] xHausx:
Normally I would say amon for wimax but I don't think it matters in this case
[EVO 4G Android Development] Amon_RA:
Could someone please provide the stock recovery from a 003 evo with 2.02 hboot?
[EVO 4G Android Development] xHausx:
Not sure if this was what you were needing but here's the recovery image being packaged with the new hBoot. I pulled it from the 3.30.651.2 RUU that only the new phones can use.
[EVO 4G Android Development] zikronix:
Thanks for answering our call...

We also need to get a demesg from a 004 because some of them work fine, with the exisiting recovery or do they? So im wondering if they are different?

I dont know if it matters but if the tethered recovery could be updated that would be outstanding maybe with the ability to nand right there. Since thats how the root is done.
[EVO 4G Android Development] zikronix:
bump for the day crew
[EVO 4G Android Development] Amon_RA:
Could someone please this version : http://dl.dropbox.com/u/4481275/evo-test.img

Is the space ok now? (Can't test myself because I don't have an Evo)
[EVO 4G Android Development] chubbzlou:
Will test now

cat recovery

dev: size erasesize name

mtd0: 00c00000 00040000 "wimax"

mtd1: 00100000 00040000 "misc"

mtd2: 00480000 00040000 "recovery"

mtd3: 00340000 00040000 "boot"

mtd4: 15e00000 00040000 "system"

mtd5: 0a000000 00040000 "cache"

mtd6: 1aa00000 00040000 "userdata"

I just flashed Groove rom and so far looks good booted up fine. your the man thanks.

Going to try backing up and restoring now will let you know how it goes
[EVO 4G Android Development] aaronbot:
I'm on a hw rev 0004, rooted 2.02 hboot. This is my first post and I'm new to the scene a bit, but I'll add:

"old" amon_ra.img:

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

31 0 6144 mtdblock0
31 1 512 mtdblock1
31 2 2304 mtdblock2
31 3 1664 mtdblock3
31 4 179200 mtdblock4
31 5 81920 mtdblock5
31 6 218112 mtdblock6
179 0 7761920 mmcblk0
179 1 7757824 mmcblk0p1
/ # cat /proc/mtd
dev: size erasesize name
mtd0: 00600000 00020000 "wimax"
mtd1: 00080000 00020000 "misc"
mtd2: 00240000 00020000 "recovery"
mtd3: 001a0000 00020000 "boot"
mtd4: 0af00000 00020000 "system"
mtd5: 05000000 00020000 "cache"
mtd6: 0d500000 00020000 "userdata"

evo-test.img:

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

31 0 12288 mtdblock0
31 1 1024 mtdblock1
31 2 4608 mtdblock2
31 3 3328 mtdblock3
31 4 358400 mtdblock4
31 5 163840 mtdblock5
31 6 436224 mtdblock6
179 0 7761920 mmcblk0
179 1 7757824 mmcblk0p1
/ # cat /proc/mtd
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"

RUU:

# cat /proc/partitions
major minor #blocks name

31 0 12288 mtdblock0
31 1 1024 mtdblock1
31 2 4608 mtdblock2
31 3 3328 mtdblock3
31 4 358400 mtdblock4
31 5 163840 mtdblock5
31 6 436224 mtdblock6
179 0 7761920 mmcblk0
179 1 7757824 mmcblk0p1
# cat /proc/mtd
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
[EVO 4G Android Development] 94tbird:
I am on 003 and hboot 2.02 as well. I am rooted but I have problems with recovery, doesntmatter whose. I can get INTO recovery but if i do ANYTHING at all other than click reboot, the device will hang o nthe next reboot and throw me into a recovery loop of which i can only get out of by flashing a new sprint lovers rom or a stock rom. Hopefully this will solve my issue.
[EVO 4G Android Development] zikronix:
let me know so i can update
[EVO 4G Android Development] chubbzlou:
95tbird I had the same issuse. Install Amon new recovery http://dl.dropbox.com/u/4481275/evo-test.img it works. Tested with Groove rom booted up fine no hanging on the htc logo.
[EVO 4G Android Development] zikronix:
do you think that the tethered one needs to be updated as well
[EVO 4G Android Development] helioXverse:
I have experienced no problems flashing or restoring roms. My cat /proc shows the missing space, however. I will flash this later this afternoon and report back.

Sent from my HTC SuperSonic 4G using the XDA app.
[EVO 4G Android Development] zikronix:
will this now also work for 004 hardware as well?
[EVO 4G Android Development] TrevE:
thanks for the quick image amon. Just flashed it with a pc36img, rebooted to recovery, did a mount -a

now i see this, looks good.

df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 212408 0 212408 0% /dev
/dev/block/mtdblock5 163840 2324 161516 1% /cache
/dev/block/mtdblock4 358400 270396 88004 75% /system
/dev/block/mtdblock6 436224 42820 393404 10% /data

will this work on any evo? or just these 003 with the new offsets? (if that was even the issue)
[EVO 4G Android Development] wantanotherbeer:
Which method is the best for rooting the 003 hBoot2.02?
[EVO 4G Android Development] bigj225:
Dang guys hate to ask a stupid question but will this fix the failed PU errors?????
[EVO 4G Android Development] 94tbird:
http://xdaforums.com/showthread.php?t=829045&page=11

but wait for them to update the guide
[EVO 4G Android Development] wantanotherbeer:
Thank you appreciate it
[EVO 4G Android Development] zikronix:
guide updated...uploading now
[EVO 4G Android Development] aaronbot:
It worked for me. After I flashed I used the recovery image to install myn's and it's working great.
[EVO 4G Android Development] 94tbird:
someone refresh my crappy memory, what is the quickest way to reflash to a new recovery?
[EVO 4G Android Development] bigj225:
Thanks so much for the hard work.. Beer coming your way
[EVO 4G Android Development] catseyenu:
Sprint Employees & Advantage Club members rejoice

Sprint Employees & Advantage Club members who have been treated like red headed step children may now do their happy dance. :D
[EVO 4G Android Development] flipper12:
Nice

You guys are the sh*t Tim... a little beer money coming your way.
[EVO 4G Android Development] flipper12:
Ditto that one....
[EVO 4G Android Development] 94tbird:
reflashed and was able to finally do a NAND backup and get out of the recovery mode successfully back into the OS. THANK THANK THANK YOU
[EVO 4G Android Development] catseyenu:
I broke down & bought mine off FleaBay last August so it's not an issue for me but I've got 6-7 lined up waiting for me to give them the go on it. It's on in Sprint town!
[EVO 4G Android Development] 6uPMAH:
Just flashed the new AmonRA recovery image. Worked like a charm. No issues. My previous version was also working fine, with an occasional hiccup, but since I live to flash, I might as well have the latest and the safest (hopefully :) )
[EVO 4G Android Development] zikronix:
None of this would have been possible with out the work of many devs and memebers willing to brick their device.
[EVO 4G Android Development] ShadowDrake:
Another confirmation saying that it worked for me too.

The recovery partition seems to be working great now. Flashed Myn's rom but I get crazy display corruption on first boot. It looks like the LCD is failing or the cable connecting it is bad, but if I cycle the screen off and back on again it doesn't come back until rebooting again. *shrug*
[EVO 4G Android Development] mptherealmp:
Does this recovery give you the option to flash a zip from a folderon the SD card or just the root? And what version number is it? It was reported Amon_Ra was updating to 2.0 version which would allow for that?
[EVO 4G Android Development] Amon_RA:
I don't know, would be great if someone could try it out on an Evo with older hardware and report back if it's working or not.

The "problem" is the kernel, I swapped the kernel to the stock 003 recovery kernel so there's probably something missing in the older kernels which are used in the current custom evo recoveries.

I'll try to find out exactly what is missing so I can compile a new evo recovery kernel and update my recovery to v2.0.0 (with the new features).

You can use the test version in the mean time.
[EVO 4G Android Development] zikronix:
seems to work for my older evo

003 w 0.76hboot

if its indeed the kernel then using the newer kernel that was released should work for all of them shouldnt it?

also is there a way to decompile the 0.76 boot loader and replace what evers broken on that so you could safely downgrade if you wanted?
[Vibrant Q&A, Help & Troubleshooting] VeryCoolAlan:
Okay I have a rooted stock ji6 with lagfix and no clockwork recovery with jacs kernel no voodoo....if I flash the stock kernel that team whiskey posted will it not brick my phone
[Vibrant Q&A, Help & Troubleshooting] djquick:
No it won't. As long as you're not running voodoo, you're good to go. Flash away!!! Might I recommend flashing Onyx 4, it's absolutely amazing:D
[Streak 5 General] GuestK00170:
Hi guys

Managed to get a Dell Streak to day .as far as I can see it has build 3883 on it. As I have read this is the 1st 1.6 build. When I try to get the streak to try and check for an update it takes me to a web page but it states there is no updates . No the hand set is new never rooted or flashed with any custom Rom.

I know I can root and do it that way . Read that dell released 2.1

Any ideas or am I just being think ?

We have a thread about the update so can you please place questions in that thread thanks
[Streak 5 General] grizlore:
As far as i can tell, NO ONE has yet received an official update!

Unlocked streaks will get it first, so your (and my) O2 Streak will be update at a later time... Lord knows when

I know it does not make sense, but we shall be after the unlocked one and shall have to wait for Dell and O2 to pull their finger out.