*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
WARNING #1: CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
USEFUL LINK OF TW ROMS:
http://forum.xda-developers.com/showthread.php?t=2616221
CURRENT PROJECT STATUS:
v3.72 (NB1): Beta testing, no rom-slots
v3.71 (MK2): Debugging some rom-slot issues
v3.65 (TW4.2): Stable
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2 on the S4 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for 3 different sizes of /data partitions: 1GB, 2GB and 3GB. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Go into your old Safestrap app and use the "Uninstall Recovery" button
THEN, open a "file explorer" of some sort (even TW "My Files" will work)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
KNOWN ISSUES:
[v3.72] ROM-SLOTs aren't supported yet
[v3.72] "Reboot Recovery" doesn't work in the APK?
NEW TO v3.72:
TWRP 2.7.0.x update for the base recovery. This includes vibration support, backup time/date fixes and more.
ROM-SLOTs now have a 16gb size limit (vs 4gb previously) [THEY DON'T WORK YET IN KK THO SO BE PATIENT]
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN AT&T SAMSUNG GALAXY S4 (NOT THE ACTIVE MODEL)
MAKE SURE IF YOU ARE UPGRADING TO v3.7x FROM v3.65 THAT YOU USE THE "UNINSTALL RECOVERY" BUTTON IN THE v3.65 APK BEFORE INSTALLING v3.7x.
NOTE: USE ONLY ROMS THAT MATCH UP WITH YOUR TOUCHWIZ VERSION. IF YOU'RE ON MK2 THEN ONLY USE ROMS BASED ON MK2 AND IF YOU'RE ON MF3 ONLY USE ROMS BASED ON MF3
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
FOR USERS OF NB1:
USE 3.72+:BETA Safestrap-JFLTE-3.72.apk (updated 2014-04-02)
FOR USERS OF MK2:
USE 3.71+:BETA Safestrap-JFLTEATT-3.71.apk (updated 2013-12-27)
FOR USERS OF MF3 (TW4.2):
LATEST FILE: Safestrap-JFLTEATT-3.65.apk (updated 2013-11-15)
Main XDA Downloads Page
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
ALSO DOWNLOAD THE KERNEL MODULES .ZIP THAT MATCHES YOUR BUILD # (FLASH THIS AFTER ROMS):
MF3: http://forum.xda-developers.com/devdb/project/dl/?id=508
MK2: http://forum.xda-developers.com/devdb/project/dl/?id=3275
HOW TO MANUALLY REMOVE SAFESTRAP:
[ INSTRUCTIONS ONLY FOR PRIOR TO v3.65. REMOVE VIA APK FOR v3.70+ ]
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
This thread is a development ONLY thread.
For discussion go here:
http://forum.xda-developers.com/showthread.php?t=2428254
XDA:DevDB Information
Safestrap Recovery v3.71 (JB) / v3.72 (KK), a Tool/Utility for the AT&T Samsung Galaxy S 4
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Beta
Current Stable Version: 3.71
Stable Release Date: 2013-12-27
Current Beta Version: 3.72
Beta Release Date: 2014-04-02
Created 2013-09-18
Last Updated 2014-04-02
Reserved
KNOWN ISSUES:
Bluetooth remote control isn't working on rom-slots.
CHANGELOG:
[2013/11/13] TWRP updates
[2013/11/13] "toolbox" binary / symlinks in recovery fixed
[2013/11/11] Uninstall from the APK fixed
[2013/09/17] /sdcard mounting bugfix
[2013/09/17] Hijack improments to support default rootfs files
[2013/09/17] ROM-slot image creation bugfix for size > 2gb
[2013/09/12] Much improved block device handling
[2013/09/11] Bugfix in script translation
[2013/09/11] hijack / init.rc tweaks
[2013/09/11] Bugfix for display lag / buffering issue (WIP)
[2013/09/10] Adjust "ROM-slot" display in UI
[2013/09/10] /data/media handling changes
[2013/09/06] custom twrp.fstab files
[2013/09/06] /data/media handling changes
Reserved
KNOWN ROM INSTALL / ISSUES:
All TW-based ROMs. If you don't have wifi make sure to flash the kernel modules for your stock kernel version.
Looks promising,
Thanks
Sent from my GT-I9505G using XDA Premium HD app
Add the MF3 kernel module .zip to the "Downloads" section.
http://forum.xda-developers.com/devdb/project/?id=680#downloads
Keep this on your SD card and flash it to the ROM-slot AFTER flashing a rom.
This will update your kernel modules to match the MF3 kernel and restore function to: wifi, bluetooth, gps etc.
Thank you so much hash!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
An at&t thread. Yes! andyfredrick
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hashcode said:
Add the MF3 kernel module .zip to the "Downloads" section.
http://forum.xda-developers.com/devdb/project/?id=680#downloads
Keep this on your SD card and flash it to the ROM-slot AFTER flashing a rom.
This will update your kernel modules to match the MF3 kernel and restore function to: wifi, bluetooth, gps etc.
Click to expand...
Click to collapse
WIFI WORKS!!!!!!!! and so does everything else...
Hash can i backup my stock rom to the external sd card and than delete it so i get my 10gigs back? is that safe?
hope this helps out some people!!.. nice job man!! :good:
Just install gpe wifi gps work! i also went back to stock rom and everything worked perfect
Andrew149 said:
WIFI WORKS!!!!!!!! and so does everything else...
Hash can i backup my stock rom to the external sd card and than delete it so i get my 10gigs back? is that safe?
Click to expand...
Click to collapse
God , no!
Sent from my SPH-L720 using XDA Premium 4 mobile app
rebel1699 said:
God , no!
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well that sucks! i hate having only 3gigs of user space =[
Graviton Rom works on SS... no issues at the moment ...what else are other users using?
---------- Post added at 07:12 AM ---------- Previous post was at 06:51 AM ----------
Can I flash performance mods zips only on slot 1 like killjoy or flyon mod etc? Or no because the stock kernel doesn't have init.d support?
Edit: as long as you flash to slot 1-4 everything will be safe. .. currently using darth stalker rom and that has init.d support, no issues at the moment.
HI
sykoj82 said:
Graviton Rom works on SS... no issues at the moment ...what else are other users using?
---------- Post added at 07:12 AM ---------- Previous post was at 06:51 AM ----------
Can I flash performance mods zips only on slot 1 like killjoy or flyon mod etc? Or no because the stock kernel doesn't have init.d support?
Click to expand...
Click to collapse
HELLO GREETINGS GUYS, GREAT JOB, I HAVE A DOUBT REGARDING THE SAFE ROMS SUPPORT STRAPS, AND ROM VERSIONS
1 - VERSION 4.3 SUPPORT? SS
2 - VERSION 4.2.2 SUPPORT? ROMS SUPPORT IS SS
3-THEME CAN FLASH MOD, ECT ..,?
* FINALLY HAVE MANY ROM Pacht LOKI LOKI IS DEVE install AFTER THE ROM OR NOT ONLY THE MODULE MF3? SORRY FOR MY ENGLISH I AM USING GOOGLE TRANSLATOR .. THANKS ..
HOLA CHICOS SALUDOS ,,GRAN TRABAJO,TENGO UNA DUDA EN CUANTO LOS ROMS SOPORTE PARA SAFE STRAPS,Y VERSIONES DE ROM
1- 4.3 VERSION SOPPORTE?SS
2- 4.2.2 VERSION SOPPORTE?SS CUAL ROMS SOPORTE
3-SE PUEDE FLASHEAR MOD THEME, ECT..,?
POR ULTIMO MUCHOS ROM TIENE LOKI PACHT SE DEVE INTALAR EL LOKI DESPUES DEL ROM O NO SOLAMENTE EL MODULO MF3 ? DISCULPEN POR MI INGLES ESTOY USANDO GOOGLE TRADUCTOR..GRACIAS..
So I've searched and searched, but can't seem to find a clear answer and I want to make sure of this before I try.
My "stock" ROMs are always CM-based 4.3 ROMs (haven't used TW in awhile). I got my S4 when it was still MDL so my qfuse isn't blown - so my intended use for this is only for the additional ROM slots. I have gathered that, at least for now, the only ROMs we can flash to the additional slots have to be TW or GPE 4.2.2. But my question is, does my primary ROM also have to meet that description? Or can I keep my 4.3 AOSP ROM as my primary?
AT&T Error
Hello,
I flashed the GEP rom to Rom Slot 1 and now I am getting an error that says Kernel Fail; System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help. There is a yellow triangle.
I followed the instructions, but now have a hosed phone unless I can somehow restore the backup of my stock rom.
Any information would be helpful.
Thanks for your efforts.
dtruong23 said:
Hello,
I flashed the GEP rom to Rom Slot 1 and now I am getting an error that says Kernel Fail; System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help. There is a yellow triangle.
I followed the instructions, but now have a hosed phone unless I can somehow restore the backup of my stock rom.
Any information would be helpful.
Thanks for your efforts.
Click to expand...
Click to collapse
Oh no...I hope I don't see that. I wish you luck! Was your phone encrypted to begin with?
Does anybody know why it would say this? Now I'm hesitant to flash anymore roms.
sykoj82 said:
Oh no...I hope I don't see that. I wish you luck! Was your phone encrypted to begin with?
Click to expand...
Click to collapse
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
dtruong23 said:
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
Click to expand...
Click to collapse
Wow...so far I flashed 2 different roms...I haven't tried the one you flashed...good luck to u... I'm definitely scared to flash any more roms...but you are 100% positive slot 1 was activated before flashing right? Thats the only thing I can think of that "stock" was activated..
dtruong23 said:
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
Click to expand...
Click to collapse
What GPE rom did u flash?? did u flash the kernel module zip??
Related
*** Started with ODIN file "Stock ROM 4.1.1 JRO03L.T999UVDLJC" (UNTOUCHED)
*** NEW STOCK Kernel 4.1.1 (UNTOUCHED) (3.0.31-370274 [email protected] #1 SMP PREEMPT Thu Jan 17 21:40:34 KST 2013)
Kitchen - SuperSU 1.02 (ROOT)
Kitchen - busybox 1.20.2
Kitchen - init.d scripts support (busybox run-parts)
Kitchen - Nano text editor + sysro/sysrw
Kitchen - Bash (command shell)
Kitchen - /data/app functionality
Kitchen - De-odex'd
Kitchen - Zipaligned
Includes these CSC Files & Folders (Customer Software Customization)
system\csc
system\etc (amzn.mshop.properties, csc_apks_list_TMB.txt, csc_ringtones_list_TMB.txt, hidden_apks_list_TMB.txt)
system\T9DB
system\wallpaper
system\CSCVersion.txt
system\SW_Configuration.xml
Removed CIQ (these 4 files Gone)
system\app\.....IQ_OOB_TMO.apk
system\app\.....IQ-tmobile-release-unsigned.signed_TMO.apk
system\app\.....IQToggle.signed_TMO.apk
system\lib\.......libiq_service_tmobile_2.2.so
Download : SGS3 JB 4.1.1 T999 UVDLJC STOCK Base (Rooted)
Use this Most Current BASE or Customize it from here!
HOW to Flash ROM
1. Boot into Recovery. I Recommend "TWRP Recovery v2.4.1.0" <-New Version (Signed + Flashable)
2. Make "Backup" of current ROM.
3. Wipe 3x: Cache - Dalvik Cache - Factory Reset - System - { Internal Storage (Optional) - Format Data (Optional) }
4. Flash ROM.
5. Enjoy.
Baseband Version (Modem) will still say T999UVDLJA...
To Update Modem to "T999UVDLJC"
1) Download file on Post #1 -> T999UVDLJC Modem
2) Extract "UVDLJC.bin" and put it on your Internal SDcard of cell.
3) Run Terminal Emulator (app from Market) enter this code...
su {this is need 1st time for Superuser Permissions}
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.bin bs=4096 {this made backup of old "modem.bin" to Internal SDCard it is 60.00 MB}
dd if=/sdcard/UVDLJC.bin of=/dev/block/mmcblk0p1 {this installed New Modem}
4) Reboot and check Settings - About Device
5) Save "modem.bin" to safe spot on PC or know where you can get it, if need be.
6) Enjoy
THANKS
Looks like we need another mirror on this happiness... Here's a sourceforge link... another-source
Though the server does have speed... once I DID get connected, I was pulling it at ~ 6MB/s...
Just out of curiosity, what's the difference between this stock rom and this one:
http://forum.xda-developers.com/showthread.php?t=2126679
mutiny said:
Just out of curiosity, what's the difference between this stock rom and this one:
http://forum.xda-developers.com/showthread.php?t=2126679
Click to expand...
Click to collapse
You may want to hold off on doing this update.
Official Description.
Security Enhancements
Enhanced User Experience
According to the Post by a T-MO Rep on T-MO News website, This update REMOVES LTE Functionality and Possibly updates IPV6 issues. According to one Poster, it still is broken.
Weather the irritating issue with Google Voice Temp Numbers is not likely fixed. Nor is the Proxy Server issues experienced by some.
So each to their own conclusion.
Thanks for mirror...
Baseband Version (Modem) will still say T999UVDLJA...
To Update Modem to "T999UVDLJC"
1) Download this on Post #1 -> T999UVDLJC Modem
2) Extract "UVDLJC.bin" and put it on your Internal SDcard of cell.
3) Run Terminal Emulator (app from Market) enter this code...
su {this is need 1st time for Superuser Permissions}
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.bin bs=4096 {this made backup of old "modem.bin" to Internal SDCard it is 60.00 MB}
dd if=/sdcard/UVDLJC.bin of=/dev/block/mmcblk0p1 {this installed New Modem}
4) Reboot and check Settings - About Device
5) Save "modem.bin" to safe spot on PC or know where you can get it, if need be.
6) Enjoy
Perseus71 said:
You may want to hold off on doing this update.
Official Description.
Security Enhancements
Enhanced User Experience
According to the Post by a T-MO Rep on T-MO News website, This update REMOVES LTE Functionality and Possibly updates IPV6 issues. According to one Poster, it still is broken.
Weather the irritating issue with Google Voice Temp Numbers is not likely fixed. Nor is the Proxy Server issues experienced by some.
So each to their own conclusion.
Click to expand...
Click to collapse
So stay away from these stock T999UVDLJC roms altogether? what about the UVDLJC radio/modem?
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
ktmdave7 said:
Thanks for mirror...
Baseband Version (Modem) will still say T999UVDLJA...
To Update Modem to "T999UVDLJC"
1) Download this on Post #1 -> T999UVDLJC Modem
2) Extract "UVDLJC.bin" and put it on your Internal SDcard of cell.
3) Run Terminal Emulator (app from Market) enter this code...
su {this is need 1st time for Superuser Permissions}
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.bin bs=4096 {this made backup of old "modem.bin" to Internal SDCard it is 60.00 MB}
dd if=/sdcard/UVDLJC.bin of=/dev/block/mmcblk0p1 {this installed New Modem}
4) Reboot and check Settings - About Device
5) Save "modem.bin" to safe spot on PC or know where you can get it, if need be.
6) Enjoy
Click to expand...
Click to collapse
The OP of that thread said to flash using recovery. Ignore those instructions and follow this instead?
mutiny said:
Just out of curiosity, what's the difference between this stock rom and this one: http://forum.xda-developers.com/showthread.php?t=2126679
Click to expand...
Click to collapse
This one has CSC Codes and had Newest v1.02 SuperSU (but they just updated it to 1.04 {in 3 days they've had 5 updates now})
-Not many people remove this file from CIQ ... system\lib\.......libiq_service_tmobile_2.2.so
-They just remove the 3 .apk's and call it good. the lib is useless by itself, but any CIQ checker app will see that file and say some kind of warning)
ktmdave7 said:
This one has CSC Codes and had Newest v1.02 SuperSU (but they just updated it to 1.04 {in 3 days they've had 5 updates now})
-Not many people remove this file from CIQ ... system\lib\.......libiq_service_tmobile_2.2.so
-They just remove the 3 .apk's and call it good. the lib is useless by itself, but any CIQ checker app will see that file and say some kind of warning)
Click to expand...
Click to collapse
Ah. Thank you for clarifying that. I'm guessing I have to debloat this myself right? I'm currently using your other Slim Stock rom and I love it. The only stock TW rom I'm happy to use.
Thanks for using that Cool ROM, I'm so close to the 4th Release (it's even better)
-already have this Update on my test version
-Removed 32 More .apks in System\app (only 80 now)
-want to fix little problem first (Phone - Logs = shows many call logs on 1 phone conversation) I narrowed it down to 55 files from 1st release is needed at least)
Read Post#1 2nd code box from bottom for Future Release changes -> Link
ktmdave7 said:
Thanks for using that Cool ROM, I'm so close to the 4th Release (it's even better)
-already have this Update on my test version
-Removed 32 More .apks in System\app (only 80 now)
-want to fix little problem first (Phone - Logs = shows many call logs on 1 phone conversation) I narrowed it down to 55 files from 1st release is needed at least)
Read Post#1 2nd code box from bottom for Future Release changes -> Link
Click to expand...
Click to collapse
I'll be impatiently waiting for your 4th release! LOL. I don't know what the significant updates are in UVDLJC are, but I trust your judgement. Thanks again for your work and contribution.
mutiny said:
I'll be impatiently waiting for your 4th release! LOL. I don't know what the significant updates are in UVDLJC are, but I trust your judgement. Thanks again for your work and contribution.
Click to expand...
Click to collapse
Will 4th Release be based on UVDLJC or UVDLJA?
will be UVDLJC..the kernel is newer as well..the update was only 4 mb . so not much is changed..alot of files are close to same as other 1
I can report improved data speeds with the JC modem in the ATL GA area for those curious about the updates as far as the ROM update I could care less about security updates lol
Sent from my SGH-T999 using xda app-developers app
mutiny said:
So stay away from these stock T999UVDLJC roms altogether? what about the UVDLJC radio/modem?
Click to expand...
Click to collapse
You understand Correctly.
ktmdave7 said:
This one has CSC Codes and had Newest v1.02 SuperSU (but they just updated it to 1.04 {in 3 days they've had 5 updates now})
-Not many people remove this file from CIQ ... system\lib\.......libiq_service_tmobile_2.2.so
-They just remove the 3 .apk's and call it good. the lib is useless by itself, but any CIQ checker app will see that file and say some kind of warning)
Click to expand...
Click to collapse
Would flashing these modems trip the dreaded System Modified Message ? Or Flash Counter ? Or Both ?
Flashed this, works great. Debloaded according to ktmdave's recommendations and voala blazing fast and stable, great job again!! Cant wait for the 4th release!!
Sent from my SGH-T999 using Tapatalk 2
I flashed this today and for no other reason you guys should try it for the kernel alone. This build is super smooth throughout. Thanks for putting this together op.
kimbo1986 said:
Flashed this, works great. Debloaded according to ktmdave's recommendations and voala blazing fast and stable, great job again!! Cant wait for the 4th release!!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Can you tell me if your "Device Status" is Marked as Modified or Normal ?
Mine says modified on every rom except synergy rom.
gmanhad said:
Mine says modified on every rom except synergy rom.
Click to expand...
Click to collapse
For the sake of JB 4.2 and Warranty, I am trying to keep this status to Normal. Chainfire has already stated that it is next to impossible to reset this status once its modified. So Triangle Away won't help.
So I guess flashing those Modems will change my status. Can someone confirm ?
Welcome to the Samsung Galaxy Ace II x / GT-S7560M Unofficial FAQ!
-The Galaxy TREND GT-S7560 is also supported-
==>THIS IS AN OUTDATED PHONE AND THE LINKS/FILES BELOW MAY OR MAY NOT BE THERE ANYMORE<==
!!SEE POST #2 BELOW FOR LINKS
Frequently Asked Questions:
1- "Flash with CUSTOM RECOVERY (TWRP/CWM)" : If you still have the stock recovery, download and use Daver18qc's Root Kit Below to install a custom recovery from the CUSTOM RECOVERIES header in post #2.
2- "Flash with ODIN" : ODIN is inside Daver18qc's Root Kit *With Detailed Instructions* below.
3- "Push with ADB" : You need to download and install Android's Development Kit and then refer to the small tutorial below !
4- If you've got problems with ODIN or ADB, make sure that you have USB Debugging Enabled under Settings > Developer Options.
--Make sure you have only 1 device showing in ODIN (Only 1 little square filled at the top-left)
--Also make sure Kies.exe is not running on the computer!
5- There are custom ROMs, such as CyanogenMOD 10 and 11, OmniROM 4.4, and more. There is no Lollipop ROM just yet, though it is slowly being worked on. A lot of work is needed to update our device code for Lollipop. You can find links to different custom ROMs for our device in post #2.
6- There is NO free method to UNLOCK SIM yet.
7- If you want to flash any deodexed rom with a custom recovery, you must first flash the complete corresponding ROM from SamMobile. That means deodexed Guatemala need to be flashed over Guatemala, not over Panama or Canada. Same goes for deodexed Australia.
8- If you get a Yellow warning triangle on boot after flashing something, use TriangleAway to remove it and reset the flash counter to 0. (On the page, use the provided TriangleAway apk file available for download at the bottom of the first post)
9- Flashing a ROM from Guatemala or Australia will not change your service provider, you will stay with Bell/Koodo/Rogers even if these companies don't exist in Guatemala.
10- Sometimes when flashing ROMS, your carrier will show as "Bell" even though you are on Virgin / Solo, this is normal as these are 2 sub-companies of Bell.
11- When you flash ANYTHING with a custom recovery, be sure to Wipe Cache and Wipe Dalvik Cache (advanced menu) before rebooting.
12- For ANY kind of flashing from a Windows computer, you will need the Samsung USB Drivers first and foremost, before doing anything else. If you're on Linux/Ubuntu, install Heimdall and search for tutorials for how to use it on XDA or Google.
13- If you have the Galaxy Trend GT-S7560 and CWM freezes while flashing a custom rom, then re-cook the rom inside the Kitchen with these tweaks:
Code:
For galaxy trend s7560
When building rom in kitchen, select Interactive Mode(1). after zipaling;
1. edit META-INF/com/google/android/updater-script in working folder and change " format("ext4", "EMMC", "/dev/block/mmcblk0p16"); " to " format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system"); "
2. extract cm11 for ace 2x and replace META-INF/com/google/android/update-binary from cm11 to your rom
======================================END OF FAQ=============================================
Short Tutorials :
Buttons combinations (phone must be shutdown before !)
Download Mode : VOLUME DOWN+HOME+POWER
Recovery Mode : VOLUME DOWN+VOLUME UP+HOME+POWER
How to "Push with ADB" :
Install the Android Development Kit
Goto "platform tools" folder
Open a command prompt
Connect your phone with USB cable and USB Debugging enabled (developer settings)
Type in the command prompt:
-adb remount
-adb push "yourfilename" "/your/destination"
-adb reboot
example: "adb push SystemUI.apk /system/app/"
How to flash with ODIN :
-If your ROM is zipped, unzip it to a folder until you got a ".TAR.MD5" file
-Load up ODIN
-Shutdown your Phone
-Boot your Phone in Download Mode
-Plug in your USB cable, Odin should recognize the Phone and fill up a small square at the top left.
-Make sure only "F.Reset Time", "Auto Reboot" and "PDA" are check-marked in ODIN
-Load up your ".TAR.MD5" in the PDA section of ODIN
-Flash, wait for ODIN to tell you (Succeeded : 1, Failed : 0)
-Done.
How to flash CM11 (CyanogenMod11) by Alex150892 :
1.Install Australia MH3 stock rom with Odin
2.Download Root Kit and follow instructions inside (follow it carefully from beginning to the end)
3.Open cwm recovery and Wipe data/cache,and also wipe dalvik cache
4.Install CyanogenMod 11
5.Install 4.4 Gapps
6.(optional) Install ba2x kernel for CyanogenMod 11
7.Reboot and enjoy...
Note that first boot will take a while,so leave it for ~10mins
Links:
------CUSTOM ROMS-------
Note: None of the custom ROMs are bug-free. Some of them are more stable and bug-free than others though. Some common bugs among all the ROMs are lack of full camera resolution (the rear camera only captures images at 3MP instead of the 5MP in Stock ROM) and lack of bluetooth (our chipset doesn't support the newer bluetooth method used in Android 4.2+).
CyanogenMOD 10.2/11 by SeannyM UNSUPPORTED
CyanogenMOD 10.1 (Android 4.2.2) by jonypx09 UNSUPPORTED
CyanogenMOD 10.2 (Android 4.3.1) by Codename13 UNSUPPORTED
Beanstalk 4.4.275 (Android 4.4.2) by jonypx09UNSUPPORTED
CyanogenMOD 11 (Android 4.4.4) by jonypx09
OmniROM 4.4.4 (Android 4.4.4) by Codename13
------STOCK ROMS-------
(These are compatible with ALL countries and should be flashed if you want the latest version of ICS on your phone, regardless of where you live or who your phone service provider is.)
Stock firmwares from Sammobile
[URL="http://www.sammobile.com/forum/register.php"]You Must register on SamMobile by clicking here first! (FREE)[/URL]
Modified stock firmware "Stock II X Plus" by Codename13. It is deodexed, rooted, has init.d functionality, has ADB support, doesn't overwrite your custom recovery with the stock one, and other misc. changes, plus it shouldn't trigger the triangle flash counter.
If you install a stock ROM/firmware over a custom ROM and you get a bootloop, meaning you probably forgot to wipe data, and you're unable to boot to recovery, flash this package (by Codename13) with Odin to wipe your data partition, which should allow you to boot into the stock ROM.
------CUSTOM KERNELS-------
Sadman2's kernels for ICS 4.0.4 with GPU Overclock !
-Flash with CUSTOM RECOVERY, Wipe Cache and Dalvik Cache, Reboot.
V1: http://www36.zippyshare.com/v/15770700/file.html : OC CPU 1.2GHZ
V2: http://www43.zippyshare.com/v/33249511/file.html : OC CPU 1.3GHZ
V3: https://drive.google.com/file/d/0BzqKRicqg1wVdl9kQnI4NUk1ZTA/edit?usp=sharing : OC CPU 1.2GHZ GPU 275MHZ
V4: http://www11.zippyshare.com/v/61114227/file.html : OC CPU 1.3GHZ GPU 325MHZ
BA2X (Better Ace 2 X) 2.0 for Stock ROM by Codename13 UNSUPPORTED
SeannyM's Overclocked/Modded Kernels For Stock ROM(Flash with CUSTOM RECOVERY) UNSUPPORTED (I think)
[/B]-A vast range of frequencies to choose from, you can start with 1094mhz and if your phone is stable and doesn't reboot on it's own you can then go up a couple more until you get to a point where your phone won't boot, then you need to go back down in frequencies.
Most people seem to hit a wall around 1248mhz.
-To take full advantage of this Kernel, you should install No-Frills CPU Control
--Set the maximum frequency to the maximum possible
--Set the minimum to 240 or 320
--Set the governor to SmartAssV2
--Set the I/O sheculer to VR
------CUSTOM RECOVERIES-------
List of custom recoveries (thread maintained by Codename13)
http://forum.xda-developers.com/showthread.php?t=2682888
------OTHER-------
Possible fix to CM10.2 WiFi problems suggested by Anas Karbila
-Install that app from the market and use it to correct the problem.
https://play.google.com/store/apps/details?id=co.in.zextr.wcf
Possible fix to ICS 4.0.4 with WiFi problems on Sadman2's Kernels :
-Use a root file explorer to overwrite the original files in /system/lib/modules with those from the link below.
http://forum.xda-developers.com/attachment.php?attachmentid=2630852&d=1394823897
Daver18qc's GT-S7560M Root Kit (With Detailed Instructions!) v.3
Daver18qc's List of Apps that are Safe To Delete (Once Rooted!):Guatemela 'MG2 or Stock ROM
===========================================================================================
That one might be bugged, try the "Stock Guatemala MG2" + "Deodexed Guatemala" below if you have problems!
Daver18qc's Deodexed/Rooted Australia MH3 ROM (Latest 24sept2013) (Flash With CUSTOM RECOVERY Over Australia 'MH3 ROM, Wipe Cache/Dalvik)
===========================================================================================
Daver18qc's Deodexed/Rooted Guatemala MG2 ROM (Flash With CUSTOM RECOVERY Over Stock Guatemala MG2, Wipe Cache/Dalvik) *Confirmed Working*
Thanks to Viper520 for ViPER4Android
Daver18qc's Pack of Modded SystemUI ("Push" with ADB)
-(Download the one with the notifications toggles you want, the others buttons are removed!)
Codename13's ModPack UNSUPPORTED (Flash with CWM) for Deodexed ROMS ONLY!
Codename13's Panama Stock ROM (Flash with CUSTOM RECOVERY)
Codename13's Insecure Stock Kernel (Flash with ODIN in PDA Section)
OstrichX's CyanogenMOD 10.1 Work In Progress Page
Mods made by other people that works on GT-S7560M:
Cbass15's Black Theme AOSP SMS App!
(Delete /system/app/SecMMS.apk, Copy this file to /system/app/ and DON'T RENAME IT, then REBOOT!)
Screenshot of the CBASS15's AOSP Messaging
Dsixda's KITCHEN
You can deodex and customize almost any ROM made for this phone using this version of the Kitchen.
You will need a computer running Linux, either on the hard drive or in a virtual machine inside Windows.
You will need extensive knowledge of the Linux commands as everything is inside a terminal (a kind of MS-DOS command prompt)
If you don't know what Linux is, don't bother, this is out of your reach and nobody will teach you here.
Learn it somewhere else and come back here when you know where you're going with this.
DOWNLOAD 0.223 KITCHEN
DOWNLOAD EDIFY_DEFS FILE
-(The EDIFY_DEFS file is necessary to make a working ROM, you will softbrick your phone if you don't put this file inside your edify-defs folder in the kitchen folder.)
MANY THANKS TO : SeannyM, jonypx09, Codename13, OstrichX and all the others who made this possible!
POST YOUR QUESTIONS IN THE MAIN THREAD HERE PLEASE!
daver18qc said:
FAQ:
6- There is NO free method to UNLOCK SIM yet.
Click to expand...
Click to collapse
till there is some way to unlock the GT-S7560m (hopefully soon)
may i suggest http://forum.xda-developers.com/showpost.php?p=44776737&postcount=1916
unlockclient co
self contained software (means no 24 hour wait for email) takes seconds to do
i searched and search for hours yesterday.. found that one post above
and pretty much nothing else.. the huge 240 page 7560m thread has people asking every second page.. no joke
more info needs to be given about this. and maybe some research on how to do it for free.. but in the mean time:
i took a chance and got it.. and was not disappointed at all (works just like youtube vid)
btw im just a frustrated end user, not affiliated with any company
I would like to download this: Daver18qc's Deodexed/Rooted Australia ROM (Latest 24sept2013) but the DropBox download link isn't working...
Links are dead
Hi...
links for stock versions are not working...
wanted to download the guatemala stock to flash other rom later, but the link is dead...
any one has a backup by any chance?
im currently on the canadian rom i guess... already got root and CWM
thanks1
mertonv said:
Hi...
links for stock versions are not working...
wanted to download the guatemala stock to flash other rom later, but the link is dead...
any one has a backup by any chance?
im currently on the canadian rom i guess... already got root and CWM
thanks1
Click to expand...
Click to collapse
samsung-updates.com has most of the Ace II X firmwares on alternate mirrors such as RapidGator and ul.to.
Links are dead
Codename13 said:
samsung-updates.com has most of the Ace II X firmwares on alternate mirrors such as RapidGator and ul.to.
Click to expand...
Click to collapse
Hi!
Thanks for pointing out where...
samsung-updates .com/device/?id=GT-S7560M
Im assuming this is the one im looking for
Galaxy Ace IIx GT-S7560M PGU S7560MUBAMG2
Unfortunately, the links on that site seem broken too... unless its me and i cant get them to work...
looking with the code "S7560MUBAMG2" i found a version PBS, CPA and TCP (panama, panama and mexico), all three have the same build date and change list numbers (05.07.2013 and 1230914)...
im downloading PBS version, its a 532mb file, is that right?... no wonder the device sucks that much... that image is bigger than the stock for my the TF300t... this **** is bloated
is this the same image as guatemala?
Can't seem to find the PGU anywhere... all links are to hotfile (which seems dead) or broken
thanks anyway...
i wanted to test the slimbean rom but guess i'll have to wait a while then...
the device is slow, but rather have a slow phone than a bricked one for not following the procedure right
this device
Flash with CWM
daver18qc said:
Frequently Asked Questions:
1- "Flash with CWM" : If you still have the stock recovery, download and use Daver18qc's Root Kit Below to install CWM.
Click to expand...
Click to collapse
Well, couldn't the actual answer tell you exactly what you do once you've installed CWM...
I seem to have installed it — the Root Kit install finished successfully and there's one entry in Apps for "Superuser" that wasn't there before — but I can't actually do anything with it. How do you "Flash with CWM"?
---------- Post added at 11:16 PM ---------- Previous post was at 11:08 PM ----------
mertonv said:
Hi!
Thanks for pointing out where...
samsung-updates .com/device/?id=GT-S7560M
Im assuming this is the one im looking for
Galaxy Ace IIx GT-S7560M PGU S7560MUBAMG2
Unfortunately, the links on that site seem broken too... unless its me and i cant get them to work...
…
Can't seem to find the PGU anywhere... all links are to hotfile (which seems dead) or broken
thanks anyway...
Click to expand...
Click to collapse
AIUI, you don't need to use MG2. Try the third link (XSA) which will give you three options to download the MH3 firmware for Australia. That has three working download links.
IwasLegend said:
Well, couldn't the actual answer tell you exactly what you do once you've installed CWM...
I seem to have installed it — the Root Kit install finished successfully and there's one entry in Apps for "Superuser" that wasn't there before — but I can't actually do anything with it. How do you "Flash with CWM"?
Click to expand...
Click to collapse
You did it, since flashing with CWM puts the SUPERUSER program inside the phone. So if you have that, then you have indeed flashed with CWM, because it is the only way to flash the root package!
The instructions in the root kit apply to any other update/package that you want to flash with CWM.
IwasLegend said:
AIUI, you don't need to use MG2. Try the third link (XSA) which will give you three options to download the MH3 firmware for Australia. That has three working download links.
Click to expand...
Click to collapse
@mertonv:
Use Australia MH3 instead. SAMMOBILE got their hosting server shut down so the links for stock firmware are invalid, but they are supposed to get fixed soon, i hope.
EDIT: The Australia Stock ROM link works at the moment, maybe you didn't LOG IN / REGISTER on SAMMOBILE before trying to download and that's why you don't see anything, but at this time, it works !
Bluetooth and Camera still broken/buggy?
Can anyone confirm that there isn't a custom ROM (10.2 or 11) where there are issues with Bluetooth and the camera? I know the FAQ says there are issues but that was in October.
Service
Since flashing CM 10.2, I haven't been able to get service and if somehow I manage I only get it temporarily. Can someone explain as to why?
Downloading Australia MH3
When I go to download file, it takes me to http://terafile.co/5d8b16638748 and the problem is the download link isn't working for me. I do the captcha and everything but when it does to download it just doesn't want to download.
CasMz said:
When I go to download file, it takes me to http://terafile.co/5d8b16638748 and the problem is the download link isn't working for me. I do the captcha and everything but when it does to download it just doesn't want to download.
Click to expand...
Click to collapse
you have to keep refreshing(F5) until it goes to the download.
Does anyone try Triangle Away? is it complete safe?
miki89 said:
Does anyone try Triangle Away? is it complete safe?
Click to expand...
Click to collapse
It's been tested and it's safe, aside from the extremely slim risk of bricking your device while using Triangle Away (but I've never heard of anybody doing this). Chainfire hosts a free version here on XDA, although being free, it doesn't include every feature. But it works well enough.
there is any application or rom that Turn the hardware buttons light up when I have Missed calls or message?
ACE 2
thanks
thmls said:
there is any application or rom that Turn the hardware buttons light up when I have Missed calls or message?
ACE 2
thanks
Click to expand...
Click to collapse
If you are indeed using an Ace 2, we can't help you. This thread is one of the few for the Galacy Ace II X, a completely different device, other than similiar sounding names.
Speaking of BLN, I remember having recently seen an app that mimicks it very well. I'll message you if I remember what it was called.
For the BA2X 2.0, I'm working on implementing BLN in the kernel along with some other things. Our devices don't have the same kernel, but I could possibly create a universal BLN diff for others. I'm trying to diff a BLN module source for the Galaxy R and Captivate, so hopefully I can get it working.
Codename13 said:
If you are indeed using an Ace 2, we can't help you. This thread is one of the few for the Galacy Ace II X, a completely different device, other than similiar sounding names.
Speaking of BLN, I remember having recently seen an app that mimicks it very well. I'll message you if I remember what it was called.
For the BA2X 2.0, I'm working on implementing BLN in the kernel along with some other things. Our devices don't have the same kernel, but I could possibly create a universal BLN diff for others. I'm trying to diff a BLN module source for the Galaxy R and Captivate, so hopefully I can get it working.
Click to expand...
Click to collapse
So is the Kitkat update still being worked on or not? You say its being worked on in the first post but later say he's stopped. Also, are the bugs listed in black from flashing to Jelly Bean?
And lastly, can I use the Ace 2 GT-I8160 method of getting Kitkat for my ace 2x?
netnoob said:
So is the Kitkat update still being worked on or not? You say its being worked on in the first post but later say he's stopped. Also, are the bugs listed in black from flashing to Jelly Bean?
And lastly, can I use the Ace 2 GT-I8160 method of getting Kitkat for my ace 2x?
Click to expand...
Click to collapse
You're using an Ace 2 GT-I8160? This thread is for Galaxy Ace II X GT-S7560M. The two devices are completely different. The only reason that us Ace II X users use the Ace 2 forums is because the names are somewhat similiar. However, don't let that similiarity ruse you.
any kitkat?
Any chance that kitkat makes its way to this phone?...
If it were too... which stock should i load to my phone to be compatible with that?
Which custom rom on jb is the least buggy right now?
Thanks!
Shiny ROM: Android 4.4.4, KTU84P for Galaxy Nexus (Maguro)
Skip right to the downloads (if you dare )
Hello there XDA GNex community! I'll admit this is a pretty spontaneous post; I've been building ROMs from the Android Open Source (Project) for awhile now, but I've never "published" any of them. I myself used to own a Verizon Galaxy Nexus, so I've always built from AOSP to make sure I'm as up to date as possible. Well, that's a little background so let's get going with the overview of the ROM itself:
Overview
This ROM is Android KitKat 4.4.4, build KTU84P. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.
As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! So now for the details...
Features
Stock Android 4.4.4, build KTU84P
Source (AOSP) built kernel (boot.img)
Easily rootable (see information below)
G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
Stock browser replaced with Google Chrome
Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
All the crazy Google proprietary app stuff has been taken care off
Updated frequently
Everything works!
So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...
WiFi Tethering (no subscription check)
Bluetooth streaming
Google account sign-in and auto-restore of apps and settings
Google Wallet
Location Services (pretty fast GPS lock in my area also)
Photosphere
Android beam
Photo editing with the new filters
Email
Exchange support
Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
More things that aren't important enough to mention here - check out the changelog for a more comprehensive list
Possible Bugs
It's impossible for me to test for and notice EVERY single possible bug in the operating system, so as of right now I can't say that there are any, although I'm sure you will find some. If you do, report them here!
Other IMPORTANT Information
Root
But wait, nothing in this post said anything about root!!!11!!1!1!!! That's right, my ROM does NOT have root built in! (I don't use any root apps, and it's important to the whole "OTA-like" theme). That being said, the ROM is easily rootable; I made sure of this because I know that many, many of you will use root for many useful purposes. If you want to root the ROM, it's as easy as installing Chainfire's new superuser control app/su with this ZIP file. More detailed information can be found in the "Installation Instructions" section. **NOTE** If you are rooted and upgrading to a new build, you should not have to reflash the rooting flashable ZIP because the ROM will keep root for you.
Updates
Now that the ROM has gotten to this stage, the update policy needs a bit of editing Based on the stats I have access to from the website host and data that I collect myself, it seems like Shiny ROM is currently (as of May 27, 2014) stable for at least 80% of the users who have downloaded it. Based on this, and because the ROM is stock, Nexus-like, it doesn't really make sense to update the ROM as frequently as before. The ROM will still be updated as soon as possible after new versions of Android are released. In between Android versions, I will work on making things 100% stable, although that goal isn't always attainable with older devices and aging hardware support. If we decide to explore other paths for the ROM, you will see many more updates If/when the time comes for me to stop updating Shiny ROM, I will let everyone know in a clear way.
Radios
This ROM will (most likely) work with any maguro radios (so long as you have the appropriate ones for your device/area; however, I of course recommend using the most recent radios doe your device. You can find flashable ZIPs of all radio versions in the download post.
Bootloader
Once again, I'm assuming that this ROM will work with all tuna bootloaders; BUT for optimal experience and performance, use the newest Google-approved bootloader, PRIMEMD04. My ZIP installation package for that bootloader can be downloaded here.
ClockworkMod Recovery
I personally recommend using ClockworkMod Recovery as it has always worked well for me with no quirks. Android 4.2 messed up a few aspects of recoveries because of its multi-user system. ClockworkMod Recovery has been updated to correct some of these issues, and I recommend updating to the most recent version, 6.0.4.7. You can flash either the touch recovery or non-touch recovery image through fastboot OR you can download my flashable recovery update ZIP (touch/non-touch) and flash it in recovery. Check out the installation instructions for more details on this.
Some Other Not-so-important Information
Naming Conventions
All of my ROM ZIP files are automatically generated by my build computer. All builds begin with the prefix ShinyROM_maguro_aosp. That prefix is always followed by the date in mmddyy format (e.g. 112212), a hyphen ("-"), and the time in 24-hour, hhmmss format (e.g. 153945). Finally, all builds end with the "signed" suffix - it just helps me know which packages have finished building and which have not. Hopefully this helps everyone to know which update is newest; I stay away from version numbers because I let Google do all of the version control.
Source
In keeping with the spirit of open-source, all relevant Shiny ROM code can be viewed on Github. I'm not extremely experienced with Github, so bear with me as I learn! Thank you!
File Hosting
I've switched over from using Dev-host to a privately hosted site, graciously and generously given to me by user Goofball. Dev-host is still an amazing service, but it's much more convenient for me to use a privately hosted site, plus I get my own suburl and FTP access! HUGE thanks to Goofball! The private hosting will definitely help me deliver a better experience to you guys as far as downloading goes. You can view all of my uploaded, public files here: http://shinyrom.goofball.org/
Also, if anyone ever wants to mirror for me, please feel free so long as you keep the file name and the file itself intact. As for everyone who downloads from a posted mirror: BE CAREFUL! Always use a virus scanner and be careful with what you are putting on your device!
Installation Instructions (VERY IMPORTANT - Note: You can flash all of these ZIPs in CWM or TWRP*)
*Android 4.4 KitKat builds must be installed using the latest version of your preferred recovery!
ROM
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's SuperSU Root ZIP, radio installation ZIPs, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. If you are updating your radios, flash the radio ZIP
11. If you are updating your bootloader, flash PRIMEMD04-signed.zip
12. Flash the ROM (ShinyROM_maguro_aosp...signed.zip)
13. If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
14. Reboot your phone, and enjoy!
**Note: If you are simply upgrading to a new version of the ROM and want to keep root, follow the exact instructions above, and do not format /system. It really is not necessary to format /system at any time (unless specifically noted), as the ROM installer has this function built in.
Mods
1. Download the latest version of the mod(s) you wish to install from the download post.
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. Install the mod(s) you downloaded in step 1.
10. Fix permissions (not really necessary)
11. Reboot and enjoy!
**Note: You can remove all mods you've installed by dirty flashing the latest version of the ROM.
ClockworkMod Recovery (Fastboot method - must have an unlocked bootloader and fastboot in your path)
1. Download either the CWM touch recovery image or non-touch recovery image to your computer and rename it to "recovery.img".
2. Power off your phone.
3. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
4. Plug your phone into your computer using the standard USB cable.
5. Open the command prompt/terminal and navigate to the folder where your "recovery.img" is saved.
6. Type "fastboot devices" to make sure your phone is recognized; a serial number should show up on the screen.
7. Type "fastboot flash recovery recovery.img" and wait for the process to complete (should be quick).
8. You're done! Use the volume keys to select "Recovery" and boot into your new recovery!
ClockworkMod Recovery (Flashable ZIP method - easier)
If you are updating your recovery before flashing a ROM, these steps should ALL be completed PRIOR to flashing the ROM.
1. Download either the touch recovery flashable ZIP or the non-touch recovery flashable ZIP.
2. Place the ZIP file downloaded in step 1 on your internal storage/sdcard.
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Choose "Install update from sdcard"
7. Select "Choose file from sdcard"
8. Find the flashable recovery ZIP file you downloaded and install it
9. Back up to the root menu of recovery
10. Select "advanced"
11. Select "reboot recovery"
12. The phone should boot up into your new recovery!
Credits
As with most ROMs, I only did a small part to get everything together. Also, a note that should be made here is that when I am using someone else's file, I ALWAYS host files on the Shiny ROM server to ensure that I don't put any unnecessary stress on their servers. Any file, however, still belongs to and is accredited to its original creator as listed below:
Willyjay - For providing us with lots of amazing and innovative mods for the ROM!
Inmanster - Another great modder who we are fortunate to have here in the thread. He works in collaboration with Willyjay and his mods for many things, but also does some of his own unique mods!
Chainfire - For their SuperSU app and su binary, as well as the convenient ZIP update package, which was previously used and recommended. Check out their website, http://www.chainfire.eu/
Groupers - My new buddy who helped me out with a GPS issue that popped up in 4.2.
Google - Without their amazing staff and willingness to share the source code of their operating system, I wouldn't have been able to build this ROM! Of course, all of the Google apps are theirs, along with the Play Store and system apps. They really are the true owners of all of this.
Samsung - We all may have some mixed feelings about them, but in the end they gave us the amazing, hackable phone that is the Galaxy Nexus.
XDA - By providing such a great Android community, ROMs like this one are able to easily connect with users and get their work out there
Dev-Host - The file-sharing service with virtually no limits on sharing - kudos to them and their hard work. d-h.st
Koush and the ClockworkMod/ROM Manager Team - They make the best recovery that's been around for longest, and their constant updates allow us to keep making ROMs! Also, Koush's recently released open source Superuser control app is the best available and the one linked to in the thread. Thanks Koush! clockworkmod.com
Kevdliu - Huge thanks to this dev and their amazing quick settings mod!
The CyanogenMod Team - For a working implementation of DSPManager on Android which can be ported to any AOSP-based ROM! Without them and Bigwavedave25, the DSP manager mod would not be available! Be sure to thank them and to check out the CyanogenMod website! Also, for their feature-filled version of the stock Messaging app which is available as a mod for my ROM!
bouchigo - a user who has helped to make the CM10 Messaging app available as a mod for my ROM in conjunction with Willyjay for bringing it to my attention.
Schoat333 - A user who helped out Willyjay with the bubble styled MMS mods. The credit for the screenshots to go along with the mods goes to him!
Yarly - The most experienced admin I've ever had the pleasure of talking with, who taught me some new debugging tricks and answered some of my questions.
Razorloves - Another admin who helped me out with a few problems and answered a lot of my questions!
Tiny4579 - A kernel dev who also took the time to talk with me and answer a few of my questions.
Thanks to everyone for their hard work and sharing that work with others!
DISCLAIMER
Come on guys, it's a Galaxy Nexus, to what extent could it really get messed up? Nonetheless, in case someone flashes this then puts their phone in the microwave or something and tries to blame it on me, I am not directly responsible for anything that occurs, either negative or positive, from flashing this ROM to your phone. Despite that, I am posting in the spirit of the Android community, a community that I have embraced and belonged to for several years, and I would never try to hurt any of your innocent, beautiful phones. Also, none of the original source for Android belongs to me, nor do any of Google's apps. All preinstalled applications are property of Google, Inc. and I make no claim of ownership to them.
Okay that's about it! THE ROM DOWNLOAD LINK AND A SUMMARY OF ALL FILE DOWNLOADS CAN BE FOUND BELOW!
ROM Download & Changelog
ShinyROM_maguro_aosp_080914-130930-signed.zip
MD5: c13636212d98b7272a6c8155ce61ac0a
Fixes/Changes Included So Far
(older changes)
6/21/14 CHANGES
Updated to Android 4.4.4, KTU84P
8/9/14 CHANGES
Added system-side support for native screen casting
Added Italian translations for the Shiny restart menu (courtesy of XDA user lparcshinoda)
Mods
Before installing any of the packages below, please be sure to check out the mod installation instructions in the OP!
Key
To make mod installation more convenient, all mod links will now be color-coded based on the files they change. The key shows what each color corresponds with:
Red - SystemUI.apk
Blue - framework-res.apk
Purple - SystemUI.apk & framework-res.apk
Green - Other
If you install mods that are in the same color group, it is likely that they will overwrite each other. It is OK to overwrite a previously installed mod, but please note that the originally installed mod will no longer be there. If you want to completely revert to stock, flash the "Back to Stock ZIP" mod under the baldwinguy77 mod section. This mod replaces your SystemUI.apk and framework-res.apk files with ones from the stock ROM.
Developer-specific Mods
All of these mods have been provided by some really awesome mod developers who take the time to continue to make updated mods for my newest ROM builds. That being said, they have lives and can't always get the mods out right away, so make sure the date next to their name matches the build you're running! They usually are around the thread and are open to doing custom mods if you ask Be sure to thank them and check out the credits section for more info!
Baldwinguy77 (Updated for 8/9/14 build)
Back to Stock ZIP - Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Stock kernel flashable ZIP - Overwrites any custom kernel you have installed with the stock kernel normally packaged with the ROM.
Inmanster (Updated for 3/9/14 build)
36 DPI Nav. Bar - Replaces the stock navigation bar with a smaller (height-wise), 36 DPI version.
Black Dash-style Softkeys - Replaces the stock navigation bar buttons with black, dash-style ones.
Blue Stock Softkeys - Replaces the stock navigation bar buttons with blue-colored ones.
Carrier Text Replacement - Replaces the carrier text on the lockscreen and pulldown notification shade with "Galaxy Nexus".
Extended Battery Framework Mods - Improve accuracy of battery level reporting for those using extended batteries.
2100 mAh (with Carrier Text Replacement mod)
3050 mAh
3800 mAh
5900 mAh (with No CRT-off Animation mod)
Grey Battery Percentage - Enables display of the current battery percentage in the status bar with grey-colored font.
InmanMod - A combination of the 2100 mAh battery, no CRT-off animation, carrier text, 36 DPI nav. bar, and white zenyth softkeys mods.
No CRT-off Animation - Removes the stock, default CRT-like screen off animation.
White Zenyth-style Softkeys - Replaces the stock navigation bar buttons with white, zenyth-style ones.
Universal Mods & Downloads
These mods have been compiled by myself, sometimes in conjunction with the modders above, to always work with any version of the ROM (but not necessarily any device). Therefore, you don't have to worry so much about these being up-to-date because they should always work. If that is ever not the case, simply PM me and we'll get it fixed This section also includes some other Verizon Galaxy Nexus related downloads such as the latest radios and bootloader. You can use these according to the installation instructions in the OP.
Universal Mods
AOSP Web Browser (for Android 4.4) - Installs the AOSP web browser with Chrome bookmark syncing for Android 4.4.
DSP Manager (for Android 4.4) - Installs the DSP Manager app along with the audio libs and configs important to running the service, allowing you to customize the audio equalizer of your device. At the moment, certain apps on Android 4.4 do not work with the modular DSP service.
ClockworkMod Images
Touch 6.0.4.7
Non-touch 6.0.4.7
ClockworkMod Recovery Flashable ZIPs
Touch 6.0.4.7
Non-touch 6.0.4.7
Chainfire's SuperSU Root Control App and ROOT Flashable ZIP (Works with 4.3 & 4.4)
Download (Latest version, v2.02)
Maguro Radios
Australia + Oceana - GT-i9250T
DVKK6
DVLE1
DVLF1
DVLH1
International (Europe) - GT-i9250
XXKK1
XXKK6
XXKL1
XXLA2
XXLF1
XXLH1
XXLJ1
International (South America) - GT-i9250
UIKL3
UILE1
UILH1
Japan + Pacific Asia - SC-04D
OMKKD
OMLA1
OMLE3
North America - GT-i9250M
UGKK7
UGKL1
UGLA4
UGLC1
UGLH1
UGLL1
South Korea + East Asia - M420
KRKK7
KRKL1
KRLB1
Tuna Bootloaders
PRIMEMD04 Bootloader Flashable ZIP (Latest)
PRIMELC03 Bootloader Flashable ZIP
Also just want to make it clear that to anyone who tested the 2/8 maguro build for me, the 2/9 one is the same!
The real deal.
Thanks.
Sent from my Galaxy Nexus using Tapatalk
No GApps "Add-on" Zip
Some people don't like the way ShinyROM includes its own GApps. Flash this zip directly after the ROM and it will strip out most of the included GApps so that you may use the preferred GApps of your choosing. This will leave the core GApps (Store, Services, etc.) as well as any others required for basic functionality (Keyboard, Camera, Launcher, Dialer, etc.) since there are none of the AOSP counterparts included.
This is particularly handy for GApps packages that try to measure the free space and may fail to install if it feels there isn't enough room.
Enjoy!
Finally! Boom!
Sent from my Galaxy Nexus using Tapatalk
osm0sis said:
I'll just copy this from the other thread.
No GApps "Add-on" Zip
Some people don't like the way ShinyROM includes its own GApps. Flash this zip directly after the ROM and it will strip out most of the included GApps so that you may use the preferred GApps of your choosing. This will leave the core GApps (Store, Services, etc.) as well any others required for basic functionality (Keyboard, Camera, Launcher, Dialer, etc.) since there are none of the AOSP counterparts included.
cwm-ShinyROM-No.GApps.Addon.zip:
View attachment 2559059
Click to expand...
Click to collapse
Thanks! I'll add this to the OP when I get a chance
baldwinguy77 said:
Thanks! I'll add this to the OP when I get a chance
Click to expand...
Click to collapse
No worries! I actually love having the GApps included, but a lot of people were fussing about it in Sesme's port thread so I thought I'd help out.
Also if you're interested, on xda here we've got a complete maguro radio thread and CWM thread I maintain:
[REF] [RADIO] [GSM] Galaxy Nexus GT-i9250 Baseband Collection & Discussion
[RECOVERY] [GN] [GSM] ClockworkMod Recovery Official + Nightlies [Flashable Zip]
:good:
Is this rom lagging for anyone? Right after I flash it I can't even pass the Setup Wizard ..
Just awesome man! The port was already the best ROM. Pure stock, and I can tell you, it's blazing fast!
osm0sis said:
No worries! I actually love having the GApps included, but a lot of people were fussing about it in Sesme's port thread so I thought I'd help out.
Also if you're interested, on xda here we've got a complete maguro radio thread and CWM thread I maintain:
[REF] [RADIO] [GSM] Galaxy Nexus GT-i9250 Baseband Collection & Discussion
[RECOVERY] [GN] [GSM] ClockworkMod Recovery Official + Nightlies [Flashable Zip]
:good:
Click to expand...
Click to collapse
Thank you! I actually downloaded all of these the other night and uploaded them to my server I just need to update the OP with a list
baldwinguy77 said:
Thank you! I actually downloaded all of these the other night and uploaded them to my server I just need to update the OP with a list
Click to expand...
Click to collapse
Haha cheers! I'll add you as a mirror.
BIG work!!!
Inviato dal mio Nexus 5
Great work man！
Official build both on toro and maguro now,could you make one for toroplus？
We need your awesome rom！
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Awesome! Exactly what we need.
Giving this ROM a go.
Nice to see its official now. But on post #1 there are some reference to rootzwiki as xda and I know its probably a copy+paste thing that's why. Just pointing it out
Sent from my Galaxy Nexus using Tapatalk
JustinXu said:
Great work man！
Official build both on toro and maguro now,could you make one for toroplus？
We need your awesome rom！
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey there! I'd love to push out builds for toroplus as well - I think it's safe to say that's next in the pipeline.
akash3656 said:
Nice to see its official now. But on post #1 there are some reference to rootzwiki as xda and I know its probably a copy+paste thing that's why. Just pointing it out
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Oops! I thought I got all of the necessary edits but I missed the one right at the beginning! *Facepalm* Thank you for pointing that out - it's fixed now
Are those battery Extended Battery Framework zips compatible with maguro? I downloaded them from toro's RootzWiki thread a while ago and they were giving me a bootloop
Also, can I use them with other ROMs?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
I've read that it's not possibile to flash ROM over a stock 4.3 rom.
Someone can confirm this? Also if I wipe /cache partition and Dalvik cache?
Investigating it seems that zip file contains an update script which only overwrites the entire /system mount point.
So, what are the consequences of updating ROM over a stock 4.3 rom?
osm0sis said:
I'll just copy this from the other thread.
No GApps "Add-on" Zip
Some people don't like the way ShinyROM includes its own GApps. Flash this zip directly after the ROM and it will strip out most of the included GApps so that you may use the preferred GApps of your choosing. This will leave the core GApps (Store, Services, etc.) as well any others required for basic functionality (Keyboard, Camera, Launcher, Dialer, etc.) since there are none of the AOSP counterparts included.
cwm-ShinyROM-No.GApps.Addon.zip:
View attachment 2559059
Click to expand...
Click to collapse
@osm0sis
If I simply add to "gapps list" in your zip the apps I do not want to be flashed, will it work?
Something like that:
Code:
/system/app/BasicDreams.apk
/system/app/BasicDreams.odex
/system/app/Books.apk
/system/app/CalendarGoogle.apk
/system/app/Chrome.apk
/system/app/CloudPrint2.apk
/system/app/Drive.apk
/system/app/EmailGoogle.apk
/system/app/EmailGoogle.odex
/system/app/Exchange2Google.apk
/system/app/Exchange2Google.odex
/system/app/FaceLock.apk
/system/app/GenieWidget.apk
/system/app/Gmail2.apk
/system/app/GoogleEars.apk
/system/app/GoogleEarth.apk
/system/app/GoogleTTS.apk
/system/app/Hangouts.apk
/system/app/HPPrintPlugin.apk
/system/app/Keep.apk
/system/app/LiveWallpapersPicker.apk
/system/app/LiveWallpapersPicker.odex
/system/app/Magazines.apk
/system/app/Maps.apk
/system/app/Music2.apk
/system/app/Nfc.apk
/system/app/Nfc.odex
/system/app/PlayGames.apk
/system/app/PlusOne.apk
/system/app/PrintSpooler.apk
/system/app/PrintSpooler.odex
/system/app/QuickOffice.apk
/system/app/Street.apk
/system/app/SunBeam.apk
/system/app/Videos.apk
/system/app/YouTube.apk
/system/priv-app/GoogleFeedback.apk
/system/priv-app/GooglePartnerSetup.apk
/system/priv-app/MusicFX.apk
/system/priv-app/MusicFX.odex
/system/priv-app/TagGoogle.apk
/system/priv-app/TagGoogle.odex
/system/priv-app/talkback.apk
/system/priv-app/Velvet.apk
/system/priv-app/Wallet.apk
MultiROM lets you install multiple ROMs into subfolders, just by flashing them using a modified TWRP.
This is an unofficial port of MultiROM originally developed for the Nexus series to our beloved TF300T.
Big thanks @Tasssadar for the original work!
THIS IS AN EARLY VERSION OF THIS PORT, NOT ALL FEATURES ARE FULLY TESTED.
But please test and give feedback, so I can eventually remove above line.
Features
Run a primary Android ROM from the normal partitions.
Run multiple secondary ROMs from subfolders on an SD card or on an external USB stick/drive.
Easily add/update your primary and secondary ROMs using a modified version of TWRP.
Install Ubuntu and Ubuntu Touch as secondary ROMs Not supported yet.
And more...
Changes vs. official MultiROM
This section is mostly useful for people using MultiROM on another device. New users can safely ignore it.
My first test - installing a plain CM 11, installing MultiROM, and then installing OmniROM with its own kernel - failed gloriously. The reason was that the official MultiROM re-uses the kernel of the currently installed Android system and that kernel does not include the kexec hardboot patch required for MultiROM to work properly.
The beauty of MultiROM is that - once installed with a proper kernel - it allows an average user that has never heard about kexec and never installed a custom kernel to run multi-boot at the touch of a finger. So I decided that my first simple use case must be supported.
The obvious solution was to ship a working kernel with MultiROM, save the currenly installed kernel for the primary ROM and boot that via kexec. The idea is to sacrifice another 10 secs on booting the primary ROM for making MultiROM much easier to install and to use. However, this decision led to several changes in the TWRP user interface:
The "share kernel with primary ROM" option was removed. Each ROM has its own boot image and is always booted via kexec.
The "Inject current boot sector" on the MultiROM screen button was replaced with a "Reinstall" button. Use this, if you have overwritten the boot sector, for example via fastboot. Mind, reinstalling MultiROM will save the current boot partition and use it for booting straight into the primary ROM, so better make sure this works, before running reinstall, or you won't be able to boot into your primary ROM after reinstallation.
The "Add/Remove boot.img" button on the ROM management screen has been replaced with "Replace boot.img" and can be used to easily install a custom kernel for that ROM.
Looking forward to your feedback on this major change!
Downloads
Downloads are available from the "Downloads" tab at the top of the page.
MultiROM installer including the modified TWRP:
multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.zip
TWRP for MultiROM (not needed, if you use the installer):
twrp-multirom-vXX-YYYYMMDD-UNOFFICIAL-tf300t.blob
Installing and Upgrading MultiROM
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet. The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet. I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Make a backup!
MultiROM will modify your system, and if anything goes wrong, this backup will be more than helpful.
Check the version of your bootloader.
On the bootloader screen, check the version shown on the top left. MultiROM was ported and tested on version 10.6.1.27.5. If your bootloader version is 10.6.1.27.1 or 10.6.1.15.3 you should have no issues. Version 10.6.1.8 might work, but is likely to cause issues; upgrading is highly suggested. For any other version, make sure you first upgrade your bootloader, or you risk ending up with a brick,
Flash the lastest multirom-vXX-YYYYYYYY-UNOFFICIAL-tf300t.zip
Reboot right away!
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Now you should be able to boot your primary ROM via MultiROM. For next steps, check out "Installing ROMs" in the next post.
Uninstall MultiROM
The uninstaller for the official MultiROM has not been ported yet, but you can get rid of MultiROM following these steps:
Flash your favourite (not MultiROM) recovery.
Restore your boot partition from a backup or re-flash your ROM.
Remove the "multirom" folder on the sdcard.
The latter is optional. You may keep it around for trying MultiROM again later.
Changes
2014-03-16:
Fixed MultiROM reinstallation from TWRP.
Some fixes for swapping primary/secondary ROMs.
Some fixes for primary ROM initrd.
Added support for Ubuntu Touch (needs upcoming manager app).
2014-03-02:
Support secondary ROMs on SD card (not fully tested).
Use packaged initrd instead of the primary ROM's.
Some bug fixes.
2014-02-13:
Allows flashing 4.2-based ROMs without removing the assert line in the updater-script.
Several bug fixes for more stability.
Note that changes may be documented, before the downloads are available. Please check back a little later in that case.
Future Work
In no particular order:
Provide uninstaller.
Add the missing features listed above.
Fix TWRP for encrypted filesystems.
Allow replacing the kernel for any ROM, keeping the ramdisk.
Remove unnecessary drivers (net, sound, camera) from the kernel (currently breaks building the kernel).
XDA:DevDB Information
MultiROM for TF300T, a Tool/Utility for the Asus Transformer TF300T
Contributors
f69m
Version Information
Status: Alpha
Created 2014-02-11
Last Updated 2014-03-16
Installing ROMs
Custom 4.2- and 4.4-based ROMs
To install/update your primary ROM, just flash it as usual with the modified MultiROM TWRP, using "Install" from the main screen.
Installing a secondary ROM is just as easy, but use:
Advanced > MultiROM > Add ROM
You can update a secondary ROM by flashing it from the ROM management screen, using;
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
OTA updates using the update manager coming with your ROM should work fine for both primary and secondary ROMs.
Note: It is no longer necessary to remove the assertion from a 4.2 updater-script.
Gaps, SuperSU, etc.
You can flash additional ZIP files for a secondary ROM from the ROM management screen, using:
Advanced > MultiROM > List ROMs > [select your ROM] > Flash ZIP
Asus Stock ROM
Asus stock ROM has a different installer and won't work the same way as custom ROMs.
Here are the steps to install stock ROM as your primary ROM:
Sorry, I have not tested this myself yet, please let me know, how it works out.
Unzip the Asus ROM twice to get the blob.
Flash the blob using fastboot.
Boot into stock ROM.
Re-install the modified TWRP using fastboot (use the separate download).
In TWRP: Advanced > MultiROM > Reinstall.
This should give you a working MultiROM setup with stock ROM as your primary ROM.
If you need more detailed instructions on the first two steps, please refer to the guides in the General section.
Ubuntu Touch
Coming soon...
Ubuntu
Not working yet.
Notes on Specific ROMs
CROMi-X 5.3
Don't try to install CROMi-X as a secondary ROM. It has an amazing installer, but that will nuke your primary ROM's /system partition.
Trouble-shooting
If your primary or one of your secondary ROMs is not booting properly, it can help to restore the boot partition of the primary ROM and then do a clean reinstall of MultiROM.
No worries, you can move your installed secondary ROMs to the side and move them back later.
First try restoring the boot partition from your latest backup, before installing MultiROM and reboot.
If your device boots cleanly into your primary ROM, without showing the MultiROM boot screen, you can skip ahad to step 3.
Next try flashing an unmodified recovery, re-flash your primary ROM and reboot.
If your device boots cleanly into your primary ROM without showing the MultiROM boot screen, you are ready to go to step 3.
Otherwise you should post your issue.
Use a root terminal or a root exlorer to remove the folder /data/media/0/multirom.
Alternatively you can rename that folder, keeping your installed ROMs.
Note: though this folder is on the sdcard, you have to use the path given; trying to use /sdcard or /storage you will get "permission denied", when trying to remove or rename the folder.
Reflash the latest multirom-v*.zip and reboot.
Make sure you see the blue progressbar on the first boot screen and you see another automatic reboot.
Then the MultiROM boot screen should show up.
Try booting your primary ROM. It should now start cleanly.
Try installing a secondary ROM, or move it back to /data/media/0/multirom/roms/ from the folder you renamed above.
Just moving back the folder will make it show up on the MultiROM boot screen.
Please read and follow each step carefully.
If these steps do not make all your ROMs boot properly, please post about your issue in this thread.
Source Code Repositories
The easiest way to build MultiROM is using my manifest following the build instructions below.
Here is a list of the MultiROM-specific repositories that can be built by adding them to the OmniROM tree:
Latest manifest:
https://github.com/f69m/android
MultiROM (check out to "bootable/multirom"):
https://github.com/f69m/multirom
TWRP for MultiROM (check out to "bootable/recovery"):
https://github.com/f69m/multirom-twrp
libbootimg (check out to "external/libbootimg"):
https://github.com/Tasssadar/libbootimg
TF300T device config (check out to "device/asus/tf300t"):
https://github.com/f69m/android_device_asus_tf300t
TF300T kernel (check out to "kernel/asus/tf300t"):
https://github.com/f69m/android_kernel_asus_tf300t
Look out for branches named "multirom-*" in above repositories.
Please check the manifest for the latest stable branch.
Build Instructions
Using my manifest makes it easy to check out the MultiROM repositories and a small part of the OmniROM tree needed for building.
Code:
repo init -u git://github.com/f69m/android -b multirom
repo sync
manifest/pick-cherries.sh
source build/envsetup.sh
lunch mrom_tf300t-userdebug
make -j4 multirom_zip
Sweet! Thanks man, this looks pretty cool!
Sent from my SGH-T999 using xda app-developers app
Finally, first download is up!
Let me know, how it works for you.
Thanks for your work.
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??
z1022 said:
Now I use CROMi-X 5.3 ROM. If I install MultiROM and TWRP for MultiROM, the exist CROMi-X 5.3 ROM can keep on primary ROM??
Click to expand...
Click to collapse
Absolutely, just flash the multirom-*.zip file (includes TWRP), and you should be able to boot into CROMi-X via MultiROM.
But I have not tested with CROMi-X yet, so make sure you have a backup!
Sent from my TF300T using Tapatalk
Thanks
I will try later and report back.
CROMi kernel should be not included the kexec. Can I use the Multirom to install second ROM ??
z1022 said:
I will try later and report back.
Click to expand...
Click to collapse
Great, looking forward to hearing about your experiences.
CROMi kernel should be not included the kexec.
Click to expand...
Click to collapse
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Can I use the Multirom to install second ROM ??
Click to expand...
Click to collapse
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk
Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
As Primary ROM i have NIGHTLY CM11 for TF300T. As "virtual" ROM i installed the same ROM (i want to examine the new GRIMKERN_KitKat).
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.
Dasdranamin said:
Hi f69m!
1000 THANKS!
I successfully installed this MultiROM on TF201 with bootloader from TF300T v. 10.6.1.27.1 ! :laugh:
Click to expand...
Click to collapse
Wow, amazing!
All works properly with 1 exception:
Don't works the touchscreen during "blue" window for ROM-selection.
So I had to specify the "default" firmware in TWRP.
Click to expand...
Click to collapse
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Sent from my TF300T using Tapatalk
f69m said:
Wow, amazing!
Hmm, not quite sure, what you mean with "blue" window. You mean the MultiROM menu that comes up after boot? If yes, could you send me a copy of /proc/last_kmsg after booting your ROM? It has the kernel log of MultiROM; maybe I can spot the issue there.
Click to expand...
Click to collapse
Yes. That's what I meant.
Dasdranamin said:
Yes. That's what I meant.
Click to expand...
Click to collapse
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Sent from my TF300T using Tapatalk
f69m said:
Thanks for the log. It is a different touchscreen, but don't see anything that should cause issues.
In TWRP touch is working fine?
Click to expand...
Click to collapse
Yes, in TWRP touch works without any problem!
I'll have a look at the differences in the input handers and will probably send you a special version with more logging.
Click to expand...
Click to collapse
That would be great! Thanks in advance!
f69m said:
Great, looking forward to hearing about your experiences.
The CROMi-X kernel does not need kexec for my MultiROM port to work. This is different from the official MultiROM for Nexus. See post #1 on more details.
Of course, that's the whole idea!
Check post #2 for instructions.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
I successfully installed just now on TF201 Omni 4.4.2. ROM TF300T Homebuild versions [20140126] (it's last ROM with MultiWindow feature) + Gapps Mini Modular Package.
All works properly. :good: MultiWindow too.
how long omni finished the booting.
---------- Post added at 11:59 PM ---------- Previous post was at 11:50 PM ----------
z1022 said:
Install MultiROM and try to install Omni 4.4.2. ROM in second. However, stick in OMNI booting Screen.
Click to expand...
Click to collapse
Try CM11 in second ROM. still stick in CM11 booting screen.
z1022 said:
how long omni finished the booting.
Click to expand...
Click to collapse
First time about 5 min (with Gapps).
Next times about 2 min.
Nice! cant wait to try this, thanks for your hard work!
Hi f69m,
I found: in "MultiROM menu that comes up after boot" I can select a ROM by VOLUME UP/DOWN and confirm by POWER (like in "old" CWM). :laugh:
Please read the changelog as it will be updated constant before posting.
* Screenshots: Post #3
* Download and Installation: Post #2
* Please do not report issues/enhancements here, use the issue tracker here
* ChangeLog and Features
MUST READ
Click to expand...
Click to collapse
* Absolutely NO XPOSED F/W or Modules supported. This is a daily driver ROM, with deep integration and modification of stock (Samsung) ROM, hence things will break, I assure you!. See FAQ for more detailed explanation as to why I will NOT support it.
* Do NOT install ChainFire SuperSU, as the ROM has built-in CM/Koush Superuser, which I will manage and update if necessary. (And SuperSU completely messes your system binaries, I have no idea what else is botched hence I will NOT support it).
* Follow the DEV thread rules, this IS a dev thread, if you cannot give possible debugging information (logcat, proper replication of the scenario) do NOT post here, go to the general thread here (TODO add link).
* I will only support Stock Kernel (it is included in the DOWNLOADS section), if you are having issues, I would recommend full wipe, flash ROM and flash the STOCK Kernel, reproduce the issue and use my github issue ticketing to report it.ISSUE Reporting Link
* This is daily driver stock themed ROM, if this is NOT what you are looking for I advice you to STOP and move on to another ROM, save that precious bandwidth.
* As this is distributed as a TWRP recovery install file, your KNOX is already at 0x1, duh! don't bother wasting a post whether it will trip KNOX or not.
* Since your KNOX is tripped, removed all KNOX bits does not make any sense.
* Do not ask for ETA, if and when time permits I will release any updates if there are. Use my github issue ticket tracker for any updates to issues. As I am pretty sure the thread will get derailed (and I will only watch it as time permits), creating an issue ticket is your best bet that it will get my attention.
* NO DPI changes supported, although it is available in Settings. A lot of MI7 TW apks are not built for multi-dpi and since I don't support xposed, you are on your own.
* Since the ROM is designed with SELinux Enforcing kernels like Stock Kernel, which also has additional restriction of not allowing adb root. ROM comes built-in with SSH enabled and defaults to root user. You can use the ssh add key in Settings -> Device -> Misc Device Settings to add the key and you can do all the operations untethered .
What is Embryo?
Click to expand...
Click to collapse
In short EMBRYO is your stock/OEM (samsung UVUBMI7 base) ROM, which will have the full support of you hardware (which will be very difficult for any after market ROM to achieve) overlayed with after market (CM/AOKP/SLIM) ROM features as time permits and which fancies my attention .
Needless to say, this is a extremely difficult task and requires very precise skill,understanding of a lot of moving parts (hence the MUST READ section entries) and a lot of patience (I mean a lot). Also I am a stickler for quality and it will show!.
Absolutely NO PERMISSION is given to post this in any other thread or kanging the work.
THEME
Click to expand...
Click to collapse
In the past I have themed EMBRYO roms, but due to time constraints this does not look like a possibility right now, maybe some time in the future. If any themers are willing to take a crack at it go for it and let me know, I will add the links here.
ChangeLog/Features/FAQ
Click to expand...
Click to collapse
They will all be logged here and updated as time permits:
* ChangeLog and Features
* FAQ
* Home Page
02-MAR-2014: EMBRYO-1.1
* bug fix: StatusBar data icon persistence
* bug fix: init.d scripts toggles were not taking effect.
* fix: removed custom carrier label preference.
DISCLAIMER
Click to expand...
Click to collapse
You are assuming all the risk for flashing this. You have been warned.
ISSUES
Click to expand...
Click to collapse
* NavBar transparency requires more work, so it will not work.
* Stock launcher in landscape layout needs fixes when navbar is enabled. I will take any patches
CREDIT
Click to expand...
Click to collapse
- Samsung for the UVUBMI7 base.
- Koush for Superuser (note: I have built it myself to ensure it works with TW roms)
- CM/AOKP/Slim aftermarket ROMs for borrowing various settings code and various inspiration
for adapting Samsung Implementation.
- Paul for the built-in File Chooser.
- Ericson for RootTools
XDA:DevDB Information
EMBRYO-NOTE3, a ROM for the T-Mobile Samsung Galaxy Note 3
Contributors
mohan_kr
ROM OS Version: 4.3.x Jellybean
Based On: TouchWiz - UVUBMI7
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2014-02-23
Created 2014-02-24
Last Updated 2014-02-23
Installation and Download
FULL ROM INSTALLATION
Click to expand...
Click to collapse
PLEASE FOLLOW THE STEPS EXACTLY AND IN THAT ORDER, do not try to be cute and invent your own process, nothing good is come out of that. Also, the only recovery I have tested is TWRP, no other recovery has been tested, so the installation instructions are tailored for TWRP only.This is full WIPE ROM Instructions, do NOT dirty flash it is NOT going to work.
Step 0) Make sure you are unplugged and fully charged (no USB or power)
Step 1) Make a Nandroid backup and better yet also TiBu if you need to restore apps.
Step 2) Did you do Step 1)???? Do it now, already.
Step 3) Make sure you downloaded the Full Wipe ROM on to your device.
Step 4) Please make sure to check the md5sum's.
Step 5) Boot into TWRP recovery.
Step 6) Select Wipe -> Swipe to Factory Reset
Step 7) Go Back to Wipe Screen -> Advanced Wipe -> Select System -> Swipe to wipe
Step 8) Did you do Step 6, 7? If not, STOP, do NOT proceed.
Step 9) Go Back to Main Screen -> Select Install Tile
Step 10) Select the Full Wipe ROM zip and flash.
Step 11) [OPTIONAL] If you need any bloat zips and add-ons if available add them now.
Step 12) [OPTIONAL] If there are any EMBRYO Update Zips you can add them now. (SHOULD BE LAST ONE ADDED)
Step 13) I Strongly recommend to Flash the Stock Kernel (MI7), the zip is in the Downloads
section.
Step 14) Good, now reboot and LET IT WAIT till everything is installed. Do NOT touch and mess around with any keys. Your installation should be fine, if you see the bootanimation and then installing applications screen shows up.
Step 15) At this point you might be prompted to allow SuperUser access to ROMCustomizer, select
allow.
Step 16) IMPORTANT Follow Any POST Installation stuff below.
EMBRYO UPDATES INSTALLATION
Click to expand...
Click to collapse
Installation is simple, as the update zip will be available as a TWRP flashable zip. Download to your device, boot into recovery and select install. That's it. If there are any special instructions, they will be in the section where the download zip is available.
POST INSTALLATION
Click to expand...
Click to collapse
Please do the following, after a full wipe installation. After the ROM boots:
1) If you missed the Superuser prompt for ROMCustomizer, please got to Superuser app and
grant privileges to ROMCustomizer.
2) Please NO restoring of system data that is a surefire way to bork the shiny new system.
3) SSH is enabled by default. To upload a public key, push it to your SDCARD and then go to Settings -> Device Tab -> Misc Device Settings -> Add Ssh Key.
DOWNLOADS
Click to expand...
Click to collapse
ROM
Click to expand...
Click to collapse
* [24-FEB-2014] [EMBRYO-1.0]: Please check the MD5SUM for all downloads on YOUR phone (not on the PC e.g). Please follow the installation instructions.
- SM-N900T-EMBRYO-1.0-FULL.zip
ROM UPDATES
Click to expand...
Click to collapse
* [02-MAR-2014] [EMBRYO-1.1-Update]: Please check the MD5SUM for all downloads on YOUR phone (not on the PC e.g). Please follow the installation instructions for updates in the section EMBRYO UPDATES INSTALLATION
- EMBRYO-1.1-update.zip
STOCK KERNEL
Click to expand...
Click to collapse
* [UVUBMI7] Stock Kernel TWRP flashable. SM-N900T-STOCK-UVUBMI7.zip
BLOAT
Click to expand...
Click to collapse
* [UVUBMI7] Samsung Bloat. APKS that are not installed as part of EMBRYO full rom. NOTE they are installed in system partition.
- UVUBMI7-Samsung-Bloat.zip
* [UVUBMI7][TMO] T-Mobile Bloat.
- UVUBMI7-TMO-Bloat.zip
Click to expand...
Click to collapse
Screenshots
See the attached thumbnails to this post.
Another One
final one.
Upload
Upload in Progress..as soon as it is up I will create a post. Patience.. see post #2.
This sounds like you out a ton of work into it. I definitely must give this a run.
Sent from my SM-N900T using Tapatalk
Download link
Post #2 has the download link..I will update the changelog/features to give more information on how to use the ROM. Enjoy!
mohan_kr said:
Upload in Progress..as soon as it is up I will create a post. Patience.. see post #2.
Click to expand...
Click to collapse
downloading now. . . feedback will follow
http://www.androidfilehost.com/?fid=23329332407573846
That's for the kernel for some reason the link you put there say's access denied when you go on it.
Sent from my SM-N900T using xda app-developers app
This is very very good. I really have no issues yet. It has a remarkable "wow" factor, even when installing. Very well done.
Sent from my SM-N900T using Tapatalk
Great job on this Rom!
Sent from my SM-N900T using XDA Premium 4 mobile app
Uploaded zip
Uploaded all the Samsung and T-Mobile APKS that are not included as part of the ROM. By default they will be installed in system partition. Since I did not investigate fully what can be moved to data. If you know that you can push the apks in /data/embryo/preload and use the Package Management from Settings -> Device to install them..
Is anyone running this how is it?..
Sent from my SM-N900T using Tapatalk
demon28 said:
Is anyone running this how is it?..
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
so far . . no issues here...
Question, can you go back to 4.3?
Sent from my SM-N900T using Tapatalk
demonchildfp said:
Question, can you go back to 4.3?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Rom is 4.3
Yep.....I feel like a retard......
Sent from my SM-N900T using Tapatalk
Wow - this is quite a piece of work here. Had to take it for a spin - no issues to report but wanted to pop in and say holy crap man, this is awesome! The navbar stuff alone... it makes my head hurt. Far better than anything I could ever muddle together that's for sure. Glad you finally got the time to share this - work like this doesn't come around very often, so for that I say - thanks!
Great job man!
Downloading now.. maybe I can find some time and see if my themes are compatible and if not I can make em compatible. Sounds like a awesome rom
Does anybody have a copy or link to the stock kernal? It says access or no such file on the link provided in the o.p. thanks