Database Develop

[ROM][STOCK]SHW-M380W Korean Tab 10.1

As I make progress towards making us an overclocked kernel I will keep m380w users informed in this thread. Wish me luck!
June 16, 2012 Had to post an updated torrent file.
May 01, 2012 New Firmware Released (NOT ICS)
Attached is a torrent file for FD19
Dec. 08, 2011 Development Halted
Here's the latest. The source code that Samsung makes available seems to have issues. I have tried and tried again to reproduce a stock kernel that will boot with the initramfs. However, the defconfig provided does not match the .config extracted from config.gz. There are some big differences between the two. The defconfig supplied with the source code defines the board as p4 yet the .config from the kernel defines it as p4wifi. So naturally I have tried both and I have tried many, many other things. All for not.
I contacted FOSS and the response was to the tune of, "We sent your message to the dev. team. If they respond, we'll respond. Until then, just wait."
With that said, I see no reason to muck about with trying to make an overclocked kernel, when there is no indication that I have valid source code.
Nov. 24, 2011
Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.
SHW-M380W.EK10.7z
Rooting directions and files I have tested and do work with this release can be found here on XDA
Nov. 26, 2011
I made some progress and have extracted the initramfs from the EK10 kernel using koush's AnyKernel. See attachments. One step closer to an overclocked kernel.
Pershoot has graciously offered his time and resources and built a recovery cwm_5.0.2.7_kor for the m380w. Which now displays correctly on this device.
He included the following notes:
UMS is not implemented (so the option will not work).
no radio/extra partitions will be available.
Click to expand...
Click to collapse

koe1974 said:
As there are only a few of us in here and nobody in Korea seems to be developing this model, I took it upon myself to retain this ROM from my most recent bout with Kies.
Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.
HOME_SHW-M380W.EK10.1207_CL583812_REV00_user_ship.tar.md5
Rooting directions and files I have tested and do work with this release can be found here on XDA
I hope to offer an overclocked kernel in the near future but we'll have to see.
Click to expand...
Click to collapse
Can you give a few more details?
Is it HoneyComb 3.2?
Is it for WiFi or 3G tablets?

BeeGee_Tokyo said:
Can you give a few more details?
Is it HoneyComb 3.2?
Is it for WiFi or 3G tablets?
Click to expand...
Click to collapse
It is Honeycomb 3.2. The shw-m380w is a wifi model.
Sent from my SHW-M380W using xda premium

One of the most noticeable difference is the integrated digital dmb tv and radio receiver and antenna. With no change in the look and dimensions. It comes wifi with or without 3g.

koe1974 said:
Nov. 26, 2011
Pershoot has graciously offered his time and resources and built recovery-cwm_5.0.2.7-sam-tab-10.1_kor_odin.tar.zip
He included the following notes:
Click to expand...
Click to collapse
refreshed:
http://droidbasement.com/db-blog/?p=2439

pershoot said:
refreshed:
http://droidbasement.com/db-blog/?p=2439
Click to expand...
Click to collapse
Excellent! Just completed a backup and all worked as expected.
Thanks
Sent from my SHW-M380W using xda premium

Thank you so much pershoot and Koe1974. Now, CWM can operate normally with my device. Actually, my device model is shw-m380s with 3g and I would like to ask you is it able to upgrade by CWM with the custom roms of P7500 (as overcome rom) and the overclock kernel?

Hi pershoot. I've just made a backup for my kor tab (model shw-m380s). Please help me to check the boot.img attached and let me know my device is able to apply your kernel or not. Thank you in advance.

Your device is not compatible with my kernel.

pershoot said:
Your device is not compatible with my kernel.
Click to expand...
Click to collapse
Thank for your reply Pershoot. Yesterday, I tried to patch your kernel and my tab couldn't boot, so I had to back to its stock kernel. I also upgraded my tab to Overcome Rom with stock kernel and it works fine exclude one issue is the brightness level couldn't adjust anymore. Because I am not good at hex and linux coding, so I appreciate if you or other developers could help me (and people own this device) to fix my stock kernel to make it is suitable with CWM roms and able to be overclocked. Thanks alot in advance.

Just to share some of my experience, I have an M380W model, I installed pershoot's CWM-based recovery, backed up everything, and installed Galaxy Task 6.2 ROM for a try (and 6.3 update). The screen keeps scrolling, but this is solved by restoring boot.img within the recovery.
I then have the same symptom as phuonglev, the screen brightness level can't be adjusted (set to medium and looks so), and I sometimes have orientation problems.
Could all this be resolved with your specific kernel koe1974 ?

