Related
STEP BY STEP GUIDE---INSTALL JELLYBEAN---ANDROID 4.1 Galaxy Note GT-N7000 Brick Free
(This method does not work on GingerBread..For GB to CM10 Goto post No.4)
No need for a PC..
INFACT..CAN BE USED TO FLASH ANY KERNEL ..AND ANY ROM.. JUST CHANGE THE KERNEL/ROM FILE YOU WISH TO FLASH..
Downloads:
Root_SuperSu: http://forum.xda-developers.com/attachment.php?attachmentid=1279136&stc=1&d=1345786322
“Mobile Odin” pro: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en
Safe Kernel Hydracore: http://forum.xda-developers.com/showthread.php?t=1749863
JB 4.1 nightlies: http://get.cm/?device=n7000&type=nightly
Gapps: http://goo.im/gapps
You are unrooted/1st time experimenting--> Start from Step No.1
Already (rooted + Unsafe kernel)--> Start from Step No.2
Already (rooted + SAFE kernel)--> Start from Step No.3
1. ROOT YOUR DEVICE
a. Reboot to recovery (vol.up+home+power button)
b. Select Install zip from Memory
c. Select Root_SuperSu 0.95 you have downloaded and flash it
d. Reboot your galaxy note
2. INSTALL SAFE KERNEL
a. Install MobileOdinPro
b. Open Mobile Odin (let it auto download something)and select Kernel and select the HYDRACOREKERNEL file you have downloaded
c. Device will reboot
d. Voila..You are now EMMC bug free. Wipe it onn
3. WIPE DATA
a. Reboot to recovery (vol.up+home+power button)
b. Select wipe data/factory reset & wipe cache partition
4. FLASH ROM
a. Select Install zip from Memory
b. 1st select JB file
c. Then select Gapps
d. Reboot
WOW…!!!!! Jelly Bean on your Galaxy Note..!!! :good::good::good:
Owning Galaxy Note is lucky...And you are even luckier..
PLEASE FOLLOW THE GUIDE TO THE CORE. Else only you will be responsible.0
There is no point in going back to Gingerbread. There are plenty of safe ICS kernels to flash from. Never EVER have I gone back to gingerbread, and I've tried almost every ROM in this forum.
Sent from my GT-N7000 using Tapatalk 2
trell959 said:
There is no point in going back to Gingerbread. There are plenty of safe ICS kernels to flash from. Never EVER have I gone back to gingerbread, and I've tried almost every ROM in this forum.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Of course there are other ways, but as our grand master of Cyanogen and Samsung ceremonies, sir Entropy pointed out, the only 100% SAFE WAY to do it is by reverting to GB, WITH PC ODIN, NOT MOBILE ODIN.
Both might work, but the 100% sure one is the PC-Odin-return-to-GB-way
Universal method
Step by step guide --> INSTALL CM10 --> Jellybean
________________________________________
Galaxy Note GT-N7000.
Running on any ROM and any android version and any kernel.
Step by step
Guaranteed Brick Free
Guide to install Jellybean
Steps:
1. Install Samsung Kies and check for any update.
2. Connect phone to Kies and check if Kies detects the phone properly. After sucess, exit Kies.
3. Download
a) PC Odin from this link http://forum.xda-developers.com/atta...1&d=1323799721 password:samfirmware.com
b) Pre rooted GingerBread ROM--SGN_XX_OXA_KJ1_FACTORYFS.zip (thx dr.ketan)---http://d-h.st/HJM
4. Run PC odin
5. Reboot Note in download mode (vol. down+home+power buttons) and then connect Download mode ready Galaxynote to PC
6. PC odin ID:COM turns yellow (ALL THE BEST NOW..!!!)
7. In PC ODIN
Auto Reboot and F.Reset Time ---> Ticked and all Others --> Unticked
Click PDA and select the SGN_XX_OXA_KJ1_FACTORYFS.zip you had downloaded. Click start.
Wait for 10minutes. Your phone will restart.
WOW..!!! now ur on a GB Rom..And its a safe kernel (emmc brick free)..Now you can play around with your phone..Plus already rooted..
8. Now to get this GB Rom working
go to recovery mode (vol up + home + power)
clean dalvik cache and wipe data and factory reset.. (yesss..u can wipe now)
9. Time to install CM10 Jellybean
Download
a) CM10 latest: http://get.cm/?device=n7000&type=nightly
b) Googleapps: http://goo.im/gapps/gapps-jb-20120726-signed.zip
10. Copy these 2 files in the internal SD card anywhere (do not rename)
11. Reboot into recovery mode: (vol up + home + power)
12. Flash the 2 files from where you saved them---> "install zip from sd card" option in recovery mode
1st -- flash cm10 file
Then -- flash gapps file
13. DO A DATA WIPE / FACTORY RESET (yess...again emmc bug free)(u can wipe 50 times )
Reboot..
And wow..
Jelly Bean on your Galaxy Note..
Owning Galaxy Note is lucky...And you are even luckier Enter the world of custom ROMS
So is there no way to move from CM9 to CM10 without returning to GB. If not I'm happy returning to GB if its 100% safe
Sent from my GT-N7000 using xda app-developers app
raikanmp said:
So is there no way to move from CM9 to CM10 without returning to GB. If not I'm happy returning to GB if its 100% safe
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
The "Return-to-GB" should only be made once you're on "dangerous" kernels, such as Stock Samsung ICS, or ROMs based on stock Samsung ICS. In the case of Cyanogen, you can flash back and forth (with the mention of full-wiping in between, as the guide in their OP says) as much as you want.
No return to GB needed between CM9 and CM10
eug3n91 said:
Of course there are other ways, but as our grand master of Cyanogen and Samsung ceremonies, sir Entropy pointed out, the only 100% SAFE WAY to do it is by reverting to GB, WITH PC ODIN, NOT MOBILE ODIN.
Both might work, but the 100% sure one is the PC-Odin-return-to-GB-way
Click to expand...
Click to collapse
Wrong, now he says that you only have to flash the CM9 safe kernel from CM9 thread FAQ. If you look at the last CM9 thread, you find that Entropy said several times there's no need to flash GB or abyss kernel.
Entropy512 said:
CM9 kernel is safe.
People are too ****ing obsessed with this Abyss ****... There are plenty of safe kernel options, as long as you avoid anything based on a Samsung stock kernel. All source-built custom kernels I am aware of other than Franco r1 and r2 (r3 and later are fine) are safe.
Click to expand...
Click to collapse
From CM9 thread
Thanks so much for this. I'm going to wait a month or two and see if any official Jelly bean live comes down the pipeline but after that I may take the plunge with my Note.
arungupta1985 said:
Galaxy Note N7000.
Running on any ROM and any android version.
Step by step
Brick Free
Guide to install Jellybean
Steps:
1. Install Samsung Kies.
2. Check for update from Samsung Kies and update Kies.
3. Connect phone to Kies and check if Kies detects the phone properly.
After sucess, exit Kies.
4. Download PC Odin from this link
http://forum.xda-developers.com/attachment.php?attachmentid=815370&stc=1&d=1323799721
password:samfirmware.com
5. Download pre rooted GingerBread ROM
SGN_XX_OXA_KJ1_FACTORYFS.zip (thx dr.ketan)
http://d-h.st/HJM
6. Run PC odin
7. Reboot Note in download mode
vol. down+home+power buttons
8. Connect Download mode note to PC
9. PC odin ID:COM turns yellow:
(ALL THE BEST NOW)
10. In PC ODIN
Auto Reboot and F.Reset Time ---> Ticked
Others --> Unticked
10. Click PDA and select the SGN_XX_OXA_KJ1_FACTORYFS.zip you had downloaded.
Click start.
Wait for 10minutes.
Your phone will restart.
11. WOW..!!! now ur on a GB Rom
And its a safe kernel
Now you can play around
Plus already rooted
12. Now to get this GB Rom working
go to recovery mode (vol up + home + power)
clean dalvik cache and wipe data and factory reset
13. Time to install CM10 Jellybean
14. Download
CM10 latest:
http://dl-bacon.bbqdroid.org/dinner/cm-10-20120727-n7000-XPLODWILD.zip
Googleapps:
http://goo.im/gapps/gapps-jb-20120726-signed.zip
15. Copy these 2 files in the internal SD card anywhere (do not rename)
16. Reboot into recovery mode:
vol up + home + power
17. Flash the 2 files from where you saved them:
"install zip from sd card" option in recovery mode
now flash cm10 file
then flash gapps file
18. DO A DATA WIPE / FACTORY RESET
19. Reboot
And wow..
Jelly Bean on your Galaxy Note..
Ur one of the lucky ones
Enter the world of custom ROMS
[[[to switch to another ROM, follow steps 1 to 17, and after that flash the ROM of your choice]]]
Click to expand...
Click to collapse
This wrong and you will get bootloop if not first installing cm9. And no need to go back to gb, just flash a gb kernel and reboot in to recovery.
Sure?
androiadicted said:
This wrong and you will get bootloop if not first installing cm9. And no need to go back to gb, just flash a gb kernel and reboot in to recovery.
Click to expand...
Click to collapse
Are you sure?
This seems very redundant to me, there's a guide with plenty of steps in the official thread.
eug3n91 said:
Of course there are other ways, but as our grand master of Cyanogen and Samsung ceremonies, sir Entropy pointed out, the only 100% SAFE WAY to do it is by reverting to GB, WITH PC ODIN, NOT MOBILE ODIN.
Both might work, but the 100% sure one is the PC-Odin-return-to-GB-way
Click to expand...
Click to collapse
It's just as safe as going back to gingerbread. The only thing that's different is how long it takes.
Seriously if you guys are that nervous about bricking your Notes, why are you even rooted?
Sent from my GT-N7000 using Tapatalk 2
hi can i safely use this guide coming from XXLPY stock 4.0.3?
A very helpful guide.
Thank you very much.
androiadicted said:
This wrong and you will get bootloop if not first installing cm9.
Click to expand...
Click to collapse
It's pointless saying this without pointing out where and why you think the guide is wrong.
Yes
LoVeRice said:
hi can i safely use this guide coming from XXLPY stock 4.0.3?
Click to expand...
Click to collapse
100% safe
Tried and succeeded by many
yeeee! thankx man -succesfuly flashed my phone, bajillion + & thankx!
Sent from my GT-N7000 using xda app-developers app
arungupta1985 said:
100% safe
Tried and succeeded by many
Click to expand...
Click to collapse
Thanks OP for the effort.
On the lighter side... I guess you will prefer to change your signature now to "CM10 Galaxy Note - Baap of all Phones" instead of CM9 Gallaxy Note - Baap of all Phones"... after all... the Baap is DADA now!!!
By the way, how is your experience with CM10-JB?
very nice and easy to.follow guide. thanks for posting this
Can someone share the bugs in cm10?
Sent from my GT-N7000 using xda app-developers app
hello,
after reading almost everything i could read on the forums about the procedure of flashing roms, i'm left with a few questions that i couldn't find answers to, or i found more then one answer.I read all the following, and more:
1. [GUIDE] All-in-One Defy Beginner's guide by Zephyrot here: http://forum.xda-developers.com/showthread.php?t=1216982
2. [JB] CM10 Android 4.1.2 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=1768702
3. [GUIDE][KitKat][CM11] Updating to 4.4 by coolshahabaz here: http://forum.xda-developers.com/showthread.php?t=2568325
4. [Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=2515036
5. http://forum.xda-developers.com/showthread.php?t=2597719
6. http://forum.xda-developers.com/showthread.php?t=2644812
7. http://forum.xda-developers.com/showpost.php?p=49558697&postcount=3
8. http://forum.xda-developers.com/showpost.php?p=49558744&postcount=4
My devicee is a Defy+ with Gingerbread 2.3.6. I found here: http://sbf.droid-developers.org/phone.php?device=28 "Android 2.3.6 Blur_Version.45.0.1610.MB526.Partner.en.IL" rom which is supposed to be my stock rom.
1. My main concern is always to keep the option to go back to stock rom. As i read here, this might be a problem with Defy+, but only if i flash SBF files, which i dont plan to. Is it correct that i will be able to flash the stock rom with RDS_lite, motorola drivers and bootloader (power up with VOL up) at any time?
questions about recovery:
2. I understand that i need TWRP 2.3.6 in order to flash new roms, and since recovery is protected in Defy, i must use 2nd_init to bypass stock recovery. Is 2nd_init include the custom recovery in it? if so, which one? and what version?
3. can i install CWM or TWRP without using 2nd_init?
4. What is rom_manager (for CWM) or goo.im (for TWRP) and do i really need them?
5. what is update_recovery.zip mentioned as part of the procedure here http://forum.xda-developers.com/showthread.php?t=2515036 does it update the custom recovery or the stock recovery? is it really needed since some of the procedures described above skip this step?
choosing a custom rom:
6. I'm looking for adnroid 4.4. what is the difference between this: http://forum.xda-developers.com/showthread.php?t=2597719 (AOSP Android 4.4 for the Defy(+)) and this http://forum.xda-developers.com/showthread.php?t=2515036 (CM11 Android 4.4 for the Defy(+))
7. If i want a as-close-as-possible to google original kitkat 4.4, which one should i use?
Thanks,
Roy.
I have some of the same questions you have... will follow this topic, hoping for some info! thx!
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
Here is where 2nd Init comes to play, this little awesome app kicks in right after the Bootloader and allows the Defy to load a different, non-Stock Android.
With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting all your stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Lite in Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back to live normally.
Click to expand...
Click to collapse
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
hotdog125 said:
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
Click to expand...
Click to collapse
Many many thks!
Im trying to up to CM 11 from 2 months.Now Im on 10.0(4.1.2).Every try to update recovery with "update-recovery.zip" or TWRP 2.6.3.0 finished with bootloop or without custom recovery and balck screen.And them flash stock .sbf and start all from the begining.And try and try....In your guide it have link to update recovery.It have something about 30+ seconds waiting after TWRP update.So I try.
you can install to Jellybean (4.1.x) (4.2.x) (4.3.x) this way
installing to 4.4 kitkat is a bit different and not fully covered here
Disclaimer::
This is based on a post I made in that thread, I'm only trying to complement what droidstyle has done and maintained over all these years
It just gets buried in there, So I thought I would make my own post about it since that's what most are looking for from that nowadays
Attention:: Do Not Quote this post in a reply,,, that only takes up unnecessary space in the thread
Jellybean is more stable than Kit Kat is right now overall, so if you that is what you need continue on reading
Install this way::
it is my take on installation, with a little more clarification/in-depth instruction, of droidstyles Guide, "" Section:4 "" and with working Links to all the files
First: Download these files to your pc:
Odin - Odin3 v1.83.exe - http://www.androidfilehost.com/?fid=23125694133305378
Samsung Driver - USB_Drivers_1.5.27.0.rar - http://www.androidfilehost.com/?fid=23134718111255952
... (install instructions here http://forum.xda-developers.com/showthread.php?t=2038555 ,,,,,, installable via "setup.exe" OR via "have disk" method )
CWM4 fixed for cm7 - cwm4_fixed_for_cm7-ODIN.tar - http://www.androidfilehost.com/?fid=23203820527944229
Stock Verizon EH03 rom - CI500_VZW_EH03_GB_CM.tar.md5.zip - http://www.androidfilehost.com/?fid=23050663588004887
... (this needs to be extracted with a program such as 7zip)
Atlas_v2.2 pit - atlas_v2.2.pit - http://www.androidfilehost.com/?fid=13858085825318748851
GB bootloaders - GBBootloaders.tar - http://www.androidfilehost.com/?fid=13858085825318748850
... (this is ready for ODIN installation)
.
Power off and pull battery,
remove micro sdhc card
put into d/l mode, install battery
odin:: :: PDA Slot :: CI500_VZW_EH03_GB_CM.tar.md5 ::
and in the :: PIT Slot :: Atlas_v2.2.pit ,,, and appropriately check box [[ Re-Partition ]]
when finished
reboot
~~check out all of Verizon goodness ~~
oh sorry ,,,
Power off and pull battery
put into d/l mode, install battery
odin:: :: PDA Slot :: cwm4_fixed_for_cm7-ODIN.tar
when finished, click reset in odin
pull battery and usb to power down the fassy and close out of odin
put into d/l mode, install battery
odin:: :: BOOTLOADER Slot :: GBbootloaders.tar ,,, and appropriately check box [[ Phone Bootloader Update ]]
when finished, click reset in odin
pull battery and usb to power down the fassy and close out of odin
Reinstall micro sdhc card
Use three button method to boot into into CWM blue recovery 4 [ie: cwm4_fixed_for_cm7] ,,, [[[ Hold -- Volume buttons UP / Down & Power (((hold all 3 until 2 time the "Samsung" Logo appears,, then release power button while continuing to hold both up/down buttons down,,, when recovery screen comes up,, release buttons and proceed))) ]]]
(((you have to use this recovery at this point in the process,,, it will let the system properly accept the update from a bml ROM to an mtd ROM)))
and then, Choose the 'Wipe Data/Factory reset', and also wipe 'dalvik cache' [1 time for each is fine]
then while still in this recovery,,, flash your 4.2.x ROM of choice,,,
it will auto reboot into any newer recovery [[ ie: cwm 6.0.x.x, or new TWRP 2.x.x, or Devil Recovery ]] ,,, never go back to the [cwm4_fixed_for_cm7] recovery,, ,, unless you have ODIN'ed back to stock,,, ,,, this is normal,,, and now you will need to select install zip from sd [again]::
and choose to install/flash your 4.2.x ROM of choice AGAIN,
if it auto reboots you back into this same recovery again [meaning: any newer recovery],,, still that is fine/normal ,,,,,,, simply install/flash your 4.2.x ROM of choice AGAIN,,,, It may also give you an "Error Code",,, still that is fine/normal ,,,,,,, simply install/flash your 4.2.x ROM of choice AGAIN,,,
...[[[ the recovery style and version is determined by the ROM you are installing, some have standard CWM Recovery, some have Hellybean Touch Recovery,,, some have TWRP Recovery, and some have a blue Touch Recovery version ]]]...when finished installing your ROM,,
if may auto reboot and load the ROM,, if not manually choose to Reboot Rom,,, and ,,, Wait ,,, patiently,,, ,,, maybe as much as 8-10 minutes for it to boot all the way up.
you may ultimately have to flash 1 more time,, some ROMs seem do be more finicky than others.
After that you really should be almost good to go.
On the 1st boot of your new 4.2.x ROM give the filesystem about 5-10 minutes to silently scan through everything before making any changes to any of your ringtones or notifications
after that reboot into recovery,,, Wipe cache only ,,, and Install a Google gapps zip :::
[ either whats recommended by the ROM dev/maintainer,,, or an official gapps of the appropriate date that matches your ROM ]
reboot
Sign in to your Google account,,, {Settings, +Add Account, Google )
Rom will be laggy as crap while it syncs all your information, it may even need to update a google app or 2,, but will get better when finished.
((Some people/methods prefer to install gapps before that 1st boot of your new 4.2.x ROM and that's OK too, I used to, but got into the habit of doing it this way as it lets me set up a few things in the ROM with out having to deal with any syncing issues if there are any... ))
Enjoy your Jellybean goodness ~ Yummy!
.
.
If all else fails please refer back to ::
Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
in the ::
[GUIDE] Installing a Rom/CWM recovery/Root or going back to Stock
posted by and updated by :: droidstyle
.
.
Dead Links???
Look here for them instead
Links to Fascinate Android 4.2 and Older files
http://www.androidfilehost.com/?w=files&flid=4298
::
Links to Fascinate Android 4.3 and Newer files
http://www.androidfilehost.com/?w=files&flid=7312
::
.
UPDATED NEWBIE GUIDE v2.0
FOR REDMI NOTE 3 SNAPDRAGON (KENZO)
(WORKS FOR ALL MIUI / AOSP / CM BASED ROMs)
GUIDE SECTIONS : QUICK LINKS#1 : MIUI ROM | TYPES OF MIUI ROM | TWRP | TYPES OF TWRP
#2 : TWRP FLASHABLE ZIPs | FULL PARTITION BACKUP | FLASHING ROM
#3 : RESTORING MIUI FIRMWARE (WIP) | SUMMARY | CREDITS
IMPORTANT NOTE !!- Before following any step or asking any question, please read the guide & the below comments very carefully & thoroughly
- You are choosing to make these modifications, I take no responsibility for bricked devices, dead or corrupt SD cards, accidental data wipe etc.
- This guide only supports users who have UNLOCKED their BOOTLOADER using OFFICIAL method
- I have dropped support for users who have UNLOCKED their BOOTLOADER using UNOFFICIAL method as it was risky & confusing
- This guide will be updated as new information, TWRP, methods are added. Do let me know if I have forgot to mention anything useful
MIUI ROM
MIUI (pronounced as Me-You-I) is Xiaomi's custom built firmware on top of Android like Samsung's Grace UX, HTC's Sense, OnePlus's OxygenOS which runs on their smartphones. MIUI is also the second most popular Android firmware, after CyanogenMod. MIUI is based on Android's AOSP base with its own modifications and extensive features over the top. At first glance it resembles like a hybrid between Google's Material Design and Apple's iOS. But unlike Stock Android or iOS, MIUI is very intuitive, feature rich and has multiple tweaking options.
MIUI is updated regularly depending on the development branch. Xiaomi takes reports, feedback and suggestions from the community, addresses the bugfixes and integrates new features upon request. Most of Xiaomi devices are regularly patched with monthly security updates. The flagship "Mi" series like Mi3, Mi4, Mi5 receive quicker Android version updates than their budget "Redmi" series like Redmi 2, Redmi 3, Note 2, Note 3 etc.
TYPES OF MIUI ROM
There are 2 development branches of official MIUI ROMs for all Xiaomi devices.
A) Stable Branch aka Stable Builds
- It is updated on a monthly basis or longer
- New features are added slowly after testing
- Higher system stability and less bugs than Beta ROMs
- It has a four digit numbering scheme (X.X.X.X)
- For eg. 8.X.X.X is MIUI8 Stable ROM
- Stable ROMs come in 2 variants
1. MIUI China Stable ROM
- This ROM is pre-installed on all Xiaomi devices sold in China
- It is made for the Chinese market & contains Chinese MIUI apps
- Google Apps are absent. You can install them manually or by using ADB
- It supports Chinese & English language
2. MIUI Global Stable ROM
- This ROM is pre-installed on all Xiaomi devices sold outside China
- It is made for the International market & contains English MIUI apps
- Google apps are pre-installed by default
- It supports 50+ languages
B) Beta Branch aka Developer Builds
- It is updated on a weekly/bi-weekly basis or longer
- New features are added quickly for testing
- Lower system stability and more bugs than Stable ROMs
- It has a three digit numbering scheme (X.X.X)
- For eg. 6.11.21 is MIUI8 Beta ROM for 21th Nov, 2016
- This ROM is not pre-installed on any Xiaomi device.
- You have to install Beta ROM over Stable ROM manually.
- Beta/Developer ROMs come in 2 variants
1. MIUI China Beta/Developer ROM
- It is made for the Chinese market & contains Chinese MIUI apps
- Google Apps are absent. You can install them manually or by using ADB
- It supports Chinese & English language
2. MIUI Global Beta/Developer ROM
- It is made for the International market & contains English MIUI apps
- Google apps are pre-installed by default
- Supports more than 50+ languages
Vendor aka Unofficial MIUI ROM
- Official MIUI ROM is found on Xiaomi devices that are bought from official channels
- Official channels include Xiaomi stores, flipkart.com, amazon.com etc.
- Vendor/Unofficial MIUI ROM is typically found on Xiaomi devices that are bought from unofficial channels/third-party resellers
- Unofficial channels include geekbuying.com, gearbest.com, banggood.com, ebay.com etc.
- Resellers take any of the official MIUI ROMs and modify it by injecting malwares, adwares, promotional apps etc.
- Vendor ROM may or may not contain Chinese MIUI Apps or Google Apps
- The Vendor ROM is then flashed by the reseller via EDL mode using MiFlash Tool, which bypasses LOCKED bootloader status
- Vendor ROMs can be identified by their odd 5 digit numbering scheme (X.X.X.X.X) eg. MIUI8 8.0.1.1.0, MIUI7 7.9.8.8.0
- You can identify a vendor ROM by comparing its version with official MIUI version here : http://en.miui.com/download.html
- Due to stability & security reasons, such ROMs should not be used and should be changed immediately.
- You should flash official MIUI ROMs using MiFlash Tool via EDL mode.
TWRP
TWRP stands for Team Win Recovery Project. It is a custom recovery used to flash ROMs, kernels & scripts, take full system backups, restore backups etc. There are multiple versions of TWRPs for the Redmi Note 3 Snapdragon (kenzo). Many new users are confused as to which version of TWRP to flash after UNLOCKING the BOOTLOADER OFFICIALLY.
Thanks to Xiaomi for the multiple hardware revisions, outdated kernel sources & the tiresome process of unlocking the bootloader, this device has become even more complicated for the developers as well as for the end users. Hopefully Xiaomi updates the kernel sources as soon as possible. This will result in a streamlined and unified environment for the developers while compiling ROMs and for the user for a better end user experience.
TYPES OF TWRP
1. Official TWRP : https://dl.twrp.me/kenzo/
- The base version of TWRP 3.0.2-2
- It is the stock version with no modifications done to it
- Used to flash flash ROMs, kernels & scripts, take full system backups, restore backups etc.
2. F2FS TWRP
Nougat : http://forum.xda-developers.com/showpost.php?p=70148939&postcount=3710
Marshmallow : http://forum.xda-developers.com/showpost.php?p=68023154&postcount=2
- Based on official TWRP 3.0.2-2
- Adds support for F2FS based file systems
- Specifically made for official CyanogenMod ROMs
- Compiled with Android 6.x & Android 7.1 branch respectively.
- Users can convert their /data & /cache partitions from EXT4 to F2FS for better performance (Optional)
3. Unofficial TWRP : http://forum.xda-developers.com/redmi-note-3/development/recovery-twrp-3-0-2-0-t3446909
- Based on official TWRP 3.0.2-2
- Up-to-date with Android 6.0 & Android 7.0 branch
- Adds support for F2FS based file systems
- Users can convert their /data & /cache partitions from EXT4 to F2FS for better performance (Optional)
- Can backup all partitions of the device
- Permissive SELinux
4. ZCX TWRP : http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
- Based on official TWRP 3.0.2-0
- Patches boot.img automatically (Removes dm-verity flag)
- Disables forced encryption
- Updated to Android 7.1 TWRP source
- SuperSU updated to v2.76
- Fixes "0MB Storage", "Unable to mount /" errors
- Adds support for Android 6.0 /data partition decryption
- Can be used to flash incremental OTA updates on MIUI rooted ROMs
5. Cofface TWRP : http://forum.xda-developers.com/redmi-note-3/development/recovery-kenzotwrp-cafface-3-0-0-t3369341
- Based on official TWRP 3.0.0-0
- Patches boot.img automatically (Removes dm-verity flag)
6. Safe TWRP v2 : http://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
- Based on Cofface TWRP 3.0.0-0
- Patches boot.img automatically (Removes dm-verity flag)
- Specifically compiled for users who UNLOCKED the BOOTLOADER using UNOFFICIAL method.
- Prevents hardbrick while flashing MIUI Recovery ROM Zip or incremental OTA Zip
7. Alka TWRP : http://en.miui.com/thread-282773-1-1.html
- Based on Cofface TWRP 3.0.0-0
- Patches boot.img automatically (Removes dm-verity flag)
- Disables forced encryption
- Can backup all partitions of the device
TWRP FLASHABLE ZIPS- These zips are meant to be flashed with TWRP with a specific order.
- Before flashing any zip make sure you have taken full backup of your device partitions using TWRP.
- Steps for full backup are mentioned in the next section.
PATCHES
1. Universal Boot Image Patcher : http://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
- This zip patches the boot.img i.e. it disables "dm-verity" (Lollipop Only)
- Use this zip if you are having official TWRP, F2FS TWRP, Unofficial TWRP installed.
- All other TWRPs automatically patch the boot.img so no need to use this zip.
- This zip has to be flashed immediately after flashing MIUI Lollipop Recovery ROM else your ROM wont boot.
2. Lazy Flasher : https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view
- This zip patches the boot.img i.e. it disables "dm-verity" and disables forced encryption (Marshmallow Only)
- Use this zip if you are having Official TWRP, F2FS TWRP, Unofficial TWRP, Cofface TWRP, Safe TWRP v2 installed.
- If you are using ZCX, Alka TWRP no need to use this zip
- This zip has to be flashed immediately after flashing MIUI Marshmallow Recovery ROM else your ROM wont boot.
3. VoLTE Patch : http://forum.xda-developers.com/redmi-note-3/development/volte-patches-nougat-based-cm-roms-t3509257
- This zip is to be flashed on specific Android 7.x Nougat based ROMs
- It enables VoLTE support by flashing modem partitions
4. RR 5.8.0 Fingerprint Fix : http://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-enable-goodix-fingerprint-t3507979
- This zip is to be flashed on Resurrection Remix 5.8.0
- This zip enables fingerprint sensor support for models having Goodix FP sensor
5. CM13 Front Camera Fix : http://forum.xda-developers.com/redmi-note-3/how-to/fix-camera-fix-official-cm13-builds-t3454893
- This zip is to be flashed if your front camera doesnt work on CM13 ROM
- This zip fixes "Could not connect to camera" issues.
6. CM13 Security & Radios Fix : https://drive.google.com/file/d/0B2CgYqnPbCh_RnJDaHJtdEFYRGM
- This zip is to be flashed after booting into system after flashing CM13 ROM
- This zip fixes the SIM issues and the force close in Security setting
FIRMWARES
1. Multi-ROM Firmware : http://forum.xda-developers.com/redmi-note-3/development/rom-multirom-firmwares-t3519420
- This zip enables us to boot multiple ROMs on the device simultaneously
- It flashes bootloader and other partitions
- This zip locks the bootloader
2. TheStrix's CM13 Firmware : http://forum.xda-developers.com/showpost.php?p=68023154&postcount=2
- This is the firmware that CyanogenMod 13 supports. Upgrades it from LP to MM firmware.
- This zip has to be flashed before flashing CM13 ROM else fingerprint & other sensors might not work.
- This zip does not lock the bootloader
3. TheStrix's CM14 Firmware : http://forum.xda-developers.com/showpost.php?p=68671310&postcount=2
- This is the firmware that CyanogenMod 14.1 supports.
- This zip has to be flashed before flashing CM14.1 ROM else fingerprint & other sensors might not work
- This zip locks the bootloader. Flash this one if you dont want BL Lock : https://drive.google.com/file/d/0BzDVQwVyIvEbTUZCR3lkSmR6X1E/
4. Android N Firmware : http://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
- This zip upgrades your firmware to support 7.x Nougat ROMs
- This zip should be flashed before flashing any Android 7.x Nougat ROM
- This zip does not lock the bootloader
ADD-ONS
1. Xposed Framwork : http://forum.xda-developers.com/redmi-note-3/how-to/guide-installing-xposed-framework-roms-t3416123
- Before installing any zip, perform a full backup.
- Official release is for AOSP / CM based ROMs
- Unofficial release is for MIUI ROMs
FULL PARTITION BACKUPBefore proceeding towards Flashing ROMs make sure you have backed up all the partitions on your device. Incase anything goes wrong, you can always restore the backup.
Requirements:
- Windows 7 / 8 / 8.1 / 10 PC
- Unofficial TWRP / Alka TWRP / ZCX TWRP
- Running on official MIUI7 / MIUI8 Stable ROM
- BOOTLOADER UNLOCKED Using OFFICIAL method from here : http://en.miui.com/thread-202290-1-1.html
- Minimal ADB+Fastboot drivers : http://forum.xda-developers.com/showthread.php?t=2317790
1. Installing drivers & initial setup
- On your PC, go to "Folder Options" and de-select "Hide file extensions for known file types"
- Install Minimal ADB+Fastboot drivers & restart your PC
- Make sure your phone's battery level is above 75%. Switch off your phone
- Copy the desired TWRP image file inside the Minimal Fastboot directory (C:\Program Files)
- Rename the TWRP as "twrp.img" Make sure the filename isnt "twrp.img.img"
- Hold "Power Button" & "Volume Down" button together & release both of them after "Fastboot" appears
- Connect the device to PC using USB cable
2. Flashing TWRP
- On your PC, go inside Minimal Fastboot folder directory. Hold shift and right click inside the folder
- Select "Open command window here" and type "fastboot devices" inside the command window.
- If everything goes right, your device should be recognized as "<serial number> <fastboot>"
- Type "fastboot flash recovery twrp.img" & press Enter. This will flash the TWRP in the recovery partition.
- Type "fastboot boot twrp.img" & press Enter. This will boot the phone in TWRP.
- If the language is in Chinese, select the right box, & select English.
- Uncheck "Keep System Read-Only" & Swipe to allow modifications.
3. Backup All Partitions
- Select "Backup" Option & select "Storage location" to external MicroSD card
- Select each & every partition & swipe to backup.
- After backing up, reboot to system.
- For additional saftey, copy the backup from MicroSD card to PC.
4. Flash Recommended TWRP
- After backup is complete you should switch to ZCX TWRP for best results
- Select "Install" Option & select "Flash Image" option
- Select Official TWRP / ZCX TWRP and swipe to flash
- After flashing go back, select "Reboot" and then select "Reboot to Recovery"
FLASHING MIUI/CM/AOSP ROM USING TWRPRequirements:
- BOOOTLOADER : UNLOCKED Using OFFICIAL METHOD
- BACKUP : Full partitions backup
- TWRP : Use ZCX TWRP for best results
1. Rooting MIUI7/8 Lollipop ROM
- Boot To TWRP
- Flash Universal Boot Img Patcher Zip (Flash if using Official TWRP, else skip step)
- Reboot to System
- Boot to TWRP
- Backup Current ROM
- Flash SuperSU Zip v2.78
- Reboot To System
2. Rooting MIUI7/8 Marshmallow ROM
- Boot To TWRP
- Flash Lazy Flasher Zip (Skip step if using ZCX TWRP)
- Reboot to System
- Boot to TWRP
- Backup Current ROM
- Flash SuperSU Zip v2.78
- Reboot To System
3. Flashing MIUI7/8 Lollipop Recovery ROM
- Boot To TWRP
- Backup Current ROM
- Factory Reset
- Flash ROM Zip
- Flash Universal Boot Img Patcher Zip (Flash if using Official TWRP, else skip step)
- Reboot To System
3. Flashing MIUI7/8 Marshmallow Recovery ROM
- Boot To TWRP
- Backup Current ROM
- Factory Reset
- Flash ROM Zip
- Flash Lazy Flasher Zip (Skip if Using ZCX TWRP)
- Reboot To System
4. Flashing MIUI7/8 Xiaomi.EU ROM
- Boot To TWRP
- Backup Current ROM
- Factory Reset
- Flash ROM Zip
- Reboot To System
5. Flashing Official CM13 ROM
- Boot To TWRP
- Backup Current ROM
- Flash CM13 Firmware Zip
- Reboot to Recovery
- Factory Reset
- Flash ROM Zip
- Flash G-Apps 6.0 Zip
- Reboot To System
6. Flashing Official CM14.1 ROM
- Boot To TWRP
- Backup Current ROM
- Flash CM14 Firmware Zip
- Reboot to Recovery
- Factory Reset
- Flash ROM Zip
- Flash G-Apps 7.1 Zip
- Reboot To System
7. Flashing AOSP 7.x Nougat ROMs
- Boot To TWRP
- Backup Current ROM
- Flash Android N Firmware Zip
- Reboot to Recovery
- Factory Reset
- Flash ROM Zip
- Flash G-Apps 7.0/7.1 Zip
- Reboot To System
FLASHING MIUI ROM USING MIUI UPDATER APP- This method does not require PC for flashing.
- We use the updater app present on the MIUI ROM itself to flash recovery ROM zip.
- Recovery ROM format : MIUI_DEVICENAME_MIUIVERSION_KEY_ANDROIDVERSION.ZIP
- Example : miui_HMNote3ProGlobal_V8.1.1.0.MHOMIDI_8e5f6f8e03_6.0.zip
Requirements:
- BOOTLOADER : LOCKED / UNLOCKED
- Recovery ROM : MIUI7/8 Stable/Beta : http://en.miui.com/download-301.html
- Stock : System, Boot Image, Recovery
- System : Unrooted
1. Flashing newer Global Stable version from older Global Stable version
i.e. MIUI 8.1.1.0 > MIUI 8.1.4.0
- All data will be preserved in this process, nothing will be wiped.
- Place the ROM zip inside internal storage
- Make sure battery level is above 75%
- Turn on WiFi / Cellular Data
- Open Updater App, select "Choose Update Package"
- Choose the ROM zip & select "Reboot and update"
- The update will take from 5-30 mins to install depending on the size
2. Flashing MIUI Global Beta version from Global Stable version
i.e. MIUI 8.1.1.0 > MIUI 6.12.15
- This process will wipe everything from your device, so take backup before proceeding.
- Place the ROM zip inside internal storage
- Make sure battery level is above 75%
- Turn on WiFi / Cellular Data
- Open Updater App, select "Choose Update Package"
- Choose the ROM zip & select "Reboot and update"
- The update will take from 5-30 mins to install depending on the size
3. Flashing newer MIUI Global Beta version from older Global Beta version
i.e. MIUI 6.12.9 > MIUI 6.12.15
- All data will be preserved in this process, nothing will be wiped.
- Place the ROM zip inside internal storage
- Make sure battery level is above 75%
- Turn on WiFi / Cellular Data
- Open Updater App, select "Choose Update Package"
- Choose the ROM zip & select "Reboot and update"
- The update will take from 5-30 mins to install depending on the size
4. Flashing Global Stable version from Global Beta Version
i.e. MIUI 6.12.15 > MIUI 8.1.1.0
- Unfortunately you cannot flash it using Updater-app
- You will have to use MiFlash Tool to flash fastboot ROM package
- This process will wipe everything from your device, so take backup before proceeding.
- Check out Section #3 for fastboot ROM package flashing using PC
RESTORING MIUI FIRMWARE (WIP)
- We can restore to Stock MIUI firmware from a custom ROM or softbrick by flashing a fastboot ROM using MiFlash Tool
- This method flashes all partitions using stock images. Your entire phone will be restored to factory state.
- Fastboot ROM Format : CODENAME_IMAGES_MIUI-VERSION_BUILD-DATE_ANDROID-VERSION_REGION_KEY.tgz
- Example : kenzo_images_6.12.15_20161215.0000.00_6.0_cn_7f97e1f7a9.tgz
- There are 2 ways for flashing fastboot ROM
1. EDL : Emergency Download Mode (Qualcomm Only)
- It is low-level mode used for recovering the device when phone cannot boot into system, recovery and fastboot mode
- This mode can be used on LOCKED as well as on UNLOCKED bootloaders
- We can boot into EDL mode using ADB commands, Fastboot2EDL Method, Manual Method or Deep Flash Cable
- When your phone boots into EDL mode, the screen turns blank & LED light flashes continuously
- To exit EDL mode, hold the power button for 8-10 seconds till the device restarts
2. Fastboot
- Fastboot Mode is used to UNLOCK bootloader, flash images onto the partitions, recover the device when phone cannot boot into system, recovery mode.
- This mode can only be used on UNLOCKED bootloaders.
- We can boot into Fastboot mode using ADB commands or by using Manual Method.
- When your phone boots into Fastboot mode, the screen will show "Fastboot" text and "Mi Bunny" image.
- To exit Fastboot mode, hold the power button for 8-10 seconds till the device restarts or by typing "fastboot reboot" inside command window.
Requirements:
- PC : Windows 7 / 8 / 8.1 / 10
- Mi PC Suite : http://pcsuite.mi.com/
- Mi Flash Tool
Beta : https://drive.google.com/file/d/0B9wtW2KGOf0RRS1lZGgybVVnbms/view
01/04/16 : https://drive.google.com/file/d/0B9wtW2KGOf0RaERVZXFtaGxfZ2s/view?usp=drive_web
28/10/15 : http://bigota.d.miui.com/tools/MiPhone20151028.exe
1. Flashing Fastboot ROM using Emergency Download Mode (EDL)
2. Flashing Fastboot ROM using Fastboot Mode
WORK IN PROGRESS
_____________________________________
SUMMARY
1. OFFICIAL UNLOCKED BOOTLOADERS users should use
Official TWRP
- If they plan on staying only on custom ROMs like CM14.1, AOSP
- Universal Boot Img Patcher / Lazy flasher needed after flashing MIUI ROMs
ZCX TWRP
- If they switch between MIUI & CM / AOSP ROMs
- Universal Boot Img Patcher / Lazy Flasher not needed after flashing MIUI ROMs
2. Just got a brand new Redmi Note 3 and wish to flash TWRP or a custom ROM?
STEP 1 : Verification
- Check the model : kenzo, kate, hennessy
- If kenzo, then proceed
- Verify if the installed ROM on your device is official MIUI ROM
- If NO, flash official MIUI ROM using MiFlash tool on PC via EDL mode
STEP 2 : Unlock Bootloader
- Apply for bootloader unlock
- Backup everything from internal storage, SMS, contacts etc.
- Unlock bootloader
STEP 3 : Flash TWRP
- Flash ZCX TWRP using fastboot mode using PC
- Backup all partitions using TWRP
STEP 4 : Flashing Custom ROM
- Factory Reset using TWRP
- Flash required files needed for the custom ROM
- Flash custom ROM zip
- Flash Google Apps zip
- Reboot to System
3. Follow the guides for recovering your device in case of softbrick/hardbrick, IMEI/EFS corrupt etc.
- Video Guide : Bootloader Unlock, Root, TWRP, Restore, Unbrick & ROMs : http://forum.xda-developers.com/redmi-note-3/how-to/video-redmi-note-3-bootloader-unlock-t3407003
- Flash/Unbrick On Locked/Unlocked Bootloader : http://en.miui.com/thread-235865-1-1.html
- Flash/Unbrick From HS USB 900E Mode : http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
- IMEI/EFS Repair : http://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789
CREDITS
TWRPs
Vibhor : Official TWRP
TheStrix : F2FS TWRP, CM Firmware
dadi11 : Unofficial TWRP
BY~XM : ZCZ TWRP
Cofface????? : Cofface TWRP
Rajdip : Safe TWRP v2
Alka121209 : Alka TWRP
PATCHES
Rajdip : Universal Boot Image Patcher
jcadduono : Lazy Flasher
Sudeep Duhoon : VoLTE Patch
*Moon- : RR 5.8.0 Fingerprint Fix
tank0412 : CM13 Front Camera Fix
banmeifyouwant : CM13 Radios & Security Fix
FIRMWARE
wmaster4g : Multi ROM Firmware
TheStrix : CM Firmware
Psy_Man : Android N Firmware
GUIDES
Tomsgt : Video Tutorial
Rajdip : Unbrick Guide
Muz_paray : Unbrick Guide
Archit9169 : IMEI/EFS Repair Guide
why after flashing alka recovery, we should again flash cofface? is alka recovery used for backup only? can we flash roms with alka recovery?
white FANNg said:
why after flashing alka recovery, we should again flash cofface? is alka recovery used for backup only? can we flash roms with alka recovery?
Click to expand...
Click to collapse
For official users you can flash other ROMs with Alka TWRP as well.
For unofficial users you must flash Safe TWRP v2 after Alka to avoid hardbrick if you flash MIUI ROM.
I am running now stocl global rom with officialy unlocked bootloader.
How can I flash Alka recovery to backup and install cm13? just use adb flash recovery?
Thanks for the initiative, can you explain more about the partitions.
What if one doesn't have all the partitions backed up and flashed custom rom ( CM 13)?
Also please include the current version of TWRP for respective recoveries.
nonyhaha said:
I am running now stocl global rom with officialy unlocked bootloader.
How can I flash Alka recovery to backup and install cm13? just use adb flash recovery?
Click to expand...
Click to collapse
fastboot flash recovery alkatwrp.img
mnsk said:
Thanks for the initiative, can you explain more about the partitions.
What if one doesn't have all the partitions backed up and flashed custom rom ( CM 13)?
Click to expand...
Click to collapse
Santhosh's CM13 zip based on M firmware has M boot loader. After flashing the zip your bootloader gets locked & gets updated to M boot loader.
So if you want to revert back to MIUI based on Lollipop you need to take backup of each & every partition using Alka TWRP, other TWRP wont work.
This restores the phone back to L boot loader & preserves IMEI.
All the links are updated to the latest versions of respective TWRPs.
SharkcpN said:
All the links are updated to the latest versions of respective TWRPs.
Click to expand...
Click to collapse
Can you also include them in the OP like official is on 3.0.2, alka on 3.0. Will be easier to keep track.
I think for officially unlocked bootloader the official TWRP should be used. You can flash the universal boot image patcher as a secondary ZIP if needed, and you can back up EFS with it
Hey all, I have successfully unlocked unofficially and flashed a alka via fastboot but I can't boot into recovery.
If I do adb reboot recovery it goes to a screen with a picture of my device which I assume is the stock recovery. If I reboot with Vol Up and Power I get the same thing. Any ideas? Thanks!
EDIT: I flashed "Safe TWRP v2" then Alka and it worked! Thanks OP
Nice information.
So the alka version is the best for official. Just want to know more:
1. Is that mean that backup/restore feature of cofface not backup all partitions?
2. Are there any differences between cofface and alka beside backup feature? Both seem not built from latest official twrp.
3. How about flashing (not restoring) other Rom from Santosh M Rom?
Thanks.
Sent from my Redmi Note 3 using Tapatalk
I installed alka version and it is in chinese, I am trying desperately to find a way to switch language, but all the guides online point to twrp theme manager, which does not work. any guide to change language from within twrp?
I flashed Cofface twrp also and the language is still in Chinese. there is no way to add some files somewhere to change the freakin' language?
Grantius said:
I think for officially unlocked bootloader the official TWRP should be used. You can flash the universal boot image patcher as a secondary ZIP if needed, and you can back up EFS with it
Click to expand...
Click to collapse
Yes you can use it too
Doublewise said:
Nice information. So the alka version is the best for official. Just want to know more:
1. Is that mean that backup/restore feature of cofface not backup all partitions?
2. Are there any differences between cofface and alka beside backup feature? Both seem not built from latest official twrp.
3. How about flashing (not restoring) other Rom from Santosh M Rom?
Click to expand...
Click to collapse
1. Yes, only Alka TWRP is capable of backing up & restoring all partitions including bootloader.
2. Alka TWRP backs up EFS (IMEI) partition as well, Cofface dosent. Rest all features are same.
3. For official unlocked users : You can flash any ROM using Alka TWRP.
Unofficial unlocked users : You must flash Safe TWRP v2 before flashing any ROM else it will lead to hardbricking.
nonyhaha said:
I installed alka version and it is in chinese, I am trying desperately to find a way to switch language, but all the guides online point to twrp theme manager, which does not work. any guide to change language from within twrp?
I flashed Cofface twrp also and the language is still in Chinese. there is no way to add some files somewhere to change the freakin' language?
Click to expand...
Click to collapse
Re-flash Alka / Cofface TWRP, you will be greeted by a chinese text. Click on the box on the right, select English & tick mark the box above slider & swipe it.
SharkcpN said:
Yes you can use it too
1. Yes, only Alka TWRP is capable of backing up & restoring all partitions including bootloader.
2. Alka TWRP backs up EFS (IMEI) partition as well, Cofface dosent. Rest all features are same.
3. For official unlocked users : You can flash any ROM using Alka TWRP.
Unofficial unlocked users : You must flash Safe TWRP v2 before flashing any ROM else it will lead to hardbricking.
Re-flash Alka / Cofface TWRP, you will be greeted by a chinese text. Click on the box on the right, select English & tick mark the box above slider & swipe it.
Click to expand...
Click to collapse
Alka and coface give an error, can't find en.xml in the zip.
nonyhaha said:
Alka and coface give an error, can't find en.xml in the zip.
Click to expand...
Click to collapse
Go to TWRP folder in the internal storage where you have installed Themes folder, delete the entire folder.
....i lost the L boot loader...
...good afternoon...
...i flashed shantosh's rom without taking backup...
...so, i lost the stock L bootloader...
...now i see the M bootloader with cyanogenmod logo...
...it's not a problem since i flashed a lot of cm based roms, and some miui roms also, with this M bootloader...
...but i want the official bunny bootloader back...
...how can i restore it back ?
...flashing with mi flash tool maby ??
Thanks for this post cos this finally clears up my confusions.... And well I suppose Cofface is good because rooting after updates is easy....But just one question....Exactly how do I install OTAs? It seems I cant install the small 150mb ota files so I have to install the fastboot rom...But do I have to wipe system before that? Because I tried flashing 7.3.6.0 update (fastboot rom 1.1gb) without wiping system and its still showing me on 7.3.5.0.... So what exactly is the method before applying OTAs?
anshulratchet said:
Thanks for this post cos this finally clears up my confusions.... And well I suppose Cofface is good because rooting after updates is easy....But just one question....Exactly how do I install OTAs? It seems I cant install the small 150mb ota files so I have to install the fastboot rom...But do I have to wipe system before that? Because I tried flashing 7.3.6.0 update (fastboot rom 1.1gb) without wiping system and its still showing me on 7.3.5.0.... So what exactly is the method before applying OTAs?
Click to expand...
Click to collapse
You need to use recovery ROM, not fast boot.
And how to move from unofficially unlocked bootloader to official unlocking?
So here it is "Shadow kernel "
Works on pie as well as oreo
Thanks to @felix3000 its his work not mine i am just sharing
Here comes the Real deal /
The kernel wont be flashed with just going to recovery and selecting your desired options in Aroma !
First Be on a clean installed rom or flash stock boot.img
Then flash shadow ....///"dont select any options or change anything just keep tapping on next and install shadow ....
Once you reboot go to about phone there you can see shadow .
After that you can go to recovery again and flash shadow with desired options of your choice !
Link :-
https://drive.google.com/file/d/1Dzkgn1jiafyZJpzaLR0Vc-GijK6hSyz0/view?usp=drivesdk
thanks for sharing the info, - I mean the installation trick... If I'm already in the recovery of a clean flash do I have to reboot the phone before flash again?
Yes follow the above steps !
Can this kernel support new android Pie tree?
-delete