yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] jfilippo:
Thanks for the fast answer, you've been answering 3 people back on this thread, impressive.

Unfortunately I made sure of that, the auto reboot was checked but it doesn't reboot the device. I wanted to put a screenshot but I didn't realize you need around 10 posts to be able to post outside links. I've been looking through xda for a while but never posting.

I'm used to adb, so Odin is a bit new I have to admit. I've put the ops file, callisto in this case, in the appropriate ops , and then the One Package file I got from samfirmware "I5510UGKC5_I5510BMCKC5_BMC". Is there something else I could flash? It wouldn't be like some other phones where I could put down a Custom Recovery, go back to stock, etc. ?
[Android Q&A, Help & Troubleshooting] shimp208:
To clarify did you put the firmware in the correct slot in Odin (PDA slot in this case) when flashing? Also double check your flashing the correct firmware for your device, as that could also be part of the problem.
[Android Q&A, Help & Troubleshooting] jfilippo:
Well you figured some things that were wrong. I was putting it in the one package slot. So I tried in the PDA slot, but it said "Invalid Image Type". From the sticker inside the battery compartment, it does say it's the GT-I5510M, so the 551 from Bell Canada it seems. But it's not easy to find a firmware for it, and the only one I found is at sammobile. There's plenty others under GT-I5510, but they're all European.

Any idea what I could use instead? The full name of the firmware I have is: "I5510UGKC5_BMCKC5_HOMEDOWNLOAD_TEST.tar" or "I5510UGKC5_I5510BMCKC5_BMC.zip" for the zip.

Thanks a lot for following this.
[Android Q&A, Help & Troubleshooting] shimp208:
You can try ignoring the "Invalid Image Type" error and trying to flash anyway just don't unplug your phone from Odin until it fully completes the process.
[Android Q&A, Help & Troubleshooting] jfilippo:
I did, but didn't work, I should have mentioned that. So the screen is still blank. But another driver got recognized and installed once the firmware was installed, Samsung com 3 if I remember well. I was hoping when I saw that!
[Android Q&A, Help & Troubleshooting] shimp208:
With the new COM port being recognized try the procedure again and see if it has any different results.
[Android Q&A, Help & Troubleshooting] adisawant:
sorry to interrupt you people.. but are you sure that it is a proper firmware file. because the pda file is .tar file. also, try entering the recovery mode and flashing a cwm recovery. then check if the system is mounted.
[Android Q&A, Help & Troubleshooting] jfilippo:
Sorry I've been away, meaning no phone and laptop with me. Thanks for the replies. I tried to flash again the firmware last week but nothing happened unfortunately.

I can't access recovery mode, only download mode by simultaneously putting the battery back in and pushing Q+Power. But I am wondering also if it could be a wrong firmware... Can I just flash a custom rom through Odin? Would that make up for it? Anything to having back in working order.
[Android Q&A, Help & Troubleshooting] adisawant:
i dont think flashing it will help. Just try to download another firmware and flash it.
[Android Q&A, Help & Troubleshooting] kunal1020:
anyone can sell samsung galaxy 551 i want to buy please call me 7384388281(india/kolkata)
[Xperia Arc Android Development] arcatarc:
http://xdaforums.com/showthread.php?p=32867696#post32867696

Optional but raccomanded click this(51% will be donate to UNICEF):

EVERY DAY CHILDREN DIE NEEDLESSY!!!

https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=Q94WGHC4F2DH2
[Xperia Arc Android Development] CarrotAk23:
Can you put some screen shots to prove it?

EDIT:Tested

I got 1240 in JB Andreno driver V3

And 1147 in this lib
[Xperia Arc Android Development] rocco6victor:
haven't tried making a video to check if it improves encoding, but i can't see much improvement compared to iridakis v3 jb drivers

thanks anyway

first screenshot is previous jb drivers and 2º is with these ics drivers
[Xperia Arc Android Development] Destroyedbeauty:
Those drivers made the Arc S laggier, are going back to JB V3 drivers instead..
[Xperia Arc Android Development] arcatarc:
8 June 2013 updated (Xperia Sx GPU Driver added)

8 June 2013 updated (Xperia Sx GPU Driver added)
[Xperia Arc Android Development] ahmadzxc:
any tried the new driver ??

is make a difference ?

can i use it with 3.4.x kernel ??

thanks
[Xperia Arc Android Development] GaboWinter:
Thread closed, on the OP you could find the thread in use, please go to that one for all the related discussion about the drivers.

Regards

Gabo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
dsixda's Android Kitchen - Now for Samsung Galaxy SIII SGH-I747

Compatible with Windows (Cygwin) / Linux / Mac OS X

The following is a guide to assist you with creating your own Samsung Galaxy SIII SGH-I747(M) (AT&T, Rogers, Bell, Telus) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.

Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I747 ROMs with the kitchen.

I have already posted an equivalent thread for the T-Mobile SGH-T999 Galaxy SIII, so no need for redundancy. The same steps will work for your device:

CLICK HERE FOR KITCHEN INSTRUCTIONS FOR YOUR GALAXY SIII.​

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

Since the above link is for SGH-T999 discussion only, please post all SGH-I747 talk in the thread right here. Enjoy!

​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Nice, will check this out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
I've been waiting for something like this for our phones. Thanks for your hard work, the time and effort in creating something like this is very much appreciated. :good::)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatsupnow:
Yea this android kitchen is awesome!!! I wasted no time trying it out, and its really straight forward too. Thanks again dsixda!

Oh yea!? Thems fightin words....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuRock:
Thanks dsixda. Will be looking into your kitchen!:D

White Hot! GS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Nice! I have been using older versions of the kitchen on my GS3 to deodex with minimal issues. Going to update right away. Thanks Dsixda!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smartguy044:
Thanks dsixda I have been using kitchen since the note even though it wasn't supported with 0 problems glad to see you are supporting the s3 even though I never had problems with it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
dsixda: Thank you for such a great tool. I've written my share of scripts so I can definitely appreciate how much work something of this size has in it. I've used your kitchen for de-odexing pretty much every ROM I've built.

About that, does API 16 work with the kitchen now? Just curious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
Hmm not sure, since the latest smali tools were released in September
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markdexter:
your the Man Dsixda!!;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Oweida:
Sorry of being off topic

Hi Dsixda

I'm a big fan of your work and I'm using your kitchen in my own custom roms :)

I don't whether you heard about this or not Qube 2 and me managed to port HTC one X rom to international S III. we still struggling with some stability issues along with ril issues as well.

Now I've got At&t variant of S III which has exact similar hardware of At&t HTC one XL. intially I thought porting would be easier as both has the same hardware but the rom won't boot and I frankly don't know why !!

I'm wondering if such a thing gets you interested to help me ?!

Now I'm really sorry to post this here and to use this thread for off topic subject.

Thanks and really glad to have you here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tiffany84:
This is awesome!! Thanks so much for all you do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
Thanks for the comments. Na, I don't know anything about porting, and I'd rather not spend more time sitting at a computer, especially considering my health.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
BIG thanks. Now to remember how to use the kitchen again…
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustard007:
Hi !

Great works !! Thanks !

I try it with a Stock ROM (Last Bell), and when I make the option 9 (Checkup), I have this error in the list:

>> ERROR: wiperiface_v02.so not found in working folder

Can I skip this error or how to fix it ?

Thanks !!

??

Also, someone have a good place to start to add MOD, THEMES, SOUND, etc.. to our custom ROM we make with this kitchen ?

Thanks !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
Ok, it’s been a while since I used the kitchen. For my project, I’m using a stock rooted rom (UCALG1). I was hoping to use a nandroid backup from CWM. I use to do this quite often for the Nexus One. On the SG3, the nandroid backup files for the system are –

system.ext4.tar

