yashsingh1/xdaforums huggingface dataset:
[HTC Aria General] dexmix:
there are threads on here describing the process, and the files you can delete.

the main one was called something like "alternative method removing bloatware"
[HTC Aria Android Development] Oren The Red:
Hi All,

My first post here, be gentle with me.

I am a recent sort-of convert to android from iOS (though, still own the iPhone 4). I decided to go with the HTC Aria here in Japan which is being sold by EMOBILE.

From looking around the web and reading the forum I came to learn that there are two versions of the Aria, AT&T and Asia. If I am not mistaken, they are different by the radio frequencies they are using. If that is the case, it seems that the Japanese version of the HTC Aria is another model that popped out to the world not too long ago as mine supports HSPA/W-CDMA: 1,700MHz.

Does that make sense? Is it really a new revision of the Aria?

I am very much interested in rooting my device and already have the "reflash" utility installed on my MacBook, but wanted to confirm whether I can safely go ahead and do that.

Additionally, How can I go back to stock ROM if I need warranty services from EMOBILE? I could not find the image of the ROM neither on EMOBILE site nor HTC (Japan, Taiwan and International).

Last but not least, if it is indeed a new model and one of the devs need any information from my phone, please let me know, I will be more than happy to help and provide info!

Thanks,

Oren.
[HTC Aria Android Development] lilhaiti:
Regardless of the radio you should be able to root your phone and try to load one of the custom ROMs on here. Unless you are already running 2.2, you should be able to use the root methods in this forum. If you are running 2.2 already you may have to do some research on rooting your phone since the stock 2.2 takes away the ability to root using the methods in this forum. Once you have rooted and loaded a custom recovery make sure you do a full backup (Nandroid backup if you use Clockworkmod) before trying the new ROM. Either way...have fun and enjoy your Aria.
[HTC Aria Android Development] Oren The Red:
Thanks for your reply. I guess I am out of luck then at the moment. My device indeed came with Stock 2.2, HBOOT-1.02.0000 (not sure if it makes a difference or not though).

I tried googling but most of the post sends me to the UNREVOKE method.

By the way, for some reason when I try to enter to the recovery menu (Volume Down + Power) I get a red triangle with an exclamation mark and an image of a phone at the background. I cant get out of that menu. I was trying to back up my existing ROM to the SD (Though, I think I read that this requires a root permissions.. ah well).
[HTC Aria Android Development] attn1:
If you have HBOOT 1.0+, you are out of luck at the moment for rooting and running custom recovery.

I am sure at some point the puzzle of the new HBOOT will be solved.
[HTC Aria Android Development] dexmix:
quick question. Is the antenna built into the battery cover in the Japanese Aria?

I'm still wondering why so many of the replacement battery cover's do not include an antenna as the US/AT&T Aria uses an antenna that is embedded in the Battery cover.

To identify the antenna, find the two gold color prongs inside the batter cover when you take it off.
[HTC Aria Android Development] h0r1n0:
Hi I'm Japan HTC Aria user.

The attached files are battery cover(antenna)'s pictures.

(Baseband Version:47.60.35.21U_77.14.35.11)

Please check it.

By the way, I tried Unrevoked(3.3.1) method.

But It is not working yet.

Do you have any update or solution?
[HTC Aria Android Development] tpbklake:
According to the Unrevoked changelog page (http://unrevoked.com/rootwiki/doku.php/public/unrevoked3), the HTC Wildfire and Aria/Gratia with Froyo 2.2 are still not working. HTC changed the HBOOT version on these phones so that the older root exploit no longer works.
[HTC Aria Android Development] crispcat89:
I never noticed until reading these posts but I lose service when I remove the battery cover. Lmao! Lame.
[Flipside General] Script:
I was just curious if anyone would be interested in making a step in the right direction dog such a new device. I have worked with a2sd on several other android phones(most of which already had froyo ported). I also have some experience in porting Roms to other devices. If anyone else that has already bought a flipside, and at least a pretty decent understanding on how the OS works and how to stuff like that. Also... it would be a huge plus if someone has experience in building Roms, as well as dumping them from our devices.

I'm planning on starting off with a clean and fast ROM for our phones... and hopefully with a2sd built in as well, or at least installable.

If you are interested then send me a PM and we can get to work... the sooner the better!
[Flipside General] gongo2k1:
Looking at /proc/filesystems it seems that the stock kernel only has support for yaffs2 and vfat. The stock image doesn't include any .ko files so I'm assuming all of the needed functionality is compiled into the kernel with no support for external module loading.

Using Busybox 1.18 from the Market I can loop mount vfat images without any problem (I had partitioned my SD card under Linux but it seems that init and motobox are hard-coded to load mmcblk0p1 at /sdcard and then it kept unmounting /sdcard randomly when I had extra partitions after it... so loop-mounting is safer without breaking things).

The problem is of course permissions since vfat doesn't support ugo-style permissions. We can't loop mount yaffs2 images since the emulated block device is not NAND flash... and that's also the reason we can't just dd a yaffs2 filesystem into a partition on the SD card.

I'm going to experiment with init.rc a bit and see if I break anything by forcing it to mount /sdcard immediately after /system (because that's where it should be mounting /data). I don't want to run the risk of loop mounting a file from /sdcard onto /data only to have it forcibly unmounted when vold gets enumerated and remounts /sdcard.

