FORUMS

[RECOVERY]TWRP 2.6.3.0 touch recovery w/ working AROMA touch[10-14-2013]

206 posts
Thanks Meter: 164
 
By nickdollahz, Senior Member on 14th October 2013, 10:51 PM
Post Reply Email Thread
So here is the latest version of TWRP with AROMA touch working.
It is no longer based off of emwno repos so I think it is worthy of a new thread. Also aroma touch is now working after some kernel modifications.

Changelog:
What's new in 2.6.3.0:

Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:

Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
What's new in 2.6.0.0:

Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.

Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks


Download:

N5100: http://www.androidfilehost.com/?fid=23159073880936414
N5110: http://www.androidfilehost.com/?fid=23156208500211927
Now go touch all over those roms those roms!

Well here is a aroma demo zip to play around with until ROM Chefs utilize aroma touch.

Credit:
@sbrissen for original port of CM10.1/10.2 to n5110.
@Maui for original port of CM10.1 to n5100.
@Dees_Troy & TEAMWIN for making TWRP

Donations:
Kraszimir Sziderov - $.$$
The Following 20 Users Say Thank You to nickdollahz For This Useful Post: [ View ] Gift nickdollahz Ad-Free
15th October 2013, 11:01 AM |#2  
Senior Member
Italy
Thanks Meter: 83
 
More
it's fully working ? some bug apart the update-script ?

ps: thanks for your hard work !! thanks from my N5110 !!!
15th October 2013, 11:34 AM |#3  
OP Senior Member
Flag Glastonbury
Thanks Meter: 164
 
Donate to Me
More
AFAIK, it should be working 100%.

N5110 now have a separate build.
The assert issue is because I build from n5100 device tree which has. "TARGET_OTA_ASSERT_DEVICE := kona3gxx,n5100,GT-N5100,kona3g"

so rom like sbrissen CM10.2 for N5110 has this lines:

assert(getprop("ro.product.device") == "konawifixx" || getprop("ro.build.product") == "konawifixx" ||
getprop("ro.product.device") == "n5110" || getprop("ro.build.product") == "n5110" ||
getprop("ro.product.device") == "GT-N5110" || getprop("ro.build.product") == "GT-N5110" ||
getprop("ro.product.device") == "konawifi" || getprop("ro.build.product") == "konawifi");


that assert will fail. so you can remove that line and it will flash until I build for N5110.
The Following User Says Thank You to nickdollahz For This Useful Post: [ View ] Gift nickdollahz Ad-Free
15th October 2013, 01:32 PM |#4  
Junior Member
Flag Kyiv
Thanks Meter: 0
 
More
Thanks for the good work!
There is still no 'Mount USB Storage' button in the 'Mount Menu'
AROMA touch working fine (n5100)!
15th October 2013, 02:12 PM |#5  
OP Senior Member
Flag Glastonbury
Thanks Meter: 164
 
Donate to Me
More
That is because it doesn't work. It is a TWRP problem outlined here: http://teamw.in/DataMedia

There is a way to get the phone in UMS mode in android though so might be doable in recovery. Even so we will only get the external sd card part. Wont be able to mount the internal storage.
The Following User Says Thank You to nickdollahz For This Useful Post: [ View ] Gift nickdollahz Ad-Free
17th October 2013, 12:15 AM |#6  
OP Senior Member
Flag Glastonbury
Thanks Meter: 164
 
Donate to Me
More
Alright N5110 build is up. Cant test it because I don't have the device but should be good to go.
The Following User Says Thank You to nickdollahz For This Useful Post: [ View ] Gift nickdollahz Ad-Free
17th October 2013, 06:24 AM |#7  
Jhokur's Avatar
Member
Thanks Meter: 6
 
More
Just tried to install for the 5110 but received an update binary error - going to redownload directly and try again.
17th October 2013, 07:36 AM |#8  
OP Senior Member
Flag Glastonbury
Thanks Meter: 164
 
Donate to Me
More
Yup, I did it again. lol Hopefully Link fixed now.
The Following User Says Thank You to nickdollahz For This Useful Post: [ View ] Gift nickdollahz Ad-Free
17th October 2013, 10:46 AM |#9  
Senior Member
Thanks Meter: 35
 
More
EDIT- Something funky was happening (buttons wouldn't work; I'd touch on one side of the screen and would hit a button apparently)after installing this, so I flashed back to the previous version.
17th October 2013, 12:59 PM |#10  
OP Senior Member
Flag Glastonbury
Thanks Meter: 164
 
Donate to Me
More
On which version? Looks like the n5110 version. Yeah I have no way to test it for that device. I'll see what I can do.

Found Issue with n5110 version. Forgot to fix touch drivers. in that build. Fixing it now and will reupload in the next hour. Thanks for reporting

New build for n5110 http://www.androidfilehost.com/?fid=23156208500211927.
The Following 5 Users Say Thank You to nickdollahz For This Useful Post: [ View ] Gift nickdollahz Ad-Free
17th October 2013, 02:39 PM |#11  
Senior Member
Thanks Meter: 35
 
More
Quote:
Originally Posted by nickdollahz

On which version? Looks like the n5110 version. Yeah I have no way to test it for that device. I'll see what I can do.

Found Issue with n5110 version. Forgot to fix touch drivers. in that build. Fixing it now and will reupload in the next hour. Thanks for reporting

New build for n5110 http://www.androidfilehost.com/?fid=23156208500211927.

That one works perfectly! Thank you so much.
The Following User Says Thank You to Melamunna For This Useful Post: [ View ] Gift Melamunna Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes