yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] tdm:
Still working on the initramfs but it's getting close. I'm having fits trying to read the initramfs directly from the kernel. It will probably involve some low level code, possibly assembly, to pass the offset+size from the decompressor to the main kernel. So I'm using the teamhacksung method for now so that I can make progress on the other stuff.

Also decided to integrate the buyer code into the kernel. It's going to work like this:

There will be /proc/buyer_code file exposed by the kernel. The init.rc will copy /efs/buyer_code.dat to it so that the touchscreen driver and sound driver can access it. This will simplify the touchscreen driver loading, which is currently a simple script that passes a module parameter. It will also eliminate the code in the sound code that reads it from /efs. I'll probably do the same with the bt mac addr, because reading files from the kernel is strongly frowned upon.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Had an epiphany on the way home today. I think I can steal some bytes from the end of the cmdline block to pass the initramfs addr+size from the decompresser to the init code. I'll investigate this on Monday.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Still making progress.

I have the efs stuff incorporated into the kernel so that the boot scripts can just do this:

copy /efs/buyer_code.dat /sys/firmware/efs/buyer_code

Then the touchscreen driver and whatever else can use the data.

I put my device back to stock (that boot sound drives me nuts!!) and tested an upgrade. The MTD convert script seems to be working, which is nice.

I think the last piece is getting my boot and recovery initramfs in order. Switching over to the teamhacksung stuff means that the boot and recovery initramfs is taken from the main build like it was meant to be. But that also means that I need to ensure my files in the main build are functional, where I didn't before.

I was able to see the nifty new blue color scheme in CWM 5.x a couple times, so I know it's getting close. :)
[Samsung Galaxy Player 4.0, 5.0] klin1344:
Keep up the awesome work! Nice to see that you are making lots of progress. :)

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] feika12:
Great work！ THX！
[Samsung Galaxy Player 4.0, 5.0] tdm:
Well, I thought that I had an error-free kernel partition, so I have been avoiding running bml_over_mtd in the boot process to load the initramfs. But I spent several hours trying to figure out why my recovery would not boot most of the time, but occasionally it would. Turns out my kernel partition has mysteriously developed a bad block that is high enough to only be needed sometimes.

So the bad part is that I wasted a bunch of time trying to figure out my problem. The good part is that bml_over_mtd is now functional.

I swear this device hates me. It's giving me problems at every turn. But I guess that's expected... I hate how Samsung made it do all this weird and proprietary stuff. :D
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
At least they are one of the most unbrickable devices. :D
[Samsung Galaxy Player 4.0, 5.0] ChaosChris:
How ca i mount the external sd?
[Samsung Galaxy Player 4.0, 5.0] tdm:
Almost there but I'm stuck on one stupid little detail. I need to figure out how to set and reset the bootmode to select recovery or normal boot. I suspect this is related to either /efs or /mnt/.lfs but I'm not sure yet.

I'm able to boot into recovery, do the install, then boot my MTD based CM7 system by forcing the boot script to ignore recovery mode. So I know both the recovery and normal initramfs are good.

Oh, and I'll probably not be able to work on this tomorrow, but I'll be back Thu or Fri.
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Thank you for sticking with it, even though Samsung is a pain in the rear!

PS:this post was purely for moral support, and may be deleted if the mods see fit. :P

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] tdm:
Still trying to figure out the reboot stuff. I may have to resort to an ugly hack but I'm pretty sure I'll have it done early next week.
[Samsung Galaxy Player 4.0, 5.0] xxxtyp:
Need help?

I noticed that there is not much development here for the 4.0 player and i would love CM7 on mine so if any one needs a test player let me know and i will flash anything you need. i mainly use my player as music only(about 10-12 hours a day) on weekends i sometimes use Google Voice to text on it and a lot of internet access via dolphin browser. if you can get me those features i will be glad to test it out! =D

