About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
http://goo.im/devs/carbon
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
How-To "Safestrap" (Just copied from Hascode's blog)
It is highly recommended to install rom derived from the CyanogenMod or other AOSP based roms only on slot1
Download SafeStrap 3.11.apk here: http://goo.im/devs/Hashcode/spyder/Safestrap-RAZR-D4-BIO-3.11.apk
[ New Safestrap v3.04 Video by DMX: http://www.youtube.com/watch?v=q-qK7kL0W3o&feature=youtu.be ]
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.2.2.1 (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 (up to 4) 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.
IF COMING FROM A PREVIOUS VERSION OF SAFESTRAP (v2.x):
You will want to move the entire “/sdcard/safestrap” directory to the external SD card (/sdcard-ext). These are your backups and in a catastrophic situation you could revert to Safestrap v2 and use them.
Go into the existing version of Safestrap and use the “Remove Recovery” button to remove the Safestrap files from the stock /system.
And lastly, remove the APK from the device as you would any other app.
HOW DO I INSTALL SAFESTRAP?
Download the Safestrap APK from here.
Find the APK using a Filemanager tool and open it on your device, then click “Install”.
(If updating from an existing Safestrap v3 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
SAFESTRAP RECOVERY (v3):
As of version 3.0, Safestrap Recovery is now based on TWRP 2.2.2.1. 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.
MAIN MENU:
Boot Options: This area is for managing your virtual ROM-slots. You create a new ROM-slot by clicking on one and if it doesn’t exist you will be prompted to create it. Follow the on-screen guides. Once a ROM-slot is created you select that slot to activate or delete it. Under each ROM slot (once created) you can:
Activate: Makes the chosen ROM-slot the “current” one, where almost all of the features of TWRP affect that slot. This will also be the ROM that is booted.
Set Nickname: For convenience you can set a small name for each ROM-slot. This is limited to 10 characters as it will eventually be added to the beginning of backup names. This name is shown on the ROM-slot button once it is set.
Fix FS (coming in the future, if needed) This could potentially be a button to perform file system checks on the ROM-slot and fix any errors found.
Delete: Delete the ROM-slot files (disabled if the ROM is active — please choose another ROM-slot to activate and then come back) USE WITH CAUTION, THERE’S NO GETTING THESE BACK UNLESS YOU HAVE BACKUPS.
Install: This is for flashing a .zip file to the currently active system. Currently, this is disabled for the stock system. In a future release I will enable flashing to the stock system.
Backup / Restore: This should be self-explanitory, but you use these options for making backups of the currently selected system. Or restoring a previously made backup to the currently selected system (regardless of where you backed it up from). DON’T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
Mount: You can manually manage mounts here. NOTE: the “system”, “data” and “cache” mounts will use the currently selected ROM-slot.
Wipe: Manually erase portions of the device. NOTE: You only have 1 internal and 1 external SD card. These are not “virtual” if you erase them. They are gone. Use with caution. Wiping the “system” when “stock” ROM is selected has been disabled. You can thank me later.
Advanced:
Copy Log to SD: Experienced something odd and want to report it? DO THIS and include the log when you send me the report. Otherwise, the recovery.log will disappear when you reboot.
Fix Permissions: This can fix up ROMs which are displaying odd force close issues, etc. You will probably never need to do this.
Partition SD Card: You can add ext3 partitions to the external SD card if you want. I’m not sure we have much of a need for this on our devices.
File Manager: This works like any other file manager inside Android. You can thank the TWRP people for this, because it is quite possibly one of the best features I’ve ever seen in a recovery.
Terminal Command: Also very handy for those once in a while moments when you have to do something via terminal but don’t have adb handy. USE WITH CAUTION
Settings:
Here you can turn on and off signature verification of .zip files
Force MD5 sum checks on .zip files prior to flashing
“Use rm -rf instead of formatting” will always be checked so that Safestrap will not break partition signatures on locked devices
There are a few other checkbox options in here. Please know what you are doing.
Simulate most actions for theme testing. If you have this checked, Safestrap/TWRP will not perform most actions but show the dialog boxes so you can review theme elements. If you turn this on, it STAYS ON till you turn it off. And will show “SIMULATING ACTIONS” up top.
Set the Time Zone (use “Set Time Zone” button after choosing which time zone you want)
Restore Defaults. Use this to reset all options back to default as it came when you installed for the first time. Does not erase backups or ROM-slots, tho it might change the active slot.
Reboot: Choose from 2 options for rebooting “System” which performs a reset/reboot of the device and “Power Off” which turns the device off.
How-To "Boot Menu Manager" (Just copied from Whirleyes site)
As its name suggest, Boot Menu Manager is a Multi-ROM boot manager.
It consist of a CWM-based recovery, a boot menu & configuration app.
* Requires ROOT permission *
* Only for Motorola Razr/Droid Razr (codename spyder)
Installation:
Very easy, just install it from Play Store on any system(slot) you currently using.
No need to reboot to main system, included installer is smart enough to do it's job.
Known bugs for 0.3.4: (so you don't have to give a 4 star rating)
- Can't modify bootmenu setting by manager app
Official support/bug report/howto :
http://www.projectlense.com/BootMenuManager
1) BootMenuManager/BootMenu/Settings/BootMode
2) BootMenuManager/Porting
Recovery
1) BootMenuManager/Recovery
2) BootMenuManager/Recovery/AdvancedOptions
3) BootMenuManager/Recovery/BackupRestore
4) BootMenuManager/Recovery/FilemanagerConsole
5) BootMenuManager/Recovery/FirmwareFlashing
6) BootMenuManager/Recovery/InstallZip
7) BootMenuManager/Recovery/MountFormat
8) BootMenuManager/Recovery/RebootOptions
9) BootMenuManager/Recovery/SwitchSystem
10) BootMenuManager/Recovery/SystemKeeper
11) BootMenuManager/Recovery/WipeClean
Many thanks to Whirleyes and Hashcode for their custom recoveries, without which we couldn't boot custom roms!
Thanks to Jack'O for maintaining a thread for Carbon on the Spyder while we were busy making the actual Rom for it. Now that we got some time freed up we made this official thread for Carbon on the Spyder/UMTS-Spyder up and running. Jack'O will remain the unofficial maintainer of this thread and be happy to answer all of your questions I am sure . Thanks Jack'O!
For users interested in Carbon and coming from stock, one of our users, hrishi21007, was kind enough to make a video tutorial on how to install BMM recovery and to then flash Carbon onto your Razr. Hopefully this will help anyone new to our ROM or to BMM. Thanks hrishi21007
HOW TO INSTALL CARBON ROM via BMM on the Droid RAZR
Wait wait wait!!
Ther's something wrong in the Donate link, and your name is not among those of the team.
Do not want to hinder, but can you clarify please?
EDIT: just cheked your credentials, and seems ok, sorry if i doubted, you know the world is full of crafty people.
Jack'O said:
Wait wait wait!!
Ther's something wrong in the Donate link, and your name is not among those of the team.
Do not want to hinder, but can you clarify please?
Click to expand...
Click to collapse
lol sure, my name is on the list, I am Bionic Beast, I am the PR for Carbon, so I use the CarbonDev account so the threads are all under the same account. To remain professional and consistent. Also thanks for the heads up about the paypal link, I will fix it now
CarbonDev said:
lol sure, my name is on the list, I am Bionic Beast, I am the PR for Carbon, so I use the CarbonDev account so the threads are all under the same account. To remain professional and consistent. Also thanks for the heads up about the paypal link, I will fix it now
Click to expand...
Click to collapse
Yep, just figured out myself, sorry again but you know...
I had only good intentions
Jack'O said:
Yep, just figured out myself, sorry again but you know...
I had only good intentions
Click to expand...
Click to collapse
Of course, thats how I know I can trust you to maintain this thread correctly. You have shown good moral character. Thank you very much
just installed rom.looks amazing.
but i have 1 issue.home button is not working...
btw: just installed gapps via goomanager but after reboot setup wizard crashing and cant use phone.(gapps package:gapps-jb-20121011-signed)
running this as my daily driver! great rom! like it a lot!
thanks for the work!
oguzpasa said:
just installed rom.looks amazing.
but i have 1 issue.home button is not working...
btw: just installed gapps via goomanager but after reboot setup wizard crashing and cant use phone.(gapps package:gapps-jb-20121011-signed)
Click to expand...
Click to collapse
Go back into safestrap, wipe cache/dalvik & reflash the ROM & gapps all in the same session. After it's done, wipe cache/dalvik again & fix permissions in safestrap & reboot.
Sent from my DROID RAZR using Tapatalk 2
im using bmm. when i flash 20121011 package setup wizard and other services giving error. when i tried to flash 20130301 gapps its not even booting. tried 4 times fresh install but still the same problem
oguzpasa said:
im using bmm. when i flash 20121011 package setup wizard and other services giving error. when i tried to flash 20130301 gapps its not even booting. tried 4 times fresh install but still the same problem
Click to expand...
Click to collapse
Sorry, I've never used bmm, only safestrap.
Sent from my DROID RAZR using Tapatalk 2
oguzpasa said:
im using bmm. when i flash 20121011 package setup wizard and other services giving error. when i tried to flash 20130301 gapps its not even booting. tried 4 times fresh install but still the same problem
Click to expand...
Click to collapse
I seems you're flashing wrong gapps.
Sent from my MB860 using xda app-developers app
i flashed what goomanager downloaded. which one should i flash ?
Minzip error during flash 20130617
Do not install, wait for next release...
Ps.GSMvet
Sent from my XT910 using xda premium
oguzpasa said:
i flashed what goomanager downloaded. which one should i flash ?
Click to expand...
Click to collapse
Right gapps for 4.2.2 roms are jb-20130301
Search on google: " goo-im browsing gapps"
Sent from my XT910 using xda premium
Jack'O said:
Right gapps for 4.2.2 roms are jb-20130301
Search on google: " goo-im browsing gapps"
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
y i flashed them also.but after that, phone is not booting
btw im using jbx kernel 0.6b
The correct gapps to use with this rom are gapps 20130301, do not use any earlier version or you will have issues.
Slim gapps work as well, especially for the dark toggle. Consider updating the OP with install instructions? Safestrap slot one? I switched to BMM and I can't remember.
Sent from my OG RAZR
PACman v4
how can I enable 1% battery mode? It only works from 10 to 10%
just flashed the rom using BMM slot 1 and everything seems to work well
thanks
Related
Droid X2 Boostrap APK (here now!)
Droid X2
Hi everyone, I would like to announce that the Motorola Droid X2 recovery is now available to download!
Video
User submitted success photographs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Additional photographs:
Photo 2
Photo 3
Photo 4
Addictivetips:
Finally there is some interesting news for Motorola Droid X2 owners as Droid X2 bootstrap recovery app is now available for download. The credit for this discovery goes to c21Johnson, who unearthed this gem while skimming through some Chinese forums discussing Android development; most probably GoAPK. There are certain users and developers at XDA not giving their consent to this build but there are users who have successfully installed Bootstrap recovery and also made and restored backups. There is a lot of controversy going on regarding this bootstrap build and we would like to stay away from it by just reporting what’s going on. According to some folks, this recovery was in reality written for Atrix 4G before it got modified and was made compatible with Motorola Droid X2.
For those who don’t know, installing this app will allow you to flash custom bootstrap recovery on your Droid X2. You can flash ROMs, partition SD Card, flash kernels, backup / restore your current ROM and do numerous stuff on your phone once you have a custom recovery on board. In order to install this bootstrap recovery on your Droid X2, simply download the file from here, unzip and then copy the APK to your phone. After you have copied the APK, use any file manager like Astro to install. After the installation is complete, tap to launch the app and follow onscreen instructions to detail in order to flash bootstrap custom recovery on your phone.
There is heated discussion going on regarding legitimacy and intellectual copyrights of this app, so please head to XDA thread here to get involved. We haven’t tested this app and you will be on your own after flashing it. Extreme caution is advised.
And if you are the developer of this recovery, please let us know in the comments area and we will be happy to add credits.
Click to expand...
Click to collapse
Phandroid:
In the first step of many to freeing up a Motorola device, our friend Koush has released a bootstrap method compatible for the Motorola Droid X2 With that comes the ability to install and run a custom recovery. Everyone’s favorite – Clockwork – is also now available and ready to go. Things are looking up for the hacking community there. We’re still some time off from custom ROMs but be sure to follow along at XDA to be a part of all the excitement. [XDA via Droid-Life]
Click to expand...
Click to collapse
If you are using your phone please do not use stock browser as it has troubles downloading files. Feel free to use your favorite browser, but I highly recommend Boat Browser, it is very light-weight, quick, and offers everything that is to be desired.
Boat Browser download:
Android Market (FREE)
You will also need a file explorer outside of stock; I highly recommend Root Explorer.
Root Explorer download:
Android Market (3.85 USD)
Background:
Initially, I had heard that p3 had announced that X2 users would be, in fact, getting some Gingerbread love. After seeing this tweet, I became inclined to believe that p3 had a leak of what he said is 2.3.4. So, I went on the search to find this leak. Knowing the ins and outs of Google search, I was determined the find this file using what I thought would be the update name in a zip file. After trying dozens of search combinations, I stumbled upon something interesting... A search that lead to nothing but Chinese websites. Then after clicking a few and finding no useful information, I found a website listed with a renown name: GOAPK. I ventured into GOAPK forums where I found what seemed to be a ROM for the Droid X2. Dumbfounded by the idea of a ROM being available, but no recovery, I then went on the search for the method of accessing recovery. Luckily, I found it quickly in the same forums. Even more blocks were soon to come though. I mustered through all the Chinese and was able to register on the forums. After I registered, I was asked to post a reply to the thread before I could download. This brought me to a halt, as when I posted, I had to enter a security code and answer a security question. The question was illegible even while using Google Translate (which did a rather poor job on the website all together). So, after copying the filenames, I began Google-ing again. Finally found the files, and found the way to successfully download... That is, after waiting about 4 hours for the download to complete. I was pretty fearless in jumping onto this and seeing if it would work, but I was ready for X2 development to begin, because, honestly, the phone as stock contains a lot of software problems, some which cannot be resolved with a simple root.
Before getting started, it is important that we have root. In order to obtain root and superuser permissions, we must use Gingerbreak. Before we begin, me must make sure we have an SD card inserted and mounted. After that, be sure to enable "Unknown sources" (settings > applications) and "USB debugging" (settings > applications > development). After this is complete, install, open, and run Gingerbreak. Your device should reboot if the installation is successful. Once the device has booted back up, be sure to check for Superuser in your applications, this will ensure you correctly have root. Note: Intallation may take a few moments, so please be patient. If your phone locks up, pull battery and try again.
Gingerbreak APK download:
Mirror 1
After obtaining root rights, you're free to install the Droid X2 Recovery.
Instructions:
Download Droid X2 Recovery. This file will most likely be in .rar format, so, unzip it using your favorite method. After the APK has been successfully installed, launch it (if you do not immediately launch it, it is titled "System Recovery" in the application drawer). It will appear to be the Atrix recovery, but this file has been modified to work with the Droid X2 device. There are on screen instructions, but I will additionally post them here. First, you want to see above for having device root. Second, install recovery by clicking the "Install Recovery" button at the top of the application. After installation, wait a few seconds to ensure it is complete. Now, hook you device to the AC CHARGER (not USB to computer). And click the "Recovery Mode" button to reboot the phone into recovery. The "Charge Mode" button will also reboot the phone, but instead of going into Android recovery, it will boot you to default charge. Many have speculated that this is an "oh **** button." This is not the case, it's just to bypass recovery and go directly to charge. The device will also charge at the recovery screen, so, no need to worry about the device becoming discharged and not being able to boot.
Droid X2 Recovery APK download:
Mirror 1
Mirror 2
Mirror 3
In the recovery menu, we will use the volume rocker to navigate up and down. The power button will be used to confirm/make a selection. The options you will be allowed to choose from are as follows:
Reboot system now
- This will reboot the device and skip recovery.
Apply SDCARD:update.zip
- This will flash an update.zip file located on your EXTERNAL SD card.
Apply SDINTERNAL:update.zip
- This will flash an update.zip file located on your internal memory.
Wipe DATA/Factory reset
- Clears the data portion of your device. As stated, is the same as a factory reset.
Wipe CACHE partition
- Simply clears the cache partition of the device as stated.
Install zip from SDCARD
- Allows a .zip file to be chosen for flash. Can be chosen from internal memory or external.
Backup & restore
- Allows creation of a nandroid backup. After backup is created, will allow restoration of said nandroid.
- This is one of the first things you should do when entering recovery. It can really save you some time and headache to have a nandroid on hand in case things do not go as planned.
Mounts & Storage
- Allows mounting of storage locations and allows wiping of those locations.
Advanced
- Miscellaneous options for your device.
+++++Go Back+++++
- Returns to the previous menu.
Also discovered was a Chinese developed ROM. Note how I said Chinese. It is fully flashable, and for the most part, functional. I don't necessarily recommend installing it as I haven't had the time to dig through it and determine what is actually included/changed.
Quens DX2 CHS ROM download:
Mirror 1
Mirror 2
Thanks for everything and happy developing!
*DISCLAIMER* You are at the consent of your device. If you choose to use, install, or follow any instruction obtained, it is at your will and is out of my jurisdiction of responsibility. You are responsible for your device and what you do to it.
c21johnson said:
Works great. I'm in recovery on my device right now. Unfortunately, no ROMs to install, but performs all other functions correctly.
Install APK, open it, and follow instructions listed
DOWNLOAD LINK HERE AFTER I SPAM 8 MESSAGES (sorry)
Head on over to DroidForums if you wish to download now.
If a mod could PM me, I'll provide download link and you can edit this post.
Here's to some X2 development!
Click to expand...
Click to collapse
Just checked DroidForums and I don't see a thing. Exciting news. Where is it?
Here
droidforums.net/forum/droid-x2-hacks
/159304-x2-bootstrap-recovery-apk.html
I deserve no credit for developing this. I was picking through chinese websites when I stumbled upon it. It seems to be a modified Atrix 4G recovery that works on the Droid X2. Everything is in English and it works great.
Oh my goodness. Making a back up now. I just came in my pants.
And my post was deleted?!
I guess just message me for download link.
Unsure. I received no PM pertaining to an explanation why it has been removed. I'll post it here once my count allows.
1 more... Apology for spam. First post will be updated shortly with download.
EDIT: Original updated. If a mod wouldn't mind cleaning up this thread of my spam, I'd appreciate it.
c21johnson said:
Works great. I'm in recovery on my device right now. Unfortunately, no ROMs to install, but performs all other functions correctly.
Install APK, open it, and follow instructions listed
DOWNLOAD HERE!
Here's to some X2 development!
Also, could a mod edit title "Boostrap" to "Bootstrap"? Thanks.
Click to expand...
Click to collapse
I'll be releasing the legit one soon...
ericerk said:
I'll be releasing the legit one soon...
Click to expand...
Click to collapse
Please define the differences between what you have and what has been released here. This one works flawlessly to all of my testing. I have flashed a ROM and it worked great.
For those wondering, it got removed from DroidForums because it APPARENTLY has affiliation with p3, and they were unsure whether or not this was the most stable version in development. I say apparently because I, personally, do not believe he was involved with this APK.
I have tried using this and it does not work. You can try for yourself if you like. If you see my previous post I have linked back to the thread that it supposedly came from and Eric also confirms this isn't legit.
Seeing as it doesn't work I would define this as not being legit.
Please post screens as I am unable to get it to work. The custom recovery that was provided in the link was for the Atrix.
Thank you for posting Johnson!
Sent from my DROID X2 using XDA App
I really don't deserve thanks, but thank you. All I did was poke through some chinese and discover the download. I am working on the screens. I assure you that this is working for me and I have successfully flashed a ROM from the same chinese website.
What kind of rom was this? Can you post it too?
So is this what gets us past the so called "locked bootloader"? Custom roms from here on?
The ROM is titled "Quens_DX2_CHS_update_signed" You should be able to find it using Google. I'd rather not post it because I don't exactly know the contents of this ROM. All I know is that it made my phone extremely chinese. It installed a few chinese APKs, replaced the original keyboard with a chinese/english alternative (that is actually extremely nice), and appeared to have changed the LCD density. I didn't do any deep digging as a few things have come up this evening that have taken me away from the computer.
I am going to SBF the phone, and do it all over again while hopefully providing screenshots, and then I'll also be able to tell the exact changes of this ROM. But do note, this ROM installed flawlessly.
If a video is what everyone is wanting, I will have one uploaded to YouTube hopefully by 10pm EST.
Works great. Did a backup successfully.
Sent from my DROID X2 using XDA App
We simply just seem to be getting mixed reviews pertaining this APK. I know most people already realize this, but you must be root.
ROOTING + UNROOTING INFORMATION + COMMON QUESTIONS + PROBLEMS w/ LINKS
DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR ANY DAMAGE THAT OCCURS TO YOUR PHONE. THIS IS A COLLECTION OF INFORMATION I FOUND TO BE USEFUL. I ONLY ORGANIZED IT HERE TO MAKE IT EASIER FOR PEOPLE TO FIND.
Don't forget to thank people who made the ROMs, Root Methods, etc. They put in a lot of work and take a lot of time helping people. All it takes is a click of a button. One for me too! It's a lot of work trying to keep everything updated. =P
This will and always will be a work in progress. If you feel something should be added, clarified, or corrected feel free to PM me. I'm not perfect and I can't read everything so any and all help is appreciated. (Yes of course I will credit you. Just no plagiarism!)
-----------------------------------------------------------------------------
Preface:
I made this guide to be a collection of information for the latest rooting methods as well as common questions and problems that arise from rooting/flashing/etc. Please read the entire guide if you are new to rooting. Also the common questions and problems are found in posts 2 and 3 of this thread. I hope you find this to be helpful. Happy and safe rooting.
----------------------------------------------------------------------------------------------------
Latest News:
-CM10 PREVIEW BUILDS READY FOR AT&T, TMOBILE, & SPRINT! Go to the Original Development forum for your carrier.
-You can now reset your flash counter! Check out "Triangle Away 1.70" in the Play Store. http://forum.xda-developers.com/showthread.php?t=1494114 HUGE THANKS TO CHAINFIRE!
-VERIZON GALAXY S3 ROOTED!!!!! http://forum.xda-developers.com/showthread.php?t=1756885
-Clear your Google Wallet data before you flash a ROM! Doing it in Titanium Backup does not work. Do so by opening Google Wallet, Menu > Settings > Reset Google Wallet.
-If you flashed an international ROM or root method and you were soft bricked, here is how to fix it: http://forum.xda-developers.com/showthread.php?t=1727443
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Information
What is rooting and why should/shouldn't I do it?
Rooting is a way of gaining access to the root directory of your phone enabling you to change every aspect of your phones software that the manufacturer has locked. This enables you to do many things with your device that the manufacturer did not intend. Here are some reasons why people root and why people don't.
Reasons to root:
Get the latest versions of Android on your phone before anyone else.
Try faster and more optimized versions of your phone's software.
Overclocking and underclocking your phone.
Longer battery life.
Theme your phone a lot more.
FREE Wireless Tethering.
Remove unwanted Sprint software.
Reasons to NOT Root:
Not comfortable with troubleshooting your phone and phone problems.
Do not have the time to spend going through countless forums to find solutions to problems.
Possibility to break your phone permanently causing you to go back to Sprint (IF YOU HAVE INSURANCE) to get another one or buy another if you don't have insurance.
VOIDS YOUR WARRANTY. (Can be undone)
Very time consuming and addicting.
Do not know what a "driver" is for a computer.
Have no knowledge of DOS.
So how do I root?
Warnings:
-Don't use any method just because the guide says "ROOT METHOD". Make sure its the latest root method used for your situation. Even this guide will get outdated one day (I'll try my best to keep it up to date).
-Rooting will cause all your information to be lost if you did not properly back them up. You will lose anything saved on the phone, such as contacts (not synced to Google) and applications and settings. Anything on your SD card will still be there such as music and pictures and video.
Basic terminology:
If you are new to Android or not comfortable yet, learn the terminology first! Found a great link to almost all the terms you will run into. If you don't understand something, ask! Its better than turning your phone into a paperweight!
http://forum.xda-developers.com/showthread.php?t=1728824
The SAMSUNG GALAXY S3 QCOM TOOLKITis currently used to ROOT your device. Please read that thread carefully and follow all directions to get it started. Also before you flash ANYTHING, go to your Google Wallet app and clear data in Android. Clearing in Titanium Backup or any other app will not work. You must clear the data before flashing anything or it will not work! You have been warned!
Root Methods per Carrier (Windows)
AT&T:
http://forum.xda-developers.com/showthread.php?t=1746665
http://forum.xda-developers.com/showthread.php?t=1739426 - Does not trip flash counter
Sprint:
http://forum.xda-developers.com/showthread.php?t=1746680
http://forum.xda-developers.com/showthread.php?t=1774722 - Does not trip flash counter
T-Mobile
http://forum.xda-developers.com/showthread.php?t=1746682
http://forum.xda-developers.com/showthread.php?t=1771687 - Does not trip flash counter
Verizon:
GUIDE TO ROOTING: http://forum.xda-developers.com/showthread.php?t=1762709 (Thanks droidstyle)
This might be complicated for some users. Please follow all directions CAREFULLY!
http://forum.xda-developers.com/showthread.php?t=1756885
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What do these methods do?
They root your device and give you the option of installing a custom recovery which is used to flash custom software on your phone! If that was in another language, go up and read through the link on Basic Terminology.
How do I know if I am rooted?
You followed the above instructions and have Superuser in your App Drawer. You can also go to the Play Store and download a root checker.
I am rooted now. What can I do?
FIRST MAKE A NANDROID BACKUP! ALWAYS DO THIS BEFORE YOU FLASH SOMETHING. THESE ARE BIG FILES SO TRANSFER THEM TO YOUR COMPUTER TO SAVE SPACE ON YOUR SD!
A nandroid backup basically takes a snapshot of your phone which you can restore. While it will fix most problems, it is not a cure all. It will fix most if not all ROM flashing blunders.
How do I make a Nandroid Backup?
#1 - Go into recovery by powering off your phone first, then holding [Volume Up], [Home Key], and [Power Key] together till you see the Samsung logo flash. Use [Volume Up or Down] to navigate the menus and [Power Key] to select.
#2 - Go to "backup and restore" and hit the [Power Key]
#3 - If you have an SD card, I recommend placing the backup there as it is quite large.
#3a - If you have an SD card, select "backup"
#3b - If you do not have an SD card or don't want to save to your SD card, select "backup to internal sdcard"
#4 - Wait for a very long time till it finishes. Once it does it will bring you back to the menus.
#5 Select "+++++Go back+++++"
#6 Do your business in recovery or "reboot system now"
OK. I made my Nandroid Backup. What can I do now?
You can now flash custom ROMs, kernels, radios, themes, etc. Go to your specific carrier's Development section on the forums. You will find ROMs, radios, kernels, etc there.
For themes and Apps, go to the Themes and Apps section of the forum.
WARNING: For the time being, you MUST flash the ROMs found in your respective carrier's forums. DO NOT FLASH A ROM FOR ANOTHER CARRIERS OR THE INTERNATIONAL VERSIONS GALAXY S3!
AT&T
http://forum.xda-developers.com/forumdisplay.php?f=1633
Sprint
http://forum.xda-developers.com/forumdisplay.php?f=1639
T-Mobile
http://forum.xda-developers.com/forumdisplay.php?f=1645
Verizon
http://forum.xda-developers.com/forumdisplay.php?f=1672
Themes & Apps
http://forum.xda-developers.com/forumdisplay.php?f=1671
---------------------------------------------------------------------------------
How do I flash a ROM/Kernel/Theme/etc
#-1 - READ THE THREAD FIRST FOR THE INSTALL INSTRUCTIONS! They will usually be a summarized version of this!
#0 - MAKE SURE YOU HAVE AT LEAST 30% BATTERY! IF YOUR PHONE DIES, IT WILL STAY DEAD (most likely). YOU CAN NOT CHARGE WHILE DOING THIS!
#1 - Download the ROM of your choosing from your carrier's forums. It will be in a .zip file format. DO NOT UNZIP IT!
#2 - Save this file to your SD card or internal storage.
#3 - Power off your device.
#4 - Go into recovery by powering off your phone first, then holding [Volume Up], [Home Key], and [Power Key] together till you see the Samsung logo flash. Use [Volume Up or Down] to navigate the menus and [Power Key] to select.
#5 - IF YOU HAVE NOT MADE A NANDROID BACKUP, SEE ABOVE! IF YOU HAVE NOT RESET GOOGLE WALLET AND ARE ON SPRINT! STOP AND GO BACK AND RESET IT!
#6 - Use the volume keys to select "wipe data/factory reset" and hit the power key. Select "Yes -- delete all user data" and hit the power key.
#7 - In the main menu, select "advanced" and then select "Wipe Dalvik Cache" and then select yes.
#8 - Go back to the main menu and use the volume keys to select "install zip from sdcard" and hit the power key.
#9 - What you select next will be based on where you saved it.
#9a - If you saved in the SD card, select "choose zip from sdcard"
#9b - If you saved in the internal storage, select "choose zip from internal sdcard"
#10 - Use the volume keys to select the .zip file you downloaded and hit the power key.
#11 - WAIT FOR IT TO FINISH!
#12 - Congrats! You just performed your first flash. Go back to the main menu and reboot your device.
#13 - Enjoy.
How do I return to stock (unroot)?
AT&T
http://forum.xda-developers.com/showthread.php?t=1737848
Sprint
http://forum.xda-developers.com/showthread.php?t=1737859
T-Mobile
http://forum.xda-developers.com/showthread.php?t=1737855
Verizon
GUIDE TO UNROOTING: http://forum.xda-developers.com/showthread.php?t=1762709 (Thanks droidstyle)
http://forum.xda-developers.com/showthread.php?t=1755386
How do I backup my apps?
Use MyBackup. You can use this to backup and restore your apps without the need for rooting. (Thanks teh roxxorz)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Appbrain is good if you are using market only apps. However app data won't be saved.
Titanium Backup is also good if you are rooted.
Credits:
teh roxxorz, noobnl, cypher_zero, qbking77, appdroid, & droidstyle
Common Questions
I am getting an Over the Air (OTA) update from Sprint. Should I accept it if I am rooted?
IF YOU ARE ROOTED, DO NOT ACCEPT THIS OTA.
This means that your phone's software is not up to date and it is telling you to update. You must download a ROOTED version of the update and manually flash it. Accepting this will cause you to lose root and worst case, brick your phone. SO DON'T DO IT! lol
I rooted using ABC's method. Do I need to root again using XYZ's?
No. Once you are rooted, you are good to go.
I turned my phone into a paperweight/bricked it/"borked" it/its just not working no matter what I do. What can I do?:
No information yet!
If you have Sprint's Total Equipment Protection Program, you are in luck. They changed their policy on October 23rd. Here are the details of what it covers.
http://www.phonenews.com/sprint-tepsr-changes-next-week-13303/
If the phone is beyond repair, you will have to go through Asurion and pay the $100 deductible. TEP does not cover rooted phones. You have to go through Asurion.
If you don't have TEP, everything except water/fire damage and lost phone replacements cost $35 per incident as long as the phone is not beyond repair. If it is beyond repair, you will have to buy a new phone.
What is PRL?
PRL stands for Preferred Roaming List. Its a list of roaming towers in your area. Its best to keep this updated in crappy coverage areas.
What is PRI?
http://forum.xda-developers.com/showthread.php?t=751935&page=7 <- Debate on what it stands for. (REALLY?!)
In actuality it is called "Product Release Instructions" and is essentially a list of settings for the radio. It's the PRI which uses the PRL to enable data roaming by connecting it to towers/cell sites listed in the PRL and for other things such as to allow calls to interrupt an active data session (ring-through).
How do I update my PRL/PRI?
Go to Menu > Settings > System Updates > Update PRL + Update Profile.
I see "deodex" and "odex" ROMs. What are those?
Basically if you want to theme your ROM you want to use deodexed ROMs. Odexed ROM's are made to be streamlined. There is a performance difference. Deodexed ROM's will take longer to boot up because everything or almost everything is unpacked. Odexed ROM's will boot faster and be more responsive.
http://lmgtfy.com/?q=What+is+deodex
Google is your friend =P
FREE Wireless Tether:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=Evo
***Some builds don't work with certain ROM's. Trial and error or searching within your ROM's thread will let you know which build numbers will work for you. Also note if you enable WIFI Encryption, the password is CASE SENSITIVE! Make sure you know that as you are typing the password in due to certain keyboards auto capitalizing. ***
Launchers: (Will review once I get my phone)
ADW
LauncherPro
Apex Launcher
Nova Launcher
Widgets (Will review and add more once I get my phone)
Beautiful Widgets - Sense like clocks and weather. Make sure to download the animation package if you want animated weather.
OneSeven - A text based date widget
Tajm - A text based clock
----------------------------------------------------------------------------------------------------
Battery - Common Questions and Problems
What is the best ROM + Kernel combination for battery life?
There is no right answer for this. Battery life is affected by so many factors, the only thing you can do is trial and error. Here are most of the factors that can affect battery life:
-Phone Settings (Haptic feedback, screen on duration, auto sync, radios, etc)
-ROMs
-Kernels
-Overclocking + underclocking
-Apps
-Signal strength
-Roaming
-Battery type
-Battery stats
-Calibrating the battery
-PRI
-PRL
-The water you drank the other day
-The **** you took just before
So how do I improve battery life?
No information yet.
Common Problems:
I created a bug thread check that first!
http://forum.xda-developers.com/showthread.php?t=1722363
Standard Troubleshooting For Many Flashing Problems:
-Try Rebooting. Most problem will be solved this way.
-Was it fine before your Nandroid Backup? If so, restore your backup.
-If you flashed something and are having issues, did you wipe your data/cache/dalvik? If not then do it and reflash.
-If you are still getting problems, the file is most likely corrupt or outdated. Try redownloading and making sure the file is updated for your ROM + Version #
-If the file is updated and NOT corrupt, SEARCH FIRST IN THE FORUMS OR GOOGLE! You will be surprised on the answers you can find in 15 seconds of searching.
-Can't find any solution or workaround? Then make a post in that thread with details of your problems, as well as ROM, error messages, etc.
I am getting random Force Closes (FCs) after flashing ****.
Did you wipe your data/cache/dalvik? Also go to Mounts and format /system. If not do a Nandroid Restore to the backup you should have done before flashing and then wipe data/cache/dalvik and then reflash. See if you still get a FC. If you do, there might be a problem with whatever it is you flashed with the ROM you are using. Check on the thread you downloaded it from for support.
I am stuck in a boot loop.
If you flashed a new ROM and you are stuck in a bootloop, you probably didn't erase your data/cache/dalvik. Try that and reflash your ROM. This will fix most boot loop issues. If it was from something else, make a post in your respective threads or in Q+A.
I am stuck in a NAND Backup!
Pull your battery and restart the backup. You might also want to erase the NAND backup that failed by going to your respective NANDROID backup folder on your SD card.
I am a MAC user and I downloaded ____'s ROM and it doesn't work.
Macs will recompress the file. Use Firefox to download and make sure it doesn't recompress the file. It should work then. Either that or use a Windows based PC.
I tried to NANDROID BACKUP and I got an error message saying "Run 'nandroid-moble.sh' via adb!"
Your SD card is full.
I am having issues with Google Wallet saying it is no longer secure. What is wrong/how do I fix it?
http://forum.xda-developers.com/showthread.php?t=1730837
Custom ROM Reviews
This will be a section where I will do a thorough review of custom ROMs. These are based on my own usage and your mileage may vary depending on what apps/etc you use. I will take requests to do certain ROMs and I will post up a schedule to do reviews so you can send me questions ahead of time. Please also note, that I will only test Sprint ROMs because I only have a Sprint device. I will take reviews from other people on different carriers.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Each ROM will be broken down as follows:
ROM Name:
ROM URL:
Version/Build:
ROM Type: (AOSP/TW/AOKP/ETC)
Recommended for:
Stability:
Features:
Bugs/Issues:
Final Thoughts:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ROM Name: Sprint CM10 Preview Build
ROM URL: http://forum.xda-developers.com/showthread.php?t=1778266
Version/Build: 7/20 Preview Build
ROM Type: CM10 (AOSP)
Recommended for: Experienced flashaholics
Stability: This is a preview build just for the community to see what is in store for their phones on Jelly Bean with CM10. There are bugs expected with this. However for a preview build, this is surprisingly stable. This build came out today and while it is still too early to say it is fully stable, it is surprisingly smooth and as of this moment, it is stable for me. I did run into a very annoying com.android.phone FC loop in the previous build that wouldn't go away till you wipe and reflash the ROM. I'm waiting to see if it happens again on the 7/20 build.
Features: Jelly Bean and all its features. http://developer.android.com/about/versions/jelly-bean.html
It is an AOSP ROM so it has better integration with Google products like Google Voice and no bloat. It is a CyanogenMod ROM so it is made for performance. It is very snappy and will only get faster and smoother once they integrate Project Aurora. If you want to test Jelly Bean, you can flash this. However you are warned that it may crap out on you. If you need 100% stability, then don't flash it.
Bugs/Issues: The camera will take pictures but I did get a force close (FC) on the Gallery and it will freeze. The previous builds did have a green hue over the camera but that is fixed. The widget toggle buttons are being worked in but they are not working as of this build. Facebook integration with contacts isn't good. Contact images do not get linked/joined with existing Google contacts. Bluetooth music does not work. Audio over Bluetooth is not working either. Phone calls over Bluetooth work but it is a little distorted.
Final Thoughts:
The reason why I jumped to CM10 despite knowing it is buggy is to try out Google Now with the new speech engine and Project Butter and it did not disappoint. It took a day or so to get Google Now to learn my habits but it was pretty much on point! The new speech recognition engine is AMAZING! Very quick and the most accurate I've used to date and I've used a lot. Overall, I would recommend this for anyone who wants to test the latest and greatest Android flavor but can work though bugs and issues.
Reviewed on 7/20/12 @ 1:46PM EST.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you want to ask me any questions, feel free to PM me or add me on GTalk @ [email protected]
Rooted Application Reviews
This will be a section where I will do reviews of rooted applications. These are based on my own usage and your mileage may vary depending on what apps/etc you use and what you use it for. I will take requests to do certain applications and I will post up a schedule to do reviews so you can send me questions ahead of time. Please also note, that I am on a Sprint device. I have bought a few paid rooted applications and utilities but I can't buy them all. I hope that I can get some donations going so I can buy more of these applications to review. If you are an application developer and would like me to review your application, please PM me and I'll toss one up.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Each application will be broken down as follows:
Application Name:
Developer:
Developer's Site:
Version/Build:
Application Description:
Stability:
Features:
Bugs/Issues:
Final Thoughts:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Application Name: Titanium Backup
Developer: TITANIUM TRACK
Developer's Site: http://www.matrixrewriter.com/android/
Version/Build: 5.4.1.1
Play Store Link: https://play.google.com/store/apps/...xMiwiY29tLmtlcmFtaWRhcy5UaXRhbml1bUJhY2t1cCJd
Paid/Free? Both.
Price: $6.58 USD
Application Description: You can backup, restore, freeze (with Pro) your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card. You can do 0-click batch & scheduled backups. Backups will operate without closing any apps (with Pro). You can move any app (or app data) to/from the SD card. You can browse any app's data and even query the Market to see detailed information about the app.
Stability: Very stable. It works with all ROMs I've used across many devices.
Features: TOO MANY! Look in the Play Store for features
Bugs/Issues: Very little if any.
Final Thoughts:
Titanium Backup has been on all the phones I have used and it is VERY VERY VERY handy. I highly recommend everyone use this for backups. The pro version allows you to auto upload your backups to the cloud so you don't waste space on your device plus other features. It also helps you get rid of certain apps and freeze them which can be really handy. There are some quirks but not with the application. What I mean is if you restore the wrong application or an application that is not compatible with your ROM, it will cause FC errors. Same thing with deleting a system application.
Reviewed on 7/20/12 @ 1:46PM EST.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you want to ask me any questions, feel free to PM me or add me on GTalk @ [email protected]
sekigah84 said:
Hut!
Click to expand...
Click to collapse
1, hut 2 hut 3 hut, Ol' Dirty Bastard live and un-cut
Can anyone confirm that this method works and what bugs there are? In other words, is it safe!!?
wramos93 said:
Can anyone confirm that this method works and what bugs there are? In other words, is it safe!!?
Click to expand...
Click to collapse
Not as of yet. It's still fresh. I can't comment cause my phone isn't here yet =[
sekigah84 said:
Not as of yet. It's still fresh. I can't comment cause my phone isn't here yet =[
Click to expand...
Click to collapse
Its safe; I'm rooted and using TB like a boss, before this thread was updated.
Though I would like to say that at the end where you list the chmod permissions, you can alternatively just install busybox from the market, after you have installed cwm and flashed the super user zip in recovery.
And with that, my support for this thread too begins.
teh roxxorz said:
Its safe; I'm rooted and using TB like a boss, before this thread was updated.
Though I would like to say that at the end where you list the chmod permissions, you can alternatively just install busybox from the market, after you have installed cwm and flashed the super user zip in recovery.
And with that, my support for this thread too begins.
Click to expand...
Click to collapse
P.S. Your Delorean needs fueling.
sekigah84 said:
P.S. Your Delorean needs fueling.
Click to expand...
Click to collapse
It does, I'll be sure to do so. Also hit me up if you need anything.
teh roxxorz said:
It does, I'll be sure to do so. Also hit me up if you need anything.
Click to expand...
Click to collapse
Will do rox. Let me know about any quirks with the phone.
sekigah84 said:
Will do rox. Let me know about any quirks with the phone.
Click to expand...
Click to collapse
This thing handles like I handle noobs on halo and gears of war: like. a. boss.
Handles multitasking well, played super mario 64 like butter; so far I haven't had any issues at all.
teh roxxorz said:
This thing handles like I handle noobs on halo and gears of war: like. a. boss.
Handles multitasking well, played super mario 64 like butter; so far I haven't had any issues at all.
Click to expand...
Click to collapse
AHHH im jelly. SHIP MY 32GB SPRINT! ROARRRRRRR
I'm doing some self learning ATM to get devin. Hopefully I'll be getting a ROM out within the next few months lol
sekigah84 said:
I'm doing some self learning ATM to get devin. Hopefully I'll be getting a ROM out within the next few months lol
Click to expand...
Click to collapse
Hey power to ya man. You know where to find me.
Noticed people having trouble getting to recovery. For me, trick was NOT holding down power, rather pressing once while holding home and volume down.
Just wondering, does the process that flashes cwm recovery through Odin, then flashes the root through the recovery, does that manipulate the kernel at all? And if it does will I have to worry about signal issues or low bars? I want to keep my phone as stock as possible, but want to remove bloat, and possibly tether. But want to maintain the integrity of the kernel by not making drastic change to it. Can someone explain to me what this root method actually does to allow access? Thank you for your time.
I will update this to combine all information across carriers soon.
wpjessie said:
Noticed people having trouble getting to recovery. For me, trick was NOT holding down power, rather pressing once while holding home and volume down.
Click to expand...
Click to collapse
Basically hold down the power button, but when you see that blue flash that says recovery at the top of the screen, release the power button.
rogermhoffmanjr said:
Just wondering, does the process that flashes cwm recovery through Odin, then flashes the root through the recovery, does that manipulate the kernel at all? And if it does will I have to worry about signal issues or low bars? I want to keep my phone as stock as possible, but want to remove bloat, and possibly tether. But want to maintain the integrity of the kernel by not making drastic change to it. Can someone explain to me what this root method actually does to allow access? Thank you for your time.
Click to expand...
Click to collapse
Basically flashes the CWM recovery, install su, binaries, ect. The kernel is still stock, and you'll be able to remove bloatware and use rooted apps.
Ok, to clear the air, I am not the original Dev for this particular project. I had been working on a very similar project until I found this. It just needed for me to add support for our device. So I did just that. I made a prominent build and after extreme testing it is ready to be shared with you.
See Continuous Integration Builds at the end of this post for a link to download latest releases. All releases starting from November 5, 2015 and onward will support the Huawei Ascend Mate 2.
It can patch:
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in other ROMs
NOTE: If you want to dualboot a stock EMUI ROM, I highly recommend installing it as your primary ROM first. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and install.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of Extsd slots. These install to the external sd partition and eat up space on the external storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny and your data partition is getting full. These slots are named "extsd-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from the custom recovery will literally backup every ROM you have installed so think about this before making a backup.
App and data sharing
DualBootPatcher got support for sharing apps (deprecated) and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply becomes unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
How do I...?
Switch the ROM if something doesn't work properly?
If you have TWRP, you can switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
I installed a new rom and want to switch to it?
Open app, select ROMs, then select the rom you want to switch to. When the switch is successful, reboot.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
WATCH THESE HOW-TO VIDEOS:
Credits to @superbass311 for making these videos.
It will demonstrate how to use this app effectively. If you read the instructions and still can't figure it out then this will be very helpful to you!
How to install Multi Boot Patcher:
How to flash another ROM with Multi Boot Patcher:
How to flash Xposed with Multi Boot Patcher:
How to share apps with Multi Boot Patcher:
Original Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Contributors
chenxiaolong, SHM
Version Information
Status: Testing
Continuous Integration Builds: https://snapshots.noobdev.io/
Created 2015-10-11
Last Updated 2015-11-07
It seems complicated. May try it later.
One question currently: What if I want to update a ROM? e.g. Huawei releases B323 or whatever to fix security issue(s). Or to do delta update for CM or PAC ROM? I know you seemed mentioning this already, but it is still sort of confusing, esp. with OTA update.
MT2-User said:
It seems complicated. May try it later.
One question currently: What if I want to update a ROM? e.g. Huawei releases B323 or whatever to fix security issue(s). Or to do delta update for CM or PAC ROM? I know you seemed mentioning this already, but it is still sort of confusing, esp. with OTA update.
Click to expand...
Click to collapse
When you download the ROM such as CM for example, open the app, then select to patch that ROM the same way you did before. Then just flash. It will flash the update to the proper ROM without affecting any other ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see I have three roms. CM is my primary ROM. Then I have PAC ROM and Carbon ROM installed on my external sd. Should I get an update for PAC ROM and download, I would open the app, then click on, Patch Zip File, change partition configuration to PAC ROM as seen in the picture, then choose the OTA ROM to patch. When the patch is done simply flash. Simple enough.
Edit: please try not to quote the entire first post. Can be a pain scrolling through if using an app.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
When you download the ROM such as CM for example, open the app, then select to patch that ROM the same way you did before. Then just flash. It will flash the update to the proper ROM without affecting any other ROM.
As you can see I have three roms. CM is my primary ROM. Then I have PAC ROM and Carbon ROM installed on my external sd. Should I get an update for PAC ROM and download, I would open the app, then click on, Patch Zip File, change partition configuration to PAC ROM as seen in the picture, then choose the OTA ROM to patch. When the patch is done simply flash. Simple enough.
Click to expand...
Click to collapse
So I have to manually flash the OTA update.zip or I could also let CyanDelta to that?
MT2-User said:
So I have to manually flash the OTA update.zip or I could also let CyanDelta to that?
Click to expand...
Click to collapse
If CyanDelta targets the patched ROM then yes, buy pointless to jump back to the cyandelta app. While using the Dual Boot Patcher app you can install from there. After the patch is made you go to, Roms, then click on the icon at the bottom right. It will have a phone with an arrow pointing down. In the same location press another icon with an add sign. Select the patch ROM. Then flash it through the app. Don't even need to go to TWRP at all unless its the primary ROM. This is explained in the OP already
Sent from my Ascend Mate 2 using Tapatalk
Thanks for your patience to explain.
BTW, I cleaned up the quoted images.
MT2-User said:
Thanks for your patience to explain.
BTW, I cleaned up the quoted images.
Click to expand...
Click to collapse
No worries, maybe @superbass311 will make a video for others to help them out. He likes making them videos lol.
Sent from my Ascend Mate 2 using Tapatalk
Oh sh+t! @SHM I did not see these post! He'll ya this will be my reading for tonight and I will try it all out then I'll make a video. Sweet!
Sent from my Ascend Mate 2 using Tapatalk
Interested in App Sharing.
From @chenxiaolong (http://forum.xda-developers.com/attachment.php?attachmentid=3318276&d=1431909206), space would be saved from keeping two/more APKs; however, if I have to install the same App in each ROM, how would that happen? Or actually the 2nd, and other subsequent ROM(s) just redirect the same App other than do real installation OR delete the same App after permission of the same shared App?
Does it matter in which ROM the shared App is enabled first, esp. regarding the App setting/data?
MT2-User said:
Does it matter in which ROM the shared App is enabled first, esp. regarding the App setting/data?
Click to expand...
Click to collapse
If the app is on your primary ROM but not on any other ROM, then you must enable that app to be shared on the primary ROM. Then switch to the other ROM and enable it in that ROM. Then you can use that app and its data from a shared location. If you wish to share all apps from the primary ROM with all other ROMs then boot up the primary ROM and enable, Share applications. Switch to any other ROM and all the apps from your primary should be available with all other ROMs you boot up. It doesn't matter which ROM you do this from. Its just a matter of which ROM has the app you wish to share in general. That specific ROM which holds that specific app that you wish to share is where you must go to enable it. Then jump to the other ROM and enable it again from there for single sharing.
I'm currently sharing all apps with all ROMs just to make it simple on my device. Its totally up to the end user what they do.
SHM said:
If the app is on your primary ROM but not on any other ROM, then you must enable that app to be shared on the primary ROM. Then switch to the other ROM and enable it in that ROM. Then you can use that app and its data from a shared location. If you wish to share all apps from the primary ROM with all other ROMs then boot up the primary ROM and enable, Share applications. Switch to any other ROM and all the apps from your primary should be available with all other ROMs you boot up. It doesn't matter which ROM you do this from. Its just a matter of which ROM has the app you wish to share in general. That specific ROM which holds that specific app that you wish to share is where you must go to enable it. Then jump to the other ROM and enable it again from there for single sharing.
Click to expand...
Click to collapse
+1. Global App Sharing is supported in primary ROM? Do I need patch every Gapps including the one for primary ROM? (There are 700 pages of the thread started by @chenxiaolong. I saw he mentioned the second Gapps needed to to patched. That's more than 2 years ago though.)
---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------
SHM said:
I'm currently sharing all apps with all ROMs just to make it simple on my device. Its totally up to the end user what they do.
Click to expand...
Click to collapse
DId you install each App 3X? Or just backup/restore using TB?
MT2-User said:
+1. Global App Sharing is supported in primary ROM? Do I need patch every Gapps including the one for primary ROM? (There are 500 pages of the thread started by @chenxiaolong. I saw he mentioned the second Gapps needed to to patched. That's more than 2 years ago though.)
Click to expand...
Click to collapse
For your first question, yes, but the primary ROM needs to be patched first in order for it to work. My recommendation with that is to grab the latest ROM zip for your primary and patch that zip using the app. Then install the patched zip to your primary. It will add needed files and binaries to make things more effective. This also makes sure not to mess with other ROMs as well. As for your second question about gapps, if you wish to install the gapps to a ROM, let's say PAC rom, and PAC rom is installed on your external SD, then you must patch the gapps zip using the configuration for PAC. When the patch is done, simply flash. Doing this insures the gapps is properly installed to that specific ROM. Otherwise it will just install to your primary ROM by default and if your primary ROM already has gapps then this isn't what you want it to do lol. You must patch the gapps zip for each ROM configuration to insure that it installs to that specific ROM. It takes no time to do this. Its easy, and quick. Give it a try
MT2-User said:
DId you install each App 3X? Or just backup/restore using TB?
Click to expand...
Click to collapse
Neither. By enabling shared apps to share all my apps on my primary ROM with all other ROMs it simply gives my ROMs access to them. No need to do multiple installs. One install of that app is all that is required. If you take a look at the first post it explains how app/data sharing works using an analogy. I would recommend you read that closely for a better understanding on how this process works.
SHM said:
Neither. By enabling shared apps to share all my apps on my primary ROM with all other ROMs it simply gives my ROMs access to them. No need to do multiple installs. One install of that app is all that is required. If you take a look at the first post it explains how app/data sharing works using an analogy. I would recommend you read that closely for a better understanding on how this process works.
Click to expand...
Click to collapse
Actually I got confused from the quoted content in OP saying in each ROM to install the App first.
MT2-User said:
Actually I got confused from OP saying in each ROM to install the App first.
Click to expand...
Click to collapse
For single sharing it was saying to enable them in each ROM. Not install in each ROM. To install in each ROM would defeat the purpose of sharing. Here is an example, I have tapatalk installed on my primary ROM. On my second ROM it doesn't exist. I want to use tapatalk on my second ROM so what I do is I enable tapatalk to be shared from within the primary ROM. I then switch to the second ROM. While in the second ROM I enable for the app to be shared as well. This way the second ROM can use it. If I have a third ROM and want to use tapatalk on that third ROM then I simply switch to the third ROM and enable the sharing of the app. No need to go back to my primary since it was already enabled previously. However, if you want to make it simple you can enable for all apps to be available for all roms by a click of a button and be dome with it.
SHM said:
For single sharing it was saying to enable them in each ROM. Not install in each ROM. To install in each ROM would defeat the purpose of sharing. Here is an example, I have tapatalk installed on my primary ROM. On my second ROM it doesn't exist. I want to use tapatalk on my second ROM so what I do is I enable tapatalk to be shared from within the primary ROM. I then switch to the second ROM. While in the second ROM I enable for the app to be shared as well. This way the second ROM can use it. If I have a third ROM and want to use tapatalk on that third ROM then I simply switch to the third ROM and enable the sharing of the app. No need to go back to my primary since it was already enabled previously. However, if you want to make it simple you can enable for all apps to be available for all roms by a click of a button and be dome with it.
Click to expand...
Click to collapse
That's why I asked at the beginning coz I was confused. Understood since your previous reply. If stock ROM set as primary, guess will not enable global app sharing; or you could distinguish between system apps and user apps?
BTW, sorry I wanted to show my appreciation but I guess I reached the 8 thx per day limit.
MT2-User said:
That's why I asked at the beginning coz I was confused. Understood since your previous reply. If stock ROM set as primary, guess will not enable global app sharing; or you could distinguish system apps and user apps?
BTW, sorry I wanted to show my appreciation but I guess I reached the 8 thx per day limit.
Click to expand...
Click to collapse
System apps are not able to be shared betweem roms. Only user apps. This is done like this to prevent system crashes. If you want a specific system app you will have to handle that manually. How you choose to do so is entirely up to you, and no worries on the thanks. Give them when you can but I won't cry if you don't lol. Not really here for credits, but here to learn, grow, and when applicable, share my experiences with others.
To properly patch the stock ROM as primary you will need to make a flashable ROM so that ROM.zip can be patched. Unfortunately, to my knowledge, no one has made a flashable stock zip and shared it publicly. Only stock roms which are shared are either backups from other members or links to the official updates which are not proper flashable zips. Huawei uses an unnatural method by default, ie. UPDATE. APP and (VENDOR_UPDATE.APP)?.. However, one could easily make a backup of the stock ROM without any modifications and turn that system backup into a proper flashable ROM using tools such as archi kitchen or anything else which is similar to that. Then patch it using this app and install as primary.
How much space are you using running three ROMs?
SHM said:
System apps are not able to be shared betweem roms. Only user apps. This is done like this to prevent system crashes. If you want a specific system app you will have to handle that manually. How you choose to do so is entirely up to you, and no worries on the thanks. Give them when you can but I won't cry if you don't lol. Not really here for credits, but here to learn, grow, and when applicable, share my experiences with others.
To properly patch the stock ROM as primary you will need to make a flashable ROM so that ROM.zip can be patched. Unfortunately, to my knowledge, no one has made a flashable stock zip and shared it publicly. Only stock roms which are shared are either backups from other members or links to the official updates which are not proper flashable zips. Huawei uses an unnatural method by default, ie. UPDATE. APP and (VENDOR_UPDATE.APP)?.. However, one could easily make a backup of the stock ROM without any modifications and turn that system backup into a proper flashable ROM using tools such as archi kitchen or anything else which is similar to that. Then patch it using this app and install as primary.
Click to expand...
Click to collapse
:good::good::good:
Joshndroid's UNOFFICIAL CM13.0 BUILDS
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
CyanogenMod
Rom Source
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65753816&postcount=4
Alternate Download - Basketbuild Download
https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu
Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.
Google Shares
Rules -
1. I WILL NOT be keeping your PM or your email address anywhere once you have been added to the share, i WILL be respecting privacy so I expect the same in return.
2. I WILL however, be creating a google doc (probably in each rom folder) to signify by XDA username only who is in the share. (This is for a couple reasons, 1 - because I can keep track of who I have added to the share, 2 - people can see if they have been added or not to the share to either remind, 3 - It keeps people accountable when their, somewhat, online identity is linked to something.)
3. Do NOT spam me with PM's if I dont get to add you within a day. I am very active on the forums due to mobile access, but to add to the share I will need to be at home. If you have not been added and see your username in the google doc after 2 days, politely PM me again.
4. If you do not use the below template (as it has all the information I will be requiring on my end to add you), You wont be added (so 2 days will pass, you wont see your name or a rom and then check the info u sent me).
5. First download for yourself is going to be rather big (about 4 roms worth). I want to keep atleast a couple roms in the share so that if something is wrong, I can pull a download or whatever at it will not affect anything to severely.
6. You will not have any access to modify or delete the files. I am the owner and you guys will only be able to download/view (which is all you need).
Okay so how can you let me know your in.
First PM me using this template:
XDA Username -
Email (google drive account) -
Rom -
Devices (some have more than one) -
I will add you to the share, I will add you to the local google doc, you will get a device folder and your files will start to sync locally to your PC.
Couple quick FAQ's
How do you know when a new rom is on the share?
You could check it manually, I also was toying with a solution that I could share within the drive that would conduct periodic checks, problem is is that it would rely on a generated file as well as direct links (something that is hard to come by on file sharing services to firstly predict and script & usually requires you to manually click a share button to get a link).
However, there is a google chrome based extention that will notify you by tracking a folder when something new has been added to a google drive folder - https://chrome.google.com/webstore/detail/folder-notifications-for/pamfobflonhoblkekglgpplpibfnckna
This will only track and send an email based on tracking 1 folder.
I am looking into the paid version myself ($2 - http://ez34.net/ezdrive/folder-notif) that will track 10 folders (which is a lot).
Can I get roms from the other locations?
Yes. I have done this setup to quicken my workflow to get roms out, the quicker you guys get them, the happier you's are. Now the primary issue I have it sync'ing to other file services to ensure I limit my bandwidth in uploading (to reduce wait times) and to keep things concurrent across. If i upload to google drive first and sync to other locations on my end, its quicker than me manually uploading to locations.
Remember the first few days I will be spammed with PM's to add everyone who wants to join, I may be a bit slow. But once that is out of the way it will be back to usual and we will then see the benefit of it. I am big on automation, the more I can automate, including checks and failsafes, the more we become something like can be provided by big rom providers.
so;
why did i make a new thread?
Well, i was tired of spamming the other thread that is of a nightly status with these unofficial builds. I pretty much run these builds each time i run a temasek build so they will be frequent enough.
Why havnt you just submitted to CM your the maintainer?
Well, everything is not fixed yet i have been looking at the camera and once that is fixed will probably submit it for nightly status for cm-13.0
what will happen then?
This will be the main thread for cm-13.0 as it continues on, through these unofficial builds and hopefully on to nightlies once the camera is done.
what about android N?
Waaaaaaaay to early to speculate about that yet.
Anything different to base cm-13.0?
Slightly, as the rom is built using UBERTC 4.9 for the rom, the kernel specifially is untouched (unlike temasek builds)
New build March 10 2016 is up on basketbuild and google shares... cheers
Further for some rom updates whatever/follow me on twitter (DW i don't spam) - @joshndroid
Thanks you for the ROM!
This is This is stable or beta or testing? Thanks
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
I prefer to use the temasek build, because of the temasek settings and the omniswitch support, but i think both releases are stable.
TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Thanks bruh just makin sure....
joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Sy Borg said:
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Click to expand...
Click to collapse
Temasek is his main project so it will get updated more often than dis one I think he started dis one to get it goin to nightly once da camera is fixed....
Gapps for temasek cm13 - difficulty
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
jaypea500 said:
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
Click to expand...
Click to collapse
Bro I have a perfectly fine gapps package linked in second post (opengapps.org)...
These packages work fine for 7 devices I use.
yeah, I fixed it. it wasn't the gapps package. I keep forgetting that when flashing a new rom you need to immediately flash gapps without rebooting in between. the older I get, the more drips out of my colander-brain...
New build 18032016 is up on basketbuild and Google shares
Preparing SD card causes black screen
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
XDAdeveloperHTC said:
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
Click to expand...
Click to collapse
Don't use that... Just use it as external storage.
drm problem
Hi,
i've installed the latest version and get a DRM Error. DRM Widevine is missing...
Thx for a reply
JMF
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have added support for the Lenovo Vibe P1
Link
I am not the creator, just the supporter
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - From here (Download the APK in Downloads Section)
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App and data sharing
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Latest DualBootPatcher APK
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install as not much space there. just install on /data partition.
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@devansh21 for being a fantastic tester
XDA:DevDB Information
DualBootPatcher for P1a42, Tool/Utility for the Lenovo Vibe P1
Contributors
MSF Jarvis, FireLord, devansh21
Source Code: https://github.com/chenxiaolong/DualBootPatcher/commit/18180f432ba1ebb69c3029c80f2678c9c4ecdb9e
Version Information
Status: Snapshot
Created 2016-10-08
Last Updated 2016-10-08
Bug reports without logs from flashing the GetLogs ZIP will be ignored and the post deleted.
Please make sure you read the entire first post properly, everything important is given here!
Reserved
hey, i'm using a stock mm 288 for primary rom.
but, when i flash anyting to data slot for secondary rom, i cant get root to work.
i've already try flash patched BETA-SuperSU-v2.72-20160510112018 but didn't work.
can you help me?
sorry for my bad english
@MSF Jarvis
hi thnx for great job.it's run perfect.
Error installation
We got found error when try installation dual boot
arfans said:
We got found error when try installation dual boot
Click to expand...
Click to collapse
Which ROM were you trying to install?
danthecoolboy said:
Which ROM were you trying to install?
Click to expand...
Click to collapse
Originally stock rom P1a42_S288_160721_ROW_RAW and i'm trying install custom rom DotOS
Thanks a ton for the update @MSF Jarvis
MSF Jarvis said:
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have added support for the Lenovo Vibe P1
Link
I am not the creator, just the supporter
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - From here (Download the APK in Downloads Section)
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created.
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App and data sharing
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Latest DualBootPatcher APK
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install as not much space there. just install on /data partition.
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@devansh21 for being a fantastic tester
XDA:DevDB Information
DualBootPatcher for P1a42, Tool/Utility for the Lenovo Vibe P1
Contributors
MSF Jarvis, FireLord, devansh21
Source Code: https://github.com/chenxiaolong/DualBootPatcher/commit/18180f432ba1ebb69c3029c80f2678c9c4ecdb9e
Version Information
Status: Snapshot
Created 2016-10-08
Last Updated 2016-10-08
Click to expand...
Click to collapse
Followed the guide in my Lenovo Vibe p1a42 rooted running custom AOSP Extended 5.6 . I tried installing Custom Carbon 5.1 Rom. The installation/flashing process is completed successfully, But after choosing the second Rom and rebooting the device, the boot open TWRP Recovery. And further boots also open recovery. I had to reinstall the AOSP Extended Rom using TWRP to boot into Android. Can you please suggest what would have gone wrong on my end which resulted the reboot to boot into recovery rather then the second ROM.