Database Users

[TOOL][WIN/LINUX] AiO•TooLBoX [BOOTLOADER UNLOCK + ROOT/UNROOT][v3.0]

My First Ever Application Developed. So please support if it is worth
AiO•TooLBoX​
Features :-
Bootloader Unlock Supports HTC & Sony Devices.
Unlocks your Bootloader At a Click.
Root/Unroot your device.
Flashes a Custom Recovery/Kernel.
Multiple Device Support.
How to Use :-
Download the App.
(WIN-ONLY) Place it in a folder with no spaces in its Path { (e.g) C:\Aio-Tb\)
(WIN-ONLY) Run App as Admin
(LINUX) Browse to the folder via Terminal And Type "./all_in_one_toolbox_linux" (without quotes) To Run
Make Sure USB-Debugging is Enabled on Your Phone.
Make Sure you have installed your Device Drivers before Starting
(As Admin on Windows).
Requirements :-
Internet Connection (For BootLoader Unlock)
Some Patience
Bugs :-
Please Report
TESTED ON MY DAD'S HTC WILDFIRE & SONY XPERIA MINI was working. Please Suggest Improvements and Better Ways.
THANKS TO :-
Revolutionary - For zergRushExploit
psneuter Exploit.
StoneBoy Tony for GingerBread Root
Bin4ry for Root with Restore Method
DoomLord for easy root kit script
All Others at forum [inspiration]
ChangeLog :-
v3.0
-Removed the GUI.. Console App Now
-Removed the BootLoader Relock method.. (Temporarily Flash Stock Roms for Relock)
-Added Root With Restore Method for Android 4+
-Fixed Broken E-Mail Account
-Improved Performance And Logging
Old:
v2.1
-Fixed HTC Stock Flash Feature.
-Better Log & Backup.
*********
v2.0
-Added Relock feature for Sony & HTC (Please Do Not Use Flash Stock HBOOT [Dev in progress])
-Added Root for other devices.
-Added Backup & Log Features.
*********
v1.0
-Initial Release
*********
Download Link :-
v3.0 - Win
v3.0 - Linux
v2.1
v2.0
v1.0
Not Tested on any tablet

is it only for sony n htc devices?can i use it for my china android phone?

fakhzanis said:
is it only for sony n htc devices?can i use it for my china android phone?
Click to expand...
Click to collapse
Just wait for v2.0. In that you can root without the need to unlock bootloader.. You must have a GingerBread or a Froyo for that

rahuliyer95 said:
Just wait for v2.0. In that you can root without the need to unlock bootloader.. You must have a GingerBread or a Froyo for that
Click to expand...
Click to collapse
can i just try this app for other android phone. is it will brick my phone?

fakhzanis said:
can i just try this app for other android phone. is it will brick my phone?
Click to expand...
Click to collapse
I don't think it will brick your phone. But still to be on the safer side don't do any experiments unless you know how to unbrick or other stuff.

could you possibly add motorola support for this you may know that motorola locks there bootloader down better than fort knox so hopefully this could help the motorola community and also help get your name out there in the process

Work on U?

But this is only if you're a generic right? Or does it unlock even the sony's with BL status NO?
Sent from my LT18i using Tapatalk 2

[DEPRECATED] Welcome to your Motorola Moto G - Resource Guide

