[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?
Related
IsoRec: Isolated Recovery for the Exynos 4210 / Galaxy S2 Family
UPDATE: This change has been merged into official CyanogenMod 11, 12.1 and 13 !!!
UPDATE: Official IsoRec TWRP 3 for i9100 is now available !!!
UPDATE: You can now use official i9100 TWRP on d710, i777 and n7000 !!!
UPDATE: Unofficial CM13 for i9100g by adxamg now supports IsoRec !!!
What is this about?
For too long the owners of Exynos 4210 family devices have been forced to use whatever recovery was chosen by their ROM or kernel provider of choice. These devices have a dedicated recovery partition that is apparently vestigial, and their bootloaders are seemingly unable to boot it. For this reason, the recovery ramdrive is typically bundled together with the kernel and the Android boot ramdisk in a monolithic binary, usually referred to as simply "the kernel" (both ramdrives share a single embedded kernel image).
This means that using your choice of recovery is a practical impossibility:
To change the recovery you must also replace the kernel and the Android boot ramdrive, possibly introducing issues with your ROM.
If you update your kernel or kernel-bundling ROM, you will loose your custom recovery if you had one.
If the kernel bundled with your choice of custom recovery does not boot, your Android will probably not boot either, and you will need a PC to debrick.
This already bad situation was exacerbated with CM 12.1, which includes a severely restricted recovery in official releases, to the point that some official maintainers have had to release semi-official kernels with alternate recoveries just to keep the XDA crowd from lynching them and ripping their limbs off.
What is IsoRec?
IsoRec (Isolated Recovery) is a very simple proposal aiming to solve this problem once and for all. ROM and kernel maintainers can keep on bundling their preferred default recovery, and users gain the freedom to override. Your kernel maintainer has to merge the IsoRec patch (or implement their own compatible solution) for you to be able to use an isolated recovery.
Kernel maintainers are kindly asked to respect their users' freedom by merging this simple patch. Your rate of adoption will make or break this initiative.
How does it work?
It is extremely simple. The IsoRec-patched boot sequence is as follows:
The bootloader loads the kernel and the unified ramdrive, then fires up the kernel.
The kernel starts and then invokes the unified ramdrive.
If booting Android, the unified ramdrive replaces itself with the nested Android boot ramdrive and invokes it.
Else if booting recovery, the IsoRec-patched unified ramdrive chooses the recovery ramdrive as follows:
if the raw recovery partition (/dev/block/mmcblk0p6) contains valid lzop-compressed data
and said data is a valid cpio archive
then use that cpio archive as the recovery ramdrive;
else use the default recovery ramdrive that comes nested within the unified ramdrive.
Finally the unified ramdrive replaces itself with the chosen recovery ramdrive and invokes it.
Where can I find the IsoRec patches?
These links are of interest only to kernel maintainers:
CyanogenMod patch: https://github.com/CyanogenMod/andr...mmit/9bfbaf337207359ef6aefe0a329a3b760054a6b7
Dorimanx patch: https://github.com/Lanchon/IsoRec-D...mmit/fe2288665fca2eb33426b71086fc7282ee687e68
Where can I find some IsoRec-compatible kernels?
In the future, hopefully everywhere. For now you can use my CM 11/12.1/13 TRIM-IsoRec kernels:
https://www.androidfilehost.com/?w=files&flid=47607
UPDATE: Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible !!! (link)
UPDATE: Unofficial Dorimanx builds by gsstudios are now IsoRec-compatible !!! (link)
Where can I find some IsoRec-compatible recoveries?
https://www.androidfilehost.com/?w=files&flid=47550
(The "disabler" files just clobber the contents of the isolated recovery partition so that the default recovery bundled with the kernel boots instead.)
UPDATE: Unofficial IsoRec TWRP 3 for i9100 by arnab has been released !!!
UPDATE: arnab and Dees_Troy teemed up to give us official TWRP 3 !!!
NOTE: TWRP 3 incompatibilities with CM 12.1 kernels have been fixed as of TWRP 3.0.2.0.
Note: I did not build any of the TWRP recoveries myself, I just bundled images shared by other developers. Big thank you to @arnab, @cyril279 and @dimoochka for the TWRP images! Recovery developers are welcome to reuse my flashing zips, just please remove my name from the filename AND the flashing script. Use lzo -9 compression and remember to sign your zips!
TWRP 3 for n7000, i777 and d710
You can use official i9100 TWRP on d710, i777 and n7000 with TWRP Patcher.
Installing TWRP 3 the Easy Way
There are many ways to skin a lolcat. You can easily flash a TWRP .img file (or any IsoRec recovery .img file) on the Exynos 4210 S2 family via adb from your PC. (Prerequisite: working adb connection and tools.) Try it out:
Download the 'twrp-X.X.X.X-i9100.img' file.
Switch to adb root by typing this in your PC:
adb root(Requires root on your phone. In CM, enable adb root in developer settings.)
Flash the recovery by typing this in your PC:
adb push twrp-X.X.X-X-i9100.img /dev/block/mmcblk0p6
WARNING: DO NOT MISTYPE ANYTHING !!!
If you do, you can HARD-BRICK your phone FOREVER. Better copy/paste to be sure.
WARNING: DO NOT TRY THIS IN ANY DEVICE EXCEPT EXYNOS 4210 S2 PHONES !!!
If you do, you can HARD-BRICK your device FOREVER. The 4210 devices are: i9100, n7000, i777, d710 and sc02c.
XDA:DevDB Information
IsoRec, Tool/Utility for the Samsung Galaxy S II
Contributors
Lanchon
Version Information
Status: Stable
Created 2016-01-12
Last Updated 2016-06-22
Reserved
Reserved
Sounds great. If this works reliable without side effects and if @Lysergic Acid merged your patch later (after it has proven that), this would make a dream come true for many here.
Thank you so much!!!
hi @Lysergic Acid,
i entered a change on gerrit:
http://review.cyanogenmod.org/#/c/127877/1
tests on the i777 are still pending.
http://forum.xda-developers.com/showpost.php?p=64778749&postcount=149
@Lanchon you are awesome. What a cool idea to fix a Samsung problem of putting the recovery and kernel together.
Sent from my Nexus 6P using Tapatalk
@Lanchon is there a possibility of some compatibility check? I mean, what happens, if the isolated recovery somehow does not match the kernel, e.g. I (hypothetically) start with CM12.1 plus isolated recovery and want to switch to CM13 with corresponding feature, but the kernels have to differ in some way so that the isolated recovery still in the partition fails. Can the isolated recovery be invalidated somehow?
Could this be done with Odin?
Have found a hilarious bug, don't worry, don't need support but if someone else can confirm, that would be fun.
Xposed 79, if Gravitybox is enabled (its settings don't matter.), and the screen is off, receiving a Skype message, reboots the phone. Completely reproducible here. LOL
Klaerchen said:
@Lanchon is there a possibility of some compatibility check? I mean, what happens, if the isolated recovery somehow does not match the kernel, e.g. I (hypothetically) start with CM12.1 plus isolated recovery and want to switch to CM13 with corresponding feature, but the kernels have to differ in some way so that the isolated recovery still in the partition fails. Can the isolated recovery be invalidated somehow?
Could this be done with Odin?
Click to expand...
Click to collapse
simple, if that happens then the person goes into android and clobbers the recovery partition from there. or writes a different recovery from there. or overwrites the kernel (manually or flashify style). or goes to download mode and uses odin or heimdall to flash a kernel or recovery or just to clobber. basically you are describing a situation of flashing the wrong kernel: the standard cure is using download mode.
that said, i thought of disabling the alternate check by pressing VOL DOWN during boot. but...
a) this affects several devices and, though IsoRec is compatible with all, the button setup could be different; that means investigating and testing, testing, testing with owners of obscure devices.
b) i don't know how to read button state directly using the kernel so i would have to research that.
c) most importantly, i don't have time to do a) nor b)! the patch took a few minutes; then building the kernels, packing the recoveries, testing, entering the change on gerrit, and writing all this down took a couple of hours already, hours that btw i shouldn't have spent on this AT ALL.
this is the best i could make it in the time i didn't have. IMHO the missing VOL DOWN functionality does not justify stopping people from having this. let's see what the CM gerrit people think. one thing is for sure: i don't have the time to make it better.
@Lanchon
Hi,
many thanks and much respect for your great work!
Im gonna test the IsoRec now, seems its working good so far,
hopefully the trim will not destroy my phone..
(Im still would be feel much more safe when kernel dont have trim functionality!)
Best regards
Lanchon said:
IsoRec: Isolated Recovery for the Exynos 4210 / Galaxy S2 Family
Click to expand...
Click to collapse
Badass. This is a really elegant solution - no need to reflash on every boot. Great job!
PS. It's awesome that you're also ripped. Are you a luchador in your day job?
dimoochka said:
Badass. This is a really elegant solution - no need to reflash on every boot. Great job!
PS. It's awesome that you're also ripped. Are you a luchador in your day job?
Click to expand...
Click to collapse
lol no, i'm just heavily invested in not looking the nerd i am
UPDATE: new devices, kernels, recoveries..
added:
CM 11 IsoRec-compatible kernels
CM (CWM-based) 6.0.5.1 IsoRec-compatible recoveries
for all supported devices:
d710
i777
i9100
n1000
this time i built the recoveries myself. these recoveries are the run-of-the-mill, old-style CM recoveries we all love and miss that used to come bundled with CM in the Kitkat days. they are compatible with CM 11 and CM 12.1 kernels, so you can use them with your Lollipop ROMs.
finally, i also added IsoRec disablers for the newly supported devices.
please note:
the (previously) published TWRP-i9100 recovery has a bug: adb sideload does not work.
EDIT: adb sideload works correctly on the newest i9100 TWRP (by arnab).
Wow, slick.
It seems I have a patch to add to the slim builds.
Happy flashing
-Cyril
@Lanchon
I read the OP, but it's not fully clear to me how it works. Where should I put the preferred recovery after having flashed the isorec compatible kernel?
Anyway thank you for the great job you did.
Sent from my GT-I9100 using XDA Free mobile app
@Lanchon
Latest twrp ramdisk as requested.
https://drive.google.com/file/d/0Bx_upRk6Kfw9MUU4UGdBel9xbDQ/view?usp=sharing
chrisXL said:
@Lanchon
I read the OP, but it's not fully clear to me how it works. Where should I put the preferred recovery after having flashed the isorec compatible kernel?
Anyway thank you for the great job you did.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
you flash it whenever you want, independently of the kernel. it has to be an IsoRec-compatible recovery; it CANNOT be a "legacy" (non-IsoRec; lol) monolithic kernel+recovery. look for some recoveries in the OP of this thread.
UPDATE: new TWRP for the i9100 contributed by @arnab.
thank you so much arnab!!!
cyril279 said:
Wow, slick.
It seems I have a patch to add to the slim builds.
Click to expand...
Click to collapse
thanks, that would be awesome!
Using
'kernel-Lanchon-TRIM-FreezeFix-TWRP-20160111-cm-12.1-i9100.zip'
right now.
In which order shall I flash:
1. kernel-Lanchon-TRIM-IsoRec-20160112-cm-11-i9100.zip
2. recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
3. Lanchon-IsoRec-Disabler-i9100.zip
- Which zip's will i have to put into CyanDelta to flash along with upcoming nightlies?
- Will I be able to go back to older TWRP etc. anytime?
- What is the benefit in one sentence?
Team Win Recovery Project 3.0.0.x ONLY For MS01LTE SM-G7105
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Phone look:
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 3.0.0-0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
DOWNLOAD:
ON post #2
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Downloads
TWRP 3.0.0
Note - Im not having this device so im not sure that this will work but you can test and report
ODIN (Tar file)- coming soon
Recovery flashable zip - coming soon
Recovery image - Here
Nice job perfectly working in 7102.
Bro how can I flash this recovery???????
Thanks a lot for helping ms01lte???
Sanjay8787 said:
Nice job perfectly working in 7102.
Click to expand...
Click to collapse
This is only for Lte
Yuen.Jason22 said:
Bro how can I flash this recovery?������������
Thanks a lot for helping ms01lte������
Click to expand...
Click to collapse
No u need to use flashify to flash this
What will happen if there is a failure in flashing?? I can't brick my phone in this period before I get a new one
Yuen.Jason22 said:
What will happen if there is a failure in flashing?�� I can't brick my phone in this period before I get a new one
Click to expand...
Click to collapse
If this wont work then u can flash another recovery from odin it will repair
how to install
adityaupreti said:
Downloads
TWRP 3.0.0
Note - Im not having this device so im not sure that this will work but you can test and report
ODIN (Tar file)- coming soon
Recovery flashable zip - coming soon
Recovery image - Here
Click to expand...
Click to collapse
İ'm on motion rom v17.my 7105 allways open download mod when i flash with flashify.
SM-G800H cihazımdan Tapatalk kullanılarak gönderildi
hey friends
diid it work for samsung galaxy grand 2 duos g7102?
plz reply fast:crying:
Hi guys.
Been trying for 3 days now to install this recovery on my Galaxy Grand 2 SM-7105, but to no avail. Here's what I did:
1- Using Odin I root the device using "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" . I got PASS in Odin, (is this an indicator that the root is successful? Because if I entered Android after that, it seems unrooted).
2- Then after rooting (I understand that I can't install the recovery without root first), and without rebooting OR after rebooting the device, I run Odin again, and in download mode I flash the TWRP 3.0.0 recovery.
3- Disconnect USB cable, remove battery, then boot into recovery, but I keep getting the message:
Could not do normal boot .
Odin mode
Current Binary: custom
System status: custom
No matter how many times I tried and how many method and Odin versions I used, the same result.
What could be wrong? How can I be sure that it is a problem in the installation of the root, and not in the installation of the recovery, or vice versa?
Appreciate your feedback !
mouadk said:
Hi guys.
Been trying for 3 days now to install this recovery on my Galaxy Grand 2 SM-7105, but to no avail. Here's what I did:
1- Using Odin I flashed root rom "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" . I got PASS in Odin, (is this an indicator that the root is successful? Because if I entered Android after that, it seems unrooted).
2- Without rebooting OR after rebooting the device, I run Odin again, and in download mode I flash the TWRP recover.
3- Disconnect USB cable, remove battery, then boot into recovery, but I keep getting the message:
Could not do normal boot .
Odin mode
Current Binary: custom
System status: custom
No matter how many times I tried and how many method and Odin versions I used, the same result.
What could be wrong? How can I be sure that it is a problem in the installation of the root, and not in the installation of the recovery, or vice versa?
Appreciate your feedback !
Click to expand...
Click to collapse
This twrp dosen't work for g7105 use my twrp 3.0.0 shoud work fine
SoUnd001 said:
This twrp dosen't work for g7105 use my twrp 3.0.0 shoud work fine
Click to expand...
Click to collapse
Thanks man. But that's actually the TWRP recovery I've been trying to flash, and that's what i mentioned.
If you were referring to the "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" , my understanding is that that's not the recovery, but the root rom, which I must flash first before the TWRP 3.00 recovery.
No ?
mouadk said:
Thanks man. But that's actually the TWRP recovery I've been trying to flash, and that's what i mentioned.
If you were referring to the "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" , my understanding is that that's not the recovery, but the root rom, which I must flash first before the TWRP 3.00 recovery.
No ?
Click to expand...
Click to collapse
You are on kitkat firmware right?
---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------
And if you want easy root flash my twrp go to recovery mode and flash update supersu
SoUnd001 said:
You are on kitkat firmware right?
---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------
And if you want easy root flash my twrp go to recovery mode and flash update supersu
Click to expand...
Click to collapse
No not Kitkat, Jelly Bean (4.3).
And sorry not sure I understood your last sentence. I can only access the stock recovery. So what do you mean by "flash update supersu", and how does that help ?
mouadk said:
No not Kitkat, Jelly Bean (4.3).
And sorry not sure I understood your last sentence. I can only access the stock recovery. So what do you mean by "flash update supersu", and how does that help ?
Click to expand...
Click to collapse
You need to flash kitkat firmware with odin
SoUnd001 said:
You need to flash kitkat firmware with odin
Click to expand...
Click to collapse
Well, the author of this post (who posted the WTRP) didn't say one must have Kitkat before flashing this recovery. So are you sure of it?
Also, can I flash Kitkat via Odin if the phone is not rooted?
If yes, where can I get the kitkat for this phone ?
mouadk said:
Well, the author of this post (who posted the WTRP) didn't say one must have Kitkat before flashing this recovery. So are you sure of it?
Also, can I flash Kitkat via Odin if the phone is not rooted?
If yes, where can I get the kitkat for this phone ?
Click to expand...
Click to collapse
Any recovery or rom needs kitkat firmware you can get kitkat by just going to setting and check for updates
SoUnd001 said:
Any recovery or rom needs kitkat firmware you can get kitkat by just going to setting and check for updates
Click to expand...
Click to collapse
Thank you. Unfortunately there are no updates, says "your device has the latest updated" !
It seems my cell provider decided they don't want to upgrade it.
TeamWin's TWRP Touch Recovery for LG G3 - currently available only for F400 variantshttps://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Flashing Instructions
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise do the following:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
OR
1. Move recovery.img to internal storage.
2. Open terminal window/command prompt to execute following commands
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
About this TWRP
compiled on LineageOS-14.1 source
always up-to-date
fixed screen brightness
permissive selinux
disabled logd/logcat in recovery
fuse exfat, ntfs-3g, jpeg, usb-otg support
external storage as default storage
touch to wake
backup of all partitions including modem, efs
crypto/decryption may work or not..
Changelog
* 170430
- Initial Build
- Disabled HW crypto due to build fails
* 170501
- Deleted unused flags
- Add back HW crypto
- exfat support
* 170507
- Disabled logd/logcat (fix for "device or resource busy", hopefully)
* 170519
- Updated to v3.1.1
- Fix Aroma Installer crash (hopefully)
Known issues
ZIP files with date check assert can't be installed (eg. crDroid) - Users should delete date check assert in binary by themselves.
AROMA Installer stucks at loading - will be fixed soon..
Download Links
Unofficial | Official
Sources
https://github.com/TheNoFace/android_device_lge_g3-common-TWRP/tree/twrp
(Based on https://review.lineageos.org/#/c/160056/)
Remember to do backup of your current recovery before installing
Any plans for suporting other G3 variants in future?
@fprhqkrtk303: Now have 2 version twrp to flash. Which one to choose to flash? Unofficial or official? Thanks!
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
ahk31 said:
Any plans for suporting other G3 variants in future?
Click to expand...
Click to collapse
Planning to support more devices when F400 version is stable.
You can build your own TWRP using my source.
@chuyennho184 @andrewKode Official version from TWRP uses older device tree and actually no one maintains. Recommend using unofficial version.
@fprhqkrtk303: I saw update firmware on March 22th for F400 variants but I don't have a link. Do you have a link? Thanks for bother you.
Updated to v3.1.1 (170519)
fprhqkrtk303 said:
Updated to v3.1.1 (170519)
Click to expand...
Click to collapse
Is aroma bootloop problem fixed in this new version?
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Not tested yet. Can you check?
fprhqkrtk303 said:
Not tested yet. Can you check?
Click to expand...
Click to collapse
Yes. Tried it yesterday. Bootloop problem is still present.
andrewKode said:
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
Click to expand...
Click to collapse
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
ZjemCiKolege said:
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
Click to expand...
Click to collapse
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
andrewKode said:
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
Click to expand...
Click to collapse
1. I try but did not happen.
2. Build of lineage?(i flash each version from february to 21.04) no any issue.
3. Issue of custom rom(problem with turn on charger and boot same issue..) ;]
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Hello, apparently no...
https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
If it's a software problem, it would be the problem of AROMA devs, but if it's related to software keys incompatibility it's will be the work of TWRP devs.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Flash Indian Stock .ozip roms works
- Flash Roms works
- Mtp works
- Backup works
- .ozip flash
- Android 10 Support
- Android 11 Decryption
Download:
TWRP 3.4.0-10 Unofficial by mauronofrio
TWRP 3.4.0-0 Unofficial by mauronofrio
TWRP 3.3.1-13 Unofficial by mauronofrio
TWRP 3.3.1-12 Unofficial by mauronofrio
TWRP 3.3.1-11 Unofficial by mauronofrio
TWRP 3.3.1-7 Unofficial by mauronofrio
TWRP Official Builds
TWRP 3.3.1-1 Unofficial by mauronofrio
TWRP 3.3.1-0 Unofficial by mauronofrio
To Flash the TWRP:
if it's the first time you flash the TWRP or you are getting problems of TWRP lost or device doesn't boot after flashed magisk or something else you need to flash a script to patch your vbmeta:
VBMETA PATCHER
To flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually.
Flash the VBMETA PATCHER and reboot.
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_realme_RMX1931
Precompiled stock one
Donations:
Credits:
Thanks to @Jerry08 for the testing
Created 2019-11-5
This is not tested, i have not the stock recovery, so before flash directly it, please try to only boot this twrp using:
fastboot boot twrp.img command
Here we go! If this works, this will be my new phone
This is exactly what I was hoping to see, just picked up this phone and can't wait to be rid of ColorOS. Is there a solution available to flash Android 10 on this device? I'd be happy to commit a donation for getting Android 10 working smoothly on this device with full camera support.
hanakon said:
This is exactly what I was hoping to see, just picked up this phone and can't wait to be rid of ColorOS. Is there a solution available to flash Android 10 on this device? I'd be happy to commit a donation for getting Android 10 working smoothly on this device with full camera support.
Click to expand...
Click to collapse
Would also love stock Android or oxygenOS. Full camera support while keeping the super macro mode. I'm not sure if that's a feature on other phones but really like it. At 50% battery as I type this with almost 9 hours of use and lil over 4 hours on on screen time. Best battery life I've had in a phone and to top it off or charges incredibly fast.
Did anyone test this? If twrp works, then it will not be far from getting a few custom roms for this device. I really hope this works since if it does, I'm buying this phone immediately!
How to unlock bootloader? , i haven't found anything about boot loader unlock for realme X2 pro yet. We can't flash twrp with locked bootloader right?
Try this?: https://realmeroot.com/how-to-unlock-the-boatloader-in-realme-x2-pro/.
kaminsky.victor said:
Try this?: https://realmeroot.com/how-to-unlock-the-boatloader-in-realme-x2-pro/.
Click to expand...
Click to collapse
Not working , cannot install that app
Is this TWRP working on Realme X2 (RMX1991)?
ospeto said:
Not working , cannot install that app
Click to expand...
Click to collapse
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
shamllakh said:
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
Click to expand...
Click to collapse
Also, i found this on RealmeX2Pro china forum:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
shamllakh said:
Yet i did get the phone....
But...
There is an option on developers menue which i guess it should be toggled: link is below...
https://www.hardreset.info/devices/realme/realme-x2-pro/developer-options/
---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------
Also, i found this on RealmeX2Pro china forum:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
Click to expand...
Click to collapse
One guy on RealmeX2Pro china forum reported A Success Bootloader Unlock, here is his method link:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
shamllakh said:
One guy on RealmeX2Pro china forum reported A Success Bootloader Unlock, here is his method link:
https://www.realmebbs.com/post-deta...06252043546624&subForumId=1181409566403866624
Click to expand...
Click to collapse
That's great , but I'll just wait for xda 's method to be sure. I hop we can get custom ROMs soon. Ported oxygen os or AEX would be great. That Color OS is not good. I am experiencing some notification and permission bugs now.
Just tried, and the phone won't go in bootloader mode. The 'adb reboot bootloader' do nothing :/
Thanks @nathan30 for testing!
I downloaded the package from that chinese website which was linked by @ospeto
I translated the folders inside the zip with google to english, since many people have issues with chinese characters in their file structure but in case anyone needs the original files, I kept the chinese zip as well.
Download English zip:
http://www.mediafire.com/file/qdkqs577zskml9k/realme_X2_pro_Eng.zip/file
Download Chinese zip:
http://www.mediafire.com/file/yrlhze0l5ahzd7n/realme_X2_pro_Ch.zip/file
If anyone can test this, please report back.
Thank you guys!
EDIT: There is a google translated bootloader unlocking guide in the zip.
SethPDA said:
Thanks @nathan30 for testing!
I downloaded the package from that chinese website which was linked by @ospeto
I translated the folders inside the zip with google to english, since many people have issues with chinese characters in their file structure but in case anyone needs the original files, I kept the chinese zip as well.
Download English zip:
http://www.mediafire.com/file/qdkqs577zskml9k/realme_X2_pro_Eng.zip/file
Download Chinese zip:
http://www.mediafire.com/file/yrlhze0l5ahzd7n/realme_X2_pro_Ch.zip/file
If anyone can test this, please report back.
Thank you guys!
EDIT: There is a google translated bootloader unlocking guide in the zip.
Click to expand...
Click to collapse
I could try but have you and idea about the phone which don't boot in bootloader mode ?
Is this TWRP working on Realme X2 (RMX1991)?
MTsv DN said:
Is this TWRP working on Realme X2 (RMX1991)?
Click to expand...
Click to collapse
Definitely not, don't you see this is for the Pro?
MTsv DN said:
Is this TWRP working on Realme X2 (RMX1991)?
Click to expand...
Click to collapse
I don't think it will work, maybe i can make a dedicated version
mauronofrio said:
This is not tested, i have not the stock recovery, so before flash directly it, please try to only boot this twrp using:
fastboot boot twrp.img command
Click to expand...
Click to collapse
Do you think you will get the stock recovery to test your Twrp ?
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 Oneplus 7/Pro/5G that supports Android 11
can be flashed to boot with working decryption on android 11 roms
bugs:
backup/restore is unreliable
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
Trees:
https://github.com/TeamWin/android_device_oneplus_guacamole
https://github.com/TeamWin/android_device_oneplus_sm8150-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus7pro.html
Unofficial 12 builds: https://www.pling.com/p/1835156/
Will there be an installer zip or just an .img?
bdwilk said:
Will there be an installer zip or just an .img?
Click to expand...
Click to collapse
Read the Installation instructions, there's a new experimental feature replacing the need for zips.
Nice, at least no more torturing my poor 7Pro with test images, haha.
Thanks.
And yes, the new feature is neat and works here pretty well.
Good job, @Nebrassy !
It says a11 ROMs can be decrypted is oos 11 also included in that ?
jaggillararla said:
It says a11 ROMs can be decrypted is oos 11 also included in that ?
Click to expand...
Click to collapse
Why don't you try it and give us feedback
@Nebrassy thank you . I am sure the entire Oneplus guys here appreciate it.
wartomato said:
Nice, at least no more torturing my poor 7Pro with test images, haha.
Thanks.
And yes, the new feature is neat and works here pretty well.
Good job, @Nebrassy !
Click to expand...
Click to collapse
Been using for awhile now it's awesome this will make things easier great job
jaggillararla said:
It says a11 ROMs can be decrypted is oos 11 also included in that ?
Click to expand...
Click to collapse
I'm using HavocOS 4.5 based on OOS 11 and managed to decrypt data partition just fine.
I can confirm it's working on OP7 with OB4 / Android 11.
Many thanks for the great job!
Uploaded new build with f2fs support
Toutatis_ said:
I'm using HavocOS 4.5 based on OOS 11 and managed to decrypt data partition just fine.
Click to expand...
Click to collapse
Did you need to wipe your phone? Recently installed Android 11 and I can't do nandroid backup and don't want to mess it again.
1 said:
Did you need to wipe your phone? Recently installed Android 11 and I can't do nandroid backup and don't want to mess it again.
Click to expand...
Click to collapse
No, I rebooted to bootloader mode, ran sudo fastboot boot filename.img and TWRP splash screen appeared, asking for password. I entered my password and that's it, data partition was decrypted. I finally rebooted to system.
@Nebrassy
Thanks for the great work btw. Appreciated.
This work with stock oos11 encrypted?
Can somebody elaborate this?
1. fastboot boot twrp.img (Which twrp is this? The one shared here?)
2. go to Advanced > Flash Current TWRP (What does current TWRP mean? Official TWRP? and where is that advanced? Advanced in new TWRP?)
1 said:
Can somebody elaborate this?
1. fastboot boot twrp.img (Which twrp is this? The one shared here?)
2. go to Advanced > Flash Current TWRP (What does current TWRP mean? Official TWRP? and where is that advanced? Advanced in new TWRP?)
Click to expand...
Click to collapse
Yes, run fastboot boot TWRP-3.5.1-guacamole-Nebrassy-2.img (this is the filename for the current latest version)
See my screenshot
Toutatis_ said:
Yes, run fastboot boot TWRP-3.5.1-guacamole-Nebrassy-2.img (this is the filename for the current latest version)
See my screenshot
Click to expand...
Click to collapse
Thanks a lot.
Can this be flashed within twrp if we're on the latest version from https://dl.twrp.me/guacamole/ ?