system.ext4.tar.a

system.ext4.tar.b

The “a” & “b” have file size (different sizes) and the system.ext4.tar is empty.

There is only one boot.img file.

Looks like I can rename

system.ext4.tar.a

file and drop “a” and that will be the valid file to use. I’ve gone thru most of the steps, just wondering if anyone done this on a nandroid backup?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
Did you add the Wipe Data option?

Sent from my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustard007:
I will check that !

Thanks !

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zerolock:
Status 0 error flashing.

So when I use the G1 ODIN rom base with the only changes being deodexing and rooting, I get a status 0 error on the flash.

I'm using the updater-script that the kitchen is making, to no avail.

Has anyone else come across this? If so - how did you fix it?

I am convinced that the updater script is the issue, there is some symatical issue in there - mounting something wrong I am not sure, though I could be wrong - often am.

I will try this weekend with a captivate stock rom and my cappy, but the target is the AT&T GS3.

dsixda - great work I love it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
Hi dsixda,

I’m using att’s new JB rom from mrRobinson in your kitchen. I mainly added some items in the /data/app section. When I flash the rom, I receive the following error message -

Status 0 – Installation aborted. Can’t partition non-vfat: datamedia. Can’t partition unsafe device: /dev/blockmmcblkpl. Can’t format unknown volume: /emmc

This has actually has been happening on all the stock ICS roms I have attempted to create in the kitchen. Must be something simple I’m doing wrong in the SG3. Never had an issue creating roms for the SG2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
The kitchen is not going to support S3 custom roms by other people, if you mean it's a zip file (or maybe I misunderstood?).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
mrRobinson's appears to be a clean stock tar w/root. I also used another stock tar from the following link.

http://xdaforums.com/showpost.php?p=34986428&postcount=1

I had the same error message using non-custom ICS roms. I prefer using stock roms to modify. If there any log files I can send, let me know. Thanks for the reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
Did you actually use /dev/blockmmcblkpl? That is wrong, there is supposed to be a backslash after the /block.

The kitchen doesn't use datamedia or whatever that partition is, it just works with the basic partitions - system, cache, boot, data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zerolock:
I believe that i had a fix for this and completely forgot to send it to Dsixda over the Holidays.

You can get me on twitter @nine13tech

Let me dig up the fix that got me past the flashing issue, now dealing with a boot loop, but cannot go back to the development since i need the phone to find a new job. I am 90% sure it's in my notebook, but it is changes in two files within the kitchen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Thanks so much for the updates! I've been meaning to try this someday, and since I'm impatient to wait for a deodex stock JB, might as well give it a whirl myself and start today!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
After the error, I selected in CWM, in Advance, to Show Log. It then displayed that following error. I did my best to type the error message exactly as it appeared.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
Hi zerolock, let us know here in this thread when you find it. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
Hi Silverexp,

Can you post your updater-script? Status 0 sometimes means there was a partition error, where it may have been defined as MTD when in fact it is some other type like EMMC.

Regarding the error: "Can't partition unsafe device: /dev/block/mmcblk1p1" --> that is your /sdcard I believe. This error is mostly likely normal and not related to the ROM, as I've seen this kind of error on my devices before as well. Sometimes the developer of the custom recovery didn't define certain unused mount points correctly, and hence the message, but it's not really an issue and can be ignored.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
Thanks dsixda,

Attached is the updater-script the kitchen made for the rom. I am on ver.217.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
That's the update binary, not the updater-script!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
sorry, selected the wrong file.... here is the correct one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
Yup, exactly as I thought in my previous reply, the mount types are wrong:

format("MTD", "system");
mount("MTD", "system", "/system");
package_extract_file("check_data_app", "/tmp/check_data_app");
set_perm(0, 0, 0777, "/tmp/check_data_app");
run_program("/tmp/check_data_app");
mount("MTD", "userdata", "/data");

What is the exact value of ro.product.model in your build.prop? Secondly, what is your operating system?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
The ro.product.model is SAMSUNG-SGH-I747 and I am using WIN7-32.

Just re-ran the kitchen and this time notice the following message…

Device name in kitchen, or variant of: d2att

Please ensure these device mount statements are correct:

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

mount("MTD", "system", "/system");

mount("MTD", "userdata", "/data");

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

Copying update-binary ...

`../../../../../tools/update_files/mtd-update-binary' -> `update-binary'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
OK that is the problem. Weird that yours has a different name. To fix it, all you need to do is to go to tools/samsung_files/model_variants/galaxy_s3/SGH-I747/, and add a blank file with a filename equal to the model name you just mentioned above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
Thank... I'll do that. It will be late tonight before I can attempt this. Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
Hopefully by then I'll have a fix up with this change. Thanks

EDIT: I've put up 0.218 with the fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silverexp:
Thanks for the update. I’ve attempted the last few days to create a new stock I747UCDLK3 rom. I’m now getting the Status 7 error.

Assert failed: write_raw_image(“/tmp/boot.img”,”/dev/block/mmcblk0p7”)

E:Error in /external_sd/[filename.zip]

I ran the utility to check the update-script and it didn't find any errors. If I read this right, boot.img is the issue. Is there a way to check it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
It means something is wrong with the mount point used (read the FAQ). I don't know specifically what the problem is on your device as it worked before on others.

You can also Google it, there are a lot of results for your problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
In case anyone is wondering, the kitchen worked GREAT on my stock LK3/JB/4.1.1 AT&T GS3. I used it to de-odex and it worked like a charm!

Three tips for those who need it:

1) If you're using a TWRP Nandroid: you're probably using compression. Thus, the system.ext4.win you have is simply a tar.gz file. The gz -> compression and the tar -> simply storage of multiple folders in one file (think of a zip without any compression). To get the system.ext4.tar that the kitchen wants Rename to system.ext4.tar.gz and use 7-zip. 7-zip, for whatever reason, will decompress AND extract it. So, you'll get all the extracted folders--oh, no! Simply use 7-zip to tar them back (obviously using the only available "store" option in compression).

2) Related: if your system.ext4.tar gives an error in the kitchen like ".... is not a tar archive!". Easy fix, after looking at the kitchen's Github code: in your tar archive, the root of the folder MUST contain a parent folder called "system" and all the system folders (app, framework,etc.) go inside that.

So, system.ext4.tar -> system folder -> app folder, framework folder, etc. It can't be system.ext4.tar -> app folder, framework folder, etc.

3) The boot.emmc.win from the Nandroid backup will NOT work in Nandroid. I asked the TWRP devs and they said it would require an unpacking script. The kitchen can "fake" a boot.img, but I wanted the real thing, haha. :D Simply use this code with the? modified.

# adb shell
# dd if=/dev/block/mmcblk0p? of=/sdcard/boot.img

Modify the "?" to the correct number for your device. To determine which mounting block the boot is on, write this in adb shell:

ls -al /dev/block/platform/msm_sdcc.1/by-name

For me, the /boot partition was 7, so this:

# dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img

Came out to 10MB. :D

~Ibrahim~
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Might be that the boot.img isnt there or is named differently

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ascyndaeon:
Hi! I've been trying to create a ROM from stock and am having trouble.

So my first build, after doing everything I wanted to the ROM, was unflashable. I got a status 7 error in cwm and so I consulted your FAQ. You say that it is associated with the format and mount codes in the updater-script, and that they need to be changed...but I still don't understand what to change them to be.

Here's what I have:

format("ext4", "EMMC", "/dev/block/mmcblk0p14");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/data");

Also...since I'm new to this (we all start somewhere, right?)...I'm just wondering if I would need to add code in the script for any new apks and stuff that I put in the ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dsixda:
That's strange, it should work as-is without any modifications required for the Galaxy S3. In fact, I just made a rooted zip recently of the Rogers I747 Jelly Bean firmware.

