[YU Yunique][ROM][OTA] Mirrors for official Cyanogen roms & OTA updates - Yu Yunique ROMs, Kernels, Recoveries, & Other Deve

Now CM appear to have disabled their links to official roms, updates & kernels for older builds, I've mirrored them all on AndroidFileHost and put the links in one post so that they're easy to find.
There are different files for each ROM: signed fastboot flashable zips, signed zips, OTA incremental update zips., boot-debuggable images and stock recovery images.
Signed fastboot flashable zips: These contain the complete rom and can overwrite everything including your data partition. These cannot be flashed via recovery - extract their contents and flash via fastboot.
Signed zips: Normal recovery-flashable zips that contains just the system and kernel (they won't overwrite your data partition).
OTA incremental update zips: These are recovery-flashable zips that update your rom to a newer version. To check which version you are running, look at the ro.build.version.incremental line in your /system/build.prop file and then update incrementally.
Boot-debuggable images: These are boot images (kernels) that enable adb root and the developer menu options. To be flashed via fastboot.
Stock recovery images: These are stock recovery images which are recommended for applying OTA incremental update zips. To be flashed via fastboot.
Signed fastboot flashable zips
cm-12.1-20150808-EXPERIMENTAL-YOG4PAP1F0-jalebi-signed-fastboot.zip
Signed zips
cm-12.1-20150808-EXPERIMENTAL-YOG4PAP1F0-jalebi-signed.zip
OTA incremental update zips
N/A
Boot-debuggable images
cm-12.1-20150808-EXPERIMENTAL-YOG4PAP1F0-jalebi-boot-debuggable.img
Stock recovery images
N/A

Credits
@Spannaa for the inspiration.
@AndroidFileHost for the hosting.
YU for the device.
Cyanogen for making the OS.
Users for supporting the similar thread for Yureka.

[How To] Flash Cyanogen OS on YU Yunique (jalebi):
Use at your own risk - blame yourself if the device is bricked or YU doesn't provide warranty! If you're skeptical, then better wait for official announcement & tutorials.
1. Unlock the bootloader.
2. Grab the latest signed fastboot flashable zip & unpack it.
3. Assuming that fastboot binary is on system's path, execute the following:
Code:
fastboot -i 0x2A96 flash aboot emmc_appsboot.mbn
fastboot -i 0x2A96 flash modem NON-HLOS.bin
fastboot -i 0x2A96 flash rpm rpm.mbn
fastboot -i 0x2A96 flash sbl1 sbl1.mbn
fastboot -i 0x2A96 flash tz tz.mbn
fastboot -i 0x2A96 flash hyp hyp.mbn
fastboot -i 0x2A96 flash splash splash.img
fastboot -i 0x2A96 flash boot boot.img
fastboot -i 0x2A96 flash cache cache.img
fastboot -i 0x2A96 flash system system.img
fastboot -i 0x2A96 flash recovery recovery.img
fastboot -i 0x2A96 flash userdata userdata.img
fastboot -i 0x2A96 reboot

Note to users:
Those who've already flashed this build are kindly requested to share info about OTA prompts. Please do share the build.prop after each OTA.

Reserved for future.

To remove the watermark, install Xposed & then use it.

how to flash d signed zip?

@Titokhan Thanx for such a great work... Just some questions before trying.
Has anyone tried it with TWRP?? Or Fastboot???
Is it working on any yunique device?? have you tried it??

Testing it right now, need to backup my stuff then my stock rom then will proceed according to the steps above.
Wondering if that fastboot cmds need to do one by one or all at once copy paste? What does this mean "fastboot binary is on system's path" ?

Ish4 said:
@Titokhan Thanx for such a great work... Just some questions before trying.
Has anyone tried it with TWRP?? Or Fastboot???
Is it working on any yunique device?? have you tried it??
Click to expand...
Click to collapse
Sameer..plz provide reviews on cos 12.1
---------- Post added at 06:15 AM ---------- Previous post was at 06:12 AM ----------
tito...which .zip file to download for flashing yunique. as u said..."signed fastboot .zip" is complete os.... so does u
it means..signd zip which has lesser features than the first one. plzz help...which .zip file will be best for yunique..

Before installing cos mod 12.1:
Bugs:
1. Removing apps from Recents also kills background services of apps like WhatsApp, Hike, etc., which prevents notifications from being received until these apps are manually opened again.
2. User-installed apps like WhatsApp do not auto-start on boot. So no notifications are received until the app is opened manually.
3. Very often, the brightness of the display automatically changes to maximum even when auto-brightness is off. This can hurt the eyes when it happens while the phone is being used in a dark environment. Manually re-setting the brightness to low only leads to 'auto-max-brightness' happening again soon after. This seems to be caused by PowerManagerService or DisplayPowerManager.
4. Boot Animation doesn't play properly in many cases.
5. "Apps with usage access" feature in Security is reported to be not working.
6. Apps like True Caller, App Lock, etc. are not working, probably due to bug number 5.
7. UC Browser if storage is set to external sd card, the downloads will get failed in a sec or two.
8. Battery backup was too less even on wifi.
9. Camera sound cannot be disabled, not even by enabling "No Interruptions" ring mode.
10. While in a call half screen is coming with caller name and half is dialpad. There is no option to receive/reject the call... After finished I've to call back to the same no, with this same halfscreen problem...
11.Cannot set another browser as default browser, unless root the phone and uninstall stock browser.
Click to expand...
Click to collapse
So I was waiting eagerly for an update or cyanogen mod (I'm first time using it now). Then I read a thread on yu forum redirecting here for cos12.1. I have already unlocked bootloader on my device and proceeded further with the above steps. And ye I asked in my previous post about those cmds to be entered together at once or separately. It have to entered separately, though most of the above cmds took barely 1-30 secs but system.img took like 3 mins. I was really worried if it was stuck or something or bricked my phone. But the flashing completed in 1 hour.
Now feeling cool without any those above bugs, whatsapp works good and truecaller is already intregated into rom, which doesn't require us to download truecaller app.
Though a bit more work have to be done, like first booting twrp, then install supersu, then xposedframework then no watermark module.
Phone is running smooth and fast, no lags. So ye it got improved by getting cos.
Loving it <3

reyyhawn said:
Sameer..plz provide reviews on cos 12.1
---------- Post added at 06:15 AM ---------- Previous post was at 06:12 AM ----------
tito...which .zip file to download for flashing yunique. as u said..."signed fastboot .zip" is complete os.... so does u
it means..signd zip which has lesser features than the first one. plzz help...which .zip file will be best for yunique..
Click to expand...
Click to collapse
download the signed zip file and flash it using twrp.

reyyhawn said:
Sameer..plz provide reviews on cos 12.1
---------- Post added at 06:15 AM ---------- Previous post was at 06:12 AM ----------
tito...which .zip file to download for flashing yunique. as u said..."signed fastboot .zip" is complete os.... so does u
it means..signd zip which has lesser features than the first one. plzz help...which .zip file will be best for yunique..
Click to expand...
Click to collapse
Complete guide on how to install CM 12.1 jalebi on yu yunique
http ://forums.yuplaygod.com/index.php?posts/334046
To open d above link...pls delete d space between http and :

Thanks

Updated Install Guide
1. Download the signed zip from this site :-
Link
2 . Boot to twrp recovery. (Power + Volume Up)
. . Backup your system and data in recovery.
3 . Wipe system, data, cache, dalvic cache.
. Now click install from Sd-Card.
4 . Flash d CM 12.1 zip file. (704Mb)
Done! Enjoy
To remove d water mark:
1. Download xposed-v75-sdk22-arm and flash it through twrp.(download http://googleweblight.com/?lite_url...641716&sig=APONPFkCzLBdAagSe1AYeRNs9siZHaaPMA)
2. Install xposed installer 3.0 alpha.apk file(download http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440)
3. Download "no watermark for xposed" from playstore and activate it from xposed in d modules section.
4. Reboot
Done!
Bugs:-
This is an experimental build Few bugs are seen.
Random Reboot
Lag in Performance
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you like the guide and want to see more guides for Yunique Like our page <Link> and Subscribe on our YouTube Channel and Press Thanks :good:

does anyone got a working build of CM recovery for Yunique ??

Experiencing heavy lag!! Clash of clans is too much lagging. Sometimes get stuck.
Don't wanna goto stock rom. Please fix lags.

Can anyone please upload stock rom backup file, i have lost mine

Is there any link for fastboot images of stock ROM in case anything goes wrong?
P.S. - Fastboot only and not TWRP image.
Thanks.....

CyanogenMod 12.1 Nightly For Yu Yunique (Jalebi)
For Screenshots click below
https://www.facebook.com/techieguy95/posts/913397038714120

Related

Root 23.1.A.0.690 (UNLOCKED BOOTLOADER)

how i did it...
UNLOCKED BOOTLOADER ONLY
flashed 5.02 ftf
- flashed boot.img with recovery
- got into recovery and installed supersu.zip
- reboot to flashmode
- flashed with flashtool (excluded everything but kernel)
booted ok
supersu is working ok
root checker all green
{
"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"
}
Is root explorer can mount system as R/O for u?
lonely2k5 said:
how i did it...
flashed 5.02 ftf
- flashed boot.img with recovery
- got into recovery and installed supersu.zip
- reboot to flashmode
- flashed with flashtool (excluded everything but kernel)
booted ok
supersu is working ok
root checker all green
Click to expand...
Click to collapse
Is your bootloader unlocked?
lonely2k5 said:
how i did it...
flashed 5.02 ftf
- flashed boot.img with recovery
- got into recovery and installed supersu.zip
- reboot to flashmode
- flashed with flashtool (excluded everything but kernel)
booted ok
supersu is working ok
root checker all green
Click to expand...
Click to collapse
I dont get it , in last step you falshed what with flash tool ??? And in second step flash which boot.img with recovery ????
Sent from my D6503 using XDA Free mobile app
yes. bootloader unlocked
no. system dir not writable
second step: find some boot.img with recovery built in (doomlord)
would rooting kernel from 4.4.2 and continuing the guide work?
NVM =\
lonely2k5 said:
yes. bootloader unlocked
no. system dir not writable
second step: find some boot.img with recovery built in (doomlord)
Click to expand...
Click to collapse
Put it in you OP this is only for Unlocked boot loader if someone flashes doomloads boot.img on a locked boot loader they'll brick there devices
getting root on unlocked boot loader is easy but locked boot loaders the problem
For Loacked boot loaders : http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150
How do i flash the boot.img,
Jhon998 said:
How do i flash the boot.img,
Click to expand...
Click to collapse
You need a unlocked bootloader
Rajeev said:
You need a unlocked bootloader
Click to expand...
Click to collapse
Yes mine is
---------- Post added at 04:24 PM ---------- Previous post was at 04:24 PM ----------
when flashing boot.img mine show waiting for device, my device is connected in fastboot mode
---------- Post added at 05:22 PM ---------- Previous post was at 04:24 PM ----------
Never mind got it working
Without one adv stock kernel,I dont think we would have full root access.
jsscx said:
Without one adv stock kernel,I dont think we would have full root access.
Click to expand...
Click to collapse
what does "adv kernel" mean?
can confirm
Just did this, can confirm that this is working, UNLOCKED BOOTLOADER, OFC
I didnt flash the boot.img per recovery because i didnt knew how, its also working with fastboot:
Code:
fastboot flash boot boot.img
How can i root 5.0.2 with unlock bootloader, anyone help me step by step, i'm noob :crying::crying::crying:
i'm sorry for bad english
Weattseat said:
How can i root 5.0.2 with unlock bootloader, anyone help me step by step, i'm noob :crying::crying::crying:
i'm sorry for bad english
Click to expand...
Click to collapse
First you download the .690 FTF from this forum, there is a post about it.
Then you use flashtoool (there are several posts, just google, how to use it)
Then download fastboot(also just google it and download, you also find tutorials) and install it.
Then google for DooMLord boot.img and download it
Put it in the same folder as fastboot and use SHIFT-Right mouse click and open CMD and type this, while your phone is in fastboot mode (also google how to)
Code:
fastboot flash boot boot.img
Download SuperSU (also google is your friend) and put it on internal or external storage
Afterwards you boot your device, during the first few seconds hold the volume up key, a menu will pop up
You choose install zip(? not sure how it is called)
Navigate to the folder you put SuperSU and install it
Then you turn of your phone
You use flashtool again, choose the FTF you downloaded in step 1, and flash it again, BUT this time you exclude(little box on the right when you choose the ftf you want to flash) EVERYTHING except kernel
DONE! Happy root!
Maybe someone can find all the requiered stuff =)
phillipo6 said:
First you download the .690 FTF from this forum, there is a post about it.
Then you use flashtoool (there are several posts, just google, how to use it)
Then download fastboot(also just google it and download, you also find tutorials) and install it.
Then google for DooMLord boot.img and download it
Put it in the same folder as fastboot and use SHIFT-Right mouse click and open CMD and type this, while your phone is in fastboot mode (also google how to)
Code:
fastboot flash boot boot.img
Download SuperSU (also google is your friend) and put it on internal or external storage
Afterwards you boot your device, during the first few seconds hold the volume up key, a menu will pop up
You choose install zip(? not sure how it is called)
Navigate to the folder you put SuperSU and install it
Then you turn of your phone
You use flashtool again, choose the FTF you downloaded in step 1, and flash it again, BUT this time you exclude(little box on the right when you choose the ftf you want to flash) EVERYTHING except kernel
DONE! Happy root!
Maybe someone can find all the requiered stuff =)
Click to expand...
Click to collapse
I try everything but my phone can not start(auto rs when show sony xperia logo)
Weattseat said:
I try everything but my phone can not start(auto rs when show sony xperia logo)
Click to expand...
Click to collapse
First make sure the phone is booting when you have 5.0.2 installed
then flash boot.img, check if it is booting
flash supersu, check if it is booting
flash FTF Kernel, check if it is booting
and tell me where it doesnt boot anymore
phillipo6 said:
First make sure the phone is booting when you have 5.0.2 installed
then flash boot.img, check if it is booting
flash supersu, check if it is booting
flash FTF Kernel, check if it is booting
and tell me where it doesnt boot anymore
Click to expand...
Click to collapse
i will try again, anyway so many tks u
---------- Post added at 09:34 PM ---------- Previous post was at 09:12 PM ----------
@phillipo6:
it work, finally
Tks u again for everything
1 First you download the .690 FTF from this forum, there is a post about it. = and then?? download, but not flash?
2 Then you use flashtoool (there are several posts, just google, how to use it) = u mean flash now???
3 Then download fastboot(also just google it and download, you also find tutorials) and install it. = Do u mean fastboot drivers??
4 Then google for DooMLord boot.img and download it = any boot file can make it??????
I loose my mind, becouse people dont have strength to write good tutorial.. They get angry
when ask something abaut it... !!!!!!!!!!!!!!
---------- Post added at 02:01 ---------- Previous post was at 01:55 ----------
Can i use this boot.img whats inside of this = D6503_23.1.A.0.690_XZDRKernel2.8.3-RELEASE.flashable.zip
Do u mean fastboot drivers??
Question..!
[*]First you download the .690 FTF from this forum, there is a post about it.
[*]Then you use flashtoool (there are several posts, just google, how to use it)
[*]Then download fastboot(also just google it and download, you also find tutorials) and install it.
[*]Then google for DooMLord boot.img and download it
[*]Put it in the same folder as fastboot and use SHIFT-Right mouse click and open CMD and type this, while your phone is in fastboot mode (also google how to)
[*]
Code:
fastboot flash boot boot.img
[*]Download SuperSU (also google is your friend) and put it on internal or external storage
[*]Afterwards you boot your device, during the first few seconds hold the volume up key, a menu will pop up
[*]You choose install zip(? not sure how it is called)
[*]Navigate to the folder you put SuperSU and install it
[*]Then you turn of your phone
[*]You use flashtool again, choose the FTF you downloaded in step 1, and flash it again, BUT this time you exclude(little box on the right when you choose the ftf you want to flash) EVERYTHING except kernel
[*]DONE! Happy root!
[/LIST]
Maybe someone can find all the requiered stuff =)
my question is, if I am already root, just flash the kernel ...?

