FORUMS
Remove All Ads from XDA

[ROM] Evervolv | 3.2.0p1 [AOSP]

560 posts
Thanks Meter: 1,720
 
By preludedrew, Inactive Recognized Developer on 13th December 2012, 04:25 AM
Post Reply Email Thread
18th May 2014, 12:47 PM |#1101  
preludedrew's Avatar
OP Inactive Recognized Developer
Flag Santan Valley
Thanks Meter: 1,720
 
Donate to Me
More
In preparation for the next build. I've got a new recovery for ya'all. The latest twrp recovery was using the old 2.6 kernel. This is completely updated for newer roms ( 4.0+), but should still allow older roms to be flashed. This is going to be needed because we'll be adding SELinux support. Please let me know if there are any issues with other roms and I'll look into submitting this for official status. So far my testing has concluded with no issues

TWRP 2.7.0.0 --
http://www.evervolv.com/get/openreco....0.0-vivow.img

I'll be adding a zip to run, that will fix some other issues with ext4 partitions. Need to finish testing it though.

Lemme know if there's any questions. If there are any issues, please report right away.

Thanks
-Andrew
The Following 7 Users Say Thank You to preludedrew For This Useful Post: [ View ] Gift preludedrew Ad-Free
18th May 2014, 02:26 PM |#1102  
Retired Forum Moderator
Thanks Meter: 124
 
More
Quote:
Originally Posted by preludedrew

In preparation for the next build. I've got a new recovery for ya'all. The latest twrp recovery was using the old 2.6 kernel. This is completely updated for newer roms ( 4.0+), but should still allow older roms to be flashed. This is going to be needed because we'll be adding SELinux support. Please let me know if there are any issues with other roms and I'll look into submitting this for official status. So far my testing has concluded with no issues

TWRP 2.7.0.0 --
http://www.evervolv.com/get/openreco....0.0-vivow.img

I'll be adding a zip to run, that will fix some other issues with ext4 partitions. Need to finish testing it though.

Lemme know if there's any questions. If there are any issues, please report right away.

Thanks
-Andrew

Will 4ext still work? I think it was able to flash a lot of the newer roms.

Thanks for your continued support.
18th May 2014, 03:51 PM |#1103  
Senior Member
Flag Duluth MN
Thanks Meter: 265
 
More
Quote:
Originally Posted by preludedrew

In preparation for the next build. I've got a new recovery for ya'all. The latest twrp recovery was using the old 2.6 kernel. This is completely updated for newer roms ( 4.0+), but should still allow older roms to be flashed. This is going to be needed because we'll be adding SELinux support. Please let me know if there are any issues with other roms and I'll look into submitting this for official status. So far my testing has concluded with no issues

TWRP 2.7.0.0 --
http://www.evervolv.com/get/openreco....0.0-vivow.img

I'll be adding a zip to run, that will fix some other issues with ext4 partitions. Need to finish testing it though.

@preludeandrew We have been trained by Chilly and others over the years to use the 4EXT recovery. You know much more about this but it has to do with partitions and formatting issues unique to DINC2 as I understand. His superduperwipe needs 4EXT, etc. The latest 4EXT flashes kitkat roms no problem. I personally like TWRP and use it as much as possible except on DINC2. Can you think of any reason why 4EXT has advantages. Having said that, I have gotten used to 4EXT too.
18th May 2014, 10:37 PM |#1104  
preludedrew's Avatar
OP Inactive Recognized Developer
Flag Santan Valley
Thanks Meter: 1,720
 
Donate to Me
More
Although you shouldn't need to, you can go back to 4EXT when not wanting to flash evervolv ( or any other kitkat roms that move to proper SELinux ). I tested his superduperwipe and it seems to work properly on my device. If chilly reads this, I analyzed what your sdw was doing, and noticed that there's no assert for device. Since your scripts use static block devices, if someone was to take that and think it'd work on another device... they could cause some issues.