Can you post the output of the "Show Working Folder Information" menu option?

Also I noticed in your other posts you were having problems getting Cygwin to work, namely gcc. I've never heard of anyone coming across the issue... Make sure you picked the "gcc" package and not "gcc-something-else".

If you are adding new APKs, use the /data/app menu option to add them there, if you want to make them uninstallable. Otherwise they go under /system/app without any modification required, unless you want to do something complicated like themes, of which I am the wrong guy to ask.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mdiaz33685:
Thanks dsixda... for all your hard work...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ascyndaeon:
Hmm...interesting. I wonder why then it didn't work...

Sure.

Android OS version : 4.1.1
Device : d2att
Model : SAMSUNG-SGH-I747
ROM Name : AscydROM
CSC version : I747ATTDLK3
Rooted (Superuser app + su) : YES
Rooted (unsecured boot.img) : YES
BusyBox installed : YES
BusyBox run-parts support : YES
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : YES
Custom boot animation allowed : YES
Nano text editor installed : YES
Bash shell support : YES
/system/framework is deodexed : YES
/system/app is deodexed : YES
ROM will wipe all data : NO

Hmm...I'm pretty sure I had checked that... I'll try it again sometime, I suppose. If it doesn't work, I guess I'll just use Zorin. :/

My laptop must be real "special" if it's having all these issues, haha.

Ah, okay. I figured otherwise it would be copy/paste like that. Thanks.

I don't think I'd want to add the multi-window (flashbarservice.apk) and Note 2 camera to /data/app though. (obviously) It makes me wonder though...can I even do that? Copy the multi-window/note2 camera apks from a ROM like Synergy or GalaxyMod and just use it in my ROM? I wonder then how they could have gotten them installed on 4.1.1 on their ROMs if it couldn't flash...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mdiaz33685:
I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 = is the one I used.. = I only used boot.img and system.img

why does my CSC version = UNKNOWN

I also get status 7 with the original file. I left my rom Odex..

I had to use meanhacker's ATT rom to work...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ascyndaeon:
Um...did you by chance remove the MD5 extension off that when you set up the working folder (as you were supposed to)?

Also, why leave it odexed? Just curious.

---------- Post added at 01:13 AM ---------- Previous post was at 12:45 AM ----------

Okay so I tried to flash it again...and it failed. (This is the second build) Luckily though, this time I actually got a picture of the log text so I can post it here.

assert failed: write_raw_image("/tmp/boot.IMG", "/dev/block/mmoblk0p7")
E: Error in /external_SD/Roms/d2att_signed_031113_220245.zip
(Status 7)
Installation aborted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mdiaz33685:
yes, I removed the md5.... odex.. I like stock...

got the CSC version to work, missed 1 step.. was up late... sorry...

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

dsixda:

it mounts incorrect.. maybe u can fix this... sorry for posting here... it does MTD not EMMC = below are the correct values for the HTC One V

these are the correct values... thanks to cpk5, HTC One V thread...

HTC ONE S --->	HTC ONE V

mmcblk0p33 ---> mmcblk0p25 system

mmcblk0p35 ---> mmcblk0p26 data

mmcblk0p ---> mmcblk0p28 cache

mmcblk0p21 ---> mmcblk0p22 boot.img

these are how it should be....

mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");

mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/data");

mount("ext4", "EMMC", "/dev/block/mmcblk0p28", "/cache");

package_extract_file("boot.img", "/dev/block/mmcblk0p22");
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ascyndaeon:
So um...what do you suppose I should do then?

...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mdiaz33685:
Just figured it out, after some many tries... I kept getting status 7....

remove the 3 lines near the end of the updater script... with the boot.img..

im using .222 kitchen : = remove these 3 lines...

assert(package_extract_file("boot.img", "/tmp/boot.img"),

write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p7"),

delete("/tmp/boot.img"));

replace them with this one..

package_extract_file("boot.img", "/dev/block/mmcblk0p7");