[Tutorial] How to root & install TWRP Recovery on Moto G XT1068 6.0 (Easiest way)

Hi everyone, i felt the need to come up with this because it is an absolute nightmare to root & install twrp recovery
on our MOTO G XT1068.
I already know that there are a tons & loads of tuts out there but those are way too complex & require reverting back to android lollipop or re-flashing the boot images & so on.
Code:
[CENTER]/*
* 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.
*/[/CENTER]
So without further ado, let's get started. :laugh:
Things you'll need:-
1. Kingroot.apk
2. Latest TWRP recovery image for titan.
3. Flashify.apk
So now that you've get hold of ALL the above mentioned three files, let's begin with the installation.It is an absolute necessity to have your bootloader unlocked prior to installation of these files.
1. Must enable usb debugging in developer options & afterwards install kingroot & it will come up with root now or try to root prompt just hit ok & let it do its thing it will take couple of minutes be sure to keep your wifi/data active at the time of doing this.
2. Now that you're successfully rooted, reboot your phone & install flashify, afterwards launch the app & the app itself will prompt for superuser access grant it & then hit install from zip file.
3. Locate the twrp-3.0.2-4-titan.img recovery image from the storage & hit ok, it will get installed.Afterwards go to fastboot mode By pressing power button & volume down button for about 5 seconds navigate to recovery mode & voila you're now rooted & now running the latest version of twrp recovery.
SCREENSHOTS
Note- This method should work on any variant of the MOTO G 2014, have tried the same on XT1069 & it worked flawlessly.
You can now install any custom rom of your liking through it, in my case i decided to flash the cosmic os & it automatically gave me root access with supersu, hope it helped.​
I personally don´t see the problem in flashing TWRP via fastboot command or maybe with flashify and less problem in flashing SuperSU-v2.79-201612051815.zip through this recovery.
And just my two cents: I would never let something like kingroot enter my device. <--- personal opinion.
I totally understand the concern but the thing is i myself tried flashing the recovery with fastboot but even after with all the success it never booted into recovery in the first place, so this method is for those who were all out of luck with the fastboot.And even i know this method is not reliable but it is only needed for flashing & booting into twrp recovery once the user enters the recovery any other rom or supersu can be flashed easily from the within.It's just a workaround for those who never gets to enter recovery even after having it successfully flashed via fastboot & yeah i had tried
Code:
fastboot boot recovery
It din't entered into recovery from there as well.
BlurStreak said:
I totally understand the concern but the thing is i myself tried flashing the recovery with fastboot but even after with all the success it never booted into recovery in the first place, so this method is for those who were all out of luck with the fastboot.And even i know this method is not reliable but it is only needed for flashing & booting into twrp recovery once the user enters the recovery any other rom or supersu can be flashed easily from the within.It's just a workaround for those who never gets to enter recovery even after having it successfully flashed via fastboot & yeah i had tried
Code:
fastboot boot recovery
It din't entered into recovery from there as well.
Click to expand...
Click to collapse
Ok,understand your aim and for the users who can´t root or flash TWRP the usual way this may be a last chance.
About the "fastboot boot" command: The last TWRP recovery that was able to boot into my device was 2.8.5.0. Later versions were only able to be flashed via fastboot,flashify or the Official TWRP app.
{
"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"
}
Download the second one from the link weighing 643.7mb from this link
Installation Method:
1. Download Firmware and Extract it to a folder
2. Download mfastboot v2 and Extract it into the same folder.
3. Reboot the phone into Bootloader
4. Run Following commands from the Command Prompt after cd-ing to the folder, one by one
1
Code:
mfastboot.exe oem lock begin
2
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
3
Code:
mfastboot.exe oem lock
4
Code:
mfastboot.exe reboot
Skip 1 & 3 if you don't want to lock the bootloader.
Wolfcity said:
I personally don´t see the problem in flashing TWRP via fastboot command or maybe with flashify and less problem in flashing SuperSU-v2.79-201612051815.zip through this recovery.
And just my two cents: I would never let something like kingroot enter my device. <--- personal opinion.
Click to expand...
Click to collapse
xcutionrstyle said:
Thanks!!! now the sim card is detected and it's working fine. But, please share how to root the phone. The king root method does not seem to work. Please share how to do it using the TWRP/SuperSU method. Also, Please help with the correct files. And last thing, can i use Nugget mod, & which mod would be the best for this phone?
Click to expand...
Click to collapse
If you can enter the twrp recovery just flash the supersu zip wolfcity mentioned and you should be good to go, as for the nougat mods go just download & flash the cosmic os rom from here, this rom has built in root access and is based out of aosp 7.1.1.The most fluid rom available for the device as of now with minimal customizations on top.Download & flash the rom using twrp & you should be good to go!
xcutionrstyle said:
Are Kingroot and purify good to keep on phone? Is it the same as other rooting techniques? I tried to run Kingroot again and i was successful in rooting the phone. when i checked in at root checker, it said the device is rooted. But i remembered wolfcity mentioning that he will never keep Kingroot in his phone, so i uninstalled it. Then i again checked in at root checker, it said root not properly installed.
Please suggest what is the best
Sorry, am quite new at rooting.
Click to expand...
Click to collapse
kingroot was there just as the last alternative when everything else refuses to work, if you've successfully rooted your phone with it just flash the given twrp image with flashify and download supersu.zip and then enter the twrp flash the supersu zip & you'll be good to go!
xcutionrstyle said:
i did exactly the same, but it's again going in the bootloader loop. Please help out.
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
I did exactly the same but stuck in bootloader loop again. Please help out.
Click to expand...
Click to collapse
Download this
, extract it on your pc.Boot your phone into fastboot mode now run the EasyInstaller.bat file while your phone is in the fastboot mode.Choose the first option flash stock rom & let it do its thing, afterwards try the original stated method in the post for rooting & it should work.Also make sure that you have all the latest drivers installed for your device you can easily install it via motorola device manager that is in the zip provided to download.
Boot into fastboot mode and unzip the root-titan-M-BR.zip onto the computer, click on Run.bat and let it do its thing, power on the phone.Copy the BETA-SuperSU-2.52.zip file to your phone memory and flash it through twrp recovery or flashify (Preferably through TWRP recovery).Alternatively, you could also flash any other custom rom through twrp which is pre-rooted like this one.
xcutionrstyle said:
Thanks for all that info.. Will first start with the nougat ROM. Please suggest where can I download the gapps from, which would be working with this OS. As there is no link provided in there.. Also suggest, if I download the nougat ROM, should I flash the file in TWRP? Also, if this ROM is having root access, does it mean, I can Uninstall KingRoot and can directly install SU app.
Sorry for all the trouble.
Click to expand...
Click to collapse
Yes you'll have to flash that rom file using the twrp recovery, custom roms cannot be flashed using fastboot mode or stock recovery, also download the gapps from here.And the rom i mentioned is having inbuilt root access and it will replace your current stock rom completely so you don't have to worry about uninstalling any app as this rom will replace everything.Just download that rom's zip file save it to your phone's memory then boot into twrp recovery & to flash that rom from there first swipe to allow modifications the very first time you boot into twrp recovery as i'm assuming you haven't booted into that recovery yet afterwards go to that wipe tab in that recovery and choose advanced wipe and tick dalvik, cache, data, system & then swipe to wipe afterwards go back & hit that install tab choose your zip don't check anything just swipe on confirm to flash & your rom will be flashed afterwards also flash the gapps after flashing the rom & after all of that is completed hit on reboot system & you'll be good to go!
And yeah don't be sorry we're all here to help each other it's all in the learning curve, welcome to xda
Edit: Also if you are rooted with the main kingroot method just remember this that you won't be able to boot into twrp recovery using that fastboot mode/bootloader screen what you can do is search for an app in playstore that allows you to reboot to recovery, some what like this app.Just install this app grant it root access & then reboot to recovery from there this way you'll able to enter the TWRP recovery easily without having the need to update your bootloader or something.
The gapps could possibly be issue here try using the mini gapps package from that link & do that rom flashing procedure from the twrp once again or if possible try without the gapps to see whether it boots or not.Also you could try without the sim inserted on the first boot after the flashing procedure has been done.The mini gapps package should do the trick anyways.Enter twrp once again wipe the data then flash the rom & mini gapps package once again, try without the sim and it should work.Also do remember that when you are not flashing other rom just go to wipe & swipe on wipe to factory reset do not ever advanced wipe if you are not planning on flashing any other rom as this will result in a bootloop & you won't be able to get to the twrp recovery if you advanced wipe the device and then boot it.
Hello brother, i have used the kingroot method to root. Root was successfull. But after rooting i tried to install twrp using flashing. But after rebooting it showed some error saying no changes where made. Now is there any other way to flash a recovery and installing SuperSU without using a pc.
ajithmc said:
Hello brother, i have used the kingroot method to root. Root was successfull. But after rooting i tried to install twrp using flashing. But after rebooting it showed some error saying no changes where made. Now is there any other way to flash a recovery and installing SuperSU without using a pc.
Click to expand...
Click to collapse
Try the official TWRP app to flash the recovery, just grant it root access select your device from the drop down list, download the image & flash it.
Hi man !
I have the same problem as someone in page 2 and 3.
I tried to root my Moto G 2014 XT1068 6.0, so I unlocked the bootloader (no problem)
Then I flashed the custom recovery TWRP 3.0.2 (no problem)
Then I tried to install SuperSU (2.46 I think).
And now im stuck on the "warning bootloader unlocked" message.
I can access to the fastboot (48.87 , not 48.86) mode and the recovery mode.
What should I do ? Thanks
lemonfalls said:
Hi man !
I have the same problem as someone in page 2 and 3.
I tried to root my Moto G 2014 XT1068 6.0, so I unlocked the bootloader (no problem)
Then I flashed the custom recovery TWRP 3.0.2 (no problem)
Then I tried to install SuperSU (2.46 I think).
And now im stuck on the "warning bootloader unlocked" message.
I can access to the fastboot (48.87 , not 48.86) mode and the recovery mode.
What should I do ? Thanks
Click to expand...
Click to collapse
When you've flashed the twrp recovery (btw why don't you use the last one?) boot into bootloader again and from there to recovery. That should make twrp stick to your device. If you boot directly to system the twrp will be overwritten by the stock recovery.
Sent from my Moto G 2014 using XDA Labs
Wolfcity said:
When you've flashed the twrp recovery (btw why don't you use the last one?) boot into bootloader again and from there to recovery. That should make twrp stick to your device. If you boot directly to system the twrp will be overwritten by the stock recovery.
Sent from my Moto G 2014 using XDA Labs
Click to expand...
Click to collapse
Hi thanks for the reply, but actually TWRP is working fine. :good:
My issue is that im stuck on the "warning bootloader unlocked"
xcutionrstyle said:
Hello... I have successfully loaded cosmic OS. But my Google Apps don't seem to work.. I tried the dynamic gapps and flashed it after I flashed cosmic OS.. All seems to work fine except the Google Apps.. Rest everything was fine.. But not being able to use keyboard too. And it really gets on ur nerves.. Please help out..
---------- Post added at 09:14 PM ---------- Previous post was at 09:09 PM ----------
Hi lemon falls, try #12, #16 of this thread suggested by BlurStreak and your problem would be solved..
Click to expand...
Click to collapse
Ok im trying
Edit : Thanks man my phone is booting
Edit 2 : It seems to be stuck on bootloop, it's been soon 10 minutes
Edit 3 : YEEEES it booted nevermind ! Time to root now
Try to do a clean flash of the rom once again wipe everything excluding internal storage & sd card, install the rom once again & it should be good.I am also rocking the same cosmic os along with the gapps i mentioned, no issues so far.This time after flashing both the rom & the gapps wipe the device e.g., after successfully flashing both the zips go to wipe & just swipe to do a factory reset do not do an advanced wipe.
That is kind of strange the ROM has an inbuilt SuperSU, anyways you could try flashing the zip provided.
BlurStreak said:
That is kind of strange the ROM has an inbuilt SuperSU, anyways you could try flashing the zip provided.
Click to expand...
Click to collapse
Maybe it's not activated in settings?
Sent from my Moto G 2014 using XDA Labs