I don't imagine it will. All I am planning at this point is to enable overclocking. It will essentially be a stock kernel. It sounds as if it is something in the rom causing the problem. As much as we would like to think the korean models are the same, from past experience with a galaxy s 'shw-m110s vs gt-i9000', the roms are just not interchangable. It always seems that there is 'something' that does not work as it should.
Sent from my SHW-M380W using xda premium

How is your progress Koe? I'm waiting for the good new from you.

Awesome, can't wait to see some progress.
I thought I was the only one with problems trying to use tasks rom.
Just FYI for any other M380W owners out there, you can supercharge your tab. Made a big difference for me.
*Edit
Btw Koe,
There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).

aigoya said:
Btw Koe,
There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).
Click to expand...
Click to collapse
If you are on EK10 then it is probably the update for Polaris Office. However, if you are not running the stock rom, your device may be reporting that is an p7500 or p7510 which I think comes with QuickOffice. So it might be confused.
Sent from my SHW-M380W using xda premium

could you upload the rom to other source please?

samoelito said:
could you upload the rom to other source please?
Click to expand...
Click to collapse
This is the best I can do ( http://www.wupload.com/file/2662167342/SHW-M380W.EK10.7z ). If you prefer bit torrent, let me know.

So, just to confirm.
If I want to root my device (I just picked it up yesterday) I need to download the
Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.
So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it
Then, who do you flash a ROM with this one?
I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before Thanks for that.
I have taken over the old thread and have been trying to fill your shoes! hahhaa

[email protected] said:
So, just to confirm.
If I want to root my device (I just picked it up yesterday) I need to download the
Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.
So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it
Then, who do you flash a ROM with this one?
I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before Thanks for that.
I have taken over the old thread and have been trying to fill your shoes! hahhaa
Click to expand...
Click to collapse
To root just follow the instructions and you will be fine.
ek10.7z is just the stock rom for if you choose to revert from back. currently, there doesn't seem to be much development going on for the m380w so I uploaded it for those brave enought to try roms built for other 10.1 models. I always delete tons of stock apps so it's helpful to have a stock rom to get back it i need to.

is flashing ROMS still the same?
Just using Odin and put the file into the PDA slot?

[Q] How to avaoid post-flash bootloop?

Hello people,
This has without a doubt been asked before but I haven't been able to find an answer. My problem is this:
A while back I flashed the then latest available version of the MIUI.us ROM for my international SGS i9000. Everything went fine with the flashing; I had to flash the ROM four times in part due to the new CM10 partition layout. Since the flashing was done late at night, I turned my phone of and plugged in the charger for it to charge during the night. The next day when I tried booting it up, the phone never got beyond the kernel screen. I didn't pay to much attention to this since I already had been thinking about flashing the CM10 ROM anyway and this seemed like a good time to do so.
I saw no other solution to escape the bootloop but to go back to stock (2.3.3 for my region) and then root the phone again (CF's method) and proceed with flashing my ROM of choice. I did not use a PIT-file in going back to stock. I flashed stock using ODIN v1.7 (I think). My computer at the time was running 64-bit Windows 7. The stock ROM I used, I found on a stock ROM collection thread here on XDA since the stock ROM from sammobile.com only got stuck in bootloop already at the first boot up after the flash with ODIN was complete.
Next I flashed the M2-version of the CM10 ROM and everything went fine. Since my phone already had the new partition layout from previously having flashed the MIUI.us ROM, I only needed to flash the CM10 ROM once.
The CM10 ROM worked like a dream for about two weeks. I stayed on the M2 during this time. After two weeks though, my phone again got stuck in bootloop unable to get beyond the kernel screen. Again it had been turned off and plugged to the charger during the night preceding the bootloop; a thing very common in my use case.
In neither of the cases did I change anything about the ROM I flashed; no custom kernels, no custom modems, everything was as it came with the ROM.
My question then is this:
What do I have to do in order to avoid ending up in bootloop again?
My thought was that I should return to stock and do everything from scratch again but this time use a PIT-file in order to make things "the right way". The thing is that half the flash-guides say one should use a PIT-file and the other half advice you not use a PIT-file since this would increase the risk of bricking your phone. Is there any point in using a PIT-file when flashing the stock ROM since flashing the CM10 ROM would change the partition layout anyways?
Am I taking the wrong approach to this? I really liked CM10 and would like to try out the stable version.
Sorry for the very long post.
Thanks in advance.

The pit file contains information about the partition layout. When you go back to stock from JB, you should use it. Try again going to stock with pit file and then flashing cm9 and then cm10. This way is the safest.
Search next time:
http://forum.xda-developers.com/showthread.php?t=987314
Sent from my GT-I9000

amerkiller1995 said:
The pit file contains information about the partition layout. When you go back to stock from JB, you should use it. Try again going to stock with pit file and then flashing cm9 and then cm10. This way is the safest.
Search next time:
http://forum.xda-developers.com/showthread.php?t=987314
Sent from my GT-I9000
Click to expand...
Click to collapse
Seems legit. I'll try that. That particular thread did not show up when I was searching for solutions to my problem. Thank you for your answer and for your patience.

Glad I helped. Please post here when the problem is solved.
Sent from my GT-I9000

amerkiller1995 said:
Try again going to stock with pit file and then flashing cm9 and then cm10. This way is the safest.
Sent from my GT-I9000
Click to expand...
Click to collapse
I just got to thinking. As you might have heard the CM-team changed the partition layout after a certain version of their CM10 release. When going from Stock to CM9 and then to CM10 is it all right if I flash the stable version of each release or should I go from Stock to CM9 to CM10 pre-partition layout change to CM10 post-partition layout change?
Also: should I prefer the Stock ROM found at sammobile.com or are the files found on this thread better?
Thanks in advance.

kayjay7 said:
I just got to thinking. As you might have heard the CM-team changed the partition layout after a certain version of their CM10 release. When going from Stock to CM9 and then to CM10 is it all right if I flash the stable version of each release or should I go from Stock to CM9 to CM10 pre-partition layout change to CM10 post-partition layout change?
Also: should I prefer the Stock ROM found at sammobile.com or are the files found on this thread better?
Thanks in advance.
Click to expand...
Click to collapse
go to the stable edition of each version
about the stock rom, use either, it doesnt matter

amerkiller1995 said:
go to the stable edition of each version
about the stock rom, use either, it doesnt matter
Click to expand...
Click to collapse
Aight! Will try that out and see what happens. Thanks again for your reply. Btw, should I go with the CM9 stable or the CM9.1 stable? Maybe it doesn't matter in my case since CM10 stable is the final aim of the project? As I understand it CM9.1 stable is only a maintenance release?
Sorry again and thanks for your patience.

kayjay7 said:
Aight! Will try that out and see what happens. Thanks again for your reply. Btw, should I go with the CM9 stable or the CM9.1 stable? Maybe it doesn't matter in my case since CM10 stable is the final aim of the project? As I understand it CM9.1 stable is only a maintenance release?
Sorry again and thanks for your patience.
Click to expand...
Click to collapse
no need to be sorry, i like helping
you're right, it doesn't matter, maybe for the placebo effect use 9.1

amerkiller1995 said:
no need to be sorry, i like helping
you're right, it doesn't matter, maybe for the placebo effect use 9.1
Click to expand...
Click to collapse
I'll do that and report back later this week. Thanks again for your time.

Well I finally had time to flash my phone. I flashed stock using the 512 PIT-file. Then I flashed CM9.1 stable and finally CM10 stable; like you advised me to. The only problem when flashing stock was that the single-file stock ROM found on sammobile.com does not seem to work for me; I get stuck in bootloop when I flash this file (doesn't matter if I use a PIT-file or not when doing so). I tried using the three-file stock ROM found on the XDA forums (with PIT) and this time it worked. Other than that everything went fine. I hope the post-flash bootloop phenomenon I've experienced earlier does not appear again.
One more thing: I also flashed the 4.2 keyboard with the swype-like function through recovery [Android4.2_Keyboard_v2_gnufabio.zip]. How do I go about uninstalling it?

kayjay7 said:
Well I finally had time to flash my phone. I flashed stock using the 512 PIT-file. Then I flashed CM9.1 stable and finally CM10 stable; like you advised me to. The only problem when flashing stock was that the single-file stock ROM found on sammobile.com does not seem to work for me; I get stuck in bootloop when I flash this file (doesn't matter if I use a PIT-file or not when doing so). I tried using the three-file stock ROM found on the XDA forums (with PIT) and this time it worked. Other than that everything went fine. I hope the post-flash bootloop phenomenon I've experienced earlier does not appear again.
One more thing: I also flashed the 4.2 keyboard with the swype-like function through recovery [Android4.2_Keyboard_v2_gnufabio.zip]. How do I go about uninstalling it?
Click to expand...
Click to collapse
You'll have to extract the cm10 keyboard apk from the cm10 zip file and put it in /system/app folder.
Tip: If you don't like cm10 or want something cool, then you can download flash another JB ROM, eg Slimbean, C-Rom, Remics-JB, X-bean etc.
Sent from my GT-I9000

To answer my own question: apparently the multi-file ROM found at sammobile.com is meant to be used with Heimdall. But as I understand it Odin is better for going back to Stock WITH re-partiotion (PIT-file). Am I wrong?

amerkiller1995 said:
You'll have to extract the cm10 keyboard apk from the cm10 zip file and put it in /system/app folder.
Click to expand...
Click to collapse
I was wondering how to uninstall the 4.2 keyboard I installed not the stock AOSP keyboard that comes preinstalled with CM10.
amerkiller1995 said:
Tip: If you don't like cm10 or want something cool, then you can download flash another JB ROM, eg Slimbean, C-Rom, Remics-JB, X-bean etc.
Click to expand...
Click to collapse
I find CM10 to be awsome. As I understand it basically *all* other ROMs are based off of CM. Out of the alternative ROMs you mentioned I would probably try out X-Bean and Slim Bean; I really like the look and feel of Vanilla Android. One thing I do miss in CM10 is the kill all button in the task manager. And that apps really close and release their memory when I close them.

kayjay7 said:
I was wondering how to uninstall the 4.2 keyboard I installed not the stock AOSP keyboard that comes preinstalled with CM10.
I find CM10 to be awsome. As I understand it basically *all* other ROMs are based off of CM. Out of the alternative ROMs you mentioned I would probably try out X-Bean and Slim Bean; I really like the look and feel of Vanilla Android. One thing I do miss in CM10 is the kill all button in the task manager. And that apps really close and release their memory when I close them.
Click to expand...
Click to collapse
I am not sure, but i think that when you installed the 4.2 keyboard, it replaced the aosp one, so you wil have to open the CM10 zip file, find the aosp keyboard .apk and put it on your phone in /system/app and then set the permissions accordingly.
Regarding other ROMs, yes they are based off cm10, but some people say cm10 is a bit slow so they prefer other versions, some with extra feautures, themes or removed things.

amerkiller1995 said:
I am not sure, but i think that when you installed the 4.2 keyboard, it replaced the aosp one.
Click to expand...
Click to collapse
Nope, both are still there. The main reason I would like to uninstall the 4.2-version is because the swype functionality only supports English (I'm multilingual). I was hoping I wouldn't need to install the Swype keyboard if the 4.2 stock keyboard worked completely with all my preferred languages. No need to have an extra keyboard installed if I'm not gonna use it.
amerkiller1995 said:
Regarding other ROMs, yes they are based off cm10, but some people say cm10 is a bit slow so they prefer other versions, some with extra features, themes or removed things.
Click to expand...
Click to collapse
Out of X-Bean and Slim Bean which one would you recommend and why? What are you running yourself? I don't know why but it just *feels* like CM10 is more stable (although, admittedly, I haven't tried any of the ROMs you listed). I guess in a way CM10 is the Official Custom ROM with the most up-to-date developer support. For instance CM10 went to Android v4.1.2 quite a while ago (when compared with other ROMs). When it comes to CM10 being a bit slow, lets face it; the i9000, although being a very good phone, is more than two years old at this point.

kayjay7 said:
Nope, both are still there. The main reason I would like to uninstall the 4.2-version is because the swype functionality only supports English (I'm trilingual). I was hoping I wouldn't need to install the Swype keyboard if the 4.2 stock keyboard worked completely with all my preferred languages. No need to have an extra keyboard installed if I'm not gonna use it.
Out of X-bean and Slim Bean which one would you recommend and why? What are you running yourself?
Click to expand...
Click to collapse
If both are there then delete the 4.2 apk and reboot your system. I dont think there is a way to uninstall it.
I use Remics-JB because of the S3 look. X-bean and slimbean are from the top of my head,both of them are focused on speed. There are many more, choose the one you like.

amerkiller1995 said:
If both are there then delete the 4.2 apk and reboot your system. I dont think there is a way to uninstall it.
Click to expand...
Click to collapse
The thing is it came as a ZIP-file; not an apk. I had to install it through recovery mode.

kayjay7 said:
The thing is it came as a ZIP-file; not an apk. I had to install it through recovery mode.
Click to expand...
Click to collapse
Flashing a zip just places some files in some directories. When you flashed the keyboard, all it did was copy the apk to /system/app.
Delete it and you should be OK.
Sent from my GT-I9000

amerkiller1995 said:
Flashing a zip just places some files in some directories. When you flashed the keyboard, all it did was copy the apk to /system/app.
Delete it and you should be OK.
Sent from my GT-I9000
Click to expand...
Click to collapse
Seems about right. I can't figure out which apk it is though. None of the ones listed has a name even suggesting it is a keyboard.

Open the keyboard zip you flashed and check the name of the apk
Sent from my GT-I9000

[Q] Time for a new ROM - noob questions...

Ok, so my P1000 (stock Gingerbread, bought SIM-freeon and currently on Vodafone UK) has become soooo slow over the past two years of ownership, and a minor water contact today forced a factory reset... So a clean JPZ based Tab to play with...
Been toying with the idea (in hope for better performance) to get a custom ROM from here, maybe one based on ICS (if the hardware can take it), but after a couple of days of reading through all the posts and threads, I confess I am at a complete loss: can anyone recommend a stable working ROM (even if essentially based on stock images) that could/should improve the tired tab's performance? Also, not clear: do most ROMs here come with rooting or do I then need to apply CFRoot separately? Lastly, at the time of my last post (way way back), Overcome ROMs seemed to be the way to go, but today their site is down?
Please be gentle, though I understand the basics, I am indeed a novice in this arena

Follow my signature for link to overcome new link thread
Sent from my GT-I9300 using xda app-developers app

Great, many thanks, downloading now... As a follow up, I understand this is their version of 2.3.6 (Gingerbread); don't want to be a , but was wondering if there's an ICS ROM out there for the P1000? Also, is overclocking possible on the Overcome ROM? (the idea is to try and get a device that actually runs better than stock GB, so not even sure if the hardware is up to speed with ICS)
Again, thanks and apologies for the q's, got more confused reading through the posts than I was before

There are AOSP based ICS/JB
Just look for them in dev section.
Either CM or AOKP.
You still need overcome kernel to have cwm first in order to flash them.
kernel, not ROM, OK?
Overcome should be overclockable.
Sent from my GT-P1000 using xda app-developers app

There is a relly good CM10 (JB) ROM I'm using: sapir-rom.blogspot.com It's nightly, but it works perfectly for me with very good performance.

[Q] Any other ROMS for the S4 Active?

Has anybody been able to find any ROMs for the S4 Active? Preferably, the i537, but I'm willing to try anything for the GT-I9295. I know it's early, as the Safestrap method is fairly new, and the kernel can't be touched right now, so a 4.3 ROM is out of the question. I'm using the ROM listed here:
http://forum.xda-developers.com/showthread.php?t=2406177
I'm loving stock, but I have Cyanogenmod on my Nexus and love the customization. Does anybody know of anything close to that available for the Active?

Yea I believe its ported from the International version...they call it google edition I think! If I helped ya..it dosent hurt to hit the thanks button! :good:

Actually there is a pre-release 4.3 ROM available, it's the MI2 build for the I537 and yes it's a leak from AT&T (thanks to designgears and you can find it here). Two issues with that one if you choose to use it:
1) You may not be able to update to the official OTA 4.3 expected sometime later this month (according to rumors, that is)
2) There's no working root so if you must have that, don't bother with this build just yet
There is a third issue that appears to be the most common problem with the MI2 build and that's the screenshot feature which isn't working, it's covered in the thread for the MI2 build.
Because it's a pre-release similar to the MF1 pre-release leak, it appears to not allow an OTA but since there hasn't been any 4.3 OTA updates from AT&T as of yet nobody really knows what's going to happen.
Also, if you flash that MI2 build, your only alternative will be to fall all the way back to the MF1 build since no ODIN One-click exists for the MF2 or MF3 builds, but you can switch between the MF1 and MI2 builds (confirmed by others and I've done it several times in the past week myself).
Aside from that "official" ROM leak, the only other current working option is using Safestrap on MF1/MF2/MF3 (with the appropriate kernel modules) along with the AOSP ROM provided by LeJay which you can find here.
That's pretty much it. I have the I537 as noted so I don't muck with the I9295 ROMs but I think there's at least the one CM10.2 build for it, and no, it doesn't work on the I537 even with Safestrap.
EDIT: DOH, forgot about the ROM from d8389 he just released yesterday, also made from the MI2 build and you can find that one here - that's for the I9295, btw.

br0adband said:
Actually there is a pre-release 4.3 ROM available, it's the MI2 build for the I537 and yes it's a leak from AT&T (thanks to designgears and you can find it here). Two issues with that one if you choose to use it:
1) You may not be able to update to the official OTA 4.3 expected sometime later this month (according to rumors, that is)
2) There's no working root so if you must have that, don't bother with this build just yet
There is a third issue that appears to be the most common problem with the MI2 build and that's the screenshot feature which isn't working, it's covered in the thread for the MI2 build.
Because it's a pre-release similar to the MF1 pre-release leak, it appears to not allow an OTA but since there hasn't been any 4.3 OTA updates from AT&T as of yet nobody really knows what's going to happen.
Also, if you flash that MI2 build, your only alternative will be to fall all the way back to the MF1 build since no ODIN One-click exists for the MF2 or MF3 builds, but you can switch between the MF1 and MI2 builds (confirmed by others and I've done it several times in the past week myself).
Aside from that "official" ROM leak, the only other current working option is using Safestrap on MF1/MF2/MF3 (with the appropriate kernel modules) along with the AOSP ROM provided by LeJay which you can find here.
That's pretty much it. I have the I537 as noted so I don't muck with the I9295 ROMs but I think there's at least the one CM10.2 build for it, and no, it doesn't work on the I537 even with Safestrap.
EDIT: DOH, forgot about the ROM from d8389 he just released yesterday, also made from the MI2 build and you can find that one here - that's for the I9295, btw.
Click to expand...
Click to collapse
I'll keep playing the waiting game then... Maybe I can submit a request for Cyanogenmod to be made for this device.

Until the bootloader is unlocked, it's most likely not going to happen at all. It's possible that someone with enough talent can put together a CM10.1 ROM which uses the current kernels (I think, I'm not 100% sure on that), but the MI2 4.3 build now is pretty locked down as it is (no known root at the moment and it looks like Safestrap may be a no-go as well for that or future builds).
The honest truth is the GS4A is simply not popular enough to get any reaction from the CM crowd at all, unfortunately, and it's entirely possible it may not even be available for much longer given that unpopularity. It's not selling well, and the few of us that do have them are just that: few and far between.
It's sad because it's a great device; it IS an S4 with a lower resolution camera and the water-resistant aspect as well as the LCD panel (not AMOLED like the S4) which is just fine by me, I can see it better in daylight than an AMOLED anyway. But the locked bootloader basically ensures the level of interest is negligible at best, not much can be done about it unless a miracle comes along at this point.
I'm very happy with mine for many reasons, not just 'cause I got it so cheap.

br0adband said:
Until the bootloader is unlocked, it's most likely not going to happen at all. It's possible that someone with enough talent can put together a CM10.1 ROM which uses the current kernels (I think, I'm not 100% sure on that), but the MI2 4.3 build now is pretty locked down as it is (no known root at the moment and it looks like Safestrap may be a no-go as well for that or future builds).
The honest truth is the GS4A is simply not popular enough to get any reaction from the CM crowd at all, unfortunately, and it's entirely possible it may not even be available for much longer given that unpopularity. It's not selling well, and the few of us that do have them are just that: few and far between.
It's sad because it's a great device; it IS an S4 with a lower resolution camera and the water-resistant aspect as well as the LCD panel (not AMOLED like the S4) which is just fine by me, I can see it better in daylight than an AMOLED anyway. But the locked bootloader basically ensures the level of interest is negligible at best, not much can be done about it unless a miracle comes along at this point.
I'm very happy with mine for many reasons, not just 'cause I got it so cheap.
Click to expand...
Click to collapse
I think our best hope is for @Hashcode to get kexec working with SafeStrap. Then we will be able to use ROMs with any kernel. Until then we're stuck with GPE 4.2.2.

Hashcode made a post or two at his blog/site stating that things are becoming incredibly tough to make such workarounds viable anymore, even to the point where it's not even worth the time and trouble to make the effort at all in some situations. I think with the GS4A, more specifically the AT&T I537 model, we could just have a device that simply isn't going to get itself cracked wide open without some small miracle happening.
Come on, someone working at Samsung... have some pity on us and drop us something to help out, will ya?

I've started a request forum here:
http://forum.cyanogenmod.com/topic/80004-cyanogenmod-for-the-s4-active/
If anyone would like to back me up, it'd be much appreciated.

Decided it wasn't worth the BS of heading back to Best Buy so I'll stick with MF1 for now. I did make a reply at the CM forum about the potential of someone building CM10.1 as a flashable zip for us and provided the link to the kernel source for the I537, maybe someone with some spare time might be able to create something.
I really wish I'd spent more time learning how to do that; if I had the necessary skill set I'd build it myself I suppose but I've never been into that side of the device firmware/ROM stuff.
But who knows...

I'm running Shostock v2.3 on my I537 with one of my rom slots in safestrap. i'm on MF2. of the S4 ROMs, i've only tried Shostock and Goldeneye, but i'm sure other S4 ROMs will work too. when you install one, you also have to install the modules pack and camera fix from the ported google edition thread. the only other problem is the menu and back buttons don't work out of the box with an S4 ROM because our buttons aren't capacitive. thankfully, Darkman was kind enough to show me how to fix those so they work like normal.

hokeymcf said:
I'm running Shostock v2.3 on my I537 with one of my rom slots in safestrap. i'm on MF2. of the S4 ROMs, i've only tried Shostock and Goldeneye, but i'm sure other S4 ROMs will work too. when you install one, you also have to install the modules pack and camera fix from the ported google edition thread. the only other problem is the menu and back buttons don't work out of the box with an S4 ROM because our buttons aren't capacitive. thankfully, Darkman was kind enough to show me how to fix those so they work like normal.
Click to expand...
Click to collapse
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap

yankeesfan714 said:
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap
Click to expand...
Click to collapse
well, i don't edit the ROM before flashing it. after flashing the ROM, any updates for it, the modules pack, and the camera patch, i go into /system/usr/keylayout using a file explorer, and add:
key 139 MENU
key 158 BACK
to gpio-keys.kl with a text editor. after that, reboot and they work like they should.

hokeymcf said:
well, i don't edit the ROM before flashing it. after flashing the ROM, any updates for it, the modules pack, and the camera patch, i go into /system/usr/keylayout using a file explorer, and add:
key 139 MENU
key 158 BACK
to gpio-keys.kl with a text editor. after that, reboot and they work like they should.
Click to expand...
Click to collapse
Is it possible to add this to either the modules zip or the camera fix to make it easier for users? Ideally this would be added to the camera fix since I think @Hashcode is going to automate the modules in SafeStrap eventually.
On another note, I had no idea we could flash regular GS4 ROMs, this opens up a world of possibilities. I assume we can only flash 4.2.2 ROMs though?

Devo7v said:
Is it possible to add this to either the modules zip or the camera fix to make it easier for users? Ideally this would be added to the camera fix since I think @Hashcode is going to automate the modules in SafeStrap eventually.
On another note, I had no idea we could flash regular GS4 ROMs, this opens up a world of possibilities. I assume we can only flash 4.2.2 ROMs though?
Click to expand...
Click to collapse
i have no idea. i could try, but it's probably a job better suited to someone who really knows what they're doing, since i'm only as good as the tutorials i find on the internet.
once again, i dunno. i'm on MF2, but shostock is MF3. so since that's different but still works, it might be possible to flash a 4.3 ROM, but the fact that i read that there's no going back once you do flash it, i haven't tried it.
i agree that it's awesome we can actually use regular s4 ROMs.

yankeesfan714 said:
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap
Click to expand...
Click to collapse
So in theory any stock based s4 4.2.2 ROM will run with this buildprop modification?
GT-i9295(i537) running SafeStrap

It's not a build.prop edit, but yeah, I think any S4 4.2.2 ROM would work.

S-Beam
Set them next to each other and use S-Beam, it's what it was designed for. Or even Bluetooth would work.

Just so everybody is aware @my-blue-snog-box has created a flashable zip file that will edit the keyboard file and get the hard keys working. It can be found here. If you try any S4 ROMs please post the functionality of them so we can create an index of ROMs working with SafeStrap.
I've posted over there that I got Hyperdrive ROM working, you just need to be careful during setup.

CM Unofficial 2013 10 10 fkosa's reply
I am running CM 20131010 Unoffical - jactiveltxxx from, ofcourse it is 4.3 and it is running smothly.
Havn't found any anoying errors yet.
http://forum.xda-developers.com/showthread.php?t=2395242&page=11
I tried to make some roms for myself and found out the following:
from: CM 20131017 Nightly - jltxxx - was a bit slow, and it felt like the touch was a bit delayed verry anoying
from: CM 20131021 Nightly - jltxxx - here there was something wrong with the screen.
But then again the nightly builds tends to a bit unstable from time to time.

Any Galaxy S4 Rom
I just recently got the galaxy note 2 and loving everything about it inside and out. But I was just wondering if there are or will be any rom or ports of a galaxy s4 rom to our galaxy note 2? Ive look in the android forums but did not see anything besides the hawkish rom which I am now currently using...

Req. Cell Broadcast.

It's been asked for before in other places but I figure I should ask here. If it's the wrong place please move this. I would like the Cellbroadcast Service to be able to be installed on a ROM. They have it for Nexus here http://forum.xda-developers.com/showthread.php?t=2164711 and someone tried to do it for Atrix 4G and seems like it failed http://forum.xda-developers.com/showthread.php?t=1946265 I'd really like this without having to use Kyler's Froyo.

Sakuryu said:
It's been asked for before in other places but I figure I should ask here. If it's the wrong place please move this. I would like the Cellbroadcast Service to be able to be installed on a ROM. They have it for Nexus here http://forum.xda-developers.com/showthread.php?t=2164711 and someone tried to do it for Atrix 4G and seems like it failed http://forum.xda-developers.com/showthread.php?t=1946265 I'd really like this without having to use Kyler's Froyo.
Click to expand...
Click to collapse
have you tried any non Froyo ROM?

palmbeach05 said:
have you tried any non Froyo ROM?
Click to expand...
Click to collapse
I've Tried Nottactrix (I know I mispelled), MROM, CM 10.1, NOWBLAST, CM9, as well as almost all others. I've tried flashing the Cellbroadcast.apk and even dis-assembled the froyo rom that has it as an option but neither work. Point of interest, Kyler's Froyo Rom lacks the Cellbroadcastreceiver.apk so I don't know what I'd have to rip for it to work/

Sakuryu said:
I've Tried Nottactrix (I know I mispelled), MROM, CM 10.1, NOWBLAST, CM9, as well as almost all others. I've tried flashing the Cellbroadcast.apk and even dis-assembled the froyo rom that has it as an option but neither work. Point of interest, Kyler's Froyo Rom lacks the Cellbroadcastreceiver.apk so I don't know what I'd have to rip for it to work/
Click to expand...
Click to collapse
Ok, I hear what you're saying, but i'm a little confused. As an end result, what ROM are you trying to use?

palmbeach05 said:
Ok, I hear what you're saying, but i'm a little confused. As an end result, what ROM are you trying to use?
Click to expand...
Click to collapse
I use Nottach as my perma install. It's what I prefer, but I would like to have the Cellbroadcast option installed. I visit some areas where I need to know about tornados, shootings, hurricanes and the like. Plus it would be nice to have just in case.

Sakuryu said:
I use Nottach as my perma install. It's what I prefer, but I would like to have the Cellbroadcast option installed. I visit some areas where I need to know about tornados, shootings, hurricanes and the like. Plus it would be nice to have just in case.
Click to expand...
Click to collapse
ok, so with that said, you are looking for a CellBroadcastReciever.apk that is designed for GB (2.3-2.3.7), not for Froyo, ICS, JB, or KK (even if KK isn't available for our device just yet)

palmbeach05 said:
ok, so with that said, you are looking for a CellBroadcastReciever.apk that is designed for GB (2.3-2.3.7), not for Froyo, ICS, JB, or KK (even if KK isn't available for our device just yet)
Click to expand...
Click to collapse
Yes one that works on the Atrix 4G because the Nexus ones are for a GB device if I am reading correctly. I've tried just flashing those (Stupid I know) and no result. I've tried swip-swapping some stuff around and Iv'e come to the conclusion I cannot do this myself with just the froyo rom, the apks and nottach to mess with.

Both of those versions (this one and this one) work on JB and above only (one is for 4.1, the other is for 4.2).
As you noticed yourself, Kyler's stock Froyo does not contain it, and I was unable to find a version that works on Froyo. Where did you find one for Froyo?

ravilov said:
Both of those versions (this one and this one) work on JB and above only (one is for 4.1, the other is for 4.2).
As you noticed yourself, Kyler's stock Froyo does not contain it, and I was unable to find a version that works on Froyo. Where did you find one for Froyo?
Click to expand...
Click to collapse
One of his links takes you to a thread with a few posts. The last post has a download link.
I get that we have a froyo version based off of his searching, and that we do have JB versions based off of experience with epinter's ROMs. I don't know about GB or ICS versions, but he's definitely looking for the GB version.
Sent from my MB886 using xda app-developers app

palmbeach05 said:
One of his links takes you to a thread with a few posts. The last post has a download link.
I get that we have a froyo version based off of his searching, and that we do have JB versions based off of experience with epinter's ROMs. I don't know about GB or ICS versions, but he's definitely looking for the GB version.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
It was in Kyler's Froyo settings, The APK is not there but the item is in the settings and fully customizable.

Well I'm trying out CM 10.2 right now but having a flashable version could work well if I switch back.

I examined Kyler's Froyo. Sadly it seems this functionality has been hardcoded into Settings.apk and BlurPhone.apk.

Ahhh, it seemed like that when I tore it apart.

I just examined the latest AT&T firmware (2.3.6) and I found the same thing therein. That means the same functionality should exist in the latest official GB as well?
I can't test this myself, I'm running a custom ROM and I don't really want to reflash now, plus to my knowledge none of the networks here offer cell broadcast.

I know florida has it, Due to ya know, all the high emergency weather and dangerous child kidnappers