Database Develop

[ROM][4.4.4][CM11][ARM][x32][Yureka ROM Odexed & De-Odexed]

DO NOT INSTALL THIS IF YOU HAVE UPGRADED TO THE LOLLIPOP BUILD. FOR 32 BIT RECOVERY ONLY.
YU Yureka Official Cyanogen OS Odexed & De-Odexed​
This is the official untouched YU Yureka ROM zip which can be installed from custom recoveries say CWM, TWRP, Philz etc…
Installing ROM from recovery is simpler than installing firmware from fastboot (but if you soft-bricked your phone, flashing firmware may save it yeah but don't flash kk fastboot images in lolliopop fastboot as itl hard brick the device).
Odexed vs De-Odexed?
Odexed firmware is faster and more secure, but a deodexed one gives more modification to freedom, and is the only way possible to change the look and feel of system apks (theming). In actual terms, deodexed ROMs are only slower in the first ever boot, after which they are the same speed as the former ones. Also, deodex doesn’t entail any serious security risks to your device either, and you can be rest assured that the millions of users opting for these aren’t suffering (including me).
Downloads:
Odexed ROM: (DEFAULT)
Yureka_Original_ROM_Odexed
MD5: 7D3BF824F4A0D28DD578084F132DDFD8
De-Odexed ROM:
Yureka_Original_ROM_De-Odexed
It has few Force Close's. I recommend Odexed ROM.
MD5: AE73E1D0C6353E65CD9FBDB103E8631D
How To Install:
i) Place the ROM zip in the device.
ii) Reboot to your Custom Recovery CWM/TWRP/Philz.
iii) Wipe Cache, Data and System.
iv) Install the ROM Zip .
v) No need to flash Gapps, Gapps already present in system by default.
vi) The system is unrooted as its unmodified, so you might wanna install SuperSU for root access. Download and intall SuperSU.
LINK: SuperSU
vii) Reboot.
FOR OTA Updates:
Download fast-boot tools.
Link: FastBoot Tools.
Download Stock Recovey.
Link: recovery-stock.img
Extract fastboot tools and place the stock recovery in it.
Power off your yureka phone.
Hold Volume Up and connect data cable to your computer.
Your device will be in fastboot mode.
In the fastboot folder in your computer, hold shift and right click.
Click on "Open Command Window here".
Type
fastboot -i 0x1ebf flash recovery recovery-s.img
Click to expand...
Click to collapse
[OPTIONAL]To re-lock your boot loader:
fastboot -i 0x1ebf oem lock
Click to expand...
Click to collapse
The process will finish within 5 seconds.
Disconnect USB and power on your yureka.
Your device is now ready to receive OTA updates!
SOURCE:
Device
Kernel
DISCLAIMER: I'm not held responsible if somehow something bad happens to your device. I've tested the ROM in my YUREKA/AO5510/tomato and it works.
XDA:DevDB Information
Yureka Official ROM Odexed & De-Odexed, ROM for the YU Yureka
Contributors
Shivam Kumar Jha
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader, Custom Recovery say CWM, TWRP, Philz etc.
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: Odexed
Stable Release Date: 2015-02-28
Created 2015-02-28
Last Updated 2015-02-28

Screenshots:

Reserved

bro how to flash this properly....
i mean step by step

Good work...

The play store keeps crashing no matter what

sharan565 said:
bro how to flash this properly....
i mean step by step
Click to expand...
Click to collapse
Download the ROM odexed / de-odexed..
Copy it to your device i.e., yureka..
If u dont have a custom recovery like CWM/ Philz/ TWRP flash one.. (see instructions on there respective page)..
reboot to recovery.. ( Enable developer options and enable advanced reboot menu)
now go to wipe menu., select clean to install a new ROM .. (cache, data, system, .android should be wiped)
now select install zip..
there select the ROM you downloaded odexed/ deodexed..
Iqbal641 said:
Good work...
Click to expand...
Click to collapse
sohny said:
The play store keeps crashing no matter what
Click to expand...
Click to collapse
Did you flash Gapp's after installing the ROM??
I'm using the de-odexed one and i never observed any kind of FC's in playstore app..