Back on the subject of recovery. Going forward, no kitkat Evervolv builds will flash properly without SELinux support in the recovery. ( I spent more than 6 hours last night / this morning making sure this worked properly ). If someone / chilly wants to update 4EXT, let me know and I'll lend my help on the issue.
The Following 5 Users Say Thank You to preludedrew For This Useful Post: [ View ] Gift preludedrew Ad-Free
19th May 2014, 02:48 AM |#1105  
brymaster5000's Avatar
Recognized Contributor
Flag New Hampshire
Thanks Meter: 3,167
 
Donate to Me
More
Quote:
Originally Posted by preludedrew

In preparation for the next build. I've got a new recovery for ya'all. The latest twrp recovery was using the old 2.6 kernel. This is completely updated for newer roms ( 4.0+), but should still allow older roms to be flashed. This is going to be needed because we'll be adding SELinux support. Please let me know if there are any issues with other roms and I'll look into submitting this for official status. So far my testing has concluded with no issues

TWRP 2.7.0.0 --
http://www.evervolv.com/get/openreco....0.0-vivow.img

I'll be adding a zip to run, that will fix some other issues with ext4 partitions. Need to finish testing it though.

Lemme know if there's any questions. If there are any issues, please report right away.

Thanks
-Andrew

This is excellent news. Thanks drew.

Sent from my Lunar Ecliptic One.
22nd May 2014, 05:03 PM |#1106  
Quote:
Originally Posted by preludedrew

In preparation for the next build. I've got a new recovery for ya'all. The latest twrp recovery was using the old 2.6 kernel. This is completely updated for newer roms ( 4.0+), but should still allow older roms to be flashed. This is going to be needed because we'll be adding SELinux support. Please let me know if there are any issues with other roms and I'll look into submitting this for official status. So far my testing has concluded with no issues

TWRP 2.7.0.0 --
http://www.evervolv.com/get/openreco....0.0-vivow.img

I'll be adding a zip to run, that will fix some other issues with ext4 partitions. Need to finish testing it though.

Lemme know if there's any questions. If there are any issues, please report right away.

Thanks
-Andrew


I was able to put this into a zip file and install with CWM. I tested backup, restore, wipe, install, vibration settings, and adb connection and shell. All seems to work well!
---------------------------------------------------------------------------------------
Update: I'm not quite sure what happened. I did attempt to do something with the theme, but I did it from the menu.

When I reboot into recovery, I am now in a place where TWRP is just flashing the 'teamwin' screen and not progressing to the option panels.

I can make an adb connection and have reflashed the TWRP recovery through dd in an adb shell, but on reboot, I get the same situation.

I also flashed TWRP from fastboot and got the same result.

I can boot into the rom with no problems.
-------------------------------------------------------------------
I ended up reflashing CWM-6.0.4.7 to get a working recovery. Re-installing TWRP just gave me the flashing 'teamwin' screen.
23rd May 2014, 05:08 AM |#1107  
preludedrew's Avatar
OP Inactive Recognized Developer
Flag Santan Valley
Thanks Meter: 1,720
 
Donate to Me
More
Okay, I ran into issues in the first build or so similar to this ( TWRP splash just flashed on for a second, the off and repeated infinitely ). I didn't have the fstab in the correct location. This has been fixed so I'm not sure what your issue is. Try this in the beginning while it's flashing the twrp splash:

Code:
adb shell cat /tmp/recovery.log
it seems to be rebooting twrp continuously, so you may have to run it a couple times and get it at the perfect time.

If/when you get the log, paste it to: http://paste.evervolv.com/ and grab me the link!
23rd May 2014, 01:38 PM |#1108  
Quote:
Originally Posted by preludedrew

Okay, I ran into issues in the first build or so similar to this ( TWRP splash just flashed on for a second, the off and repeated infinitely ). I didn't have the fstab in the correct location. This has been fixed so I'm not sure what your issue is. Try this in the beginning while it's flashing the twrp splash:

Code:
adb shell cat /tmp/recovery.log
it seems to be rebooting twrp continuously, so you may have to run it a couple times and get it at the perfect time.

If/when you get the log, paste it to: http://paste.evervolv.com/ and grab me the link!

I pulled the battery for a while, then re-installed TRWP and it now is working. I will see if I can get it to fail again the same way and get that log for you.

-------------------------------------------------------------------------------------------------------
I was able to get the behavior again. It happened after I cancelled an adb sideload operation. At least, that was the most unusual thing I did. Your site did not give me a URL, so I am posting the log here.

I:Attempt to load settings from settings file...
I:Loading settings from '/sdcard/TWRP/.twrps'.
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 2.7.0.0 on Fri May 23 12:43:52 2014
I:Single storage only.
I:No internal storage defined.
I:No storage defined, defaulting to /sdcard.
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file'
I:TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
Starting the UI...Pixel format: 480x800 @ 16bpp
Pixel format: BGR_565
Not using qualcomm overlay, 'msmfb'
framebuffer: fd 3 (480 x 800)
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/system'
I:Processing '/data'
I:Processing '/cache'
I:Processing '/sdcard'
I:Processing '/sd-ext'
I:Processing '/misc'
I:Creating Android Secure: /sdcard/.android_secure
I:Backup folder set to '/sdcard/TWRP/BACKUPS/HT***********'
I:Settings storage is '/sdcard'
Updating partition details...
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
I:Unmounting main partitions...


Partition Logs:
/boot | /dev/block/mmcblk0p22 | Size: 4MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p22
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/recovery | /dev/block/mmcblk0p21 | Size: 8MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p21
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/system | /dev/block/mmcblk0p25 | Size: 549MB Used: 415MB Free: 133MB Backup Size: 415MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p25
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/data | /dev/block/mmcblk0p26 | Size: 1156MB Used: 301MB Free: 855MB Backup Size: 301MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Encrypt_Backup Use_Userdata_Encryption
Primary_Block_Device: /dev/block/mmcblk0p26
Display_Name: Data
Storage_Name: Data
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/cache | /dev/block/mmcblk0p27 | Size: 293MB Used: 21MB Free: 271MB Backup Size: 21MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p27
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/sdcard | /dev/block/mmcblk1p1 | Size: 1941MB Used: 1366MB Free: 574MB Backup Size: 2MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI Removable IsPresent Has_Android_Secure Is_Storage
Symlink_Path: /sdcard/.android_secure
Symlink_Mount_Point: /and-sec
Primary_Block_Device: /dev/block/mmcblk1p1
Alternate_Block_Device: /dev/block/mmcblk1
Display_Name: sdcard
Storage_Name: sdcard
Backup_Path: /and-sec
Backup_Name: and-sec
Backup_Display_Name: Android Secure
Storage_Path: /sdcard
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files

/sd-ext | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI Removable Can_Encrypt_Backup Use_Userdata_Encryption
Primary_Block_Device: /dev/block/mmcblk1p2
Display_Name: SD-Ext
Storage_Name: SD-Ext
Backup_Path: /sd-ext
Backup_Name: sd-ext
Backup_Display_Name: SD-Ext
Storage_Path: /sd-ext
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/misc | /dev/block/mmcblk0p17 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p17
Display_Name: misc
Storage_Name: misc
Backup_Path: /misc
Backup_Name: misc
Backup_Display_Name: misc
Storage_Path: /misc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