i have lots of experience flashing roms since the windows 5.0-6.5 days till my current Sammy galaxy epic that started on 2.1 and ended up running CM9 Beta 2. i have gone through about 7 different android phones(Hero, Evo, Samsung Moment, Evo 3d, Samsung captivate, my Fave-Motorola RAZR, Motorola Droid 2) and none of them have run there manufacture software for more than an hour(what it takes me to get home from the sprint store lol) I don't know much programming though but atleast im not a TOTAL newb. =/
[Samsung Galaxy Player 4.0, 5.0] tdm:
Sorry for the delay .. there was some big developments for my phone and I spent a few days playing with that instead. I'm back on the recovery/bootmode issue now and I hope to find out something this week.
[Samsung Galaxy Player 4.0, 5.0] klin1344:
I remember you saying that you got aosp gingerbread working. If I compiled aosp with your sources, would it have the same errors as your current cm7? Or are those issues cm7 related only?

Thanks.

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] tdm:
Okay I finally figured out the bootmode/recovery issue well enough to get it functional.

I figured the magic was in either the efs or param partition, so I took the contents of the files on these filesystems with bootmode set to recovery and with bootmode set to normal and diffed them. Turns out the value that controls bootmode is in the "param" partition. It is a byte in the file /mnt/.lfs/param.blk, offset 0x54. Values correspond to those in the kernel file arch/arm/mach-s5pv210/include/mach/param.h:

/* REBOOT_MODE */
#define REBOOT_MODE_NONE 0
#define REBOOT_MODE_DOWNLOAD 1
#define REBOOT_MODE_CHARGING 3
#define REBOOT_MODE_RECOVERY 4
#define REBOOT_MODE_ARM11_FOTA 5
#define REBOOT_MODE_ARM9_FOTA 6

If the value is 0x00, the device does normal boot. If the value is 0x04, the boot loader inserts bootmode=2 on the kernel commandline and the device does recovery boot.

The problem is, /mnt/.lfs/param.blk is on a j4fs filesystem mounted on top of STL and BML, so we don't have any way to access it. I might eventually get the open source j4fs driver going but that probably won't do much good without BML and STL drivers. That's way too much reverse engineering and way too many layers of crap.

So what to do?

Well, I noticed a signature at the start of param.blk "$frr". So I wrote a little utility to scan through the raw param device and when it finds this signature, it sets the bootmode value directly. There are 6 instances of this signature on my device, and I don't know which one actually controls the boot, so I have the utility set all of them that it finds.

And what do you know .. it works! :D

Yeah it's a horrible, ugly hack. But it seems to work for now. I'll try to ping teamhacksung to see if they have any more ideas on the issue. Or maybe they haven't even gotten this far, who knows...
[Samsung Galaxy Player 4.0, 5.0] tdm:
Okay here is another test image. Please let me know how it works. (md5=0db7e94629578fbc9eb95a9fb12340f0)

Instructions:

Start with a CWM based recovery like Steve's.

When you install the ROM, the first thing it will do is flash the kernel and backup your data (efs, dbdata, data, cache). Then it will reboot.

Note I don't have it set to automatically reboot into recovery yet, so you'll have to hold VOL+UP to get back into recovery in the new kernel. Note the strange looking initlogo -- I haven't figured out why the framebuffer format isn't correct. Just ignore it for now. :p

At this point, the system doesn't know whether the device is US or INTL because efs has not been restored. So the home key won't work on US devices. Use the menu key to select.

Now install the ROM again. This time it will restore the data directly on MTD/yaffs2 and do the actual install. When it's done, reboot. You should have a functional system and the home key should work on US devices again, since the efs data is now available again.

Finally, wipe data and cache.

Known issues (other than the above):

* Reboot into recovery does not work yet

* Setup wizard doesn't run properly, just skip it

* Bluetooth won't scan properly

* External sdcard isn't mounted properly

