Database Develop

[DEV] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6

Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.41.6)
https://docs.google.com/uc?id=0B5c3gpyMBJusWi1XN09fZjkzUWM&export=download
aromafm_tass.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusLTk5ZENsNWpudms&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ-Touch Recovery for Galaxy Mini, Tool/Utility for the Samsung Galaxy Mini
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-26

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
GALAXY MINI GOES OFFICIAL NOW!!!!!!
You'll now find Galaxy Mini in the officially supported devices list at the Main thread.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.

alexanderq said:
Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.
Click to expand...
Click to collapse
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery

Faiyaz5yaz said:
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery
Click to expand...
Click to collapse
You mean, you are always rebooting to recovery and not to your rom?
If so, it is a problem of your device configuration by your device developer because this happens also in Jenkins recovery. This is not a fault of my recovery.
Now, you can restore boot of a backup (if you made any) or you can install your current rom again and wipe dalvik cache and you'll be back normal.

But i have renamed the zip and it does not work.And i tried another ROM but it all ways reboots to recovery.

Can someone else confirm that it always reboot to recovery even after re-installing a rom?

Good work bro.:thumbup:
Sent from my GT-S5570 using xda premium

no
Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I didn't restore back up..
I reflashed my previous cwm..
it booted normally

Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I confirm it. I even flashed another ROM and it still reboots to recovery instead of system.
Aroma FM works, but there is something I noticed: If you tap internal sd or external sd, they are empty, you have to go to storage/sdcard00 to get to your sd card. Can you somehow link the external sd to the sd card?

Thanks everyone for reporting....
I'll try to fix this when I get time...
ast00,
Internal sd and External sd will be empty because they are kept there for devices having two different memories. There should be an option: sdcard directly on the root directory. Please see carefully.

Good news:
My friend @chraso gave me hint about the problem. There was a very small problem with tags, I'll be fixing and making updated recovery today/tomorrow. Will also update recovery sources.

First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.

Bhargav97 said:
First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.
Click to expand...
Click to collapse
flashed the latest zip
still not booting into the same rom..
didn't test new rom

Faiyaz5yaz said:
flashed the latest zip
still not booting into the same rom..
didn't test new rom
Click to expand...
Click to collapse
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?

Does not work for me either, it reboots to recovery and i noticed that to make aroma work i must first install the zip from recovery and then it works OK .

not that
Bhargav97 said:
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?
Click to expand...
Click to collapse
I mean I just changed the recovery didn't touch any roms.. after changing recovery , it keeps bootin to the recovery

Bro,
please read FAQs, this is a problem of your device sources. For solution, see FAQs.
After that, please give me broader report.

You di not ask the right question:
Does this work for someone , anyone please confirm.

[STOCK][D650X][4.4] Update to 17.1.1.A.0.402 [Root & XZDR]

{
"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"
}
Requirements:
Flashtool 0.9.16 by @Androxyde
XZDualRecovery 2.7.124 BETA or newer.
Current rooted FW version: 17.1.A.0.55 or 17.1.A.0.69.
Special features:
SuperSU integrated in system, FULL ROOT!
XZDualRecovery 2.7.124 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
init.d support (read how to enable)
For both locked and unlocked bootloaders!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
If you are unable to download torrent files directly, have http://zbigz.com/ do it for you!
How to update to 17.1.1.A.0.402:
Files (Find the files on the DevDB Downloads tab!):
For D6502: Download D6502_17.1.1.A.0.402.flashable.zip (931MB) and D6502_17.1.1.A.0.402_Stripped.ftf (23MB)
For D6503: Download D6503_17.1.1.A.0.402.flashable.zip (912MB) and D6503_17.1.1.A.0.402_Stripped.ftf (22MB)
Save them somewhere you remember;
Put 'D650X_17.1.1.A.0.402.flashable.zip' on (the external) SDcard1;
Put 'D650X_17.1.1.A.0.402_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in TWRP and don't forget to backup the contents of 'SDCard' (the internal storage!);
Flash 'D650X_17.1.1.A.0.402.flashable.zip' in TWRP;
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'D650X_17.1.1.A.0.402_Stripped.ftf' using flashtool;
Reboot to system.
The first boot will be slow and after some time at the boot animation you will see Android start optimizing the apps on your phone.
Enjoy! :laugh:
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a .55 or .69 FTF using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery;
Then try to update again using TWRP.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /sdcard1/XZDualRecovery, pack them up and send them to me or attach them to your bug report.
Thank you
XDA:DevDB Information
[STOCK][D650X][4.4] Update to 17.1.1.A.0.402 [Root & XZDR], ROM for the Sony Xperia Z2
Contributors
[NUT]
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 17.1.A.2.55/.69
Based On: STOCK
Version Information
Status: Abandoned
Stable Release Date: 2014-06-17
Beta Release Date: 2014-06-16
Created 2014-06-16
Last Updated 2014-08-26

