Database Users

[Tutorial] How to flash Jelly Bean on Samsung Korean Galaxy S / SHW-M110S

How to upgrade from Gingerbread WF07 to a Jelly Bean ROM on the SHW M110S
Basic Considerations that will help you to restore your current ROM ​
First make a Backup of your current ROM, such that you can return to it, IF the Jelly Bean ROM is not what you expected it to be. How?
a) When Using a tegrak Kernel on the M110S , you can get this done on the bootup screen , by entering it and making a system and also a dbdata/data backup of your phone, which can be restored by using the terak kernel again IF WF07 ROM is what suits you best.
Your backup will be placed in the Tegrak Folder in the Internal SD card...so save this to your PC or external SD card for safe keeping.
b) When using a Speedmod kernel, you need to enter recovery first to make a nandroid backup of your system and data
Your Backup will be placed in the ClockWorkMod Folder of your SD card. Which can be restored by using the speedMod kernel again IF WF07 ROM is what you desire.
None of these Kernels can be used for Jelly Bean ROM, and you need to use a Version 5 CWM (ClockWorkMOD) recovery, to flash the Jelly Bean or ICS ROM direct from your SD card...as such the first thing you need to do is change the Recovery on your M110S to a version 5 ClockWorkMOD.
Second Backup your efs folder, why? read this. How? read this
What you should know about this Jelly Bean ROM on the M110S​
a) It may take from 3 to five minutes for the ROM you flashed to stabilze, so try to be patient or you will have a non responsive phone in your hands, even when the ROM is stable.
b) When ever certain functions do not seem to work initially...like unable to connect to your WIFI, network etc just reboot phone.
c) Poor response may be due to settings or permissions that need to be fixed, which can be done on your settings menu or in the advanced menu of your recovery ...so you must have ample knowledge of the numerous features the Jelly Bean settings menu has.
The Jelly Bean ROM's for Korean Galaxy S (SHW M110S) that have little to NO issues at the moment are​
Common Issue in Jelly Bean being having NO Ringtone only vibration
Typhoonoid aokp verion 2.1.2 or here
Typhoonoid paranoid version 1.1
CM 10 All Fixed
Provisionmod All Fixed
JBean 4.2 under construction here only for testers to verify bugs
Reminder, What you do with your Phone is your own responsibility, so do it at your own risk. Always ensure your Battery is fully Charged prior to flashing any phone​
This is the basic procedure for Jelly Bean upgrade​​
1) Download the CWM Recovery.tar ( Attached below), the ROM's come in .zip format ( it can be as many as you wish, for you to test them out, one after the other) and Place them in a Folder (create and name it as you wish) on your SD Card Also Download the Gapps.zip (Google apps) File that need to be flashed after flashing the ROM. ( So it will always be two packages to flash, in order to get your phone functioning)
Download:-
a) CWM Version 5.0 Recovery attached below
b) Rom of your choosing from here or here or here Zip file includes ROM & Kernel (do not unzip)
c) Gapps Here (do not unzip)
d) Ringtone Fix here (Tested not working on M110S)
e) New 4.1.2 Kernel use Odin to flash when using older ROM
2) Flash the version 5 and up CWM recovery on your Phone, How?
Put your phone into download mode, Fireup Odin3 on your PC, connect to Odin3 with USB cable, select CWM Ver.5.0 recovery.tar under PDA and Flash it. Ensure you do not reboot the phone by "UNTICK" reboot in Odin3 such that it will not power ON after Flashing, in case it does power ON, just pull out Battery , press power button for 30 seconds and insert battery again
3) After flashing recovery with Odin, You can enter " Recovery Mode" by press VolumedownKey+PowerKey+HomeKey. You do this every-time you want to switch to a JellyBean or iCS ROM or to utilize the many features this recovery has, like Backup/restore/fix permissions and mostly to do the full wipes (NEEDED to be done every time you want to SWITCH ROMS) etc
4) Once in CWM Recovery you do the Full wipes (use your volume keys to move up or down in the recovery menu to select and the power key to execute that command).
The undermentioned wipes need to be done and will constitute a FULL Wipe of your Phone but your SD card will not be fully formatted as such your Images and other non system files will remain as is.
a) Wipe data / Factory reset
b) Wipe cache
c) Enter advanced and wipe dalvic Cache
Once the full wipes are done,
5) You now choose the ROM you placed in your SD card by selecting "Install zip from sdcard" which will lead you to "choose zip from sdcard", which will take you to all the folders you have on your SD Card..scroll down to where you placed the downloaded files and select it
Once selected the ROM will be Flashed on to your phone, so wait till it says "install completed" Now you do the same selection process again (Step 5) to select the Gapps file and wait till it says "Install completed"
6) That's it, Now select "Reboot system Now".
Now the ROM has been installed on your phone, so let it boot up and you can repeat this procedure to switch again and again till you have the best ROM of your choosing.
Solutions to solve problems, if any
In the event that it fails to boot-up or you placed a wrong ROM that caused a boot loop or any other problem, just look in My Android Solutions , IF you cannot enter Recovery mode to flash another ROM.
or ​
You can also use Odin3 to Flash a Gingerbread ROM in Download mode and use your First backup ( made by Tegrak or speedMod) to return your phone to its original state.
Ringtone Codec from this post unfortunately it seems to fail in fixing the Ringtone issue but no harm done in installing this codec
atrix4g18 said:
This is the fix for Audio/Sound on any Jelly Bean ROM on any device.
JB needs this file "/system/etc/media_codecs.xml"
This file is missing, but simply copying the file there using Root Explorer or any file explorer with root access works. This does not require a permissions change. The file is not there originally so you won't be overwriting anything. I did this fix on my Atrix 4G and it worked perfectly. It is universal and will work on any Jelly Bean ROM on any device with this issue.
Here is a link to the file:
http://forum.xda-developers.com/attachment.php?attachmentid=1207669&d=1342668760
Steps:
- Extract "media_codecs.xml"
- Copy it to /system/etc/
- Make sure to mount system as R/W (read/write) before pasting the file
- Reboot
- Sound Fixed!
Click to expand...
Click to collapse
Final Advice
IF you like the ROM you had just installed and after doing all the tweaks and adjustments you would like to try another ROM, just get back into your CWM recovery , scroll down to "backup and restore" and back it up. Such that you can restore it, if your next selection is below expectations. or you wish to tweak it further at some other time. You can have many ROM's backed up and restored whenever you like...just remember on what date you backed it up.
You , YES! you are an " Android ".
You Must watch this documentary concerning your privacy Terms & Conditions we agree to
If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