* Deep sleep is still disabled
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Downloading right now.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Got a quick reply from teamhacksung that says

I'll look into this but I don't think it is applicable to our devices.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
There's something weird:confused: I'm getting random reboots. I've tried to flash 3 times.

Here's my boot.txt:

Fri May 11 23:54:54 GMT 2012
+ exec
+ cd /
+ mount -t proc proc /proc
+ mount -t sysfs sysfs /sys
+ rm /init
+ bml_over_mtd dump kernel 72 reservoir 2004 /stage1/boot.bin
Failed to access reservoir partition.
dump_bml_partition: Error opening reservoir part for reading.
mtd_scan_partitions: found efs
mtd_scan_partitions: found param
mtd_scan_partitions: found kernel
mtd_scan_partitions: found recovery
mtd_scan_partitions: found factoryfs
mtd_scan_partitions: found dbdatafs
mtd_scan_partitions: found cache
mtd_scan_partitions: found modem
mtd_scan_partitions: found reservoir
No bad blocks.
Generating empty block mapping table for error-free partition.
bml_over_mtd_read_partition: failed to open /dev/mtd/mtd8: No such file or directory
+ grep -m 1 -A 1 BOOT_IMAGE_OFFSETS /stage1/boot.bin
+ tail -n 1
+ eval
+ load_offset=
+ load_len=
+ mount -t yaffs2 /dev/block/mtdblock0 /efs
+ test -e /efs/buyer_code.dat
+ test -e /efs/imei/bt.txt
+ umount /efs
+ rm -rf /efs
+ insmod /lib/modules/qt602240.ko
+ grep -q bootmode=2 /proc/cmdline
+ load_offset=
+ load_len=
+ echo 0
+ rm -rf /cache
+ dd bs=512 if=/stage1/boot.bin skip= count=
+ zcat
+ cpio -i
dd: invalid number ''
zcat: short read
+ grep -q 1 /sys/class/power_supply/battery/charging_mode_booting
+ umount /sys
+ umount /proc
+ date
Fri May 11 23:54:55 GMT 2012
+ mount -t vfat /dev/block/mmcblk0p1 /emmc
+ cp /boot.txt /emmc/boot.txt
[Samsung Galaxy Player 4.0, 5.0] tdm:
Try reflashing?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Its not working either.:confused:
[Samsung Galaxy Player 4.0, 5.0] tdm:
Strange. I haven't really changed the kernel except to support mtd.
[Samsung Galaxy Player 4.0, 5.0] tdm:
I'll look at that boot.txt later, thanks.
[Samsung Galaxy Player 4.0, 5.0] tdm:
In your boot.txt note the load_offset is blank. Either it's a bad flash or its using the wrong device. Try extracting boot.img from the ROM and flashing it with heimdall.
[Samsung Galaxy Player 4.0, 5.0] tdm:
Oh wait... That error about the reservoir partition is probably the issue. Do you have A custom pit? I'll need to remove the hard coded values.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Not really. I just have a pit when I was in stock I can send it to you if you want it.
[Desire HD Q&A, Help & Troubleshooting] jovanov:
MOD EDIT : Linking to, discussing, asking for or promoting warez is strictly against XDA Rules.
[Desire HD Q&A, Help & Troubleshooting] LowGasPrices:
MOD EDIT : Linking to, discussing or promoting warez is strictly against XDA Rules.
[Desire HD Q&A, Help & Troubleshooting] SoldaCz:
MOD EDIT : Linking to, discussing or promoting warez is strictly against XDA Rules.
[Desire HD Q&A, Help & Troubleshooting] major fecker:
Gun bros is great (overhead shoot em up), Chaos (Helicopter Gunship battles), Skies of Glory (WWII fighters), Dead Space (very creepy 3rd person shooter) Modern Combat 1,2 and 3 (1st person shooters COD Modern Warfare style)
[Desire HD Q&A, Help & Troubleshooting] starkilling:
I play Minesweeper Classic and Sudoku Brainiak free, sometimes Fruit Ninja.
[Desire HD Q&A, Help & Troubleshooting] marko958:
Wordmatch (free), Tetris (free), Angry Birds (free), Can Knockdown (buy), Flick Golf (buy),
[Desire HD Q&A, Help & Troubleshooting] badman1150:
MOD EDIT : Linking to, discussing or promoting warez is strictly against XDA Rules.
[Desire HD Q&A, Help & Troubleshooting] Andy:
Asking for, linking to & discussing warez (copied / pirated / cracked) apps is strictly against XDA rules, don't do it.