ROM STATUS: STABLE
WARNING:
Be prepared to lose everything if it for some reason goes belly up!

Huzzah! Thanks for your hard work, @[NUT]! You were there since the beginning, and without you (and the others) this wouldn't be possible!
Just out of curiosity, what's the base FTF for this ROM?

How do I get TWRP to start instead of CWM?

hidea said:
Huzzah! Thanks for your hard work, @[NUT]! You were there since the beginning, and without you (and the others) this wouldn't be possible!
Just out of curiosity, what's the base FTF for this ROM?
Click to expand...
Click to collapse
D6502 is based on Customized_IN
D6503 is based on Customized_DE
Puffin617 said:
How do I get TWRP to start instead of CWM?
Click to expand...
Click to collapse
Press volume down to enter twrp.

Puffin617 said:
How do I get TWRP to start instead of CWM?
Click to expand...
Click to collapse
Hold vol down on boot or use NUT app to set which recovery will be primary when you restart device. (you'll get that app with recovery)

[NUT] said:
D6502 is based on Customized_IN
D6503 is based on Customized_DE
Press volume down to enter twrp.
Click to expand...
Click to collapse
BTW, the only backup options I see in TWRP are:
Kernel Image
Trim Area
System
Cache
Data
I don't see SDCard

funky0308 said:
Hold vol down on boot or use NUT app to set which recovery will be primary when you restart device. (you'll get that app with recovery)
Click to expand...
Click to collapse
where I can find the NUT app?

pacomicro said:
where I can find the NUT app?
Click to expand...
Click to collapse
If I'm reading this correctly,
The default on first boot with the boot-to-recovery flag set by any recovery is PhilZ Touch Recovery.
In your XZDualRecovery folder in either /cache or /storage/sdcard1 you will find a file called XZDR.prop. Set dr.default.recovery=cwm to dr.default.recovery=twrp to change the default recovery to TWRP. The button choice however takes precedence, so you can always overrule the default!
You can also change back to 'Vanilla CWM' if you wish by changing dr.vanilla.cwm=false to dr.vanilla.cwm=true in the XZDR.prop file.
Init.d support is disabled by default, set dr.enable.initd to true to enable it.
Insecure ramdisk support is disabled by default, set dr.insecure.ramdisk to true to enable it, set to 'power' to boot it by pressing the power button at boot.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=2261606

pacomicro said:
where I can find the NUT app?
Click to expand...
Click to collapse
Once you're done with flashing all the files and reboot your phone, you will see a new app installed. That's [NUT]'s app.

funky0308 said:
Hold vol down on boot or use NUT app to set which recovery will be primary when you restart device. (you'll get that app with recovery)
Click to expand...
Click to collapse
Cant get it to work... Do I really NEED to use TWRP? PLease help...
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
Something is not right. When I keep VOL down with reboot the device stays black
UPDATE : Got everything done Thanks
Am on 402 rooted without even touching the bootoader

@[NUT]
OK mate...
Awesome work

Ahh, yes. @[NUT] app is actually in the app drawer, and it's called NDR Utils. The icon is a cute red little devil! The app will let you choose which primary (default?) recovery to use. Also, has a bunch of power menu options.
Now… slightly off topic; will we be seeing a similar XZDR and ROM for the Z2 tablets (particularly the 16GB WiFi/SGP511)?
Again, thanks for the good work, @[NUT]!

Super!!
Fantastic!! Downloading files to downgrade first and then will test this!! Excited and will report back in 3-4 days due to slow bandwidth speeds!

It works! Woohoo!
I'm happy to report that I went through the entire process (downgrade to .55, rooted via Community RootKit, installed dualrecovery, then flashed [NUT]'s files) and I'm on 402 with locked bootloader and everything's working well so far! :good::laugh::highfive:

Guys, AWESOME work...
Being on .402, rooted, TA backed up, locked, seems almost unreal

ok everything went well but i have no network signal just a red cross next to the icon

Strangeland16 said:
ok everything went well but i have no network signal just a red cross next to the icon
Click to expand...
Click to collapse
What model? Did you flash the entire ftf as instructed?
hidea said:
Now… slightly off topic; will we be seeing a similar XZDR and ROM for the Z2 tablets (particularly the 16GB WiFi/SGP511)?
Click to expand...
Click to collapse
I'm working on the Recovery at least, using my DIY guide some brave and helpful soul should be able to create a package then.

Strangeland16 said:
ok everything went well but i have no network signal just a red cross next to the icon
Click to expand...
Click to collapse
Try to go to Settings -> More -> Internet settings and download your network settings.

[NUT] said:
What model? Did you flash the entire ftf as instructed?
d
I'm working on the Recovery at least, using my DIY guide some brave and helpful soul should be able to create a package then.
Click to expand...
Click to collapse
im on d5603 and yes followed instructions to the letter but the phone finds no network

[DualBoot] DualBootPatcher - a much simpler dual boot solution for Android One device

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support Android One devices Link
I am not the creator, just the supporter
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch)
2. A ROM
3. The Dualboot Patcher - From here (Download the APK in Downloads Section)
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a Stock ROM, I highly recommend installing Stock as the primary ROM. Otherwise, any mods will need to be patched before flashing.
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
cm-13-20160118-sprout4.zip
would create a new
cm-13-20160118-sprout4_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
App and data sharing
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.​
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!​
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.​
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.​
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.​
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it ​
Downloads:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install as not much space there. just install on /data partition.
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
​
XDA:DevDB Information
DualBootPatcher - a much simpler dual boot solution for Android One devices, ROM for the OEM Cross Device Development
Contributors
Anik_khan, chenxiaolong
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Stable Release Date: 2016-01-20
Created 2016-01-20
Last Updated 2016-01-22

Reserved

Great work @Anik_khan thanks for porting for sprout
Sent from my Nexus 5X using Tapatalk

Dude that was awesome, will it work for both sprout4 and sprout8?

:good: It's Awesome bro.. Very interesting.. :good: :good: and thank you for your support

Hell thats SoooogoooD...

hp5942 said:
Dude that was awesome, will it work for both sprout4 and sprout8?
Click to expand...
Click to collapse
Yep it will! all android one varients

Great job, nice to see that it's up !

Awesome Dude
And add "Android One" to tag list

Name any Custom kernels for dual boot support plz

?......
Sharing apps not working..not show on 2cd rom..... Anyone try sharing apps?

Can't Boot in Data Slot ROM Stuck On Boot Logo
Please Help

You did a great work thanks...........

sweet how does it work

Sharing apps not working
Show update ramdisk
Then show,
The ramdisk failed to update ....,
Plz help

thanks for that

Secondary ROM upgrade
I have a flashable zip for update of secondary ROM (in data slot 1)
How do i install that update?
there is an option 'primary ROM upgrade' but no 'secondary ROM upgrade'

very delighted. finally can be realized in the boot multiple sprouts. thank you for your hard work and team developer
---------- Post added at 04:14 PM ---------- Previous post was at 04:14 PM ----------
you rock ! bro ... awesome

Can we Dual Boot Stock ROM (6.0.1) and CM13?
Hey Guys, I just wanted to know that, Can we Dual Boot Stock Rom (6.0.1) with CM13 ? If anyone has tried doing it please let me know ?Coz I watched Video by #Coreman on YouTube abt Dual Booting Of ANDROID ONE and in that Video he said that we can Dual Boot Stock Rom only with MIUI ROM So if anyone knows please Let me know ? Thank You !

How to install gapps and other zips on secondary ROM ,dataslot.

[CLOSED] BETA - [ MOD DS EMUI4.0.3 Special by Persona78 ] - Update 06-05-2019

BETA - MOD DS EMUI4.0.3
Special-Version​
​
Hi!
Before we going to MOD, READ THIS!!!
{
"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"
}
HTML:
# Your warranty will be void!!!
# Battery must be above 50% before flash it!
# I m not responsible for any bricked devices, dead SD cards or what ever!
# YOU ARE CHOOSING to make these modifications!
# Before flashing do backup from your personal data!
# Backup BOOT, CUST, RECOVEY and SYSTEM images!!!
# You can restore it if mess up or you don t like it!
# This is the MOD that i have and I like it like it is!!!
# Do not blame me if something goes wrong on your phone!
# !!! I always advise to do a factory reset after flashing the ROM !!!
# Don´t complain if you don´t have done anything written above
#
#
#
#
Now the MOD!!!
MOD for Android 6 version
Is based on Stock B638,, i don´t test it on lower versions
You need to be in Android 6 first before install it!!!
​
To install ROM and mod:
Option 1:
Do backup with default backup app from Huawei
copy update.app to dload folder in sd card or internal memory, if you don´t have that folder you can create it
Install default recovery
Boot in to recovery and do factory reset
will in recovery press (vol +) (vol -) (power) at same time wait untill reboot and release only power then volumes when star installing
Again boot in to recovery and do factory reset
Press vol - and power untill boot in to bootloader
Install TWRP
Unplug USB!
Boot in TWRP by pressing vol + and power
Copy my mod in to phone and install my mod, reboot
restore backup
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Option 2:
Do backup with default backup app from Huawei
If you are in stock Android 6 and and even then it's not possible to flash any other default stock ROM use Rollback ROM Package bellow to unlock
Rollback Package Android 6 to 5
copy update.app to dload folder in sd card or internal memory, if you don´t have that folder you can creat it
Install default recovery if you don´t have it on phone
Boot in to recovery and do factory reset
will in recovery press (vol +) (vol -) (power) at same time wait untill reboot and release only power then volumes when start installing
Again boot in to recovery and do factory reset
Press vol - and power untill boot in to bootloader
Install TWRP
Unplug USB!
Boot in TWRP by pressing vol + and power
Copy my mod in to phone and install my mod, reboot
restore backup
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Option 3:
Do backup with default backup app from Huawei
Install default ROM with TWRP
Go to reboot, choose recovery, let boot in to default recovery
Do factory reset
Press vol - and power untill boot in to bootloader
Install TWRP
Unplug USB!
Boot in TWRP by pressing vol + and power
Copy my mod in to phone and install my mod, reboot
restore backup
This is the default ROM update.zip B638<-LINK
And here is B638 by dload <-LINK​
Changelog from default B638:
This update enhances carriers' network compatibility.
Integrates Google security patches released in Aug 2018 for improved system security.( 2018-08-05 ).
Kernel version Fri Aug 24 18:50:35 CST 2018
Changelog from my mod:
ROM cleaned - apps deleted but all can be found in Google Play Store
Try to get better performance - 06-05-2019
Fix Power drain - 06-05-2019
Add translator app
Add NFC tag app
Add new clonned apps, check bellow
Add a new default theme
Install Swift key as main keyboard
Add stock Recovery as main recovery . ( With phone off press vol+ and power)
Add TWRP 3.2.3 as recovery2: ( With phone off plug USB in to PC and in to Phone and press vol+ and power)
[*] Add Arena Of Valor Game - [ I play a lot! You can unistal after flash as default app ] - DELETED
Add Chrome Browser again - [ I use it as my default Browser. You can unistal after flash as default app ]
Add wifipro backgroung service
Call volume rised
Replace Bluetooh app with P9 Bluetooh app, works better and add Bluetooh direct sharing
Fix Theme Manager
Phone calls are now on 4G network, by default was on 3G ( can check it by turning ON data and do a phone call, old version add it to but i never check it to confirm)
better battery management
Mirror share was changed to Multi screen, it allow to connect to a Smart TV and use WIFI at same time with out wifi direct
Add lockscreen settings on lockscreen
Add 1080p in Youtube
Add new themes
Add P8 Lite 2017 Media Player
Add Smart rotation option on settings
Add option to hide Navigation Bar
Add ADB trough WIFI
Code:
How to use:
*Phone must be in the same network as PC
*Enable developer options
*Enable debug mode for USB
*Open ADB and type : adb connect your.phone.IP.here
*Check if in phone screen is requesting any permissions,
Give it!
*Done!
Better performance - Antutu tested 52000 score - OpenGLES 3.0 ON but not full working 10-04-2019
add some providers to cust to avoid balong issue
add lineageOS apn file
Unlock with draw - you cna draw C, E, M ,W to unlock
Have more shortcuts options on shortcut bar
Have Karaoke function
Fotos quality tweaked
Have MATE 8 camera app tweaked ( Activate more functions)
When you are on LTE zone it will show 4GLTE if not only shows 4G
Add Pixel function to Google Photos with unlimited upload ( upload limit set to the max of the user account limit) and full quality in uploads
Add Google Lens function and unlimited storage for backup in Google Photos ( the limiti is the one of your Google cloud)
Add clone app function, the empty spaces is because it is prepared for apps that you don´t have installed.
This are athe apps:
-Whatsapp
-Facebook
-Facebook messenger
-Instagram
-Telegram
-LinkedIn
-Youtube
-Google Play Games
-Google Photos
-Chrome
-Mega
-MediaFire
-Sapo Cloud ( Portugal)
Have multi window option
High Debloated
Have Fonts costumization - To use this You need a theme with font or a font theme that only have font to appaly )
Add missing libs in ROM
Have lock screen option with the palm of the hand (also works with the forearm, etc, etc)
Call Recorder
Boot tweaked for better response
Have floating video
Huawei P Smart bootanimation animation
Tweaked [ prop and xml tweaks]
SWS for speaker and headphones improved
DTS improved
Have Super night shoot in camera
Have Scanner in camera
Have light painting in camera
Have VoLTE ON by default
eyesight protection switch
Multiuser option
softlock key option
Have NFC tag app
Have launcher rotation option on launcher settings
And i think is all!
Click in the box to get the link for the MOD!!!
Special Note: Update zip linked to Stock Recovery, at the end will reboot in to Stock Recovery and will do FACTORY RESET!!!!!!!!!!!!
Click in Google Drive icon below to download MOD!
Google Drive
md5: 6f4f163609057b7c211aa146e475bf46 *Mod_B638_by_persona78.4.0.3.Special_version_060520192212.zip
* This are some apps that i cut of, to add if you want just download from Cloud storage below and install it as a regular app:
GoogleAndroidAuto.apk
GoogleAssistante.apk
GoogleCamera.apk
GoogleVRvrCore.apk
Huawei_Swype_for_Huawei.apk
HwMediacenter_12.11.2.306-121102306.apk
HwNfcTag.apk
HwThemeManager.apk
* I add 2 Wallpaper themes:
Cars.hwt
Nature.hwt
DON´T APPLAY LIKE DEFAULT THEME!!!!
Download
copy to HWThemes folder
Press a empty space on screen
select wallpapers
Select the wallpaper that you like
applay it
Cloud storage
MEGA
MediaFire​
The other apps i cut you can find it on Google Play Store or just use Huawei Backup app to backup and restore after flash.
Flash zip was tested before upload - OK
Se HERE how to get Magisk and Xposed.
IMPORTANTE NOTE:
FACTORY RESET WITH TWRP WILL NOT WIPE FULL DATA, ISSUES WILL APPEAR.
NEED FACTORY RESET WITH DEFAULT RECOVERY.
Any other issue please tell me.
Use this zip to be easy to change recoverys, download and extract to desktop, open folder and use the bat to flash default recovery or TWRP.
PS: Don´t forget, you need to be in bootloader mode to flash...
flash_recoverys.zip
Update 01-02-2019 - add TWRP 3.2.3-ALE​
If you like it press THANKS bellow!
​.

