Related
Diviance's Mods and How-To's for Users and Developers
If you are on Windows, Notepad++ is the text editor I recommend to apply these mods
EXT 4 Conversion Scripts
Warning: Must have an up to date copy of CWM (Rom Racer OR Rom Manager versions work), must be using a kernel that supports ext4 (faux is currently the only one available that does) and you must get down on your knees and tell me you love me. If you skip any step, this won't work. Seriously.
Click to expand...
Click to collapse
For Developers (Version 3) Without Journaling (Higher Performance, Lower Stability):
Download this: Here
Replace your format partitions with the script above, and the information in the updater-script file. Then use ext4 as your mount option, not ext3. Provided you are using an ext4 compatible kernel, you now have an ext4 rom.
Click to expand...
Click to collapse
For Developers (Version 3) With Journaling (Lower Performance, Higher Stability):
Download this: Here
Replace your format partitions with the script above, and the information in the updater-script file. Then use ext4 as your mount option, not ext3. Provided you are using an ext4 compatible kernel, you now have an ext4 rom.
Click to expand...
Click to collapse
For Developers (Version 3) With Journaling and without Extents (Lowest Performance, Highest Stability, Backwards Compatible):
Download this: Here
Replace your format partitions with the script above, and the information in the updater-script file. Then use ext4 as your mount option, not ext3. Provided you are using an ext4 compatible kernel, you now have an ext4 rom.
Click to expand...
Click to collapse
For Users (Version 3) Without Journaling (Higher Performance, Lower Stability):
Download this: Here
Copy to your SDCard and run in CWM. Your rom of choice should now be proper EXT4.
Click to expand...
Click to collapse
For Users (Version 3) With Journaling (Lower Performance, Higher Stability):
Download this: Here
Copy to your SDCard and run in CWM. Your rom of choice should now be proper EXT4.
Click to expand...
Click to collapse
For Users (Version 3) With Journaling and without Extents (Lowest Performance, Highest Stability, Backwards Compatible):
Download this: Here
Copy to your SDCard and run in CWM. Your rom of choice should now be proper EXT4.
Click to expand...
Click to collapse
Changelog:
Version 3:
Added: Cache to fsck boot check
Added: No Extents version to enable backwards compatiblity (should, anyway)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1 Signal Bar Fix (For Devs)
Go into the \system\etc\motorola\com.motorola.android.providers.settings folder and open settings.mkitso
Change
rat_signal_strength_raw=1
to
rat_signal_strength_raw=0
Now your rom will have the 1 Signal Bar Fix, without modifying smali or apk's.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hotspot Enable (For Devs)
Go into the \system\etc\motorola\com.motorola.android.providers.settings folder and open settings.mkitso
Change
entitlement_check=enabled
to
entitlement_check=disabled
Click to expand...
Click to collapse
Click to expand...
Click to collapse
AGPS Option (For Devs)
Go into the \system\etc\motorola\com.motorola.android.providers.settings folder and open settings.mkitso
Add
agps_feature_enabled=1
to the bottom of the file.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Set App Download Location (For Devs)
Go into the \system\etc\motorola\com.android.providers.settings folder and open system.mkitso
Add
set_install_location=1
to the bottom of the file
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So if I flash the user version of Ext4, will the Rom automatically turn Ext4?
Notorious544d said:
So if I flash the user version of Ext4, will the Rom automatically turn Ext4?
Click to expand...
Click to collapse
Worked for my versions of 1.2.0.0 and 1.1.3. Should work for any rom.
Diviance said:
Worked for my versions of 1.2.0.0 and 1.1.3. Should work for any rom.
Click to expand...
Click to collapse
Well I just did this to my Homebase build and I constantly get FC's on everything. Completely trashed.... On startup I get "Systen IUD's Inconsistent" I did the User EXT Conversion... Time to wipe and start over... Dang but it happens when you try to be the first to test.
Earthsdog said:
Well I just did this to my Homebase build and I constantly get FC's on everything. Completely trashed.... On startup I get "Systen IUD's Inconsistent" I did the User EXT Conversion... Time to wipe and start over... Dang but it happens when you try to be the first to test.
Click to expand...
Click to collapse
Which version of homebase? I will want to check on this when I get time, hopefully after work.
Try again, if it happens again send me this file:
/data/system/uiderrors.txt
I am guessing some apps don't appreciate the filesystem conversion, which wouldn't really be MY fault...
Diviance said:
Which version of homebase? I will want to check on this when I get time, hopefully after work.
Try again, if it happens again send me this file:
/data/system/uiderrors.txt
I am guessing some apps don't appreciate the filesystem conversion, which wouldn't really be MY fault...
Click to expand...
Click to collapse
Don't get me wrong I am NOT casting blame at all. I appreciate all you do very much. I will PM you the log. I am using the Orange 2.6b build.
Me too, using homebase orange, booted once, then started with superuser fc' ing, then next boot up, everything fc'ed.
I'm also using faux 1.0ghz 0.2.0 kernel.
Nandroid restored fine from CWM 5.
(oh dear, while typing, just realized, should I be using romracer?)
Also where should file be stored, sdcard our sdcard-ext?
Swyped from 'mount' olympus
Swyped from 'mount' olympus
No fc's on hb2 4.5.91 build. Maybe there is an issue with Orange builds
Sent from my MB860 using xda premium
Maybe I am just paranoid...but after running the script my phone is not quite as smooth as before
Sent from my MB860 using xda premium
lilhaiti said:
Maybe I am just paranoid...but after running the script my phone is not quite as smooth as before
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Most likely paranoia. I don't honestly prefer the user conversion script, converting a filesystem is never as good as starting a fresh one, but performance should be better than the fake ext4 from faux. Especially over time.
lilhaiti said:
No fc's on hb2 4.5.91 build. Maybe there is an issue with Orange builds
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I flashed script with Orange Build and my phone is screaming! I think you need Romracer's recovery.
Figured I should post here instead of clogging up HB. Dov, you said flash the script you made after ROM. I tried and now my phone is stuck in the Dual Core screen. I flashed via CWM from the ext SD.
Any advice? Am i using the wrong script? I see people using the USER one. Im using the one from HB that's listed.
EDIT: checked real.post.on computer. I see what im missing.
You're awesome Diviance! I just updated my backups of HB and Darkside to ext4 with no issues and no FC's.
Strictly speaking, if I were going for pure performance, I would go back to ext2. But that would be a slight performance difference yet a huge decrease in stability and reliability.
A worthy sacrifice.
Also, glad it is working for most people.
I got it to work following the steps.
1. Formatted Internal SDCard
2. Fastboot -w
3. Boot CWM wiped data, dav
4. Clean Install of Orange Ver. 5
5. Booted and waited 15 minutes
6. Rebooted and ran script for Ext4 conversion
All is good now. All I can think is I had previous Orange Builds and updated each step from initial build.
Thanks for your efforts FYI: The thing boots incredibly fast now.
This doesnt work on alien build #4. I ran this cwm and i got stuck at the motorola screen.
roughriduz said:
This doesnt work on alien build #4. I ran this cwm and i got stuck at the motorola screen.
Click to expand...
Click to collapse
Using what version of CWM and which kernel?
i have the latest version of the romracer cwm from the rom manager unstall and im using the stock kernel
roughriduz said:
i have the latest version of the romracer cwm from the rom manager unstall and im using the stock kernel
Click to expand...
Click to collapse
Stock as in... stock motorola gingerbread kernel?
roughriduz said:
i have the latest version of the romracer cwm from the rom manager unstall and im using the stock kernel
Click to expand...
Click to collapse
Stock kernel doesn't support EXT4, use faux's kernel. Also update your recovery to 5.0.2.3-atrix4.1 if you aren't already running 4.1.
Welcome to Lollipop
Clean install with custom recovery (TWRP) (recommended)
Download the following files:
aosp_mako-ota-eng.5.0.zip or aosp_mako-ota-eng-preroot.5.0.zip (if you want to have root*) (mirrors, thanks to dorqus)
* In case you have already downloaded aosp_mako-ota-eng.5.0.zip you can also flash aosp_mako-boot-root.5.0.zip to prepare for root
optional: BETA-SuperSU-v2.19.zip
defcon-L-gapps-v2.zip
Recommended: Backup your apps:
Code:
adb backup -apk -obb -all -system
Recommend: Backup your internal storage (see FAQ below for the reason). Either copy all files in Explorer or use adb:
Code:
adb pull /sdcard/
Boot to recovery
Recommend: Factory reset. Warning: All your apps and app data will be deleted! Make sure you have a backup!
Recommend: Format/wipe internal storage (see FAQ below for the reason). Warning: All your files will be deleted! Make sure you have a backup!
Format/wipe system
Unmount system
Install aosp_mako-ota-eng.5.0.zip (or aosp_mako-ota-eng-preroot.5.0.zip)
Install gapps-lp-20141105-signed.zip
Optional: Install BETA-SuperSU-v2.19.zip
Reboot
Have a break and don't panic! The first boot can take 5 to 10 minutes
Optional: Recover from backup:
Code:
adb restore backup.ab
Optional: Copy your files back to internal storage
Clean install with fastboot
You won't have GApps this way ...
WARNING: If you flash userdata.img, all your data will be gone! Even the files on internal storage!
Download the images
boot.img or boot-root.img (prepared for root, you still have to install SuperSU somehow...)
system.img
Optionalrecovery.img
Optional, should be empty: cache.img
Optional, should be empty: userdata.img
Boot to bootloader
Flash
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
FAQ
Oh no, all my files are lost!!!
or
Why should I wipe internal storage?
5.0 uses a much stricter SELinux policy than most 4.4 ROMs do. Normally the first boot should migrate all the things (and it did for me, but only the first time). If not, you are no longer able to see your internal storage (aka SD card). E.g. Camera says: Please enter an SD card. To fix that problem you have to either wipe the internal storage and let Android recreate the file structure. (You can before still access the /sdcard in TWRP for a backup with adb). Or you can fix the SELinux context with the following command (in recovery):
Code:
adb shell
IFS="
"
for i in `find /data/media`; do chcon u:object_r:media_rw_data_file:s0 "$i"; done
Is this the official update from Google?
No, this is an AOSP build from the latest Lollipop sources.
Do I need to be on stock 4.4.4 before flashing?
No, but you should consider doing a factory reset otherwise.
Can I do a dirty upgrade?
Yes, you can. But you might spend a lot of time in fixing F/Cs...
Can this ROM be rooted?
Yes, just flash aosp_mako-ota-eng-preroot.5.0.zip (or aosp_mako-boot-root.5.0.zip) and BETA-SuperSU-v2.19.zip
Known issues
General:
No access to internal storage, even not with adb or as root. Seems like SELinux is misconfigured. See FAQ for solution
Due to incomplete GApps:
WLAN/mobile based location isn't working
No face unlock (libs missing) works with new gapps
calendar sync provider missing works with new gapps
How to build
This ROM is build with the original Google sources:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r2
See https://source.android.com/source/building.html for build instructions.
Binary blobs are taken from https://developers.google.com/android/nexus/blobs-preview.
The kernel is the default precompiled kernel provided by Google (can be found in device/lge/mako-kernel/kernel).
To prepare for root, you have to remove the seclabel line from system/core/rootdir/init.rc:
Code:
service flash_recovery /system/bin/install-recovery.sh
class main
seclabel u:r:install_recovery:s0
oneshot
C-o-M said:
Welcome to Lollipop
Download: https://drive.google.com/file/d/0B10l7w-7w3boRzlmT1pxSFF5YlU/view?usp=sharing
We don't have 5.0 gapps yet, so I flashed pa-gapps-modular-mini-4.4.4-20140930 (after removing the version check in updater-script). Works great so far.
I'm running a dirty upgrade from 4.4.4, no issues so far. Just format /system, flash ota.zip and gapps, wipe cache and enjoy.
Click to expand...
Click to collapse
I guess this requires me to be running stock 4.4.4 before flashing.
Could you post the system.img , userdata.img , cache.img , boot.img and recovery.img so I could flash it via fastboot.
Thanks
Amazing work!!
can you upload modified pa gapps??
or any instruction to modify it?
Good job!
trasteando...
is this from google ?
richardyusan said:
is this from google ?
Click to expand...
Click to collapse
all ROM's are from Google's base dude
maybe what you really mean is from stock L image?
is this rooted guys?
Is this official aosp build and can I clean flash?
Please explain how to root tris ROM?!
C-o-M said:
Welcome to Lollipop
Download: https://drive.google.com/file/d/0B10l7w-7w3boRzlmT1pxSFF5YlU/view?usp=sharing
We don't have 5.0 gapps yet, so I flashed pa-gapps-modular-mini-4.4.4-20140930 (after removing the version check in updater-script). Works great so far.
I'm running a dirty upgrade from 4.4.4, no issues so far. Just format /system, flash ota.zip and gapps, wipe cache and enjoy.
Click to expand...
Click to collapse
dirty flash from stock 4.4.4 ?
also can you provide a link to working gapps
great job , waiting issues from other
groovepeppy said:
all ROM's are from Google's base dude
maybe what you really mean is from stock L image?
Click to expand...
Click to collapse
lol you don't say
we know every android build is from google
is this official from google or not?
richardyusan said:
lol you don't say
we know every android build is from google
is this official from google or not?
Click to expand...
Click to collapse
It's in the topic dude.
AOSP not OTA
Bladyle said:
It's in the topic dude.
AOSP not OTA
Click to expand...
Click to collapse
What he means is this proper aosp fully working 100% and has latest kernel and everything?
SRun said:
What he means is this proper aosp fully working 100% and has latest kernel and everything?
Click to expand...
Click to collapse
it will be 100% working when we have OTA or after some time with AOSP when developers fix all the missing binaries, libraries, bugs and etc.
SRun said:
What he means is this proper aosp fully working 100% and has latest kernel and everything?
Click to expand...
Click to collapse
i think we should install the rom and experience
Bugs? Root? Smooth? Please post bugs and stuff
I'm returning to stock 4.4.4 as I type this, and then I will do a clean flash of this 5.0 AOSP build and see how I go. Shall report back here upon completion.
richardyusan said:
lol you don't say
we know every android build is from google
is this official from google or not?
Click to expand...
Click to collapse
understood "sam"
that's why i wrote "maybe what you really mean is from stock L image?"
how to i disable the version check to install gapps?
anyway to get the official launcher? the one in this rom looks like 4.4 stock
I have a Nexus 5X on the Developer Preview 5 and twrp can't mount the data partition to flash SuperSu so could I flash SuperSu using the command line only
PKSYHR said:
I have a Nexus 5X on the Developer Preview 5 and twrp can't mount the data partition to flash SuperSu so could I flash SuperSu using the command line only
Click to expand...
Click to collapse
It can't mount the /data partition because your probably encrypted. I'd recommend unencrypting before proceeding on the N Previews as I constantly had problems encrypted.
Okay thanks I'll try that
So I would have to flash factory then root then disable encryption then return to the developer preview correct?
PKSYHR said:
So I would have to flash factory then root then disable encryption then return to the developer preview correct?
Click to expand...
Click to collapse
No you'd run fastboot format userdata which wipes your ENTIRE INTERNAL STORAGE beware. Make backups.
So the developer preview doesn't force encryption at boot?
Or would I format user data then flash supersu then boot into N 5
PKSYHR said:
Or would I format user data then flash supersu then boot into N 5
Click to expand...
Click to collapse
This.
Okay thank you very much for all the help
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
@pl_blaze brother always thank you for the contributions that you do without coming to the light .and thanks for you @op to post working twrp for stock
this twrp will work on 7.1.2 ? i'm now on aex rom
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
I reshare this twrp img on Telegram group,I tested it, works without problem
Flash of permaent twrp not tested by me
It's a good twrp!
CosmicDan said:
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
Click to expand...
Click to collapse
what does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
View attachment 4438212
teacapan said:
Fastboot boot (hotboot) anwhat does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
Click to expand...
Click to collapse
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
alkesh95 said:
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
Click to expand...
Click to collapse
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
It's possible to make password for twrp
DELETED.
lef7er1s said:
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
Click to expand...
Click to collapse
1-yes
2-yes
3-yes
Anyway thanks for try help me.
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Polluktus said:
this twrp will work on 7.1.2 ? i'm now on aex rom
Click to expand...
Click to collapse
Not sure, I've only tested on stock Oreo. Try and and let us know!
atttoush said:
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
Click to expand...
Click to collapse
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Sounds like you just need to learn more about how to use console tools. You need to make sure the "fastboot boot filename.img" command will have a "filename.img" that matches the img filename in the current directory. This is just an example - substitute "filename.img" for the real filename. Use the CD command to change directory to where the img is.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Click to expand...
Click to collapse
Try renaming the img file to something simpler like oreo_twrp.img
Edit: ah yes, the file you are pointing to has to be in the same directory where you opened cmd window, as cosmicdan stated above
CosmicDan said:
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
Click to expand...
Click to collapse
Glad you open this thread. I'll wait for your compiled version to give it a try
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
silv3rfox said:
Glad you open this thread. I'll wait for your compiled version to give it a try
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
Click to expand...
Click to collapse
Thanks, i will.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
Before flashing recovery
CD C:\Users\YOUR_USERNAME\Desktop\Adb
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
The name of the file is ending with .img, delete ending " .img ", see below that patched_boot without .img in the end
Thanks for this. I checked out the differences between this and the flashable zip I was using (twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester) and found this:
Code:
# write the new boot image to boot block
write_boot() {
print "Writing new boot image to memory..."
cd "$tmp"
if $use_dd; then
dd if=boot-new-a.img of="$boot_block"_a
[ $? = 0 ] || abort "Failed to write boot image A! You may need to restore your boot partition"
dd if=boot-new-b.img of="$boot_block"_b
[ $? = 0 ] || abort "Failed to write boot image B! You may need to restore your boot partition"
else
flash_image "$boot_block" boot-new.img
fi
[ $? = 0 ] || abort "Failed to write boot image! You may need to restore your boot partition"
}
This also flashes it into boot_a and boot_b correct?
What other differences does this have over that?
Unofficial TWRP Upstream for hero2lte
- TWRP 3.3.0-0
- Built on top of latest kernel source and upstreamed to 3.18.138
- Support for Samsung ROMs and can mount data after using them
- Code was cleaned up a lot and it should be more stable.
Credits to Ivan Meler for kernel and device sources and exynos-linux-stable for the upstreaming of linux kernel for our devices.
Instructions:
How to install TWRP recovery.img
1. Boot into an existing TWRP build
2. Download recovery image.
3. Copy TWRP image to your device
3. Click the 'Install' button
4. Click the 'Install Image' button
5. Navigate to where you downloaded the image and click on it
6. Select 'Recovery' partition option from the list, and swipe to confirm flash
7. Reboot back into recovery and you'll be in the updated recovery.
--
How to install Odin recovery.tar
1. Download Odin3 v3.13.1
2. Download Odin flashable
4. Restart your device in to Download mode (by holding Vol- & Home & Power)
5. Connect your device to your computer
6. Click 'AP' and select the .tar image you downloaded
7. Click the 'Start' button to flash the recovery
8. Reboot into recovery (by holding Vol+ & Home & Power) after successful flash.
Downloads:
16-04-19
————-
TWRP recovery.img
Odin recovery.tar
Sources: https://gitlab.com/developerlukeroms/twrp-hero
Thank you! I'm already using Tkkg1994's moded version but I guess you made some updates and improvments on it.
gonna flash it later.
edit: No freezing while changing time zone and language. Working really smooth. I think it's also faster while getting back-up and creating diggest.
Adding it to my signature since many people asking about mount data problems on custom rom threads. Once again thank you for the great work.
is there quota support like tkkg1994-version?
I flashed this version and everything went ok but i only noticed that battery level is always lower in twrp but not a big deal,thanks.
dangerhouse said:
is there quota support like tkkg1994-version?
Click to expand...
Click to collapse
Yep
Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)
Champ16 said:
Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)
Click to expand...
Click to collapse
I'm using it on pie port, working great. you can take it as Android 8.1+
Champ16 said:
Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)
Click to expand...
Click to collapse
Yes, android 8.1 means the twrp base, not what rom it works for. it works perfectly on pie roms
huge thank you dude!!
turbolukex5 said:
Unofficial TWRP Upstream for hero2lte
Click to expand...
Click to collapse
Is there a way to make TWRP settings permanent? It reset to default after some time. (It's like that with official one too) also anychance to have it without Official TWRP app? I uninstall it but after 1st recovery boot it comes back again. Have to keep it disabled.
The settings for twrp saved in internal sdcard... Don't delete the TWRP folder
wurstherpes said:
The settings for twrp saved in internal sdcard... Don't delete the TWRP folder
Click to expand...
Click to collapse
That really helped Thank you!
rroyy said:
Is there a way to make TWRP settings permanent? It reset to default after some time. (It's like that with official one too) also anychance to have it without Official TWRP app? I uninstall it but after 1st recovery boot it comes back again. Have to keep it disabled.
Click to expand...
Click to collapse
You can't if you wipe internal storage, plus theres an option to uncheck installing twrp app in the recovery.
Is it possible to add f2fs data and cache
Good working ty so much
Nice work
But can it keep data decrypted after I install magisk?
Currently using root with supersu
gupt07ash said:
Nice work
But can it keep data decrypted after I install magisk?
Currently using root with supersu
Click to expand...
Click to collapse
As long as dm-verity is disabled, it will keep decrypted, without this twrp it wouldnt mount to twrp although being decrypted
turbolukex5 said:
As long as dm-verity is disabled, it will keep decrypted, without this twrp it wouldnt mount to twrp although being decrypted
Click to expand...
Click to collapse
This worked like a charm. I can read internal partition over magisk now. But I'm getting an error while making a backup. the recovery says "E: recv error on uevent". this error does not interrupt the backup progress and the backup can still be completed but its an error I keep getting.
gupt07ash said:
This worked like a charm. I can read internal partition over magisk now. But I'm getting an error while making a backup. the recovery says "E: recv error on uevent". this error does not interrupt the backup progress and the backup can still be completed but its an error I keep getting.
Click to expand...
Click to collapse
E: recv error on uevent is harmless message, no need to worry about it.
turbolukex5 said:
E: recv error on uevent is harmless message, no need to worry about it.
Click to expand...
Click to collapse
Bruh if you made this, you're a legend!
I can finally use root hide and make full backups
Thanks :good: