Related
Base On stock otaJB4.1.1 JRO03D for Nexus7
Didnt sign this zip,before flash,check Ur reovery sign Verify switch off
Cause I'm chinese,sorry about my English
chinese user may go gfan,same post in chinese
=============Features/log=============
What's works：
Google Now (Seems offline voicedata not support nexus s now) only work in N7&GalaxyNexus
Every thing works.
=======================================
*1 deodex/zipalign
*2 busybox
*3 rooted by superSU(Chainfire)
*4 bettery% ，mostly like this
*5 Advanced Power Management (1reboot 2reboot to recovery ，long press recovery to BLmode)
*6 Camera join，works fine，(MODACO)
*7 Volume button wake up
*8 USBdebugging works fine
including full google services,but books/video/etc...not support my location,just download them from google play,that's easy
If anyone wanna disable the Nvbar,go check my app fullscreen toggle
This app madefor galaxy nexus,also support Nexus7
==========Download JB4.1.1 JRO03D =============
N7-Stock-OTA-rooted-deodex-zipaling-JRO03D.zip - 233.80 MB
Thanks for this. I'll give it a flash and let you know how it goes. Also, I think you're English is pretty good!:good:
Can I flash this ROM?
I unlock bootloader, flash clockworkmod and made root in my nexus 7, can I make OTA update to 4.1.1 or is better flash this rom in recovery clockworkmod?
What is the boot.img file?
My state is in the fallowing:
* BOOTLOADER *
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - 015d24a424042006
SIGNING - not defined yet
LOCK STATE - UNLOCKED
* SYSTEM *
Modelo: Nexus 7
Versão do Android: 4.1
Versão do Kernel: 3.1.10-g55edff4
Número da compilação: JRN84D
if. ota ,you need unroot first
Sent from my GT-P1000 using xda premium
What is the boot.img file?
What is the boot.img file?
kernel
Sent from my GT-P1000 using xda premium
Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!
Angst said:
Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!
Click to expand...
Click to collapse
I can't tell if you're trolling or don't know but the boot.img is the kernel. u wanna check? go look in the zip of the Trinity kernel b4 u flash.its boot.img..same with the Franco kernel or any other kernels.
examples of this can be seen with grub or lilo (linux bootloaders).
Hope this has cleared this up.
RED OR BLUE YOU CHOOSE !!!
Boot.img contains the kernel, believe the OP was just using that ad a shorthand explanation.
But the boot.img does indeed contain more than that. When unpacked it has all of the init.rc files and other essential system operations. If you build your own kernel, you can pack the boot.img and replace the kernel with your own newly made zimage.
<del>
Angst said:
Hold on here, PLEASE !!!
The boot.img is not the Kernel, they are very different and separate.
The boot.img contains the instruction set and fixed files the computers needs to start, bootup this then calls the kernel after it is done.
When you update a kernel you are NOT UPDATING THE boot.img unless the developer has included it in the package.
RED OR BLUE YOU CHOOSE !!!
Click to expand...
Click to collapse
Put the zImage from boot.img in your pipe.
This ROM won't even boot for me, which is really weird. Anybody else have that issue?
test on cwm6.1.0
Sent from my Galaxy Nexus using xda premium
Hello everybody!
Yesterday, I collected my previous recoveries, updated them and built a new one (TWRP) too. I made CWM-flashable and Odin-flashable packages too.
CWM v4.0.0.2: (Thanks to The-Droidster for the recovery! )
- This is the first ever custom recovery for the Galaxy R.
- It has all the nice CWM features.
- You can restore ICS with this.
- It has no known bugs. Everybody used it as a starting point.
- What I changed:
- Removed the /lib/modules directory. --> 0,1MB size decrease.
- Enabled button backlight.
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
CWM: http://www.mediafire.com/download.php?71ynk9btw7euocr
ODIN: http://www.mediafire.com/download.php?iczq8xed26ohakw
CWM v5.5.0.4:
- Built from the latest CM9 sources.
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Very stable!
- It has no known bugs yet (Lot of users have been using it and no bugs have been reported).
- Toggle feature is disabled! (I find it really annoying and it doesn't make real sense for a recovery to lock the screen.)
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
CWM: http://www.mediafire.com/download.php?98c1smq7nk4485d
ODIN: http://www.mediafire.com/download.php?c7qbjaqwgpnbr9w
CWM v6.0.3.2:
- Built from the latest CM10.1 sources.
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Key layout: Scrolling: Volume up+down, Selecting: Home key, Going Back: Power+Back button. (Menu key doesn't do anything.)
- Known issues: ADB Sideload
CWM: http://www.mediafire.com/download/7xyevjf32fixf3a/CWMv6.0.3.2_CWM.zip
ODIN: http://www.mediafire.com/download/oksv1o2hu63gohi/CWMv6.0.3.2_ODIN.tar
CWM v6.0.1.5 Touch:
- Built using the online builder at http://builder.clockworkmod.com
- It has all the nice CWM features.
- It can restore v4 backups (you can restore ICS with this too).
- Key layout: Scrolling up: Volume up or home button, Scrolling down: Volume down or menu button, Selecting: Power button, Going back: Back button. (This is the default layout and cannot be changed.)
- The touch responsiveness is a little lazy. You have to wait some seconds before it starts working. (The online builder says it needs an ICS kernel for the touch version. We use the CM10 kernel (based on stock ICS one), but it's still lazy.)
CWM: http://www.mediafire.com/download.php?jz24eugrrr988f2
ODIN: http://www.mediafire.com/download.php?6vju9tlf9byeufe
TWRP v2.5.0.0: (Thanks to 'cooleagle' for the tip! )
- Built from the latest TWRP and CM10.1 sources.
- It has a lot of nice features, more than CWM does.
(For example:
- on-screen keyboard -> custom backup names
- built-in file manager
- built-in terminal)
- It has a fully touch-driven and very intuitive interface.
- The touch responsiveness is a little lazy. You have to wait some seconds before it starts working. (The online builder says it needs an ICS kernel for the touch version. We use the CM10.1 kernel (based on stock ICS one), but it's still lazy.)
Note: Backups of TWRP are said not to be compatible with those of CWM. For everything to work well, I recommend that you create a TWRP backup too before modding.
CWM: http://www.mediafire.com/download/8ibammwrtwrwo3d/TWRPv2.5.0.0_CWM.zip
ODIN: http://www.mediafire.com/download/pjxp5xhi96gtbvb/TWRPv2.5.0.0_ODIN.tar
PhilZ v5.06.6: (Thanks to Tha TechnoCrat for the tip! )
- Built from the latest PhilZ and CM10.1 sources.
- It has a lot of nice features, more than CWM does. Check here: http://forum.xda-developers.com/showthread.php?t=2201860
- Based on CWMv6.0.3.2
- Known issues: ADB Sideload
CWM: http://www.mediafire.com/download/4qz1g86oncn4foq/PhilZv5.06.6_CWM.zip
ODIN: http://www.mediafire.com/download/ixlxkh87s2lxbp9/PhilZv5.06.6_ODIN.tar
Stock GB recovery (XWLA4): (Thanks to xlm13x for this! )
- Use this if you want to return to the stock version.
CWM: http://www.mediafire.com/download.php?di4e3ms3qrxuapy
ODIN: http://www.mediafire.com/download.php?i4a1t7ntavvguu7
Stock ICS recovery (XXLQ7): (Thanks to xlm13x for this! )
- Use this if you want to return to the stock version.
CWM: http://www.mediafire.com/download.php?kg58rxmlnxkpkqv
ODIN: http://www.mediafire.com/download.php?pjn87j4fyjs34vt
If you want to install a custom recovery for the first time, you always have to start with an Odin-flashable package first. Flashing a recovery with Odin doesn't increase the download counter!
Tutorial (Flashing with Odin):
Please refer to the following thread (This is very detailed and good in my opinion): http://forum.xda-developers.com/showthread.php?t=1406664
Choose a downloaded TAR file (ODIN-flashable) for PDA option.
Tutorial (Flashing with CWM):
Note: This only works if you have already flashed CWM with Odin.
1: Reboot into recovery mode. Do this with a custom rom or by powering on your phone and pushing Volume UP+Home button simultaneously while the Samsung boot logo appears (you have to be fast).
2: Select 'Install zip from sdcard' menu.
3: Select 'Choose zip from sdcard' menu (or if you want to flash something from your internal sdcard, select 'Choose zip from internal sdcard' menu.) Note: On CWM v4.0.0.2, there isn't any separate menu for internal sdcard. It shows internal sdcard by default. External sdcard is mounted under the external_sd folder on the internal sdcard.
4: Navigate to the file you want and choose it.
5: Choose 'yes'.
6: Wait for it to finish and you're done.
Changelog:
08 July 2012: Initial release of v5.5.0.4 in old thread
09 July 2012: Added CWMv6.0.0.0 Touch (alpha)
17 July 2012: Added CWMv6.0.0.3
18 August 2012: New thread (this) created. CWMv5.5.0.4, CWMv6.0.1.1, CWMv6.0.1.1 Touch and TWRPv2.2.1.4 added.
30 August 2012: Modified CWMv4.0.0.2 (touchkey backlight, some init tweaks and smaller image) added.
2 September 2012: Stock GB (XWLA4) and ICS (XXLQ7) recoveries added.
10 November 2012: CWMv4.0.0.2 and CWMv5.5.0.4 reuploaded. CWMv6.0.1.5, CWMv6.0.1.5 Touch and TWRPv2.3.1.1 with new CM10 kernel added.
14 June 2013: CWMv6.0.3.2 and TWRPv2.5.0.0 added
16 June 2013: CWMv6.0.3.2 and TWRPv2.5.0.0 with USB Mass Storage fix updated, PhilZv5.06.6 added
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!
Dude, you're awesome
Sent from my Galaxy Nexus using xda app-developers app
Man thanks. you are the one who making Galaxy R known to the world. thanks again:angel:
wow you are rocking buddy :good:, thank's a lot just now flashed TWRP and its rocking........
Hey guys, sorry for the links being disabled. I've just received a mail about it. Dropbox thinks the links are generating too much traffic. Thank you for downloading so much! I'll reupload everything to somewhere else asap.
Sent from my GT-I9103
Adam77Root said:
Hey guys, sorry for the links being disabled. I've just received a mail about it. Dropbox thinks the links are generating too much traffic. Thank you for downloading so much! I'll reupload everything to somewhere else asap.
Sent from my GT-I9103
Click to expand...
Click to collapse
Thats means u r world famous buddy.. Bt we are waiting.. If someone need that one then we will ask in PM.
Sent from my GT-I9103 using Tapatalk 2
I think this should be stickied!:good:
The-Droidster said:
I think this should be stickied!:good:
Click to expand...
Click to collapse
Me too :good:
Update the OP!
@Adam...Now that this thread has been stickied it is best that you also add the attached CWM recovery v4.0.0.2 to the OP. This will make it a one stop thread for all recoveries for Galaxy R. Also please include a short tut about flashing these recoveries through recovery and ODIN separately!(With screenies if possible!)
One more thing, the attached v4 CWM recovery is ODIN flashable. See if u can make a CWM flashable version out of it as you did for other recoveries!
Thnx:good:
The-Droidster said:
@Adam...Now that this thread has been stickied it is best that you also add the attached CWM recovery v4.0.0.2 to the OP. This will make it a one stop thread for all recoveries for Galaxy R. Also please include a short tut about flashing these recoveries through recovery and ODIN separately!(With screenies if possible!)
One more thing, the attached v4 CWM recovery is ODIN flashable. See if u can make a CWM flashable version out of it as you did for other recoveries!
Thnx:good:
Click to expand...
Click to collapse
Thanks for the idea! I'll do it on tuesday (I'll arrive home then.) as well as I'll reupload everything to somewhere else as Dropbox has limits with file downloads. I may also add a flashable stock recovery if somebody wants to revert only the recovery.
Sent from my GT-I9103
Adam77Root said:
Thanks for the idea! I'll do it on tuesday (I'll arrive home then.) as well as I'll reupload everything to somewhere else as Dropbox has limits with file downloads. I may also add a flashable stock recovery if somebody wants to revert only the recovery.
Sent from my GT-I9103
Click to expand...
Click to collapse
Along with the stock recoveries of ICS & GB CWM flashable zips kindly try to add a Unroot CWM zip (ICS / GB separate if needed) so that everyone can just flash that zip & get unrooted if in any circumstances they can't flash the stock ROM via a USB if the port is damaged. This will serve as a way for people who have damaged their USB port to get unrooted, flash stock recovery & claim warranty for the damaged USB port.
pankaj88 has already made one but it doesn't remove the busybox so if possible try to make a zip which removes all the traces of the a rooted stock ROM.
You could start a new thread for it if you think it's needed as it is pretty useful & important.
Cheers !
Adam Now we are having ICS, so is it possible to rectify the touch Recovery bug (little lazy for few seconds) please.....
oops sorry i haven't read the OP fully, Ok now i understood because of kernel size you are not able to do it.....
UPDATE:
I updated the links, added CWM v4.0.0.2 and a short tutorial.
I'll get stock GB and ICS recoveries and add them in the following days (It depends on when I get them.)
If u want I can send u stock recovery images.
Sent from my Galaxy Royale using Tapatalk 2.
xlm13x said:
If u want I can send u stock recovery images.
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
It'd be really great! I think a GB and an ICS one is enough. Thanks in advance!
ICS Stock Recovery: http://d-h.st/Zgw
(extracted from XXLQ7)
GB Stock Recovery: http://d-h.st/M1R
(extracted from XWLA4)
This is great since I need to repack the stock firmware with CWM now just to get rid of the emmc bug.
xlm13x said:
ICS Stock Recovery: http://d-h.st/Zgw
(extracted from XXLQ7)
GB Stock Recovery: http://d-h.st/M1R
(extracted from XWLA4)
Click to expand...
Click to collapse
Added them to the OP.
can we flash through stock recovery
Sent from my GT-I9103 using xda app-developers app
kartiknnn said:
can we flash through stock recovery
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
You cannot flash through stock recovery right now. Flash a one with Odin first, it'll not increase the binary counter.
Sent from my GT-I9103
DEODEXED/ODEXED DDMD1
You can use this ROM as base for your ROM, Just PM me with a link to the thread!
This is the "FULL ROM" not just the /app and /framework folder. :highfive:
Click to expand...
Click to collapse
FEATURES:
Latest Busybox (Completely Symlinked).
Latest Indian firmware.
Rooted with latest Superuser.
No scrolling bug (as in DDLK2).
Fully stock, no changes in UI.
Now works with any kernel.
Bugless & Rock Solid Stock Build.
The successor of DDLK2.
INCLUDED KERNEL DETAILS:
Latest DDMD1 Kernel
DOWNLOADS:
Deodexed DDMD1
Odexed DDMD1
Mod Edit: Link removed due to using pay per click's site Mirror - File Repository[/URL]
CREDITS:
Samsung
Evanlocked
SamFirmware
dsixda Kitchen
nolinuxnoparty
d3cka
zalzondabuzz
RiddlerA
SCREENSHOTS:
Lidroid Toggles:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Settings Mod:
Evolution X4 Statusbar:
4 Way Boot Menu:
ADDONS & PATCHES:
Swipe To Remove Notifications
All Kernel Fix (Call, IMEI, etc.) (MD5: 1EBAE85470D1ECF388A358241B1096A4)
Evolution X4 StatusUI
4 Way Boot Menu
Lidroid Toggles
Settings with embedded QuickPanel Options
For Deodex:
Rename to Settings.apk
Push to /system/app
Set permissions r w- r-- r--
Reboot!
For Odex:
Rename to Settings.apk
Push to /system/app
Remove Settings.odex from /system/app
Set permissions r w- r-- r--
Reboot!
INSTALLATION:
Newbies:
Flash DDMD1 Stock ROM via Odin.
Reboot in Recovery.
Flash Temporary CWM.
Wipe Data & Cache.
Flash ROM.
Advanced users:
Reboot into CWM.
Format system, cache and data.
Mount all partitions.
Flash ROM.
ADDITIONAL INFORMATION:
Know why you should "even" think of using the odexed version.
WHAT IS AN ODEX FILE?
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
HOW THIS WORKS
For the more geeky amongst us, Android OS uses a Java-based virtual machine for running applications, called the Dalvik Virtual Machine. A deodexed, or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK. An .odex file, on the other hand, is an optimized version of this same .dex file that is stored next to the APK as opposed to inside it. Android applies this technique by default to all the system applications.
Now, when an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages. Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
ADVANTAGES & DISADVANTAGES
The advantage of deodexing is in modification possibilities. This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first, since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times. However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used. Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Prevent this thread from dying.
Rate this thread ★★★★★
Press "Tip us?"
Press thanks
Post in this thread (I am not asking you to spam!)
Click to expand...
Click to collapse
At last.Deodexed version is up!
Please upload it Asap
No longer switching to old Stock ROM's because of GNU Kernel, Hells Fusion Kernel, etc. not working!
NOTE: The problem why DDMD1 was not so commonly used is that if you flash a custom kernel other than the one provided with this, then you can't call anyone and IMEI is not displayed.... That is due to some changes in new libs and it is now fixed by flashing the lib provided in OP.
NOTE: To fix all Call & IMEI Problem, you need to flash the above (posted in OP) fix!
NOTE: According to some reports, that although network problems are fixed with above patch, IMEI does not appear with custom kernels. This error should not have occurred if you have followed EXACT instructions as in OP.
Thread Changelogs:
CURRENT:
18-09-2013 WEDNESDAY
--------------------------------------
Added 4 Way Boot Menu to Addons.
OLD:
05-07-2013 FRIDAY
--------------------------------------
Added ODEXED | DEODEXED DDMD1 (no addons till now)
06-07-2013 SATURDAY
--------------------------------------
Added ADDONS - Lidroid Toggles, QuickPanel Settings, Swipe To Remove
08-07-2013 MONDAY
--------------------------------------
Removed Swipe 2 Remove. (Bootloop)
19-08-2013 MONDAY
--------------------------------------
Added Broadcom Radio Interface Layer fix.
boot.img
Do you guys have kernel of ddmd?
I need it for r&d.
CharsiBabu said:
Do you guys have kernel of ddmd?
I need it for r&d.
Click to expand...
Click to collapse
The above package also contains the DD MD1 kernel.
You may download and extract it.
low on data pack
Yash98 said:
The above package also contains the DD MD1 kernel.
You may download and extract it.
Click to expand...
Click to collapse
If I could, I would've downloaded the entire package.
But since I can't, I simply asked for it.
nvm.
Another thing,
can you provide me link to update 4 source?
Because i can't find it on their official page.
Link:-
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=5360
Its not yet released
(source)
Here is your boot.img
CharsiBabu said:
If I could, I would've downloaded the entire package.
But since I can't, I simply asked for it.
nvm.
Another thing,
can you provide me link to update 4 source?
Because i can't find it on their official page.
Link:-
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=5360
Click to expand...
Click to collapse
Can I ask you a question?
What would you do with the RamDisk?
The ODIN firmware(zip)package you've provided contains only one .tar.md5 file, but not separated PDA/MODEM/CSC files we've seen in earlier packages(DDLA2,DDLC2,DDLK2, and so on) and this cannot be flashed via ODIN. Even after checking a guide on XDA on how to use ODIN( I know how to use ODIN but I was confused when I found this only one file) and it fails to flash via ODIN. Later I flashed DDMD1 using this one. Please check the firmware package you've provided.
l0lh4rd said:
The ODIN firmware(zip)package you've provided contains only one .tar.md5 file, but not separated PDA/MODEM/CSC files we've seen in earlier packages(DDLA2,DDLC2,DDLK2, and so on) and this cannot be flashed via ODIN. Even after checking a guide on XDA on how to use ODIN( I know how to use ODIN but I was confused when I found this only one file) and it fails to flash via ODIN. Later I flashed DDMD1 using this one. Please check the firmware package you've provided.
Click to expand...
Click to collapse
Then how did I flash it?
Bro, that 1 .tar.md5 is to be put in PDA section and then start flashing.
You'll be suprised when it works!
You are right, but that was believed some time back
Like for example when you download ODIN flashable kernel .tar, do you get all the three tar's: PDA/CSC/MODEM ?
Yash98 said:
Then how did I flash it?
Bro, that 1 .tar.md5 is to be put in PDA section and then start flashing.
You'll be suprised when it works!
You are right, but that was believed some time back
Click to expand...
Click to collapse
Doesn't work
EDIT: Anyways I don't want to bother you with my problems( latest one: can't flash any custom kernels; might be due to new ramdisk as mentioned by member: Nitzz). Nice work
[REVERTED BACK TO OLD BASEBAND; FORGOT TO PROVIDE LOGCAT ]
Bro, if you want I can PM you the three PDA/CSC/MODEM .tar.md5 files by splitting this package, what say?.
Yash98 said:
Bro, if you want I can PM you the three PDA/CSC/MODEM .tar.md5 files by splitting this package, what say?.
Click to expand...
Click to collapse
No thanks but I already got from this thread http://forum.xda-developers.com/showthread.php?t=2335690&highlight=ddmd1 (thread closed but links not removed )
Yash98 said:
Bro, if you want I can PM you the three PDA/CSC/MODEM .tar.md5 files by splitting this package, what say?.
Click to expand...
Click to collapse
Nice idea :thumbup:
PM me too!
aniket.lamba said:
Nice idea :thumbup:
PM me too!
Click to expand...
Click to collapse
Here: http://www.mediafire.com/download/023udvzhhrgnb4z/S5360_DDMD1_ODDMD1_DDMD1.zip
Please report me if it is not 3 package!
l0lh4rd said:
Doesn't work
EDIT: Anyways I don't want to bother you with my problems( latest one: can't flash any custom kernels; might be due to new ramdisk as mentioned by member: Nitzz). Nice work
[REVERTED BACK TO OLD BASEBAND; FORGOT TO PROVIDE LOGCAT ]
Click to expand...
Click to collapse
yo yo!
m back..
yeah just read my thread..
latest firmwares support either my kernel or latest stock kernel..
what are the problems u all are facing?
Update Changelog:
Added Mirror
Update Changelog:
Added Swipe 2 Remove
Added Settings mod
Updated Credits
Can anybody provide me the latest stock kernal of ddmd1??
Sent from my room using sgy evo-x4//
I m always there to help.
CyanFox is a free, community built distribution of Android 4.4 kitkat which greatly extends the capabilities of your phone and to increase performance and reliability over stock Android for your device.
*
Cyan Fox is a light-weight Android 4.4custom ROM, which is based on AOSP/Android (4.4) and CyanogenMod (11) source bases.
Supported devices:
- All devices which are supported on CM 11
Additional FEATURES WILL INCLUDE
- TO BE ADDED SOON
Whats Working:
Theme chooser
Calls
Display
Data (3g/4g)
SMS/MMS
Camera
Video
Sensors (compass, gyro etc)
Vibration
Wifi
Audio
GPS
Bluetooth
Camera
-------------------------------------------------------------------------
Not Working:
No apps to sd... Already fixed for next version < (add by LoLaTiOn) let me know for galaxysl please
Downloads: CyanFox-2.0-20131123-UNOFFICIAL-galaxysl.zip - 184.30 MB dhiru1602 source 13/11/23
----------------------------------------------------------------------------------------
GApps 4.4
gapps 4.4 core gapps
: http://d-h.st/PbA
Changelog:comming soon
Source:
CyanFox: https://github.com/cyanfox
Device: GT-I9003
Kernel: /CyanogenMod/ by dhiru1602 source 13/11/23
G+ Page: /communities/cyanfox
Web site http://www.cyanfox-rom.com
Specia...3/11/21/dute8ydu.jpg[/IMG]
Created 2013-11-25
How to install perfectly i9003
If this is the first liver you use Odin only > Install Driver Samsung and reboot your computer (inclued in Full LF2 link)
If you change version android especialy GB to ICS/JB/KK > Format your SDexternal with SDformter https://www.sdcard.org/downloads/formatter_4/
Before flashing make a copy of your data and ESF
Backup your EFS IMMEDIATELY. [Backup and Restore Guides]
With Odin 1.85 only !!!
Full LF2
PIT > latona_20110114.pit
[BOOTLOADER] only need come from froyo ! no need on GB ...
PDA > CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
PHONE > MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5
CSC > GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5
in bootanimation samsung sound Reset Odin and pull off batterie
With Odin 1.85 only !!!
DDMF1 in PDA
in bootanimation samsung sound Reset Odin and pull off batterie
With Odin 1.85 only !!!
CF Root DDMF1 in PDA
in bootanimation samsung sound Reset Odin and pull off batterie
Recovery VolUp+Home+Power (5 seconds)
Flash Rom x2* (first for repartitioning get new recovery > second flash rom)
Flash gapps > PA-GOOGLE APPS lite for galaxysl
First boot take time beer !!!
Reture recovery for Wiping cache and dalvik cache after setting google !!!
How to change modem
Never flash MODEM with ODIN !!!
Open your firmware whit winrar for extract the modem.bin
Use root explorer for replace existing modem.bin located in root/radio
Reboot
downloading
installed. testing for bug now. thanks lola and dhiru
---------- Post added at 07:03 AM ---------- Previous post was at 06:46 AM ----------
sorry one question... is ART is safe to use? thanks in advance
Can't see the Fox!
Here comes again The Lolation with fire.
Flashed several times over KK4.4 and ended up in cwm boot loop;
How to get pass it to see the Fox!
Tell me please...
overall it is smooth i like it very much. thanks lola for bringing this custom rom. now waiting for pound rom to test
bageraz said:
overall it is smooth i like it very much. thanks lola for bringing this custom rom. now waiting for pound rom to test
Click to expand...
Click to collapse
Please provide CyanFox 2 flashing steps...
sam_777 said:
Please provide CyanFox 2 flashing steps...
Click to expand...
Click to collapse
basically i followed the step from CM11 dev tread to flash CyanFox 2 rom and it work fine.
from the last stable version of slim bean; in recovery mode i ran
- wipe data / factory reset
- wipe cache
- wipe system (format system)
- install CyanFox 2
- install 4.4 gapps
- wipe cache
- wipe dalvik
- reboot
by the way... (forgot to mention in previous post)
there are few flaws on apps that i frequently used such facebook (superb lag and cause heat) and instagram (can't use latest version).
for facebook i use Fast for Facebook and for instagram i used version 3.4.0
for launcher i used smart launcher because it is light-weight and it can auto categories the apps (kudos for that).
a few hiccups here and there (not much to expect from alpha version CM11 because still in development; lockscreen most probably when i see a little lag) but it is a miracle it is working and much more stable and smooth than the previous version of android that i used.
:good: to mr lolation :victory: to mr dhiru
Made this firmware ok. Looks ok but couldn't reach my SD card. All applications shows 0.0 Gb (tryed embended and ES explorer)
sorry...
Dear Lolation,
If possible please give a small share of meat to this cute foxy.
Its starving.....for a long time...
Regards.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS for Samsung Galaxy S5 LTE+ / LTE-A
Code:
- Your warrenty is now void.
- You [b]WILL[/b] trip KNOX!
- You have been warned.
- Use at your own risk.
Introduction:
This is the thread for the offical port of LineageOS to
Samsung Galaxy S5 LTE+, SM-G901F, codename kccat6, and
Samsung Galaxy S5 LTE-A, SM-G906S/K/L, codename lentislte.
This port is mostly stable. Still, there's no software without bugs.
This project is based on the port to CyanogenMod by @sktjdgns1189. For details on the history, please have a look at the original thread.
How to install:
For kccat6, use bootloader CQJ1, CQJ2 or later.
For lentislte use bootloader CPL1.
install custom recovery, ideally directly from the TWRP project.
For kccat6: twrp-3.3.0-0-kccat6.img
For lentislte: twrp-3.3.0-0-lentislte.img
Note: TWRP 3.2.1-0 is required starting with Lineage-15.1/Oreo!
Enter recovery mode
Factory reset
Flash below ROM
Optionally flash Gapps. I suggest OpenGapps.
Optionally, if you want SU, install the LineageOS SU addon.
Reboot
Know problems:
Sometimes the SIM doesn't show up after reboot.
Occasional Camera hiccups.
State of kernel security:
CVE tracking list
Download from:
Official nightly builds:
kccat6: https://download.lineageos.org/kccat6
lentislte: https://download.lineageos.org/lentislte
Test builds (only on demand or request):
kccat6: https://cygwin.de/lineageos/kccat6/
lentislte: https://cygwin.de/lineageos/lentislte/
Sources:
LineageOS on GitHub
XDA:DevDB Information
LineageOS for Samsung Galaxy S5 LTE+ / LTE-A, ROM for the Samsung Galaxy S5
Contributors
cvxda, sassmann, xamio, sktjdgns1189
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: kccat6: CQJ1/CQJ2, lentislte: CPL1
Based On: Lineage OS
Version Information
Status: Beta
Created 2017-01-08
Last Updated 2019-04-17
Notes:
Thanks to @Stamgastje for the first cut of these notes.
History and older builds (LineageOS)
The Lineage OS project -- a.k.a. Lineage Android Distribution (LAD) -- is a continuation of the CyanogenMod project, which was discontinued in December 2016. Before maintaining Lineage OS 14.1 ROM for this phone, @xamio maintained CyanogenMod ROMs (CM13, CM14.1). You can still find these builds via the link to his site (ionkiwi.nl) above. The original (and oldest) CyanogenMod builds for this phone were created by @sktjdgns1189. His original builds are still available here: http://fsrv1.sayanogen.com/KCCAT6-13/, and this was the original thread on this forum.
Installation
Below some hints that may help you to install these ROMs on your phone.
Clean install, or dirty flashing?
What is the difference?
The difference is whether you clean (format) the entire /data partition (which contains your apps and user data, as well as the dalvik cache), or not, before flashing the new ROM image:
A clean install means: clean the /system, /data (incl. dalvik cache) and /cache partitions, and then install the ROM
Dirty flashing means: clean the /system and /cache partitions, as well as the dalvik cache, but not the entire /data partition, before installing the ROM
With a clean install, you need to manually restore your apps and user data after flashing the new ROM image. With a dirty flash, there is no need to do this -- so this is the faster, but riskier solution. Therefore, it is always recommended to make a backup of your apps (e.g. with Titanium Backup) and user data (internal storage) before flashing any ROM image.
When could you consider a dirty flash?
It is, generally speaking, possible to perform a dirty flash:
When upgrading a ROM to an newer build of the same ROM (but be careful when upgrading between major versions, e.g. from CM13 to CM14.1)
When upgrading from CyanogenMod 14.1 to Lineage OS 14.1 (as Lineage OS is the continuation of CyanogenMod, based on the same sources)
When should you perform a clean install?
In all other cases, so e.g.:
When downgrading a ROM to an older build of the same ROM
When switching between ROMS, e.g. from CyanogenMod to Resurrection Remix (or vice versa). Reason: different ROMs use different code bases that are usually not 100% compatible (exception is upgrading from CyanogenMod 14.1 to Lineage OS 14.1, see above)
(Note: in case you choose to perform a dirty flash over your existing ROM, don't forget to re-flash the GApps package immediately afterwards!)
How to dirty flash an official weekly over an unofficial build (and vice versa)?
When trying to update an unofficial build to an official weekly build, I get an error message in TWRP saying
"Can't install this package on top of incompatible data. Please try another package or run a factory reset". How do I fix that?
At the start of an installation the installer checks the build keys. They differ between unoffical and official builds, and the installer refuses to overwrite builds with different keys. To fix this you have to install the official keys before trying to install the official build:
Run this script called lineage-migration-signed.zip in TWRP.
Then install the official ROM zip.
You only have to do this for the first switch from unoffical to offical build.
There may be reason to dirty flash an unofficial build over an official build, for instance, if you're developing or testing new stuff. The problem is the same, just in the other direction: You have to install the unofficial build keys:
Run this script called lineage-migration-unsigned.zip in TWRP.
Then install the unofficial ROM zip.
Modem and bootloader
Which version do I need?
Builds from Sept. 19 (cm-13.0-20160919-UNOFFICIAL-kccat6xx.zip) and later should use a Marshmallow modem & bootloader (starting with 'C', so e.g. CPE1, CPH3, CPJ1). Older builds require a Lollipop modem & bootloader (starting with 'B', so e.g. BOH4, BOK2).
Generally, it is recommended to use the latest modem that is compatible for your device.
How do I get these images?
The original ROM files containing the modem and bootloader files are available from the Sammobile site. You have to extract bootloader and modem files and flash them to your device using Odin (Windows) or Heimdall (Linux, MacOS, Windows).
Download the firmware file from Sammobile's firmware page for the G901F, G906S, G906K or G906L, depending on your device. The last ones available are CQJ1/CQJ2 for G901F, CPL2 for G906S/K/L. Assuming you download the CQJ1 version for G-901F, the resulting file will be called G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip.
Unpack that file. On Windows, right click on the file and choose "Extract all...". On Linux/Mac, simply use the command line:
Code:
$ unzip G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip
After unpacking you get a new file G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. This is a standard tar archive and can be opened with any archiver capable of handling the tar format (especially with tar itself). The attached .md5 suffix indicates, that a md5 checksum has been attached to the file.
Extract the file. On Windows you can do this by installing the swiss-army knife of archivers, 7zip. It installs an entry for the right-click context menu. Use it to extract G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. On Linux/Mac, simply use the command line:
Code:
$ tar xf G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5
Apart from the different download page and the different file names, the procedure is the same on the G906 variants.
Either way, this extracts the following list of files:
Code:
NON-HLOS.bin cache.img.ext4 recovery.img sdi.mbn
aboot.mbn hidden.img.ext4 rpm.mbn system.img.ext4
boot.img modem.bin sbl1.mbn tz.mbn
The files with suffix .img and .img.ext are the actual system files. You don't want them, unless you want to reinstall stock Samsung Android.
The files NON-HLOS.bin and modem.bin constitute the baseband, all other files with .mbn suffix constitute the bootloader.
How do I flash these images on Windows with Odin?
This is only marginally more complex than by using Heimdall (see below). The difference is that Heimdall can immediately flash the extracted .bin and .mbn files, while Odin needs them packed into a tar file. Fortunately you already have 7zip!
Select all of the aforementioned .bin and .mbn files. Right click to open the context menu. Select 7zip and choose Add to archive... from the sub menu
This opens 7zip's archive dialog. As Archive format choose tar. Append .md5 to the archive filename and press the OK button
Congratulations, you're now the happy owner of an Odin file with only bootloader and baseband images.
Sidenote: You could also create a tar.md5 file, you just have to append the md5 sum to the just created tar file. It's not really tricky, but you'd need an additional md5sum tool which is not available on Windows by default, so we just skip this here.
If you haven't already, download and install Odin.
Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
Connect your device to your PC's USB port.
Start Odin.
Select the .tar file you just created.
Enable (only) these options: 'Auto Reboot' and 'F. Reset Time'.
Flash the images.
How do I flash these images on Linux/MacOS/Windows with Heimdall?
If you haven't already, download and install Heimdall. If you have trouble with the most recent version of Heimdall (the official version 1.4.1 has a few annoying bugs) you have to rebuild heimdall from source by yourself. Instructions for rebuilding can be found here and here.
Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
Connect your device to your PC's USB port.
Check if Heimdall recognizes your device:
Code:
$ heimdall detect
If it doesn't, you have to do some digging:
On Windows you might have to install Samsung device drivers.
On Linux you might have to create a udev entry for your device. As root, open or create the file /etc/udev/rules.d/51-android.rules and add a line
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", USER="[insert your non-root username here]"
, then reboot the machine.
On Mac... sorry, I have no idea what to do on a Mac in this case.
Flash the bootloader and baseband images:
Code:
$ heimdall flash --APNHLOS NON-HLOS.bin \
--MODEM modem.bin --SBL1 sbl1.mbn --DBI sdi.mbn \
--ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn
This may take a minute or two and then reboot your device automatically. It might reboot into your recovery. That's nothing to worry about. Just reboot from there into system.
Reserved
super!
Just for completeness, hereby a link to a summary of the history of this ROM. I'll stop maintaining that overview post now, with this new thread and the up-to-date overview in the topic start.
Stamgastje said:
super!
Just for completeness, hereby a link to a summary of the history of this ROM. I'll stop maintaining that overview post now, with this new thread and the up-to-date overview in the topic start.
Click to expand...
Click to collapse
I reserved the first two comments to serve as some kind of FAQ. It would be pretty nice if you could have a look over your notes from the old CM thread and rework them slightly for this thread and, if it's not asked too much, the RR thread. If you send them to me in source (i.e. with all format markers), I'd add them to the reserved comments.
Edit: To be clear, there's still some stuff in your notes which isn't in the OP, which might be helpful to newbies and pros alike.
Thanks,
Corinna
cvxda said:
I reserved the first two comments to serve as some kind of FAQ. It would be pretty nice if you could have a look over your notes from the old CM thread and rework them slightly for this thread and, if it's not asked too much, the RR thread. If you send them to me in source (i.e. with all format markers), I'd add them to the reserved comments.
Edit: To be clear, there's still some stuff in your notes which isn't in the OP, which might be helpful to newbies and pros alike.
Thanks,
Corinna
Click to expand...
Click to collapse
Sure, will do so! How can I best send you the source? I can't send you a private message on this forum. AFAIK you should be able to send me a private message, so would be good if you could share me your contact details there (e.g. an e-mail address).
Stamgastje said:
Sure, will do so! How can I best send you the source? I can't send you a private message on this forum. AFAIK you should be able to send me a private message, so would be good if you could share me your contact details there (e.g. an e-mail address).
Click to expand...
Click to collapse
You got a PM.
Thanks,
Corinna
Excellent (separate thread and the rom).
One annoyance still remaining is the backlight not turning on sometimes, have to lock unlock to get it back.
Great work. Pls make for G906x too ?
girtsn said:
Excellent (separate thread and the rom).
One annoyance still remaining is the backlight not turning on sometimes, have to lock unlock to get it back.
Click to expand...
Click to collapse
What backlight?!? This is an AMOLED display. It has no backlight.
Corinna
not sure what is the correct name but usually the phone when unlocked goes quite bright. there are however situations (the issue is not sure how to reproduce) when the display is much more pale, like energy saving or something.
i have adaptive brightness on and display mode of livedisplay on auto
cvxda said:
What backlight?!? This is an AMOLED display. It has no backlight.
Click to expand...
Click to collapse
girtsn said:
not sure what is the correct name but usually the phone when unlocked goes quite bright. there are however situations (the issue is not sure how to reproduce) when the display is much more pale, like energy saving or something.
i have adaptive brightness on and display mode of livedisplay on auto
Click to expand...
Click to collapse
Sometimes, the screen is indeed very dark after wake up (e.g. with power button) and it is fixed by turning the screen off and on again.
I think this is related to the ambient light sensor.
In my opinion it's not a major issue... only a small annoyance at best (if rarely happens).
Stamgastje said:
Sometimes, the screen is indeed very dark after wake up (e.g. with power button) and it is fixed by turning the screen off and on again.
I think this is related to the ambient light sensor.
In my opinion it's not a major issue... only a small annoyance at best (if rarely happens).
Click to expand...
Click to collapse
I see the same problem on klte. IMHO the ambient display brightness algorithm might not be the brightest one
Edit: However, on klte as well as on kccat6 I just have to move the brightness slider to get a more matching brightness.
Corinna
I believe the ROMs can be uploaded to the download section of this thread.
Anyone know how to set the SD card permissions? I can't make any changes to it.
And I'd love to hear when someone has a working Xposed!
Also, settings crashes very often when I try to change my ringtone for example, and I found my phone randomly rebooting twice today.. clean install was done..
Proioxis said:
Anyone know how to set the SD card permissions?
Click to expand...
Click to collapse
I don't understand this. Need more information regarding this? Like cannot see SD card or no write permissions or what?
ruchern said:
I don't understand this. Need more information regarding this? Like cannot see SD card or no write permissions or what?
Click to expand...
Click to collapse
I can't make any changes to the SD card, but I just read it's a known ROM issue.
"File Manager app can't access the SD card, even with root permissions (generic Lineage OS problem)"
Proioxis said:
I can't make any changes to the SD card, but I just read it's a known ROM issue.
"File Manager app can't access the SD card, even with root permissions (generic Lineage OS problem)"
Click to expand...
Click to collapse
I had this problem before but upgrading the ROM worked for me. I couldn't remember what exactly happened.
Are you on LineageOS-20160107 build?
ruchern said:
I had this problem before but upgrading the ROM worked for me. I couldn't remember what exactly happened.
Are you on LineageOS-20160107 build?
Click to expand...
Click to collapse
I'm on the 20170104 build. I'll check the 0107 build.
EDIT: Just checked the SD permissions, still can't change anything.
Proioxis said:
I'm on the 20170104 build. I'll check the 0107 build.
EDIT: Just checked the SD permissions, still can't change anything.
Click to expand...
Click to collapse
Just install and use any other file manager; the one provided with the ROM does not work. I use ES File Explorer and that gives me full access to the SD card.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
ruchern said:
I had this problem before but upgrading the ROM worked for me. I couldn't remember what exactly happened.
Click to expand...
Click to collapse
I think you're mixing things up. In one of the first CM14.1 builds, the complete SD card was invisible, but that has been fixed long time ago already.