yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Themes and Apps] mankind_18:
Hi raubkatze.. Now after carefully read your post about how to get 100% transparent status bar, finally I've done it! Thank you very much! :victory:

But just a little question here.. I've installed

- N2_15T_BS_mod --> 15 toggles mod grey

- center green clock

- 100% transparent status bar

- green close button

- Stock Brightness Slider and Checkbox

- Stock Green battery

- Green Signal Meters and status icons, and

- Toggle Buttons Green transparent Icons for using with STOCK TOGGLES MODs..

Everything was perfect, except for the last one.. My 15 toggle buttons still grey here.. Any clue about it? :confused:

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

nah, I installed 15 toggles green icon set and everything is perfect.. thanks again! :victory:
[Galaxy Note II Themes and Apps] ravni:
Hi

Is it compatible with arhd rom ? It should because cooker says it's almost stock rom. I'll try later and report back.

And for info, i use 240 dpi too, and i can't modify multi windows app list unless the bar is on the bottom.

I can't if the bar is on right or left.
[Galaxy Note II Themes and Apps] raubkatze:
Nice to hear that you finally got it :)
[Galaxy Note II Themes and Apps] raubkatze:
I think it will work with ARHD. What about multi-window, it is not a bug. It will work properly only with 320 dpi.
[Galaxy Note II Themes and Apps] Blair1076:
Reserved 4
[Galaxy Note II Themes and Apps] raubkatze:
Hmm... What would you like to ask me mate? :)
[Galaxy Note II Themes and Apps] raubkatze:
Btw I quite forgot to ask... what colour?
[Galaxy Note II Themes and Apps] Guitarfreak26:
Is there any chance of adding Facebook messenger?

Sorry for another request... Last one I promise lol
[Galaxy Note II Themes and Apps] raubkatze:
I think yes but a bit later.
[Galaxy Note II Themes and Apps] sunny2303:
Thanks buddy.. really liked the transperent multi window.. also special thanks for bringing Handelgothic font to my notice. Its making my Note II look really cool now :)
[Galaxy Note II Themes and Apps] turilo:
Ah I'd say blue would look good :D
[Galaxy Note II Themes and Apps] raubkatze:
Okey :) A lot of threads, a lot of answers... :D
[Galaxy Note II Themes and Apps] slonn:
Has the mod for removing the status bar clock been put up?

Sendt fra Tapatalk
[Galaxy Note II Themes and Apps] raubkatze:
It will mate when it's ready... I'm too busy now with another mod :)
[Galaxy Note II Themes and Apps] sha3r_al7ob:
dear,

the s pen shortcuts & headset shortcuts not shown..
[Galaxy Note II Themes and Apps] austin_dreq:
I'm not sure if the RED mod set has issue or Omega v4 but "airplane mode" is not showing in toggles even set correctly....

Is it possible to have RED time at "lock screen" also?

