This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*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.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
3.Nexus 5 (HammerHead)
Prerequisites
Code:
1. A Hammerhead
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[url]http://forum.xda-developers.com/google-nexus-5/orig-development/recovery-twrp-2-7-0-0-f2fs-support-t2746030[/url]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Now Scripts are Device Specific
6. Error conditions at many places so a noob cant go wrong
***Special note for CM /CM based ROM users***
Code:
I dont test the script since I dont own an HH !! This is the CM kernel by @kdh2834
If it does not work kindly post the detailed error on the thread . Will try my best to resolve it
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM/or a Stock ROM with busdybox installed
Instructions
Code:
[LIST=1]
[*] Unpack the Zip file you downloaded from Link Below to a folder named F2FSROMConvetor (Dont Mess with the name).
[*] Take Care that the path you extract my Zip for eg in my case "C:\Users\Nabendu\Desktop\F2FSROMConvetor"
does not contain any blank spaces in between or else the script will not work as intended.
[*] Run F2FS Convertor.bat
[*] Select your device
[*] Place the Zip in the Extract /Input directory when prompted
[*] The script will Unpack your ROM
[*] Select option of boot.img based on your rom
[*] Repack your ROM
[*] A black window will open showing the Repacking progress. Dont close my Blue Window anytime during it the repacking process.
After 100% repacking is done the Black Window will close automatically and you can now press any key to Continue
[*] Check NEW F2FS ROM directory for the Repacked ROM
[*] Flash and Enjoy
[*] Cleanup the working directory cleanup.bat (Cleans everything including original input ROM.Only a copy of the Output ROM is maintained)
[/LIST]
***FAQ's***
Q. I get errors compiling the ROM on my XYZ Windows Version?
A. Read through my steps once again especially point 1 & 2. Hopefully u can get it to work.
If you think you are doing everything correctly post it on the thread and Ill try to reply within 24Hrs.
Q. I want to do it on Linux !! Why you no create bash scripts ?
A. Im not good at bash scripting !! Also dont own a Linux Distro so cant help you guys !! But look here @jolinnard has a script for Linux users
https://github.com/figue/f2fs-scripts/blob/master/convert_ROM_to_f2fs.sh and make necessary changes for Hammerhead updater script if any
Q. I can do the same with the Convert to F2FS apk on the Playstore ?
A. Sure you can. Converting on mobile is easier also. But only reservation is that it is paid.Not everyone can afford it.
Also time permitting Ill create a Android Terminal Script based on jolinnards script for Linux.
Q. Do you think I can convert it myself ?
A. Yes its just clicks . Read my steps and do it you wont go wrong.
Download Links
1. V1.1 OLD
2.V1.2 NEW
Changelog
Code:
V1.0 Intial Release
V1.1 : Add Device Support
1) Added Device Compatibility : Nexus 5
2) Scripts now will come seperate for each device.
3) Did some cleaning up on my messy script
V1.1 : Add more Boot.imgs for N5
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
[user=4851200]@Rohit02[/user] For being the beta tester
[user=14325584]@kdh2834[/user] For his AOSP Kernel
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Screenies
Screenies atlast
{
"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"
}
Excellent test on
Big thanks
c-rom v6.4 Network Connectivity fail
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
I dont own a HH so not much I can help you with !! But try flashing a different kernel on top of it , think it should work !! And does c rom used the aosp kernel in the first place !! Look at the thread for modified Kernels , i guess flashing one should solve your problem !!
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img (AOSP) that NABENDU1 provide inside his tool will not work with your rom.
c-rom is aosp based.
micr0g said:
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img that NABENDU1 provide inside his tool (AOSP) will not work with your rom.
Click to expand...
Click to collapse
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
belictony said:
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
Click to expand...
Click to collapse
Okay you have the com.androidprocess phone fc problem right !! If its only that Ill patch the kernel myself and get you a new one in a few mins and rest assured it will work for sure !!
rabbo3 said:
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
Click to expand...
Click to collapse
Yup what kind of Rom u use !! If it has differential update like Mokee OS or xdelta ( I dont know xdelta/opendelta in detail ) like Omni I can create some kind of allied script for it too !! Put the same question in the N7 2012/N4 but dint get any responses for it mosly due to devs still use the traditional way !! Anyways if anyone wants patching for those im up for the task !!
EDIT: Version 1.2 for HH online ( Bigger Size due to 4 boot.imgs included in the script itself)
Dl Link : https://mega.co.nz/#!dxcVmQRS!5zv6RCqJs82rv5-aW3GqICW5YgCPuZtUhiH0F1vpVP8
Changelog:
Added CM boot.img ( Untested by me ) thx to @kdh2834
Added Purity boot.img ( Untested by me) thx to @kdh2834
Added AOSP com.android process phone fc boot.img ( Untested by me) thx to @me
Kindly post feedback on the thread !!
I will fix the screenies sometime later or tomm
I've used this tool to successfully switch over to f2fs-all with crDroid (a CM based rom). My biggest problem, however, is that I am completely unable to flash elementalx afterward because it freezes on boot. Anybody found a way to fix this?
Edit, I'm an idiot. I found out I have to manually mount /system before flashing ElementalX
fantastic job, works great with cm11-m6,very faster
Great!
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
tavocabe said:
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
Click to expand...
Click to collapse
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
NABENDU1 said:
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
Click to expand...
Click to collapse
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
callidus_ex_de_latebros said:
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
Click to expand...
Click to collapse
Moto G is infact already has /data partition in F2FS file format !! The only thing is making the cache and system full f2fs !! For this firstly your kernel dev should take a initiative to create a fully compatible f2fs kernel and also a f2fs recovery !! Once that is done I would be more than glad to help you guys out !! Anyways till then enjoy f2fs on /data !!
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
Works fine on my crDroid setup. Did it work for you before with Euroskank? Have you tried toggling from MTP to PTP and back? If you have a secure screen lock in place, are you ensuring that you have unlocked the phone after plugging it in? Are you waiting to plug the phone in until after it's booted up? Just trying to rule out the obvious troubleshooting steps
Sent from my Nexus 5 using Tapatalk
work in 4.4.3?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
It works for me using omni-elementalx.
danielalonso said:
work in 4.4.3?
Click to expand...
Click to collapse
Yes
To @NABENDU1
Hi, so far everything is good, only complain is that most of the times when I reboot to recovery and flash any update to rom/kernel or when I add a new rom using multirom (tested and working good with omni, slim and paranoid), when finished and reboot the phone I see the boot screen many times. Like a bootloop but eventually it makes it to the rom or the multirom menu to select a rom. Is this because of my configuration of f2fs with multirom or maybe the kernel I use (elementalx shared with all the roms)?
@NABENDU1 thank you very much for this, it's quick and easy as well as educational (to me)
Related
{
"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"
}
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
This is an unofficial build of CM11.0.
This is an attempt to stay close to official cm11.0 and not make crazy hacks to make things working.
This is a pure CM build, only contains official CM features. I will not add any other external feature/app/etc.
For an up-to date working/not working list, bug tracker, useful guides & FAQ, visit our website:
http://legacyxperia.github.io
WARNING: This ROM uses a modified internal memory layout.
Our /system partition is originally 400MB but this space is not enough for a fluid kitkat experience and a full installation with proper google apps.
Our /cache partition is also too small to fit art-cache when we enable the ART runtime. We originally had 100MB /cache but art-cache needs ~150mb of free space.
I have repartitioned the internal memory layout, giving:
450mb in /system
469,5mb in /data
8mb in /cache
If you want to use this ROM you will always have to use the included kernel or use a kernel that includes the layour changes. Bug reports with non-standard kernels will be ignored.
You will have to wipe the device and make a clean install.
You cannot restore nandroid backups from previous android versions or restore nandroid backups from this ROM to other ROMs that don't use the new partition layout since you risk corrupting the data.
I suggest to use Titanium Backup, Helium or any other similar app to backup your data if you really need to.
Requirements:
* Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
* LT15i (Arc) users need to flash LT18i (Arc S) ftf
* MT15i (Neo) users need to flash MT11i (Neo V) ftf
Steps required for correct installation (order is important):
1: Flash boot.img in fastboot & reboot into recovery
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
2: Enter recovery, go to mounts and storage
3: Format /system, then /data and then /cache (Important step!)
4: Flash update zip
5: Flash gapps (recommended package is the one provided in the link below)
Steps 1.1, 2 & 3 are not needed when you install new cm11 nightlies on top of older cm11 builds in the future
If you want to return to a ROM that doesn't use the new partition layout, you need to follow the above steps again (only replace boot.img & update zip with the ones you want to use).
How to build:
[GUIDE][DEV] How I build my own CM11.0 test builds
Changelog:
Release/nightly changes
Working/Non-working list
CM11.0 with new kernel 3.4 status
Downloads:
https://s.basketbuild.com/devs/LegacyXperia
PLEASE DON'T MIRROR OUR UPLOADS
Recommended Google Apps:
Google Apps Minimal Edition
NOTE:
Following xda's rule #12 spirit: If you are developing something that is based on my work, you MUST first seek my permission, you must add my name in the credits and you must add links pointing to my original thread and to my github sources.
Breaking this rule will lead me to report the thread to the moderators.
NEW!!! BUG Tracker
If you want to help fixing those bugs, please report the bugs in the bug tracker. Thanks!
Logs are needed (logcat/dmesg/last_kmsg), not just "got FC" or "+1" useless replies.
XDA:DevDB Information
LegacyXperia, ROM for the Sony Ericsson Xperia Mini, Mini Pro, Active
Contributors
mikeioannina, nobodyAtall, pcfighter, Blefish
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest version of official ICS firmware: 4.1.B.0.587 or the latest supported baseband: 8x55A-AAABQOAZM-203028G-77
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: nightly 20140702
Beta Release Date: 2014-07-02
Created 2013-11-27
Last Updated 2014-09-06
Reserved
## Alpha build 20131127 - cm-11.0
* Latest cm11.0 changes
* Initial KitKat 4.4 build
Builds will roll alphabetically for all devices until tomorrow
Please do not spam the thread with "thanks" posts.
Only use the thread for development discussion, anything else belongs to the Q&A thread.
Nice Working / Not working list for a first alpha built! :good:
Please respect the developers wishes and do not post "Thank You" and "waiting" ect. in the thread, if you wish to say thanks simply click the thanks button.
Make sure to read all posts including post#3 where Mike says:
mikeioannina said:
Please do not spam the thread with "thanks" posts.
Only use the thread for development discussion, anything else belongs to the Q&A thread.
Click to expand...
Click to collapse
Thread cleaned
Such a great work!
is there any hope to have ART working in our phones? any goods about having ART in our device or it doesn't make much difference for us?
(sorry for too many "?" )
Mobile data now working
First of all thanks for bringing KitKat to our devices
Now to the issue, everything is working fine except mobile data. The mobile data connection checkbox is checked and to be on safer side roaming checkbox is also checked, still no internet connection or any E or H sign on Network icon
EDIT::
Toggle network mode to 2G and 3G, 4 to 5 times then automatically seems to work, I dont know what triggers this
anyway now all things are workind and is buttery smooth
deamonoid said:
First of all thanks for bringing KitKat to our devices
Now to the issue, everything is working fine except mobile data. The mobile data connection checkbox is checked and to be on safer side roaming checkbox is also checked, still no internet connection or any E or H sign on Network icon
After that i checked the APN it was there and enable, then I manually added the APN configuration still no luck.
This problem is not mentioned in Working/Not working list, so thought this would be a issue.
Any more I can do to help you solve this problem, then it will be my pleasure :highfive:
and my device is coconut(wt19i)
Click to expand...
Click to collapse
have you try to reinstall the rom with a full wipe once again ?
will report you as soon as possible, but i though the data connection normal and had no issue.
installed
okay, I installed the ROM, its very smooth and looks awesome
But since i got an MDPI LWW, layout bugs are there (already reported by mike)
rest is fine!
The smultron build is bootlooping in my device. With or without wiping, with or without gapps. Tried redownloading as well. I thought it might not be fully uploaded but it has been sitting at 170mb for a while now
i have xperia ray, what about perfomace? better than 4.3 ?
Why??
No USB mass storage. But why?
Bug in recovery
Hey Mike I found a bug in the CWM recovery while installing the kk-gapps the installation blue bar went outside than the defined space...
And the other thing is not a bug but a concern where is the screenshot option....
good
Arbelzapf said:
The smultron build is bootlooping in my device. With or without wiping, with or without gapps. Tried redownloading as well. I thought it might not be fully uploaded but it has been sitting at 170mb for a while now
Gesendet von meinem NookColor mit Tapatalk
Click to expand...
Click to collapse
I flashed it in my smultron and it boots good and works well. Still testing!! the 4.4 launcher doesnt have swipe left to google now even it is ON in google settings.
---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------
siddharthnair96 said:
Hey Mike I found a bug in the CWM recovery while installing the kk-gapps the installation blue bar went outside than the defined space...
And the other thing is not a bug but a concern where is the screenshot option....
Click to expand...
Click to collapse
I had this bug too. In CWM the blue bar went beyond the screen and it stayed as "cleaning up and setting the meta data" for a long time, and it got complete. I have never encountered this before.
hi mike thanks sooo much for rom
for now all things runs cool and superfast
i have 2 questions:
1.where is the brighness control in status bar??i mean with scrolling in there?!
2. i have this bug in cm10.2 too
in phone app whene i export my contacs from sd card when i go to phone app it gives me FCs
in cm10.2 i found a way too fix it:i go to phone settings and disable the auto complete dialing .
but in cm11 there is no option like that and at every luanch it gives me FC(
plz help meeeee
Link2sd problem
Link2sd not working, Link2sd can easily link the internal app but when opening the app it is force closing, when I checked the app status the library file was not linked. I then again linked the file, but no use the app is still force closing
Is Link2sd supported for Android 4.4?
I will post logcat on bugtracker
Sent from my Xperia Live with Walkman using Tapatalk
Link2SD works but...
deamonoid said:
Link2sd not working, Link2sd can easily link the internal app but when opening the app it is force closing, when I checked the app status the library file was not linked. I then again linked the file, but no use the app is still force closing
Is Link2sd supported for Android 4.4?
I will post logcat on bugtracker
Sent from my Xperia Live with Walkman using Tapatalk
Click to expand...
Click to collapse
Same here mate... Link2SD works with 4.4 Kitkat... i think its a problem with some other compilation... Let Mike look into it I guess he may be able to do something... When i open the app it works but after linking Super Backup to the SD card Super Backup Force Closes every single time.....
Arbelzapf said:
The smultron build is bootlooping in my device. With or without wiping, with or without gapps. Tried redownloading as well. I thought it might not be fully uploaded but it has been sitting at 170mb for a while now
Gesendet von meinem NookColor mit Tapatalk
Click to expand...
Click to collapse
Make sure you've flashed the right kernel (which is included in zip).
mihaum said:
Make sure you've flashed the right kernel (which is included in zip).
Click to expand...
Click to collapse
Pardon my ignorance. My Mini is a secondary phone for toying around with and I don't use it that often. So I'm not used to the whole "flashing kernel first"-thing which I haven't seen on other devices before.
Anyway, it's right in the OP which I failed to study carefully enough, so sorry for being stupid.
EDIT: Flashed successfully, obviously
@Arbelzapf, no problem - we're just humans after all
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
{
"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"
}
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
Portal Link: http://www.xda-developers.com/android/twrp-recovery-now-available-for-the-xperia-u-p-go-and-sola/
Click to expand...
Click to collapse
Installation:
since our device developers are constantly trying to fix bugs, they are always changing something in init.*.rc files for testing. For this reason I can't post a regular boot.img file because it won't work. For now, I've created a script that will take all init.*.rc files from current rom's boot.img and then compile new boot.img with TWRP inside it.
Note : For Rooted & Unlocked Bootloader Only
Note : For 4.4 ROM (should work on older version of android upto 4.1). I don't own XP. So please provide feedback
1) Download the latest zip file.
2) Extract it in a folder and place your current rom's boot.img inside that folder. (it must be named boot.img)
3) Connect your phone with PC. (adb must be working)
4) Open your command line and cd to that folder
5) For linux users, type
Code:
chmod 755 run_me.sh
./run_me.sh
For windows users, type
Code:
run_me.bat
new boot.img file will be created in the current directory named new_boot.img. Power off your phone and flash the boot image.
Code:
fastboot flash boot new_boot.img
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
To ROM makers
if you include it in your ROM, please give proper credits cause I've spent almost a month trying to port this.Thanks.
Download
recovery_install_XP.zip - 6.43 MB
Source
TWRP source -> https://github.com/omnirom/android_bootable_recovery
Credits
all teamwin members, especially @Dees_Troy for giving me constant advice
@munjeni for his support and answering all my questions
@percy_g2 for providing gyroscope fix in touch
Changelog 21/03/2014
booted
full touch working
adb working
usb mass storage working
fixed show battery capacity & charging status (+ icon next to percentage)
reboot to bootloader/recovery working (from twrp menu)
reboot to bootloader/recovery working (from rom)
battery led to indicate battery status
brightness slider working (under settings=>screen in twrp)
F.A.Q
1) Are CWM backups compatible with TWRP ?
Ans: CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it.
edit: kernel not supported, stock rom, anyway thanks bro, good job!
miui
MIUI 5 (4.2.2) works +++
Confirmed working on SlimKat 4.4.2 by @DroidModderXtreme. Really good job man!
Sent from my Xperia P using XDA Premium 4 mobile app
kosmos-2011 said:
MIUI 5 (4.2.2) works +++
Click to expand...
Click to collapse
kopter36 said:
Confirmed working on SlimKat 4.4.2 by @DroidModderXtreme. Really good job man!
Sent from my Xperia P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Pls confirm if everything is working according to changelog. Thanks
Well, noob Coder Here's It
booted
full touch working
adb : I dont know how to check
usb mass storage: working super fine
battery percentage is showing... as it is showing in my phone 14%+(guess thatz it)
reboot to bootloader/recovery working (from twrp menu) = working well
reboot to bootloader/recovery working (from rom) =working
battery led to indicate battery status=working
brightness slider working well
Buddy, itz cool to see someone from my country helping here. Thnx for your effort.
MIUI 4.2.2
booted yes
full touch working yes
adb working ? yes
usb mass storage working ? yes
fixed show battery capacity & charging status (+ icon next to percentage) yes
reboot to bootloader/recovery working (from twrp menu) ? yes
reboot to bootloader/recovery working (from rom) ?
battery led to indicate battery status ? yes
brightness slider working (under settings=>screen in twrp) ? yes
Who can make zip for recovery for CM11?
Sent from my Xperia P using xda premium
Xperia_Fans said:
edit: kernel not supported, stock rom, anyway thanks bro, good job!
Click to expand...
Click to collapse
you're on locked BL ? If not, it should work. Did you try it?
kaziupal said:
Buddy, itz cool to see someone from my country helping here. Thnx for your effort.
Click to expand...
Click to collapse
anytime
after flashing this kernel root doesnt seem to be working on miui 4.2.2
work parfectly in stock rom based ( dark) with nemsis v6.3 as original karnel
i thinks that is better than cmw
thanks a lot
Using it on latest carbon but fix permission failed will provide logcat later
Sent from my Xperia P using Tapatalk
ibudanov said:
Who can make zip for recovery for CM11?
Sent from my Xperia P using xda premium
Click to expand...
Click to collapse
Not sure it's possible, since the boot.img is compiled a script that runs on the device.
I suppose it would be possible to do it by running the script on an XP with CM11 installed then using the compiled boot.img to create a flashable ZIP.
I'm going to try do this once I get to my computer.
Are you using Percy's CM11?
not working
i have an XP with the stock rom .100, the stock kernel and Unlocked Bootloader. I followed the instructions but it failed.
here's a screenshot of cmd and if you see something wrong in it tell me plz.
Thanks for your great work !!
big-A said:
i have an XP with the stock rom .100, the stock kernel and Unlocked Bootloader. I followed the instructions but it failed.
here's a screenshot of cmd and if you see something wrong in it tell me plz.
Thanks for your great work !!
Click to expand...
Click to collapse
check your folder, you must have a new file: "new_boot.img" and after fastboot it via flashtool
no
dastane said:
check your folder, you must have a new file: "new_boot.img" and after fastboot it via flashtool
Click to expand...
Click to collapse
there's no new_boot.img in the folder it's clear in the cmd screenshot that the process failed...
did you copied your curent karnel file in this folder and rename it into " boot.img" as its said in the OP??
djkk16 said:
after flashing this kernel root doesnt seem to be working on miui 4.2.2
Click to expand...
Click to collapse
+1
no root acces
now i'm using Liquid smooth based 4.4.2
the probleme is from the original karnel not from this recovry; waiting for karnel fix and i will re flash twrp
TWRP for Transformer Pad TF201T
{
"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"
}
MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1
Changelog 2.7.8.2
- All Upstream changes
- Small changes to the 'new theme' (thx z31s1g)
- Added flash to staging partition, via flash image feature.
Changelog 2.8.7.1
- Removed ability to flash raw .img files....
- gui: keyboard: support longpress label offset, code cleanup ( Thx @_that)
- Added flashable zip
- merged upstream changes
Changelog- 2.8.7.0
- Fully merged 2.8.7.0 source from upstream
- Removed SU from twrp ( Its useless & only takes up extra room)
Changelog- 2.8.6.5
- New theme fully implemented ( Huge thx to @z31s1g ) Still a WIP
- Fix mount -o bind error on recreating /data/media/0 (Huge thx to @xiaolu ) & ( @_that )
- All upstream merges by Team Win
Changelog 2.8.6.1
- GUI: Prevent duplicate page overlays. Thx Matt & _that
- Replace legacy DEVICE_RESOLUTION with the new TW_THEME
- Using new common repo to build recovery.
- Build with grimlocks-5.1 kernel from zombi
- All upstream changes. Thx TeamWin
Changelog- 2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Changelog- 2.8.5.1
- Added dock sd card support to twrp
Changelog- 2.8.5.0
- Added formatting of ext sdcard for ROM2SD & DATA2SD
- Added ability to backup ext sdcard partitions
- Added reboot to recovery & reboot to bootloader from with TWRP
- Fixed error formatting /data to f2fs <- Thx Dees Troy for this fix
- A few upstream changes
Click to expand...
Click to collapse
UPGRADE INSTRUCTIONS----------------------------------------------------------------------------------------------------------------------------------------
- Flashing recovery with fastboot
- Boot tablet into fastboot.
Code:
fastboot -i 0x0B05 flash recovery foo.img
- Replace foo with the file name.
- Once flashed reboot into bootloader.
Code:
fastboot reboot-bootloader
- Enter recovery.
----------------------------------------------------------------------------------------------------------------------------------------
- - Flashabale zip
- Boot into current recovery .....
- Flash the zip it is signed so turn that on ......
- Reboot in to android, fully
- Boot into bootloader, enter newly flashed RCK ....
----------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
TWRP for TF201T [KANG], Tool/Utility for the Asus Eee Pad Transformer Prime
Contributors
lj50036, hardslog
Source Code: https://github.com/zombi-x-lp
Version Information
Status: Testing
Created 2015-03-06
Last Updated 2015-03-06
DOWNLOADS
OLDER VERSIONS
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] WILL UPLOAD
The more you know
JOIN US ON IRC !!!https://webchat.frt/
Channel: #zombi-x
HOW TO TAKE A RECOVERY LOGYou will be taking this log cause of some kind of error message .....
Once you get and error message, here is how to retrieve a recovery log ....
Using a PC with adb/fastboot installed on it, and if windows the correct drivers. ....
Code:
adb pull /tmp/recovery.log
This log will be in the same directory as the terminal/cmd window is cd'd into ....
Now you have the log, upload it to a pasting site or for download, and give us a link....
lj50036 said:
it may appear to hang on the twrp curtain, let it boot there is nothing wrong here
Click to expand...
Click to collapse
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
flumpster said:
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
Click to expand...
Click to collapse
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
lj50036 said:
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
Click to expand...
Click to collapse
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
https://www.androidfilehost.com/?fid=95916177934537081
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
Got it if you would like to pull the download your call ....
Yes I will go back to stock bootloader then upgrade .....
Will let you know how I get on ....
Thx Josh
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Lavrentsii said:
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Click to expand...
Click to collapse
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
lj50036 said:
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
Click to expand...
Click to collapse
Cheers mate. I am in bed at the moment but I will make you another test tomorrow with your recovery added into it for you to try.
lj50036 said:
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
Click to expand...
Click to collapse
I'm testing DATA2SD on a non-supported ROM (Katkiss LP with Grimlock 300t/201 kernel) and so far with this recovery and the DATA2SD zip it seems to be working fine. This looks pretty promising
lj50036 said:
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
Click to expand...
Click to collapse
I can confirm that this works thanks to Josh's help/instruction on doing it. He is an awesome & great teacher as I learned so much from him. GREAT RECOVERY! Thanks again Josh! :good:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
elchevi said:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
Click to expand...
Click to collapse
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
lj50036 said:
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
Click to expand...
Click to collapse
Maybe choosing among some predefined templates would do the trick for most users. But yes, it can be potentially problematic hehe
Thanks!
Img vs. blob
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
JuraP said:
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
Click to expand...
Click to collapse
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
lj50036 said:
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
Click to expand...
Click to collapse
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
JuraP said:
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
Click to expand...
Click to collapse
It does not matter you can leave it .img or rename it .blob will not matter ....
Thx Josh
Hello everybody,
I've just compiled PACMAN-ROM for my new Z3C. Current version is PAC-LP MR1 Beta2.
Device trees are CyanogenMod's so probably all device specific CM-bugs will be there too.
The boot.img inside the zip contains CM 12.1 kernel and "Cyanogen Recovery" (no backup right now!).
For alternative recoveries/kernels scroll down to "TESTED - WORKING"...
If the rom is stable for daily use (as I hope) I'm gonna build newer version periodically (depending on PAC & CM updates).
{
"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"
}
EDITS:
2015-07-09:
i've been trying to get rid of the latest problems, i.e. crashing android browser, opera browser, voice recorder and google apps (if installed). tried 4 or 5 builds in the meantime. i've got no idea why and not the skills to search in log files.
if anyone likes to test and find out, i uploaded version from july 4th.
2015-06-25:
New Version - updated CM & PAC sources. Some new PAC features there!
Version is PAC-LP MR1 Beta2 now. Unstable with crashes.
2015-05-24:
New Version - updated CM & PAC sources
2015-05-12/13:
New Version - updated CM & PAC sources
Volume bug on in-call got solved today!
2015-05-01:
I've uploaded an EXTRA boot.img including XZDualRecovery provided by NUT's!
http://nut.xperia-files.com/?ql=34070511dc3ee6809f305c66a5fa122fcbf9dcff
Flash it before or after installing the PACROM zip. It contains the zip's
kernel + DualRecovery. Installing the rom zip will overwrite recovery again
so for backups it might be necessary
to flash it always before installing a new zip, e.g.
2015-04-29:
- Screenshots
- Yes! I got it running. After some hours of use, it seems really smooth & snappy. No reboots.
- How I installed everything: Root on Kitkat stock rom, backup TA-partition, install
Dual-recovery, update to Lollipop rooted, make nandroid backup of hole system,
unlock bootloader, flash PACMAN boot.img, wipe data/caches,
flash PACMAN zip + GAPPS ... quite some hours of work.
TESTED - WORKING:
- 2G, 3G, 4G
- wifi, wifi hotspot
- bluetooth audio
- nfc
- usb otg
- GAPPS (mentioned below)
- titanium backup
- PAC customizations (not all tested)
- video playback on youtube, vlc, mxplayer
- camera & video recording
- GPS using Google Maps
- headphone sound
- XZDR recovery (version 2.8.15 not working): http://nut.xperia-files.com/
- FOTA TWRP recovery (persistent in fota kernel partition): http://forum.xda-developers.com/z3-...12-nightly-t3010550/post58854063#post58854063
- M5 kernel (CM12.1 based): http://forum.xda-developers.com/z3-compact/orig-development/kernel-m5-kernel-t3115498
BUGS:
- phone call volume loud / not reducable in dialer app. (skype & whatsapp calls are alright) solved on 150512
- If alarm clock is set active -> reboot leads to normal shutdown -> deactivate alarm for that case
- photo: Little fish-eye effect on short distance (it's not that little actually)
NOT TESTED YET:
- encryption
Installation notes: Unlocked bootloader required
- flash boot.img (rashr on phone/ fastboot on pc), then boot into custom recovery
- wipe cache, wipe art/dalvik cache
- when coming from a different rom wipe data (factory reset)
- when changing between different gapps packages format system may be useful
- flash rom zip
- if needed flash gapps zip
Download PACMAN: https://www.androidfilehost.com/?w=files&flid=30581
Download GAPPS: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Device trees used: https://github.com/filou76/manifest/blob/master/z3c.xml
Credits!!!:
PACMAN project for their great and cool work!! www.pac-rom.com/#Home
All CM developers for giving a solid custom rom ground!!
All Z3C developers who are trying hard to make this great phone ready for daily use, especially those couple of root/bootloader/recovery hackers!! bilbao1 for the great howto root/backup etc! [NUT]'s for this very cool online kernel builder!
Google, of course
Screen shots please...
I guess its a cm based. So we need unlocked bl right?
shakkirk said:
Screen shots please...
Click to expand...
Click to collapse
It's the same as any Lollipop based PAC ROM, so just search the web for pics.
basti2909 said:
I guess its a cm based. So we need unlocked bl right?
Click to expand...
Click to collapse
Yes.
at least a custom rom for z3c. thanks man for your efforts...
basti2909 said:
I guess its a cm based. So we need unlocked bl right?
Click to expand...
Click to collapse
I think PAC is AOSP & CM based. Custom kernel. Unlocked bootloader, yes.
drorcun said:
at least a custom rom for z3c. thanks man for your efforts...
Click to expand...
Click to collapse
Happy to build actually it's not that difficult with CM device support. Probably I'll build some monthly versions or so...
drorcun said:
at least a custom rom for z3c. thanks man for your efforts...
Click to expand...
Click to collapse
just what i wanted to write. big thanks
hope we can see some more, maybe validus/resurrection remix? (maybe i should get me better informed to do it myself^^)
becks0r said:
just what i wanted to write. big thanks
hope we can see some more, maybe validus/resurrection remix? (maybe i should get me better informed to do it myself^^)
Click to expand...
Click to collapse
:good: In case of resurrection remix you only need to add/edit 1 file (local_manifest) to be able to compile a working rom. All the rest it just setting up ubuntu, init/sync repo an start building ...
Hmm it could be a reason to unlock bootloader.,)
XZDualRecovery
I've uploaded an EXTRA boot.img including XZDualRecovery provided by NUT's! http://nut.xperia-files.com/?ql=34070511dc3ee6809f305c66a5fa122fcbf9dcff
Just flash it before or after installing the PACROM zip. It contains the original kernel + DualRecovery. CyanogenRecovery really sucks, not even a way to make backups. Now we can
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
beflythis said:
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
Click to expand...
Click to collapse
there's nothing like this included. as far as i know custom roms/ custom kernels can't handle drm keys from TA partition. not sure about flashable drm replacement, i don't think it will work, but maybe it does
perhaps someone knows more about this sony image processing stuff.
isn't that all software based? if so, i could imagine that a good camera app (FV-5 or something like) can bring the same results.
Great work mate. Been running a few hours with the updated boot.img
Hopefully there is no "memory leak"
beflythis said:
does this have a camera fix included, or does that need to be flashed separately? I don't have a backed up TA partition, so I rely on the fix for image processing (like many others on here, I'm sure).
thanks in advance and nice to see the ROM!
Click to expand...
Click to collapse
That fix is only useful on stock Sony based rom's.
bugs update
(1) i found a small, almost funny bug. couldn't reboot to recovery today because phone always ended with shutdown. i desperately flashed the boot.img again but no change. only after deactivating everything i thought not being active at installation the problem disappeared.
well, it's the active alarm, that i use every morning ...
(2) in call volume issue seem's to be somewhere hidden in android_device_sony_z3c/audio/mixer_paths.xml of the repo. just in case someone likes to search :laugh:
I have noticed a small bug, could be just me though. When rebooting while plugged in to the USB charger it goes as far as the Sony logo then freezes until I unplug it. How would I go about submitting a bug report for it?
Sent from my Xperia Z3C using Tapatalk
mrrflagg said:
I have noticed a small bug, could be just me though. When rebooting while plugged in to the USB charger it goes as far as the Sony logo then freezes until I unplug it. How would I go about submitting a bug report for it?
Sent from my Xperia Z3C using Tapatalk
Click to expand...
Click to collapse
Hi, thank's for that! I've just reproduced what you wrote. On my phone this is also connected to active alarm clock. It's rebooting fine when alarm is off. So, quite the same as my last post.
I have no suggestion about real bug reports, because of 2 reasons: this is an unofficial build, primarily for myself ... but shared. I would stop building if Z3C would get official PAC support. And I've just started building roms 2 months ago. So, I'm not having the skills (yet) for advanced debugging. Right now it's more like being voluntary apprentice :laugh: ... I'm gonna add your input it into 1st post.
For now stability of this rom is mainly dependent on PACROM itself and official CM support.
Im glad you could reproduce the same bug. I think you have done a great job mate. I'm loving this ROM and appreciate your efforts. I'm trying to figure the dev side of things myself, not having much luck yet.
Sent from my Xperia Z3C using Tapatalk
Good job, m8!
Can someone post a picture, taken by camera on this phone with this rom ?
A picture of a door , or a wall, for example. Any picture featuring a rectangular shape with straight lines.
I had a broblem be4 on CM12 @z3c , the camera ( any camera app ) took pictures, distorting proportions, like there was a fisheye filter applied
{
"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"
}
## Introduction ##
MultiROM is one-of-a-kind multi-boot mod for Nexus 6. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!:
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
## Installation ##
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 4 parts, but you really only need to install 3 parts:
MultiROM Installer:
TWRP Modified Recovery:
Patched Kernel: Primary roms Must have a Kexec Hardboot Patched Kernel
MultiRom UnInstaller:
Adding ROMs:
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 5.0 after first boot (with dalvik cache generated and connected to google account) takes about 1 GiB of space.
Using USB drive:
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs:
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Special Thanks to @Tasssadar..
XDA:DevDB Information
MultiRom V32 Resurrected, ROM for the Sprint LG G3
Contributors
Eliminater74, thewalkingdude, Tasssadar
Source Code: https://github.com/Tasssadar/multirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2015-07-12
Last Updated 2015-07-12
reserved
MultiRom V32 Installer: multirom-20150711-v32-UNOFFICIAL-ls990.zip
MultiRom Modified TWRP Recovery: TWRP_MultiRom_2.8.7.x__ls990_20150712-signed.zip
MultiRom Kexec Hardboot Kernel By @777jon: AOSP-777-Kernel_ls990-R10.zip
MultiRom Uninstaller: multirom_uninstaller.zip
Warning: Kernel is for LP 5.1 Only with 32gb variants at question. Sorry 16gigers, I havent done one for you yet.. but you can try this one.. It just may work.
Note: You can compile your own Kexec Hardboot Kernel as well. @fechanaitor and @777jon both have the Correct MultiRom patch that works with this version.
SideNote: Little UnKnownFact. This MultiRom is set up to allow installing Stock OEM roms as secondery as well..
And @777jon's 777Kernel does work on secondary as well with this version..
reserved
reserved
Thank you very much! I just finished Navel kernel with 777jon's kexec patch! I'll give it a test tomorrow.
Our original Multirom, was giving me tz demigod crash.
A million thanks, again!
Update: MultiRom V32 resurrected Now available for download.
engine95 said:
Thank you very much! I just finished Navel kernel with 777jon's kexec patch! I'll give it a test tomorrow.
Our original Multirom, was giving me tz demigod crash.
A million thanks, again!
Click to expand...
Click to collapse
Actually that patch is my patch. I created it with the help of @Tasssadar because the old patch that @Skin1980 did didnt work so well.
Btw, my version also will boot stock OEM roms as secondary as well..
Figured you might want to know this is working. And it mostly is!!
I've got XenonHD as Primary. And CM as secondary. And that works.
But as for stock as secondary, I'm not having any luck there. It gets stuck at the LG logo, requiring a battery pull.
Nice work! Thanks again. :good::good:
Edit: I've tried stock from a backup and fresh install. On internal and external. No love. It just stays at the LG logo for over 10min, then I end up pulling the battery.
Sorry I didn't get you any logs, but I will later when I can play with this more.
engine95 said:
Figured you might want to know this is working. And it mostly is!!
I've got XenonHD as Primary. And CM as secondary. And that works.
But as for stock as secondary, I'm not having any luck there. It gets stuck at the LG logo, requiring a battery pull.
Nice work! Thanks again. :good::good:
Edit: I've tried stock from a backup and fresh install. On internal and external. No love. It just stays at the LG logo for over 10min, then I end up pulling the battery.
Sorry I didn't get you any logs, but I will later when I can play with this more.
Click to expand...
Click to collapse
hmm.. can you send me a log? I know hooks.c was added.. thats what is allowing the stock.
Problem with stock is it uses a unfinished fstab.. so it causes multirom to abort.. so the hooks.c allows it to continue even if the fstab is incomplete...
as for your problem, I need to know what version of stock. I never tried the LP versions yet.. and if you have a log, could you plz post it or send it.
ill look at it and if I cant figure it out, ill send it to @Tasssadar to see if he can figure it out.
As I dont own this device, even know I have a G3 D851.. So I cant really break down and test it like I would with my own.... I know I can install stock and run it.. I have done it.
but I havent messed with that in a long time too. Just send me a log if you can.
BTW, thanks for posting that it works. I been waiting on that.. I just got confirmation that the D855 Global port I did works too. so im on a role here....
Now if I can just get my kernel to build with no issues ill be ok..
It sucks building blind for sure.
Im using ZVA which is our latest update. BarePapA with NavelA kernel to be specific. I have a commit for the kexec patched kernel but it's not working. If you want to look at it.
Hopefully I can get you the logs later today. Do you want the one that Multirom provides? Or is there a better one to help you?
Also, following your International version, we have 4 memory banks and have to "Bump" our kernels also. Most of us use the old ZV4 bootloader and add /system, /boot, and/modem images, to keep it unlocked. I don't know if that changes or helps at all.
engine95 said:
It sucks building blind for sure.
Im using ZVA which is our latest update. BarePapA with NavelA kernel to be specific. I have a commit for the kexec patched kernel but it's not working. If you want to look at it.
Hopefully I can get you the logs later today. Do you want the one that Multirom provides? Or is there a better one to help you?
Also, following your International version, we have 4 memory banks and have to "Bump" our kernels also. Most of us use the old ZV4 bootloader and add /system, /boot, and/modem images, to keep it unlocked. I don't know if that changes or helps at all.
Click to expand...
Click to collapse
hmm msg me on hangouts and maybe I can help you get that patch to work right for you. Its all in the kernel.. as for bump.. the device tree automatic bumps all the devices that need it.
you can either look at my profile and get the nfo for hangouts or pm me and ill give it to you or you can give me yours... then we can see whats going on.
Im half asleep while typing so i might sound a little offff
Fix to boot MultiRom and get it working
Thread Moved to: XDA Link
Thread closed per OP request.