It's really unfortunate that there's so little space on the internal memory of this device... /cache is ~140 Mb, /system is ~180 Mb, and /data is ~160 Mb, so even if we were to lean out /system and swap it around with the others, we only get 20 Mb more on /data... that's way too much work for such little gain.

OT - Why is there so much hatred against this device? It's more than fast enough to play Quake 3 and I'd trade all the screen real estate in the world for a hardware keyboard... oh, and the phone actually fits in my pocket (unlike my friend's Droid X which is so huge and unwieldy...). Anyway, I just think it's odd.
[Flipside General] gongo2k1:
Update: It seems that the device checks that boot and recovery images are signed with a Motorola digital certificate at runtime... I can flash the partitions just fine, but it just boot-loops with "Error CC00 DBAD" and then eventually drops back to the bootloader. Unfortunately this means that I can't test any changes to mount points in init.rc at this time. Since I don't have any means to recover the device from a bad bootloader flash, this will have to be the end of the road for me at this time. Some other brave soul will have to experiment with replacing mbmloader or lbl to allow loading custom images signed with test certificates from the SDK.

EDIT: I should mention that I had to use sbf_flash to upload images since fastboot won't work until we have an unlocked bootloader on the device. I wish I had read up on and-developers.com before discovering all of this stuff the hard way. Oh well. Even the ramloader from the SBF image is signed with a Motorola digital certificate so I'm not sure that using sbf_flash (I haven't tried RDSlite, don't have Windows) is the way forward either. I don't think we can just dd the new images for the bootloader either since not all of the MTD partitions are exposed to the OS. This is going to be harder than I expected.
[Flipside General] gongo2k1:
Init.rc executes /system/etc/install-recovery.sh as a privileged user. Lucky for us, this is at the end of the init script once everything is up and running and AT&T/Motorola have removed the file so we don't have to alter anything of value. I've tested it and adding install-recovery.sh will run commands as root. This is our way in.

Hopefully we can get apps stored on the SD card soon.
[Flipside General] gongo2k1:
At the risk of sounding like I'm only talking to myself, I'll post another update...

I found that most of my troubles were stemming from waiting so long to remount /data, so I caved and put an ext2 partition on my SD card so that I don't have to wait 30 seconds before mounting over /data.

Oddly enough, mounting a native ext2 partition for /data from the SD card was actually MUCH slower than the loop mounted image. I should note that I'm not mounting the partition with the 'sync' option. I could get away with that on the loop device since it's just doing it in memory anyway and changes are only being written on the default commit interval for the host filesystem. Anyway, I'm using a 4 GB class 10 SD card, but it's still much slower than the internal flash. Just to confirm my results, I tried with a native ext2 partition on a 2 GB class 2 SD card... the phone took nearly 5 minutes finish booting to a responsive home screen!

But, at least I can mount /data right away when I'm using a physical partition... So I've done the best of both worlds by creating a ext2 partition on my SD card and then loop mounting an ext2 image onto /data. The result: I'm running my entire /data on a class 2 SD card and it's much faster than a native partition on a class 10! In fact, the difference in boot time compared to internal storage is only a few seconds! Now that I'm mounting /data right away I no longer have problems with missing apps or data after reboots. The only drawback is that you have to waste a bit of space to do it this way since the filesystem reserves 10% for itself, you need a 560 MB partition to hold a 512 MB image (in my case I'm actually running a 384 MB image since I don't really need that much space anyway). Personally, I don't mind since I'm running it off of a cheapo class 2 device and having everything in a single image file makes it super simple to migrate to a different SD card if I want to.

I'll keep running this setup for a couple days now to make sure that there's nothing else broken, but for right now I've got it setup just how I want it: no extra application to manage which apps are where and no random force closing from applications running off of SD card that weren't meant to be. Oh yeah, and I don't have to worry about dalvik-cache cannabilizing my internal storage either.

If anyone else is following along, I'd like to hear your experiences with this too. I'll post the final write-up once I'm certain that nothing else is broken.
[Flipside General] tacitapproval:
I'm definitely following along appreciatively, but will have to wait for the step by step to give it a try.
[Flipside General] ErebusRaze:
Alright, just making sure. You're last Edit:, you said that we have to run your "install busy-box.sh". To run it, is it in the script in your post above, or is there some other way? I'm pretty new to runnin' all these scripts since I'm on a Captivate which is far easier than this (I'm doin' this for my girlfriends Flipside).

Just in general, what are the steps you run your install busy-box?

Thanks ahead of time.
[Flipside General] djkaka:
thank!!!!!!!
[Flipside General] haydenis14:
can anybody help me do this because when i do it at the bottom it says failed
[Flipside General] gongo2k1:
You leave it on "Charge Only" because otherwise it will unmount the /data image and cause it to crash.

This was stated previously in my posts. Please read carefully next time.
[Flipside General] gongo2k1:
1. Install Android SDK on your computer.

2. Hook up via ADB and install z4root.

3. Run z4root on your phone. It will root the phone and reboot.

4. Install Busybox from the Market.

5. Copy the contents of the zip file to your SD card.

6. Log in as root via ADB ("adb shell" then "su -").

7. busybox mount -o rw,remount /system

8. cp /sdcard/install-busybox.sh /data/local

9. busybox sh /data/local/install-busybox.sh

10. reboot

11. Log in as root via ADB ("adb shell" then "su -").

12. ls -la /

If everything is done properly, the last step should result in an expanded directory listing in a color terminal. You can now proceed with the rest of the tutorial.
[Flipside General] haydenis14:
ok after i reboot i got look at my phone storage and it is still the same it didnt increase or anything
[Flipside General] igetsosickofregistering:
the method you've presented here sounds interesting, but i'd really hate to lose the memory card access function of my phone (i use it quite often...very often in fact). so i have a question or two:

would it be possible to get a bigger sdcard(say a 4GB or 8GB sdcard), and dd my current sdcard's partition to the new card, and then create another partition on the rest of the new card and have this method utilize that new partition in the manner described here? would the entire sdcard still get unmounted if i set the phone to memory card access?

<edit>: never mind...it seems this question would be answered by: "The script will now setup a 512MB partition on your SD card with a 448MB image for /data".....so apparently yes the sdcard would still be unmounted :/
[Flipside General] rignfool:
why would you even bother?...

search: link2sd

nuff said
[Flipside General] mlbrusby:
I backed up my sdcard and copied the files over. I have busybox and it is rooted.

I accessed superuser and copied the files over per the write-up.

When I ran setup.sh, it gave me the following error:

----

busybox found.

Usage: mount [-r] [-w] [-o options] [-t type] device directory

grep: not found

:bad numbergrep: not found

:bad numbermodule insertion failed, aborting!

rm failed for /system/lib/modules/ext2.ko, Read-only file system

Usage: mount [-r] [-w] [-o options] [-t type] device directory

----

I understand that it is a read only error, but not sure how to edit the script (or if I even need to) to get it to work. It looks like the first line of the script remounts the system properties to -rw, but it still failed to write.
[Galaxy S I9000 General] ilbulgaro89:
where the hell is the official 2.2.1 update via kies without regHack, spoofer, ecc...?

Any news?

Thanks

Edit: now available JPY for XEU without spoofer xD
[Galaxy S I9000 General] Hazurr:
They arn't, the 2.2.1 releases are as of yet only leaked beta's or release candidates.

I'd rather have samsung take their sweet time making a solid update then releasing an untested snapshot that makes the phone even worse.
[Galaxy S I9000 General] seltaeb:
I think it's been released officially for some European countries, which is why people in other locations are able to 'reg-hack' to get it.

And the update(s) don't make the phone even worse - for most part, they are a big improvement over 2.2. WiFi battery drainage seems to be the only niggling issue.
[Galaxy S I9000 General] nazrazr:
yeah i connect my phone almost everyday to check in case there is FW update but JPO still the latest!! btw ithink most people with jpx are spoofing the Kies and end effect the phone doesn´t run as what we expect such as some setting doesnt work properly and lost a few of apps (this is from what i observe from the thread!) and on that reason i prefer to wait the FW update w/o reg. hack eventhough tired of waiting....but let give some time for a perfect-ish FW!!!
[Galaxy S I9000 General] ilbulgaro89:
the update is not been released....who had already updated not use reg hack only for have XEU product code, but they use spoofer to go in kies test mode.....

Everybody update from a JPO XEU...i've this firmware, but without spoofer i can't get update....
[Galaxy S I9000 General] vannhi:
Released officially for UK.

I'm using reg-hack to update to JPY via Kies since I'm from France. It works very well, best firmware ever.
[Galaxy S I9000 General] ilbulgaro89:
yeah...now it's available!!!!! i have spoofer disablet and my JPO XEU see the update!!!! Great!!!!! xD
[Galaxy S I9000 General] Jrhoop:
Ive got official update to JPY from JPO on Kies as well. Im gonna go for it :D
[Galaxy S I9000 General] Tehpriest:
So many people leaving test mode on so much confusion..... :rolleyes:
[Galaxy S I9000 General] wingerj:
No confusion for me. JPY has been stubbornly unavailable (and I haven't resorted to the Kies hack) and today the update has appeared simply plugging in the phone.

I think now that it is safe to say that it has been "officially" released.
[Galaxy S I9000 General] mosd:
What country
[Galaxy S I9000 General] wingerj:
UK/XEU

JPY firmware
[Galaxy S I9000 General] Cyberdyne systems:
Well i had thought it official before, no one was sure if it was put out and then withdrawn or they had left kies spoofer on or something else, so forgive our confusion. Good news though if it is and more people confirm that
[Galaxy S I9000 General] taurui:
This should be exactly the same firmware that could be obtained by spoofing, right?
[Galaxy S I9000 General] _dsk_:
Interesting. I hope there isnt much difference to the one that I flashed yesterday via the reg hack! Dont think i can really be bothered going through all of that again. :P
[Galaxy S I9000 General] Geryatrix:
I'm in the UK with an XEU phone, and following the info in this thread I decided to try to update.

Connected to Keis and was immediately offered the update to JPY, I updated and it took about 25 mins, with no loss of data.

I've only been playing for about 10 mins but all seems good so far, only time will tell.

Thanks to everyone that have posted bits of info.
[Galaxy S I9000 General] marv101:
Downloading now for UK/HKDXEU, never spoofed or hacked :)
[Galaxy S I9000 General] gslayer1988:
Is it out official in europe?

Or just the UK ?
[Galaxy S I9000 General] Ibleedandroid:
I don't know about Europe.. but the 2.1.1 update on the cdma network was just to remove superuser and wifi..(verizon)

I hope its better for you guys tho. (:

Sent from my HTC G2 CM6.1.1 free your phone
[Galaxy S I9000 General] lownoise:
Whell according the SGS fus update checker server http://everyrandom.com/sgs/

select on the drop down europe and press submit.

These are the results

Europe Countries / GT-I9000HKDXEU / I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3

---------------------------------------------------------------------------------

CmdRef/Status	2 / 200

LATEST_FW_VERSION	I9000XXJPY/I9000OXAJF3/I9000XXJPY/I9000XXJPY

BINARY_URI	http://fus.samsungmobile.com/Phone_...00OXAJPY_I9000XXJPY_I9000XXJPY_XX_XEU.zip.enc

BINARY_ENCRYPT_STRING	2503541

BINARY_CRC	3145879040

GSM_NATION_CODE	XX

LAST_MODIFIED	10/12/21

CURRENT_DISPLAYVERSION	I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3

LATEST_DISPLAYVERSION	I9000XXJPY/I9000OXAJPY/I9000XXJPY/I9000XXJPY

So yes it's official and you should get it from KIES if your product code is XEU!!

all credit go's to bodhans http://xdaforums.com/showthread.php?t=884537
[Galaxy S I9000 General] marv101:
Installed JPY - phone feels really zippy now without lagfix! Quadrant of 1253
[Galaxy S I9000 General] nesx87:
Ive got XEU model, kies didnt ask me for upgrading to JPY until today. I have JPO.. Looking forward to this!!!!
[Galaxy S I9000 General] Hazurr:
i hope HKDXEN will be up next :)
[Galaxy S I9000 General] rigor.m:
I assume this version is the same as the JPY that was available through KIES hack , as the decrypt code and everything matches...
[Galaxy S I9000 General] :
Oddly Sammy are saying this on Facebook atm. But it is 2.2 they are announcing not 2.2.1 ?

http://www.facebook.com/#!/SamsungUK
[Galaxy S I9000 General] nazrazr:
just uk with pcode XEU
[Galaxy S I9000 General] :
I suppose the next question is. Is the test JPY build the same as the Official Release build? Does anyone know how to check this?
[Galaxy S I9000 General] lvvine:
Kindly post the details between the test build JPY and the official Kies released JPY

Any changes have done ?

or its the same ROM which was avialble through reg hack couple of days back?

Is this a diffrent ROM....

Kindly post it
[Galaxy S I9000 General] Cyberdyne systems:
Having compared it to my phone running vodafone branded 2.2 thats around 1000 on quadrant and runs pretty well, even the email which was bad for me before, so this should be quite an improvement
[Galaxy S I9000 General] silverstorm:
i'm in the UK, but with CPW product code, not XEU and Kies v102 also offered me JPY.

I clicked the option not to backup anything, however looks like all my apps and settings (wifi, email accounts) are still there.
[Galaxy S I9000 General] kunjar:
Smart move by Samsung, get this out before christmas so all those getting a brand new shiny SGS can plug into kies and update (perhaps)....

Hopefully it'll roll out worldwide over next few days as final version because, im getting tired of flashing, putting my handset at risk each time lol.
[Galaxy S I9000 General] Cyberdyne systems:
The things that kies backs up are contacts, music, photos and videos. If you do a factory reset (which was recommended for going up from 2.1 to 2.2) then you'll loose it all
[Galaxy S I9000 General] Fizzig:
Does anyone know yet what JPY is supposed to do better than JPO? I.e. is it worth the risk of flashing it from Kies?
[Galaxy S I9000 General] lasitha85:
Compared to jpo jpy is damn fast and snappy... And yea it is worth the risk... Trust me... After jpy its a whole new phone.....
[Galaxy S I9000 General] Tanis64:
Using JPY a couple of days now on a GT-I9000 unbranded in Germany. (using regpatcher to get it).

So far the fastest Firmware, realy snappy no lags (without lagfix) and gps is much faster and better now also.

Now you have a device in the hands thats realy worth its price!

Regards

Christopher
[Galaxy S I9000 General] chrisjcks:
I'm in the UK, and I got my update from JPO to JPY today.
[Galaxy S I9000 General] Cyberdyne systems:
Just upgraded, factory reset, reinstalled everything i had from before and ran quadrant, only get 1080, more than before but not as much as some say.

Thing is it seems quicker and works fine, the email app which was my biggest lagger is working well now and phone generally feels faster, even the quadrant itself is quicker to perform, but just gives a lower score?
[Galaxy S I9000 General] chrisjcks:
Yeah, I only got 1100 exactly after the official update, on the leaked one I tried last week, I was getting 1250+
[Galaxy S I9000 General] Fizzig:
Thanks for the info seems worth the risk... Except I have Voodoo 5.0 installed over JPO... Quadrant 1400 (I know it's not a perfect reflection of real world performance but I have noticed a reasonable correlation so far). How do I easily take off Voodoo before I flash via Kies... (I used a one click lagfix to get Voodoo into the phone in the first place...). Is it going to work better than what I have(I mean feel and function of the phone not it's Quadrant score)?
[Galaxy S I9000 General] android53:
Jpx firmware and onwards are great. Samsung have really upped their game
[Galaxy S I9000 General] chrisjcks:
Hmm, I installed voodoo 5.0.3 kernel, applied lagfix and system conversion then removed it and quadrant now shows 1250, so maybe the installation via kies messed up something that voodoo fixed.

The question now is, should I use the lagfix or not?
[Galaxy S I9000 General] Fizzig:
Does the Voodoo website give a list of compatible ROM versions for each kernal?
[Galaxy S I9000 General] chrisjcks:
Ive put voodoo back on, getting 1650 on quadrant now.

There are different versions, im using stock+voodoo for JPY 5.0.3

For firmware versions pre-JPU, you need to use 5.0.1

What firmware are you using,?
[Galaxy S I9000 General] d3ck4rd:
Does anyone else find that the battstatt widget doesn't work after updating to JPY?

Its just stuck saying "loading..."
[Galaxy S I9000 General] alexhull24:
If you update battstatt to the latest version it should fix that.
[Galaxy S I9000 General] d3ck4rd:
I checked and the app was up to date. I tried reinstalling it though and that worked