Is it possible to request for "100% transparent toggles" instead of solid black background? If I have red drop down mod, I should not have toggle background of black only.
[LG Nitro HD] Hutch89:
So I've been waiting for a while now to see of anyone is developing any new roms, custom kernels (oc/uv capable), tweaks or mods, etc. based on the official att ics/v20c with "optimus ui." From what I understand all of these things are possible now since the source code was released. The stock Rom is smooth, stable, blazing fast, and the optimus ui is awesome as well. I believe with the ability to overclock this Rom or a Rom based on it would make it the best thing out for our nitros, pushing quadrant scores over 4000 (currently maxes around 3700 in quadrant). Also gpu overclocking would be sick. So, this being said, is anyone working on any of this? Is any of it even possible? I would love to do it personally if someone could answer these questions and maybe point me in the right direction of where to start as I've never built my own Rom or kernel. Any input would be greatly appreciated. Thanks again.
[LG Nitro HD] BigSexySCJCD:
Yea I second this!!! Would like to see some love on this subject.
[LG Nitro HD] tuilalnvinh:
U could try official miui port for P930 of navik, it's based on LU6200 fw, which is almost the same with our nitro. Mine has quadrant about 3500-3700 :)
[LG Nitro HD] Hutch89:
Sooo your saying the mui Rom is based off of LG' s official Rom? Does it use optimus ui? If so I would assume that means custom roms are possible...what about the kernel?
[LG Nitro HD] sdotagain:
I agree. The stock V20c ROM is nice. I would like to see tweaked ROMS based off of it as well.
[LG Nitro HD] Hutch89:
I was really curious if HONo had anything in the works but I haven't seen him in a while...
[LG Nitro HD] Hutch89:
Are you using jellybean or Ics version? Does lte work? Also is Navik updating often? Thanks
[LG Nitro HD] tuilalnvinh:
It's ICS version here http://xdaforums.com/showthread.php?t=1898270 and lte not work, just 3G. Navik will update it as soon as miui release new update for LU6200. Current miui based on official ics for LU6200 (v163 kdz).
[LG Nitro HD] navik:
Now MIUI base on offical ics of LU6200(V166KDZ）.
[LG Nitro HD] Victor B:
+1. I have been back on stock for a while an am loving it. If there were some stable roms based of v20c it'd be amazing.
[LG Nitro HD] Billy Madison:
I suggest you to try http://xdaforums.com/showthread.php?p=33166336 it makes 7100+ in Antutu, more than tegra2, exynos 4212 or omap4430 based smartphones, it's FAST
[Samsung Infuse 4G] pkm6:
I have searched around, And i keep getting linked to sites with the roms removed.

Can anyone link me to somewhere where i can download the Odin and stock roms for;

Samsung Galaxy S 2 LTE (SGH-I727R) (UXKJ7) and

Samsung Galaxy S Infuse 4G (SGH - I997R) (UXKG3)
[Samsung Infuse 4G] Pony Express:
I997r: http://xdaforums.com/showthread.php?t=1197248
[Samsung Infuse 4G] pkm6:
thanks, still cant get it to boo past samsung logo just hangs t think i need pit file allso infuse 4g sgh-i997r.
[HTC EVO 3D] EnesGTR:
Yes @all

I flashed today a New Rom - called SAD: Sensational or something like this...

After the installation a installed some apps that I backed up via titanium... But now my phone says: insufficient storage available!

But on the phone is mor than 300mb in ram, and in the other storages are even more mb free...

A user here said me, I should delete the app2sd script... So I removed it...

Then I could install 2 apps and now my phone says again insurance storage available... What I have to do?!?

Any ideas?! I format the data via 4ext, but this doesn't help...

Sry for my English, but in the last 2 weeeks I installed over 6 roms and no one was perfect for me... So I get crazy...

Please help anybody!
[HTC EVO 3D] flashallthetime:
There is a patch also on the op that should delete your problem or you could also manually delete some apk as that worked for me , unfortunately that was a issue and why I did not use that rom for along period of time

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
[HTC EVO 3D] 0rfeo:
You should format your sd card on a pc and then insert it back
[HTC EVO 3D] flashallthetime:
It wont help, it is an issue with this rom, when flashed it over inflates the size of certain files, not an sdcard problem but a rom issue

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)

---------- Post added at 07:59 PM ---------- Previous post was at 07:56 PM ----------

Just use viper3d.

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
[HTC EVO 3D] EnesGTR:
Thanks for the answers!

Formating the sd card brings no results, tried many times...

Wich patch do you mean?! Any link?! I don't wannt to flash 20 roms per.day... After a while this sucks... How is the viper 3d Rom?! Daily usable?!
[HTC EVO 3D] EnesGTR:
http://beta.androidfilehost.com/?a=show&w=files&flid=626

Is this the gsm Rom?!

If no, where can I find it?!
[HTC EVO 3D] flashallthetime:
I will send you the link as all those r roms have issues, installed both and bugs are with camera fc's

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)

---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------

The r 73 rom is good, I ran that one, r143 and 158 don't touch

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)

---------- Post added at 08:48 PM ---------- Previous post was at 08:47 PM ----------

Or this is the actual rom 9-12 multi.http://www.androidfilehost.com/main/EVO_3D_Developers/Virus/Team_Venom/Viper3D/Nightly/

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
[HTC EVO 3D] doom666:
yep this rom is really awesome, i´m using it too (r73), with antrax kernel! Runs like hell, very smooth and very battery saving with 2G!

Using Wi-Fi at home!

can use the phone for 2,5days with googlesync on and weather sync 3hrs!

OC at 1,5GHz and uv -75mv all Voltages!
[HTC EVO 3D] EnesGTR:
So, this is also the r73 Rom, right?

"Viper3D_1.0.0-MULIT-9_12.zip"

Allright, I try!
[HTC EVO 3D] EnesGTR:
I found the r73... But I think its the CDMA version, or?!

http://beta.androidfilehost.com/?fid=9390113915771289764
[HTC EVO 3D] flashallthetime:
No both gsm and cdma

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
[HTC EVO 3D] Jsparta26:
He could try a factory data wipe. Had that problem a few times and factory wipe worked for me.
[HTC EVO 3D] EnesGTR:
Already tried a factory reset, doesn't help...

