yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Fornowagain:
Could someone with a UK phone that has updated please check the code using *#272*XXXX# ?
[Galaxy S I9000 Android Development] kuwari316:
My code is swc
[Galaxy S I9000 Android Development] Fornowagain:
Interesting, that's a Switzerland code. Wondered if a UK code like XEU was needed. Changing JF3 to all of the region codes still didn't find any updates. I'm at a loss to think why it won't get the update. Started as an O2 phone.
[Galaxy S I9000 Android Development] esticbo:
Sure because you have a Spanish SGS and the M3 is for Italy (ITV).

I try to put my Spanish SGS with *#272*HHMM# in ITV with the F3, but kies won't update my SGS to the new firmware
[Galaxy S I9000 Android Development] Bynar010:
Fyi managed to get my sgs back to official jm1 after flashing non official firmware -

Download JF3 from samsung firmwares

Flash with 513 pit file, choose repartition option

Start kies firmware upgrade and press ctrl-alt-u-p to put it into test mode

Connect phone, will see JM3 as the latest firmware

Upgrade phone firmware, you'll actually end up on the official JM1
[Galaxy S I9000 Android Development] kuwari316:
that is exactly what i did and my phone isn't from Switzerland, i dont know why i have a Switzerland code for it
[Galaxy S I9000 Android Development] Greg82uk:
During my experimentations, I found that the JF3 from Samsung-Firmwares seems only to have the option of being Swedish. I'm not more than convinced that we O2 users will have to wait for an O2 update to be made available in order to upgrade (pure speculation based on the 20 odd flashes I've done in the last couple of days in the attempt to get back to an official firmware). I tried the Vodafone JF3 also... but alas still no joy (although I didn't explore the sales codes with that one). I am now back to the unofficial JM2 with the modem from the JM5 pack.

I am now wondering whether obtaining a sim-unlock code from O2 would unbrand the phone sufficiently to obtain none o2 updates.. Any thoughts on this one?
[Galaxy S I9000 Android Development] Greg82uk:
Ooooh... S-F has a *new* JM1 update available.. I wonder if this is the one which has been released through Kies!
[Galaxy S I9000 Android Development] Bynar010:
Jf3 from samsung firmwares has 2 csc files with it, off top of my head I think one is XA other is SWC or something, you need to make sure you use the xa one. Sorry in bed so can't check exact version names!
[Galaxy S I9000 Android Development] kuwari316:
i think it is the new one from kies, why not try it out
[Galaxy S I9000 Android Development] n1kon:
The update is not available for all countries, UK being one of them. I'm doing a little research on this here http://xdaforums.com/showthread.php?t=762458 If you want to get the update you need to change your product code to one of the ones that can update in my post, but the firmware you get will be the update for that country.
[Droid Eris Android Development] tenzomonk:
good stuff!

i've never used clockwork... and from my observations... GOOD!

in any case... this should help many users (i personally only recommend Amon).
[Droid Eris Android Development] midnight assassin:
What was the version the caused the issue? can't you also flash amons from clockwork in rom mgr then delete rom mgr? or would that not work? thank you.
[Droid Eris Android Development] edge.thefly:
Not sure of the exact version as I don't personally use rom manager (kinda a manual guy) but I think it has been fixed in the most recent release. As for using Rom Manager to reflash I can't say for sure either but this method is pretty simple and already resolved two cases. I believe stick may have tried it he was in IRC with us for hours and we were bouncing everything we could think of at him but he got sig verification failure in a flash using it not knowing the issue and corrupted his userdata partition.

If there are any more questions I will have to answer them when I wake up because I'm nearly sleeping in my chair right now :)
[Droid Eris Android Development] midnight assassin:
thanks for the answer and putting this together. I know there are a lot of noobs like myself around here lately who may benefit from this and the time you put into it. thanks for makin it simple.
[Droid Eris Android Development] homewmt:
Thanks for the great post.

I just have to say theres an easier/alternate way to do it

1)download rom manager.

2)at the bottom of rom manager click flash alternate recovery.

[PC WAY]

As pointed out by bftb0 the below method will only work for those on HBOOT 1.49.2000 S-OFF bootloader. (those who flashed the original root rom)

1) download amon's recovery from this thread http://xdaforums.com/showthread.php?t=648025