@persona78 will you pls provide how to enable font style, eyesight protection and soft lock on screen.

Can I flash this rom on C432B610-NOVA directly?
Will C432B612-NOVA be released?
thanks

geppone1970 said:
Can I flash this rom on C432B610-NOVA directly?
Will C432B612-NOVA be released?
thanks
Click to expand...
Click to collapse
Yes, can be flashed over Nova, i don't gonna update Nova because i use the clone app option from Huawei launcher.
.

udtul said:
@persona78 will you pls provide how to enable font style, eyesight protection and soft lock on screen.
Click to expand...
Click to collapse
The font style was a issue i had done, by default rom let you do customise font, the other things are all re-written in many posts i this group!
Use the search bar!
.

After the first start I am asked to restore allow or not allow

persona78 said:
The font style was a issue i had done, by default rom let you do customise font, the other things are all re-written in many posts i this group!
Use the search bar!
.
Click to expand...
Click to collapse
Well I will search thank you for your work.
Have flased your huwaei pack but no eyesight protection and soft lock on navbar.
What is wrong?

@persona78 Please, can you tell me what software you used to make system.img? I really need it.

Tested, using it... Much better than B608 and even B610!

XTutorials said:
@persona78 Please, can you tell me what software you used to make system.img? I really need it.
Click to expand...
Click to collapse
I create and use this: https://forum.xda-developers.com/p8lite/development/betap8litetoolpack-mod-p8-lite-t3589396
.