Shivam Kumar Jha said:
Download the ROM odexed / de-odexed..
Copy it to your device i.e., yureka..
If u dont have a custom recovery like CWM/ Philz/ TWRP flash one.. (see instructions on there respective page)..
reboot to recovery.. ( Enable developer options and enable advanced reboot menu)
now go to wipe menu., select clean to install a new ROM .. (cache, data, system, .android should be wiped)
now select install zip..
im with cwm recovery first wipe factory reset then wipe cache then we have to format system or not
i was installed other roms only i wiped factory reset and installed rom it worked i didnt wiped cache and system
Click to expand...
Click to collapse

A weird question
Will i get official OTA after installing this?? as this is stock...

sharan565 said:
Shivam Kumar Jha said:
Download the ROM odexed / de-odexed..
Copy it to your device i.e., yureka..
If u dont have a custom recovery like CWM/ Philz/ TWRP flash one.. (see instructions on there respective page)..
reboot to recovery.. ( Enable developer options and enable advanced reboot menu)
now go to wipe menu., select clean to install a new ROM .. (cache, data, system, .android should be wiped)
now select install zip..
im with cwm recovery first wipe factory reset then wipe cache then we have to format system or not
i was installed other roms only i wiped factory reset and installed rom it worked i didnt wiped cache and system
Click to expand...
Click to collapse
The updater-script has a command to mount and then format system..
so doing just factory reset is totally fine...
sanjeev7 said:
Will i get official OTA after installing this?? as this is stock...
Click to expand...
Click to collapse
Yes you will..
just make sure the update recovery while OTA is enabled in developer options (by default it is)..
or manually install the stock recovery
Click to expand...
Click to collapse

Shivam Kumar Jha said:
Did you flash Gapp's after installing the ROM??
I'm using the de-odexed one and i never observed any kind of FC's in playstore app..
Click to expand...
Click to collapse
NO I did not flash gapps
I am using the de-odexed rom and playstore was already present, should i flash gapps?

sohny said:
NO I did not flash gapps
I am using the de-odexed rom and playstore was already present, should i flash gapps?
Click to expand...
Click to collapse
Doesnt matter wont work

sanjeev7 said:
Will i get official OTA after installing this?? as this is stock...
Click to expand...
Click to collapse
I guess you will get OTA update but not able to install as the recovery should be stock to install the OTA update

Is this modified?
I mean to ask is this rom modified from stock? if yes are few bugs solved like the headset bug? Atleast a single bug solved would be great, any ways good work dude

sohny said:
Doesnt matter wont work
Click to expand...
Click to collapse
try flashing CM11 gapps..
sanjeev7 said:
Will i get official OTA after installing this?? as this is stock...
Click to expand...
Click to collapse
AndroTech said:
I guess you will get OTA update but not able to install as the recovery should be stock to install the OTA update
Click to expand...
Click to collapse
Exactly..
FOR OTA Updates:
Download fast-boot tools.
Link: FastBoot Tools.
Download Stock Recovey.
Link: recovery-stock.img
Extract fastboot tools and place the stock recovery in it.
Power off your yureka phone.
Hold Volume Up and connect data cable to your computer.
Your device will be in fastboot mode.
In the fastboot folder in your computer, hold shift and right click.
Click on "Open Command Window here".
Type
fastboot -i 0x1ebf flash recovery recovery-s.img
Click to expand...
Click to collapse
[OPTIONAL]To re-lock your boot loader:
fastboot -i 0x1ebf oem lock
Click to expand...
Click to collapse
The process will finish within 5 seconds.
Disconnect USB and power on your yureka.
Your device is now ready to receive OTA updates!
nikhilchandhra said:
I mean to ask is this rom modified from stock? if yes are few bugs solved like the headset bug? Atleast a single bug solved would be great, any ways good work dude
Click to expand...
Click to collapse
Nope its not at all modified..
I''l prepare a custom one using the deodexed ROM as base like this one Link
Which headset bug?? tell me more about this as i did'nt face any headset issue, just one minor issue in AudioFX app..