Screen Shots of Typhoonoid aokp

Screen Shots of Paranoid

Typhoonoid by ODIN? Tegrek after Typhoonoid?
oh my god, your post is amazing. thank you thank you!
Question:
your post suggests using CWM Version 5.0 to do the ROM flashing. can i use just ODIN to flash Typhoonoid? or do i have to use CWM?
also, i believe that Tegrek kernel only supports stock ROM on the M110S, which is gingerbread. after flashing Typhoonoid, is it possible to flash Tegrek kernel again? can Tegrek lagfix be applied to Typhoonoid?

md11980 said:
oh my god, your post is amazing. thank you thank you!
Question:
your post suggests using CWM Version 5.0 to do the ROM flashing. can i use just ODIN to flash Typhoonoid? or do i have to use CWM?
also, i believe that Tegrek kernel only supports stock ROM on the M110S, which is gingerbread. after flashing Typhoonoid, is it possible to flash Tegrek kernel again? can Tegrek lagfix be applied to Typhoonoid?
Click to expand...
Click to collapse
Nope, you MUST use the Version 5 CWM recovery to flash ICS or Jellybean ROM's and Nope you cannot use tegrak anymore, and lag fix (sort of ) can be done with seeder app already included in the ROM

soft bricked
xsenman said:
Screen Shots of Paranoid
Click to expand...
Click to collapse
My phone turned to Upgrade Boot Logo after failed flashing of CWM 5.0 in my phone, is there a solution for this?

