DualBoot Patcher - Add Support
(Unofficial & Official)
Dualboot patcher is an open source project that makes an android phone compatible with multiple roms by patching them.That is we can install more than one rom on an android device at a time. But we cant use both at the same time,a restart is required to switch between roms. This awsome app is contributed to the android world by @chenxiaolong.
Pre Requirements :
Device must be rooted.
Custom recovery (twrp/cwm) should be installed.
Basic knowledge about rom flashing.
Patience
Active brain.
Can I use it on my x device right now ?
Check here the list of supported devices -Supported Devices
If your device is listed, its well and good download only the app from below links.
Downloads :
Download the app from
Mediafire
Or official server -
https://dbp.noobdev.io/downloads/
Code:
These are releases automatically built from the source by the continuous integration server.
Due to the constantly changing nature of the ROM development community, DualBootPatcher has many incremental releases as opposed to large, infrequent releases.
These releases contain the latest and greatest features, but may also have unforeseen bugs.
Be sure to make backup before installing and using these builds!
Terminal Emulator
Other Patches :
GET_PROP ; Mirror
PATCH_DATA ; Mirror
Your device is not in the list..?? Then you are at right place
NOTE: If you are new to dual boot patcher, and don't know to unbrick in case of soft/hard bricks, first take a full backup before doing anything.
Im not responsible for anything that happens to your device
Common Steps :
First download and install the app from any of the above links, open roms section.
Grant all the permissions including root permissions.
you need bellow properties (info) of your device
Code names of your device.
Archetecture.
All mount point and block device path details.
Mandatory (for boot ui) :-
Cpu temp path, brightness control path.
Flags for bootui
Grafics backends
For more info
To get these info,
Flash this from twrp and you will get most of the required details - GET_PROP
This works on all mtk 64bit devices,( should work on others also).
But details for boot ui may not be proper for all devices, you have to check it yourself.
After flashing this,
two files - info.txt and <brand_name>.yml are created in internal storage. You can edit them with any text editors if you find some details are Wrong or Missing !
Method 1: Patching data of DBP to work with your device
In this method, we required info.txt that is created on internal, make changes in it if required.
Make sure you have already downloaded, installed the app and opened roms section.
And also flashed GET_PROP.zip from link given above.
Then go to twrp and flash this script - PATCH_DATA
It will patch data of dbp app and makes it work with your device(it will takes the info from info.txt)
Now boot to system and open Terminal Emulator,
type :-
Code:
su
dbp.sh
Your device should support now.
For confirmation ->
it should ask to set kernel when you open roms section.
Set kernel, update-ramdisk in primary-rom's options, do not reboot.
Install boot ui in settings.
Now reboot to check whether boot ui is working or not.
A twrp like screen will appear during boot if its working.
If boot ui is not working, try to change graphics backends value in info.txt and reflash PATCH_DATA
No worries if boot ui is not working, you can still use the app to dual boot roms on your device
Click to expand...
Click to collapse
Method 2 : Add Official Support
In this method, you have to add the device definition to the SOURCE of DualBoot Patcher.
<brand_name>.yml created in internal can help us in doing this.
Do the required changes in it using any text editor.
(like adding some codenames used in custom roms, remove bootui part if it is not supported).
First LogIn to your github account or SignUp for free.
If ur using in mobile,Select desktop version at right bottom.
Fork DualBoot Patcher from SOURCE to your git account.
(fork option is at right top.)
Now head on to your git account, open DualBoot Patcher repo.
Check whether there is your <brand_name>.yml at /data/devices/<here>
If it is already there :- just copy all the contents of your yml file to that in git.
If the file does not exist, you have to do two things
Upload yml file to /data/devices/<here>
Edit /data/devices/CMakeLists.txt - add your <brand_name>.yml in the list
Now the source of Dual Boot Patcher that supports your device is ready in your git account.
Either you can compile the app by yourself :- Procedure ( need a lnux pc or linux server )
Or :-
Select New pull request(in your git account).
Select the same in next page also to confirm pull request.
You will have to wait for some time, and the admins will verfy your pull request,
If it is all proper, they will merge it to source.
The next release of the app will have official support to your device.
After getting support for your device, if you are strugling to use it,
Just google or youtube for dual boot patcher.
Its way of use are same on almost all devices.
Click to expand...
Click to collapse
Original thread by Chenxiaolong
https://forum.xda-developers.com/android/development/tutorial-dual-boot-roms-patcher-t3559254
Common Q &A :
This is too lengthy, it totally went over my head. Won't it be much simpler..??
1. Just download apps and patches from download section.
2. Install app, open roms section there.
3. Now reboot to twrp,
flash GET_PROP.zip and then flash PATCH_DATA.zip(should be in this order)
4. Reboot to system, open terminal emulator app and type :-
Code:
su
dbp.sh
5. Now DualBoot Patcher should work on your device
Click to expand...
Click to collapse
Something went wrong.I need help...
You are most welcome...
But please come up with info.txt, <brand>.yml and MultiBoot/devices.json
that are created in the storage(internal or external, & mention it)
Dont forget to have look into comment section befor reporting, it may solve your probleams sometimes.
Click to expand...
Click to collapse
Stuck at Roms section, what can be done.??
Probably it is not possible to make a full support for your device,
But still its possible to dual boot using this app,
But you need to try lot of workarounds by your own.
Click to expand...
Click to collapse
Not showning any device in patch roms section..!!
1. Find patched devices.json yourself,
2. Place it in internal storage.
3. Create it's symlink to /data/data/com.github.*/files/*/here.
(You can use Root Browser or romtoolbox)
Click to expand...
Click to collapse
Good @Uday Hegde.
It will help a lot of people.
kuberrocks96 said:
Good @Uday Hegde.
It will help a lot of people.
Click to expand...
Click to collapse
Thanks
flashing GET_PROP.zip and twrp says Failed to detect block devices aborting cant flash this zip
kutlay1653 said:
flashing GET_PROP.zip and twrp says Failed to detect block devices aborting cant flash this zip
Click to expand...
Click to collapse
Your device..??
Can u provide /etc/recovery.fstab from your recovery..??
Get_prop.zip have some limitations, ill try to fix them..
Uday Hegde said:
Your device..??
Can u provide /etc/recovery.fstab from your recovery..??
Get_prop.zip have some limitations, ill try to fix them..
Click to expand...
Click to collapse
Mt6592 General Mobile etab5 fstab in zip file
kutlay1653 said:
Mt6592 General Mobile etab5 fstab in zip file
Click to expand...
Click to collapse
Check with this...
Ill add it to the main thread if its working...
Uday Hegde said:
Check with this...
Ill add it to the main thread if its working...
Click to expand...
Click to collapse
it worked but when i try to patch a rom on dualbootpatcher it gives fc any idea?
Edit i forget update ramdisk but when i try update ramdisk app says cant update ?
kutlay1653 said:
it worked but when i try to patch a rom on dualbootpatcher it gives fc any idea?
Edit i forget update ramdisk but when i try update ramdisk app says cant update ?
Click to expand...
Click to collapse
Sorry, i hav no idea about that issue
You may try with older vesions...
Wait @kutlay1653 check this :-
Uday Hegde said:
Please check there is /sdcard/Android/devices.json file, manually copy it to /data/data/com.github.chenxiaolong.dualbootpatcher.snapshot/files/data-9.2.0.r199.gcfbba1c6/here
Click to expand...
Click to collapse
I have successfully edited the info.txt and *.yml files accordingly to my device but when I tried to patch it gives that "Could not determine the boot partition because this device's codename 'G42' is not recognized
Mohd.faraz.abc said:
I have successfully edited the info.txt and *.yml files accordingly to my device but when I tried to patch it gives that "Could not determine the boot partition because this device's codename 'G42' is not recognized
Click to expand...
Click to collapse
Please check there is /sdcard/Android/devices.json file, manually copy it to /data/data/com.github.chenxiaolong.dualbootpatcher.snapshot/files/data-9.2.0.r199.gcfbba1c6/here
Uday Hegde said:
Please check there is /sdcard/Android/devices.json file, manually copy it to /data/data/com.github.chenxiaolong.dualbootpatcher.snapshot/files/data-9.2.0.r199.gcfbba1c6/here
Click to expand...
Click to collapse
Tried and now same error and one more thing I think this is responsible for this. Please see attachment
Can't download patch_data.zip....
It says authorised download...
sagargjasani264 said:
Can't download patch_data.zip....
It says authorised download...
Click to expand...
Click to collapse
Mirror added in download section..
Mohd.faraz.abc said:
Tried and now same error and one more thing I think this is responsible for this. Please see attachment
Click to expand...
Click to collapse
Its an issue that dualboot patcher app can't read device.json file after modification, though i fixed correct uid,gid and permissions.
So i placed the file in internal and created a symlink to its data directory.this actually worked for me
Let me try some other workarounds and i will try to fix it..:good:
After flashing patch_dat.zip whenever i try to open ROMS options, it app force closes..
sagargjasani264 said:
After flashing patch_dat.zip whenever i try to open ROMS options, it app force closes..
Click to expand...
Click to collapse
This is the issue with latest app, that issue is even exist on supported device(coolpad note 3 lite)
Use older app, (u can use the one given in download section, mediafire link)
Stuck at this section
kutlay1653 said:
Stuck at this section
Click to expand...
Click to collapse
Ohh
Thats new issue that i saw..?
Related
Hello Fire owners!
I open this thread to keep all things of Fire together, only one thread, everything here.
So here we go:
THIS THREAD IS FOR MOTOROLA XT311/XT316/XT317, XT530/XT531, XT532 AND XT611 (aka SMARTFLIP) ONLY. IF YOU HAVE A SIMILAR THREAD, PLEASE PM ME AND PASS ME YOUR POST. LET'S KEEP XDA ORGANIZED!
CWM FOR FIRE XT XT530/XT532, SPICE XT XT531, FIRE XT311, SPICE KEY XT316 OFFICIALLY LAUNCHED
This thread was focused in the 2nd-Init for XT31X and XT530, 531 and 532. For almost six months, we worked patientlly to get the CWM working on our devices. The wait for CWM is OFFICIALLY OVER. In a couple days ago, our friend aweosomeabhijeet found a way to run CWM on Gingerbread. The tutorial (made by himself) will be posted NOW:
Hey Guys
All your wait is over.
Here I'll tell you how to get CWM for Moto Fire XT.
Disclaimer : I'm not responsible for any damage to your phone. I have tried it and finished successfully.
Try only if you know little bit about android.
This is beta version. However, a dev is working on not using a PC to reboot back into system, and is trying to make the installation simplified.
Lot of thanks to andrewidya
Required things
1. Rooted XT
2. Pc
Download these things on your phone:
1. Terminal emulator
2. Busybox(Open it and install)
3. Root browser
4. Pimp my Rom
5. ES file explorer
You can find all of them in the Play Store.
If you have done with it download the attachment.
Now main work.
It is not easy though but I think everyone can do it.
Steps:
1. Extract the attachment and copy it to your sdcard
2. Mount /system as RW.
3. Open Root Browser and copy bootmenu folder from sdcard/XT530 and paste it in /system.
4. Open Pimp My Rom and Add universal init.d support.
5.Create 97bootmenu manually.(For this using ES file explorer is recommended)
Steps:
a.Open /system/etc/init.d
b. Create a file, name it 97bootmenu.
c. Open the file as text
Type:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
d.save the file
6. Change permissions of 97bootmenu to rwx r-- r--
7. Reboot your phone.
Now your phone will start at bootmenu.
Select Recovery>Custom Recovery
PS: If you want to get back the phone to boot normally. Just connect it to PC, open CMD and type
cd path-to-adb.exe
adb shell
rm -R /system/etc/init.d/97bootmenu
exit
adb reboot
I succeeded here's the video:
http://youtu.be/OyHwMqkBArk
Sorry for poor camera quality.
Thanks to all the members.
Special Thanks to:
Gentrylamp for creating bootmenu.
7amdoun for his great knowledge and modding bootmenu for XT530.
andrewidya for correcting me at every point.
Mazen.kh for everything he did.
Mr.Indigo for giving us hopes.
And all other members whom I forgot to mention here.
Click to expand...
Click to collapse
This above quote is the 1ST post of his thread.
THANKS TO HIM AND TO ALL OF THE DEVELOPERS WHO HELPED TO GET THIS.
ROOTING & UNROOTING
You will follow this tutorial if you have 2.3.5 version of Android:
Downloads:
Here are the apps/files needed for Rooting -
1. SuperOneClick 2.3.3.0
2. SUT LR 1.8.2 (Doesn't seem to be working on 64-bit systems)
3. FXX_PR3_NV.xml and NvDefinition.xml [ATTACHED]
Before Rooting:
Prepare your phone by doing the following:
- Go to Settings > Applications > CHECK "Unknown Sources"
- Go to Settings > Applications > Developer > CHECK "USB Debugging" and "Stay Awake"
- Connect your phone via USB, when prompted DO NOT select USB Mass Storage.
- Extract FXX_PR3_NV.xml and NvDefinition.xml from the attached zip file in to a folder
- Now, install SUT LR, run the app
- Select the FXX_PR3_NV.xml [ensure NvDefinition.xml is also in the same folder as FXX_PR3_NV.xml]
- Your phone will restart.
It does NOT erase anything on the phone, since it only patches the ROM.
Rooting:
After the phone restarts, open SuperOneClick and select root. It will take less than a minute to finish.
Click to expand...
Click to collapse
From: Motorola Fire XT / XT-530 / XT-531 ROOTING! - NEW METHOD - [ DEVS NEEDED ] posted by the user jeet.9890427233
Official Motorola SBF Files
Link: www.grupoandroid.com/topic/43248-motorola-firmwares-superthread/
Just copy and paste.
Custom ROMs
None yet.
Custom Recovery
None Yet.
Custom Kernels
None yet.
Applications that you can removeThere are some apps that you can remove, here is the complete list with all apps:
My ROM is VIVO 2.3.5 and can be different in some ROMs.
7x27_FQC or FQC Program= YES, maybe is F actory Q uality C heck or other thing....
AccountAndSyncSettings.apk= NO
ApplicationsProvider.apk= NO - Will brick apps install/uninstall
APR.apk= ?
BatteryManagerAP.apk= YES
BatteryProtect.apk= ?
Bluetooth.apk= NO
BlueToothTestMode.apk= NO
Browser.apk= YES
Calculator.apk= YES
Calendar.apk= NO
CalendarProvider.apk= NO
Camera.apk= NO
CDA.apk= ?
CDASYSTEM.apk= ?
CertInstaller.apk= NO
Contacts.apk= NO
ContactsProvider.apk= NO
DataConnectionWidget= YES
DateTimeSetup.apk= NO
DbgCfgTool.apk= ?
DefaultContainerService.apk= ?
DeskClock.apk= YES/NO
DMClient.apk= NO
DownloadProvier.apk= NO
DownloadProviderUI.apk= NO
DrmProvider= NO
DxDrmApplication= NO
DxDrmPlugin= NO
ECompassCalibration= NO
Email= NO
Facebook_LT= YES
Fallback= NO
FileManager= YES
FM Radio= ?
Gallery3D= YES, but replace with another gallery app
GenieWidget= ?
- THIS LIST WILL BE UPDATED SOON -
Click to expand...
Click to collapse
If you are a DEV our a guy who can provide a ROM for us, please PM me and i will add you in GTalk. If you have a mod or something useful or want to help me, please PM me and i will add you on GTalk. If we get sucess this thread will be updated!
Thread changelog:
- Initial post
- CG2.smg extractor added to the 2nd Post (THANKS TO: Mazen.kh)
- Chainfire 3D support added ( THANKS TO: Overcrasher)
- Thread stopped a lil bit
- Back with some news
- SUPPORT FOR XT530/531/532 (FIRE XT) Added
- SUPPORT FOR XT317 (FIRE in Brazil) Added
- XT317 kernel tested, but didn't work smoothly as 2.2 kernel
- SUPPORT FOR XT611 (aka SMARTFLIP) added
- SUPPORT FOR XT611 DROPED. See more below.
- CWM FOR FIRE DEVICES LAUNCHED BY aweosomeabhijeet
about CG2.smg
Hey man I'm interested in the thread and i can help you extracting the CG2.smg
Here you are my tut. [for windows] it worked for me
1- unrar the file in the attachments
2- make sure that your file is named to 'CG2.smg' without quotes for sure, and in the same folder..
3- just run the .bat and wait for cmd to finish the job then you will find a folder called 'CG2-extracted' in the same place you extracted my .rar file
Note: you will find in the folder called 'CG2-extracted' some mbn files, systemsec.mbn is the /system folder in the xt311/xt316
extract it easily using unyaffs like a system.img file, if you need help in this PM me. i can help you extracting systemsec.mbn only, i dunno about other files also to repack systemsec.mbn you'll need mkyaffs and i think it's usable on ubuntu only and i can't help you with it
sorry for long reply but press thanks if i helped.
Mazen.kh said:
Hey man I'm interested in the thread and i can help you extracting the CG2.smg
Here you are my tut. [for windows] it worked for me
1- unrar the file in the attachments
2- make sure that your file is named to 'CG2.smg' without quotes for sure, and in the same folder..
3- just run the .bat and wait for cmd to finish the job then you will find a folder called 'CG2-extracted' in the same place you extracted my .rar file
Note: you will find in the folder called 'CG2-extracted' some mbn files, systemsec.mbn is the /system folder in the xt311/xt316
extract it easily using unyaffs like a system.img file, if you need help in this PM me. i can help you extracting systemsec.mbn only, i dunno about other files also to repack systemsec.mbn you'll need mkyaffs and i think it's usable on ubuntu only and i can't help you with it
sorry for long reply but press thanks if i helped.
Click to expand...
Click to collapse
IT WORKED!
Thanks!
It helps me a lot!
Now my device Works!
Thanks!
Sent from my Xt316
Is there any custom rom for XT316/XT311?
luume said:
Is there any custom rom for XT316/XT311?
Click to expand...
Click to collapse
Unfortunately not yet.. Neither custom recoveries
Mr.Indigo said:
IT WORKED!
Thanks!
Click to expand...
Click to collapse
Anytime Sir ! I just want to help in anyway getting this device better, By the way here's a list of useless applications so far !
- 7x27_FQC.apk
- Arabware.apk < 7 megabytes and useless
- Wifipowersavingmode.apk < I think it drains the battery faster -.-
- i also removed all motoswitch APKs, And installed go launcher instead in the system. And removed pre-installed live wallpapers
Also if you have errors like "preparing sd card - checking for errors" in the status bar you can delete system/bin/fsck_msdos since i deleted i get no errors for my partitioned sd card
Q/Request: Do you know how can i customize Notify led ? Like changing color and speed ? also it doesn't work with whatsapp!
Thanks anyway ! Ps. led works by Notifyled.apk.. of course you know xD
And Yeah, i found some srs files also, time ago, i thought it would be awesome to have a panel for it ! but maybe it's the normal speakers at the back and it's drivers..
Mazen.kh said:
Unfortunately not yet.. Neither custom recoveries
Anytime Sir ! I just want to help in anyway getting this device better, By the way here's a list of useless applications so far !
- 7x27_FQC.apk
- Arabware.apk < 7 megabytes and useless
- Wifipowersavingmode.apk < I think it drains the battery faster -.-
- i also removed all motoswitch APKs, And installed go launcher instead in the system. And removed pre-installed live wallpapers
Also if you have errors like "preparing sd card - checking for errors" in the status bar you can delete system/bin/fsck_msdos since i deleted i get no errors for my partitioned sd card
Q/Request: Do you know how can i customize Notify led ? Like changing color and speed ? also it doesn't work with whatsapp!
Thanks anyway ! Ps. led works by Notifyled.apk.. of course you know xD
And Yeah, i found some srs files also, time ago, i thought it would be awesome to have a panel for it ! but maybe it's the normal speakers at the back and it's drivers..
Click to expand...
Click to collapse
No, i don't know, srry!
And we cannot use the control panel with the file incluided in the ROM. Needs a lot of files...
And i'm trying to por XT300 Toggle Widget to XT316. It will be harder but... it's beautiful!
Mr.Indigo said:
No, i don't know, srry!
And we cannot use the control panel with the file incluided in the ROM. Needs a lot of files...
And i'm trying to por XT300 Toggle Widget to XT316. It will be harder but... it's beautiful!
Click to expand...
Click to collapse
It's weird how motorola build their phones and drivers, unlike samsung they give full customization !
And good luck man i wish i could help but i'm not really helpful in porting and modding
Mazen.kh said:
It's weird how motorola build their phones and drivers, unlike samsung they give full customization !
And good luck man i wish i could help but i'm not really helpful in porting and modding
Click to expand...
Click to collapse
Yeah, Motorola lock the bootloader, locks the customization and much more. We need a CWM. FASTER!
Edit: before 2.3 versions, Motorola odexed the roms. All of the files were odexed. But Motorola now deodexed everything. So it will be easier.
And i think we can port the CWM from XT300. So, let's try!
Mr.Indigo said:
Yeah, Motorola lock the bootloader, locks the customization and much more. We need a CWM. FASTER!
Edit: before 2.3 versions, Motorola odexed the roms. All of the files were odexed. But Motorola now deodexed everything. So it will be easier.
And i think we can port the CWM from XT300. So, let's try!
Click to expand...
Click to collapse
I didn't know that there was cwm for xt300, but i think, if there is cwm for xt530/xt531/xt532 it'd be easier to port, since xt53X is to close to our xt311/xt316 and it also have 2.3.5 while xt300 2.1 only
Edit: i think xt311/xt316 users will never have custom recoveries/roms unless the bootloader is unlocked, and it'll be so hard to unlock such bootloader since the phone is not popular
Mazen.kh said:
I didn't know that there was cwm for xt300, but i think, if there is cwm for xt530/xt531/xt532 it'd be easier to port, since xt53X is to close to our xt311/xt316 and it also have 2.3.5 while xt300 2.1 only
Edit: i think xt311/xt316 users will never have custom recoveries/roms unless the bootloader is unlocked, and it'll be so hard to unlock such bootloader since the phone is not popular
Click to expand...
Click to collapse
Some guys tried to do an 2ndInit to maybe try to get CWM work. But didn't worked. A file from the battery (when you turn off the phone and conntect the charger, the big battery icon) was missing. But works without this file.
AND I FOUND WHERE WE CAN ACTIVATE SRS! Is in cda.prop, it's configured to false.
So what happens if i changed the value to true ?
i don't think cda props apply actually i tried to change the value of lock screen support rotation to true and nothing changed.
And Yup i read something about that battery icon too but i didn't understand fully how does that relate to unlocking bootloader
i think the bootloader must get hacked easily since as i see it's a common bootloader in many fones for ex. xt530 xt531 xt532 xt300 xt311 xt316 xt317 or am i wrong ?
If i can test the ROM in my computer (i don't know how to do it), we see if works. And Bootloader it's not the same for every phone series. XT300 executes 2.1 WITH UNLOCKED BOOTLOADER. And XT316 with 2.3.5 WITH THE LOCKED Bootloader.
The SRS file is in the attachments. Just take a look on the 'st line:
BLOCK... I understand that is blocked.
And the battery icon maybe is on a apk or anywhere. We might look better.
EDIT:
I googled around and i found a thread that talks about CG2.smg. They tried to do the same what i doing, and didn't finish very well. The phone was bricked, but they use some files, replace and the ROM was going on very well.
Mr.Indigo said:
I googled around and i found a thread that talks about CG2.smg. They tried to do the same what i doing, and didn't finish very well. The phone was bricked, but they use some files, replace and the ROM was going on very well.
Click to expand...
Click to collapse
i actually didn't understand what you said in the "EDIT" but i read that even with a locked bootloader we can have a custom rom, but not a custom kernel right ?
so you can recompress the edited cg2.smg files and re sbf it again after customizing it or am i saying meaningless words ?
Mazen.kh said:
i actually didn't understand what you said in the "EDIT" but i read that even with a locked bootloader we can have a custom rom, but not a custom kernel right ?
so you can recompress the edited cg2.smg files and re sbf it again after customizing it or am i saying meaningless words ?
Click to expand...
Click to collapse
OK. I will explain the edit first.
They edit the systemsec.mbn, repack the mbn and repack everything. but they've got an error. Then, the phone was bricked and RSD doesn't saw the phone.
A custom kernel will be pretty great, but we have to unlock the bootloader 1st.
Mr.Indigo said:
OK. I will explain the edit first.
They edit the systemsec.mbn, repack the mbn and repack everything. but they've got an error. Then, the phone was bricked and RSD doesn't saw the phone.
A custom kernel will be pretty great, but we have to unlock the bootloader 1st.
Click to expand...
Click to collapse
so what kind of error did they get, cause i wanted to do the same as they and repack the rom as sbf and flash it..
also, can we try porting as .nb0 rom? i can see our stock recovery have the option to flash nb0 files
Mazen.kh said:
so what kind of error did they get, cause i wanted to do the same as they and repack the rom as sbf and flash it..
also, can we try porting as .nb0 rom? i can see our stock recovery have the option to flash nb0 files
Click to expand...
Click to collapse
Maybe... Here is the error they got:
I got this after the flash attempt.
Phone[0000]: Error flashing subscriber unit. Device API error. 0xE002000B Address 0x94C3800 Command: BIN (0xE032300B)
Click to expand...
Click to collapse
I've got from ModMyMobile (M3). They mod and bang! Bricked the device!
But they recovered.
See another error here
The recover is change the FLEX VERSION to please flash please (something like that)
Does this file mean anything ?
Code:
ro.product.model.num=2013
ro.product.name=XT316
ro.product.device=XT316
ro.product.model=XT316
ro.product.brand=Motorola
ro.product.board=XT316
ro.telephony.num.auto.hyphen=false
ro.telephony.gsm.spn.shortname=true
ro.telephony.gsm.wait.switch=true
ro.telephony.rat.network.select=true
ro.telephony.gsm.sms.auto-reg=false
ro.telephony.add.mccmnctable=true
ro.telephony.spn.support.mvno=false
ro.telephony.fdn.data=true
ro.telephony.configurable.mtu=false
ro.nitz.name.ignore.plmns=72405
ro.telephony.cphs-spn.support=true
ro.telephony.dun.show=true
ro.telephony.fast.dormancy=true
ro.tether.denied=false
ro.telephony.mvno.sim.spn=false
ro.telephony.croatia.shortcode=false
ro.CDG_MENU_EVDO_ONLY=false
ro.telephony.custom.showspn=false
ro.telephony.extended.mnc=false
ro.telephony.hidemenu.data=false
ro.telephony.gsm.ecclist=112,911,190
ro.telephony.ecclist=112,911,190
ro.telephony.cdma.ecclist=112,911,190
ro.telephony.gsm.voicemail=*555
ro.telephony.cdma.ecm=false
ro.contacts.number.match.length=11
ro.contacts.number.match.minima=7
ro.contacts.polyphonename=false
ro.sf.lcd_density=120
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.config.dbgcfgtool_config=3
ro.DRM_SOLUTION_ID=1
ro.SYSTEM_CTA_MODEL=false
ro.NETWORK_DISABLE_3G_MODULE=false
ro.USB_PLUG_IN_NOTIFICATION=true
ro.LOCKSCREEN_SUPPORT_ROTATION=false
ro.SETTINGS_ENABLE_MSISDN_ALPHA=true
ro.CC_SEC_INC_CALL_OPTIONS=false
ro.SETTINGS_LANG_HIDE_TW_CHINA=false
ro.CALENDAR_FESTIVALS_OPTION=false
ro.SETTINGS_LOCK_PRELOADED_APN=NONE
ro.PHONE_ENABLE_COUNTRY_CODE=false
ro.MEDIA_ENABLE_SRS=false
ro.FB_ENABLE_HIDE_FOLDER=false
ro.CONTACT_VCARD_VERSION=3.0
ro.NETWORK_SB_CUST_FD_MECH=false
ro.SETTINGS_LOCK_VOICEMAIL_NUM=false
ro.CC_QUERY_CF_ON_BOOT=false
ro.BROWSER_ENABLE_PROXY=false
ro.SETTINGS_REMOVE_SIGNAL_STR=false
ro.SYSTEM_GCF_MODEL=false
ro.CC_HIDE_CB_PW_CHANGE=false
ro.SYSTEM_UI_STYLE_ID=0
ro.SB_SHOW_PLMN=false
ro.SETTINGS_DISABLE_TOUCH_TONE=false
ro.NETWORK_ENABLE_HOTSPOT_SEC=false
ro.CC_ENABLE_MAKE_OOS_CALL=false
ro.NETWORK_NET_MODE_IND=false
ro.NETWORK_ENABLE_OP_LABEL=false
ro.NETWORK_HOTSPOT_AUTO_OFF=false
ro.NETWORK_OP_NAME_OPTION=0
ro.NETWORK_WIFI_SLEEP_POLICY=0
ro.NETWORK_SIGNAL_DISP_STYLE=0
ro.SYSTEM_LED_NOTIFY_STYLE=0
ro.SL_DISABLE_UNLOCK_PROMPT=false
ro.BT_ENABLE_FF_RW=false
ro.MUSIC_DEACTIVATED_BY_FW_BW=false
ro.RSS_DISABLE_COST_PROMPT=false
ro.SETTINGS_HIDE_WIFI_SCAN=false
ro.PHONE_ENABLE_REBOOT_FUNC=false
ro.SYSTEM_SIM_WATCHER=false
ro.CAMERA_DISABLE_H263_ENCODER=false
ro.SYSTEM_SPK_OFF_WHEN_HS_IN=false
ro.NETWORK_REMOVE_GSM_COMBO=false
ro.STANDMODE_ENABLE_TV=false
ro.IME_DISABLE_AUTO_PUNC=false
ro.IME_DISABLE_SHOW_SUGGESTION=false
ro.MEDIA_HIDE_3g2_FILE=false
ro.BROWSER_DL_POPUP_DIALOG=false
ro.CC_HIDE_SIP_UI=false
ro.SYSTEM_DISABLE_LOW_MM_CHECK=false
ro.SYSTEM_ENABLE_FLIP_FONT=false
ro.MUSIC_ENABLE_FORCE_TRNAS_RU=false
ro.DL_PROVIDER_CUSTOMIZED_FUNC=0
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.ms=android-hms-tef-{country}
ro.hwt.softbank=false
ro.cust.cover_shutdown=false
kent_lkc said:
Does this file mean anything ?
Code:
ro.product.model.num=2013
ro.product.name=XT316
ro.product.device=XT316
ro.product.model=XT316
ro.product.brand=Motorola
ro.product.board=XT316
ro.telephony.num.auto.hyphen=false
ro.telephony.gsm.spn.shortname=true
ro.telephony.gsm.wait.switch=true
ro.telephony.rat.network.select=true
ro.telephony.gsm.sms.auto-reg=false
ro.telephony.add.mccmnctable=true
ro.telephony.spn.support.mvno=false
ro.telephony.fdn.data=true
ro.telephony.configurable.mtu=false
ro.nitz.name.ignore.plmns=72405
ro.telephony.cphs-spn.support=true
ro.telephony.dun.show=true
ro.telephony.fast.dormancy=true
ro.tether.denied=false
ro.telephony.mvno.sim.spn=false
ro.telephony.croatia.shortcode=false
ro.CDG_MENU_EVDO_ONLY=false
ro.telephony.custom.showspn=false
ro.telephony.extended.mnc=false
ro.telephony.hidemenu.data=false
ro.telephony.gsm.ecclist=112,911,190
ro.telephony.ecclist=112,911,190
ro.telephony.cdma.ecclist=112,911,190
ro.telephony.gsm.voicemail=*555
ro.telephony.cdma.ecm=false
ro.contacts.number.match.length=11
ro.contacts.number.match.minima=7
ro.contacts.polyphonename=false
ro.sf.lcd_density=120
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.config.dbgcfgtool_config=3
ro.DRM_SOLUTION_ID=1
ro.SYSTEM_CTA_MODEL=false
ro.NETWORK_DISABLE_3G_MODULE=false
ro.USB_PLUG_IN_NOTIFICATION=true
ro.LOCKSCREEN_SUPPORT_ROTATION=false
ro.SETTINGS_ENABLE_MSISDN_ALPHA=true
ro.CC_SEC_INC_CALL_OPTIONS=false
ro.SETTINGS_LANG_HIDE_TW_CHINA=false
ro.CALENDAR_FESTIVALS_OPTION=false
ro.SETTINGS_LOCK_PRELOADED_APN=NONE
ro.PHONE_ENABLE_COUNTRY_CODE=false
ro.MEDIA_ENABLE_SRS=false
ro.FB_ENABLE_HIDE_FOLDER=false
ro.CONTACT_VCARD_VERSION=3.0
ro.NETWORK_SB_CUST_FD_MECH=false
ro.SETTINGS_LOCK_VOICEMAIL_NUM=false
ro.CC_QUERY_CF_ON_BOOT=false
ro.BROWSER_ENABLE_PROXY=false
ro.SETTINGS_REMOVE_SIGNAL_STR=false
ro.SYSTEM_GCF_MODEL=false
ro.CC_HIDE_CB_PW_CHANGE=false
ro.SYSTEM_UI_STYLE_ID=0
ro.SB_SHOW_PLMN=false
ro.SETTINGS_DISABLE_TOUCH_TONE=false
ro.NETWORK_ENABLE_HOTSPOT_SEC=false
ro.CC_ENABLE_MAKE_OOS_CALL=false
ro.NETWORK_NET_MODE_IND=false
ro.NETWORK_ENABLE_OP_LABEL=false
ro.NETWORK_HOTSPOT_AUTO_OFF=false
ro.NETWORK_OP_NAME_OPTION=0
ro.NETWORK_WIFI_SLEEP_POLICY=0
ro.NETWORK_SIGNAL_DISP_STYLE=0
ro.SYSTEM_LED_NOTIFY_STYLE=0
ro.SL_DISABLE_UNLOCK_PROMPT=false
ro.BT_ENABLE_FF_RW=false
ro.MUSIC_DEACTIVATED_BY_FW_BW=false
ro.RSS_DISABLE_COST_PROMPT=false
ro.SETTINGS_HIDE_WIFI_SCAN=false
ro.PHONE_ENABLE_REBOOT_FUNC=false
ro.SYSTEM_SIM_WATCHER=false
ro.CAMERA_DISABLE_H263_ENCODER=false
ro.SYSTEM_SPK_OFF_WHEN_HS_IN=false
ro.NETWORK_REMOVE_GSM_COMBO=false
ro.STANDMODE_ENABLE_TV=false
ro.IME_DISABLE_AUTO_PUNC=false
ro.IME_DISABLE_SHOW_SUGGESTION=false
ro.MEDIA_HIDE_3g2_FILE=false
ro.BROWSER_DL_POPUP_DIALOG=false
ro.CC_HIDE_SIP_UI=false
ro.SYSTEM_DISABLE_LOW_MM_CHECK=false
ro.SYSTEM_ENABLE_FLIP_FONT=false
ro.MUSIC_ENABLE_FORCE_TRNAS_RU=false
ro.DL_PROVIDER_CUSTOMIZED_FUNC=0
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.ms=android-hms-tef-{country}
ro.hwt.softbank=false
ro.cust.cover_shutdown=false
Click to expand...
Click to collapse
This is cda.prop right?
it has some tweaks like build.prop, if you tried to change the mobile model that appears to the market from build.prop it won't work, but if you change it from cda.prop it will work also it have some other tweaks that i actually don't know what's it's use
And Don't Forget Thanks Button ^^
XT316 bricked
Hello guys, sorry if this is not the best place to post a problem but, this is the only one active discussion about XT316 that i have found, i have this phone with Brazil Claro stock 2.3.3 Gingerbread Android installed, then i have installed the ChainFire3D hoping to have better experience with some games...
But i got a bricked phone... when powering on, the phone shows only the Motorola logo, then a black screen with no response, and continous reboot
I started the phone in recovery mode and tryed to perform a Factory Recover, but no sucess, same with Wipe Cache Partition option, so, what is left to do now is my question...
Multiboot for Sony Xperia Z1 Compact
How its look -> http://i58.tinypic.com/35346bt.png
How to install boot menu
download bootmenu_amami.rar, extract folder "bootmenu" to the your internal storage
put boot.img or kernel.elf to the mainrom folder, make sure thats the same kernel like your primary rom (aka main rom)
download bootmenu.img from attachment, flash bootmenu.img using fastboot commnd: fastboot flash boot bootmenu.img
Click to expand...
Click to collapse
Since your bootmenu folder no contain settings.ini (you runing bootmenu at a first time), settings.ini will be created easily. You need to complete main step aka main rom creation:
(mainrom creation)
reboot into bootmenu, chose "patch rom package", navigate to the bootmenu folder on your internal storage, navigate to the mainrom folder, select mainrom.zip package (make sure boot.img or kernel.elf is the same like your current main rom kernel, and make sure boot.img is in folder mainrom), select mainrom.zip and click "yes". Main rom will be added into boot menu entry. Now reboot again into boot menu and you will see new menuentry, chose these menu to boot into your primary rom!
(other roms creation - you can do only if you completed main rom step)
reboot into bootmenu, chose "patch rom package", principe is a bit diferent than main rom step (we have 3 steps):
(step 1): make sure seccond rom package is on your external storage ...see this post -> http://forum.xda-developers.com/showpost.php?p=52830021&postcount=45
(step 2): chose rom zip you want to patch, patch them
(step 3): reboot again into boot menu (new rom entry will be displayed), select these rom to boot, on led blinking press to boot into cwm, now you are in cwm of these rom, now navigate to the same folder where is your package, you will find zip with appended name "patched.zip", chose these patched zip to install trought these recovery, you are done!
Click to expand...
Click to collapse
WARNING:
there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
Click to expand...
Click to collapse
Source code of the my bootmenu project
https://github.com/munjeni/bootmenu_z1_and_z1c
Public License for BOOTMENU and for my Auxiliary Work
You can Distribute my source without my Permissions. Distribution should include my XDA name 'munjeni' and Link to this 'BOOTMENU' thread in your Credits sections/About sections and Properly Visible to Human Eyes. If you use our source and have them modified, you need to make them public to everyone!!! If you not propertly use my source and you not give proper credit, and you not share your modified source code which is based on my source code, I will find you and I will report your post!
Click to expand...
Click to collapse
No doubt, I'm really interested in multi boot,
I have tried it on my XU and it was awesome:laugh:
munjeni said:
Hallo, just to reserve our thread for something that you will like for sure! I have plan to port my old project to our device, more info you can see here -> http://www.xda-developers.com/android/xperia-boot-menu-ported-to-the-xperia-p-in-preview-form/
First thing - I will port them, thats for sure! Next thing - will try to integrate all things into boot menu (look into tutorial thread to see how it working) to make all things easy to all as possible, first of all I need to get more free time! Soon when I get one free day I will give you beta version! By now whant to see your opinions! Do you have interest in multiboot??? Let me know first!
Click to expand...
Click to collapse
I'm flashoholic,like to test everything, multiboot sounds nice
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Would this for example allow to have stock and cm11 both installed and easily switch between those 2? If yes then im totally up for it
Sounds definitely awesome!
Progress... Boot menu beta done, having problem with kexec, seems kexec not working. Will try with stock kernel since cm kernel probably have no working kexec.
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
munjeni said:
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
Click to expand...
Click to collapse
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
XperienceD said:
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
Click to expand...
Click to collapse
I'm sorry but I do not know what you're talking about! Plese be more clear!
munjeni said:
What? Plese be more clear
Click to expand...
Click to collapse
tap2wake
CABL
XperienceD said:
tap2wake
CABL
Click to expand...
Click to collapse
Sorry mate but our thread is related to the multiboot and not to the kernel things, you can open a new thread for your problem, sorry!
munjeni said:
Sorry mate but our thread is related to the multiboot and not to the kernel things
Click to expand...
Click to collapse
Oh, given that a boot.img is actually a kernel I thought it might be something you could implement whilst working on it.
munjeni said:
you can open a new thread for your problem, sorry!
Click to expand...
Click to collapse
They're not problems they are suggestions.
New version is out!
Changelog:
- all isues with kexeced kernel solved (missed modile data, wifi, bluetooth...etc)
- black theme
Enjoy!
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
munjeni said:
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
Click to expand...
Click to collapse
I'm planing on trying tomorrow, I'll try and give some feedback
Solved! Will give you soon cm11 in multiboot!
munjeni said:
Solved! Will give you soon cm11 in multiboot!
Click to expand...
Click to collapse
Well then I shall wait until you do so Thank you for your effort:fingers-crossed:
Done and CM11 is booted sucesfully from sdcard By now have only one problem which I have experienced last year on my multiboot for Xperia Go, I have solved them on Xperia Go but unable to find a thread how I got fixed them solved, problem now on Z1C is these seccondary rom runing from sdcard is very slow like was a year ago on Xperia Go, if some one found my post where I have fixed that please give me a link. I don't know if there is something related to the tune2fs parameters since I forgot how I got them fixed. Every idea is welcome!
Maybe this
http://forum.xda-developers.com/showpost.php?p=44945343&postcount=24
http://forum.xda-developers.com/showpost.php?p=44969886&postcount=36
http://forum.xda-developers.com/showpost.php?p=44979190&postcount=47
Yes seems 3.th post related to tune2fs and journal_data_writeback to cache and data giving better performance. Stil noticed some lags, probably because my 8gb old sdcard is so slow Will try to boot from internal storage, maybe it will give better performance or at least maybe an 64gb class 10 sdcard can solve lag problems? What you think guys?
So... here I will share 2 scripts I made to fix permissions for ViPER4Android running with enforced SELinux.
Why 2 scripts?
I like to keep everything open-source. Here I like to notice, Cyanogenmod is taking the wrong direction in my point of view. Every update takes out something of the customization possibilities of the user, so I am thinking of choosing new ROM. I faced real nightmare with SELinux permissions (well... SELinux is good, but Cyanogenmod doesn't provide any tool or way to manage those permissions). The more funny part is that with branch 13.0 of cyanogenmod there is no more init.d. Before someone corrects me - yeah... there is init.d, but SELinux blocks any script from executing at boot time, so don't use it. You will get your logs spammed by error messages. So... I've tried to enable init.d again, but there is no way to manage init.d to work as before. I've tried lots of different fixes from other posts, but nothing seems to work anymore, because of SELinux restrictions. I didn't managed to find any way to run scripts on boot time with root permissions in a suitable way... without messing with other system files or rebuilding build.img... so I came with those 2 solutions:
ViPER4Android (OpenSource) This is the solution I recommend to all of you. It is full open source. It doens't mess with you current system and it should work on any device/ROM. The zip file contains ViPER4Android app and driver, sepolicy-inject tool from setools-android so we can set permissions for ViPER4Android to work with enforced SELinux and Universal Init.d.
sepolicy-inject is open source equivalent to supolicy tool of Chainfire's SuperSU. I strongly recommend sepolicy-inject over supolicy, because every root closed source app should be threaten as security risk as the code can't be examined. I don't trust it esepcially when it is part of your android root manager
Universal init.d is just a application - it simulates init.d function. Imagine it like init.d on the user side... sadly enough you need to be pre-rooted to get it running.
ViPER4Android (Legacy) Maybe more of you will like this solution as it is more automated and it doesn't require any user action after installing the zip. This zip will do the same as the one above - it will install ViPER4Android removing all other DSP apps, but here come the difference - THIS SCRIPT WILL INSTALL CHAINFIRE'S SUPERSU in order to set SELinux policies for ViIPER4Android. Chainfire's SuperSU uses supolicy-tool - it let you manage SELinux policies on boot time. Chainfire's SuperSU will run everything in /system/su.d/ so again... you have init.d support - this is the real pain in the ass.
Before you download and flash, please read:
Both scripts WILL REMOVE other DSP apps from your device and will install ViPER4Android 2.4.0.1. I STRONGLY RECOMMEND TO USE SOLUTION 1 AS IT IS FULL OPEN SOURCE! Support open source software!!!
INSTRUCTIONS
ViPER4Android (OpenSource) - IN ORDER TO WORK, YOUR DEVICE MUST BE ROOTED! (Your device need to be rooted as Unversal Init.d needs root permissions in order to simulate init.d functionality)Download the .zip; Flash and reboot; Open Universal Init.d and grant root permission if asked; Reboot once more in case it don't work!
Sometimes Universal init.d is not fully initialized and needs some root permissions. That's why you need to reboot second time - then everything works. No further actions needed.
ViPER4Android (Legacy) - Just flash and reboot... but once more - SUPPORT OPEN SOURCE AND CHOOSE SOLUTION 1!!!!
For Samsung devices - if the scripts above doesn't work for you, check this post. Thx to Viper4713 for the instructions and voshchronos for solving the issue!!!
Hope to make someone happy
PS: If u want to make me happy with some beer, here you can donate a small amount. Thank you for your support.
Can i flash it on android one device running on 6.0.1
Yes. If you have any issues, please let me know!
rpangelov said:
Yes. If you have any issues, please let me know!
Click to expand...
Click to collapse
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
hiropandaz said:
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
Click to expand...
Click to collapse
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
rpangelov said:
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
Click to expand...
Click to collapse
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
hiropandaz said:
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
Click to expand...
Click to collapse
You are welcome! As I mentioned in the instructions - the legacy script will work always, but I don't like the implementation of it. I am working on new version of the opensource script, so there won't be any issues of that kind. When I am ready I will upload it here after updating my first post.
Greetz,
Angelov
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Primokorn said:
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Click to expand...
Click to collapse
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
rpangelov said:
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
Click to expand...
Click to collapse
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Primokorn said:
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Click to expand...
Click to collapse
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
rpangelov said:
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
Click to expand...
Click to collapse
I mentioned su.d because that's a solution with newer Android versions but I didn't say it's the best one. Using FLOSS softwares is a good move but you are using proprietary codes with CM.
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
trongtin64 said:
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
Click to expand...
Click to collapse
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
rpangelov said:
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
Click to expand...
Click to collapse
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
trongtin64 said:
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
Click to expand...
Click to collapse
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Primokorn said:
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Click to expand...
Click to collapse
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
trongtin64 said:
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
Click to expand...
Click to collapse
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Primokorn said:
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Click to expand...
Click to collapse
I'll use the one from my custom rom . Thank you for helping me :good:
It works great. thanks.
my bad for not following the instructions.
Preliminary operations/infos
First of all: what's Treble?
Find it out here.
How do I obtain my bootloader unlock code?
GO HERE, FAST!
Huawei officially ceased the unlocking service.
How do I get Treble on my device?
At the moment of this write down, EMUI it's still in private BETA.
The only chance to obtain it it's to follow this guide CAREFULLY.
What if I want to revert to EMUI 8/5?
Follow the steps described in the guide to get treble on your device using EMUI 8 files if you want to revert to EMUI 8, or EMUI 5 if you wish to revert to it.
The road it's long...
So, you're sitting there, not understanding why there are so much ROMs in this section and why you shouldn't use the ones appearing in Treble-Enabled Device Development since you worked so hard to get Treble on it.
Let's try to answer a universal question.
What's the difference from the "standard" GSIs and the ROMs in this section?
Well, the ROMs here were made keeping an eye on the "optimization per-platform" concept, basically tracking down some proprietary stuff inheriting them under /system .
**WHAT FOLLOWS ARE PERSONAL OPINIONS**
I honestly think, that we should cut off this approach.
Inheriting stuff under /system has no more sense.
Am I saying that what I did till now had no sense?
Yes.
The whole Treble concept relies on moving away from system, any vendor related stuff.
So why in the hell should we inherit proprietary stuff in our system partition again?
When we have other ways to don't mess with it?
The only stuff that still "deserves" to have something to do with /system it's the Huawei Camera.
Everything else, belongs to /vendor.
Furthermore, our goal, as developers and users, should be to track down specific-platform bugs and report them.
Co-operation is the sake of open-source and the key to success in a wonderful GSI experience for everyone.
Is my device ready to use a "standard" GSI?
Pretty much.
Huawei doesn't ship any overlay under /vendor in our PRA, because it's inherited in EMUI under /system.
But, you can follow this guide, to include the needed overlay to be fully GSI-ready.
Also, you need this thread too to fix offline charging on your Huawei device.
Known Bugs on GSI and "specific-GSI"
NFC has been an annoying issue all along the development process on some Huawei devices.
But this flashable zip, seems to solve the issue on our PRA.
Indeed it needs more testing.
Available tools/software for your PRA
ADB and Fastboot
TWRP
MindTheGapps
Huawei Camera Magisk
OEMInfo (TWRP backup)
HuRU
Stock Ramdisk (ramdisk partition)
Stock Recovery (recovery_ramdisk partition)
Specific-GSI available
Lineage OS https://forum.xda-developers.com/p8...t/rom-lineage-os-huawei-p8-lite-2017-t3787193
CrDroidhttps://forum.xda-developers.com/p8.../rom-crdroid-4-2-huawei-p8-lite-2017-t3785615
AospExtendedhttps://forum.xda-developers.com/p8.../rom-aospextended-5-4-huawei-p8-lite-t3778938
AOSPhttps://forum.xda-developers.com/p8...ent/rom-aosp-r23-huawei-p8-lite-2017-t3779115
Resurrection Remix 6https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444
SlimRom 8
AICP
Specific GSIs are now discontinued.
Go to the Treble Enabled Development sub to get some ROMs to flash!
NOTE:
This ROMs will be discontinued in a couple of weeks, since the installation of the overlay (previously highlighted in the paragraph "Is my device ready to use a "standard" GSI?") will give access to a full fledged GSI experience without the need of specific GSIs.
Custom kernels
Labyrinth
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
If this isn't clear enough, please, check this contribution.
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
From 16.6 version, Magisk it's fully working.
Please, refer to this thread for a correct installation.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
adb logcat > file.txt
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Hey you!
If you're reading this message I want you to help this community.
Share your thoughts about this posts or post your un-answered questions below.
The more we share, the best experience we'll get.
Also, please respect my work.
If you do integrate some of this infos in your thread/website or whatever, add me in the credits.
Furthermore, feel free to join us at @GSI_HI6250 on Telegram, we're funny people, I swear.
Is this non-clear somehow?
Or you just need help?
Fill the help form below.
Device Variant:
Device Firmware:
Is your device rebranded?:
How frequently this issue happens?
Is this happening now?
Describe the issue:
Describe steps to reproduce the issue:
Attach logcats/full bugreports as described on the paragraph "How to report bugs"
Or simply join the telegram group.
Peace.
Dil3mm4 said:
Kaioken reserved
Click to expand...
Click to collapse
Super Saiyan reserved
Lol
Dil3mm4 said:
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Click to expand...
Click to collapse
THAT WORKED. FINALLY 8.1 WITH BOOTLEGGERS GSI, 128GB micro SDXC as INTERNAL. I AM HAPPY
for beginners:
boot after working rom in twrp
go in advanced
go to file manager
go to /vendor/etc/
open file "fstab.hi6250" (after copying with and having a recovery of it, open with notepad++ or something else)
there should be a line with: "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
erase the part: ",fileencryption=aes-256-xts:aes-256-cts"
save
erase the original fstab.hi6250 file in vendor/etc
and put the new fstab.hi6250 file in
reboot in bootloader
flash stockrecovery.img
reboot recovery
factory reset in stock recovery
reboot
DONE.
now you can see the SD card as internal and use for apps.
Need your help
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Mister746 said:
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Click to expand...
Click to collapse
Updated last post, please submit the infos needed via that form.
Thanks.
Hi, i am experiencing a weird bug on every GSI, specifically, snapchat video recording is fine and smooth, but after tapping on the "send" button it says "failed to add" and doesnt even give a chance to resend the same snap. It happens on all treble roms i've teted so far (i tested every specific GSI for PRA, and some openkirin and otger ones). @dill3m4 do you have any idea how to fix it? I hope there is a way to do a flashable zip or something like the NFC fix. Once i get back home (2-3 days) i will post some logs, in the meantime, can someone please confirm if the issue persists, and gather logs? ?
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
jedtan025 said:
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
Click to expand...
Click to collapse
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
neondragon1909 said:
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
Click to expand...
Click to collapse
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
jedtan025 said:
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
Click to expand...
Click to collapse
I couldn't find the file using TWRP either. Had to use root explorer to find and edit the file. As for hurupdater, I'm not sure if it's the same for your region, but for pra-la1 there were 3 files.
And as for the the 2 files, I successfully flashed using the updater with only the update.zip so try updating anyway. If that doesn't work, use the eRecovery
Update:
Added Magisk news;
Added stock PRA ramdisk
UPDATE:
Added Offline Charging Fix in post #2
Added references to Treble Enabled device development;
New Huawei Magisk Camera;
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
cyprian99 said:
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
Click to expand...
Click to collapse
Obtain what?
Treble roms?
Yay! Emui 8.0 has arrived on my c432 pra-lx1 (b360) . Everything is perfect.
The guide to get treble is unclear, how can the very first step be to download update.zip? I did and now i have a trojan, thanks a lot
How to unlock bootloader? Now the Huawei site is unavailable
Wysłane z mojego PRA-LX1 przy użyciu Tapatalka
[Mod announcement] This thread was closed due to a takedown request by author. You will find this module in the official Magisk repository and support channels can be found in the accompanied documents. Thank you for your interest and have a great stay on XDA.
Disclaimer: I will not be held responsible if your device stops working, catches fire and claims to have been modified before it was cool.
Description
Font Changer allows you to change the font on your Android device. (check the requirements section for more)
Requirements
root(magisk 20.0)
font changer(magisk modules)
terminal
busybox
custom recovery (not a requirement per-se, but highly recommended in case something goes wrong
install font changer modules once check active in magisk manager then reboot device
open terminal
#su
#font_changer(type in terminal)
would like to update the font list
Y/ n
select font
list downloadable fonts install and reboot
Supported ROM OS Version:
Q (Android 10) - OOS
@topjohnwu(magisk modules)
https://github.com/topjohnwu
Original author: @JohnFawkes
This sounds great, bu there's no link to the module....
docnok63 said:
This sounds great, bu there's no link to the module....
Click to expand...
Click to collapse
So you know you can search modules in Magisk Manager?
Not sure why you're didn't credit the creator @JohnFawkes....
TotallyAnxious said:
Not sure why you're didn't credit the creator @JohnFawkes....
Click to expand...
Click to collapse
Thanks..... Yea would be nice to be credited at least...... even say that the module is available officially in the magisk repo.......
docnok63 said:
This sounds great, bu there's no link to the module....
Click to expand...
Click to collapse
the module some time update or some Dev need to update that y not add to links one i share the experience bcoz many time serach android pei but not working on font so android working now android q i shared thank you
JohnFawkes said:
Thanks..... Yea would be nice to be credited at least...... even say that the module is available officially in the magisk repo.......
Click to expand...
Click to collapse
you know the reason thank buddy
george.simbu said:
the module some time update or some Dev need to update that y not add to links one i share the experience bcoz many time serach android pei but not working on font so android working now android q i shared thank you
Click to expand...
Click to collapse
i have no idea what your trying to say..... regardless i am the original creator and would really appreciate if you could at least credit me and say the module is available in magisk repo. or just read the readme file. or even just add my website. https://john-fawkes.com/Downloads/fontchanger.zip as the link
---------- Post added at 04:18 AM ---------- Previous post was at 03:52 AM ----------
george.simbu said:
you know the reason thank buddy
Click to expand...
Click to collapse
Please dont include the zip here......... this could cause issues in updates etc etc
JohnFawkes said:
i have no idea what your trying to say..... regardless i am the original creator and would really appreciate if you could at least credit me and say the module is available in magisk repo. or just read the readme file. or even just add my website. https://john-fawkes.com/Downloads/fontchanger.zip as the link
---------- Post added at 04:18 AM ---------- Previous post was at 03:52 AM ----------
Please dont include the zip here......... this could cause issues in updates etc etc
Click to expand...
Click to collapse
yes i add to credits thanks you buddy you have great work:angel:
george.simbu said:
yes i add to credits thanks you buddy you have great work:angel:
Click to expand...
Click to collapse
Thanks! I appreciate it! not sure if your in the telegram group but this is the message i posted there about FC earlier today
"ATTENTION ALL USERS!!!!!!!!
Im in the process of transfering my domain name john-fawkes.com to another provider! While this is happening EXPECT downtime in fontchanger! Downloading new folts/emojis will likely fail. fonts/emojis you already have in your fonts folder in fontchanger folder will still apply since the code checks for the font before it starts downloading it and if it exists already then it uses the on device one instead of downloading."
george.simbu said:
Disclaimer: I will not be held responsible if your device stops working, catches fire and claims to have been modified before it was cool.
Description
Font Changer allows you to change the font on your Android device. (check the requirements section for more)
Requirements
root(magisk 20.0)
font changer(magisk modules)
terminal
busybox
custom recovery (not a requirement per-se, but highly recommended in case something goes wrong
install font changer modules once check active in magisk manager then reboot device
open terminal
#su
#font_changer(type in terminal)
would like to update the font list
Y/ n
select font
list downloadable fonts install and reboot
Supported ROM OS Version:
Q (Android 10) - OOS
Credits
@JohnFawkes(font changer)
https://github.com/Magisk-Modules-Repo/Fontchanger/commits?author=JohnFawkes
@topjohnwu(magisk modules)
https://github.com/topjohnwu
you can download latest version on this
https://john-fawkes.com/Downloads/fontchanger.zip
Click to expand...
Click to collapse
Icon name in that ss ?
insaneparnoid said:
Icon name in that ss ?
Click to expand...
Click to collapse
linebit
I am getting this error while select rosemary font and also if i select any other font , the fonts dosent change for system , file i cant see fonts getting changed in my setting as posted in ss
insaneparnoid said:
I am getting this error while select rosemary font and also if i select any other font , the fonts dosent change for system , file i cant see fonts getting changed in my setting as posted in ss
Click to expand...
Click to collapse
"ATTENTION ALL USERS!!!!!!!!
Im in the process of transfering my domain name john-fawkes.com to another provider! While this is happening EXPECT downtime in fontchanger! Downloading new folts/emojis will likely fail. fonts/emojis you already have in your fonts folder in fontchanger folder will still apply since the code checks for the font before it starts downloading it and if it exists already then it uses the on device one instead of downloading."
george.simbu said:
"ATTENTION ALL USERS!!!!!!!!
Im in the process of transfering my domain name john-fawkes.com to another provider! While this is happening EXPECT downtime in fontchanger! Downloading new folts/emojis will likely fail. fonts/emojis you already have in your fonts folder in fontchanger folder will still apply since the code checks for the font before it starts downloading it and if it exists already then it uses the on device one instead of downloading."
Click to expand...
Click to collapse
just on more try and reboot you can change robotic to normal in font system settings
george.simbu said:
"ATTENTION ALL USERS!!!!!!!!
Im in the process of transfering my domain name john-fawkes.com to another provider! While this is happening EXPECT downtime in fontchanger! Downloading new folts/emojis will likely fail. fonts/emojis you already have in your fonts folder in fontchanger folder will still apply since the code checks for the font before it starts downloading it and if it exists already then it uses the on device one instead of downloading."
Click to expand...
Click to collapse
But fonts are getting downloaded, its giving copy error that it couldnt cp the downloaded font to destination , even if i move the required folder manually idk how to apply it
insaneparnoid said:
But fonts are getting downloaded, its giving copy error that it couldnt cp the downloaded font to destination , even if i move the required folder manually idk how to apply it
Click to expand...
Click to collapse
You need to download fonts copy to custom floder
connect to pc path: (Computer\GM1911\Internal shared storage\Fontchanger\Fonts\Custom)
or use root browser
and install custom font
Will this work on custom ROMs based on Android 10? Or is strictly for OOS?
sparky2029 said:
Will this work on custom ROMs based on Android 10? Or is strictly for OOS?
Click to expand...
Click to collapse
i am using oss only i tested
george.simbu said:
i am using oss only i tested
Click to expand...
Click to collapse
Okay thanks for the reply! Maybe I'll test it in a little bit and see if it works