2) (if you don't already have the android sdk, download it) If your in Windows fastboot is included in the android sdk, if your in mac or linux go here http://developer.htc.com/adp.html and scroll down a bit, click download and move fastboot to your /sdk/tools folder.

3) with your phone connected to your computer and off hold the power and send buttons at the same time until fastboot comes up on the screen.

4) open cmd/terminal and cd to your /sdk/tools folder, and type in "adb flash recovery <path to amon's recovery>"(if your in linux or mac type ./ in front of fastboot).

5)reboot your phone.

I personally use clockwork recovery and have had no problems, though I do not suggest it for anyone. (unless your trackball is as messed up as mine is, I can't even scroll down in amon's recovery)
[Droid Eris Android Development] bftb0:
A couple of comments.

Stick's phone

A corrupted "userdata" (/data mount point) alone might prevent the OS from booting, but that should not effect the ability to start the phone in HBOOT, FASTBOOT, or RUU (oem-78) mode. I didn't sit in on the IRC, so maybe I'm missing something, but there really are only three things which will completely brick the phone:

- screwing up a flash of the (512 kB) bootloader

- screwing up the NVRAM area

- (maybe) screwing up the misc partition

You can screw the pooch in /boot, /recovery, /system, and /data (aka "userdata") - even all four of them at the same time, if you please - and your phone should still not be bricked.

If the bootloader can not be started (in any mode), then that is absolutely a bricked device; OTOH, if you can start up the bootloader in HBOOT mode, the only thing that would prevent you from re-flashing the Leak-V3/"Official" PB00IMG.ZIP file is corruption of either the /misc partition or NVRAM. None of the dev ROMs touch those areas though. So, it is very strange that someone using any custom recovery would cause corruption of those partitions. Is Stick really bricked?

I once corrupted my /system partition which caused it to be unmountable (in Amon_RA) by doing something dumb (twice!) - but re-flashing the entire ROM (HBOOT+PB00IMG.ZIP) overcame that and gave me an earlier starting point from which to re-root and recover via Nand. There is evidence, from looking at the string data contained within the bootloader that it knows how to recreate the partition tables in flash memory - presumably this would be needed if HTC shipped a ROM which needed more space in the /system or /data partitions than existed in prior ROMs. Whether it does that for normal PB00IMG.ZIP-style ROM flashing, I can't say - but there are hints that the HTC bootloader knows how to deal with flash memory in which the entire partition table has been destroyed.

PC-based method

Step #6 in the first set of instructions will not work for rooted (dev) ROMs which do not start adbd as root (that is, "adb shell" from the PC does not launch a root shell). Most dev ROMs do that, so perhaps this is a nit-picking point. If "su" is available in the ROM, prefixing the command with "su" should work, though - just as in the PC-less example.

Use of fastboot

homewmt should probably edit his post to add the disclaimer that using fastboot for flashing of recovery will only work for folks who gained root by flashing the "Root-ROM" (or post-installing it after root was gained), which gave them the 1.49.2000 S-OFF bootloader. None of the other bootloaders will let fastboot do this. I think it is important to mention this because a lot of the new rooters are using either the "One-Click" or "Dummies" (AF) methods to install a custom recovery - and so they never touch their bootloaders.

bftb0
[Droid Eris Android Development] kzoodroid:
So as long as you can get the boot loader up (power + volume down) then you can still use the 2.1 RUU (for those with HBoot s-on) to get the phone back working?

I think people assume that since the moded recovery image is fried that means the phone is bricked since you can't get into recovery on the phone to restore a backup.

Myself I've been using Clockwork Mod Recovery for 3 months without any problems and I've flashed a lot of ROMS and restored a lot of backups. Both using the recovery console and ROM Manager. I'll never go back to Amon's as I see no point and Koush is at least updating Clockwork on a regular basis.
[Droid Eris Android Development] edge.thefly:
Yes stick is really bricked. He had access to the recovery but got a sig failure which terminally corrupted his userdata partition and the only option available to him was fastboot which would throw a sig failure at any attempt to flash over (even tried PB00IMG and RUU at the end)

NOTE: Good catch on #6 I edited the OP to drop into a shell then su in.