I try these viper Rom... If you say that is for booth, I hope... Don't want to have a brick...
[HTC EVO 3D] flashallthetime:
It wont brick your phone,open the zip and you will see shooteru

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
[HTC EVO 3D] sitlet:
I've had this problem with the last 2 CDMA ICS roms I've tried. Phone shows over 100mb free, but no new apps will install, and current apps will not update. Moving apps to the SD card shows more free space, but again still gets the error.
[HTC EVO 3D] flashallthetime:
It is a rom issue with this particular rom

( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
[HTC EVO 3D] coal686:
Between 100 and 150 mb free, the OS won't let you install or update apps. I think it's reserving space for caches and such.
[Android Q&A, Help & Troubleshooting] DivinityCycle:
I'm working on my first ROM that is based on the "stock" Samsung firmware. I am used to messing around with AOSP and CM ROMs where there's a nice flashable ZIP with a boot.img in it. Working from the "stock" Samsung image has been less clean.

My device is a Samsung SGH-T869 (the T-Mobile version of the Galaxy Tab 7.0 Plus).

I began with the file T869TMBLG7_T869UVLG7_T869UVLG7_HOME.tar.md5, which is the newest firmware available for this device.

I am able to extract the image using 7-zip, which gives me the error "There is no correct record at the end of archive", but otherwise appears to extract perfectly.

Extracted files include:

-boot.bin

-cache.img

-factoryfs.img

-hidden.img

-modem.bin

-param.lfs

-recovery.img

-Sbl.bin

-zImage

These files are enough to give Android Kitchen something to start with, but AK is complaining about the lack of a boot.img, plus I want to do some ramdisk tweaking. I have been researching this for hours, and I get the impression that what I need is in there, just in a proprietary format. I have installed KernelKitchen, which I guess I can use to build boot.img from zImage and a ramdisk, I'm just not sure where to go from here.

I also tried dumping ADB (dd if=/dev/block/mmcblk0pX of=/sdcard/boot.img, tried all partitions one by one).

I also looked at a backup made via CWM 6 of the 'stock' untouched ROM running on my tab. My backup contains:

-boot.img

-cache.ext4.dup

-data.ext4.dup

-nandroid.md5

-recovery.img

-system.ext4.dup

So far, no success. The various imgs I have pulled are all treated as invalid by Android Kitchen and also split_bootimg.pl by William Enck. When running that nice Perl script I get the error "Android Magic not found".

My general first goal is a cleaned up stock ROM which has been deodexed, zipaligned, with insecure boot enabled, and of course, root.I would like to also do a sweet custom boot image and boot animation, but I believe its best to start with a solid foundation before jumping into the other stuff. Any suggestions, XDA gang? Somewhere in that mix did I get the actual boot.img but Samsung uses a weird header? Or something else?
[Android Q&A, Help & Troubleshooting] xSkArx:
Rename file.tar.md5 to file.tar and unzip

Find an updater-script of custom based stock rom and you get "name' of kernel partition
[Android Q&A, Help & Troubleshooting] DivinityCycle:
Your first instruction (to "rename and unzip") makes no difference at all.

The second suggestion seems like it may be useful.

From the CM9 flash script I found that /dev/block/mmcblk0p5 is the boot partition.

I am not sure what's wrong with the boot.img I am pulling.

Here's my command session:

adb shell
su
dd if=dev/block/mmcblk0p5 of=/mnt/sdcard/boot.img
exit
adb pull /mnt/sdcard/boot.img

I attached the resulting file. I looked at it a bit in a hex editor but I'm not sure what I'm lookin for...
[Android Q&A, Help & Troubleshooting] k02a:
It seems that you managed to extract a kernel image (zImage). What you are looking for is an image starting with the signature "ANDROID!".

What do you see if you enter the following command?

$ cat /proc/mtd

It should read something similar to:

dev: size erasesize name
mtd0: xxxxxxxx xxxxxxxx "system"
...
[Android Q&A, Help & Troubleshooting] xSkArx:
My first instruction is to get boot.bin without error when unzip it.

With the boot.img that you attached try this http://xdaforums.com/showthread.php?t=1849666
[Android Q&A, Help & Troubleshooting] thewadegeek:
You are probably going to have to trim some extra data off the front of your boot.img so that the tool finds the needed Hex address. If you haven't already I'd pull the applicable scripts out of dsixda's kitchen and see how he handles it.
[Android Q&A, Help & Troubleshooting] DivinityCycle:
I'm pretty sure you're after the partitions. However, there's no /proc/mtd on the SGH-T869 running stock.

shell@android:/proc # cat partitions
cat partitions
major minor #blocks name

179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 1280 mmcblk0p2
179 3 1280 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 204800 mmcblk0p7
259 0 16384 mmcblk0p8
259 1 786432 mmcblk0p9
259 2 13791232 mmcblk0p10
259 3 524288 mmcblk0p11
259 4 8192 mmcblk0p12
179 8 30318592 mmcblk1
179 9 30317568 mmcblk1p1

When looking at /proc/mounts, I see that partitions 1, 4, 7, 9, and 10 are all mounted. I'm also relatively certain that mmcblk1 is the microSD card slot, based on its size (I've got a 32GB card installed at the moment).