D1stRU3T0R said:
Tested, using it... Much better than B608 and even B610!
Click to expand...
Click to collapse
I edited boot and add/change some apps from other models...
.

persona78 said:
I create and use this: https://forum.xda-developers.com/p8lite/development/betap8litetoolpack-mod-p8-lite-t3589396
.
Click to expand...
Click to collapse
Ok, but I found no option to rebuild system.img, how to use your tool? There are many files in there and I saw "repackimg" batch file but when I run it it says "No files found to be packed/built" What does that mean?

Hello, does the alarm clock work while phone is off?

XTutorials said:
Ok, but I found no option to rebuild system.img, how to use your tool? There are many files in there and I saw "repackimg" batch file but when I run it it says "No files found to be packed/built" What does that mean?
Click to expand...
Click to collapse
Use the pull system.img option, it will pull your system as image

persona78 said:
Use the pull system.img option, it will pull your system as image
Click to expand...
Click to collapse
Which one?
P.S. Sorry for very small text, but my Surface Pro has a bug with cmd windows.

XTutorials said:
Which one?
P.S. Sorry for very small text, but my Surface Pro has a bug with cmd windows.
Click to expand...
Click to collapse
Boot in twrp then use option 5!
You will get your phone system.img, only can be flashed using a zip and TWRP!
If you use option 4, you will get boot, recovery and cust images to then with option 6 you can create a flash zip with it!
.