This is inadvisable as stick tried the RUU which is what killed off his ability to enter hboot
[Droid Eris Android Development] bftb0:
That is truly bizarre. I don't know what Clockwork does for checks, but Amon_RA performs (in the verification step) the equivalent of a "jarsigner --verify" operation: it computes the SHA1 hash of every last file in the .zip archive, and compares those sigs to the manifest. If even a single file is wrong, it won't proceed to the install, but just bombs out on a verification failure. The upshot of that is - in the Amon_RA (or stock recovery update.zip) case - it is literally impossible to install a corrupted ROM file.

In the case of HBOOT and PB00IMG.ZIP installs, a "whole-archive" signature is performed - the individual images are not inspected, but that doesn't matter: if you touch a single bit anywhere, even in the .zip file directory, that verification step will also fail.

So - in both of those examples, the only way to burn something wrong onto the phone is if the files get corrupted internally to the phone, after they have already passed signature checks - or if they are read off the SD card differently between the verification pass and the install pass!

Do you know if Stick has a S-OFF bootloader? (i have a tricky idea, if so) I suspect he doesn't, because if fastboot passes a privilege check, I don't think there are ever any sig checks performed by the phone when the bootloader is in FASTBOOT mode - all you have to do is have a S-OFF bootloader, and you can write total crap to the phone.

bftb0
[Droid Eris Android Development] edge.thefly:
I'm almost certain he had S-ON but hes not around right now so I can't verify.

I should also note that while he can still power on the device he only has fastboot access it wont even get into bootloader or recovery at this point.
[Droid Eris Android Development] rrem:
thanks edge this work like a charm (:
[Droid Eris Android Development] bftb0:
Ugh. Vol-Down won't get him from FASTBOOT-USB mode to HBOOT?

Sux.

I was going to suggest - only if he had the S-OFF (1.49.0000) bootloader - that he could boot to a recovery image without ever flashing it to the device, e.g.

[B]C:\blech> [COLOR=green]fastboot boot recovery-RA-eris-v1.6.2.img[/COLOR][/B]

Even if he had S-OFF, and can get a recovery boot up on it's legs, it might still be a long uphill climb if e2fsck/mke2fs can't repair/rebuild /dev/block/mtdblock5 (for instance if the mtd device is so corrupted that the partition map got thrashed).

But that route is a no-go if he has a S-ON bootloader.

bftb0
[Droid Eris Android Development] infamousxsniper:
What's the difference between Amon and Clockwork?
[Droid Eris Android Development] edge.thefly:
Good question. I personally dont use clockwork but...

the navigation interface is different (uses volume keys to select instead of trackball)

Amon_RA is far more tested and reliable on Eris

and of course the general consensus that clockwork should NOT be used on the eris.

NOTE: I am sure there are other internal differences someone like bftb0 or koush would be more apt to give a detailed explanation.
[Droid Eris Android Development] Macrodroid:
I've been using clockwork for a while now... I haven't had issues yet. What kind of problems have people had with this, anyway? There is an option in rom manager to flash back to Amon ra...
[Droid Eris Android Development] edge.thefly:
The usual, failed flashes failed nandroid backups i heard something about a random reboot issue but that could be unrelated and of course the one case of corrupted partition/inability to get into hboot or recovery resulting in a brick.

I will note some people are using clockwork without issue and for them great but it is not advisable on the Eris at this time though I do realize some people have trackball issues and have to in which case best of luck to those few brave souls.

NOTE: If you have trackball issues i advise you to attempt the usb wiggle method. there is some sort of connection between the usb housing and the trackball down sensor that makes the trackball register a down movement when the usb gets rocked in a downward motion (extra note. be gentle)
[Droid Eris Android Development] rrem:
maybe you should post this on OP (: the trackball issue that is
[Droid Eris Android Development] rougegoat:
so...I'm not at my normal computer(and I can't get Root Explorer because my card always screws up when it converts from US to any other currency) and am trying the On-Phone method via Astro. The issue I'm having is I cannot get it to show me the /data/local folder. I can't find any tweak for it in settings or anything. There's no read only error or anything like that, so I don't think that mount command in the first post will help very much. I'm fairly new to Android hacking, so this could easily be something I just don't know yet. My gut says it's a permissions thing, and that since Astro is meant for normal users it just doesn't set itself to show the restricted stuff by default.

So I guess does anyone know how to make this folder appear in Astro?

(I've been meaning to change back to Amon_Ra for a while ever since I noticed that RomManager deleted the other recovery program. Just can't trust something that does that.)

[edit] tried the command to remount as a rewritable et all that jazz(mount -o remount, rw /) and no change.
[Droid Eris Android Development] edge.thefly:
Do you have Superuser installed? My astro sees those extra files and it isnt in my Superuser permissions list.

However if you cant get past this issue go ahead and use the terminal emulator to perform the move.

su
mv /sdcard/download/flash_image /data/local
[Droid Eris Android Development] rougegoat:
I have Superuser v2.3.2.3 installed. The rom I'm running now is the KaosFroyo v30 if that makes any difference. The Astro thing is gonna bug me now, but I guess I can rely on good 'ole ls from terminal should I really need to know system file contents.

I never thought I'd miss a tab key so much as when I was typing file paths by finger on a touch screen.

After some frustration due to mistyping on my part, I got it to work. Back on Amon_Ra, the one that doesn't randomly delete files for me!

Thanks again for the tips and guide.
[Droid Eris Android Development] edge.thefly:
No problem :) I love to help.
[Droid Eris Android Development] Sjflowerhorn:
You can flash the alternate recovery from rom manager directly, much easier to do on the fly. But also the issue was fixed. Works fine now.

But don't take that as me recommending it. I am NOT responsible for sh#t.
[Droid Eris Android Development] kzoodroid:
You can't have two recoveries running at the same time and ROM Manager doesn't delete Amon's recovery when you install it. The first time you use it a message pops up telling you that you have to have Clockwork Mod Recovery installed to use it. You then have to select install Clockwork Mod Recovery from the options. So you made a conscious decison on your own to delete it. If you paid the $1 for Rom Manager you then should be able to use the flash alternative recovery from the menu and reinstall Amons recovery.

As far as Astro goes I don't believe it can access the root folders you need root explorer to do that. But I don't use it but I have used ES File Explorer and that too cannot access root folders. I paid the $1 for Root Explorer. I would suggest setting up a Google Checkout account so that you don't have problems buying apps in the future.

As far as the OP goes I'm wondering if they could get a recovery image back onto the bricked phone using the race method that I used to orignally root my s-on phone. The method captainkrtek published back in June.
[Droid Eris Android Development] edge.thefly:
Nope. Unfortunately the bricked phone has no access to anything. when it boots its black screen then when you plug in usb it has HTC and /!\ in all four corners. No hboot no recovery only fastboot commands and any attempt to flash over userdata or erase userdata results in fail.
[Droid Eris Android Development] midnight assassin:
what was the issue?
[Droid Eris Android Development] Sjflowerhorn:
Not too sure I just saw they added support for the eris(cdma) pretty recently. I wouldn't suggest you use it still because RA is proven, and the developers would have cleared ClockworkMod with everybody if it was 100% safe. I use it because I enjoy the ability to flash from a folder on my sdcard and flash multiple zip files at once instead of flashing the rom then all of the patches one at a time. It does have some cool features. You can flash ClockworkMod recovery and RA(alternate) recovery from the free version BTW.

KAOSFROYOFTW!
[Droid Eris Android Development] edge.thefly:
Sorry helping my friend put 2.2 on his X. If anyone has problems don't hesitate to ask.
[Droid Eris Android Development] stick2e:
rest in peace!

I had try so many thinks that is not even funny. I had no results at all, so I have a nice Droid Eris paper holder now :-(

Thanks for all the ideas and suggestions.
[Droid Eris Android Development] the_rhino:
Thanks, it worked like a charm!
[Droid Eris Android Development] edge.thefly:
:-( Sorry man. Its a rare miss for us but at least you have been able to help many here and inspire a fix. I'm still bummed personally I hate to see good hardware brick :-/

#- rhino n/p man thats what we are here for :)
[Droid Eris Android Development] PepsiTom:
Another Bricked Eris?

I am hoping that I haven't joined Stick in the bricked Eris club. Here's what happened:

1) I paid for the Full version of ROM Manager this morning.

2) I ran ROM Manager and let it install the updated Clockwork Recovery.

3) I decided that this would be a good time to let Rom Manager do a backup, so I initiated the backup process.

4) The phone rebooted, but did not boot. I found myself at the HBOOT menu with just one item listed, FASTBOOT. Nothing I did would select FASTBOOT. (I tried all physical buttons, with a reboot between each). Note: The only way to get the phone to power off was to pull the Battery. I only did this when looking at the main HBOOT Menu, never during any of the steps below.