So, ruling those out, we're left with:

major minor #blocks name
179 2 1280 mmcblk0p2
179 3 1280 mmcblk0p3
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
259 0 16384 mmcblk0p8
259 3 524288 mmcblk0p11
259 4 8192 mmcblk0p12

I have already extracted the first 8 partitions and tried running each through Android Kitchen's boot.img unpack tool without success. The script fails to locate the ANDROID header within any of the files. I'm guessing Samsung uses some sort of custom header, because if it works perfectly fine, why not mess with it?

I've searched through a few of the files with XVI32 for "ANDROID" but didn't get any hits.

As posted earlier, other ROMs flash boot.img to mmcblk0p5 so I'm pretty sure that's the right space.

Any hints on an application I can use to analyze the dump and locate the offsets where the header and ramdisk are inside it?
[Android Q&A, Help & Troubleshooting] DivinityCycle:
Update. In my research I have come across this article:

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

It wasn't directly helpful but it did give me a key idea: "Find the Magic Number for a GZ archive and you'll find the ramdisk inside the raw image"

As per http://www.garykessler.net/library/file_sigs.html, the "Magic Number" for a GZ archive is 1F 8B 08. The first article only mentions "look for a bunch of zeros and then 1F 8B." That never occurs in my dumped file, and the number 1F 8B occurs 65 times. However, "1F 8B 08" only occurs once in the entire file, indicating the spot where the header and kernel end and the ramdisk begins.

I deleted everything before 1F 8B 08 and saved the result as ramdisk.gz.

Then, I threw the resulting file onto one of my Linux boxes and used the following commands to extract:

mkdir ramdisk
cd ramdisk
gunzip < ../ramdisk.gz | cpio -i --make-directories
ls
(results of ls command here:)
data init.goldfish.rc lpm.rc ueventd.goldfish.rc
default.prop init.rc proc ueventd.rc
dev init.smdk4210.rc sbin ueventd.smdk4210.rc
fota.rc init.smdk4210.usb.rc sys vendor
init lib system

I did this stuff in a command terminal connected over Putty, and I got a ton of crazy output during extraction, mostly the line "cpio: Malformed number" over and over.

My next planned task is to take 3 boot.img dumps from my tablet and them compare MD5s on all 3 dumps, to ensure I got a "good" copy.

I imagine this is largely unnecessary, but I've learned from working on other embedded devices that you can't be too careful about raw reads / writes.

I'm pretty sure now that I have extracted the ramdisk I am OK. The factory firmware has zImage as a discrete file, so I'm pretty sure I can use either Android Kitchen or Kernel Kitchen to repack the stuff into a "normal" boot.img.

I'll post my results here, since there may be like one other person interested in doing ROMs for the T869 :P
[Android Q&A, Help & Troubleshooting] DivinityCycle:
Just a little update, the md5sums on ALL of my various dumps matched.

By that I mean CWM's backup and all the various dumps I did via ADB (using the dd command) all match.

md5sum for this firmware's boot.img appears to be 1e4367954524901c7dfff14b02023163
[Android Q&A, Help & Troubleshooting] k02a:
Interesting and a great research!

I look forward to see more of your progressive work.

---------- Post added 11th October 2012 at 12:00 AM ---------- Previous post was 10th October 2012 at 11:39 PM ----------

According to RFC1952, the gzip header only contains two bytes (ID1, ID2), while the third byte (CM) normally seems to be set to 0x08 (deflate) - so you did the right thing to include the third byte.

http://tools.ietf.org/html/rfc1952
[Android Q&A, Help & Troubleshooting] DivinityCycle:
After much searching, it looks Samsung's boot.imgs sometimes simply have no header at all, so like the first chunk is the kernel, and the second is the ramdisk. I'm gonna test out unpacking ramdisk, making the changes I need, repacking it, and then combining the two chunks back together for flashing.