[TUTORIAL][ZS550KL][ZS570KL/PRO] How to change device SKU to WW [29-09-2017]

Zenfone 3 Deluxe ZS550KL / ZS570KL / ZS570KL PRO
How to change device SKU to WW​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 procedures,
* tools or terms in this thread before proceeding! 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.
*/
The are two main reasons to change our SKU from TIM, CN or JP to WW. Firstly, the WW firmware is apparently getting OTA updates first. In second place, Marshmallow 6.0 Bootloader Unlock process requires 4.12.40.1698 firmware version and above, but only WW got the update (you may find this useless as 7.0 update is here, but some 6.0 users may need it). This will guide you in the process.
Warning!
Always have your original firmware, recovery and boot files in case things don't go as expected
Backup all of your personal data!
PLEASE MAKE SURE you are using the respective files for your CPU (ZS570KL SD820 2.15Ghz - ZS570KL PRO SD821 2.3GHz)
Prerequisites
Adb and Fastboot installed. I recommend you to install it from HERE.
Drivers installed. Try using these or Universal ADB Drivers
Python 2.X or 3.X installed.
WW target firmware. You can download it from the ASUS official website or from AndroidFileHost mirror: ZS570KL SD820 or ZS570KL PRO SD821.
Respective firmware stock recovery. You can download it from here: ZS570KL SD820 or ZS570KL PRO SD821
sdat2simg toolkit (you can find img2simg linux binary in second post).
Guide
In this case we are going to change a ZS570KL using the UL-Z016-WW-4.12.40.1698 firmware (the version needed to unlock the bootloader in Android 6.0) and it's respective recovery.
1. Extract the sdat2simg toolkit
Extract the sdat2simg_toolkit.rar and you will have this folder structure:
- sdat2simg_toolkit/
|-> bin / > necessary tools
|-> input/ > input system files
|-> output/ > output system files for flashing
|-> sdat2simg.bat > tool execution​2. Extract system files from firmware
Open the firmware zip and extract system.new.dat and system.transfer.list into the input folder.
{
"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"
}
​3. Run the tool
Now open the sdat2simg.bat file. There must no be trouble if you have properly installed python.
The tool will first convert the system.new.dat and system.transfer.list into a raw ext4 image, then it will be converted into a sparse flashable image.
When the process has finished, check the output folder. The system.img file is what we are interested in. This is our flashable system image.​4. Flash the WW system image
Now we need to reboot into bootloader mode. Turn off the device and press Volume up + Power button. Or by using adb command:
Code:
adb reboot bootloader
Now open a terminal inside output folder and flash the system image by using the fastboot command:
Code:
fastboot flash system system.img
5. Flash the WW recovery image
Then we are going to flash the WW recovery image. Open a terminal where you placed the recovery image and flash it by using fastboot command:
Code:
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
5.a. (Optional) Flash WW boot image
You can optionally flash the WW boot image contained inside the firmware zip. Extract it, open a terminal next to the boot.img file and flash it by using the fastboot command:
Code:
fastboot flash boot boot.img
(Not tested)​6. Factory reset
Reboot your device by using fastboot command:
Code:
fastboot reboot
Wait until it boots up and power it off. Then boot to recovery mode: Volume down + Power button, wait for the "No command" sign
and keep pressed power button + tap Volume up to show the recovery menu.
To factory reset the device choose the following options:
Code:
Wipe data/factory reset
Wipe cache partition
7. Reboot!
Now you are all up! You can Reboot your device by choosing the Reboot device now option
and you will boot into your new WW firmware. If you changed to WW to unlock the bootloader now you are able to do it.
You can also download OTA updates for WW firmware or you can manually download it and place the firmware in the internal storage, reboot and a window will prompt asking to install the new firmware.​
Special thanks
@xpirt
@A.S._id
Additional Information
Building...
Building...
Building...
Building...
Building...
i need ZS550KL CN -> WW :angel:
ken2006i said:
i need ZS550KL CN -> WW :angel:
Click to expand...
Click to collapse
Just follow the steps... I have uploaded CN firmware to AndroidFileHost. I have not been able to find CN stock recovery image... but you can make a dump of yours (and share it!).. Follow this guide https://forum.xda-developers.com/showthread.php?t=2450045
Help me, please! During flash recovery appear this message: FAILED (remote: partition flashing is not allowed
elenanole said:
Help me, please! During flash recovery appear this message: FAILED (remote: partition flashing is not allowed
Click to expand...
Click to collapse
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.
sebastiandg7 said:
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.
Click to expand...
Click to collapse
Yes I want to flash stock recovery but when I try to flash system image once it went well and then when I tried to flash recovery image it came a message partition is not allowed. Now appear partition is protected.
Please you can explain well what I have to do exsactly? Sorry for my english but I thank you for help me.
sebastiandg7 said:
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.
Click to expand...
Click to collapse
this is error
elenanole said:
View attachment 4266710 this is error
Click to expand...
Click to collapse
Show me the exact command you are using. You must do this:
1. Flash the system.img image in the system partiton.
Code:
fastboot flash system system.img
2. Reboot your device and wait until it boots up.
3. Reboot to fastboot mode.
4. Flash the stock recovery image to the recovery partition.
Code:
fastboot flash recovery <stock recoery name>.img
If you need more help you can find me in Telegram as @sebastiandg7
hello to all the guys, before proceeding to the flash, i want to make a backup of my (TIM) recovery because i do not find it. How can I do? Where was stock WW recovery taken?
P.S. My phone is not rooted
xtia87x said:
hello to all the guys, before proceeding to the flash, i want to make a backup of my (TIM) recovery because i do not find it. How can I do? Where was stock WW recovery taken?
P.S. My phone is not rooted
Click to expand...
Click to collapse
Are you able to boot twrp recovery? (Not installing it, check this thread)
sebastiandg7 said:
Are you able to boot twrp recovery? (Not installing it, check this thread)
Click to expand...
Click to collapse
Yes, I'm able to start twrp without installing it. From here how do I save my original recovery?
edit: Sorry I made a mistake i can't boot twrp without installing... The error: FAILED (remote: unlock device to use this command) is there a way to save the recovery without unlocking the bootloader?
Hi, I've been able to make the move finally! And when it gave me a mistake, partition is not allowed was why I had to do a factory reset and clean everything because it seemed to be insufficient memory. Sorry for my english and I hope that I help you
Some one have sotck recovery Z016D_CN please give me .tks
sebastiandg7 said:
Are you able to boot twrp recovery? (Not installing it, check this thread)
Click to expand...
Click to collapse
Do I need to flash the recovery and the firmware in one go? Is there any order I must proceed in? Are you sure I don't need to unlock the bootloader first? ASUS told me the bootloader unlock app also works with my TIM branded version.
---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------
Also, what do I do if I already have TIM firmware with Android 7? Can I still follow the steps in the tutorial, or how should I proceed? Can/must I downgrade to Android MM, and if yes how? Thanks in advance.
What about dat to img by stupdroid.com? Which is newer? Does it make a difference if i want to get oreo system image?
I tried both tools and dat to img by stupdroid makes a system image with 3,65 GB but sdat2simg 3,54 GB...

Help Me Unbrick My Mi A1!!

I bought the Mi A1 some weeks ago and it was working just fine. I flashed twrp, rooted and was happy with it until I found out that I could no longer install OTAs so I decided to flash the fastboot ROM, downloaded the lastest one from www.xiaomifirmware.com, attemted to flash it but couldn't. The MiFlashTool for some reason simply didn't have a flash option in it which it was supposed to have so uninstalled the flash tool and tried installing older versions of it but still no signs of the flash option, this got me frustrated and I was searching for other ways to flash the fastboot rom, I did found some and tried putting the rom in the minimal adb and fastboot tool, it did flash it but the slot a or b, i don't remember, was stuck on recovery mode, mean while i could boot from the another slot normally, I agan istalled twrp on the working slot(Idk why) and
the wifi was broken. I simply couldn't turn it on(the wifi). So I was back to flashing the fastboot rom and in the process I figured a way to find the flash option that was missing using the tab key on the keyboard but the flash itself didn't go very well, i got a modem_a error so I was back to other ways of flashing it and in the process the phone turned off and a Qualcomm driver began to install, it got installed and I was extremely happy that I could flash the rom with the MiFlashTool but after the flash completed and I got the sucess message, the phone got stuck on the bootlogo and rebooted normally in the next automatic reboot, I was greeted with the basic setup and I was happy but after 30-60 sec it got hung and the device started to repeat this process. I tried flash the older versions of the rom but still no luck. Can some one help me with this issue???
*************************************************************************
Video shocasicg the issue: https://www.youtube.com/watch?v=3YcWsWYQVGQ
This issue has been fixed, Try following these steps:
1) Unlock the bootloader.
2) Download Mi Flash Tool and install it. (For the drivers, skip it if you have installed the drivers already)
3) Download and Install minimal adb and fastboot , persist.img from august build link will be below.
4) Copy the persist.img to the where the minimal adb fastboot tool is located.
5) Goto the minimal adb fastboot tool folder where you had put the persist.img.
6) Open cmdhere.exe
7) Put your phone in fastboot mode (Volume - and Power)
8) Type the following commands:
- fastboot devices (you should something like this:
Fastboot dsad5454sfs, If not, re-install the the fastboot drivers correctly. )
- fastboot erase persist.img
- fastboot flash persist persist.img
Voila! Done but please note that you can just do it once and not repeatedly.
Adb and fastboot tool: https://forum.xda-developers.com/sho....php?t=2317790
i have the same issue look at the video
https://www.youtube.com/watch?v=3YcWsWYQVGQ
I don't know the specifics but you're going to have to go for a very basic low-level wipe and re-flash of the stock ROM from Xiaomi. Be *very* careful to get the correct ROM files and flashing tools. I'd head to the official Xiaomi EN (english) forums or ask here on XDA. I think the reason you haven't had more replies is because your post was a difficult to read wall of text.
If you're currently booting up but then it's rebooting on it's own - that's actually a good sign that you hopefully should be able to restore it to stock firmware and then go from there. Beyond that I can't help you but I'm sure someone else here can. Good luck! And if you figure it out make sure to come back and let us know how you fixed it in case anyone else has similar problems.
Just take it to service center they will do it.
info:
If you can flash anything using fastboot then do fastboot flash partition gpt_both0.bin and you'll enter edl mode and should be able to flash the FASTBOOT ROM through the mi flash tool if you have installed the drivers properly.
alsheron said:
I don't know the specifics but you're going to have to go for a very basic low-level wipe and re-flash of the stock ROM from Xiaomi. Be *very* careful to get the correct ROM files and flashing tools. I'd head to the official Xiaomi EN (english) forums or ask here on XDA. I think the reason you haven't had more replies is because your post was a difficult to read wall of text.
If you're currently booting up but then it's rebooting on it's own - that's actually a good sign that you hopefully should be able to restore it to stock firmware and then go from there. Beyond that I can't help you but I'm sure someone else here can. Good luck! And if you figure it out make sure to come back and let us know how you fixed it in case anyone else has similar problems.
Click to expand...
Click to collapse
So I did got it fixed and to a working state but my dissatisfaction led me to some more trouble and it's currently hard bricked or need to be flashed using a deep flash cable to be presice. Basically it's on its way to the service centre.
So how I fixed the issue?
1) Unlock the bootloader.
2) Download Mi Flash Tool and install it. (For the drivers, skip it if you have installed the drivers already)
3) Download and Install minimal adb and fastboot , official fastboot rom.
4) Extract the fastboot rom and copy the persist.img located in the Images folder of the fastboot ROM to the where the minimal adb fastboot tool is located.
5) Goto the minimal adb fastboot tool folder where you had put the persist.img.
6) Open cmdhere.exe
7) Put your phone in fastboot mode (Volume - and Power)
8) Type the following commands:
- fastboot devices (You should see something If not re-install the the fastboot drivers correctly. )
- fastboot erase persist.img
- fastboot flash persist persist.img
Voila! Done but please note that you cant just do it once and not repeatedly.
Links:
Adb and fastboot tool: https://forum.xda-developers.com/showthread.php?t=2317790
fastboot rom: http://bigota.d.miui.com/7.11.18/tissot_images_7.11.18_20171117.0000.00_7.1_3ac9b1f856.tgz
headshotde said:
i have the same issue look at the video
https://www.youtube.com/watch?v=3YcWsWYQVGQ
Click to expand...
Click to collapse
Look up ^^^^^
{
"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"
}
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
I am unable to erase or flash persisti.img on my Mi A1
khkalam said:
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
I am unable to erase or flash persisti.img on my Mi A1
Click to expand...
Click to collapse
The same hapend to me... Please how can i fix it!
khkalam said:
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
I am unable to erase or flash persisti.img on my Mi A1
Click to expand...
Click to collapse
Why tiffany? Mi A1's code name is tissot, Mi 5x's codename is tiffany.
I have both device, Mi 5x and Mi A1
NicoNewbie said:
Why tiffany? Mi A1's code name is tissot, Mi 5x's codename is tiffany.
Click to expand...
Click to collapse
I have Mi 5x and Mi A1. Tried this method and fail to flash. Also I am using A1 ported rom on my Mi 5x.
Thanks
khkalam said:
---------- Post added at 03:15 PM ---------- Previous post was at 03:12 PM ----------
I am unable to erase or flash persisti.img on my Mi A1
Click to expand...
Click to collapse
Why don't you just use the batch file already provided in the stock image folder? Install adb fastboot system wide drivers. Connect your phone to pc in fastboot mode. And just run the batch file in tissot_images folder (I prefer flash_all_except_storage.bat)
Please just have a look at this thread: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
It includes a guide and already a lot of answered questions.
solution
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
here's how to flash persist
N.B YOU NEED TO DOWNLOAD THE FILE FROM THE GUIDE (32 mb Iin size)
Edwin Hamal said:
I bought the Mi A1 some weeks ago and it was working just fine. I flashed twrp, rooted and was happy with it until I found out that I could no longer install OTAs so I decided to flash the fastboot ROM, downloaded the lastest one from www.xiaomifirmware.com, attemted to flash it but couldn't. The MiFlashTool for some reason simply didn't have a flash option in it which it was supposed to have so uninstalled the flash tool and tried installing older versions of it but still no signs of the flash option, this got me frustrated and I was searching for other ways to flash the fastboot rom, I did found some and tried putting the rom in the minimal adb and fastboot tool, it did flash it but the slot a or b, i don't remember, was stuck on recovery mode, mean while i could boot from the another slot normally, I agan istalled twrp on the working slot(Idk why) and
the wifi was broken. I simply couldn't turn it on(the wifi). So I was back to flashing the fastboot rom and in the process I figured a way to find the flash option that was missing using the tab key on the keyboard but the flash itself didn't go very well, i got a modem_a error so I was back to other ways of flashing it and in the process the phone turned off and a Qualcomm driver began to install, it got installed and I was extremely happy that I could flash the rom with the MiFlashTool but after the flash completed and I got the sucess message, the phone got stuck on the bootlogo and rebooted normally in the next automatic reboot, I was greeted with the basic setup and I was happy but after 30-60 sec it got hung and the device started to repeat this process. I tried flash the older versions of the rom but still no luck. Can some one help me with this issue???
*************************************************************************
Video shocasicg the issue: https://www.youtube.com/watch?v=3YcWsWYQVGQ
This issue has been fixed, Try following these steps:
1) Unlock the bootloader.
2) Download Mi Flash Tool and install it. (For the drivers, skip it if you have installed the drivers already)
3) Download and Install minimal adb and fastboot , persist.img from august build link will be below.
4) Copy the persist.img to the where the minimal adb fastboot tool is located.
5) Goto the minimal adb fastboot tool folder where you had put the persist.img.
6) Open cmdhere.exe
7) Put your phone in fastboot mode (Volume - and Power)
8) Type the following commands:
- fastboot devices (you should something like this:
Fastboot dsad5454sfs, If not, re-install the the fastboot drivers correctly. )
- fastboot erase persist.img
- fastboot flash persist persist.img
Voila! Done but please note that you can just do it once and not repeatedly.
Adb and fastboot tool: https://forum.xda-developers.com/sho....php?t=2317790
Click to expand...
Click to collapse
hey mate i'm getting "image not allowed to download" error
how to fix this ?
neither do i see Fastboot dsad5454sfs
i see my device's no like 193a22 in CMD
can you help ?
i have 7.12.7 build can i still flash the persist that u have shared or do i need to extract it from 7.12.7 build?
anybody manage to solve the problem stuck at Android One logo ?
For MI5x with ported A1 rom