5) Below FASTBOOT was the text: <VOL DOWN> HBoot Mode. That was it. No other options. In desperation, I pressed the VOL DOWN button. This caused the device to load PB00IMB.zip... or so it seems. After Loading the file, the phone rebooted right back to the HBOOT menu, as in step 4. I have been thru this several times, but no luck, always back to the HBOOT where nothing but <VOL DOWN> works.

6) Somewhere along the way I thought to try powering on with the VOL UP and VOL DOWN buttons. VOL DOWN didn't do anything. VOL UP gave me the option to Clear the memory. At some point I tried that as well. This did not change anything.

So now I sit here, with a phone that won't boot, hoping for some help. I went to the IRC channel on FreeNode and asked for help, but no one replied to my message. I have the SDK Tools installed on my computer, but they won't see the phone (not even Fastboot.exe). Any ideas or suggestions?

Thank you,

Tom
[Droid Eris Android Development] Macrodroid:
When you power off/vol up, do you get into clockwork recovery? I use rom mgr as well and never had any backup issues. Send me a pm with some more details and i'll help you through it. The fact that you get into any recovery means your not bricked yet. What hboot are you on?

Sent from my Tazz Froyo 3.0!
[Droid Eris Android Development] Macrodroid:
Using the alternate recovery from rom manager doesn't mean amons ra will be in control. Tried to use that once, amons ra comes up, but only after clockwork reconfigures recovery, so clockworkmod is still in the recovery partition. I've never had a problem with clickwork, but there's alot of options in cw that could "help" you brick your phone, if you're not paying attention.

Sent from my Tazz Froyo 3.0!
[Droid Eris Android Development] sungal:
I wish I would have read this thread sooner - yesterday my Eris became a brick :( I had no idea clockwork didn't play nicely with an Eris and I guess I learned the hard way...not sure if that is what caused my problems but it sure didn't help me either.

I'm awaiting the arrival of my replacement Eris this morning and def. plan to root this one too, but this time I will know more than I did before. Thanks for the info!
[Droid Eris Android Development] Captainkrtek:
Also you can flash amon_ra from inside rom manager I think
[Droid Eris Android Development] edge.thefly:
From what I've heard you can. I don't personally use rom manager but if it can flash a recovery it should be able to flash amon.
[Touch Diamond, MDA Compact IV ROM Development] KingBonecrusher:
Hi!

I will start to install Android CM6 on my Diamond. Why only 500MB are allowed for the second ext2 partition after fat32?

Can i use under Android the first partition too, or only the 500MB. Or maybe the 500MB is only for the System, and data comes on fat32? 500MB is real small...

regards
[Touch Diamond, MDA Compact IV ROM Development] _Opiate_:
Hmmm Im am interested to know this as well. 500mb is rather small for a partition.
[Touch Diamond, MDA Compact IV ROM Development] neopeek:
Don't go higher than 512MB and don't go less than 256MB for ext2. I am using 350MB for EXT2 and that's fine. You are able to use full size of FAT32 with my Android builds and sure this Fat32 is also usable under WinMo.
[Touch Diamond, MDA Compact IV ROM Development] KingBonecrusher:
Thx! That is great, so i will shrink down to ~3,5GB, ~436MB ext2 and ~64MB Swap. Primary, not extended partition?

Ist ja nett hier gleich einen Landsmann zu treffen ;-)
[Sony Ericsson XPERIA X10 Mini] bingobadgo:
If, hypothetically speaking of course, I had some pictures in a folder containing a .nomedia folder to hide them from Album, is there a way to use them as wallpaper? I have tried setting the wallpaper using Astro as the selector instead of album and I can browse to the image and select it but then it freezes and never gets to the screen where you crop the paper. Also, even when using "normal" images, I have noticed that when I go to change the wallpaper it will hang after I "Select wallpaper from" Pictures, necessitating me pressing the back key and having to restart the process. It always starts the second time but is quite slow.

Any ideas?
[Sony Ericsson XPERIA X10 Mini] Lordje:
I think you can use those pics as wallpaper by browsing to them with a filemanager....

Then just push on the photo and select the menu button in the lower left corner.

Select set to background...

That should work...