Thread Closed.
[Galaxy S II Q&A, Help & Troubleshooting] ozmund:
Hi XDA,

I've been trying to root this SGS2 and get Cyanogen or Litening on it, whichever. Anyway, I've just run into problem after problem, and I can't seem to figure it out or get around it.

I can confirm that the phone is rooted, Odin 1.8.5 and F-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4.zip were used.

CWM 4.0.1.5 is installed. I can get to it by Volume up/Home/Power, but it's broken, it doesn't want to do anything, and when selecting restart or power off, it just sits there with the CWM logo on the screen. I noticed that CWM 1.80 is in the app drawer as well, could this be causing the problems?

Choosing 'Install ROM from SD card' it just reboots into the blue e3 system recovery.

Baseband: I9100TDVKF2

Kernel: 2.6.35.7-i9100ZSKF4

No idea what to do now, any guidance appreciated.

Cheers
[Galaxy S II Q&A, Help & Troubleshooting] Deleted member 4038153:
Sounds like you have an I9000, not I9100.
[Galaxy S II Q&A, Help & Troubleshooting] ozmund:
It's definitely a, I9100, I just realised my typo in the baseband :S
[Galaxy S II Q&A, Help & Troubleshooting] screamworks:
Depending on a few factors, mainly, if or if not you have a backup of what's on your device, I'd say start again. Open up ODIN, flash a stock ROM, then CF-Root, and from there use the recovery menu to wipe/factory reset data, wipe cache & Dalvik cache, and then flash a new ROM - I recommend the latest CyanogenMod 9 nightly build.

screamworks.
[T-Mobile Samsung Galaxy S II SGH-T989] prech:
I would like try out the Sky-ICS ROM for the i727 Skyrocket:

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

Has anyone successfully flashed this ROM on their T989? I flashed it's RC 7 version then used the conversion zip from here:

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

Everything seemed fine until using Market forces a reboot, so I'm curious if any T989 owners have played around with this ROM?
[T-Mobile Samsung Galaxy S II SGH-T989] Jester6:
Im running Sky ICS speed 7.4 with darksides kernel, runs beautifully. Little bit of playing around to get it running right but its been fine since (flashed this morning). I flashed the RC 7 let it boot and set everything up with the SR kernel first and let it sit for 5 mins, then flashed the 7.4 update, let it boot and sit for about 5 minutes, reflashed the darkside kernel did a few more reboots and it seems perfect. I didn't flash the conversion zip at all. No wifi/gps issues, market works great.

Good Luck
[T-Mobile Samsung Galaxy S II SGH-T989] azn_indeed:
running skyics for a while now, no problems so far

did not flash the conversion zip, just any t989 kernel
[T-Mobile Samsung Galaxy S II SGH-T989] prech:
Thanks both for responding. I'm still having difficulty with Market

I did a Darkside Superwipe, then flashed RC7. Market works fine at this point.

I then tried faux's T989 kernel and Market forces reboot.

Re-wiped and flashed RC7, this time with the Synergy T989 kernel, and same thing with Market.