Headset Bug
Shivam Kumar Jha said:
try flashing CM11 gapps..
Exactly..
FOR OTA Updates:
Download fast-boot tools.
Link: FastBoot Tools.
Download Stock Recovey.
Link: recovery-stock.img
Extract fastboot tools and place the stock recovery in it.
Power off your yureka phone.
Hold Volume Up and connect data cable to your computer.
Your device will be in fastboot mode.
In the fastboot folder in your computer, hold shift and right click.
Click on "Open Command Window here".
Type
[OPTIONAL]To re-lock your boot loader:
The process will finish within 5 seconds.
Disconnect USB and power on your yureka.
Your device is now ready to receive OTA updates!
Nope its not at all modified..
I''l prepare a custom one using the deodexed ROM as base like this one Link
Which headset bug?? tell me more about this as i did'nt face any headset issue, just one minor issue in AudioFX app..
Click to expand...
Click to collapse
The headset bug which some times irritates me to the peaks, the audio routing isnt perfect in stock, i.e even after connecting a headset the sound comes from the speaker and it can be only solved by restarting the mobile. Even though it detects the headset, when i remove the headset the audio will be still routed to headset, i.e no sound from speaker. Again a restart is needed to solve this problem. Is this problem solved? and no headset icon on connecting a headset, any way i use a third party app for that. Is this issue solved in this rom? Do say it.
---------- Post added at 11:56 AM ---------- Previous post was at 11:36 AM ----------
Could some one give me the link of the gapps for odexed rom? Thanq

sanjeev7 said:
Will i get official OTA after installing this??...
Click to expand...
Click to collapse
Shivam Kumar Jha said:
.....Your device is now ready to receive OTA updates!....
Click to expand...
Click to collapse
even if we're running stock de-odexed rom? or do we have to get back on odexed rom?
Shivam Kumar Jha said:
....I''l prepare a custom one using the deodexed ROM as base...
Click to expand...
Click to collapse
please do. and, try and keep it as slim as possible.
i'm sure there are folks who don't use much of g00gle stuff anyway.

problem in deodexed rom
As sohny mentioned in deodexed rom I'm getting messages that playstore, themes and cm account are stopped working. Flashing gapps didnt solved it.

problems in de-odexed
gokuss1234 said:
As sohny mentioned in deodexed rom I'm getting messages that playstore, themes and cm account are stopped working. Flashing gapps didnt solved it.
Click to expand...
Click to collapse
I'm facing the same problems.
get messages that services have stopped working.
Also play store force closes everytime.
Please find a fix for this.

dalvi.nishant9 said:
I'm facing the same problems.
get messages that services have stopped working.
Also play store force closes everytime.
Please find a fix for this.
Click to expand...
Click to collapse
yeah i checked as it wasnt deodexed properly..
cant help this one now as im lollipop now .. cant revert back to x32 kitkat..
y dont u guyz update to lollipop as well?? make d most of ur hardware with x64 lollipop

[Recovery](KENZO)TWRP-COFFACE (3.0.0) No patched boot.img required to flash MIUI roms

