Related
Here is a CWM-Based Recovery built from source for use with either Honeycomb or Gingerbread hboot.
Thanks to Team Revolutionary for their CWM4 Recovery and DooMLoRD for his Custom CWM-Based Touch Recovery 5.0.2.7 which I used to set up the board config and makefiles.
To install place the recovery.img in your fastboot directory and type the following commands into a terminal;
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Flyer CWM-Based Recovery 6.0.1.1 GB.zip - 4.92 MB
MD5: 5f8bc34e44eaeccaf320f89cecca5e52 (for .img not .zip)
Flyer CWM-Based Recovery 6.0.1.1 HC.zip - 5.02 MB
MD5: 30b5bf5952ceba8fbab02f54b39da4df (for .img not .zip)
Click to expand...
Click to collapse
Koushik Dutta said:
New ClockworkMod Backup Format
TL;DR:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Click to expand...
Click to collapse
Thanks, I couldn't get if that is touch enabled or not.
teorouge said:
Thanks, I couldn't get if that is touch enabled or not.
Click to expand...
Click to collapse
I dont have access to the touch based repos as they're closed at the moment so I'm afraid for now this recovery is old school. The "change log" Koushik posted on his Google+ was enticing enough to try it out though!
Koushik Dutta said:
Backups are much faster. 4-5x faster. (Bug fix due to excessive status updates of the UI and new backup technique)
Incremental backups are smaller. Way way smaller. Only 15-20MB each for each additional backup of a ROM. This is done using a new tool I wrote to dedupe the files between incremental backups to eliminate duplicates.
Click to expand...
Click to collapse
a quick note for those who wonder.
Aroma installer does not work with touch, without the touch enabled and ntrigd running in recovery. but thats just so you know.
so thats key controlled too.
Can someone make a flashable zip?
Dexter_nlb said:
a quick note for those who wonder.
Aroma installer does not work with touch, without the touch enabled and ntrigd running in recovery. but thats just so you know.
so thats key controlled too.
Click to expand...
Click to collapse
Just to clarify, Aroma will still work manually with the volume keys and power button I assume? Thanks for the heads up.
lekhwani said:
Can someone make a flashable zip?
Click to expand...
Click to collapse
I'll check that out now.
What do i gain with flashing this ower ver. 5.?
Thx!
jprednik said:
What do i gain with flashing this ower ver. 5.?
Thx!
Click to expand...
Click to collapse
5.0.2.8 is the most up to date recovery version on the gingerbread branch at the moment. These 6.0.0.x versions are from the ics and jellybean branches. To my knowledge I don't think Koushik posts "changelogs" on the various recovery updates but he's made a few posts talking about version 6 of ClockworkMod Recovery here and here.
I have Gingerbread.
So Work well with GB ? --- >HTC Flyer - CWM-Based Recovery 6.0.0.7 - GB.zip - 4.92 MB
What are the improvements.
Thanks
No offense but what is the point of this ?!.
lekhwani said:
Can someone make a flashable zip?
Click to expand...
Click to collapse
There is no touch support when flashed and Power button actually switched the screen OFF, so it is pretty useless. The DormLord touch -based CWN is just perfect as it is. There is no serious ICS ROM to flash anyway, so I do not understand why cripple this CWN when there is no real value here.
Max128 said:
I have Gingerbread.
So Work well with GB ? --- >HTC Flyer - CWM-Based Recovery 6.0.0.7 - GB.zip - 4.92 MB
What are the improvements.
Thanks
Click to expand...
Click to collapse
The GB version will work with the Gingerbread hboot. Check out the previous posts to read up on the changes.
fteo_viking said:
There is no touch support when flashed and Power button actually switched the screen OFF, so it is pretty useless. The DormLord touch -based CWN is just perfect as it is. There is no serious ICS ROM to flash anyway, so I do not understand why cripple this CWN when there is no real value here.
Click to expand...
Click to collapse
Flash the recovery.img manually through fastboot if you're having problems. If you look at the ClockworkMod site a lot of devices don't have ClockworkMod Recovery 6 or a Touch supported version at all. The Flyer has never had an officially supported ClockworkMod Recovery anyway. I wanted to check out version 6 myself and put these up in case anyone else wanted to as well. It's not for everyone as there won't be a ClockworkMod Touch Recovery without an ICS kernel or until DooMLoRD and Team UtterChaos port their Touch UI to the ics branch. If you don't want to use it don't.
I have a WiFi + 3g Flyer and with recovery 6.0.1.0 the power button doesn't work, so I'm not able to use it...
nikoan89 said:
I have a WiFi + 3g Flyer and with recovery 6.0.1.0 the power button doesn't work, so I'm not able to use it...
Click to expand...
Click to collapse
If the text options disappear when you press the power button press it again so they return then press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
revert back to 4.0.1.4
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery.
Any ideas?
UPDATE: I ended up changing to Doomlords 5.0.2.7 and it works great.
nikoan89 said:
I don't have this kind of issue, mine is that power button in recovery mode simply doesn't work, all the text options still on screen, I'm only able to navigate with the volume buttons but I'm not able to select them.
EDIT: I've fix it holding the power button and pressing repeatedly the vol down button, now it seems to work
Click to expand...
Click to collapse
Work for me with this method. Thinks.
mkintop said:
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery.
Any ideas?
UPDATE: I ended up changing to Doomlords 5.0.2.7 and it works great.
Click to expand...
Click to collapse
I had the same problem, took me several hours to figure out how to re-flash to 5.8.3.1.
This one is not good.
nikoan89 said:
I don't have this kind of issue, mine is that power button in recovery mode simply doesn't work, all the text options still on screen, I'm only able to navigate with the volume buttons but I'm not able to select them.
Click to expand...
Click to collapse
mkintop said:
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery. Any ideas?
Click to expand...
Click to collapse
oushouseki said:
I had the same problem, took me several hours to figure out how to re-flash to 5.8.3.1.
This one is not good.
Click to expand...
Click to collapse
I enabled the "BOARD_HAS_NO_SELECT_BUTTON" flag in BoardConfig.mk and now the power button works as soon as recovery boots. No need to toggle between "Back menu button disabled" and "Back menu button enabled" anymore.
If the recovery doesn't boot properly and hangs at the splash screen use "fastboot erase cache". Similarly, if you want to flash any other recovery use the commands in the OP.
Code:
adb reboot bootloader
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot
Can someone make a flashable zip?
THX
I would like that too...
i am a hardcore noob so bear with me.
What is a terminal and how and where to i type that?
can somebody please explain!
Ok, first i wanna say, maybe there's many of you knew this way, but i created this thread for noob like me, hope you like
What you need
- L9 with unlock bootloader
- and of course it's Rooted
- Download Flashify from playstore
- Download one of The Recovery from here
TWRP 2 .6.1.0 Thread is Here
TWRP 2 .6. 1.0 for P768
TWRP 2 .6. 1.0 for P765 & 760
ClockWorldMod 6.0.4.x by artas182x Thread is Here
Only for P765 & 760
Touch Clockworldmod Thread is Here
Test on P769
How to install
- Open the Flashify app
- Give root permission
- Choose Recovery Image
- Choose a File
After the installation done, the phone will reboot
now you have new recovery
note: I'm not the creator of the recovery images and the application, if you to give Donations, give it to the creator, not to me, I'm just sharing how to install it
And Do With Your Own Risk
Don't forget to hit THANKS buttons
It worked fine on my p778g
rezarpado said:
It worked fine on my p778g
Click to expand...
Click to collapse
happy to hear that
don't forget to hit THANKS buttons
[RECOVERY] TWRP 2.8.7.x - TeamWin Recovery Project
TeamWin is proud to present TWRP 2.8.7.x for the Samsung S4 Mini Plus (64-Bit ONLY) (I9195I)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Support Status: Current
Maintainer: None
Code Name: serranoveltexx
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Serranoveltexx Download
( I am posting this on behalf of TeamWin with permission of Dees_Troy)
Some more information on the new variant.
Click Here For More Information
Is it possible to install and run this recovery without breaking the knox fuse ?
JackyJack said:
Is it possible to install and run this recovery without breaking the knox fuse ?
Click to expand...
Click to collapse
Not sure, both of my devices are tripped already.
I applied this on my i9195i and did got root/su
After a reboot it got bricked and now it keeps rebooting into TWRP recovery after this message:
kernel is not seandroid enforcing
set warranty bit: kernel
Click to expand...
Click to collapse
Edit:
Dunno what went wrong but re-installed stock rom ( I9195IXXU1AOD2 ) and re-applied twrp 2.8.7.1 with Odin. Had to update su binaries from Play Store (SuperSU) before i got root.
Try and reflash twrp recovery via Odin
Probably no cyanogen mod for this., this phone is so unpopular I am afraid a custom rom will never be released. Thanks for the recovery+root though
I also have problems installing the xposed framework after root. Everytime I try to install the framework i get the "kernel is not seandroid enforcing, set warranty bit: kernel" error.
KeesKaas said:
Probably no cyanogen mod for this., this phone is so unpopular I am afraid a custom rom will never be released. Thanks for the recovery+root though
I also have problems installing the xposed framework after root. Everytime I try to install the framework i get the "kernel is not seandroid enforcing, set warranty bit: kernel" error.
Click to expand...
Click to collapse
So does xposed not work yet on the s4 mini plus?
Seconding this, no xposed for the "plus" version?
Its too bad theres no CM for the 919xi with the Quad core, seems you cant even get the old versions with dual core any more, just had mine replaced and got the quad one.. so either have to sell it or im effed
How to know if my phone is 64 bit ?
Is it possible to change ?
I've updated the TWRP recovery, it supports brightness and additional partitions to backup now, as well as a few minor changes and optimizations for our device. Thanks to Dees_Troy for taking the time to integrate my changes into the official version of TWRP.
NxtGenCowboy said:
[RECOVERY] TWRP 2.8.7.x - TeamWin Recovery Project
Click to expand...
Click to collapse
Any chance you could support our device GT-I9195?
This looks promising. How do I install this though on my GT-i9195i?
And is a Cyanogenmod available too?
Hope someone can help me out.
Kind regards,
Dennis
Thanks, works like a charm. I wish there would be more funny things for this phone. It's cheap and quite good actually :highfive:
Tried installing twrp-2.8.7.1-serranoveltexx.img thru the TWRP manager, it said it was unsuccessful. Nothing broke thankfully. I saw 3.0.0.0 in the list too, but couldnt find any info about it anywhere. Now im too scared to try other methods.
Phone is rooted with kingroot.
I need TWRP for (Samsung Galaxy S4 Mini 32bit (serranoveltexx)) because the 64bit doesn't work for me !
look for rom i9195i
hi, sorry for ask!
does anyone know if there is a ROM for this device? i9195i 64bit
inviv said:
hi, sorry for ask!
does anyone know if there is a ROM for this device? i9195i 64bit
Click to expand...
Click to collapse
No and there propably never will be as this device is not as popular and uses different CPU structure so only if a willing dev decides to support the phone there will be a rom
---------- Post added at 02:56 PM ---------- Previous post was at 02:53 PM ----------
Safest way I found for flashing recovery is downloading the twrp.img file from the net and flashing it with flashify . Worked like a charm full root access through kingroot ->SuperSUme . Only thing is I get recovery is not seandroid enforcing warranty bit: recovery which hasn't caused any real problem so far flashing works, backups work, xposed is recommended after adding twrp and using monsterui module to get the lollipop like feel . also flashing the recovery doesn't wipe the download mode for odin so it's safe to go
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
ahmedghazi said:
I need TWRP for (Samsung Galaxy S4 Mini 32bit (serranoveltexx)) because the 64bit doesn't work for me !
Click to expand...
Click to collapse
Search the forums for your model which is serranoltexx and follow instructions there
inviv said:
hi, sorry for ask!
does anyone know if there is a ROM for this device? i9195i 64bit
Click to expand...
Click to collapse
There actually is a ROM.. Check my thread: "[index] s4 mini plus" http://forum.xda-developers.com/showthread.php?t=3283053
Sent from my GT-I9195I using XDA-Developers mobile app
NxtGenCowboy said:
Code Name: serranoveltexx
Click to expand...
Click to collapse
Stupid question from my side:
The code name that I know is serranoltexx. Why is it serranoveltexx for TWRP?
I have ported EFIDroid (developed by @m11kkaa) for the Nexus 5.
@m11kkaa's original EFIDroid thread here: https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466.
This is an unofficial port of beta software. I am not responsible for anything that may happen to your device. Use at your own risk.
NOTE: This has been tested with last LineageOS Build (21/03/2017) and TWRP 3.1.0-0. All other configurations are untested by me, but should work.
Working ROMs
[Here I will post the ROM's that are working for multiboot (Of course I will need people's feedback to fullfill this list)]
LineageOS 14.1 (As primary, as secondary with SELinux permissive option)
DU 11.2 (As primary, as secondary with SELinux permissive option) tested by @AndresOrue
PureNexus 7.1.1 (Should work as primary but not tested, as secondary with SELinux permissive option) tested by @AndresOrue
Lineage OS DarkRom by Dark_Eyes (As primary, not tested as secondary-should work with SELinux permissive option) tested by @willyinpr4u
AlmostVanillaAOSP Marshmallow (As primary, not tested as secondary-should work with SELinux permissive option) tested by @alessio89g
AOSP Nougat (Should work as primary but not tested, as secondary with SELinux permissive option) tested by @alessio89g
UntouchedAOSP 6.0.1 tested by @BreckZeBoulay
MiUI 8 tested by @sa4ni
Euclidean OS tested by @willyinpr4u
Xenon HD AOSP tested by @willyinpr4u
AICP 12.1 7.1.2 tested by @phpbb3
Elixr-hammerhead-V1.1-20140420 tested by @playerkirk1
Plasma-Mobile tested by me
Installation
Install the attached EFIDroid Manager apk. Since this is an unofficial port, the EFIDroid Manager app from the Play Store won't work. (This is modified to use my unofficial server)
Open the EFIDroid Manager app, open the menu (at the top left), and click "Install/Update".
Click the big orange Install button.
And voila, you're done in 3 easy steps! Reboot to see your new 2nd-stage bootloader!
Post below with your installed ROM if you have success.
To update EFIDroid, just repeat step 2, and the click the big orange Update button.
The app won't automatically check for updates, so I'll post an announcement on this thread whenever an important update is available.
Migrating from MultiROM
TWRP Backups should work fine but as /sdcard gets mocked on TWRP for secondary ROMs to prevent an "accidental" wipe there is some steps to follow
1-Create a new slot
2-Go to /data/media/0/multiboot/your_new_slot/data
3-Create folder media/0/TWRP/BACKUPS
4-Move/copy your backup to the created folder -remember the backup folder is the one that look like a hash (like "'03480ffg04395g234")
5-Boot TWRP from EFIDroid for the new slot
6-Format System
7-Flash your backup
Multibooting
You can use EFIDroid as a multiboot manager. To add a multiboot ROM, do the following:
Open the EFIDroid Manager app. Press the plus button at the bottom right side of the screen to start adding a multiboot slot.
Under "Location", there should be a couple paths. Select the one containing "/data/media/0".
You can give the slot a name/description by using the appropriate fields.
Press the checkmark at the top right side of the screen to create the multiboot slot.
Reboot. When EFIDroid comes up, select TWRP, then select the newly created slot.
Go to the "Wipe > Advanced Wipe" menu. Select "System", then swipe to wipe.
Install all the zips you want on that slot.
NOTE: To prevent accidentall data loss when booting in recovery the real /sdcard gets mocked so you are not going to find your .zips as usual under TWRP's /sdcard. To acces the "real" /sdcard go to /multiboot/data/media/0
Reboot, and when EFIDroid comes up, your new slot should automatically be selected. Press the power button to boot, and enjoy!
IMPORTANT:your main ROM should boot without changing any configuration on EFIDroid but secondary ROM's are used to fail because of selinux denials. I strongly reccomend you to enable Force SELinux to permissive under EFIDroid options (the Gear icon in the main screen placed at the top right) - Once you kwon your secondary ROM is working you can try to boot without this option disabled - If you end up in a bootloop logcat and dmesg are welcome.
Troubleshooting
If you are unable to boot the OS/recovery from EFIDroid, do the following (you do have a working boot.img (from your main OS) and recovery.img (TWRP 3.1.0-0 recommended), right?)
This assumes you have fastboot properly setup. (Ubuntu: sudo apt-get install android-tools-fastboot - Windows: just google for the binaries)
OPTION 1:
In EFIDroid, use the volume keys to navigate to "Fastboot", the press the power key to select it.
There should only be one entry in the Fastboot menu. Press the power key to select it.
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot oem exit
In EFIDroid, use the volume keys to navigate to the back button at the top of the screen. Press the power key to select.
Use the volume keys to navigate to "Reboot", then press the power key to select.
OPTION 2:
Enter LG's Fastboot Mode (Volume Down + Power Off)
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot reboot-bootloader
Use the volume keys to navigate and select "Start" or "Recovery", then press the power key to select.
You should be able to boot the installed OS/recovery now. If this doesn't work, you can always enter Fastboot Mode (Volume Down + Power Off) and then flash your recovery and boot from there.
Clarifications
When Installing EFIDroid boot and recovery partitions are flashed so you only can enter recovery through EFIDroid to prevent any confusion
To enter Recovery just select your recovery on EFIDroid and then select the ROM you want the recovery to apply the .zip you are going to flash (EFIDroid properly patches TWRP ramdisk to affect the desire slot/ROM)
How does this work?
Well I'm going to explain it a little:
Right now you have your ROM kernel (boot.img) custom or stock ( it don't mind) in your boot partition and your recovery.img (I think TWRP) in your recovery partition. UEFIDroid is a kernel but it is not a linux kernel, it's based on Little Kernel aka LK... Qualcom port LK to Snapdragon chipsets and developed their custom bootloader, then the EFIDroid developer take this and implemented UEFI over the Qualcom's LK port.
Whe you install EFIDroid this is what happens:
-EFIDroid Manager backups your boot.img and recovery.img in /data/media/0/UEFIESP folder
-EFIDroid Manager flash EFIDroid in your boot and your recovery partitions (the recovery is flashed to prevent you using your recovery without booting it from EFIDroid)
Then the next time you boot the stock bootloader aka aboot loads UEFIDroid that is flashed in your boot partition, LK kernel boots and execute UEFI. Then the UEFI looks for the original boot.img (for booting your actual ROM aka Internal) and looks for your actual recovery.img, remember both were saved into /data/media/0/UEFIESP.
And finally it looks for slots/ROMs in /data/media/0/multiboot (of course these are the slots for multibooting a lot of ROMs).
A slot for a ROM is composed by a data folder, a system.img(1GB) and a boot.img (these are the ones used/mounted to boot the ROM you select in multiboot menu) -slots are added from EFIDroid Manager app.
In the last step it shows you the Menu to select what you want to boot and it applies the propers patchs to ramdisk to use the correct data folder and system.img, then boot the correct boot.img using libboot (the usually used by android bootloaders)
Recoveries
I personally tested EFIDroid with TWRP and TWRP CAF in their 3.1.0.0 versions and they worked great.
As I stated before, your current recovery is backed up to /data/media/0/partition_recovery.img so if you somehow ended having trouble to boot your recovery, you can boot to your main OS and replace /data/media/0/partition_recovery.img with another recovery (ofc change the name of the new recovery to partition_recovery.img) - YOU NEED A ROOT BROWSER -
Custom Kernels
Well custom kernels are known to break things, so to say that a ROM is working I need you to test with the stock kernel that comes with it, then of course if you want to test custom kernels you're welcome and I will update this post with your feedback.
NOT WORKING CUSTOM KERNELS:
ElementalX 7.09 (Don't pass EFIDroid boot Splash Screen) tested by @AndresOrue with DU 11.2 (It should not matter because it's not booting the ROM at all) -may be ramdisk patching problem-
WORKING CUSTOM KERNELS:
BluSpark r122 tested by @AndresOrue
Franco.Kernel r105 tested by @alessio89g
ElementalX 8.00 tested by me
Credits
-All credit goes to @m11kkaa for doing all the hard work in developing EFIDroid.
-@abraha2d for the help with porting and giving permission to use his post for Note 4 as the base for this one!
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
EFI Specification: 2.60
Beta Release Date: 2017-03-27
Created 2017-03-28
Last Updated 2017-04-17
-Initial Release 2017-03-27
Bugs:
ElementalX 7.09 Kernel not booting (may be ramdisk compression incompatibility)
Screen blinks when using AROMA Installers in TWRP (no details) - AROMA Installer is usable but in a very annoying way :/
Flashable scripts logs are not shown in TWRP console when flashing in a secondary ROM (no details)
Thank you mate for it, i will try it as soon as i can and i let you know how it works.
Edited: app installed, works ok so far
Edit2: @lukss12 mate the new boot Menu works but the phone don't boot anymore. I don't try to install new roms only reboot the phone but it only says rebooting android 7.1.1 internal .
I solved the problem, i dirty flash my rom ( du 11.2).
My rom: DU 11.2 android 7.1.1
Anyway at night i will try again
The prospect of an alternative to multirom is exciting. The great hammerhead lives on!
AndresOrue said:
Thank you mate for it, i will try it as soon as i can and i let you know how it works.
Edited: app installed, works ok so far
Edit2: @lukss12 mate the new boot Menu works but the phone don't boot anymore. I don't try to install new roms only reboot the phone but it only says rebooting android 7.1.1 internal .
I solved the problem, i dirty flash my rom ( du 11.2).
My rom: DU 11.2 android 7.1.1
Anyway at night i will try again
Click to expand...
Click to collapse
Great you could solve ur problem, yes flashing boot.img from your actual ROM will boot the device. Remember EFIDroid is also installed in your recovery partition, you can boot TWRP from there but if you want to revert back to "stock" DU with TWRP you need to flash TWRP to recovery partition.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
Did you try to set Force Selinux permissive option in Efidroid?
Also for the internal ROM you can try unpatched boot... For this boot efidroid and long press the power button on the Entry for your ROM.
lukss12 said:
Great you could solve ur problem, yes flashing boot.img from your actual ROM will boot the device. Remember EFIDroid is also installed in your recovery partition, you can boot TWRP from there but if you want to revert back to "stock" DU with TWRP you need to flash TWRP to recovery partition.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
Did you try to set Force Selinux permissive option in Efidroid?
Also for the internal ROM you can try unpatched boot... For this boot efidroid and long press the power button on the Entry for your ROM.
Click to expand...
Click to collapse
Did you try to set Force Selinux permissive option in Efidroid?
No i will try it at night.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
For me 5 min and nothing.
Also i need to read a little more to avoid problems.. and also i think when flash suspersu breaks the boot but i need to confirm it
AndresOrue said:
Did you try to set Force Selinux permissive option in Efidroid?
No i will try it at night.
About your boot problem, mine takes about 7 seconds on "booting" splash before showing bootanimation...
For me 5 min and nothing.
Also i need to read a little more to avoid problems.. and also i think when flash suspersu breaks the boot but i need to confirm it
Click to expand...
Click to collapse
Yep I recommend reading the full OP once or twice before starting....well is good to see that the app and installation is working... It's weird that you can't boot internal - please if you can try the unpatched boot option-
lukss12 said:
Yep I recommend reading the full OP once or twice before starting....well is good to see that the app and installation is working... It's weird that you can't boot internal - please if you can try the unpatched boot option-
Click to expand...
Click to collapse
Questions:
What is lf laf recovery?
I flashed twrp from my pc but i still have this new boot, other way to deleted?
How can i deleted this app completely? flashing stock rom is ok or i can flash a custom rom with full wipe?
Anyway now i am doing a backup of my app So I can try it without problems
AndresOrue said:
Questions:
What is lf laf recovery?
I flashed twrp from my pc but i still have this new boot, other way to deleted?
How can i deleted this app completely? flashing stock rom is ok or i can flash a custom rom with full wipe?
Anyway now i am doing a backup of my app So I can try it without problems
Click to expand...
Click to collapse
Enter fastboot mode (volume down + power off)
fastboot flash recovery twrp.img
fastboot reboot-bootloader
Select recovery
Flash your ROM zip
Or extract boot.img from your ROM zip
Enter fastboot mode
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Both of those options will revert your boot and recovery partition to "stock"
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
lukss12 said:
Enter fastboot mode (volume down + power off)
fastboot flash recovery twrp.img
fastboot reboot-bootloader
Select recovery
Flash your ROM zip
Or extract boot.img from your ROM zip
Enter fastboot mode
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Both of those options will revert your boot and recovery partition to "stock"
Click to expand...
Click to collapse
A few things:
To revert to stock recovery, I had to repeat two times the process of flashing the boot.img and twrp.
Obviously you lose root at this time.
Installed EFIdroid again and now first rom boot ok , no more "booting android internal" for 5 min anymore. I dont know if it because I reflashed the boot image again or maybe was the custom kernel because now i have stock DU kernel.
Now i try to add a second rom:
1) Steps from EFIdroid to create second rom works great.
2) rebooting ok
3) I selected twrp and install DU 11.2
4) installation was ok
5) Rebooting into second rom , bootloop in bootanimation after five minutes it freeze and reboot
6)edited here ( i forgot the part of change selinux to permissive )
7) wipe and installed again the second rom and finally second rom boot ok , using DU 11.2 as second rom.
8) Supersu was intalled and works ok in second rom too.
I can confirm now that the reason that the first and second rom dont boot was elementalX kernel. With the stock DU kernel works perfect. primary and secondary rom.
I hope it helps...
Questions:
how i delete second rom completely ? only with full wipe?
---------- Post added at 09:02 PM ---------- Previous post was at 08:57 PM ----------
MINECRAFT4PDA said:
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
Click to expand...
Click to collapse
the first time that i installed EFIdroid i was using elementalx 7.09 and it installed ok but first rom dont boot anymore. The second time, after i reflashed the boot image from DU the rom boot fine
edited: I can confirm now that with elementalX the rom dont boot
MINECRAFT4PDA said:
I apologize for the question, but I did not understand a bit, efidroid will be work if I have installed a custom kernel?
Click to expand...
Click to collapse
Well I'm going to explain it a little:
Right now you have your ROM kernel (boot.img) custom or stock ( it don't mind) in your boot partition and your recovery.img (I think TWRP) in your recovery partition. UEFIDroid is a kernel but it is not a linux kernel, it's based on Little Kernel aka LK... Qualcom port LK to Snapdragon chipsets and developed their custom bootloader, the EFIDroid developer take this and implemented UEFI over the Qualcom's LK port.
Whe you install EFIDroid this is what happens:
-EFIDroid backups your boot.img and recovery.img in /data/media/0/UEFIESP folder
-EFIDroid Manager flash EFIDroid in your boot and your recovery partitions (the recovery is flashed to prevent you using your recovery without booting it from EFIDroid)
Then the next time you boot the stock bootloader aka aboot loads UEFIDroid that is flashed in your boot partition, LK kernel boot and execute UEFI. Then the UEFI looks for the original boot.img (for booting your actual ROM aka Internal) and looks for your actual recovery.img, remember both were saved into /data/media/0/UEFIESP.
And finally it looks for slots/ROMs in /data/media/0/multiboot (of course these are the slots for multibooting a lot of ROMs).
-An slot for a ROM is composed by a data folder, a system.img(1GB) and a boot.img (these are the ones used/mounted to boot the ROM you select in multiboot menu) -slots are added from EFIDroid Manager app.
In the last step it shows you the Menu to select what you want to boot. It applies the propers patchs to ramdisk to use the correct data folder and system.img and boot the correct boot.img using libaboot (the usually used by android bootloaders)
Deleted
AndresOrue said:
Installed EFIdroid again and now first rom boot ok , no more "booting android internal" for 5 min anymore. I dont know if it because I reflashed the boot image again or maybe was the custom kernel because now i have stock DU kernel.
Click to expand...
Click to collapse
Great so DU works as internal , and secondary with SELinux permissive
AndresOrue said:
I can confirm now that the reason that the first and second rom dont boot was elementalX kernel. With the stock DU kernel works perfect. primary and secondary rom.
Click to expand...
Click to collapse
Yes it is possible that a custom kernel is making problem to patch ramdisk
AndresOrue said:
Questions:
how i delete second rom completely ? only with full wipe?
Click to expand...
Click to collapse
No, you don't need full wipe. Slots/ROMs are stored ind /data/media/0/multiboot/your_rom, just delete "your_rom" folder with a root browser and goodbye ROM.
AndresOrue said:
Deleted
Click to expand...
Click to collapse
Sorry I was on the phone and it's a little slow to write and QUOTE there.
I have not tested custom kernels because I don't use them, I think is possible that the custom kernel makes ramdisk patching to fail
lukss12 said:
Sorry I was on the phone and it's a little slow to write and QUOTE there.
I have not tested custom kernels because I don't use them, I think is possible that the custom kernel makes ramdisk patching to fail
Click to expand...
Click to collapse
Sorry too mate I posted it before I read that you replied to me... yes DU11.2 works as primary and secondary rom. I will try others roms tomorrow but so far all is working great in secondary rom.
Thank you for you work!!!
AndresOrue said:
Sorry too mate I posted it before I read that you replied to me... yes DU11.2 works as primary and secondary rom. I will try others roms tomorrow but so far all is working great in secondary rom.
Thank you for you work!!!
Click to expand...
Click to collapse
There is no need to thank I'm doing this for fun
It' can be usefull if you got us some dmesg and logcat logs when the secondary ROM is bootlooping because of the SELinux permissive option not enabled. - you can get this with adb, the ROM bootloops but adb should get started at some point (of course you need to properly boot to the ROM the first time and enable adb and authorize your computer -
Thanks for the testing and wathever you have to share about using EFIDroid is usefull
lukss12 said:
There is no need to thank I'm doing this for fun
It' can be usefull if you got us some dmesg and logcat logs when the secondary ROM is bootlooping because of the SELinux permissive option not enabled. - you can get this with adb, the ROM bootloops but adb should get started at some point (of course you need to properly boot to the ROM the first time and enable adb and authorize your computer -
Thanks for the testing and wathever you have to share about using EFIDroid is usefull
Click to expand...
Click to collapse
Here is the log from second rom with selinux permissive not enable.
Also I confirm that the first rom boot ok with selinux permissive not enable ( selinux as enforcing ).
tell me if the log are correct, if not i try again.
Edited: i did some more test:
I tried as secondary pure nexus rom version : purenexus_hammerhead-7.1.1-20170216-HOMEMADE and boot ok in permissive enable
Also as secondary and permissive enable, I tried DU11.2 with the kernel blu_spark_r122_hammerhead_5472df4 and here boot ok too. It Does not hang up, with the massage " booting android 7.1.1" ( so elementalX 7.09 doesn't work so far).
Thanks for taking the time for this amazing work.
Just downloaded the .apk and installed, boot to EFIDroid, I guess, because I saw a never before seen menu with my internal ROM, TWRP, etc...
As of now it's late where I'm from, but I will download a secondary ROM later and post results.
Thanks.
willyinpr4u said:
Thanks for taking the time for this amazing work.
Just downloaded the .apk and installed, boot to EFIDroid, I guess, because I saw a never before seen menu with my internal ROM, TWRP, etc...
As of now it's late where I'm from, but I will download a secondary ROM later and post results.
Thanks.
Click to expand...
Click to collapse
Yep that "never seen before menu" is EFIDroid hehe, so your primary ROM is booting ok, please share what ROM you are using. And remember to enable Force SELinux permissive when booting a secondary ROM to prevent a SELinux denial bootloop, then you can try with the option disabled. But if the LineageOS kernel, that is the most "normal" kernel I know, couldn't do it I don't think any other could boot with SELinux enforced as secondary ROM. Anyways logcat and dmesg from a bootloop are useful and welcome.
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Redmi note 10 Global/India (sunny/mojito)
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Tree: https://github.com/TeamWin/android_device_xiaomi_mojito
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomiredminote10.html
Unofficial android 12 builds:
https://www.pling.com/p/1836625/
mirror: https://store.kde.org/p/1836625/
OMG.. thanks sir for helping us about that recovery..
Can someone clarify what "repacking" means in this context? Does this mean the recovery cannot be updated through flashing? When a more stable recovery becomes available, will I have to install it using fastboot?
new build with repacking support is up, installation instructions are in the OP
Nebrassy said:
new build with repacking support is up, installation instructions are in the OP
Click to expand...
Click to collapse
Can we flash Xiaomi.eu ROM using new build?
bravonova said:
Can we flash Xiaomi.eu ROM using new build?
Click to expand...
Click to collapse
If they provide recovery zips, yes
Nebrassy said:
If they provide recovery zips, yes
Click to expand...
Click to collapse
Need to inform Xiaomi.eu developers @ingbrzy Pls have a note of this.
"Advanced" does not have a choice "Install Recovery Ramdisk".
I have recovery PixelExperience.
Twrp - I'm triggering like boot (TWRP-3.5.1-mojito-Nebrassy-2.img).
Recovery Ramdisk but doesn't exist.
StaryMuz said:
"Advanced" does not have a choice "Install Recovery Ramdisk".
I have recovery PixelExperience.
Twrp - I'm triggering like boot (TWRP-3.5.1-mojito-Nebrassy-2.img).
Recovery Ramdisk but doesn't exist.
Click to expand...
Click to collapse
It does, but you can also use
Install > install image > select the image and flash it to recovery ramdisk
Thank you, i expected the button. My mistake.
no mirror available at the time writing this
Does backup and restore work? and what are the select for backup?
.
it will be great, give flashing rom instruction using this TWRP. thanks.
Thanks for your work on this.
If I want to do a standard TWRP backup, would I select data, boot and super? There's no partition called system.
Is installing TWRP to ramdisk due to this model having A and B partitions? Why do some phones have this setup and others don't?
For all those who fail to boot up a rom through TWRP....
Plz re-install TWRP into the ramdisk immediately after rom flash... it'll save your day...
I join the question: Does backup and restore work?
Can I only flash TWRP without flashing any other ROM?
I don't want to root or use a cutom ROM at this moment.
Just want to backup and restore with TWRP.
No one?
nierewa said:
I join the question: Does backup and restore work?
Can I only flash TWRP without flashing any other ROM?
I don't want to root or use a cutom ROM at this moment.
Just want to backup and restore with TWRP
Click to expand...
Click to collapse
It does work. But you need to use either sdcard to store the backup, or other storage like PC or external drive. Because switching roms will cause data format.
Ok. Thanks a lot.
I have a sdcard in the phone so I use it for storing the backup.
So I do this:
Installation:
1. fastboot boot twrp.img
2. copy that same twrp image to the device
3. go to Advanced > Install Recovery Ramdisk
4. select the image you copied
and then I can boot the Redmi without the need to flash a custom ROM?