I:Loading package: TWRP (/script/ui.xml)
I:Loading package: TWRP (/sdcard/TWRP/theme/ui.zip)
I:Loading package: TWRP (/res/ui.xml)
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page main
I:Loading page main2
I:Loading page install
I:Loading page flash_confirm
I:Loading page flash_zip
I:Loading page flash_done
I:Loading page clear_vars
I:Loading page confirm_action
I:Loading page action_page
I:Loading page singleaction_page
I:Loading page action_complete
I:Loading page filecheck
I:Loading page rebootcheck
I:Loading page wipe
I:Loading page advancedwipe
I:Loading page formatdata
I:Loading page formatdata_confirm
I:Loading page backup
I:Loading page backupname1
I:Loading page backupname2
I:Loading page backupencryption
I:Loading page backupencryption2
I:Loading page checkbackuppassword
I:Loading page backup_run
I:Loading page restore
I:Loading page restore_read
I:Loading page restore_decrypt
I:Loading page try_restore_decrypt
I:Loading page restore_select
I:Loading page renamebackup
I:Loading page restore_run
I:Loading page selectstorage
I:Loading page mount
I:Loading page usb_mount
I:Loading page usb_umount
I:Loading page reboot
I:Loading page settings
I:Loading page timezone
I:Loading page screen
I:Loading page Vibrate
I:Loading page advanced
I:Loading page partsdcard
I:Loading page htcdumlock
I:Loading page lock
I:Loading page filemanagerlist
I:Loading page filemanageroptions
I:Loading page choosedestinationfolder
I:Loading page filemanagerrenamefile
I:Loading page filemanagerrenamefolder
I:Loading page filemanagerchmod
I:Loading page filemanagerconfirm
I:Loading page filemanageracction
I:Loading page decrypt
I:Loading page trydecrypt
I:Loading page terminalfolder
I:Loading page terminalcommand
I:Loading page sideload
I:Loading page installsu
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
SELinux contexts loaded from /file_contexts
Full SELinux support is present.
Startup Commands: I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/sdcard/TWRP/.twrps'.


The actual log is quite long and shows repetition. I included slightly more (two lines are shown twice) than one repetition so you can see what is happening.
23rd May 2014, 05:49 PM |#1109  
OK, I can reliably reproduce and fix the problem in TWRP recovery.

The issue comes up if you are under the settings tab and change the different settings too quickly, say by changing the screen settings, then re-setting to defaults, then changing them again. Evidently, if this is done too quickly, the .twrps file gets corrupted. The next time TWRP is booted, it goes into a loop. If, however, the .twrps file is deleted, TWRP will boot normally.
The Following User Says Thank You to polymath257 For This Useful Post: [ View ] Gift polymath257 Ad-Free
25th May 2014, 12:57 AM |#1110  
preludedrew's Avatar
OP Inactive Recognized Developer
Flag Santan Valley
Thanks Meter: 1,720
 
Donate to Me
More
Quote:
Originally Posted by polymath257

OK, I can reliably reproduce and fix the problem in TWRP recovery.

The issue comes up if you are under the settings tab and change the different settings too quickly, say by changing the screen settings, then re-setting to defaults, then changing them again. Evidently, if this is done too quickly, the .twrps file gets corrupted. The next time TWRP is booted, it goes into a loop. If, however, the .twrps file is deleted, TWRP will boot normally.

Building another tester for you with a possible fix. I'll let edit this post with the link.

EDIT: I've been unable to reproduce the issue with this recovery: http://www.evervolv.com/get/openreco...ivow-test2.img
Please re-test everything that should be working again.
The Following 2 Users Say Thank You to preludedrew For This Useful Post: [ View ] Gift preludedrew Ad-Free
25th May 2014, 01:35 PM |#1111  
Quote:
Originally Posted by preludedrew

Building another tester for you with a possible fix. I'll let edit this post with the link.

EDIT: I've been unable to reproduce the issue with this recovery: http://www.evervolv.com/get/openreco...ivow-test2.img
Please re-test everything that should be working again.


I was also unable to break this one. The steps that broke the previous do not break this one. Good work!
The Following 2 Users Say Thank You to polymath257 For This Useful Post: [ View ] Gift polymath257 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