{
"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"
}
DEPRECATED, NO MORE UP-TO-DATE, ONLY KEPT FOR ARCHIVE
Technical Specifications -
Model Number(s) -
XT1031: Boost Mobile8GB
XT1032: This Model Number is shared by International GSM Version and the Google Play Edition 8 GB/16 GB (Single SIM) EU & International GSM - 8GB/16GB. (Does not Support 1700 MHz AWS)
XT1033 : Brazil, India, Malaysia (BrightStar) - 8GB & 16GB(Brazil Colors Edition) (Both are Dual Sim) and also for Moto G (Music edition) (Dual Sim) (16GB Only), Malaysia 8GB & 16 GB are Dual Sim
XT1034: AT&T and T-Mobile - 8GB/16GB.
Frequencies / Bands:
AT&T and T-Mobile - HSDPA 850, 900, 1900, 2100 MHz; GSM 850, 900, 1800, 1900 MHz
Verizon and Sprint - CDMA:800, 1900 MHz, CDMA2000 1xEV-DO
Display Resolution: 720 x 1280 pixels Corning Gorilla Glass 3 (IPS LCD capacitive)
Screen Size: 4.5" 16 M Colors (329 PPi)
Bluetooth Enabled: Yes
Wi-Fi Enabled: Yes
Internal Memory: 8 GB (Actual Space for user data ~6 GB)
16 GB (Actual Space for user data ~12 GB)
External Memory: None
Size / Dimensions: 5.11 x 2.59 x 0.46 inches (129.9 x 65.9 x 11.6 mm)
Weight: 5.04 oz (143 g)
Battery Capacity: 2070 mAh (Not User Replaceable)
Camera: 5 MP (2592х1944 pixels) Camcorder: 720p (30fps), stereo sound rec., HDR Front-facing camera: 1.3 megapixels
Operating System: Android 4.4, 4.3
Keyboard: Touch Screen
GPS: Yes
Click to expand...
Click to collapse
Unique Features -
Motorola Assist
50 GB Google Drive Space Free
Dual Sim
FM Receiver
Click to expand...
Click to collapse
Moto G Review -
Moto G Review - Here's great thread with collated Reviews of this device. Thanks to @matmutant
Click to expand...
Click to collapse
List of Commonly used Terms -
All that is fine, but I don't know what this rooting, flashing, nandroid, Modding etc. mean? Yelp ?
Fear Not! Here's a little Cheat Sheet for you. Please thank @benjamingwynn for this. I took his original list for HTC and extended it for here. Given bellow is a Glossary of sorts for commonly used terms. Please let me know if I missed any and I will add it. Also please visit this Q & A thread. Its more than likely to answer most of your questions.
ADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AFAIK - "As far as I know"
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free (see open-source)
APK - "Android Package" an Android application
Binary - (sometimes called bin's) a group of executable files.
Brick - When the device refuses to boot at all, despite having a full battery is termed as Bricking. Most of the times, the devices gives some indication of problems such as blinking Red Led, but no other signs of life. It is also called Hard Brick. Also see Soft Brick.
Bootloader - Its a small piece of code that's embedded in the device. Its the first to be executed when the device is turned on.
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
CM - See CyanogenMod
CM10 - Cyanogenmod 10. A modified version of Jelly Bean release of Android 4.2.x as well as 4.3.x (see CynogenMod)
CM11 - Cyanogenmod 11. A modified version of Kitkat release of Android 4.4.x. (see CynogenMod)
Custom recovery - An unofficial recovery developed by other developers for your device. Its typically used to install unoffical ROMs. See CWM and TWRP.
CWM - ClockWorkMod, a project that makes Custom Recovery.
Cyanogenmod - A free open-source project based on the AOSP. It is a modded (see modded) version of the Android firmware
Dev - See developer.
Developer - A man or woman who has created (developed) software.
Deodexed - Where the two part ODEX files (see Odex) are moved into the actual APK (apk), thus making it one.
Execute - To "run" or "start" a binary
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM. (See ROM)
Flash - The process of installing a software on your device.
Flashing - See Flash.
FOTA - "Firmware over the air" this normally refers to ROM's but can refer to radio firmware (see OTA)
Froyo - Android 2.2
GB - Could mean one of two things. 1. Gingerbread or 2. Great Britain
Gingerbread - Android 2.3
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop bellow the (just as easily configurable) minimum frequency.
Honeycomb - Android 3.x. it was never released or ported to the wildfire s because it was built for tablets.
Ice cream sandwich/ICS - Android 4.0. The latest version of Android.
JDK - "Java Development Kit" an SDK for the java platform. It is needed to run the Android SDK.
JRE - "Java Runtime Environment" a collection of binarys and files to allow java software to execute.
KANG - The process of creating a code based of someone else's code.
Kernel - This is another term brought over from Linux World. A Kernel is a piece of software, that takes over from the Bootloader and then completes the booting of the device. It handles the CPU and other vital components. A modded kernel may be used for overclocking.
Library's/Libs - a set of instructions for applications to use to function. A functioning camera lib would allow the camera to be used.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
Modding - To perform a mod
Modded - to have included mods or condition after applying a mod.
Modification - see mod
Open-Source - (not to be confused with free) A piece of software that is free to edit, use, distribute and share with no charge.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
Radio Firmware - (see firmware) a type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Overclock - (not to be confused with underclock) to exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Nandroid - Its a process of taking a backup of most of the partitions in Android. This is usually performed in Recovery Console when OS is not running.
Partition - Similar to Linux, Android storage is divided into Partitions. These are akin to compartments that house specific part of the OS boot and operation.
RAM - Could be one of three meanings: 1. Memory for the CPU to process processes. 2. Random Access Memory, a place where information can be used, executed from, modified, or deleted. 3. A type of sheep.
Recovery - Its a dedicated Android partition, that has Recovery console installed. This is invisible during normal operation of the android device.
ROM - 1. A modified version of the Android operating system operating system. 2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
RUU - "ROM Update Utility" An automatic installer for Radio Firmware, ROM and HBOOT. (Predominantly used on HTC).
SD - Short term for MicroSD
SDK - "Software Development Kit" a set of tools used for software development.
Soft Brick - When the device refuses to boot despite a full battery, but shows some other signs of life, its considered as soft Bricked. Also see Brick
Stock - An unchanged version of something. Example: I just flashed stock Rom. Typically this term may be used to refer to Official firmware. But this is not the case always.
TWRP - Team Win Recovery Project. This also has a newer edition called TWRP 2.
Underclock - to change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WFS - "Wildfire S" an armv6 device made by HTC in 2011.
WIP - "Work In Progress"
Zipalligned - This is something that makes a ROM faster. Best see this link for more.
Click to expand...
Click to collapse
Ok Now that you have a hang of your device, you probably want to explore your options and maybe install a Custom Rom. Well, the first thing you will need is to Root the Device.
So what really is a Root ? Why should I do it ? Would it break my Phone ? How about my Warranty ? All legitimate questions. To start off, here's an easy guide by Lifehacker. This whole concept may seem mystical to some of us. Let me try to make it pretty straightforward. Rooting is a process on Android that effectively grants you superuser access. Think of it as Administrator access on Windows. Android is a derivative of Linux. So those from Linux should have no difficulty with this concept.
There are certain operations that only a Superuser can do. Hence you'd want to root in order to so. For ex, remove any application that is installed as System application. Just like on on Windows, Root access does come with risk, so you need to use it with care. Just because you have Root access, does not mean your phone is broken. Typically making wrong changes to system with Root access, will result in affecting smooth operation of your phone. In extreme cases, the device may be Bricked if incorrect software (Rom, Mod or others) is flashed.
When it comes to Warranty, typically Root as such does not void your warranty. But if you end up flashing anything with a custom Recovery, then your Warranty may be voided.
Rooting -
Ok so, I got what Root is and I need to be responsible in what I do. How do I get the root ? Well the first and basic thing would be to install appropriate drivers for Windows.
Next in order to Root, please follow this thread by @paulobrien . As you will see, there are two ways to go about it. Both do require your Bootloader to be unlocked. However, neither method, applies to the Google Play Edition (XT1032) as there is no supporting Custom Recovery for this variant.
If you do not have or do not wish to unlock your bootloader then you can opt for @oasoas014 's method of bootloader downgrade. You may also visit @Cooptx's more detailed guide. Note, with the most recent recoveries, you do not need to downgrade your bootloader.
Note - Flashing a bootloader is inherently dangerous. You can possibly hardbrick your device if you flash incorrect bootloader. Always check the MD5 value of downloaded file.
Only In Case of Moto G Google Play Edition (XT1032), it is possible to unlock the Bootloader on your own. You do not need to pay to get an Unlock Code from Motorola. Instead, you can follow the same method as Nexus or other Google Play Devices. Here's a nice tutorial. For those technically minded, here's Android Source Documentation of the same process. Once unlocked, the bootloader cannot be re-locked unless you flash a signed system image, (which Motorola has not made available as of 01-22-2014).
One of the first things you should do upon Rooting is to backup your PDS Partition.
[SIZE=+1]How to backup / restore PDS partition and why?[/SIZE]On Motorola devices the 'pds' partition contains information specific to your machine: IMEI, MAC address, serial number, etc. This partition can be lost by accidental format or over time due to filesystem corruption. If you have made a backup, there is a good chance you can bring your handset back to life.
==> PDS backup will help to restore lost IMEI. It is a situation when the phone reports that the IMEI is unknown. ; This works like a vaccine, apply before having issue with IMEI, after it will be too late !
Instructions:
**Root Required**
Using ADB you can make a copy of the partition and move it to a safe place (Google Drive?):adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.img​To restore in the event of corruption or loss:adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds​(assuming you've pushed pds.img to internal SDcard storage first)
Click to expand...
Click to collapse
Once rooted, some of you may wish to stick with that and not proceed any further. With root, you will want to remove some of the apps that you don't need. I wish to suggest that you take a complete backup with a tool such as Titanium Backup. That way if you accidentally uninstall/remove something that's critical to android's operation, then you can restore it. For those of you, who wish to install custom Rom, read on.
The first step towards installing a custom Rom is to install a custom Recovery.
Please note, In order to flash any custom Recoveries, you need to have unlocked Bootloader. The viable options are either follow this guide or get an unlock code from Motorola.
Custom Recoveries -
A Custom Recovery is a unofficial Recovery Console that can be flashed to your device's Recovery Partition.
Typically unofficial recoveries offer several advantages over Stock or Official Recovery. Hence the unofficial recoveries are necessary in order to flash a Custom Rom. Apart from flashing a Rom, Kernel or any other firmware, unofficial Recoveries can also take Nandroids.
An unofficial Recovery is also commonly referred to as Custom Recovery. There are two major projects that contribute Custom recoveries. One is called CWM. The other is called TWRP. Given bellow is a list of Custom Recoveries available for your device.
Note - CWM and TWRP recoveries do not support the Google Play Edition variant (XT1032). You will need to wait for Motorola to release the Kernel source code before @a1Pha can support. However Philz Touch does support Google Play Edition.
CWM Recovery v 6.0.4.5 by @a1Pha -
This is the ClockWorkMod Recovery for the Moto G. Head over to the thread for more details.
(Thread as of 12-15-2013)
CWM 6.0.4.7 Swipe Recovery from CM11 thread
CWM 6.0.4.7 Swipe Recovery
TWRP Recovery v2.6.3.0 by @a1Pha -
This is TWRP 2 project brought over to Moto G by @a1Pha. Keeping with TWRP 2, its a Touch Recovery. Head over to the thread for more details.
(Thread updated as of 12-09-13)
Philz's Touch Recovery v2.6.3.0 by @Phil3759 -
This is CWM Advanced Edition Recovery for the Moto G. Head over to the Thread for more details. Other members have reported that this is compatible with the Google Play Edition of this phone.

ROMs for Moto G
ROMs -
Given bellow is a list of known Roms for Moto G. Most of the Custom Roms for Moto G require Unlocked Bootloader in order to flash via custom Recovery. Only in the case of Stock firmware or Stock based firmware, it will be possible to flash without unlocked bootloader.
If I miss on a Great Rom, let me know.
AOSP ROMs - [KITKAT 4.4.x]
Android Open Source Project, commonly known as AOSP is a repository of Official Google Codebase for Android. Any Rom built from this code will provide a true Android Experience.
CM 11 (Unofficial) - by @Dhacker29
Unofficial release of CynogenMod 11 (4.4.2) for the Moto G. It is released only for GSM variants only. International GSM and US domestic (AT&T and T-Mobile) are supported. Please head over to the thread for details.
Nexus G - by @xmattjus
This Rom offers a pure vanilla Nexus experience on your Moto G. As of 13-01014, Modem does not work for dual sim models. Please see the thread for details.
SlimKat Unofficial - by @SpaceKiller
Following on the Traditions of Slim Rom, this unofficial port provides the same experience on Motorola G. As of 01-18-14, the rom supports only GSM Variants for EU, International and US. Please see the thread for more details.
Paranoid Android Unofficial - by @Vocoderism
Unofficial Port of the Paranoid Android Rom for Moto G. This rom is intended only for EU and international GSM variants. Please see the thread for more details.
Beanstalk Unofficial - by @Cameron581
This Rom is based on the CM codebase as well as Slim Code. It has a lot of nice features. Please see the thread for more details.
AOSP ROMs - [JB 4.3]
None Listed as of 12-31-2013.
Stock based ROMs - [Kitkat 4.4]
Stock Firmware - [KITKAT 4.4.2] by @antiquezip
The OTA Update to Kitkat 4.4.2 is posted for the U. S. GSM version of this device. It is dubbed as U.S. GSM (UMTS Version with AWS)
Please see this thread for more details.
This note, it is possible to apply this update to other Non-US GSM Devices successfully. Please look for a Guide in Post 4.
Kitkat+ Rom - [Kitkat 4.4.2] by @anerik
This is a stock based Kitkat rom. It enhances the stock Kitkat firmware and hence the name. Please head over to the thread for details.
OTA Firmware (All variants) - [Kitkat 4.4.2] by @josalaito
The original 4.4.2 release for GSM version has been re-packed for all variants of this device. It now applies to US as well as international versions of the Moto G. Head over to the thread for details.
(Rom Thread as of 12-23-2013.)
Stock based ROMs - [JB 4.3]
List of Stock Firmwares by @Skrilax_CZ -
All the Stock unrooted firmwares are available over here. The process to flash this, has been linked in the Post 3.
INFUSION B2 Rom by @tillaz -
This is a modified stock based Rom. Please head over to the thread for more details. Or you could also visit Modaco Thread for Screenshots and more details.
(Rom Thread as of 12-23-2013)

KERNELS -
Given bellow is a list of kernels for Moto G. Please let me know if there's one I have missed.
AOSP Kernels -
Hybrid Kernel by @faux123 - [for JB 4.2]
Although based on Linux 3.4, this kernel incorporates some of the advanced features of Linux 3.8+. Head over to the thread for more details.
[ANYKERNEL] pink Kernel by @pinkflozd
This kernel offers a host of features. It does support ExFAT and NTFS. It is based on Linux 3.4.x. It is not Compatible with Stock Rom. Head over to the thread for more details.
Furnace Kernel by @Savoca
This Kernel offers a host of features and includes good collection of Governers and Schedulers. It is based on Linux 3.4.x. It is not Compatible with Stock Rom. Head over to the thread for more details.

Baseband/Modems -
We have a list of possible Modems / Basebands for the Moto G. Please see the thread by @lost101 for details. The thread is Work in progress as of 04-16-2014.
Guides, Tutorials, How To -
Streamlined Rooting International Variants - [Kitkat 4.4.2] by @nupi
This thread has a nice Guide for Non-US versions the Moto G. by This only applies to those who have updated to Kitkat. See the thread for details.
How to Flash OTA Update to Non-US GSM Devices - by @darkeingel
For the Stock OTA updates that are being rolled out, here is a nice Guide by @darkeingel.
GUIDE : APK Parsing Errors -
When uninstalling an app, you got an error message "APK not found" or something to that effect, you may want to follow this Guide.
Mods and Apps -
Calendar Mod - by @Shaftenberg
This mod lets you see Text view in the Calendar when looking at Month as a whole. Head over to the thread for more details.
Status Bar Mod - Remove Carrier Label - by @Shaftenberg
This mod helps you to remove the Carrier's name from the phone's status bar. See the thread for details.
Volume Button Mod - by @Shaftenberg
This mod allows you to long press volume button to skip to the next Track or to the previous track. See the thread for details.
[Xposed] Framework Mods for Moto G -
Xposed Framework is a new framework introduced to the AOSP world. It helps access and modify system settings on the fly that would have otherwise taken a lot of steps.
MotoGuide collection of Tweaks -
@Kameo has created MotoGuide, a collection of assorted appearance tweaks to modify Status bar and other changes. Please see the thread for more details.
Wakeup on Volume Up -
@dubidu has written a module to the framework that allows you to wake the phone by pressing the Volume Up button. See the thread for details. You do need the Framework installed as basic requirement. You may wish to also visit a list of all Xposed modules written. Note, not all of them will work with Moto G.
Modified Phone Apk displaying Caller photo - by @shaftenberg
This mod shows the full picture of the caller from your contacts instead of being cut off at top. See the thread for the screeshot and details.
Customizations - Themes, Bootanimations, Media -
Boot Animation - by@Cooptx
There's a great bootanimation created from one of the Moto G animation video files. Please see the thread for details.
Font Pack for Motorola G- by @gianton
We have universal Font Packs that are compatible with Moto G. These can be flashed from Custom Recovery. Please see the thread for details.

Specific to International Variants -

Thanks for this!
Enviado de meu XT1033 usando Tapatalk

leonardoroza said:
Thanks for this!
Click to expand...
Click to collapse
I am still building this. Presently working on my Moto X thread.

Update this with a new faux Kernel

This summary is very helpful thank you.
Sent from my XT1034 using XDA Premium 4 mobile app

root problem
Hello!
I have a Moto G with android 4.3, and I want to root, but I can't.
Can you help me please?
I installed the moto driver, the java jdk, and I not find the android jdk.
What I find 480 Mb and there is no install file. /on windows 7 X84/ :silly: :crying:

It would be great if you could add a link to the stock ROM images

robagp said:
Hello!
I have a Moto G with android 4.3, and I want to root, but I can't.
Can you help me please?
I installed the moto driver, the java jdk, and I not find the android jdk.
What I find 480 Mb and there is no install file. /on windows 7 X84/ :silly: :crying:
Click to expand...
Click to collapse
Please follow this thread.
Cooptx said:
It would be great if you could add a link to the stock ROM images
Click to expand...
Click to collapse
I intend to. I am working on building up. Its a work in progress.

Hello!
I have a new problem /the jdk is ok now/
I want to open the bootloader, and they write me the email is sent, but nothing. I not get email, not in spam too.
I used my gmail email, when I login the motorola site.
I made again, but same, no email.

robagp said:
Hello!
I have a new problem /the jdk is ok now/
I want to open the bootloader, and they write me the email is sent, but nothing. I not get email, not in spam too.
I used my gmail email, when I login the motorola site.
I made again, but same, no email.
Click to expand...
Click to collapse
It may take a day or so. Please wait 24 to 48 hours.

Hello!
I have again a problem.
I unlocked the bootloader, when it start shows the screen.
I want to root but nothing.
I downloaded the Superboot, and I do this:
OSs-MacBook-Pro:r2sr maverick$ chmod +x superboot-mac.sh
OSs-MacBook-Pro:r2sr maverick$ sudo ./superboot-mac.sh
Password:
downloading 'boot.img'...
OKAY [ 0.356s]
booting...
OKAY [ 0.251s]
finished. total time: 0.607s
OSs-MacBook-Pro:r2sr maverick$
But when restart nothing. I downloaded googleplay store the superSU , but it shows:
There is no SU binary installed, and SuperSU cannot install it.
:crying:
I do it with windows but not rooted too...

robagp said:
Hello!
I have again a problem.
I unlocked the bootloader, when it start shows the screen.
I want to root but nothing.
I downloaded the Superboot, and I do this:
OSs-MacBook-Pro:r2sr maverick$ chmod +x superboot-mac.sh
OSs-MacBook-Pro:r2sr maverick$ sudo ./superboot-mac.sh
Password:
downloading 'boot.img'...
OKAY [ 0.356s]
booting...
OKAY [ 0.251s]
finished. total time: 0.607s
OSs-MacBook-Pro:r2sr maverick$
But when restart nothing. I downloaded googleplay store the superSU , but it shows:
There is no SU binary installed, and SuperSU cannot install it.
:crying:
I do it with windows but not rooted too...
Click to expand...
Click to collapse
Please note that this is a resource guide, not a Q&A thread. I have written a guide that I think may help you. http://forum.xda-developers.com/showthread.php?t=2585755

Disregard, already corrected.
AFAIK touchless control and active notifications are for the X only, please correct the first post(or me if I'm wrong)
Sent from my phone

miklosbard said:
AFAIK touchless control and active notifications are for the X only, please correct the first post(or me if I'm wrong)
Sent from my phone
Click to expand...
Click to collapse
You are correct.
Edit: Moto Maker is also not available for the Moto G
More OP edits
CM9 - Cyanogenmod 9. A modified version of ICS. (see CynogenMod)
CM10 - Cyanogenmod 10. A modified version of ICS. (see CynogenMod)
Should be JB
CM11 - Cyanogenmod 11. A modified version of ICS. (see CynogenMod)
Should be KK
Not that it matters right now, because we don't have any CM
Also, CyanogenMod is spelt wrong at the end. And I am pretty sure that you can remove all preJB words
INFUSION B2 Rom by @tillaz -
This is a JB ROM
And there is no need to label JB as 4.1, 4.2 and 4.3 because we only have 4.3
Also, you should add the two root methods for KK
http://forum.xda-developers.com/showthread.php?t=2583652
http://forum.xda-developers.com/showthread.php?t=2585755

In OP special features have listed Active noti and Touchless controls ....
both are not features of G(they are of moto x)

Cooptx said:
You are correct.
Edit: Moto Maker is also not available for the Moto G
More OP edits
CM9 - Cyanogenmod 9. A modified version of ICS. (see CynogenMod)
CM10 - Cyanogenmod 10. A modified version of ICS. (see CynogenMod)
Should be JB
CM11 - Cyanogenmod 11. A modified version of ICS. (see CynogenMod)
Should be KK
Not that it matters right now, because we don't have any CM
Also, CyanogenMod is spelt wrong at the end. And I am pretty sure that you can remove all preJB words
INFUSION B2 Rom by @tillaz -
This is a JB ROM
And there is no need to label JB as 4.1, 4.2 and 4.3 because we only have 4.3
Also, you should add the two root methods for KK
http://forum.xda-developers.com/showthread.php?t=2583652
http://forum.xda-developers.com/showthread.php?t=2585755
Click to expand...
Click to collapse
Thanks for mentioning. I have made rest of the changes except for the 2 Root methods. Will add them to the Op. All changes are done.
Between the two methods you have mentioned, the basic premise of bootloader downgrade is pretty much the same right ? Your's seems more elaborate list of steps. Or am I missing something ?
Ankush menat said:
In OP special features have listed Active noti and Touchless controls ....
both are not features of G(they are of moto x)
Click to expand...
Click to collapse
Thanks for mentioning. This has been corrected.

[TOOL] PRFCreator - easily create pre-rooted firmwares

Introducing my new tool called PRFCreator. With this tool, anyone can easily create a pre-rooted firmware.
What is a pre-rooted firmware
A pre-rooted firmware is a firmware, which already includes root. This is for example important if you want to update the firmware to a version, where there is no public root exploit. To flash a pre-rooted firmware, you need a recovery menu. An unlocked bootloader is not required.
How does the tool work
The tool should be self-explanatory. SuperSU zip can be downloaded from here. [NUT]'s dualrecovery (*.flashable.zip) can be downloaded from here. Recovery is optional and if your device is not supported by dualrecovery, you can use any recovery (just has to be a flashable zip).
Depending on the firmware size and your computer speed, generating a pre-rooted firmware can take up to 7 minutes. The pre-rooted firmware will be created in the directory of the executable and called flashable-prerooted.zip.
{
"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"
}
The order for the extra files is
Extra flashable
In the order you added it initially in the GUI
APKs
TWRP is recommended for flashing!
Note: If you do not include the kernel in the pre-rooted firmware, it's recommended to flash it afterwards with flashtool (check "system" under Exclude).
Note2: I am not responsible for any damage done to your device or if you end in a bootloop.
Credits
Androxyde - some helpful information about sin files from his flashtool
[NUT] - used his flashable scripts as base
E:V:A - sgdisk utility compiled for arm
dotnetzip developers (note I'm using a slightly modifed version with a bugfix)
Requirements
Microsoft .NET 4.0
Source code
https://github.com/dosomder/PRFCreator
Changelog
v1.3
Fix a signing bug when PRFCreator was in a folder which included a space (thanks Calystos)
Allow multi select for Extra Zip / APK
Update sinflash to v0.42 (fix sha256 bug (thanks RoberM) and large zip file handling (thanks Fragmentation))
v1.2
Fix a signing bug (thanks RyTekk)
Fix bug when flashing multiple apps
Update lz4 lib and 7zip binaries (thanks tetsuo55) and dotnetzip library
Update sinflash binary to v0.4 (supports now also non-msm devices, thanks eoinkennedy for report)
.
v1.1
Allow users to add APKs
Improved sinflash to allow compression
Fix smaller bugs and improve speed
.
v1.0
New method using sinflash (sin files are flashed on the phone directly instead of extracting on the computer)
New busybox
.
v0.9
Compatible with mono
New settings file to change temp folder and choose another destination for the pre rooted firmware
Work towards new sin format introduced with Z3+
.
v0.8
Add the ability to include additional flashable zip files
Display information when clicking on version number
.
v0.7
Add zip signing option
Small fixes in code
.
v0.6 - Nuked (wrong binary uploaded)
Prefer to use gpt uuid instead of partition names
Add different modem sin names
Clean code
.
v0.5
Fixed bug with missing dualrecovery
Added check if SuperSU and recovery are flashable
Added ability to flash modem
Support for sin v2
.
v0.4
Make dualrecovery zip optional
Fix exception if file does not exist in sin
.
v0.3
Initial release

I have a question!
What should I check under 'Include' ?
Kernel: Personally I recommend to check kernel. For some firmwares it's important otherwise the phone won't boot.
FOTAKernel: This kernel is used for OTA Updates. I recommend to include it.
Modem: This is the baseband / modem. Some updates can give you slightly better battery life and signal.
LTALabel: This is a partition with regulatory informations. It should not really change the performance of your device. I recommend to include it.
Click to expand...
Click to collapse
.
Do I need to include a recovery?
No, recovery is optional. If you do not wish to include recovery you should add this flashable zip under Extra Files to be able to mount system as rw: https://github.com/dosomder/SonyRICDefeat/blob/master/RICDefeat.zip
Note: If your bootloader is unlocked, this is not needed as RIC will be disabled anyway.
Click to expand...
Click to collapse
.
Can I edit system.ext4 inside flashable zip?
Yes, you can edit it on a linux machine. You don't have to change anything else in the flashable zip. See here for more info: http://forum.xda-developers.com/showpost.php?p=55547862&postcount=246
Click to expand...
Click to collapse
.
What is zip signing?
For a proper flashable zip, zip signing is used. It generates a hashtable of all the files in the flashable zip to verify its integrity. Note that zip signing might double the process time of generating a flashable zip.
Click to expand...
Click to collapse
.
Does it wipe my user data?
No.
Click to expand...
Click to collapse
.
What is extra zip?
With this feature, you can include additional flashable zip files. An example is to include Xposed directly (you can find the flashable zip in the Xposed apk).
Click to expand...
Click to collapse

Good news... Will try later...

This is awesome tool...
Still couldn't find free time to test it but if it's working and I'm sure it is...
This is more then welcome...
Tnx mate...
Sent from my D6503 using Tapatalk

Will try this on the next FW release, thanks! :good:

Thanks for the tool. Looks great. I'll try it.

Hi,
Thank you.. Looks really good! What do the Kernel, FOTAKernel and LTALabel checkboxes do? Also, will this work with the latest .133 ftf?
Regards,
Alan

nalab1 said:
Hi,
Thank you.. Looks really good! What do the Kernel, FOTAKernel and LTALabel checkboxes do? Also, will this work with the latest .133 ftf?
Regards,
Alan
Click to expand...
Click to collapse
It will include those in the flashable zip. FOTAKernel and LTALabel are not really important but I thought why not include this feature. Kernel is more important and I recommend to always use the kernel from the firmware you're using.
It should work with all the current ftfs (the tool is built for sin version 3).

zxz0O0 said:
It will include those in the flashable zip. FOTAKernel and LTALabel are not really important but I thought why not include this feature. Kernel is more important and I recommend to always use the kernel from the firmware you're using.
It should work with all the current ftfs (the tool is built for sin version 3).
Click to expand...
Click to collapse
Thanks for the reply... What is sin version 3? Also, what are your recommended settings? Tick all boxes or just the Kernel box? What devices/ROMs has it been tested on? Sorry for all of the questions! :laugh:

i just used the xperifirm tool to get the latest z2 .323 update, then used flashtool to create .tft, then your prfcreator tool to make the flashable zip. everything worked perfectly fine (many thanks to the dev's for all this nice and easy to use tools btw), this .zip rom should now be flashable from twrp (i got a locked and unlockable BL) no matter what i have installed on the phone right?
Thanks for your help, i'm new to sony devices and my z2 is only 20 days old, i'm trying hard not to brick it

Wow! Is this magic?
Xperia™ Z (C6602) with Tapatalk!

There was a dev who would create pre-rooted images you could flash on Galaxy S3 phones... that was something very cool!
So, I should be able to flash the zip this creates and have a "pre-rooted" phone image...
I'd half thought you were creating a root-injected FTF file... but this is actually pretty cool as well... (saves the pain that I normally go through to root the image after flashing it... thankful I have an unlocked boot loader...)

nalab1 said:
Thanks for the reply... What is sin version 3? Also, what are your recommended settings? Tick all boxes or just the Kernel box? What devices/ROMs has it been tested on? Sorry for all of the questions! :laugh:
Click to expand...
Click to collapse
The first byte of a sin file (contents of ftf file, the ftf is just a zip) is the version. Currently Sony uses version 3. Well if I would create a pre-rooted zip for myself I would tick all the boxes. I have tested the tool a handful of times on my Z1C.
ptmaniac said:
i just used the xperifirm tool to get the latest z2 .323 update, then used flashtool to create .tft, then your prfcreator tool to make the flashable zip. everything worked perfectly fine (many thanks to the dev's for all this nice and easy to use tools btw), this .zip rom should now be flashable from twrp (i got a locked and unlockable BL) no matter what i have installed on the phone right?
Thanks for your help, i'm new to sony devices and my z2 is only 20 days old, i'm trying hard not to brick it
Click to expand...
Click to collapse
Good to hear. And yes, that is correct. I still recommend to take a backup in TWRP before flashing it (just to be on the safe side).
scifan said:
There was a dev who would create pre-rooted images you could flash on Galaxy S3 phones... that was something very cool!
So, I should be able to flash the zip this creates and have a "pre-rooted" phone image...
I'd half thought you were creating a root-injected FTF file... but this is actually pretty cool as well... (saves the pain that I normally go through to root the image after flashing it... thankful I have an unlocked boot loader...)
Click to expand...
Click to collapse
It's actually not possible to create modified FTF as Sony uses RSA2048 signatures. And yeah, the tool is mainly aimed for those on locked bootloader

NICE! I was just waiting for a root method for my Xperia M2 with KitKat.. The only problem is that there's no Dual-Recovery for it... Would be possible to try the T2U Dual-recovery on my M2?

Very clever, thanks!

Make for samsung please...

linuxct said:
NICE! I was just waiting for a root method for my Xperia M2 with KitKat.. The only problem is that there's no Dual-Recovery for it... Would be possible to try the T2U Dual-recovery on my M2?
Click to expand...
Click to collapse
+1

after finish, app create zip and 2yn file. is it safe to delete 2yn file?

najar360 said:
after finish, app create zip and 2yn file. is it safe to delete 2yn file?
Click to expand...
Click to collapse
What is the filename of the second file? Are you sure it's created by PRFCreator?

Hi @zxz0O0
Thanks for your reply! This is definitely for locked bootloaders - correct?
Regards,
Alan

MiPatcher: A MIUI forking utility

No more free rides

Donor is Port Rom?

Black_Eyes said:
Donor is Port Rom?
Click to expand...
Click to collapse
Yes

Tqr said:
{
"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
Runs on Windows & Linux with WINE
MiPatcher is designed to append MIUI to any CM base that shares the same 'Build.id'. This can be found in build.prop.
At the same time this will also serve as a technical guide for folks just starting out with porting MIUI in the 4.4 era, those doing this by hand or others who are just returning to the game.
MiPatcher is not a substitute for PatchROM and is not the same in function by any means although it can use Patch components on the most basic level.
This is geared more toward people who are trying to build a functional MIUI for neglected devices and also for people testing various bases who may not yet be configured to build from source to accommodate some of MIUIs functionality.
MiPatcher is as of right now very straight-forward; you pick the resolution for the device you are porting for and it will adjust the Donor MIUI to 'look right' on your device.
Requirements
- Autohotkey (Only if you intend to run the source for this)
- CyanogenMod 11
*Disabled SELinux
*Boot.img edits (for full functionality if not using PatchROM)
*Modified seapp_contexts (At Kernel level for use with PatchROM, at source level for manual porting/using this tool)
**Stock CM with init.d support may also be used; although it will be sloppy.
- MIUI donor firmware with the same 'Build.id' found in /system/build.prop
- PatchROM resources (If your Donor is a different resolution, you do not 'need' them unless things look terrible)
*Or get PatchROM resources here if you intend to grab for every resolution; it's half the size of the one on Github better compression
- WinRAR or 7zip
Features
- Automatically append MIUI to any same code-base firmware.
- Append init.d on supported devices to force boot without changes to the kernel
Prep-work
Only three files must be edited for test-ports, which I'll cover now.
Framework-res.apk
Open your Base and donor Framework-res.apk, navigate to res/xml and import the following XMLs:
Code:
Storage List
Power Profile
Build.prop
Code:
ro.build.version.incremental=x.xx.xx
persist.sys.root_access=0
ro.config.notification_sound=xxx.ogg
ro.config.alarm_alert=xxx.ogg
ro.config.ringtone=xxx.ogg
ro.skia.use_data_fonts=1
ro.miui.ui.version.code=3
ro.miui.ui.version.name=V5
qemu.hw.mainkeys=0 **[U] If you have no physical HW keys.[/U]
Updater-Script
Code:
set_perm(0, 0, 06755, "/system/xbin/lbesec"); ***If LBEsec exists in your donor
set_perm(0, 1000, 06750, "/system/xbin/shelld");
set_perm(0, 0, 06755, "/system/xbin/su");
With these most basic edits, MIUI will boot but with the need to install MIUI Lite to fix themes partially; as native ThemeManager, updater and backup will FC continuously.
Planning to use PatchROM? If you have an unlocked BL device or a device that will accept an unsigned kernel you can split your boot.img's ramdisk and add the following entries to 'seapp_contexts' immediately under user=shell, like this :
user=shell domain=shell type=shell_data_file
Code:
user=theme seinfo=platform domain=platform_app type=platform_app_data_file
user=backup seinfo=platform domain=platform_app type=platform_app_data_file
user=updater seinfo=platform domain=platform_app type=platform_app_data_file
And above anything else that may follow user=shell.
If you are not planning on using PatchROM, you will have to disable SELinux fully and edit your 'seapp_contexts' in source. In CyanogenMod11 source it is located in the following directory:
Code:
external/sepolicy/seapp_contexts
Now it's time to kill SELinux, navigate to your Kernels config folder in source; generally found at:
Code:
kernel/brand name/kernelname-common/arch/arm/configs
and find 'kernelname_defconfig' or 'kernelname_selinux_defconfig', change the following value to 'n':
Code:
CONFIG_SECURITY_SELINUX=[B]n[/B]
This will yield a functional CyanogenMod11 that can be used with PatchROM without issue, and can also be used to just fork firmware which is useful in the case of unified device builds, which Patch does not really like so much.
Now that you've built your base the following edits must be made to the kernel's Ramdisk:
Init.rc
Add this line at the very end of init.rc
Code:
import /init.miui.rc
init.miui.rc
Create this file in the root of your ramdisk and place the following inside:
Code:
#service for shelld
service shelld /system/xbin/shelld
class main
#service for su
service su_daemon /system/xbin/su --daemon
class main
oneshot
service lbesec /system/xbin/lbesec
class main
oneshot
init.superuser.rc
Code:
Delete this file
init.cm.rc
Add a '#' to the following line to disable the calling of init.superuser.rc
Code:
[B]#[/B]import /init.superuser.rc
Default.prop
Change the following values:
Code:
ro.adb.secure=[B]0[/B]
ro.secure=[B]0[/B]
ro.allow.mock.location=[B]1[/B]
Once these edits have been made your base can now be adapted to MIUI.
MiPatcher Instructions
1. Extract the contents of baserom.zip to 'base'
2. Extract the contents of miuidonor.zip to 'donor'
3. Inside of the PatchROM resources zip, extract 'HDPI' 'xHDPI' and 'xxHDPI' into the 'PatchROM' folder
4. Run MiPatcher, select your resolution and if you haven't made any kernel editing or done special source building, use soft-mods.
5. Zip the contents of 'Base' and flash it.
6. If this yields a non-booting build your codebase is too distant from your donor, find another same Build.ID release and try again if not proficient with ADB.
Current version:0.01
0.01: First release, Basic functionality and enough to produce one-shot ports when the base is properly prepared.
0.01: x64 x86 stand-alone .exe
Next Version:0.02
0.02: Clean up redundant/inefficient code.
0.02: Add options for boot.img, build.prop, meta-inf backup and loading.
*to avoid having to edit or manually move these with each attempt on base.
Download
9/28/2014: MiPatcher x86&x64
This is stand-alone and requires nothing to run, PatchROM parts are optional but suggested nonetheless.
Source
To use this source as an executable 'program' you must download and install Autohotkey, after right-click on your desktop to create a new '.ahk' file, paste the contents of this inside of it and save.
Create the following folders in the same folder as your .ahk file, the folder structure should mimic the following in terms of layout with extracting things:
-base
*META-INF
*System
*Boot.img
-donor
*META-INF
*System
*Boot.img
-mod create two notepad++ files with no extension, name them the following and place the respective content inside:
*00lbesec
Code:
#!/system/bin/sh
/system/xbin/lbesec &
*00shelld
Code:
#!/system/bin/sh
/system/xbin/shelld &
-patchrom
*HDPI
*xHDPI
*xxHDPI
AHK source:
http://paste.ee/p/balNM
FAQ
Q: My ROM isn't booting!
A: Try another MIUI that uses the same Build ID as yours, or use ADB to debug your build as it will be really close either way.
Q: Is there any difference between using a .ahk file and a .exe?
A: Yes. It's easier to update by pasting new code into a .ahk text file than to download packed .exe files in the longrun; however when using a .exe you don't need to install Autohotkey.
I will make standalone .exe for this at some point soon today.
Q: Theme/Updater/Backup is FCing!
A: It's a SELinux related error, sounds like you may be using PatchROM or a unified build; in this case build from source with the Seapp_context, and with SELinux turned off.
Q: Storage isn't mounting!/File Explorer is closing!
A: Import CyanogenMod11's 'StorageList' located in Framework-res.apk/res/xml into MIUI's along with the 'PowerProfile' to resolve unreadable storage
Q: [Insert name] App is crashing...
A: Debug using ADB or find another donor if you're feeling lazy, most of the time this yields perfect results but some things will maybe need a little polish depending on how far the codebase from the Donor and your Base firmware are.
Big TY to:
Code:
* Sijav
* Chevelle
* Yun
* All the Russian firmware developers, ahead of everyone else by a bit..
XDA:DevDB Information
MiPatcher: A MIUI forking utility, Tool/Utility for all devices (see above for details)
Contributors
Tqr
Version Information
Status: Testing
Stable Release Date: 2014-10-04
Beta Release Date: 2014-09-30
Created 2014-09-28
Last Updated 2014-09-28
Click to expand...
Click to collapse
What's the "MIUI donor firmware" ? Doest it work on Ubuntu with Wine ?

h2o64 said:
What's the "MIUI donor firmware" ? Doest it work on Ubuntu with Wine ?
Click to expand...
Click to collapse
Any MIUI firmware as long as it has the same build.id as your base
Edit: Yes this tool works in ubuntu with WINE, but only as a .exe, it can't run as a .ahk file I believe.. I mean I've never tried running raw .ahk files in Linux

Tqr said:
Any MIUI firmware as long as it has the same build.id as your base
Edit: Yes this tool works in ubuntu with WINE, but only as a .exe, it can't run as a .ahk file I believe.. I mean I've never tried running raw .ahk files in Linux
Click to expand...
Click to collapse
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?

h2o64 said:
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
Click to expand...
Click to collapse
Sure, I don't mind Q&A

h2o64 said:
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
Click to expand...
Click to collapse
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64

Black_Eyes said:
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Click to expand...
Click to collapse
I'll try from one plus one (4.4.4)
If we need to wait. I prefer waiting for Redmi 1S which have a configuration very near to Moto G's one.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
Tqr said:
Sure, I don't mind Q&A
Click to expand...
Click to collapse
Works perfectly fine on Ubuntu 14.04 64 bits (I've used x64 one).
I'll flash the zip file. Keep you updated.

Black_Eyes said:
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Click to expand...
Click to collapse
I just made a post for the Moto X, sorry about that lol

Tqr said:
I just made a post for the Moto X, sorry about that lol
Click to expand...
Click to collapse
Which base did You use?
Help us to Boot it on Moto g

Black_Eyes said:
Which base did You use?
Help us to Boot it on Moto g
Click to expand...
Click to collapse
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it

Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Click to expand...
Click to collapse
Ok Thanks i will be waiting
---------- Post added at 08:06 PM ---------- Previous post was at 08:02 PM ----------
Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Click to expand...
Click to collapse
That will be Great :good:

Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Click to expand...
Click to collapse
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?

h2o64 said:
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
Click to expand...
Click to collapse
He will Build for Us

Black_Eyes said:
He will Build for Us
Click to expand...
Click to collapse
I'm a dev. I want to try it myself and to learn how to do.
I've work a lot on it :'( :'( :'(

h2o64 said:
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
Click to expand...
Click to collapse
When using PatchROM you can leave SELinux intact, when porting manually/using this tool you must fully disable SELinux or use a base that does not have it to begin with.
You don't even need to touch PatchROM to use this, or Linux honestly.. even the PatchROM Resources aren't required unless you're coming from a device with a different resolution sometimes.. but not always
Edit: Otherwise make the following edits I've outlined to CyanogenMod in source, I feel I was pretty clear on what to change

Tqr said:
When using PatchROM you can leave SELinux intact, when porting manually/using this tool you must fully disable SELinux or use a base that does not have it to begin with.
You don't even need to touch PatchROM to use this, or Linux honestly.. even the PatchROM Resources aren't required unless you're coming from a device with a different resolution sometimes.. but not always
Edit: Otherwise make the following edits I've outlined to CyanogenMod in source, I feel I was pretty clear on what to change
Click to expand...
Click to collapse
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?

h2o64 said:
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
Click to expand...
Click to collapse
@h2o64 Yes
and i think that's why Rom doesn't boot with manually Porting
---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------
How can i disable SELinux without Building the Kernel ?

h2o64 said:
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
Click to expand...
Click to collapse
No; you will still have Fingerprint errors

[HACK+MOD] Sony Xperia XZ Premium TWRP + KERNEL + ROOT + DRM fix/restore

{
"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"
}
A MESSAGE TO SONY:
Dear Sony,
It was never my intention to publish a hack for your devices. But... It also was never my intention to buy a device for which I have no control. I find it impertinent to forbid the customer to root a purchased smartphone. I would not have made the effort, if at least the standard functions of the camera could have used. I paid ~750 euros and got a non-functioning camera because I want to have full control of my device. If at least the Camera2 API would have been opened, in order to be able to use other camera apps with full resolution, a hack would not have been necessary. But even with that you are fooling your customers. The only reason I have spent so much time and nerves is that I wanted to have a functioning debloated device with root.
Okay, let's go...
First we need some good music: HERE
##### WARNING: ########
Please note that the modification can result in a loss of warranty. I accept no responsibility for any damage that may occur and do not guarantee the functionality of the modifications. I have created this modification for myself and I just want to make it available to other users. If you have no idea of these things, please keep your fingers away. This hack may - in case of incorrect application - destroy your phone. Please keep to the instructions and report errors right here in the thread.
##### INFO: ###########
I' m providing a complete guide here, explaining how to unlock and root the Sony Xperia XZ Premium. In addition, I offer my hack for the DRM problem. You can root your device and still use the full functionality of the camera. Please note: DON'T flash the fix of other devices/versions to your phone! There are patched system files in my fix, which are only for the related phone/version! I will create different patches for other devices and firmware versions in the future!
Sony has worked on the newer devices on the security functions and made it more difficult to crack the DRM protection. Hidden checks were implemented to make cracking more difficult. The old DRMfix by Tobias Waldvogel no longer works with newer devices. I therefore spent a lot of time (a few weeks) and cracked the protection. Since this was my first time with Sony and I had previously no experience with it, it was a very hard job for me. But okay... finally I did it. And here are my 5 cents...
##### INSTRUCTIONS: #####
Before you start: PLEASE CHECK THE RIGHT VERSION OF YOUR FIRMWARE!!!
Settings -> About the phone -> Model & Build number
Don't flash anything that doesn't match your build!
+++++++++ UPDATE +++++++++++++++++++++++++++
I created a tool "XperiFIX" which can do the magic for you.
See it in action...
If you nevertheless want to do it manually on Nougat, the old instructions and downloads are here: https://forum.xda-developers.com/showpost.php?p=74426201&postcount=285
1. Unlock your bootloader
Visit: https://developer.sonymobile.com/unlockbootloader/ Choose "Xperia XZ" from the list of the devices (only if your device isn't listed) and follow the instructions to unlock your bootloader. Please note, that as soon as you unlock your device, your unique device keys are lost (forever!) and there is NO way back anymore!
2. Use XperiFIX to get what you want
1. Download, install and start "XperiFIX" (as administrator!)
2. Hold down the VolumeUP(+) key only and plug the USB cable to PC and mobile phone until the LED is blue.
3. Read the warning and check the checkbox
4. Click "Fix my device!" button in XperiFIX
5. Now the tool will do it's magic! Please be patient, it can take a few minutes!
Note: If TWRP ask you if the system partition should be mounted read-only, then swipe to the right to allow modifications!
6. If all is done, the device should restart.
7. Check your security status, configuration and camera.
8. Donate me a pizza or some toys for my little son, hehe...
Congratulations!
You now have an unlocked, rooted XZ Premium with my DRMpatch and can use your camera and other functions again without ugly green pictures! Wohoooo... Easy going, huh?
Let's be quiet for a moment and imagine the faces of the developers, who wanted to prevent a DRMfix with the new firmware versions and complex encapsulated security functions:
Cheers!
//sToRm (Heiko Frenzel)
##### FAQ: ################
Can this patch bring back the device key?
No! It simulates the key and a locked device without root. If you unlock and root your device, the unique device key is gone forever! There is not turning back!
Can I use another kernel with this patch?
Yes, but only with Xperifix 2.0 and above. It will patch the ramdisk of the kernel automaticly.
Can I use the patch for other devices or versions?
No! Please don't try this! In my patch I had to fix a system file which is different between the devices and versions. If you flash the wrong version, it could brick your phone! I will create other versions of my patch for other devices, too. So be patient!
TWRP freezes and nothing happens, what should I do?
Please check if you have the correct driver for your device, installed on your PC.
I already rooted my device. Can I use XperiFIX, too?
Yes. If you used Magisk before, you can use XperiFIX without problems. Because XperiFIX will flash a new kernel which isn't pre-rooted. After that XperiFIX will flash Magisk, which will recognize your last Magisk installation. It will patch the new kernel ramdisk and all is fine. Your Magisk old settings will be there, too. If you want to use SuperSU, you can't use XperiFIX, because it's not implemented yet and I personally won't install and test it cause Magisk is running perfect on Nougat and Oreo, too!
I used XperiFIX but it gives me an error and now my device is in a bootloop!
That's not good dude. Please report what exactly you did, with all informations about your device. I will check it. To get a working device again, you can flash the firmware with Newflasher 10+.
My device doesn't respond, nothing works, it stucks in a bootloop, I can't power off?!
Just hold the VolumeUP(+) key together with the Power key. Wait until the device vibrates 3 times (!). Now it's completely off. Then you can try to go in Fastboot mode again to flash or use XperiFIX.
I have a problem, what can I do?
If your question can't be answered here in the FAQ, please post your report. Be sure to give all needed informations. Which device, which firmware version, what you exactly did, ... Without details, nobody can help you!
What does the fox say?
Hatee-hatee-hatee-ho! ^^
##### DOWNLOADS: ##########
XperiFIX_Installer MOD edit, links removed.
Official website: https://www.xperifix.com
Supported devices:
Sony Xperia XZ Premium (Single/Dual)
- Firmware @47.1.A.12.75
- Firmware @47.1.A.12.34
- Firmware @47.1.A.8.49
Sony Xperia XZ1 (experimental)
- Firmware @47.1.A.12.75
- Firmware @47.1.A.12.34
- Firmware @47.1.A.8.49
Sony Xperia XZ1 Compact (experimental)
- Firmware @47.1.A.12.75
- Firmware @47.1.A.12.34
- Firmware @47.1.A.8.49
Old version:
If you are using older firmware versions on your XZ Premium, you can download the last old version (v1.4) from the website (look at the history on the download site).
##### SUPPORT / DONATION: #####
If I could help you with my work, I would be glad if you give me a small thank you. You can DONATE HERE. This would also support further development for newer versions and other devices. Big thanks!
THANKS:
@munjeni
@zxz0O0
@the_brad
@serajr
... and all other users of the "brainstorm thread" for their infos and ideas!
CREDITS:
Included in XperiFIX:
Old DRM restore by @tobias.waldvogel
Magisk by @topjohnwu
TWRP by @Myself5
AndroidLib by @regaw_leinad

YES!
---------- Post added at 10:22 PM ---------- Previous post was at 10:06 PM ----------
Works just like you promised !

Priceless!!!
Congratulations sToRm//!!!

Thank you for your hard work, but it's only for G8141?

oneheart said:
Thank you for your hard work, but it's only for G8141?
Click to expand...
Click to collapse
Other versions will follow. I have a G8141 and the relevant files for this device. But I will download the other versions and release these versions also.

@sToRm//
Waiting a kernel and patch for my sony xperia xz1 dual
I will donate when patch is done
Thank you STORM for your time and work
Pls include my country lebanon in the donation country

Will be sources of the patch and kernel available so we can try to port to nonstock ROMs?
Thanks for all you hard work @sToRm//

@sToRm// For me SafetyNet didn't pass. I don't really care though but I wonder why.
Might be xposed's fault.

FartyParty said:
@sToRm// For me SafetyNet didn't pass. I don't really care though but I wonder why.
Might be xposed's fault.
Click to expand...
Click to collapse
Yes, it's because of Xposed.
@ ALL
G8142 (dual sim) added.
Please test ist and give feedback. I only have a G8141 here.

sToRm// said:
Yes, it's because of Xposed. .
Click to expand...
Click to collapse
Wouldn't it work if I used xposed magisk module then?
Nvm it says in the thread it doesn't pass.
Alright, no big deal for me.

So awesome! Thank you so much.

karrouma said:
@sToRm//
Waiting a kernel and patch for my sony xperia xz1 dual
I will donate when patch is done
Thank you STORM for your time and work
Pls include my country lebanon in the donation country
Click to expand...
Click to collapse
I need the right version of your kernel. Then I can download the FW and check it.
Lebanon? How can I do that? I have no idea... hahaha...

Freaking great work! Congrats on achieving this finally!
Some thoughts on your instructions: TWRP is officially supported for G8141, why not just use that?
If your patch contains patches system files wouldn't it make sense to create a simple magisk module, to keep it systemless?

thaks a lot 4 your work, how about oreo? here the kernel version is 4.4.78, will it work with your patch? Vielen Dank im Voraus )

ponytojas said:
Will be sources of the patch and kernel available so we can try to port to nonstock ROMs?
Thanks for all you hard work @sToRm//
Click to expand...
Click to collapse
If I have some free time, I will write a guide for this. It's a little bit tricky, because you have to understand the reversed code. But I try to create a universal patch.

Hello, just wanted to ask if ist just the stock firmware but with root or an acctual Rom, also: does this version have the Camera2Api and support its super-slow mo? Sorry if i missed something. Great Job by the way

sToRm// said:
If I have some free time, I will write a guide for this. It's a little bit tricky, because you have to understand the reversed code. But I try to create a universal patch.
Click to expand...
Click to collapse
That would be extremely awesome.
Really appreciate all your work, once I get next month salary, you will get enough for a pizza and a beer

stalkopat said:
Hello, just wanted to ask if ist just the stock firmware but with root or an acctual Rom, also: does this version have the Camera2Api and support its super-slow mo? Sorry if i missed something. Great Job by the way
Click to expand...
Click to collapse
It's just a modified kernel and a patch for a system file. The ROM is stock, the kernel is 99,9% stock. It has no effect to Camera2Api.

Hopefully modders like you will convince Sony and other OEMs to get their heads out of their arses and stop wasting time and money (both ours and theirs) with stupid $hit like these.

can you mod this kernel–G8142_45.0.A.7.90，Created byAndroPlus，Thank you！ download link
http://pan.baidu.com/s/1qYmLcO8 or https://drive.google.com/file/d/0B0j3VJ1Xp5N8Z0pxaW9ZZ0taaFE/view