asukaragnaboy said:
My phone turned to Upgrade Boot Logo after failed flashing of CWM 5.0 in my phone, is there a solution for this?
Click to expand...
Click to collapse
means still in download mode and needs a full flash of ROM or Kernel or recovery you had earlier attempted to flash
upgrade screenshot http://forum.xda-developers.com/attachment.php?attachmentid=2147778&d=1374970741

On provisionmod ram swap is not working is there any cm 10 with swap support
Please can i get lidroid rat9 wc13 screenshots.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
On provisionmod ram swap is not working is there any cm 10 with swap support
Please can i get lidroid rat9 wc13 screenshots.
Click to expand...
Click to collapse
Not too sure, the others can achieve swap support, but give it a try, it pretty easy to change ROMS and test out, which can do what lidroid screen shots may be on their website here http://bbs.lidroid.com/forum.php?mod=viewthread&tid=110092&highlight=lidroid+wc13

http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Please tell me this rom is for m110s because in all roms its written galaxy s no model no it's quite confusing.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Please tell me this rom is for m110s because in all roms its written galaxy s no model no it's quite confusing.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
yup, it works, seems there was a ver 5 too..but ver 2 was much smoother, anyways you should test it out, since my trials where way too short and incomplete

xsenman said:
yup, it works, seems there was a ver 5 too..but ver 2 was much smoother, anyways you should test it out, since my trials where way too short and incomplete
Click to expand...
Click to collapse
Sorry for asking again but i want a cm 7.2
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Is this cm 7.2 is this rom has bugs
Please tell the bugs.
Thanks for helping bro.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
Is this cm 7.2 is this rom has bugs
Click to expand...
Click to collapse
NO. its ver 4.1, meaning Jelly Bean, CM 7.2 is gingerbread/ICS combo, try looking in the links given in OP, you need to go into their parent directory and it will clearly state CM 7.2. CM 9 would be ICS , CM 10 would be Jelly Bean.
unfortunately I Have not tested them , so unable to tell you the bugs in each of them.

Oops i am sorry posted wrong link.
I know that that cm 10 is jb and 9 ics
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/Sayanogen/M110S CM7.2(TOUCHWIZ4.0).tar
This is cm 7.2 touchwiz 4 tar want to know bugs.
Thanks in advance.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
This is cm 7.2 touchwiz 4 tar want to know bugs.
Thanks in advance.
Click to expand...
Click to collapse
like i said earlier , have little knowledge about its current development or bugs, as far as I know, they stopped short of fixing bugs when CM 10 came into the picture. So best you test it out.
visit PIT STOP for 7.2 version 3 plus guide (click on original post to see screenshots and latest info) and 7.2 perfect version download from here

It means there are no bugs in 7.2cm sms fixed.zip
And there is swap support.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
It means there are no bugs in 7.2cm sms fixed.zip And there is swap support.
Click to expand...
Click to collapse
I hope so, that's what perfect should mean but may mean different in Korea so check it out.

xsenman said:
I hope so, that's what perfect should mean but may mean different in Korea so check it out.
Click to expand...
Click to collapse
Thanks for support.
Just one thing I have to flash cm7finalkernel.tar and gapps also.
There are 2 kernel tar files cm7.2oc.tar something like that help.
So there is no kernel in the zip.
Or these kernel have special features.
Thanks.
Sent from my GT-I9070 using xda app-developers app

hey bro. i'm just a little confused, what kernel should i use for a jellybean rom?