Xz2p on gsi 11-12 android

Hello everyone! The camera works on courvus 12L. and cr droid 12L but the battery is big on it. on the courvus 12L the battery is normal.
install twrp and boot into the stock firmware and then boot into twrp again. install the firmware from under twrp as a system image.
enCorvus_vS1.0-Revolt-treble_arm64_ab_vndklite-Gapps-Alpha-0000.img.rar
drive.google.com
this collected all the necessary patches for magisk
patchi.rar
drive.google.com
after installing the firmware, you can flash this recovery.this is recovery-extract the folder from the archive and flash it via fastboot by clicking on the bat file-"1lineage 18.1 recowery.cmd"
lineage 18.1 recowery.rar
drive.google.com
and to run the firmware, be sure to flash it from under recovery
Permissiver_v5.zip
drive.google.com
Sony gallery,fotoredactor sony
Kasper666666 said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Hello kasper666666, that`s what I am looking for! It sounds like a fairy tail!
But.....
my knowledge about AOSP and Magisk is poor and even my trial to install magisk for my H8166 was not successfull.
I started from stock rom H8166_Customized DACHBLX_52.1.A.3.49-R6C and Magisk-v24.3 (or alternatively Magisk-v21.4).
Then I flashed system-squeak-arm64-ab-vndklite-gapps.img.
Error: "non supported Magisk-version"
Can you give any advice?
Thanks for your efforts!
I made a mistake. the camera works on firmware courvus 12 v 1.0.magisk does not work because you need to remove system / bin / phh su, and in build.prop in ro.build.fingerprint = you need to insert your own values, the camera also works on cr droid 12 but on it Big battery zhor with gapps.. https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Alpha/20220315/ and be sure to flash it for the sensors to work https://drive.google.com/file/d/1-4cIIg8BNz1o1SlHEqamFKIprYcx9oOX/view?usp=drivesdk
der.lange said:
Can you give any advice?
Thanks for your efforts!
Click to expand...
Click to collapse
if you can’t do this, I will help you, only I will need your build.prop from vendor

			
				
Thank you for your quick response and offer!
My last trial was insatalling "magfisk-phh.apk"; but stuck with Sony-logo.
it was not necessary .... I have a ready-made file, now I will upload it to disk and send a link to the finished firmware
put the usual magisk 24.3. install twrp and boot into the stock firmware and then boot into twrp again. install the firmware from under twrp as a system image
then you can put recovery lineage and it will work
lineage-18.1-20220113-recovery-aurora.img
drive.google.com
put all the files in the topic header
sorry, but I can´t see any attachment....
bytheway: will your solution enable the use of the stock xperia camera? As far as I know Bionic does not allow the use of their cameradrivers for the further development.
all attachments open. camera tama 0.3.0 from denny trank works it is in patchi.rar
it´s a hard piece of work for me and an end not to be seen...
1. flash stock with newflasher: ok
2. flash magisk_patched boot.img: ok
3. install twrp
3.1 fastboot boot twrp-kang.img; adb push twrp-kang.img /; install recovery ramdisk; reboot into recovery (with decryption); reboot system doesn´t work, boots into recovery instead!! Flashing system-squeak.img immediately stops with error.
3.2 fastboot boot twrp-aurora.img; boots but no input possible, dead screen
So what I`m doing wrong? Is there another better twrp?
download the archive. extract the twrp-akari.img file, copy it to the memory card. you must have the official firmware, connect the phone to the computer in fastboot and in the folder that you downloaded, click first on 1vbmeta.cmd then on 2twrp.cmd and wait until the phone reboots into twrp. in twrp select advanced then install recowery ramdisk and select the file on the memory card twrp-akari.img and wait for the firmware to finish. then reboot into the system. you can go to twrp and flash the firmware from twrp in system image. flash recovery lineage 18 on fastboot...magisk flash from under recovery lineage 18
xz2p dual TWRP 3.4.0.rar
drive.google.com
sorry, where can I find vbmeta.cmd and twrp.cmd?
xz2p dual TWRP 3.4.0.rar
drive.google.com
sorry
still no end to be seen!
1. install stockrom (newflasher)
2. boot and install ramdisk recovery (twrp-akari.img)
3. flash system.img via recovery or fastboot flash system_a system.img
4. reboot system: SONY-Logo stuck
what´s wrong with me?
2. boot and install ramdisk recovery (twrp-akari.img)!system reboot required!!3. flash system.img via recovery!! no fastboot!!!!4.flash Permissiver_v5.zip..5.reboot system
That´s exactly what I have done. Permissive-zip: too large; aborted....
I think, there´s not enough room for both twrp and permissive in the ramdisk and I dont know howto increase size. If I change the sequence of the installation twrp-img is too large.
"new image larger than boot partition. Aborting"
did you flash it from twrp.? flash recovery lineage 18 and flash permissiver from it
"It′s been a hard day's night
And I′ve been working like a dog" (Beatles)
Finally successfull!
I highly appreciate your work! Thank You!!
My steps installing android 12
1. install stockrom H8166_Customized DACHBLX_52.1.A.3.49-R6C (newflasher)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2. boot and install ramdisk recovery (twrp-akari.img)
3. reboot recovery ; reboot system ; reboot recovery again
4. push system.img /sdcard and install
5. replace ramdisk recovery with lineage-18.1-20220113-recovery-aurora.img
6. flash Permissiver_v5.zip from it
7. flash Magisk-v24.3.zip
8. reboot system
9. install camera-0.3.0-tama.zip from patchi.rar via magisk
the original SONY Xperia camera is working!!

Categories

Resources