persona78 said:
Boot in twrp then use option 5!
You will get your phone system.img, only can be flashed using a zip and TWRP!
If you use option 4, you will get boot, recovery and cust images to then with option 6 you can create a flash zip with it!
.
Click to expand...
Click to collapse
You didn't understood me, no?
I am making KangVIP 4.1 and I extracted system.img to mod it and now I want to repack it to be able to flash the rom... this is what I want to mean

How can I enable root on this rom?
Because Root Checker's app show that I don't have root

XTutorials said:
You didn't understood me, no?
I am making KangVIP 4.1 and I extracted system.img to mod it and now I want to repack it to be able to flash the rom... this is what I want to mean
Click to expand...
Click to collapse
Oh! That only with linux and i don´t know! Need to mount system, etc, etc... I found it some where one time will seraching in Google.
But do you have the mods on phone?
.

persona78 said:
Oh! That only with linux and i don´t know! Need to mount system, etc, etc... I found it some where one time will seraching in Google.
But do you have the mods on phone?
.
Click to expand...
Click to collapse
And how did you done your mods?

[ROM] [8.0.0] [yuga] LineageOS 15.0 for Xperia Z (Unofficial)

{
"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"
}
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
About ROM:
This is Experiemental Build of Android 8.0 Oreo for Sony Xperia Z (C6602, C6603), Based on LineageOS.
Thanks To:
Mardon
What's working:
* ROM is experiemental and is not recommended for daily usage *
* Now we have working Audio *
I have not tested whole rom but everything works fine except:
- Flashlight and Camera
- Adaptive Brightness
Please report any bugs in the comments below!
(Special) Install Instructions for Newbies:
Warning: If you flash ROM first time do it at your own risk, You may brick device.
Before resuming remember these things:
- You can't restore TA codes on a custom ROM, TA codes only work on Stock ROMs, So if you ever reflash Stock ROM you can restore them.
- If you're Windows 8/8.1 or 10 User this Tutorial may not work for you as long as you've done This Tutorial
- Read everything Carefully, I wish you Good Luck
1.0 - Backing up TA Codes
- First you need an unlocked bootloader, But before unlocking it you have to backup DRM keys (Optional)
- Download KingoRoot, Root your device with One-Click-Root and then Download Backup-TA Program from Here
1.1 - Unlock Bootloader
- After you've done that, Unlock your bootloader from Here
1.2 - Preparing Drivers
- After you unlock your bootloader Install Sony Flashtool from Here
- Go to Flashtool Folder then go Drivers folder and select Flashtool-drivers.exe
Check the Fastboot and Flashmode drivers then Scrool down and find Xperia Z SO-02E drivers, Check it and Install them.
1.3 - Installing ADB
- Now it's time to download ADB 15 Seconds Installer from Here
Follow the instructions in the program and Install ADB/Fastboot drivers, then locate "C:/adb" folder and open it.
- Download Latest TWRP 3.1.1 from Here and move into adb folder located in "C:/adb"
- Rename TWRP 3.1.1 file to twrp (If your file extensions are shown twrp.img)
- As long as you can't flash TWRP directly as Recovery you must flash it as boot, Your ROM won't start again so back up everything before restarting to ADB!
- After you back up everything just enable USB debugging in your phone (go Settings/About and press Build Number couple times)
- Press Back button and go to Developer Settings and find USB Debugging, Enable it.
- Now go to "C:/adb" and press and hold SHIFT, Then press RMB (Right Mouse Button) and press open command window here.
- Congratulations! Now you're in adb.
1.4 - Flashing TWRP
- Write next ADB Commands:
adb devices (so you will check your device is detected by ADB or not, If adb shows any number row and then DEVICE its okay, If it doesn't then just write):
adb reboot bootloader (Look at your phone and give permissions of USB Debugging to PC, If phone reboots it means you've done everything correctly, If it doesn't then you did something wrong!)
- Well if the phone rebooted you will see blue led in the top of your phone, That means you're in a bootloader!
Write next commands:
fastboot devices (And check your device is detected by fastboot or not, same thing it will show number row and then FASTBOOT, So you did everything correctly, If it doesn't check your installed drivers, You may have little update from Device Manager so comment down below, If drivers are installed wrong and you don't see device number and FASTBOOT just restart phone and wait for the answer in the comments)
- If you see your device number and FASTBOOT enter next commands:
fastboot flash boot twrp.img
- After you've done that and you see that it has flashed without any Errors write next command:
fastboot reboot
- Now you're in TWRP recovery, Congratulations !!
1.5 - CleanFlashing ROM
- If you backed up everything just see if your computer detects your phone's MTP (media file transfer)
Go to My Computer/Xperia Z and see is there Internal Storage or not
- If There is any Storage that's good so make a Fully Clean Install
- Go back in the main menu of TWRP press Wipe, Advanced Wipe and check: Data, Cache, Dalvik Cache, System and Internal Storage, Then swipe to wipe.
- After you wiped your phone go back to the main menu of TWRP, Enter your internal storage folder from your PC and move ROM, Gapps and Rootkit in there.
- After that Press Install, You'll see lineageos, gapps and rootkit in the TWRP so press lineageos file and swipe to flash.
- Then go back (Don't Reboot) and press gapps file, flash it as you flashed lineageos.
- Go back again and flash Rootkit but when it's finished just press wipe dalvik cache and swipe to wipe it!
- After you've done that press Reboot phone.
- Congratulations!! Wait for 10 minute to boot and enjoy your new Android 8.0.0 Oreo!
1.0-2 - Troubleshooting
- If you want to install any other Custom ROMs just resume this tutorial from ADB (adb reboot bootloader) And do the same.
- If ROM doesn't boot up that means you did something incorrectly, So you have to do next steps:
Long Press Power Button and Volume UP, After it vibrates it will vibrate three more times and then release so your phone will shut down.
Get your USB Cable which's connected to PC and hold Volume UP, then connect USB Cable into phone
- You're in a fastboot, resume tutorial from (fastboot flash boot twrp.img)
- If you flashed ROM again and still doesn't work change your gapps version and download gApps-Pico
- Then it will work 100%, Or you can flash LineageOS14.1 and wait for Stable Oreo build.
- Thank you for attention, do it at your own risk and good luck
Downloads:
MOD EDIT: Download link removed.
Download the gApps (ARM, 8.0, Pico)
Download Rootkit if you want (I've tested Magisk and works fine)
- Links updated & No more error7 in TWRP
Short Install Instructions:
Move the ROM/GAPPS/ROOTKIT on your SDCARD
Flash latest TWRP (If you have old version already reflash it using flash image)
Wipe Cache, Data, Dalvik cache and System
Flash ROM
Flash gApps
Flash Rootkit
Wipe dalvik cache
Reboot!
- First boot may take some time for optimizing apps, bootanimation may have a little lag, be patient and wait.
ROM Information:
ROM Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information:
Status: Experiemental
If you like the ROM please hit that Thanks button and give some support

Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3

#iLiKo said:
Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3
Click to expand...
Click to collapse
omg I can't believe this @@
thank you so much for your awesome work ^^

with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?

404 not found
Can't find it!
If you are seeing this error page then the file in question has been deleted from the site and servers. Please contact the developer/uploader for a new link to the file.

cyparisss1 said:
with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?
Click to expand...
Click to collapse
Not TWRP problem at all, don't delete rom because mby link got broken, ill help you to fix tommorow, update-script must be changed

Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Link of old version:
MOD EDIT: Removed download link

not happen
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?

cyparisss1 said:
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?
Click to expand...
Click to collapse
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..

#iLiKo said:
Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Click to expand...
Click to collapse
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.

I am using custom rom and my device model is Xperia Z , it is possible to not verify my phone like c6603 and then the installation fails. See on the screen shots

#iLiKo said:
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..
Click to expand...
Click to collapse
welcome my friend, MOD EDIT: Removed download link

NamenIos said:
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.
Click to expand...
Click to collapse
ill explain u smth this rom is shared and doesnt require any rights to post on websites, also people must have single oreo rom for this phone to try how its like, plus i made whole tutorial of newbies now i think they wont get in problems, also everyone knowns that this is experimental testbuild, but LOSTEAM still want to share only stable.. i think differently, i think people can see how oreo really is, whats the differences and etc.. by themselves. stop it, im not gonna delete rom again.

cyparisss1 said:
welcome my friend, MOD EDIT: Removed download link
Click to expand...
Click to collapse
new link: MOD EDIT: Removed download link

Bug
Camera not working
Lag ui (recent app)
Error 7 script delete assert line

mohammadnadimi48 said:
Camera not working
Lag ui (recent app)
Error 7 script delete assert line
Click to expand...
Click to collapse
Error 7 has been fixed i think so.
Use new link

Thread closed.
#iLiKo said:
ill explain u smth this rom is shared
Click to expand...
Click to collapse
Yes, you are right here - LineageOS can be built from source.
#iLiKo said:
doesnt require any rights to post on websites
Click to expand...
Click to collapse
Not quite correct - you still need to stick to the XDA rules (see rule 12).
You need to accept the fact that the developers of the ROM don't want to release half-baked builds or unfinished work (even if it's open source). Don't we all want a stable daily driver after all?
Thread closed.