Develop Bugs

Samsung Galaxy Gio GT-S5660M - ArpegGioMod ROM

(Avis aux intéressés, j'ai parti une discussion en français sur Frandroid.)
Hello everyone,
Here's my ArpegGioMod ROM, for the Galaxy Gio GT-S5660M. Current (and final) version is 0.9
(ArpegGioMod has had over 1500 downloads! Thanks!)
Features:
Rooted
Deodexed apps and framework. (Optional)
Working FM radio (remember, your headphones are the antenna!)
No power on sound.
Restored support for the normal Android bootanimation.zip format. Right now it's just running the "base" animation (with the green Android text). I'm open to suggestions/logos/proposals!
CRT screen off animation re-enabled, you do need to turn back animations on in the settings to see it.
ADW Launcher (I just used the "standalone" version and placed it in /system/app/, not the cleanest way, but it works, and leaves you the choice between that and Touchwiz Launcher)
Removed all Bell software, as well as some Samsung apps.
New in 0.6
Added options to the power button menu: Reboot (Normal), Reboot Recovery Mode and Reboot to Download Mode.
Car mode.
New in 0.7
Phone will not relock itself to Bell after doing a factory reset without a SIM card in the phone.
Changed the default browser homepage to Google instead of Bell's.
New in 0.8
Phone will not relock itself to Bell after doing a factory reset without a SIM card in the phone. (Turns out I mixed up some files and uploaded a version with Bell apps left in the CSC folder, along with the unmodified customer.xml. Not an issue, until someone did a factory reset.)
Unsecure kernel. So now, adb remount and push work. adb shell is permanently root.
New in 0.9
CWM installation instead of Odin
Using Phiexz's customized stock ROM kernel, with support for both ext4 and RFS partitions. The kernel also includes different wifi drivers, and they work for me!
Updated superuser apps (3.0.7) and binaries (3.0.3.2). The upgrade of su from 3.0.3 to 3.0.3.2 seems to have fixed whatever caused the crashes.
Reodexed, this seems to provide better performance.
Removed the annoying "Full charge" notification.
Enabled native SIP functionality. (Untested.)
Removed the "Android Tips" widget.
Added the "Roboto" FlipFont apk, found on XDA.
No-frills CPU Control 1.20
Google Application updates:
Android Market 3.4.4
Gmail 2.3.5.2
Google Maps 6.3.0
Google Search 1.3.3.247963
Street View 1.7.1.0
Voice Search 2.1.4
YouTube 2.3.4
To do:
Implement BLN by patching /system/framework/services.jar
Things I will not do. (Or at least, not without significant assistance from those requesting it.)
Additional languages.
Files required to install 0.9:
Galaxy Gio ext4 converter
Backup RFS User Data (Optional)
Restore User Data to ext4 (Optional)
ROM Zip file: ArpegGioMod 0.9 MD5 hash: 010DA7C4542537443D2DD2E9BDBAFC43
Re-odex script (Optional)
Short Version 0.9 Installation instructions:
If you're upgrading from a stock ROM or ArpegGioMod 0.8: Backup User Data Script
(You'll probably want to delete the two tar.gz files remaining on your SD card afterwards.)
As required: format from RFS to ext4.
If you're upgrading from a stock ROM or ArpegGioMod 0.8: Restore User Data Script
Flash ROM zip
Re-odex as required
Detailed Version 0.9 Installation instructions:
(Or, the "this is my first time trying this out and frankly I'm a little overwhelmed with information" version.)
I'm going to start this one with a brand new, freshly out of the box Gio. I will however assume that you already have a working Odin and Android SDK install. Plenty of tutorials out there for both. (See links below for the correct Odin version.)
Copy the zip files to your MicroSD card.
Reboot your phone in Download Mode. (Hold Volume Down + Home + Power. There will be a pink warning screen. Press Volume Up.)
Flash ClockWorkMod Recovery with Odin.
Reboot the phone into Recovery Mode. (adb reboot recovery, or Home + Power)
"install zip from sdcard"
"choose zip from sdcard"
Install the ext4 converter zip.
Install the ROM zip.
Install the Re-odex script zip.
Reboot
Optional: adb shell, then dd if=/dev/block/bml5 of=/sdcard/bml5 bs=4096 to get your unlock code as per Tweakradje's unlock tutorial.
Enjoy!
Version 0.8 Installation instructions:
Un7zip and flash with Odin.
I strongly suggest you do a factory reflash and reset if you're flashing from something other than stock or ArpegGioMod.
Version 0.8: http://www.mediafire.com/?nxp0ce21909c676 7-Zip file MD5 hash: 6CEE73812AF9D30189A5F808CE0A7DEA
(Thanks Koodiifin!)
Tools and additional information:
CWM 5.0.2.7-based recovery, compiled for the 5660 by Phiexz, modified for the 5660M by Peteragent5: http://forum.xda-developers.com/showthread.php?t=1493932
"Supersafe" bml5 unlock method by Tweakradje, originally meant for the GT-I5500, should also work with little or no modifications for the 5660M: http://forum.xda-developers.com/showthread.php?t=828534
My other thread from which all of this started: Samsung Galaxy Gio GT-S5660 and GT-S5660M Partition Mapping This thread contains links to a rooted, but otherwise completely stock ROM backup I made prior to starting my work on ArpegGioMod.
Older Clockworkmod-based recovery, meant for the Europe/Asia 5660, but working fine on the 5660M: http://particle.blurringexistence.net/samsung-gt-s5660/clockworkmod-recovery
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
Goodbye,
Darkshado

Just installed ArpegGio on my Virgin Mobile 5660M and it seems to be working great. 3G wifi and FM are working, plus I am glad to be rid of a bunch of carrier garbage apps. Thanks Darkshado I can't wait to see a2sd in there. Could I install it the manual way on this FW?
OT:
Thanks too Darkshado for all your tips for 5660M owners. I got mine 3 days ago, rooted and unlocked on day 2, flashed your FW on day 3. Reminds me of my days making custom OS for my blackberry

hardran3 said:
Just installed ArpegGio on my Virgin Mobile 5660M and it seems to be working great. 3G wifi and FM are working, plus I am glad to be rid of a bunch of carrier garbage apps. Thanks Darkshado I can't wait to see a2sd in there. Could I install it the manual way on this FW?
Click to expand...
Click to collapse
If you mean by modifying your boot.img ramdisk, yes. That's what I've been unable to do. I suspect an outdated/incompatible mkbootimg binary, and can't download the source make a new one as of writing this since kernel.org is still down.
If you're feeling adventurous, you could also try flashing an Euro 5660 boot.img. But I can't guarantee there won't be other issues.
OT:
Thanks too Darkshado for all your tips for 5660M owners. I got mine 3 days ago, rooted and unlocked on day 2, flashed your FW on day 3. Reminds me of my days making custom OS for my blackberry
Click to expand...
Click to collapse
You're welcome.

Hi, This is going to be my first flash for my S5660M. I've a small question for it. What mode should I choose in ODIN? Do I need to care about the ops file?
Sorry for my newbie question. Thank you.

You have to rebuild kernel with ext support. To create system.rfs or other *.rfs you have to type in console
Code:
mkfs.ext4 -O ^huge_file system.rfs
or it won`t boot. Of course you need modify initscripts. You can change from rfs to ext4 and it should work.

My problem is that due to the troubles at kernel.org I haven't been able to download the AOSP source yet.
I already suspected it wouldn't work with the stock kernel boot.img before trying.
For the conversion, I used a modified Galaxy Tab ext4 conversion update with the mkfs binaries included. That worked like a charm, CWM mounted the partitions, no questions asked.
I'll have to wait until an official AOSP repo comes back online to take this further.
Goodbye,
Darkshado
Sent from my Nexus S using XDA App

It will work with stock kernel, but you need change build config.

Hi
Just installed your rom this sunday... It work nice and no problem!
Was wondering, is the factory reset from the cwm is better than the one within the phone app? And or is the same?
And keep up the good work it is really appreciated
Thx Dark!
Sent from my GT-S5660M using XDA App

Darkshado said:
Hello everyone,
New in 0.6
[*]Added options to the power button menu: Reboot (Normal), Reboot Recovery Mode and Reboot to Download Mode.
[*]Car mode.
[/LIST]
Goodbye,
Darkshado
Click to expand...
Click to collapse
Nice job, very nice.
Is it duable to create that option in a aditional zipfile.
That you can flash it in recoverymode with a other rom????
You would make me very happy with that.

You have to modify framework-res.apk framework.jar and android.policy.jar for this to work, and it requires editing Smali code.
I did it by loosely following guides meant for the I9000 found here.
You could always push those files from my ROM to give it a try like that, but I wouldn't count on the framework from the 5660M to be fully compatible with the 5660 (which I understand you have from some of your other posts).

Question: has anyone else managed to re-Sim-lock their phone?
It's happened to me inadvertently, twice. Not knowing why on Earth the phone did this, I decided to get to the bottom of things.
The unlock code from bml5 still works, but I find this annoying to say the least.
I found some strings in the CSC files (customer.xml to be exact) that seemed to tell the phone what network to lock itself to.
I managed to make the phone relock itself by going into recovery, wiping user data, and rebooting the phone without a SIM card in. Checking lock status with *#7465625# shows Network Lock [ON]
I turned off the phone, put a foreign SIM back in, unlocked the phone again, and re-wiped user data, leaving the non-Bell SIM in for the first boot. No relock.
I relocked the phone as above. Rebooted into recovery and pushed modified customer.xml files, without the network lock strings, to my /system/csc/ and /system/csc/BMC/system/csc/ directories. No relock!
Those modified CSC files are going to be included in ArpegGioMod from now on.
Goodbye,
Darkshado

Darkshado said:
You have to modify framework-res.apk framework.jar and android.policy.jar for this to work, and it requires editing Smali code.
I did it by loosely following guides meant for the I9000 found here.
You could always push those files from my ROM to give it a try like that, but I wouldn't count on the framework from the 5660M to be fully compatible with the 5660 (which I understand you have from some of your other posts).
Click to expand...
Click to collapse
Hi, thx for the reply
Yes i have the 5660 ( no M ).
But i don't have a linux machine........
And i need that to compile those files.
I supose a linux-live dristri doesn't ad up for the job

Amadeus01 said:
Hi, thx for the reply
Yes i have the 5660 ( no M ).
But i don't have a linux machine........
And i need that to compile those files.
I supose a linux-live dristri doesn't ad up for the job
Click to expand...
Click to collapse
I think a live distro would work fine... Me I installed Vmware player (free) to run a virtual ubuntu machine and it work fine for editing some of the the tar file... so a live distro would even be better i'm sure!
Sent from my GT-S5660M using XDA App

I unlocked with safe bml5 trick and wiped a couple of time but i did not put back a non bell sim since then... So i dont really know...
Did you use some script or some like that in you Rom? Because I got like almost 400-500 more point on antutu benchmark.... Nice
Sent from my GT-S5660M using XDA App

theboo23, Amadeus01: Practically all of my ROM work has been done under Windows so far!
You need:
Java JDK
Android SDK
apktool
Cygwin
A hex editor (I've used Frhed so far)
Notepad++ (Free, open source, tons of features: syntax highlighting and Unix line ending support to name a few)
(Optional) A program that can open FAT format image files such as MagicISO, to extract files from RFS partition images.
(Optional) xUltimate, to simplify deodexing a great deal.
(Optional) 7-Zip
I have installed Ubuntu (on an external USB drive with Wubi and Grub4DOS) to attempt boot.img and kernel modifications, and to build from AOSP/CyanogenMod source.
However, kernel.org, which hosts AOSP repositories, is still down almost three weeks after having been hacked. So those parts of my project have been stalled in the meantime as I hadn't downloaded the source beforehand.
theboo23: There have been multiple reports of deodexing increasing performance, that might explain the points increase on the benchmark. To be frank, I don't bother with them unless I have something really specific to test.
Goodbye,
Darkshado

Darkshado said:
Those modified CSC files are going to be included in ArpegGioMod from now on.
Click to expand...
Click to collapse
By "from now on" I suppose you mean ver 0.7 included which is also on the changelog for it. However, it's exaclty after I flashed 0.7 (from 0.6 and stock before that) that my phone re-locked again and I had to use the unlock code (which I retreived while ago using bml5 method and still keep). I wiped before flashing 0.6 on top of stock, but did now wipe before flashing 0.7 on top of 0.6.
By the way, I knew already that at one point I will need my unlock code again. Having unlocked 6 or 7 5660Ms in the last week I have noticed that, once unlocked for a network (say, Fido) and you put a different SIM (Chatr), it gets locked again! Not only that, if you put the Fido SIM back, it is still locked. You have to enter the unlock code again, and luckily it's always the same. So, I resorted to writing down the code on the back of the phone under the back plate for further reference
And a couple of questions: your ROM has only one file/partition in it - system.rfs - and apparently this is the only thing that it replaces, everything else remains stock. One other custom ROM available on this site contains two files in the .tar - system.rfs and boot.img.
Q1: will it be safe to flash that other ROM on a 5660M having in mind it only replaces those two files/partitions? I know you already answered this before, just being extra cautious
Q2: if I want to return to ArpegGioMod after that, how do I proceed? Where do I get the boot.img from? Posible answer here: I have made a full backup via CWM of the stock ROM. It contains boot.img. Can I insert it in your .tar and flash and expect to get the same as flashing ArpegGioMod directly on stock?
Q3: if I get the system.img (renamed to system.frs) and boot.img from the SWM backup, put them in a .tar and flash, will that give me stock phone?

stfn74 said:
By "from now on" I suppose you mean ver 0.7 included which is also on the changelog for it. However, it's exaclty after I flashed 0.7 (from 0.6 and stock before that) that my phone re-locked again and I had to use the unlock code (which I retreived while ago using bml5 method and still keep). I wiped before flashing 0.6 on top of stock, but did now wipe before flashing 0.7 on top of 0.6.
Click to expand...
Click to collapse
I tried a couple more wipes and SIM swaps (T-Mobile USA, Koodo and Telna) with no relock occurring, so I hate to say, but I'm a bit stumped if there's something else than the CSC files causing this.
By the way, I knew already that at one point I will need my unlock code again. Having unlocked 6 or 7 5660Ms in the last week I have noticed that, once unlocked for a network (say, Fido) and you put a different SIM (Chatr), it gets locked again! Not only that, if you put the Fido SIM back, it is still locked. You have to enter the unlock code again, and luckily it's always the same. So, I resorted to writing down the code on the back of the phone under the back plate for further reference
Click to expand...
Click to collapse
I take it you work at a Rogers/Fido kiosk or store right? You're probably going to get more data on this than I ever will. I too wrote my code in the battery door just in case after it relocked a second time.
Q1: will it be safe to flash that other ROM on a 5660M having in mind it only replaces those two files/partitions? I know you already answered this before, just being extra cautious
Click to expand...
Click to collapse
Should be safe, if the boot.img is meant for the Euro 5660, you could encounter some bugs. I haven't tested those boot partitions and kernels.
Q2: if I want to return to ArpegGioMod after that, how do I proceed? Where do I get the boot.img from? Posible answer here: I have made a full backup via CWM of the stock ROM. It contains boot.img. Can I insert it in your .tar and flash and expect to get the same as flashing ArpegGioMod directly on stock?
Click to expand...
Click to collapse
You could just restore that nandroid backup.
Otherwise, tarring the boot.img with Cygwin and flashing with Odin should work. Then flash ArpegGioMod. Or make a single tar file with both partitions in Cygwin.
Here's a "universal" command: tar -H ustar -c amss arm11boot mibib oemsbl qcsbl boot.img recovery.img csc.rfs system.rfs data.rfs efs.rfs > GT-S5660M_MUGKG3.tar
I put it in a text file with the .sh extension, in cygwin/bin/ making it a command that can be invoked directly. (It's actually part of a set of batch files I've made to automate the copy and preparation of ArpegGioMod updates.)
Q3: if I get the system.img (renamed to system.frs) and boot.img from the SWM backup, put them in a .tar and flash, will that give me stock phone?
Click to expand...
Click to collapse
No reason it shouldn't.

Darkshado said:
I take it you work at a Rogers/Fido kiosk or store right?
Click to expand...
Click to collapse
No, I'm just an user, my job has nothing to do with mobile business. It's just Futureshop had a great deal on 5660Ms last week and half of my family and friends got one I was the first to root and unlock mine so... had to do it with everybody else's. I'm playing with custom ROM flashing now and want to make sure I got everything right, because I suspect I will be doing it number of times.
So I'm using the opportunity to say "Thank you!" for your work!

i used this rom with m 5660m and i still got wifi problems. wont turn correctly. im seeing you mention about ops file and boot img modding.dont kno how to do that

chairsz said:
i used this rom with m 5660m and i still got wifi problems. wont turn correctly. im seeing you mention about ops file and boot img modding.dont kno how to do that
Click to expand...
Click to collapse
Did you flashed a 5660 rom? You'll need to flash the stock 5660m rom first. The link is here;
http://forum.xda-developers.com/showthread.php?t=1233719

Backup and Restore of Stock Gio S5660M Rom After Installing EXT4 Based Custom ROMs

I have been researching the forums for a few weeks now but I have not stumbled across enough threads that would assist me to fully understanding the proper process for restoring via CWM back to a stock ROM (without going back to ODIN to flash it).
Of course this all relates to my Samsung Gio GT-S5660M from Bell in Canada (Pay as you Go). I really only purchased the phone to play with it to learn more. My wife has had the same phone for over a year. Her phone was rooted in order to be none carrier specific so she could use it to replace a phone under contract that was stolen. Other than that, it is stock.
I tried not to post and continue reading but now I am at the point where I need to ask a some specific questions.
First, some background as to what I am trying to do and what I have done so far.
The goal, as I am sure is the case with others, is to test custom ROMs but also be able to restore back to a factory default Samsung based ROM CWM backup at any point in the most convenient fashion.
I would like to perform this process with known working tools on this forum.
To start, I am familiar with the installation of the CWM from phiexz's work http://forum.xda-developers.com/showthread.php?t=1421650. I have installed 5.0.2.7 via Flash from Recovery signed_cwm-5.0.2.7-flashablezip-ext4+rfs. After the installation of CWM I performed a backup of the stock rom.
Once that was complete, I began playing with some custom ROMs installing them via CWM off the SD card from zip files.
I learned after installing the custom ROMs that my phone was reformatted to EXT4 file system. This obviously makes it difficult to simply restore back to the stock ROMs original RFS file system easily. I received the obvious errors message (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) when trying to restore the original ROM files via nandroid restore within CWM.
I have reviewed the nandroid backups stored on the SD card in the \clockworkmod\backup\appropriate dated file and I can see that the file names include RFS before the .tar extension for the system, data and cache files. From everything I have read this is normal since stock Samsung ROMs (at least FROYO and Gingerbread based ones) are based on the RFS file system as opposed to most custom ROMs which are based on EXT4. I made backups of some of the ROMs I was playing with from within CWM nandroid backup. I did notice those files had ext4 before the .tar extension in the file names. So I believe I am clear in understanding that portion.
I read that the only way to really get back to the RFS file version is to use ODIN to flash back the stock firmware all in one package retrieved from www.sammobile.com for the GT-S5660M for Bell in Canada. That again worked perfectly fine. I again went back into restore mode and re-installed signed_cwm-5.0.2.7-flashablezip-ext4+rfs. Once CWM was installed I tried to restore the original stock ROM backup I had saved originally and it gave me the same error (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) even though I know the phone is now back at RFS file system again. Even when I try to perform a backup from CWM of the ODIN installed stock rom it complains stating (Backing up system.... Can't mount /system!.
I of course can reinstall Custom ROMs and restore them just fine after one initial installation and the file system being formatted back to EXT4.
So here are the questions.
1. What is the proper way to restore a stock ROM backup?
2. Is it possible to convert the RFS backup or existing system to EXT4 and have it still operate?
From what I can tell there is custom kernels that support EXT4 that can be injected via ODIN or CWM. Such as CF-ROOT however it is completely confusing to me on how to do that. I tried the ODIN method and that complained. I am not sure what version of CF-ROOT to use. Really I would like to stay with the EXT4 file system and convert the Stock backup to run with a custom ROM if need be. The goal is really just to be able to do it all within CWM and not require a computer other than for transferring files to the SD card as required.
I do not mind using ODIN but I would like to be able to restore with all the settings and changes I made in the stock OS to carry forward so I do not have to do that again.
3. Is there an easier or more reliable method to carry these steps out? Overall I would choose a method that consistently works over convenience.
Any assistance that could be provided would be appreciated.
Thank you in advance for your time in reading and/or hopefully replying to this thread.

Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk

AvrX said:
Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply AvrX.
Is there any particular reason you are suggesting that I use an older version of cwm (5.0.2.6) over 5.0.2.7? Is it due to your experience with stability between the two versions or support of RFS over EXT4?
Also your procedure is a bit vague to me.
Why would backing up another version of the stock ROM again assist me? Converting the stock ROM to EXT4 and then reflashing stock ROM again with Odin does not really make sense. Does the phone have to be rooted again? I thought once rooted you did not have to root it again.
I believe I am even more confused now.
I am confident these are all noob questions that can be answered by someone out there with S5660 experience. Then maybe this thread can be locked for future reference for everyone.

http://forum.xda-developers.com/showthread.php?t=1449320
The thread above is not in the S5660 area but it seems like a step in the right direction. I just can not figure out what version of CF-Root to install via CWM from the following thread http://forum.xda-developers.com/showthread.php?t=788108 for the GT-S5560M. I realize the thread is for a different model phone though.
There is the thread for the GT-S5660 http://forum.xda-developers.com/showthread.php?t=1564629 but I do not see where you download the file for CF-ROOT 3.7. I have signed up for Gio Community forum but my account is not approved yet.
Hence I am still at a loss as to what to do next.
So as you can see I have done research which leads me to believe it is possible but I have no proof it can be done or I just do not fully understand and/or have access/knowledge of the tools to achieve it.

(I have the Canada Model of Galaxy Gio)
1. First use EXT4-only version of CWM
2. You could do a nandroid backup of your EXT4 ROM, the rename then files from .[highlight]EXT4[/highlight].IMG to .[highlight]RFS[/highlight].IMG
3. If you do this, make sure you also edit the [highlight]md5sum[/highlight]
4. Now use RFS+EXT4 version of CWM
5. Replace boot.img in the folder where you saved the backup, with a RFS kernel only! (Stock Kernel) To avoid bricking...
6. Then restore using CWM or nandroid
NOTE:​Do with your own risk. I plan to do it myself soon, but be careful...​

I've re-read your post a few times and I'm not 100% certain that I get what you're trying to do... Going back to a completely stock, out-of-the-box phone from CWM?
Different builds of CWM are available for the Gio. Some support RFS, others ext4. I'd rather avoid those with dual support as they're not very clear regarding what format they're using for which operation.
Let's clarify the types of ROMs out there, you've got:
-Stock, Samsung releases, RFS, Odin-flashable. Leaked images (such as those from samfirmware et al.) contain the CSC image, "put-together" ones (like my early 5660M stock backup) don't as the files are already integrated.
-Stock-based. Community-made ROMs with varying levels of modification; earlier ones were typically Odin-flashable (with a number of issues due to modem and kernel changes, especially for 5660M and V users), later releases usually CWM-flashable. File system support depends on the kernel used. The Samsung kernel only runs RFS, whereas others such as Phiexz's will run either ext4 or RFS.
-AOSP and derivatives. Community-made, CWM-flashable, ext4 ROMs, such as CM7, 9 and 10, or MIUI.
Recoveries:
-CWM, as previously discussed
-Stock: the Samsung recovery you've overwritten pretty early on if you're a typical XDA poster. It does provide for proper CSC installation when flashing a stock ROM through Odin. Can also do a factory reset and reformat /data and /cache RFS partitions.
In most situations you would want to go back to a stock ROM and kernel, but keep the CWM recovery, that's relatively easy to do with an RFS-compatible CWM and a nandroid backup. Even a non-RFS compatible CWM could be made to work with appropriate images and the (ADB shell) dd command.
But back to the question: going back to a completely stock, out-of-the-box phone from CWM, stock recovery, CSC and all?
I've thought about it for a few minutes, and it might just be possible to do. Neat? Kinda. Worth the trouble? Meh.
It would involve dd-ing RFS-format /system, /data and /cache partitions, boot.img and recovery.img, into place.
The part I'm not sure about is how to go about extracting CSC.rfs in the proper location and issuing a reboot recovery command at the end of the script, which should kick stock recovery into gear and apply CSC.
Maybe one manual reboot to finish the process.
Let us know if that helped,
Darkshado

Thank you for the replies Peteragent5 and Darkshado. Again I really do appreciate your time and your support of those out there interested in learning more about android based devices.
Going back to a completely stock, out-of-the-box phone from CWM?
Click to expand...
Click to collapse
Good question Darkshado....let me try to clarify things again. I apologize as I tend to ramble. I would rather give more information than not enough.
Yes that is the goal. Or at least I would like the ability to do that. I understand it is not entirely accurate though as with the installation of CWM it is not really stock.
Let's clarify the types of ROMs out there, you've got:
-Stock, Samsung releases, RFS, Odin-flashable. Leaked images (such as those from samfirmware et al.) contain the CSC image, "put-together" ones (like my early 5660M stock backup) don't as the files are already integrated.
-Stock-based. Community-made ROMs with varying levels of modification; earlier ones were typically Odin-flashable (with a number of issues due to modem and kernel changes, especially for 5660M and V users), later releases usually CWM-flashable. File system support depends on the kernel used. The Samsung kernel only runs RFS, whereas others such as Phiexz's will run either ext4 or RFS.
-AOSP and derivatives. Community-made, CWM-flashable, ext4 ROMs, such as CM7, 9 and 10, or MIUI.
Click to expand...
Click to collapse
Well of course I started with the Out-of-Box Stock Samsung/Bell Canada ROM on the phone based on Gingerbread 2.3.4. I rooted it of course. Then I installed CWM that supported both RFS and EXT4. I believe 5.2.0.7 by Phiexz as mentioned in my first post. To be honest, since I am a noob and I wanted to get started so quickly, I cannot honestly remember which version of CWM I used originally. It may have even been px-CWM-v2.zip. Regardless of the version it obviously supported Stock Samsung/Bell Canada RFS based file system and I used that to make the Nandroid based backup within CWM of the existing Stock ROM on the phone.
After that point I thought I would be safe to start playing with Community-made ROMs CWM-flashable installs based on the GT-S5660 although of course I had the GT-S5660M Canadian version. So I went forward and tried [ROM] Enhanced236 - stock 2.3.6 (06.08.2012 update) http://forum.xda-developers.com/showthread.php?t=1654317 as I wanted something close to original version of Gingerbread that came Out-of-Box with the phone but was upgraded to fix and issue I had with version 2.3.4 of Gingerbread.
The main drive for doing this was to assist my wife with an issue she has on her Bell GT-S5660M running on the SaskTel telco in SK. There is an issue with her SMS/texting. She always has to turn on/off Settings, Wireless and Network, Mobile Networks, Use Packet Data to get texting to send out. Receiving is fine. It seems to be a known issue when the phone is used with Telus or SaskTel networks in Canada. From what I understand the phone with 2.3.4 of Gingerbread is not affected on the Bell and Rogers network in Canada. It seems to be related to a bug in the phone at the particular Gingerbread version 2.3.4 from what I read. Since Kies did not have an update for the Bell based phone beyond version 2.3.4 I thought it is time to check out custom ROMs. After trying her SIM card with the Enhanced236 - stock 2.3.6 everything worked perfectly on my test phone for texting. So I took a Nandroid backup via CWM of that ROM. Then I tried [DEV] CyanogenMod 9.1 / CyanogenMod 10 by MacławStudios http://forum.xda-developers.com/showthread.php?t=1414173 to see what the Jelly Bean hype was about and again made a CWM backup of the ROM to maintain my settings.
I had a friend over and I was showing him what I had learned so far and I was showing all the capabilities of CWM. Then I told him I could even restore back to original factory ROM as well although I had not tried it yet thinking CWM was full proof. I tried it and it failed in front of him. So then I thought...wow...I do not understand as much as I think. That is when I stumbled on the difference between RFS in Stock Samsung ROMs and EXT4 in the Community-made ROMs. Sorry I know that is quite a bit of background information but it helps to show where I am coming from in terms of wanting to accomplish to here.
So I read a bunch and realized that the only way to go back was to flash back to Stock with ODIN. So that at that point I tried your Stock ROM GT-S5660M_MUGKG3_stock_rooted_ROM and the one from sammobile for the GT-5660M from Bell GT-S5660M_BMC_S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3. I thought then I could simply install CWM again (the version that obviously supports RFS and EXT4 5.2.0.7) and then restore the original Stock Nandroid backup I made of the original Out-of-Box ROM. As mentioned in the previous post I saw the rfs in the file names of the back before the .tar extension.
That is when the failures in restoring via CWM occurred noted in the first post (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!). I thought this would work for sure. That is when I started to think if I could get this all to work I would convert the stock ROM with a custom kernel to running exclusively on EXT4 so that if I ever wanted to go back to 2.3.4 I could do it easier with out having to use ODIN and going back to stock RFS file system. So I guess really I do not want to go back to Stock but the Stock Files in EXT4 formatted form...which I understand would require a custom kernel. Regardless I am not able to restore the original backup so obviously there is something I am missing. That is where I would like to start. I thought as long as I can not get the original backup to restore....then I do not understand enough to continue on the journey. Hence to post requesting assistance.
Can also do a factory reset and reformat /data and /cache RFS partitions.
Click to expand...
Click to collapse
I am not exactly sure what you mean here. Once I flashed the Stock RFS Samsung/Bell Canada ROM back via ODIN in some cases it would not boot. It was in a boot loop stuck on the Samsung logo. I went into normal recovery mode (Not CWM recovery mode since I did not reinstall it yet at that point) and I would perform the Wipe Data and Wipe Cache functions within recovery to get it out of the boot loop. I always made sure the OS fully loaded and functioned before moving to the next step of what I was trying to do. It was at that point I would install CWM again and then find out the original backup I took would not restore with the same error (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!).
In most situations you would want to go back to a stock ROM and kernel, but keep the CWM recovery, that's relatively easy to do with an RFS-compatible CWM and a nandroid backup. Even a non-RFS compatible CWM could be made to work with appropriate images and the (ADB shell) dd command.
Click to expand...
Click to collapse
I read a bit about this but I did not completely understand it. Is there a thread you can point me to in regard to this? Ultimately the goal is just to be able to restore to stock (or stock converted to EXT4 with a custom "close to original" kernel like CF-Root) if and when I want to in the easiest fashion.
But back to the question: going back to a completely stock, out-of-the-box phone from CWM, stock recovery, CSC and all?
I've thought about it for a few minutes, and it might just be possible to do. Neat? Kinda. Worth the trouble? Meh.
Click to expand...
Click to collapse
Yes I can understand that it is a bit of an odd request and not one that many would really be that interested in...but I am simply from the point of view of just seeing if it is possible. Once I get something in my head I want to prove or disprove it is possible. But I need knowledgeable people like you to offer suggestions and share past experience. I do not mind performing the work....I just need some help from time to time. I have been employed in the IT field for over 15 years but I am more of Windows guys.... but I am not afraid to play with anything and learn. Please do not bash me on the Windows/Microsoft thing....it pays the bills.
Again the goal is to keep everything within CWM so that you do not really need to go back to a computer. It might take some work and effort to get there though. I am not sure who else would be interested but it then could be shared with the masses on this forum. Again not sure of the value to everyone.
It would involve dd-ing RFS-format /system, /data and /cache partitions, boot.img and recovery.img, into place
Click to expand...
Click to collapse
GREAT!!!...I am game to try it. Again if you have a post of step by step on how to achieve this it would be appreciated. I believe I saw a post of yours when I was performing my research about this but it may not be exact for what we are trying to accomplish here. Perhaps it is though.
The part I'm not sure about is how to go about extracting CSC.rfs in the proper location and issuing a reboot recovery command at the end of the script, which should kick stock recovery into gear and apply CSC.
Click to expand...
Click to collapse
Well based on the posts I have read on your dissection of the partitions on the GT-S5660, you are one of the great resources to assist on this. I noticed that the CSC.rfs in not in your GT-S5660M_MUGKG3_stock_rooted_ROM but it was included in the S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3_home from samsmobile. So I am not sure where that version came from if it was leaked or what. I would guess that my original Out-of-Box CSC.rfs has been overwritten by the S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3_home version if there happen to be any differences. My wife's phone is still available so I could still extract the original file from her phone. Maybe that would not help though....I am not really sure what is contained in the CSC.rfs if it is phone, ROM specific...etc.
Anyway regardless I appreciate the time anyone has put in reading or thinking about my post. Again thank you for your time and effort. This is really a great forum full of great information.
ps. How much do I dislike the ReCaptcha spam blocker when trying to post? Very much!!!....you have to hit refresh about 100 times before you can actually make out some words you can type.....FAIL. I see it on numerous sites....really annoying...I like the pattern based ones that you put together way better.

NOTE:​Do with your own risk. I plan to do it myself soon, but be careful...​
Click to expand...
Click to collapse
You first. You seem to have more experience. Ha!!!. Kinda joking but also kinda serious. I guess I am still a noob so I would be leery to try this. I always have the fear of the bricking.

LOL I admire you for your long list of explanations. As well as Darkshado's posts.
Let's backtrack shall we?
The reason it gave you "error while formatting /system" is because CWM doesn't support converting the filesystem back to RFS. At least that's what I know. But for ODIN, you can do this fine. The thing about ODIN, is that it includes the base RFS files and doesn't come with other RFS partitions because it assumes your phone is already RFS
Hmmm I don't know any reason to go back to Stock RFS if you have already converted your partitions into a far more superior filesystem --> EXT4. Darkshado has his own custom ROM that has these specifications
A CF-Root kernel is a kernel that includes root. So when you flash the kernel, it also gives you root and possibly busybox.
Busybox is a series of UNIX tools for Linux and derivatives (Android) to use in the Terminal.
Hehe. It's fine if you're getting paid at IT, or doing IT, dunno which one.. But if you wanna learn more about Android and whatever stuff about it, that's great! It's a nice place to start. Then make your way towards linux.
Linux Distros (Distributions):
Ubuntu = Newbies
Debian = Ubuntu based on this
Fedora = Productivity
Linux Mint 12/13 = Ease of Use
Arch Linux =Advanced
BackTrack = Hacking/Cracking
Tails = Security
Bohdi = Speed
SliTaz = Small & For old hardware + Nice UI
(Just giving you tips here, if you do wanna do this )
Be careful if you're dd'ing your data, cache, system, stl, bml, etc..
Because there is a chance of bricking your device. I know dd'ing stl5 has a high chance that you'll brick your device.
The CSC contains all the info about your carrier, and some other stuff... Lol
Yes I hate the 5 minute waiting period to post a reply or thread, and i hate the captcha..
Sent from my BlackBerry PlayBook

Let's backtrack shall we?
Click to expand...
Click to collapse
Fine by me.
The reason it gave you "error while formatting /system" is because CWM doesn't support converting the filesystem back to RFS. At least that's what I know. But for ODIN, you can do this fine. The thing about ODIN, is that it includes the base RFS files and doesn't come with other RFS partitions because it assumes your phone is already RFS
Click to expand...
Click to collapse
Okay I understand that. However when I made my first backup via CWM the system was stock with RFS. When I restored back to stock ROM after playing with custom ROMs with EXT4 filesystem, the system was back to RFS right? Therefore how come the original restore would not work when the filesystem of the stock rom was back to RFS. That is where I am struggling. Is there an easy way to confirm you are on RFS vs EXT4 from within CWM? Or does ODIN have the ability to restore the RFS Stock version back to a EXT4 formatted phone. I assumed it converts the system back to RFS during the flashing. Is that an incorrect assumption?
Hmmm I don't know any reason to go back to Stock RFS if you have already converted your partitions into a far more superior filesystem --> EXT4. Darkshado has his own custom ROM that has these specifications
Click to expand...
Click to collapse
I guess I have not spent the time to really check out every single Custom ROM. So are you saying Darkshado's ROM is Gingerbread based with EXT4? I agree I would like to stay with EXT4 over all as I understand it is superior and that even Samsung has finally moved to it for its Stock ROMs on newer phones. Really I just want the stock image converted to EXT4 and the ability to restore to that EXT4 based version of the stock ROM via CWM.
A CF-Root kernel is a kernel that includes root. So when you flash the kernel, it also gives you root and possibly busybox.
Click to expand...
Click to collapse
I also understand that CF-Root supports EXT4 and is supposed to be the closest to the original Samsung based kernel.
Hehe. It's fine if you're getting paid at IT, or doing IT, dunno which one.. But if you wanna learn more about Android and whatever stuff about it, that's great! It's a nice place to start. Then make your way towards linux.
Linux Distros (Distributions):
Ubuntu = Newbies
Debian = Ubuntu based on this
Fedora = Productivity
Linux Mint 12/13 = Ease of Use
Arch Linux =Advanced
BackTrack = Hacking/Cracking
Tails = Security
Bohdi = Speed
SliTaz = Small & For old hardware + Nice UI
(Just giving you tips here, if you do wanna do this )
Click to expand...
Click to collapse
To be more clear I am employed in the IT field/profession..however you want to describe it...for the past 15 years. More of a Windows Server Administrator position and previous to that various other positions starting in client support. I have played with Ubuntu before and I have used bootable versions of Knoppix and other linux based distros in the past. I just do not use them enough on a regular basis. It is more of a time issue than anything. Arch Linux looks interesting to me. Perhaps enough to try. I appreciate the tips. Regardless playing with the phone is fun for me for now. I have an iPhone as well but I love the flexibility and NON closed ecosystem that android offers. I guess ultimately both are based on Unix/Linux based OSs.
Be careful if you're dd'ing your data, cache, system, stl, bml, etc..
Because there is a chance of bricking your device. I know dd'ing stl5 has a high chance that you'll brick your device.
Click to expand...
Click to collapse
That is exactly why I am asking for step by step. It is really not worth it to me if the potential of bricking is high. I am interesting in playing and learning but not at the stake of losing the cash I put in to play with the phone.
The CSC contains all the info about your carrier, and some other stuff... Lol
Click to expand...
Click to collapse
I figured based on what I read in Darkshado partition mapping post that CSC has the carrier content. Really then that does not seem that important if the carrier is the main part of it to consider it for restoration. Again unless there is other items in there I should be concerned about.
Yes I hate the 5 minute waiting period to post a reply or thread, and i hate the captcha..
Click to expand...
Click to collapse
Well that is 2 votes. Moderators please consider another spam deterrent. Ha!!!

AvrX said:
Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
Well it appears that CWM 5.0.2.7 may have been one of my issues in getting my original backup to restore.
I loaded CWM 5.0.2.6 from the following thread http://forum.xda-developers.com/showthread.php?t=1493932 and I was able to restore my original backup of the stock ROM with no issues. Thanks again Peteragent5 for putting that great post together.
Also a thank you AvrX for that for the suggestion of going back to 5.02.6. Also Darkshado's guidance of sticking with a CWM that supports one file system or the other.
I downloaded and installed the second version of 5.0.2.6 indicated in the 1st post of the thread named S5660M_cwm-5.0.2.6_feb_26_12.zip. Not sure if that is correct or not Peteragent5 as I not totally understanding the difference between Phiexz & Maclaw Roms and My ROMs in your post. I would assume you are speaking of the Custom ROMS created by Phiexz & Maclaw vs ones created by you? Regardless it would be nice to have a bit greater detail so I am confident in which tool to use in which situation.
So question 1 from my original post in this thread has been solved. Well sort of. Still not clear why 5.0.2.7 supports both RFS and EXT4 but it seems like all the functions for formatting are EXT4 based within it. Although the backup I made within it still shows the rfs prior to the *.tar extension.

Based on my last post I have a few new questions. After performing some more testing (trial by fire/trial and error) with CWM I am not sure that I really understand the support of CWM 5.0.2.7 RFS and EXT4 file system as mentioned in my last post.
Typically before I perform a backup of a ROM (in this case the stock ROM which is RFS filesystem based) I perform the following procedure in CWM regardless of the version of CWM
1. wipe data/factory reset
2. wipe cache partition
3. go to advanced menu
4. Wipe Dalvik Cache
5. Wipe Battery Stats
6. Main Menu -> backup and restore
7. Backup
Questions:
1. Is that the correct procedure? Could some steps be left out or added? What is the safest most reliable way? Should I even use those steps before I perform a backup or are they only really to be used when you are having problems? These are all really the same question presented in different ways.
2. If I am using CWM 5.0.2.7 (supports both RFS and EFS) and I perform the wipe data/factory reset, I see that it is Formatting /data /cache /sd-ext etc on the screen. Also with the wipe cache partition option I see Formatting /cache displayed on the screen. When using these functions in CWM 5.0.2.7 does this format the phone for those partitions from RFS to EXT4?
I am beginning to agree with Darkshado's comment
Different builds of CWM are available for the Gio. Some support RFS, others ext4. I'd rather avoid those with dual support as they're not very clear regarding what format they're using for which operation.
Click to expand...
Click to collapse
However if anyone else has done some extensive testing and know the answer to this....then I can move on and stop using tools. I believe that some of the tools are suppose to work and perform a certain operation but do the opposite or not what is claimed or do not explain the functions well enough for me to understand what operation does what. I want to understand....not just do.
The reason I am asking is that when I try to run a restore of an RFS (stock ROM) backup that was preformed in CWM 5.0.2.6 (only RFS supported) or a backup from CWM 5.0.2.7 (supports RFS and EXT4) after performing the above procedures within CWM 5.0.2.7, it always fails with the
dreaded (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) error. This is of course after flashing via Odin back to the stock RFS based ROM GT-S5660M_BMC_S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3 from sammobile.com and then entering stock recovery mode and installing CWM 5.0.2.7.
Does CWM 5.0.2.7 change the stock Kernel on my phone to one that supports RFS and EXT4? My assumption is yes but it would be nice to know for sure.
Based on my testing and findings so far I can tell right now that 5.0.2.7 is more EXT4 based then RFS. It will read RFS files and install on an RFS based filesystem (Stock ROM) and it will even make good backups of the RFS system. However it will not restore those RFS backups regardless if they were made in CWM 5.0.2.6 or CWM 5.0.2.7. Now if you flash back to stock ROM again via ODIN and install CWM 5.0.2.6 only RFS supported, you can restore backups of RFS based file systems backups( on a stock ROM system) made in either CWM 5.0.2.6 or CWM 5.0.2.7.
So the verdict is again (finding out the hard way)....DarkShado and AvrX are indeed correct. Use CWM 5.0.2.6 for backups and restores of Stock ROM.
For custom ROMs...which are predominantly EXT4 based now...I guess you need to use 5.0.2.7....but I will use the soley EXT4 based one from now on as the RFS & EXT4 based one I believe is limited. The only thing is if you install the 5.0.2.7 EXT4 only supported version, you will need to use the EXT4 Formatter (installed via CWM) before to make everything work properly before playing with EXT4 based Custom ROMs. Unless EXT4 formatting is built into the installer like it is with enhanced236_06.08.2012.
Morale of the story is again Darkshado is correct in what he was implying....what I am trying to accomplish is "Neat?" "Worth the Trouble"....My answer now...is a "NO".
None of the current versions of CWM "Fully" (read and write) support RFS and EXT4 at the same time and allow you to return to the stock based RFS backup plus play with EXT4 based new Custom ROMs. I know about the EXT4 Formatter....does anyone know of RFS Formatter tool that installable via CWM?
That tool might accomplish what I would like to achieve. Then it really is only a matter of the procedure to follow to make it all work within CWM. Just have to switch between CWM 5.0.2.6 and CWM 5.0.2.7.
Thanks for following the thread and reading my "trial and error" findings. I may perform a summary of my current findings in this post. It would be be a reply to my questions in the first post with the answer to my own questions. However I think I will wait to see if anyone is interested in providing any further comments.

modem issues after flashing anything other than stock
I am facing a similar issue to you TrippleRipple.
Sorry for the lengthy back story..but here it goes;
I am in Saskatchewan on Sasktel and I had originally given this phone to my son flashed with CM9 as a cheap android media and games device...but the screen on my SGS2 broke the other day and my son offered to "rent" his to me to use until my screen replacement comes in. When I put my SIM in the device (unlocked by retrieving code via ADB) it can connect to some providers in the area (Rogers)...but not to my home network of Sasktel. I read in a previous thread here on XDA that there is an issue with the baseband of custom firmware and that you should keep your stock modem for Bell/Telus handsets (Sasktel also falls in that category)....and so..I am trying to completely restore stock FW...to be able to connect to my home network.
Did you/do you have this modem issue as well?

kid___icarus said:
I am facing a similar issue to you TrippleRipple.
Sorry for the lengthy back story..but here it goes;
I am in Saskatchewan on Sasktel and I had originally given this phone to my son flashed with CM9 as a cheap android media and games device...but the screen on my SGS2 broke the other day and my son offered to "rent" his to me to use until my screen replacement comes in. When I put my SIM in the device (unlocked by retrieving code via ADB) it can connect to some providers in the area (Rogers)...but not to my home network of Sasktel. I read in a previous thread here on XDA that there is an issue with the baseband of custom firmware and that you should keep your stock modem for Bell/Telus handsets (Sasktel also falls in that category)....and so..I am trying to completely restore stock FW...to be able to connect to my home network.
Did you/do you have this modem issue as well?
Click to expand...
Click to collapse
To be honest, I have only really been playing with the custom ROMs but not really using them with an active SIM. So unfortunately I am not the best point of reference. I do know the stock firmware on sammobile does have the correct baseband in it as I copied down all of the details of the original out of box rom and it was the same once restored with the stock firmware from sammobile via odin. However with the out of box stock rom, there were issues with texting on SaskTel. You might want to try the enhanced236 ROM. That seemed to work fine on SaskTel with texting as well. However you should of course backup what you have now with CWM so that you can restore it back for your son when you get your other phone back.
I have not tried CM9 with the SIM chip...only with enhanced236. I did however play with CM9 and CM10. Sorry I could not have been of more assistance. Good luck.

[LINK][ROM][ODIN][TAR]SPH-D710VMUB GB28 (GB28 Modem/Kernel/ROM - Root/Stock)

VIRGIN MOBILE ONLY
Credits
Thanks go to the following:
- sfhub for many hints on how to do this - I'm just trying to help fill in while he's away.
- sextape for GB27 leak used to help make full restore
- rwilco12 for advice and hosting
- rainmotorsports, dev-host for hosting
- Forum Members for their support and hopefully feedback on these builds!
Make sure you give them any thanks for this build - they did far more than I on this! :highfive:
sfhub said:
You may have heard... the zerglings fought a noble battle against the samdroids and held their own for many battles, but were finally defeated on the EL13 battleground. Starting with EL13 the zergrush exploit is plugged. Do not fear, as the zerglings have enlisted their old ally Odin to fight the next battle for them.
Click to expand...
Click to collapse
This is the GB28 Kies Release with GB27 restore components added to make a full restore.
Stock restores will still behave as official.
Since most people are familiar with sfhub's format I'm going to include it here.
Again thank him for the LARGE amounts of time that he put into these posts.
NOTICE
This is expected to be the final official release for this device.
A big thanks for all of the leaks we have seen and the info that we get even when one doesn't leak.
-----------------------------------------------------------------------------------------------------------------------------------
This will NOT trigger the Yellow Triangle NOR will it increment the ODIN flash count.
This does NOT have the issue with the USB jig being disabled.
There are two versions provided, a FULL Restore that resets your whole phone, similar to a factory restore, and a No Data Restore, which is the same, except it preserves your User Data. The NoData version is only suggested if you are upgrading or remaining at the same version.
(Sorry, No Image, forgot to get one!)
Instructions - (No Video Yet)
0) Backup anything important and Disable any PINs
This process will restore you to factory software. All your Android data will be reset.
To be safe, it is best to archive your backup off your phone, ie on your PC or dropbox.
Note #1: Please DISABLE any PIN code you may have created to protect your phone. As a security measure, after the flash, Android will ask you for your PIN, if you have one enabled. It is simpler to have no PIN active. If you forgot your PIN then, after the factory restore, just enter the wrong PIN a few times and it will warn you. Enter the wrong PIN again and it will reset the filesystem.
1) Install Samsung USB/Android drivers (if necessary) [USB/Android]
2) Download the GB28 One-Click self-extractor of choice from our mirror:
[ROM][ODIN][TAR]SPH-D710VMUB GB28 (GB28 Modem/Kernel/ROM - Root/Stock) (Rwilco12 Android Forums)
Mac/Linux - Install 7-zip, then use it to unpack the individual ODIN components in Reference Section B (below). If Heimdall fails flashing all 3 files together, try doing them individually. Skip the remaining instructions that are windows specific (steps 3, 4, 6).
Android - Install ZArchiver, then use it to unpack the ODIN OneClick 7zip self-extractor file in this section (long press *-oc-sfx.exe, Open as archive, Odin-OC, select *-OneClick.exe, Extract). Use Mobile ODIN to Open File the resulting *-OneClick.exe file. Mobile ODIN issue - modem might not flash consistently. Skip the remaining instructions that are windows ODIN specific (steps 3, 4, 5, 6).
3) Extract the package
double-click on the self-extractor file, specify the directory to extract to (instructions assume C:\)
4) Start ODIN One-Click
Note #1: On Vista or newer, you may need to right-click on the file and Run as Administrator.
5) Place phone in ODIN download mode
Code:
[B][U]Method #1[/U][/B]
Power down phone
Wait for capacitative button [B]lights to turn off[/B]
Simultaneously [B]Press and Hold [Power] [VolDn][/B] until confirmation screen appears
Press [B][VolUp][/B] to enter Download mode
Code:
[B][U]Method #2[/U][/B]
adb reboot download
Code:
Connect USB cable to PC if not already connected
ODIN should show yellow COM port in 2nd column
Note #2: If you do not see a yellow COM port, you may need to run the ODIN One-Click as Administrator and/or unplug/plugin the USB cable after starting ODIN One-Click.
6) Start ODIN flash process
Press [Start]
7) Complete - PASS!
When complete you should see a screen similar to what is shown at top of post
Phone will automatically reboot
Status should change to green PASS!
Boot process will be slightly longer than usual during which time you'll see the 4G logo screen.
CWM will be available via a built kernel or repack shortly. Be on lookout for a separate post.
If you need to clear NVRAM/Sprint data login info, perform a ##72786# reset from the Dialer and enter MSL.
Type getprop ril.MSL in adb shell or terminal to retrieve your MSL.
For NoData install:
- If you are getting random force closes, wipe cache/dalvik-cache
- If you have troubles with Android Market, clear data from
menu->applications->all->market->clear data
- If you have troubles booting into Android, perform factory reset in ICS using the ODIN OneClick Factory Reset tool.
---------------------------------------------------------------------------------------------------------------​
NOTE: All previous versions of one clicks posted by me will no longer be maintained.

Thanks so much for these!

Second!awesome work.
Sent from my SPH-D710 using Tapatalk 2

Why do I suspect everything could be an april fools joke today?

Sadly the joke's on me. I went on vacation and while gone the model info came out for the GS4 (Just posted details) and all 3 E4GTs got source and JB official. Boy did I miss a lot.

One clicks were bad. Sorry about that.
Md5s updated to reflect fixed one clicks. Should be all uploaded in an hr from this post.
Sent from my SPH-L900 using Tapatalk 2

Nice april fool joke
Sent from my SPH-D710 using xda premium

Hey is this for Virgin Mobile?
Just checking.
Pp. :beer::thumbup:
Sent from a bean shooting Epic Touch ......in your eye ....phone.

Task Manager does NOT work.
Hey, Everyone. I haven't found many flaws in this. The one flaw I did find (which is pretty crucial IMO) is that the Task Manager does not work. I have the JobManager.apk but it does not work. Perhaps they forgot to include the framework and/or libraries needed for the app to function? Anyone know a way to fix this? The task manager was how I kept my phone from dying, by clearing apps and RAM when the phone was not in use. Please let me know if anyone has a solution! Thanks.
---------- Post added at 02:13 PM ---------- Previous post was at 02:05 PM ----------
PanchoPlanet said:
Hey is this for Virgin Mobile?
Click to expand...
Click to collapse
Yes. GB28 is exclusively for Virgin. Everyone else has GB27.

ErikBush97 said:
Hey, Everyone. I haven't found many flaws in this. The one flaw I did find (which is pretty crucial IMO) is that the Task Manager does not work. I have the JobManager.apk but it does not work. Perhaps they forgot to include the framework and/or libraries needed for the app to function? Anyone know a way to fix this? The task manager was how I kept my phone from dying, by clearing apps and RAM when the phone was not in use. Please let me know if anyone has a solution! Thanks.
---------- Post added at 02:13 PM ---------- Previous post was at 02:05 PM ----------
Yes. GB28 is exclusively for Virgin. Everyone else has GB27.
Click to expand...
Click to collapse
Try these apps with homescreen shortcuts for added accessibility.
RAM Manager:http://db.tt/xHXAIp29
Task Manager:http://db.tt/C0L9uYeu
App Manager:http://db.tt/zL0BbU8a
Install with a file browser, place the icon in your app drawer onto your homescreen.
Team Rejectz

So.. It's says to go back to the stock kernel.. Anyone know if you can use a CWM based Kernel instead? Couldn't find one that works. I get Boot Loop.

ErikBush97 said:
So.. It's says to go back to the stock kernel.. Anyone know if you can use a CWM based Kernel instead? Couldn't find one that works. I get Boot Loop.
Click to expand...
Click to collapse
What are you using to flash the kernel? I have never gotten a bootloop from a kernel. Mobile Odin to flash .tar files, recovery to flash .zip files, and PC Odin to flash .exe files. Make sure you are flashing a GB27 kernel (it does not matter which carrier you are on for the kernel).
Here is one that has a custom recovery-http://forum.xda-developers.com/showthread.php?t=2244781
Team Rejectz

bilgerryan said:
What are you using to flash the kernel? I have never gotten a bootloop from a kernel. Mobile Odin to flash .tar files, recovery to flash .zip files, and PC Odin to flash .exe files. Make sure you are flashing a GB27 kernel (it does not matter which carrier you are on for the kernel).
Here is one that has a custom recovery-http://forum.xda-developers.com/showthread.php?t=2244781
Team Rejectz
Click to expand...
Click to collapse
I wasn't in boot loop, per say, but I got stuck on the first Samsung screen that appears as soon as the phone is powered on. Anyways.. I fixed that... BUT I switched to the S5 0.8 ROM by Venom earlier, and now I have a new problem (It's ALWAYS something...) The ROM is not rooted, and the only rooted FF18 kernels I could find, include the FF18 Kernel, Rom, and modem. So I have to choose between this awesome ROM or Root. :/ Unless someone here knows how I can root the Venom S5 ROM without touching the ROM!

Thanks

THANKS

[Q] Rooted but need HELP with ROM & Recovery Plz!

Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!

Making progress but still confused...?
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
BrianN_Cols_OH said:
Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!
Click to expand...
Click to collapse

Success - Finally got CWM - Ready to play with ROMs
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
BrianN_Cols_OH said:
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
Click to expand...
Click to collapse

BrianN_Cols_OH said:
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
Click to expand...
Click to collapse
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.

More updates...
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
nikon120 said:
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.
Click to expand...
Click to collapse

New issues - need help with CM 10.1...
OK, I've made progress and learned a lot. Essentially restored the bricked phone by going back to stock. Then, I started my process again.
- Used ODIN to flash rooted kernel with CM 5.0.2.7
- Flashed Cyanogenmod 10.1.3
- Flashed correct Gapps (dated 8/12 I think)
Software great, but modem not working. So, then I found the forum for the NS4G modem patches. I've tried several and I did get one to work. But, the latest version of CM 10.1 has SU built-in. When I do the modem repair, it breaks my SU root.
I've tried the nitest kernal (by the way, I like the TWRP recovery better than CM - it). I've tried several of the modem patches.
Do I need to go back to a certain stable version of CM 10? What order to I need to apply things?
Here's what I have on the phone at the moment. It has SU/root but no modem.
- Android 4.2.2
- 3.0.79-JB42-nitest-nr kernel
- CM 10.1-20130526-NIGHTLY-epicmtd (although I've tried several other builds)
I was sooooooo close. Please help? How do I get my modem working AND keep my SU/root?
BrianN_Cols_OH said:
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
Click to expand...
Click to collapse

ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.

Modem issues...
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
nikon120 said:
ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.
Click to expand...
Click to collapse

More info...
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
BrianN_Cols_OH said:
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
Click to expand...
Click to collapse

Modem.bin
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse

BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
BrianN_Cols_OH said:
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
Click to expand...
Click to collapse
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4

Thanks!
Great, thanks so much. I will look for the modem files a little later.
nikon120 said:
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse

BrianN_Cols_OH said:
Great, thanks so much. I will look for the modem files a little later.
Click to expand...
Click to collapse
Ok, all Epic modems and NS4G modems are reuploaded. I also included the swap files for each. Everything with (Flashable) means to be flashed within recovery. Those swap files are the blob changes I mentioned earlier. This way you can swap modems using recovery, rather than relying on Odin.
Everything in the Odin folder can be placed in the phone slot and flashed as-is. (No need to extract the .bin file from the archive.)
As for the built-in root manager in CM, I'd try reflashing the rom first, and then messing with the modem.

[05-15-17] Debloated-Deodexed-Rooted N910PVPS4DQC1

Attention! I've just noticed some activity here. Thanks to all the members for answering questions.
I haven't had this sprint device for awhile now so I don't keep track of this thread so much. For those of you needing help with gsm support, I'll try to offer assistance, since that's how I always used this device. I'll try to post a universal gsm fix script that'll modify any CDMA rom to work with gsm! Thanks!
DeBloated, DeOdexed N910PVPS4DQC1​Now with Rom Control! ​GSM ROM! (See Post 2)​
First Off About Me:
First off, Let me state, I'm a full-time construction worker and also a full-time Dad. I'm not a Dev, like the peeps I learned from. So don't expect this Rom to get massive updates or often updates. I no longer have a N910P, so this might be it for me!
About ROM
Warning: This ROM is ONLY for the Sprint SM-N910P!!! DO NOT FLASH THIS ROM ON ANY OTHER MODEL!!! If you do then you are on your own! Know what you are doing before flashing and modifying your phone!!! You have been Warned!! I am not responsible for your phone breaking or blowing up!!
This Rom is a debloated, deodexed, slightly modded Stock Rom! It is pre-rooted! And I removed a handful of non essential apps. Plus I added a handful of mods!
I really wanted to add some more useful apps and a custom aroma installer but just wanted to get this out for the people asking for it. Hope you like the debloat and included mods.
Version: 1.0
This is based on stock with some custom mods!
Fully deodexed framework and system apps
Debloated-Deodexed-Rooted
Basic Mods (Power menu, hotspot, etc)
Added a few useful apps!
Su.d support
Removed Knox
Removed ItsOn
Zip-Aligned
Slightly Modded Stock Kernel
Software Base version: N910PVPS4DQC1
Kernel Base: Official Samsung N910PVPS4DQC1
ROM Features
Mods added: CSC edits, Hotspot mod, Only Once/Always, All apps multi window, remove permanent notification, remove USB plug/unplug awake screen, removed high volume notice, added Advanced Power Menu.
Added app: YouTube adblock&background playback & AdAway!
Changelog
v1.0 - Released 05/15/2017
ADD-ON Features!
Rom Control by @ROBERT CM !
Flashing instructions:
Before you flash this rom you should be on the N910PVPS4DQC1 firmware. Specifically the bootloader and modem. (Uploading Now)
Heres QC1 firmware for anyone needing!
Full ROM - https://www.androidfilehost.com/?fid=529152257862726726
Firmware / Modem - https://forum.xda-developers.com/showpost.php?p=72341335&postcount=16
***Before you flash this rom, please make sure your battery has at least 30% charge***​
OK... Lets begin!
1. Download the rom and all the other mods you want!
2. Check the MD5!!! Use a MD5 checksum tool on your pc or phone (Google is your friend)
3. Copy the downloaded files to your phone's internal storage or micro-sd card
4. Backup anything you need to backup from your internal storage and copy it to your pc or sd-card
5. Reboot to TWRP custom recovery. Do "Advanced Wipe" options and wipe Dalvick-Cache, System, Data, and Cache. I also advise deleting /Android directory from Internal storage and SD card!
6. Install the rom!
7. REBOOT!!
8. The initial boot process will take around 12 minutes. Please be patient. It WILL boot. The phone might reboot once from SuperSU.
9. Once you reach the setup wizard proceed as usual and setup your phone.
10. Once phone is setup, Now Install Rom Control!
11. You're done! Enjoy!!
Credits
Without the following people NONE of this would be possible. Period.
In no particular order!
@SuperR. for his awesome kitchen, @Chainfire for root and SuperSU, @iBotPeaches for apktool, @JesusFreke for smali/baksmali tools, and @asc1977 & @edzamber & @tdunham for all their amazing collection of guides!
Also @tx_dbs_tx, @carlosggb, @SaintZ93, @hsbadr, @osm0sis, @freeza, @ianmb, @LMMT, @samep, and @wantedman76 for all their work that I've learned much from! And SO Many more here at XDA!
Thank You All !!​
DOWNLOADS
Fixed Zip Uploaded!!!
DeBloated, DeOdexed N910PVPS4DQC1-Fixed
MD5: 617f196041c2d8c9a330d783438cf0f8
GSM Rom! See Post 2
MODS
Rom Control
See Post 3!
Contribited By: aaron74
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N910PVPS4DQC1_N910PSPT4DQC1_N910PVPS4DQC1_HOME
Based On: Stock N910PVPS4DQC1
Created 05-15-2017

GSM ROM!
Gsm Rom:
Fyi, If your using this phone for gsm, I found its just easier and better to install a Tmobile rom. I don't believe you need a data fix with it. (Sorry it's been awhile). Never use a tmobile odin firmware though!
You can also install any other international rom but you will need a data fix and kernel!
https://mega.nz/#!t510lCoI!qqK8Wr-ttM5VJvAG8zo86KldSW7_2tMNUlxM_zQRuX8
Gsm fix patch from old rom: (Not needed for above rom! Only to flash over sprint rom in post 1)
https://forum.xda-developers.com/attachment.php?attachmentid=4134974&d=1493690641
Thread: https://forum.xda-developers.com/showpost.php?p=71301823&postcount=2

Rom control!
A great Dev @ROBERT CM made a Rom Control for our stock roms.
Goto his Thread below to Download and don't forget to Thank him and leave him a reply!
Here's his Main Thread!
You must Download both zips and flash consecutively.
Setup Rom first!, before flashing!
Thank you, & Enjoy!

Just in case!

Magnifiquè!!!!

Thanks for this!
Sent from my SM-N920P using Tapatalk

Excellent! Thank you!
Sent from my SM-N920P using Tapatalk

Please let me know if any problems! I usually never post unless i personally flash. But this time, i couldn't flash. I didnt do anything crazy, so all should be fine! But please let me know.

aaron74 said:
A great Dev @ROBERT CM made a Rom Control for our stock roms.
Goto his Thread below to Download and don't forget to Thank him and leave him a reply!
Here's his Main Thread!
Thank you, & Enjoy!
Click to expand...
Click to collapse
This weekend update my rom control and mods
I trying adapted more mods for n4 stock
This motivate me a development and keep it up and I know what more more persons and devs enjoy of this mod :laugh:

​
ROBERT CM said:
This weekend update my rom control and mods
I trying adapted more mods for n4 stock
This motivate me a development and keep it up and I know what more more persons and devs enjoy of this mod :laugh:
Click to expand...
Click to collapse
Thanks bro. I know the note 4 is dying out with devs. So it's always nice to have people keeping us alive. Take your time bro, i know how it is!

I flashed, and this is what I came encountered:
I was not rooted, so I Odin flashed TWRP, wiped everything but SD Card (Deleted SD Card Android folder) and flashed ROM followed by Rom Control 1, then 1.1.
First thing I noticed is that the top bar (not sure of its proper name) was missing, and when I swiped down, nothing happens. So, I cannot see any type of activity (i.e. new email icons, new text messages icons, notices, etc..). With that, I could not see my battery level, time, date, etc...
Second, I did not have root. I flashed SuperSU via twrp and still did not have root.
Third, when pressing the Power button to awake the device, it takes a few seconds to turn on. At first, I thought it wasn't turning on, so I kept pressing the power button... so the phone screen would not turn on. I eventually found out that I needed to wait a few seconds after pressing it the first time.
Fourth, pressing the "Recent" app button does nothing.
At this point, I think I am going to re-flash but without ROM control to see if these problems still exist. I'll report back.

Aloupha said:
I flashed, and this is what I came encountered:
I was not rooted, so I Odin flashed TWRP, wiped everything but SD Card (Deleted SD Card Android folder) and flashed ROM followed by Rom Control 1, then 1.1.
First thing I noticed is that the top bar (not sure of its proper name) was missing, and when I swiped down, nothing happens. So, I cannot see any type of activity (i.e. new email icons, new text messages icons, notices, etc..). With that, I could not see my battery level, time, date, etc...
Second, I did not have root. I flashed SuperSU via twrp and still did not have root.
Third, when pressing the Power button to awake the device, it takes a few seconds to turn on. At first, I thought it wasn't turning on, so I kept pressing the power button... so the phone screen would not turn on. I eventually found out that I needed to wait a few seconds after pressing it the first time.
Fourth, pressing the "Recent" app button does nothing.
At this point, I think I am going to re-flash but without ROM control to see if these problems still exist. I'll report back.
Click to expand...
Click to collapse
Yes, i had that problem with Rom Control once but it was on a N7 port rom.
When i last tested this rom control with stock. It worked but i also already had the rom up and running. I wonder if that has anything to do with it.
Thanks for reporting. Please let me know how just my rom works without it.

aaron74 said:
Yes, i had that problem with Rom Control once but it was on a N7 port rom.
When i last tested this rom control with stock. It worked but i also already had the rom up and running. I wonder if that has anything to do with it.
Thanks for reporting. Please let me know how just my rom works without it.
Click to expand...
Click to collapse
I just re-flashed. Other than root, all the other issues are gone.

Aloupha said:
I just re-flashed. Other than root, all the other issues are gone.
Click to expand...
Click to collapse
You have no root?
I'll have to pull file and check. I must have rushed.
Thanks for letting me know.
Also check the SU Hide app? Maybe that's messing it up. I've never used it before but included it, as some are interested in it.

aaron74 said:
You have no root?
I'll have to pull file and check. I must have rushed.
Thanks for letting me know.
Also check the SU Hide app? Maybe that's messing it up. I've never used it before but included it, as some are interested in it.
Click to expand...
Click to collapse
@aaron74 can you please provide ODIN files for only modem and bootloader
My internet connection is slow here
Thank you

natibongo said:
@aaron74 can you please provide ODIN files for only modem and bootloader
My internet connection is slow here
Thank you
Click to expand...
Click to collapse
Warning!! I am not Responsible for Brick!!!!
This is the first time I made a firmware and modem package!! Maybe someone can verify my commands below, before trying to Flash!!
Without going in detail, Heres my commands, If anyone wants to verify anything wrong!!
tar -H ustar -c modem.bin NON-HLOS.bin > modem.tar
tar -H ustar -c aboot.mbn sbl1.mbn sdi.mbn tz.mbn rpm.mbn > firmware.tar
md5sum -t my-file.tar >> my-file.tar
mv my-file.tar my-file.tar.md5
But Here you GO! For all who are UnAfraid!!
N910P-QC1-Firmware
N910P-QC1-Modem

Aloupha said:
I just re-flashed. Other than root, all the other issues are gone.
Click to expand...
Click to collapse
For anyone reading this,
I just verified results, Yes we must not flash rom and rom control at same time. Or no status bar.
Flash Rom, reboot, setup. Then flash Rom control.
All good! Reboot will take a bit, dalvik gets cleared.

aaron74 said:
Warning!! I am not Responsible for Brick!!!!
This is the first time I made a firmware and modem package!! Maybe someone can verify my commands below, before trying to Flash!!
Without going in detail, Heres my commands, If anyone wants to verify anything wrong!!
tar -H ustar -c modem.bin NON-HLOS.bin > modem.tar
tar -H ustar -c aboot.mbn sbl1.mbn sdi.mbn tz.mbn rpm.mbn > firmware.tar
md5sum -t my-file.tar >> my-file.tar
mv my-file.tar my-file.tar.md5
But Here you GO! For all who are UnAfraid!!
N910P-QC1-Firmware
N910P-QC1-Modem
Click to expand...
Click to collapse
Which download is bootloader?

reekotubbs said:
Which download is bootloader?
Click to expand...
Click to collapse
Firmware=bootloader.
Sent from my SM-N920P using Tapatalk

What about the root issue, did you get to the bottom of it?