I haven't gotten to 7.4 yet, but am thinking I'll just be content with our T989 ROMs for now...
[T-Mobile Samsung Galaxy S II SGH-T989] allenjthomsen:
You need to wipe factory data cache and format system then flash ROM then flash kernel after first boot should fix force close of market of not pm me cuz I have the srgs2 conversion file
[T-Mobile Samsung Galaxy S II SGH-T989] JasjarMan:
Battery life is terrible but rom is nice.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] fivefinga:
I was on the xda app and my phone just turned off and now it won't turn back on.

It won't go into download mode or recovery.

Any help would be greatly appreciated..

I'm stock 2.3.5 rooted
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
did u try a battery pull? Take it out and let it sit for a few minutes, then put it back and hold power button for at least 20 secs
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] fivefinga:
I did a few battery pulls just hoping it would work. Is there anything else I could try?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kr3w1337:
Does anything happen when you leave the charger in? Also, holding the power button for a while doesn't do anything?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] fivefinga:
If i plug it into my computer it says qhsusb_dload. And the power button doesn't do anything
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] silver03wrx:
Its dead bricked. U need a new phone. Be honest did u try to flash a galaxy s2 i777 rom?

That or checked repartition in odin.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] fivefinga:
Nope just on xda and it turned off

Sent from my YP-G70
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] DoctorQMM:
if that's the case.... then this is concerning..... hard bricked ln its own.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] fivefinga:
Is there any wy to get any of the data on the internal sd card?

Sent from my YP-G70
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] fivefinga:
I was on romracers 0.3 kernel if that matters

Sent from my YP-G70
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] silver03wrx:
Mabye overclocked to high

Or ur phone just didnt like oc or uv and quit.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] DoctorQMM:
I don't think any of romracer's "stockish" kernels have uv/oc patching.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] silver03wrx:
In that case. That sucks. Use your warranty. Your phone killed itself. What a shame
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] fhp3:
This happened to me as well. I was browsing the web and the phone just died and wouldn't show any signs of life. Tried everything including buying the Samsung Jtag dongle. I got it replaced but now am really concerned about rooting it and loading a new rom. I was on Sky ICS 6.35.
[Acer Iconia A500] jaizero:
I've been reading and watching YouTube videos describing building android roms and kernels from source but they are really confusing. Just wondering if one of you experienced developers could do a step by step tutorial on building roms and kernels from source for our beloved A500. A substantial donation would be in your future. :-) I think this would be a great resource for people that want to make their own roms and kernels instead of relying on other peoples releases.

Thanks for reading..
[Acer Iconia A500] erica_renee:
I mentioned this in another thread earlier.I think it would be best for you to start if you have not already.

developer.android.com.

also go to nvidia.c om and follow there development for tegra 2 . it would be one very long step by step tutorial.
[Acer Iconia A500] jliedeka:
I was wondering about that myself. I compiled my share of linux kernels back in the day. I'd like to be able to contribute to making ICS on Iconia better.

Thanks for the references.

Jim
[Acer Iconia A500] querobolo:
can someoone help me too??
[Acer Iconia A500] hatefuel19:
you might be surprised to know that devs WILL help so long as your not asking hey what is a kernel or something goofy like that. I've gotten help through pm's from devs before on theming and things like that. My advice would be to get ad far as you can on your own and when you've hut the wall and absolutely cent get any further, reach out to a dev for guidance
[Samsung Galaxy Fit GT 5670] eslam hassan:
:):):):):)

1. Go to the Kitchen page http://uot.dakra.lt/kitchen/

2. Go to Lockscreen section: :cool::cool::cool::cool:

-frist choose ldpi (240x320) for galaxy fit

-then mark heading you want & adjust it as you like

-not forget to press Generate preview

*I think you must select only one from sliding tab & rotary

3. Go to the file upload section : :confused::confused::confused::confused:

-select type galaxy from flashable zip scripting

-select mdpi (320x480) / ldpi (240x320) from ThemeChooser preview

-select Upload system files for Select your rom from kitchen's list, or upload your own files

-upload :* framework-res.apk from "/system/framework"