shaikhsumair99 said:
Thanks for support.
Just one thing I have to flash cm7finalkernel.tar and gapps also.
There are 2 kernel tar files cm7.2oc.tar something like that help.
So there is no kernel in the zip.
Or these kernel have special features.
Thanks.
Click to expand...
Click to collapse
looks like provision made a new kernel even for Jellybean, so it can flashed using odin3 after flashing ROM & gapps. oc means its an overclocked version
swiftcity1305 said:
hey bro. i'm just a little confused, what kernel should i use for a jellybean rom?
Click to expand...
Click to collapse
you use the one that is included in the ROM package. and can be updated with new version of that kernel later, you cannot use gingerbread kernels like (tegrak or speedmod)

[RECOVERY][ROOT]TWRP 3.1.0-1 Samsung Galaxy J3 Emerge SM-J327P

Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.

Reserved

Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro

Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.

@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it

JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.

@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app

rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.

Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app

I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?

joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?

Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.

Everything went smooth! Thank you so much!

rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.

No problems at all... Everything went perfect!

I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?

Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.

need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS

pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921

ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"

[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!

Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
​
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
After that you don't have to flash full ROM anymore.. Just always wait for the update from updater app and let it automatically reboot in to the RedWolf.
Now you can flash SuperSU or Magisk and incremental OTA's without any hustles. Use the built-in SuperSU/Magisk option for rooting your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Frequently Asked Questions
Q. I am getting Error 7 while flashing incremental OTA?
Ans: If you are really sure that you followed the installation process correctly then send us a log or screenshot and we will look at it.
Q. Can I install xposed, Viper, blah blah..?
Ans: Yes! You can install anything but make sure that you use this recovery for flashing the zip files.
Q.This recovery can be used in any ROM?
Ans: Yes! You can use this recovery in any ROM.

ATG Droid said:
Red Wolf Recovery Project
Red Wolf Recovery is custom recovery based on the TWRP source code with it's own unique features. And one of these features is also support of the MIUI Incremental OTA's! However this thing is slightly more complicated then just downloading of the zip and flashing.. You have to first enable some things for this and flash some another ZIP file etc. So that's reason why i think that it would be nice to create a guide for this. Now let's look at it...
​
Pre-requisite
Redmi Note 3 - Snapdragon version!
Common sense
Steps
Download latest build of the recovery from here. And correctly follow the installation process.
After the correct installation reboot your device in to the recovery.
Now click on the "Advanced" and then on "Special Actions".
Here enable these checkboxes:
"Support MIUI Incremental OTA" and "Include System in OTA Survival".
Now clean/dirty flash some full MIUI ROM and flash whatever you want after that.
Now reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
[SIZE="3! You can use this recovery in any ROM.
Click to expand...
Click to collapse
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.

What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk

Androbots said:
Its much better than ZCX since once zcx is replaced by official twrp then it requires full wipe so keep up the good job.
Click to expand...
Click to collapse
Can I flash this on 2gb ram variant?

lordsh said:
What is different from zcx twrp
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Look at the thread in the development section.. Here is the feature list. Anyway the main difference here is that RedWolf is based on the latest TWRP base and it also support AOSP 8.0.0 based ROMs
rohan_45 said:
Can I flash this on 2gb ram variant?
Click to expand...
Click to collapse
Yup

In ZCX the system img file (size more than 1 gb) is stored in sdcard. Do RedWolf also stores the system img file in sdcard ? (for incremental ota updates)

What if i edit build.prop...will i still be able to update incremental updates??

is that really ota update working on it??anyone tested??

umang0712 said:
What if i edit build.prop...will i still be able to update incremental updates??
Click to expand...
Click to collapse
Depends on what will you edit.

I can't save my custom settings, like reverse nav bar, system time etc. It is auto defaulted after every reboot. How can I save them?

Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.

M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys

kg hggggg tightly said:
M RN3 got bootloop . its not booting only mi logo showing what to do pls help fast as it is not my phone !! Its my fathers pls help guys. The device was running miui 8 marshmallow one. I did flashed correctly twrp also boot up but then I selected reboot to system from within twrp and it doesn't boot to system . What to do pls help. No offence to the twrp recovery developer but I need help pls ? Guys
Click to expand...
Click to collapse
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me

dudemathai said:
Dude I got the same problem, download lazyflasher zip file ,flash it through twrp ,and reboot,it worked for me
Click to expand...
Click to collapse
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?

kg hggggg tightly said:
Ya i understood so that means that if i want to flash custom rom will i need to flash lazyflasher whenever i flash a custom rom?
Click to expand...
Click to collapse
I don't think you need to flash it when you change roms,what I know is that lazyflasher bypasses miui so that you won't be stuck in bootloop while you flash anything into miui

otyg said:
Awesome recovery looks great, but I will downgrade to ZCX until the "bad app" checking is fixed.
Thanks.
Click to expand...
Click to collapse
What problem are you facing? This recovery seems better and updated than ZCX.
Sent from my Redmi Note 3

can i use magisk with this?

rs168 said:
can i use magisk with this?
Click to expand...
Click to collapse
Yes

is this support with newest miui 9..?

xerocracker said:
is this support with newest miui 9..?
Click to expand...
Click to collapse
Yes
Sent from my Redmi Note 3 using XDA Labs

[ROM][Android 12][sirius] crDroid v8.2 [26.02.2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
<!-- change according to your needs -->
Backup your data to PC, OTG flash drive
Now reboot to recovery
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Flash crDroid zip
Flash recovery from the download link
Reboot to system
Update installation:
<!-- change according to your needs -->
Boot to recovery
Flash a zip with crDroid
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm710
Download:
ROM https://crdroid.net/sirius>
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/12.0/changelog_sirius.txt
Known issues:
[*]None
Visit official website @ crDroid.net
crDroid sirius Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

thanks for you great work.

Is the face unlock work?

Yes it is.
-----
Love thise ROM thanks for you great work.
Only thing it miss is buld in call record.

Could anybody get OP's twrp from https://t.me/uixdessDrive/20 and upload to here?
I use latest official TWRP, this ROM installs and works like charm. but I can't boot into twrp ever after, it stuck at TWRP's logo screen forever.
I guess it's because this ROM flashes new keymaster partition which crashes official twrp.
Anyway I should try TWRP posted by OP but can't download from that link. Could anyone help?

NexusRunner said:
Could anybody get OP's twrp from https://t.me/uixdessDrive/20 and upload to here?
I use latest official TWRP, this ROM installs and works like charm. but I can't boot into twrp ever after, it stuck at TWRP's logo screen forever.
I guess it's because this ROM flashes new keymaster partition which crashes official twrp.
Anyway I should try TWRP posted by OP but can't download from that link. Could anyone help?
Click to expand...
Click to collapse
I tried to attach it here but not uploaded i don't know why.

yamabokra01 said:
I tried to attach it here but not uploaded i don't know why.
Click to expand...
Click to collapse
Could you upload it to MEGA?

NexusRunner said:
Could you upload it to MEGA?
Click to expand...
Click to collapse
Don't use it.
I just flash it then I got bootloop + no recovery + no bootloader.
Now I'm trying to open the back of the device to put it in edl mode

yamabokra01 said:
Don't use it.
I just flash it then I got bootloop + no recovery + no bootloader.
Now I'm trying to open the back of the device to put it in edl mode
Click to expand...
Click to collapse
omg wish your device recovered soon
I flashed the ROM using official twrp. It went OK but no longer boot into twrp.
I managed to install magisk without recovery (by patching and fastboot flash boot.img), but can't install gapps without a working recovery.
Maybe I should start over again and try the other A12 ROM with built in gapps. But for now I feel good with this ROM. I think maybe I will try it without gapps for a little longer.

NexusRunner said:
omg wish your device recovered soon
I flashed the ROM using official twrp. It went OK but no longer boot into twrp.
I managed to install magisk without recovery (by patching and fastboot flash boot.img), but can't install gapps without a working recovery.
Maybe I should start over again and try the other A12 ROM with built in gapps. But for now I feel good with this ROM. I think maybe I will try it without gapps for a little longer.
Click to expand...
Click to collapse
I payed 30$ and recovered my mobile.
Then i flashed a rom and for the second time i flashed the recovery again and my mobile again dead

UIxDess said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
<!-- change according to your needs -->
Backup your data to PC, OTG flash drive
Now reboot to recovery
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Flash crDroid zip
Flash recovery from the download link
Reboot to system
Update installation:
<!-- change according to your needs -->
Boot to recovery
Flash a zip with crDroid
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm710
Download:
ROM https://crdroid.net/sirius>
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/12.0/changelog_sirius.txt
Known issues:
[*]None
Visit official website @ crDroid.net
crDroid sirius Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Click to expand...
Click to collapse
Dear, I flashed the rom 3 times and followed the instructions, but I get loopboot + no rom + no recovery + no bootloader, meaning dead device. The from edl flash China Rom.
Do I have to be in certain FW? Or do I have to flash something before I start the process for this ROM??

yamabokra01 said:
Dear, I flashed the rom 3 times and followed the instructions, but I get loopboot + no rom + no recovery + no bootloader, meaning dead device. The from edl flash China Rom.
Do I have to be in certain FW? Or do I have to flash something before I start the process for this ROM??
Click to expand...
Click to collapse
I don't encouter anything special except I can't boot back to recovery after boot into this ROM
I flash FW from sirius_images_V12.5.1.0.QEBCNXM_20210625.0000.00_10.0_cn_0969fb8c9f.tgz (which is the latest stable stock ROM)
And use twrp-3.6.1_9-0-xmsirius.img (which is the latest official twrp from https://twrp.me/) to install crDroidAndroid-12.0-20220226-sirius-v8.2.zip

NexusRunner said:
I don't encouter anything special except I can't boot back to recovery after boot into this ROM
I flash FW from sirius_images_V12.5.1.0.QEBCNXM_20210625.0000.00_10.0_cn_0969fb8c9f.tgz (which is the latest stable stock ROM)
And use twrp-3.6.1_9-0-xmsirius.img (which is the latest official twrp from https://twrp.me/) to install crDroidAndroid-12.0-20220226-sirius-v8.2.zip
Click to expand...
Click to collapse
I will try now and report. Thanks bro

NexusRunner said:
I don't encouter anything special except I can't boot back to recovery after boot into this ROM
I flash FW from sirius_images_V12.5.1.0.QEBCNXM_20210625.0000.00_10.0_cn_0969fb8c9f.tgz (which is the latest stable stock ROM)
And use twrp-3.6.1_9-0-xmsirius.img (which is the latest official twrp from https://twrp.me/) to install crDroidAndroid-12.0-20220226-sirius-v8.2.zip
Click to expand...
Click to collapse
Appreciate it bro. at least I update the device and finished my 3 day fighting with this device

Bro this rom is amazing.
I have found a bug.
Double Tap Screen Wake doesn't work after when screen goes sleep about 10+ second later.
Screen doesn't wake up bro.
God bless you.
Edit
When pocket mode is on, it works fine.

Sure you can highly customize settings with this ROM. But experiences are not good enough. One Setting may collapse another; the number in the battery icon is hard to be recognized...It needs a product manager. If mobile phones get more standardized one day, it may be less hard to mantain a unified UI, just like gnome desktop on PCs.

yamabokra01 said:
I payed 30$ and recovered my mobile.
Then i flashed a rom and for the second time i flashed the recovery again and my mobile again dead
Click to expand...
Click to collapse
my problem is same as yours, how to fix it? I am a student currently I am having difficulty. Help me please.

12

[ROM][13.0][TOCO][UNOFFICIAL] Evolution X 7.1 | Eve

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Evolution X 7.1 for the Xiaomi Mi Note 10 Lite [toco]
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
- Have the latest Global stable MIUI v13.0.2.0 installed
- Make sure you're running TWRP or OrangeFox for Android 13
- Boot into recovery
- Copy Rom
- Flash Rom
- Format data
- Reboot to system & #KeepEvolving
Update / Dirty Flash
- Boot into recovery
- Flash Rom
- Wipe Dalvik Cache & Cache
- Reboot to system & #KeepEvolving
Download
Donate me! / Official Chat / Device Support​
Android version: 13.0.0_r6
Evolution version: 7.1
Security patch level: September 2022
Build Author: AndroidHQ254
ROM Source: [URL]https://github.com/Evolution-X[/URL]
Kernel Source:: VantomKernel
ROM Developer: Joeyhuab
XDA:DevDB Information
Evolution X, ROM for the Xiaomi Mi Note 10 Lite
Contributors
AndroidHQ254, @NeoArian
Source Code: https://github.com/Evolution-X
ROM OS Version: Android 13
ROM Kernel: Linux 4.14.292
ROM Firmware Required: Latest Stable MiUI v13.0.2.0 (Android 12)
Based On: AOSP
Version Information
Status: Stable
Created 2020-09-22
Last Updated 2022-09-22

Dirty flash is available/possible when I'm update from A.12.1 of evoX?

kavillock said:
Dirty flash is available/possible when I'm update from A.12.1 of evoX?
Click to expand...
Click to collapse
NO. This requires a clean flash

i wanted to ask befor i upgrade from omega is it stable and dose it have ay removed features , especially the spoofing for free google photos , i wish to daily this rom and thats why i want to know about the experience

I have evox Snow, but I do not remember the latest installed miui. Is there a way to check it?

i flashed it and it boots but i get a black screen the os is on i belive cause holding the pwoer button makes my phone slightly vibrate so idk whats hapening

Alenett said:
I have evox Snow, but I do not remember the latest installed miui. Is there a way to check it?
Click to expand...
Click to collapse
You need Global MIUI 13.0.2.0 and this is specified in the post

Fox_it3 said:
i wanted to ask befor i upgrade from omega is it stable and dose it have ay removed features , especially the spoofing for free google photos , i wish to daily this rom and thats why i want to know about the experience
Click to expand...
Click to collapse
It would not be shared here if it were not stable

Fox_it3 said:
i flashed it and it boots but i get a black screen the os is on i belive cause holding the pwoer button makes my phone slightly vibrate so idk whats hapening
Click to expand...
Click to collapse
Ensure you perform a proper clean flash on the right base and make sure you are formatting data using the specified TWRP or OrangeFox for Android 13

AndroidHQ254 said:
Ensure you perform a proper clean flash on the right base and make sure you are formatting data using the specified TWRP or OrangeFox for Android 13
Click to expand...
Click to collapse
I've installed the orange fox for Android 13 roms and had a bug that caused the data partition not being able to mount and it wouldn't flash any rom so i had to downgrade , but ill try it again in the near future, so i need to update my orange fox then clean install the android 13 rom

Fox_it3 said:
I've installed the orange fox for Android 13 roms and had a bug that caused the data partition not being able to mount and it wouldn't flash any rom so i had to downgrade , but ill try it again in the near future, so i need to update my orange fox then clean install the android 13 rom
Click to expand...
Click to collapse
If you are on Android 13, you should not have any mounting issues unless you have something messed up. Keep in mind that the recoveries are tested extensively before posting

I am on Android 12 as for this moment, i have the Evo x 6.5 omega.

AndroidHQ254 said:
You need Global MIUI 13.0.2.0 and this is specified in the post
Click to expand...
Click to collapse
I know that, but it is not the question i did. Simply i can avoid to reflash the original MIUI if i know the version i have already installed previously. Anyway i reflashed the original firmware before installing evox 7.1 to be sure.

Fox_it3 said:
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
Click to expand...
Click to collapse
There is a separate recovery for each Android version. So I don't understand why you are using an OrangeFox for Android 13 on Android 12. Stick to the specifications and follow instructions

Alenett said:
I know that, but it is not the question i did. Simply i can avoid to reflash the original MIUI if i know the version i have already installed previously. Anyway i reflashed the original firmware before installing evox 7.1 to be sure.
Click to expand...
Click to collapse
Just flash the latest firmware if you are not sure what you have. You don't need to flash the entire MIUI 13.0.2.0 stock rom

AndroidHQ254 said:
Just flash the latest firmware if you are not sure what you have. You don't need to flash the entire MIUI 13.0.2.0 stock rom
Click to expand...
Click to collapse
It is what i did.

Alenett said:
It is what i did.
Click to expand...
Click to collapse
All working great I hope

Fox_it3 said:
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
Click to expand...
Click to collapse
- Install latest TWRP you can find in the other thread (using fastboot).
- Flash the lastest MIUI via adb sideload and perform a format data (backup your data before this).
- Reboot to system and let the MIUI to run.
- When the MIUI is ready (on the welcome page), reboot the phone in fastboot.
Then:
- Flash the TWRP again via fastboot (the MIUI restore the standard boot).
- Reboot in recovery mode (TWRP).
- Flash the new evox via adb sideload
- Format data
Reboot to system.
There is nothing else to do or explain. It must works.
Evox 7.1 works a lot better then 6.5. I have a good improvement in performance and battery life.
If you want to root when you have configured the phone and it is ready to be used:
- install root explorer from google play store
- download and install magisk app downloading the apk from github and installing it by root explorer (i recommend to not allow the browser to install apks).
- on the pc, extract the boot.img from the evox zip.
- attach the phone to the pc and transfer the boot.img to the phone.
- run magisk and patch the boot.img
- transfer the patched image to the pc
- reboot the phone in fastboot
- flash the patched boot.img via fastboot
- reboot to system
Enjoy!

Alenett said:
- Install latest TWRP you can find in the other thread (using fastboot).
- Flash the lastest MIUI via adb sideload and perform a format data (backup your data before this).
- Reboot to system and let the MIUI to run.
- When the MIUI is ready (on the welcome page), reboot the phone in fastboot.
Then:
- Flash the TWRP again via fastboot (the MIUI restore the standard boot).
- Reboot in recovery mode (TWRP).
- Flash the new evox via adb sideload
- Format data
Reboot to system.
There is nothing else to do or explain. It must works.
Evox 7.1 works a lot better then 6.5. I have a good improvement in performance and battery life.
If you want to root when you have configured the phone and it is ready to be used:
- install root explorer from google play store
- download and install magisk app downloading the apk from github and installing it by root explorer (i recommend to not allow the browser to install apks).
- on the pc, extract the boot.img from the evox zip.
- attach the phone to the pc and transfer the boot.img to the phone.
- run magisk and patch the boot.img
- transfer the patched image to the pc
- reboot the phone in fastboot
- flash the patched boot.img via fastboot
- reboot to system
Enjoy!
Click to expand...
Click to collapse
Thanks i must have missed this for sure , im pretty basic at this custom rom stuff thanks a lot

Double tap to wake does not work after ~5 seconds after screen off (after the always on display dims down)
* Might be related to a broken screen replacement.
* I DID verify that the problem is a software problem - flashed xiaomi.eu rom and it DOES work there.
* I'm NOT at all sure it worked even with original screen (screen was fully functional, just a few cracks in the glass)
Update:
Tried derpfest and project elixir, same problem.
also found this on pixel-experience github issue tracker...
exactly the same issue - AOD becomes too dim and tap to wake stops working.
seems it's a known problem.