Hi All,
You guys must be thinking why i'm sharing this recovery when we already have Official TWRP Recovery
actually this Recovery is Lil bit modified (One of my friend Found it somewhere)
via this Recovery you guys will able to Flash any MIUI Rom without Modifying/Patching Boot.img (I tested it my self)(i flashed miui global stable 7.2.3 and global dev 6.4.28)no patched boot.img required
Note:- I'm Not responsible for any kind Of damage caused to your device
Orignal Link => https://drive.google.com/file/d/0B6zD6Bewl4FmQVJGVVBOdzRmT2M/view
Password to the zip :- www.cofface.com
Instructions to flash
download the zip file (link provided)
extract The TWRP recovery.img (password given)
and flash it via flashify or Fastboot
Fastboot Command "Fastboot flash recovery "image-name.img"
yoo done
BUG:- Its not a major bug its not even a bug(i'm just considering it as a bug) but kinda annoying once you flash this recovery this recovery will change your device name from KENZO to CM_KENZO(this not gonna affect anything) but if you will try flash AOSP v4 or anyother AOSP build that verifies the Product name will give some errors
that "This build is for kenzo devices not for Cm_kenzo device"
Solution :- Open the zip in winrar and edit the updater script just change the Kenzo word with CM_Kenzo and it will work (alot of work to do right)
Another solution (this one is better i guess)
when ever you wanna flash MIUi official firmware flash this reocvery via Flashify.
flash the miui rom...
boot it up again flash the official TWRP recovery(so that you will able to flash other roms)
WARNING:- Dont flash miui rom via official TWRP recovery it will not boot untill you flash the Modify boot.img
Update
Bug fixed ===> "This build is for kenzo devices not for Cm_kenzo device"==>No Error now
Link(bug fixed) => https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Credits
Developer :- Cofface
Source :- http://www.miui.com/thread-3941604-1-1.html (orignal thread)
Special Thanks to @Rajdip for solving the bug
pls hit thanks if you guys found it helpful

what about the emmc_appsboot file ? should be remove from official rom ?

What is the zip password?? Can you share some screen shot

Anands3 said:
What is the zip password?? Can you share some screen shot
Click to expand...
Click to collapse
read my post zip password is already provided

wawan20 said:
what about the emmc_appsboot file ? should be remove from official rom ?
Click to expand...
Click to collapse
if your device is unlocked officially then No need to remove EMMC_appsboot file
but if your device is unlocked unofficially then yeah you have to dlt that file otherwise it will relock

Please add credits and source links

Rajdip said:
Please add credits and source links
Click to expand...
Click to collapse
I should have added the credit and sources link
But the thing is Idk who developed this recovery.
one of my friend provided me the link and he just found it randomly
i have only this info

Ashish0077 said:
I should have added the credit and sources link
But the thing is Idk who developed this recovery.
one of my friend provided me the link and he just found it randomly
i have only this info
Click to expand...
Click to collapse
Here's the source http://www.miui.com/thread-3941604-1-1.html
and those who are wondering, It works I tested.
---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------
Okay I edited cafface TWRP, no more "This build is for kenzo devices not for Cm_kenzo device" error here it is https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk

Rajdip said:
Here's the source http://www.miui.com/thread-3941604-1-1.html
and those who are wondering, It works I tested.
---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------
Okay I edited cafface TWRP, no more "This build is for kenzo devices not for Cm_kenzo device" error here it is https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Click to expand...
Click to collapse
Thanx Alot Bro.....and dude its "COFFACE" not "Cafface" and did you tested your build?? if yes i will add your link in the post and will give you credits
Credits Gives

Ashish0077 said:
Thanx Alot Bro.....and dude its "COFFACE" not "Cafface" and did you tested your build?? if yes i will add your link in the post and will give you credits
Credits Gives
Click to expand...
Click to collapse
Yeah I tested my build.. thanks

will this fix the unofficial bootloader unlock hard brick scenario? since now the phone should boot even if the bootloader gets relocked

Nice work, i will test it. Thx.
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka

Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!

Immortal68 said:
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Click to expand...
Click to collapse
The first prompt that appears is whether you would like to make TWRP modify system files or keep it read only. In simple words, if you swiping to the right Mi recovery wont replace TWRP when MIUI roms are flashed. If anyone didnt swipe right on the first prompt, just goto mount and unselect the read-only option.

Rajdip said:
The first prompt that appears is whether you would like to make TWRP modify system files or keep it read only. In simple words, if you swiping to the right Mi recovery wont replace TWRP when MIUI roms are flashed. If anyone didnt swipe right on the first prompt, just goto mount and unselect the read-only option.
Click to expand...
Click to collapse
Nice to know. TWRP asked the same thing (again apparently) when I rebooted from menu to system. It also provided the option to install SuperSU (or rather install the SuperSU Installer - whatever that was worth). I'm confirmed rooted now and recovery is still TWRP after many reboots. :good:

But is 3.0.0.0
I don't understand that

meangreenie said:
will this fix the unofficial bootloader unlock hard brick scenario? since now the phone should boot even if the bootloader gets relocked
Click to expand...
Click to collapse
No it will not fix that.... actually the thing Is When we unlock Bootloader with Official method it will not get relock while flashing any rom(via recovery)(miflash can still do that) in unofficial Method we replaces the emmc file with the modified one(and when we flash any official rom this file get replaced as this one is modified and (update. Zip/miuirom.zip) does not verify that emmc and relocks the boot loader....
What This recovery does is...
Miui roms inculde some recovery verification On The first boot
Which means it will replace twrp with the stock miui recovery which will cause bootloop...
For this we need to flash the patched/modified boot.img
But This recovery is Lil modified (it auto patches the boot.img and and our recovery does not get replaced and yoo thats how this recovery successfully flashes miui without a patched boot.img

Immortal68 said:
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Click to expand...
Click to collapse
Mine was in english Only on first Boot too?? But yeah i didnt use fastboot to flash was not in mood to turn on my pc.... I flashed it vai flashify and it the recoverg was in english by default and ymyou can flash it via twrp itself..
Anyways Thnx For Reporting This and giving solution

jujusito said:
But is 3.0.0.0
I don't understand that
Click to expand...
Click to collapse
Does that really matter?? Actually i dint face any problem with this recovery and atleast we can flash Miui roms without patching Boot?? And what you dont uderstand??
Its just an old version of twrp as iwas unablefound any updated one
As soon as i get it i will update here...

can I flash this recovery in current TWRP?
Sent from my kenzo using Tapatalk

Permanent Blu Vivo XL IMEI Fix for MM

ISN'T NECESSARY MTK DROID TOOLS OR OTHER MTK TOOLS , JUST MTK ENGINEER MODE IN LP FIRMWARE
This way it’s permanent just if you don’t wipe nvram & nvdata partitions and work only on who have LP and MM Firmware + TWRP Recovery for LP Firmware
Disclaimer : I'm not responsable for any damage on your device , use my tutorial step by step and will result a success!
Click to expand...
Click to collapse
Go back to LP Firmware [trought SP FLash Tools],
Restore IMEI with MTK Engineer Mode,
Flash TWRP,
Wipe cache,
Backup nvram,
Restore backup of nvram,
Install stock recovery,
Wipe cache,
Update again to MM using OTA
After MM is booted up ,
You will see IMEI,
Reboot to Recovery [Stock]
Wipe cache,
Install TWRP 2.8.7-N (Download)
[Trought SP FLash Tools]
To install TWRP with success , after TWRP is flashed just reboot to recovery first!
If you reboot first to system , will replace twrp with stock recovery , and entrie operation need to repeat [ from installing twrp ]
READY , NOW YOU HAVE PERMANENT FIX IMEI FOR ALL DEVICES [MTK] WHICH HAVE LP & MM FIRMWARE + TWRP ON BOTH VERSIONS
IF YOU WILL DO FACTORY RESET , IMEI WILL BE STILL HERE , NO ERASE , 100% TESTED

IacobIonut-DW said:
ISN'T NECESSARY MTK DROID TOOLS OR OTHER MTK TOOLS , JUST MTK ENGINEER MODE IN LP FIRMWARE
This way it’s permanent just if you don’t wipe nvram & nvdata partitions and work only on who have LP and MM Firmware + TWRP Recovery for LP Firmware
Go back to LP Firmware [trought SP FLash Tools],
Restore IMEI with MTK Engineer Mode,
Flash TWRP,
Wipe cache,
Backup nvram,
Restore backup of nvram,
Install stock recovery,
Wipe cache,
Update again to MM using OTA
After MM is booted up ,
You will see IMEI,
Reboot to Recovery [Stock]
Wipe cache,
Install TWRP 2.8.7-N (Download)
[Trought SP FLash Tools]
To install TWRP with success , after TWRP is flashed just reboot to recovery first!
If you reboot first to system , will replace twrp with stock recovery , and entrie operation need to repeat [ from installing twrp ]
READY , NOW YOU HAVE PERMANENT FIX IMEI FOR ALL DEVICES [MTK] WHICH HAVE LP & MM FIRMWARE + TWRP ON BOTH VERSIONS
IF YOU WILL DO FACTORY RESET , IMEI WILL BE STILL HERE , NO ERASE , 100% TESTED
Click to expand...
Click to collapse
Thanks for your effort IacobIonut-DW, and it works great, but only if you decide to use Blu's Stock Marshmallow ROM.
The bad news is that the problem is still present if one goes beyond stock and try to install any other custom ROM like AEX or Resurrection Remix ROMs.
I think that most people here want to skip using the stock (while rooted) ROM and experiment with other ROMs like AEX and RR.
Any pointers would be welcomed!
In the meantime, I am on MM Stock, Rooted and debloated.

Try to use SPlus LP and MM Firmware

IacobIonut-DW said:
Try to use SPlus LP and MM Firmware
Click to expand...
Click to collapse
Thanks but I don't quite understand.
After that, will I be able to install RR or AEX?

Rayan said:
Thanks but I don't quite understand.
After that, will I be able to install RR or AEX?
Click to expand...
Click to collapse
yes
Do same operation but with S Plus Firmware

IacobIonut-DW said:
yes
Do same operation but with S Plus Firmware
Click to expand...
Click to collapse
Great, will do and post results [emoji106]
Sent from my VIVO XL using Tapatalk

IacobIonut-DW said:
READY , NOW YOU HAVE PERMANENT FIX IMEI FOR ALL DEVICES [MTK] WHICH HAVE LP & MM FIRMWARE + TWRP ON BOTH VERSIONS
IF YOU WILL DO FACTORY RESET , IMEI WILL BE STILL HERE , NO ERASE , 100% TESTED
Click to expand...
Click to collapse
Thank you very much!!! I have also checked it and it works perfectly !!!!

msellaro said:
Thank you very much!!! I have also checked it and it works perfectly !!!!
Click to expand...
Click to collapse
Quite honestly I've been swamped with other things and have not tried this yet.
So you're saying that you have AEX running (or other custom ROM) with your Blu Vivo XL without losing both IMEI?
I'll try it out later, but just checking in the meantime

Rayan said:
Quite honestly I've been swamped with other things and have not tried this yet.
So you're saying that you have AEX running (or other custom ROM) with your Blu Vivo XL without losing both IMEI?
I'll try it out later, but just checking in the meantime
Click to expand...
Click to collapse
It works very well and I was really surprised at the speed with which the operating system loads. Although surely much is because I have not installed the gapps yet.

Awesome to know!
But I'll have to ask which S Plus rom variant did you use? I found three different ones with different numbers. ?
Also what Custom ROM did you installed?
Thanks in advance!

Rayan said:
Awesome to know!
But I'll have to ask which S Plus rom variant did you use? I found three different ones with different numbers. ?
Also what Custom ROM did you installed?
Thanks in advance!
Click to expand...
Click to collapse
XOS V2
Sent from my Blu Vivo XL using XDA Labs

Hmmm, even after trying all that's been said here, I simply can't keep the IMEI functions after flashing any custom ROM. I know my way around custom roms since the XDA days but this one is really getting on my nerves... U_U

Nevermind I have it working now!!!... With your feedback I was able to come up with a different path to get the firmware directory in place without corrupting the ROM.

Rayan said:
Nevermind I have it working now!!!... With your feedback I was able to come up with a different path to get the firmware directory in place without corrupting the ROM.
Click to expand...
Click to collapse
Please tell us how you did. I tried to repeat the process and this time it didnt work for me. Thank you!!!

Sorry for late reply!
I have moved to an LG G6 since and now I don't recall the exact steps! U_U

Restore IMEI with MTK Engineer Mode, i dont undertand is there any video tutorial?

Hello guys, how can I fix my BLU VIVO XL, its showing invalid imei, the baseband got wiped off after hard resetting the phone, pls I really need y'all to help me. can Gionee S plus stock ROM work on this phone? cos I've downloaded the stock ROM & flash the phone still it didn't work.

Youngklassic said:
Hello guys, how can I fix my BLU VIVO XL, its showing invalid imei, the baseband got wiped off after hard resetting the phone, pls I really need y'all to help me. can Gionee S plus stock ROM work on this phone? cos I've downloaded the stock ROM & flash the phone still it didn't work.
Click to expand...
Click to collapse
Did you ever recover your imei and baseband...I just did that myself and it was to easy to fix...

[ROM] [STOCK] [08-Mar] TWRP flashable Stock ROM [v340]

Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues.
If already on Stock Rom then visit THIS THREAD for OTA updates.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - TWRP_Stock_v340.zip from this post.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
Users coming from Android Pie reported microphone issues - in case you face it then flash DolbyPlus-Oreo_8.1.zip from THIS post via Magisk which might resolve the issue.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.

To ROOT the ROM
Flash Magisk from TWRP and you will have root access

Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......

piku2008 said:
Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......
Click to expand...
Click to collapse
Did you performed factory reset and flashed ROM & decrypt.zip
The TWRP survives the flash and Magisk can be flashed to Root the ROM but after above two files are flashed.

Well I successfully flashed ROM after complete factory reset with internal memory tooo ......
But some how TWRP got replaced with factory default (the one with root checker) with bootloader unlocked screen

Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available

Aftab_khatri said:
Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available
Click to expand...
Click to collapse
Will do

Thank You bro.. Your Guide has tested successfully from AOSiP build to stock ROM 309.. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app

AOSP to Stock
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...

jroviel18 said:
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...
Click to expand...
Click to collapse
Great .. Sorry could not reply earlier but you got the resolution of the query.
For subseqeunt update with TWRP intact .. please follow this guide in future .. https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269

Update - WW-15.2016.1805.311
Updated Stock ROM file - TWRP_Stock_v311.zip now avaliable.
For those who are already on stock ROM,
The instructions to flash are in THIS POST.
For those who are on custom ROM,
The instruction to flash are in THIS POST

Do these zips format internal storage or not ??

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
No

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
I believe this is the exact same firmware as the official one. It is just modified to work with TWRP. Nothing more, nothing less.

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
You will have to format data (i.e. factory reset) but the Internal Storage will be safe.

aaa
Work For Max Pro M1 ?
This rom XOOT not XOOTD
---------- Post added at 11:26 AM ---------- Previous post was at 11:07 AM ----------
.A.V.i.n.a.S.h. said:
Code:
[B]NOTE : [/B]Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues. BUT still proceed at your own risk.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - Stock_X00T_Patch_May_Version_311_TWRP.zip.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
This will update your firmware to WW-15.2016.1805.311 to have updates after this follow THIS THREAD.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
Click to expand...
Click to collapse
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english

arielrizuly said:
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english
Click to expand...
Click to collapse
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.

.A.V.i.n.a.S.h. said:
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.
Click to expand...
Click to collapse
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.

Abby 244 said:
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.
Click to expand...
Click to collapse
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.

.A.V.i.n.a.S.h. said:
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.
Click to expand...
Click to collapse
No response even in fastboot.

Tutorial(downgrade8.1.0=>7.1.1)use nougat stok/custom-roms on Oreo BC-12 bootloader

Tutorial(downgrade8.1.0=>7.1.1)use nougat stok/custom-roms on Oreo BC-12 bootloader
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work​
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!

reserved

Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
vaserbanix said:
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work​
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!
Click to expand...
Click to collapse
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?

ShattrdChain said:
Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?
Click to expand...
Click to collapse
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk

vaserbanix said:
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk
Click to expand...
Click to collapse
Oh ok. Thank You very much

I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix

What are the problems with 8.1? I'm still on Android 7 (RETEU)

Argon007 said:
What are the problems with 8.1? I'm still on Android 7 (RETEU)
Click to expand...
Click to collapse
1. Oreo Battery drains considerably faster than 7.1. (But charges faster too)
2. Fingerprint unlocks slower than 7.1
3. Lags slightly when doing intensive tasks.

Now we need a maintainer for (a) Nougat rom(s)..

Ænimal said:
Now we need a maintainer for (a) Nougat rom(s)..
Click to expand...
Click to collapse
YES indeed!

Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.

mysticauls said:
Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.
Click to expand...
Click to collapse
lineage 14.1 work so it should work ViperOS too!
to be sure ask in ViperOS thread.
Thankyou!

Hello!
Do you lose biometrics by installing twrp?

vaserbanix said:
YES indeed!
Click to expand...
Click to collapse
LOS14.1 has been updated:
NEW BUILD: https://www.androidfilehost.com/?fid...63190603848665
Change log: November 18 Security Update
NOTE: Like so many other users, I too updated my device with OREO and stuck with that. I haven't tried downgrading it because I don't want to end up with a hard-bricked device once again. Point here is the new build is not tested. So please take a TWRP backup before using this build. Don't forget to post me even if works fine.
Thanks,
KS
Click to expand...
Click to collapse
EDIT: When I try to quote properly I get logged out for some reason, so see this thread obviously (and don't forget to thank @kalyansundhar ):
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918

Fantastic tutorial, vaserbanix. Thank you!
Does anybody know where can I get a nougat stock rom TWRP flashable? There is a thread with stock roms but all of them are only flashable via Fastboot...
I would like to get this in particular: [MONTANA_NPP26.102-49-14]
---------- Post added at 08:38 PM ---------- Previous post was at 08:13 PM ----------
ShattrdChain said:
I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix
Click to expand...
Click to collapse
Thank you so much for your feedback, ShattrdChain! :good:
May I know what rom did you use for flashing with this method?
And do you know if bootloader needs to be unlocked in order to downgrade with this guide?

TWRP method doesn't work (bootloop), pls fix or delete.

FanderWasTaken said:
TWRP method doesn't work (bootloop), pls fix or delete.
Click to expand...
Click to collapse
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!

vaserbanix said:
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!
Click to expand...
Click to collapse
Its works great.
You can also use fastboot to downgrade!

can the downgrade be done without the bootloader unlocked?

the methods don't work for xt1799-2!