Will post results :)
[Android Q&A, Help & Troubleshooting] k02a:
I took a new look at your boot.img today.

Besides the gzip header at address 0000:4634 (which you found), I also noticed that there are 256 (0x100) bytes at 007f:fc00.

Any clue about this?
[Android Q&A, Help & Troubleshooting] merwin:
Feel free to use my updater-script in the scorched kernel thread. The updater works for ics boot images. just remove the parts about copying lib files and setting permissions ... and remove the lib files from the zip. they are specific to the kernel. a stock kernel will break if those lib files are copied to /system/lib/modules.

Oh, and you can get the boot image easily in CWM by doing a backup of the stock rom and grabbing it from the clockworkmod folder on the sdcard.
[Android Q&A, Help & Troubleshooting] DivinityCycle:
As posted earlier in this thread, I pulled a boot.img from a CWM backup, but that was back before I knew how to do anything useful with it yet.

The md5sum of the CWM-generated backup boot.img matches the dumps I did over ADB using the dd command, so they're different ways to get the same end result. I have a pretty good understanding of the syntax used in the CWM flashable ZIPs. My rough plan was to first build a "restore to stock boot.img" flashable zip (so I can fix it if I make my tab unbootable :P), then experiment with building my own boot.img and flashing it using the same methods. The only thing that'll be different about the "flash modded boot.img" and "flash stock boot.img" is the actual boot.img file included in the zip. Didn't get a chance to do it while off work last night, but should be able to knock it out today.
[Android Q&A, Help & Troubleshooting] DivinityCycle:
Your guess is probably better than mine, honestly. I would think that second address is actually within the 'ramdisk' part of things, so that seems pretty odd. I'm a relative noob when it comes to hex stuff, as that's a couple levels down from where I usually operate with computers :p

If I unpack, modify, and repack the ramdisk, any suggestions on the 'best' way to reattach the header/kernel to it?
[Android Q&A, Help & Troubleshooting] DivinityCycle:
Following up on this earlier point, it looks like there are a few more regions within the 8 MB file than I initially saw.

I use XVI32, so the addresses I found are formatting as such.

it seems like the following is the layout of the file contents:

Part 1 - $000000 to $004633 = 17.5 KB header?

Part 2 - $004634 to $4768A6 = 4.44 MB ramdisk (?)

Part 3 - $4768A7 to $7FFBFF = 3.53 MB of zero padding

Part 4 - $7FFC00 to $7FFCFF = 241 bytes footer

Part 5 - $7FFD00 to $7FFFFF = 768 bytes of zero padding

My initial attempt to unpack / repack the image of course made the device unbootable. My "restore" flashable zip worked as expected, so I'm now able to mess around with this stuff with relative ease.

I'm still getting a bunch of weird crap in my terminal when extracting the ramdisk. The command I am running is gunzip -c ../ramdisk.gz | cpio -i run within the directory where I want the files to extract. Both under Cygwin in Windows and under Ubuntu Server, I get tons of "cpio: Malformed number" followed by garbage. Under Ubuntu Server, despite this weird output, the files actually DO appear to extract and I get 1.65 MB of unpacked files, all in the expected format and directory structure.

Under Cygwin it didn't extract at all.

I'll continue to mess around but for your hacky fun, I have attached the parts all split up and then packed into a single ZIP.

Post if you have any ideas. I'm gonna try and repack the ramdisk and then re-assemble the whole thing. The repacked ramdisk will be smaller, but I'll just fill in the empty spot with zero padding so that the footer still ends up at the same address. We'll see if that works :P
[Android Q&A, Help & Troubleshooting] k02a:
Quite interesting result so far...

I wonder if there are some documentation on the data structure of the footer information floating around in public, and secondly if the offset is static.

Speaking of padding zeros. Maybe the number of trailing zeroes depends on the payload size and the page size (evenly divided by given page size), which is the case for e. g. boot.img?
[Android Q&A, Help & Troubleshooting] DivinityCycle:
It will take some experimentation to see how picky the boot loader is. I have been sidetracked today by actual work (imagine that!) and also I have been working on exhaustively cataloging and documenting the contents of the stock ROM, particularly /system/app. Cutting the Samsung bloat has been challenging only in that there's so much stuff to remove :P

I just had a brainstorm: I'm going to examine the boot.img from the CM9 and CM10 ROMs for the T869. After all, both of them are accepted by the bootloader, so those two and the "stock" boot.img must share some common properties, which one would think would be the "key" stuff to make the boot.img work.