* SystemUI.apk from "/system/app"

* twframework-res.apk from "/system/framework"

-others as default

4. Go to the summary section. :All chosen mods must have a green background. If there is a mod in red background it means you didn’t finish it.

Press Submit work to kitchen

5. Remember the UOT file name (your order number) .

6. Go to the Pickup " http://uot.dakra.lt/pickup/ " page and wait for your file to appear (it can take from 5min to 1hr or more:mad::mad::mad::mad::mad: )

7. Download UOT zip into SD card of your phone

8. Reboot into recovery

9. Flash UOT zip

:D:D:D:D
[Samsung Galaxy Fit GT 5670] krish30990:
Not working

I'm tired of the default lock screen in my Gfit. Also i need no launcher apps since it consumes much of ram. I was only able to notice a change in battery indicator and glowing scroll effect. This method for changing the default lock screen is not working in my gfit with rooted stock rom and CWM 4.0.0.5. Is there any other method to do it??? plz help :( :(
[Nexus S Q&A, Help & Troubleshooting] kalitza:
hi every1.

I've been searching but didn't find any info about the topic.

Does someone knows how or just tryed already to overclock the gpu to higher rates? (i would like to get more to play better games).

another question: i'm using the matr1x kernel (17.5) and in the menu i have an option to overclock the gpu but there're options to get it to 1000Mhz? really?

Which are the riscs?

I apreciated any info.

thanks in advance
[Nexus S Q&A, Help & Troubleshooting] simms22:
stock nexus s gpu is at clocked at 200mhz. you CAN NOT overclock it 500% to 1000ghz. thats just silly. thats like overclocking your cpu to 5ghz. the highest ive overclocked my gpu or ran a kernel that already has it overclocked is 250mhz. thats a 25% oc :p
[Nexus S Q&A, Help & Troubleshooting] Harbb:
That's the CPU clock you're looking at. LiveOC can overclock the GPU as a percentage value (ie, 110% is 200 * 110% = 220mhz), but it does the same to the CPU (so 1000mhz turns into 1100mhz). This will generally need adjusting the voltages upward.
[Nexus S Q&A, Help & Troubleshooting] kalitza:
So no need for any app to oc, just increase the LiveOc % ?

ya, that question about overclocking the gpu to higher then 300mhz was really silly, but asked t anyway :P
[Nexus S Q&A, Help & Troubleshooting] Harbb:
GPU Clock is stock at 200mhz, CPU is at 1000mhz. Increase LiveOC % and you'll go up by that percentage. Just remember, as i said, you will most likely need to adjust voltages to prevent instability and reboots. It's best just to set all of this up using NSTools.
[Nexus S Q&A, Help & Troubleshooting] kalitza:
Ok. I've tryed oc to 110% but instable. just need to set voltages to get the right combo.

Thanks!!
[Nexus S Q&A, Help & Troubleshooting] Harbb:
Not all phones can handle such an OC (either because of GPU or CPU, or combination, it all varies). Hopefully you can get a stable setup, the extra GPU OC is a great performance booster.
[Nexus S Q&A, Help & Troubleshooting] zgomot:
And what a performance booster... I never bothered to try the LiveOC... I just OCed the CPU and thought that was the most I can do. But with 110% LiveOC and 1300MHz CPU OC, my phone is now eve faster than before.
[Samsung Galaxy SL i9003] moizsami:
I saw on the x8 forum that a developer has made a mod of the android 4.0 settings work on cm7...i think it would be great if some one from our developers could do that too..

here is the link of the OP in the x8 thread..

http://xdaforums.com/showthread.php?t=1526925
[Samsung Galaxy SL i9003] nitinvaid:
I wil try it on my ics theme
[Samsung Galaxy SL i9003] vishal24387:
wow...best of luck dude :)
[Samsung Galaxy SL i9003] moizsami:
Thanks man...it would be awesome if it works