Related
Team Win Recovery Project 2.8, 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.
For official change logs, see here:
http://teamw.in/project/twrp2
For recent code merges, see the Omnirom gerrit here:
https://gerrit.omnirom.org/#/q/proje...+status:merged
______________________________________
Download flashable TWRP 2.8.1.1 zip for TF101:
signed_twrp-2.8.1.1_tf101.zip
TWRP 2.8.1.1 MD5 sum for TF101:
signed_twrp-2.8.1.1_tf101.zip.md5
______________________________________
Download flashable TWRP-2.8.1.1 zip for TF101G:
signed_twrp-2.8.1.1_tf101g.zip
TWRP-2.8.1.1 MD5 sum for TF101G:
signed_twrp-2.8.1.1_tf101g.zip.md5
______________________________________
Download flashable TWRP 2.8.1.1 zip for SL101 Slider:
signed_twrp-2.8.1.1_sl101.zip
TWRP 2.8.1.1 MD5 sum for SL101 Slider:
signed_twrp-2.8.1.1_sl101.zip.md5
____________________________________
If experiencing any boot loops or you don't see the blue-green flash progress bar after you thought you just flashed a recovery, then try the suggestions from this post:
http://forum.xda-developers.com/showpost.php?p=46806749&postcount=187
concerning dd methods to clear a stuck flag and maybe flash a recovery blob if other methods aren't working for you, particularly if you attempted to use ROM Manager or certain versions of CWM or other programs to flash this recovery.
____________________________________
Credits:
Team Win Recovery Project
josteink for tf101 device tree
timduru for tf101 device tree
josteink for tf101 kernel source
OmniROM for Android 4.4.2 base
Google for Android AOSP
Anyone else who previously contributed to this.
In particular, many thanks to josteink who encouraged this and provided much useful information to get it going.
For more information:
http://teamw.in/project/twrp2
TWRP Screenshots
Latest screen shots from TWRP:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP Custom Themes [10-10-2013]
I will use this post to post links to custom TWRP themes, both my own and any that users would like to provide me the links to in a PM. This first one is my first attempt at TWRP theming and is just a pretty basic, modified stock theme. It is based on the stock theme for 1280x800 devices. I know everyone won't like it, but it is my first stab at it. Have fun and if anyone would like some instructions for creating a custom theme, then hit me up with a PM and I'll try to help. It is not really difficult, just time consuming and tedious work. There are also links to guides on the twrp site for theming.
Instructions:
Just download, reboot to recovery (you are running TWRP recovery?), flash the theme zip file, reboot, and reboot to recovery again to see the results.
[EDIT] Here's a second one for you:
sidneyk-theme2.zip download link:
https://dl.dropboxusercontent.com/u/47619656/sidneyk-theme2.zip
sidneyk-theme2.zip.md5 download link:
https://dl.dropboxusercontent.com/u/47619656/sidneyk-theme2.zip.md5
[EDIT] Here are some screenshots taken with my camera, as I don't know any other way to get them right now:
##########################
sidneyk TWRP custom theme zip download:
https://dl.dropboxusercontent.com/u/47619656/sidneyk-theme.zip
sidneyk-theme MD5 sum:
https://dl.dropboxusercontent.com/u/47619656/sidneyk-theme.zip.md5
Reserved #3
Awesome thanks a lot. I was wondering if you can do titanium custom zips with twrp? It seems i was not able to previously. Like flashing a user app or titanium itself?
Installed perfect!! Now waiting for KatKiss 4.3 v021
Thx for continuing to keep our beloved tf alive!!
Sent from my Transformer TF101 using XDA Premium 4 mobile app
YayYouFixedIt said:
Awesome thanks a lot. I was wondering if you can do titanium custom zips with twrp? It seems i was not able to previously. Like flashing a user app or titanium itself?
Click to expand...
Click to collapse
I never had much luck with titanium zips myself. I'll have to give it a try sometime.
Sent from my SAMSUNG-SGH-T769 using XDA Premium HD app
Thanks for taking this over man! Flashed it and it works perfeclty. Did a backup, full wipe, restore and it had no issues.
Is there anyway to have this app recognize the USB port (with a thumb drive) that's built into the keyboard attachment ?
Good jeez I need a third job just for donations! This is outstanding work man. Made a backup all good last night, and installing, wiping, fix perms seems work all fine for me as well. Thank you so very much for continue support in this awesome tab
~S-Off LTEvo; Back on the Always Solid Viper4G Latest; Expletive Deleted Kernel
cpu0/1: 1.5ghz ¦ 384mhz ¦ sleep: 486mhz max
Ondemand
fiops
thermald: dynamic
With tapatalk4
Hey all,
I've got a small problem with this version of TWRP 2.6.1.0 that was not present in any of the previous version I've used. The problem is each time I use this version no matter what function is preformed (all works fine) when it comes to restart the system I am presented with the following screen:
*********************************************
*********************************************
Fix Superuser Permissions?
Root permissions appear to be lost.
Fix root permissions now?
(Fixes permissions on su binary & app)
<Do Not Fix>
>> Swipe to fix Root >>
*********************************************
*********************************************
I've have cleaned SurerSU on system and reinstalled it with no errors, but did not work.
I've downgraded to 2.6.0.0 but still not worked.
I've restored from a working Nandroid Backup but no joy (TWRP 2.5.0.0) and no more permission screens.
Any idea what is going on???
worf105 said:
Hey all,
I've got a small problem with this version of TWRP 2.6.1.0 that was not present in any of the previous version I've used. The problem is each time I use this version no matter what function is preformed (all works fine) when it comes to restart the system I am presented with the following screen:
*********************************************
*********************************************
Fix Superuser Permissions?
Root permissions appear to be lost.
Fix root permissions now?
(Fixes permissions on su binary & app)
<Do Not Fix>
>> Swipe to fix Root >>
*********************************************
*********************************************
I've have cleaned SurerSU on system and reinstalled it with no errors, but did not work.
I've downgraded to 2.6.0.0 but still not worked.
I've restored from a working Nandroid Backup but no joy (TWRP 2.5.0.0) and no more permission screens.
Any idea what is going on???
Click to expand...
Click to collapse
I've only ever seen anything about reinstalling supersu after I've formatted data ( and factory reset ) and am getting ready to reboot, as suggested, because, of course, I've just wiped it out and have no OS or anything installed. I've said yes and I've said no, without any issues either way, but that was previous versions and not this particular one. Maybe your root really was messed up? There was supposedly an updated supersu included in this version or 1 back I believe according to the change logs.
the.teejster said:
Is there anyway to have this app recognize the USB port (with a thumb drive) that's built into the keyboard attachment ?
Click to expand...
Click to collapse
Did it work with any previous versions? I've not made any changes that would affect that functionality one way or the other, so if it worked before it should work now, if it didn't then it probably still won't.
sidneyk said:
I've only ever seen anything about reinstalling supersu after I've formatted data ( and factory reset ) and am getting ready to reboot, as suggested, because, of course, I've just wiped it out and have no OS or anything installed. I've said yes and I've said no, without any issues either way, but that was previous versions and not this particular one. Maybe your root really was messed up? There was supposedly an updated supersu included in this version or 1 back I believe according to the change logs.
Click to expand...
Click to collapse
Thanks sidneyk :good:
My root still functions flawlessly when using my TF101 no matter if I select Yes fix or No to the fix at reboot system. I now have restore the nandroid back up for earlier today as I have loads of changes that are not on my later backup. Now to look where ive found the download link to twrp2.5-tf101-unofficial.beta which works flawlessly
Cheers
worf105
worf105 said:
Thanks sidneyk :good:
My root still functions flawlessly when using my TF101 no matter if I select Yes fix or No to the fix at reboot system. I now have restore the nandroid back up for earlier today as I have loads of changes that are not on my later backup. Now to look where ive found the download link to twrp2.5-tf101-unofficial.beta which works flawlessly
Cheers
worf105
Click to expand...
Click to collapse
Sorry you had a bad experience with it. Did you also download the md5 file to verify a good download?
worf105 said:
Thanks sidneyk :good:
My root still functions flawlessly when using my TF101 no matter if I select Yes fix or No to the fix at reboot system. I now have restore the nandroid back up for earlier today as I have loads of changes that are not on my later backup. Now to look where ive found the download link to twrp2.5-tf101-unofficial.beta which works flawlessly
Cheers
worf105
Click to expand...
Click to collapse
2.5.0.0 download is in the 2.6.0.0 (joesteink's) thread.
frederuco said:
2.5.0.0 download is in the 2.6.0.0 (joesteink's) thread.
Click to expand...
Click to collapse
Thanks, found it :good:
---------- Post added at 01:31 PM ---------- Previous post was at 01:10 PM ----------
sidneyk said:
Sorry you had a bad experience with it. Did you also download the md5 file to verify a good download?
Click to expand...
Click to collapse
Now even 2.5.0.0 is doing the same.
I have now since done the following:
Wiped Cache, Dalvik cache and System,
Flashed KatKiss 4.3 r2.2 #20 ROM'
Flashed Gapps,
Flashed KatKernel 107b,
Flashed TWRP 2.6.1.0,
Wiped Cache & Dalvik Cache
Rebooted with no fix root permission screen,
Rebooted in to recovery, (2.6.1.0)
Deleted older Nandroid Backups,
Created new Nandroid Backup,
when finished creating new backup I am now presented with the fix superuser permission screen,
Swiped to fix superuser,
Reboots and root works fine, (opened up SuperSU v1.60 and no error or updates to binary required, Opened Root Checker Basic v5.0.6 by Joes Krim and verified root access with no errors.)
Rebooted into recover again,
Fixed Permission's (Successful)
selected Reboot button and still taking to the Fix Superuser Permission screen again so Swiped to Fix and TF101 reboots with no screen output,
Again check if root is OK on system, which it is,
Reboot to Recovery again and when in recovery I select reboot then system,
Presented with the Fix Superuser Premission screen again so I select Do Not Fix,
Reboot to system to verify Root which is OK,
Reboot into Recovery for the last time and selected reboot then system which brings up the Fix Superuser screen again,
Swiped to fix, system reboots OK and user (me) gives up
Any Ideas
worf105 said:
Thanks, found it :good:
---------- Post added at 01:31 PM ---------- Previous post was at 01:10 PM ----------
Now even 2.5.0.0 is doing the same.
I have now since done the following:
Wiped Cache, Dalvik cache and System,
Flashed KatKiss 4.3 r2.2 #20 ROM'
Flashed Gapps,
Flashed KatKernel 107b,
Flashed TWRP 2.6.1.0,
Wiped Cache & Dalvik Cache
Rebooted with no fix root permission screen,
Rebooted in to recovery, (2.6.1.0)
Deleted older Nandroid Backups,
Created new Nandroid Backup,
when finished creating new backup I am now presented with the fix superuser permission screen,
Swiped to fix superuser,
Reboots and root works fine, (opened up SuperSU v1.60 and no error or updates to binary required, Opened Root Checker Basic v5.0.6 by Joes Krim and verified root access with no errors.)
Rebooted into recover again,
Fixed Permission's (Successful)
selected Reboot button and still taking to the Fix Superuser Permission screen again so Swiped to Fix and TF101 reboots with no screen output,
Again check if root is OK on system, which it is,
Reboot to Recovery again and when in recovery I select reboot then system,
Presented with the Fix Superuser Premission screen again so I select Do Not Fix,
Reboot to system to verify Root which is OK,
Reboot into Recovery for the last time and selected reboot then system which brings up the Fix Superuser screen again,
Swiped to fix, system reboots OK and user (me) gives up
Any Ideas
Click to expand...
Click to collapse
You can't flash TWRP together with a ROM as flashing TWRP will overwrite the staging partition and the ROM's kernel will then not get flashed. So first flash your ROM, gapps and katkernel, then reboot into your rom, then reboot into recovery to flash TWRP, then reboot again.
sidneyk said:
Did it work with any previous versions? I've not made any changes that would affect that functionality one way or the other, so if it worked before it should work now, if it didn't then it probably still won't.
Click to expand...
Click to collapse
Ye it work great when running 2.5.0.0, no errors
worf105
---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------
jrohwer said:
You can't flash TWRP together with a ROM as flashing TWRP will overwrite the staging partition and the ROM's kernel will then not get flashed. So first flash your ROM, gapps and katkernel, then reboot into your rom, then reboot into recovery to flash TWRP, then reboot again.
Click to expand...
Click to collapse
Ok Thanks will flash on that order and remember it in future, will get back to you as I've done it with results. :good:
cheers
worf105
---------- Post added at 02:18 PM ---------- Previous post was at 01:49 PM ----------
worf105 said:
Ye it work great when running 2.5.0.0, no errors
worf105
---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------
Ok Thanks will flash on that order and remember it in future, will get back to you as I've done it with results. :good:
cheers
worf105
Click to expand...
Click to collapse
Done what you said but no joy. When I swipe to fix superuser it reboots that quickly it looks as if it doesn't have time to fix the problem before it reboots
sidneyk said:
Did it work with any previous versions? I've not made any changes that would affect that functionality one way or the other, so if it worked before it should work now, if it didn't then it probably still won't.
Click to expand...
Click to collapse
it didnt work before.
CM10.2 for Milestone2
[Downloads][Gapps]
It's based on defy(made by Quarx) version.
Changelog:
12.03.2014 - CM code synced. This is most likely the final CM10.2 build.
18.12.2013 - CM code synced
21.11.2013 - CM code synced
07.11.2013 - reverted wpa supplicant(fixes wifi tethering, wifi network list do not refresh again); torch tile added to quick settings; CM code synced
31.10.2013 - wpa supplicant updated(fixes wifi list updates); more kernel tweaks; TWRP updated; keyboard file names aligned(sholes-qwerty.kcm->sholes->keypad.kcm); CM code synced; new gapps available
23.10.2013 - Fixed baseband switching; no other changes, so don't update if you do not have problems with carrier signal
21.10.2013 - Interactive and ondemand CPU governors tweaked(Blachd0se) - this should fix battery drain in the latest build; polish keychars updated(thanks to Rabinhood; see NOTES); CM code synced
17.10.2013 - 720p recording enabled; CM code synced(Long Term Orbits(LTO) added)
10.10.2013 - Fixed(hope that this time for good) camera orientation when using custom camera apps(e.g. igcamera).
09.10.2013 - Reverted camera orientation changes(colors should be ok right now, but igcamera orientation is again incorrect-need some more time to figure this out); data transfer statistics(download/upload arrows on the wifi icon) fixed(Quarx/Blachd0se); CM code synced(resolved Settings->Buttons crash and black camera preview after taking a picture).
02.10.2013 - Fixed multitouch points number setting; Igcamera should behave ok right now; CM code synced
30.09.2013 - Added switching to horizontal mode when hardware keyboard is open; CM code synced; NOTE: you may need to add google account again after update from previous version(s), so sync/backup your google stuff.
26.09.2013 - Call recording fixed(tried with AutoCallRecorder 1.0.9 - present in some tezet's ROM's); Some more work on internal storage; CM code synced
25.09.2013 - Internal storage size fixed
24.09.2013 - Keyboard layout fixed
23.09.2013 - Camera should work ok at 848x480(720p not supported yet); CM code synced
20.09.2013 - Initial version
NOTES:
Keyboard - to access polish letters, choose Qwerty polish in Settings->Language & Input->Sholes keypad->Set up keyboard layout. Use ALT LOCK or ALT LOCK + SHIFT to get polish letters. ALT LOCK + '?' is mapped to pipe symbol('|').
If you wish to see national symbols for some other language, please download and update the following file (similarly as Rabinhood has done for polish symbols(look at letter A and ralt/shift+ralt modifiers)), test it by replacing file /system/usr/keychars/sholes-keypad.kcm with your version(reboot required), and once you are satisfied with the outcome, send it to me.
Known issues:
If bluetooth is on, and autocallrecording is installed, no sound during calls(reported by Fedroid)
Sound quality when using BT headset is not very high
Wifi list does not refresh.. workaround: turn wifi off and on
Sources:
repo init -u git://github.com/czechop/android.git -b cm-10.2
Installation
If coming from stock ROM or CM7:
install tezet's CM10 first(http://forum.xda-developers.com/showthread.php?t=1827801) and look at next point
If using tezet's CM10 ROM or engle mars's CM10.1:
go to bootmenu(press VOLUME DOWN key when booting);
choose recovery->custome recovery;
when in recovery, choose install zip from sdcard, and select the latest CM10.2 on your card;
in the same way install gapps.
reboot, and hold VOLUME DOWN button to go directly into bootmenu.
choose tools->file tools->format DATA + CACHE to ext4(note that you will loose your data(the ones on the sdcard are safe)).
reboot and... that's it
If coming from engle mars's CM10.2 ROM(haven't tried it, but should work):
go to bootmenu(press VOLUME DOWN key when booting);
choose recovery->TWRP;
when in recovery, choose install zip from sdcard, and select the latest CM10.2 on your card;
in the same way install gapps.
reboot, and hold VOLUME DOWN button to go directly into bootmenu.
choose tools->file tools->format DATA + CACHE to EXT4(note that you will loose your data(the ones on the sdcard are safe)).
reboot and... that's it
If want to get back to tezet's CM10 or engle mars's CM10.1:
go to bootmenu(press VOLUME DOWN key when booting);
choose tools->file tools->format data + cache to EXT3(not that you will loose your data(the ones on the sdcard are safe))
choose recovery->TWRP recovery
when in recovery, choose install zip from sdcard and instlall ROM you want.
in the same way install gapps(if not included in the ROM)
reboot
if something goes wrong... post here describing what's going on... there is a slight chance that someone will help you
Credits:
Credits for this rom goes to: Quarx2k, Tezet, Blachd0se, CM team... and many, many more.
czechop said:
CM10.2 for Milestone2
[Downloads][Gapps]
It's based on defy(made by Quarx) version.
Changelog:
20.09.2013 - Initial version
Known issues:
Camera is far from good
Call recording not working
Hardware keyboard might produce incorrect characters when ALT used in some languages(polish version works quite well)
Notes:
For installation instructions look at other threads
Full wipe recommended!!!
Sources:
repo init -u git://github.com/czechop/android.git -b cm-10.2
Click to expand...
Click to collapse
1. Fix camera, and it will be perfekt rom.
2. Just copy keyboard layout from CM10.2 of EngleMars.
3. Its very fast, and really nice ROM.
Bye
Faster than engle mars rom?
Can someone post photos how the rom looks like?
Good to see you back in the game, Czechop! The ROM is really great, very snappy. It seems like it is ready for daily use, but I hope you will be able to find time for future updates as well. Thanks!
---------- Post added at 08:46 PM ---------- Previous post was at 08:26 PM ----------
Just one minor issue. Keyboard layout doesn't work for me on version from 23th. I have tried with QWERTY, QWERTZ and AZERTY as well as with no keyboard layout selected at all. In all cases the characters with ALT were (totally) incorrect.
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
tezet said:
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
Click to expand...
Click to collapse
tezet is still alive! cm10.2 seems to become a really great and stable rom
you will find the qwertz keyfile attached. download and decompress it and change it, by replacing this file in system/usr/keychars and set permission to rw r r
cheers
Hey guys. I believe at least some of you have already tried this fresh ROM. Could you please share your comments? How does this ROM look like in comparison to Engle_Mars CM 10.2 in terms of performance and features? Do you think the differences make this ROM worth trying?
Thanks.
tezet said:
Good to see you back in the game, Czechop! The ROM is really great, very snappy. It seems like it is ready for daily use, but I hope you will be able to find time for future updates as well. Thanks!
---------- Post added at 08:46 PM ---------- Previous post was at 08:26 PM ----------
Just one minor issue. Keyboard layout doesn't work for me on version from 23th. I have tried with QWERTY, QWERTZ and AZERTY as well as with no keyboard layout selected at all. In all cases the characters with ALT were (totally) incorrect.
Click to expand...
Click to collapse
Hi Tezet... good to see you too You haven't posted anything for so long, that I started thinking you sold your phone and switched to some other brand. But after all, motorola is the best
Keyboard layout should be fine right now.
tezet said:
One more observation. The internal storage is only 256MB, and not 8GB. I suposse it's a leftover from Defy.
Click to expand...
Click to collapse
Haven't noticed it earlier... thanks, will have a look.
downloading the rom to test.
After I have installed'll post a print for the curious :cyclops:
To those who have installed this:
- How is battery life compared to EngleMars's 10.2?
- Can this be backed up via recovery, ie does the restore function actually work?
These are the only two areas in which EngleMars's, otherwise perfect in my opinion, ROM is lacking.
first impression: very, very similar to the ROM CM10.2 Engle_Mars.
In visual and performance ... Very stable.
Surely in the next updates will be even better.:good:
{ Internal memory showing wrong size. (~ 254mb only) }
gigabruno said:
{ Internal memory showing wrong size. (~ 254mb only) }
Click to expand...
Click to collapse
Should be fixed in the newest version
Tried to install this ROM twice (downloaded latest release twice from Google Drive), but ClockworkMod Recovery v2.5.0.8 is telling me:
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Am I doing something wrong? I don't see any installation instructions in the OP except "For installation instructions look at other threads" which doesn't help someone who isn't used to doing this sort of thing at all... I searched and found tezet's instructions for stock ROM users installing his CM10 release... they are as follows:
Installation guide for stock roms users
1) Root your phone (you may use SuperOneClick root method)
2) Install Droid2 Bootstrap Recovery
3) Open Droid2 Bootstrap Recovery and tap "Bootstrap Recovery", then "Reboot Recovery" granting root privileges. The phone should reboot into recovery. Use volume buttons to navigate, camera button to accept, power button to go back. You will install files by selecting "Install zip from sdcard".
4) Optionally: create a backup of your data
5) Install latest CM ROM image file.
6) Optionally: install Google Apps
7) Select "Wipe data/factory reset"
8) Reboot and enjoy
9) Optionally: select baseband version corresponding to your country and BPSW version
Click to expand...
Click to collapse
Is that not correct? I'm stuck at step 5 as CWM seemingly won't accept the .zip file I've downloaded (twice, to be sure I didn't get a corrupted download). So far I've only ever loaded SBF files using RSDLite (stock UK 2.3.4), so I'm sure I must be doing something wrong... A little help?
Thanks
As it is not mentioned anywhere, am I correctly assuming that Bluetooth is working flawlessly?
I'm excited to try this but BT is crucial!
Have you tried the "TWRP Recovery"?
xyphur said:
Tried to install this ROM twice (downloaded latest release twice from Google Drive), but ClockworkMod Recovery v2.5.0.8 is telling me:
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Am I doing something wrong? I don't see any installation instructions in the OP except "For installation instructions look at other threads" which doesn't help someone who isn't used to doing this sort of thing at all... I searched and found tezet's instructions for stock ROM users installing his CM10 release... they are as follows:
Is that not correct? I'm stuck at step 5 as CWM seemingly won't accept the .zip file I've downloaded (twice, to be sure I didn't get a corrupted download). So far I've only ever loaded SBF files using RSDLite (stock UK 2.3.4), so I'm sure I must be doing something wrong... A little help?
Thanks
Click to expand...
Click to collapse
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Here are the files you will need: http://www.mediafire.com/folder/1p23cv7r38491aq,nteg1stu575rjde/shared
gigabruno said:
Have you tried the "TWRP Recovery"?
Click to expand...
Click to collapse
I haven't yet, no. Of course, that may be because I was completely unaware of its existence, probably because most of these ROM release threads expect everyone reading them to know the ins and outs already... quite frustrating.
Is "TWRP 2.1.1" the latest available? Should I attempt to use that?
Appreciate the help btw...
---------- Post added at 08:43 AM ---------- Previous post was at 08:37 AM ----------
lulli1 said:
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Click to expand...
Click to collapse
That seems.... exceptionally convoluted, lol... I'll give it a try though. Thanks for the link.
---------- Post added at 09:12 AM ---------- Previous post was at 08:43 AM ----------
lulli1 said:
Flash Bootmenue with cwm3 first, out of your cwm2 (its the bootstrap recovery)
After that, boot into cwm3 and flash cwm5.
Now boot into cwm5 and flash the rom zip.
Click to expand...
Click to collapse
Okay, got CWM3 loaded, rebooted, CWM3 booted on its own. Then I loaded CWM5... took me a few tries, but I finally remembered how to enter the recovery menu... tried to load the ROM zip, now it says:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
...should I also have downloaded the matching .md5 file from OP's Google Drive link?
Also, I held 'X' during power-up, waited for the android exclamation logo, then hit vol down/vol up and got the blue text recovery menu titled "Android system recovery (3e)" is this correct? Or am I sitting in the stock recovery menu instead of CWM5? Sorry, I've forgotten much of this, it's been forever since last time...
---------- Post added at 09:45 AM ---------- Previous post was at 09:12 AM ----------
Okay, so it looks like CWM5 didn't flash... according to google searches, I should be staring at a recovery menu where Clockworkmod Recovery 5 is prominently displayed at the top... instead, as I outlined above, I'm seeing "Android system recovery (3e)" which sounds to me like I'm looking at the stock one...
What exactly should I be doing to load CWM5 from CWM3? The menus are completely different between CWM2 & CWM3, and once CWM5 is loaded/flashed, I can't seem to get into it... booting recovery simply reverts to whatever the (3e) menu is...
See what I meant about it sounding convoluted now? lol, yeah...
xyphur said:
Okay, got CWM3 loaded, rebooted, CWM3 booted on its own. Then I loaded CWM5... took me a few tries, but I finally remembered how to enter the recovery menu... tried to load the ROM zip, now it says:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
...should I also have downloaded the matching .md5 file from OP's Google Drive link?
Also, I held 'X' during power-up, waited for the android exclamation logo, then hit vol down/vol up and got the blue text recovery menu titled "Android system recovery (3e)" is this correct? Or am I sitting in the stock recovery menu instead of CWM5? Sorry, I've forgotten much of this, it's been forever since last time...
---------- Post added at 09:45 AM ---------- Previous post was at 09:12 AM ----------
Okay, so it looks like CWM5 didn't flash... according to google searches, I should be staring at a recovery menu where Clockworkmod Recovery 5 is prominently displayed at the top... instead, as I outlined above, I'm seeing "Android system recovery (3e)" which sounds to me like I'm looking at the stock one...
What exactly should I be doing to load CWM5 from CWM3? The menus are completely different between CWM2 & CWM3, and once CWM5 is loaded/flashed, I can't seem to get into it... booting recovery simply reverts to whatever the (3e) menu is...
See what I meant about it sounding convoluted now? lol, yeah...
Click to expand...
Click to collapse
reboot/turn on your device, press vol-down button while blue LED blink and choose recovery, then custom recovery. now you can install rom or cwm5.
henediac said:
reboot/turn on your device, press vol-down button while blue LED blink and choose recovery, then custom recovery. now you can install rom or cwm5.
Click to expand...
Click to collapse
Got into CWM5 finally via the bootmenu... the CWM5 .zip file that was linked to earlier by lulli1 is "CyanogenDefy Recovery v5.0.3.4-jordan" if that matters.
It's still not accepting the latest release of this ROM though (25.09.2013), keeps claiming the following:
...
E:Error in /sdcard/cm-10.2-20130925-UNOFFICIAL-milestone2.zip
(Status 0)
Installation aborted.
Obviously there's something wrong somewhere... has anyone else successfully installed latest version?
This is really starting to frustrate me...
Maybe I should attempt TWRP method?
Thanks for the pointer abut vol down during blue LED... that's what I had forgotten and why I kept seeing the stock recovery menu. :S
---------- Post added at 11:40 AM ---------- Previous post was at 11:16 AM ----------
Just verified the MD5 hash for the heck of it. File checks out OK.
Any ideas?
This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
Prerequisites
Code:
1. A Mako/Grouper
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[URL="http://forum.xda-developers.com/showthread.php?t=2678140"]http://forum.xda-developers.com/showthread.php?t=2678140[/URL]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Single script for both Nexus 4/ Nexus 7 ( 2012)
6. Error conditions at many places so a noob cant go wrong
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM
Instructions
Code:
1. Unpack the Zip file you downloaded from Link Below
2. Run F2FS Convertor.bat
3. Select your device
4.Place the Zip in the Extract /Input directory when prompted
5. The script will Unpack your ROM
6. Select option 11 for boot.img supplied with the script or option 12 for cm boot.img and 13 for any other F2FS compatible boot.img
7. Repack your ROM
8. Check NEW F2FS ROM directory for the Repacked ROM
9. Flash and Enjoy
10.Cleanup the working directory cleanup.bat
Download Links
1) English
2) German (Thanks to @mikaole)
Changelog
Code:
V1 : Initial Release
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Reserved
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
SkOrPn said:
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
All the best things, take time to come
SkOrPn said:
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Its just 3 weeks ago things started to build up for f2fs for mako !! I created this script primararily for my Mako dont own a grouper !! Took me two weeks to polish the script !! Basically wanted to make kernels compatible too but after trying hard had to give it up !!
Do I get this right: I can use this script to convert the latest CM 11 nightly to F2FS compatibility? And what if the kernel changes in the nightly? Has the included kernel the fixes for the recently changed ram disk?
NABENDU1 said:
Its just 3 weeks ago things started to build up for f2fs for mako !! I created this script primararily for my Mako dont own a grouper !! Took me two weeks to polish the script !! Basically wanted to make kernels compatible too but after trying hard had to give it up !!
Click to expand...
Click to collapse
I was just poking fun at ya, nothing rude was intended. I am very happy to see something like this take place. Now we have something to do the next time our favorite ROM gets released.
We just need about 100 more devices to get supported and this may take off with the manufacturers themselves. Then I will consider all smart devices up to that point one large 10 year long beta test. Lmao
Sent from my Nexus 7 using Tapatalk
So this won't work on the Galaxy Note II ...... wish it would lol
master.peterm said:
So this won't work on the Galaxy Note II ...... wish it would lol
Click to expand...
Click to collapse
If you can link me to its thread which can make it fully f2fs compatible I'll be more than glad to help !!
SkOrPn said:
I was just poking fun at ya, nothing rude was intended. I am very happy to see something like this take place. Now we have something to do the next time our favorite ROM gets released.
We just need about 100 more devices to get supported and this may take off with the manufacturers themselves. Then I will consider all smart devices up to that point one large 10 year long beta test. Lmao
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I had no hard feelings or stuff on you or anybody !! Just that wanted to inform you about why my script was released so late !! And ya that's exactly my intention to make flashing Roms easy !! I mean changing manually isnt always gr8 especially when you flash on a daily basis like I do
edisso10018 said:
Do I get this right: I can use this script to convert the latest CM 11 nightly to F2FS compatibility? And what if the kernel changes in the nightly? Has the included kernel the fixes for the recently changed ram disk?
Click to expand...
Click to collapse
No idea I don't own a grouper so I don't test it at all !! @USBhost gave this boot.img to me and I included it in my script !! I think he could explain this better
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Note this does not convert the kernel to f2fs you have to flash a custom All-F2FS kernel
Oh, I thought it did that? Can we please have that included into this script? Just put your favorite f2fs kernel into a folder and let it include it into your new f2fs rom? That would be nice...
SkOrPn said:
Oh, I thought it did that? Can we please have that included into this script? Just put your favorite f2fs kernel into a folder and let it include it into your new f2fs rom? That would be nice...
Click to expand...
Click to collapse
If I get some time, I may try to put together a bat file to do this. Should be able to just extract both zips, merge the kernel library modules into the system folders in the ROM zip, and replacing the boot image. The whole system folder gets extracted recursively so the kernel files go with it, and zip it back up. This program fixes the updater-script.
Sent from my SCH-I545 using Tapatalk
icarianecho said:
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Click to expand...
Click to collapse
Its not that you went wrong it's my script which is calling the wrong directories !! I had faced the same problem with my mako script in its early days but after changing a few things here and there it was gone !! Bdw I'll hook you up to a test script hopefully by today evening and I think you should be good to go
Edit : Others report it as working !! Might be you doing something wrong on your end ! Bdw you should extract all my folders in d F2FSROMCONVERTOR folder !! Name change or anything will effect the script to through errors
And ya the v3 test version is d same as the released version as far as I remember
NABENDU1 said:
Its not that you went wrong it's my script which is calling the wrong directories !! I had faced the same problem with my mako script in its early days but after changing a few things here and there it was gone !! Bdw I'll hook you up to a test script hopefully by today evening and I think you should be good to go
Click to expand...
Click to collapse
I tired a bit different method but was not working for me !! Tried android image kitchen to extract the boot.img made a compatible zImage of my kernel and copied the modied zImage to that of the unpacked boot.img from android image kitchen !! Then changed the fstab and repacked but the same still won't boot !!
If you can help me get this working with kernels I'll be much more happy
NABENDU1 said:
I tired a bit different method but was not working for me !! Tried android image kitchen to extract the boot.img made a compatible zImage of my kernel and copied the modied zImage to that of the unpacked boot.img from android image kitchen !! Then changed the fstab and repacked but the same still won't boot !!
If you can help me get this working with kernels I'll be much more happy
Click to expand...
Click to collapse
That's exactly what I tried
---------- Post added at 01:42 AM ---------- Previous post was at 01:32 AM ----------
I wonder if you just replaced the boot.IMG from the ROM with the kernel's boot.img
Would that boot
---------- Post added at 02:03 AM ---------- Previous post was at 01:42 AM ----------
It works!!! Cheer !!
Amazing tool lml
Enviado desde mi Nexus 7 mediante Tapatalk
Carbon ROM 4/24/2014 with the M-kernel
---------- Post added at 04:01 AM ---------- Previous post was at 03:29 AM ----------
icarianecho said:
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Click to expand...
Click to collapse
F2FSROMConvetorV3
this one works for me
I tried using this tool to build a omni verison and a cyanogenmod version, both the latest nightly. On each build I get the message " Type Password to Decrypt ..."
Also the recovery provided does not boot up after flashing it using fastboot. The recovery from http://forum.xda-developers.com/nexus-4/orig-development/recovery-rom-kernel-f2fs-05-04-14-t2706825 is working
joefso said:
I tried using this tool to build a omni verison and a cyanogenmod version, both the latest nightly. On each build I get the message " Type Password to Decrypt ..."
Also the recovery provided does not boot up after flashing it using fastboot. The recovery from http://forum.xda-developers.com/nexus-4/orig-development/recovery-rom-kernel-f2fs-05-04-14-t2706825 is working
Click to expand...
Click to collapse
You flashed a MAKO recovery onto your Grouper? I did not know that would work
EDIT: Never mind me, I see that you have a mako and trying to convert your Omni to it.
OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 7"
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848
CHECK KNOWN ISSUES BEFORE FLASHING. MAY NOT BE GOOD ENOUGH FOR DAILY USE.
Official nightly builds can be found here:
http://download.cyanogenmod.org/?device=tate
Download Google Apps for Android 5.1:
https://www.androidfilehost.com/?w=files&flid=25361
(Choose newest *-5.1-* file)
NOTES:
Older versions of TWRP will show a "mount failed error". This is safe to ignore.
First boot after a clean wipe will take a LONG time. Be patient.
KNOWN ISSUES:
Use XDA Bug Reporter
SCREEN SHOTS:
Use XDA Screenshots
XDA:DevDB Information
CM12.1 KFire HD 7 (LP 5.1.x), ROM for the Amazon 7" Kindle Fire HD
Contributors
Hashcode
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Beta Release Date: 2015-06-24
Created 2014-12-27
Last Updated 2015-06-24
Reserved
KERNEL UPDATES for Lollipop Android 5.0 / 5.1
Added F2FS support which can be turned on (with a full /data format) in a future release of TWRP
Combined defconfig setup to better support all HD models
Picked "Wakeup reason" patchset from Google's common 3.4 kernel (not fully implemented yet)
Picked IPV6 routing changes from Google's common 3.4 kernel
Reverted a hardcoded disable of Secure Discard and added the official upstream patch for Secure Discard support detection
Reserved
Android 5.1 / CM-12.1 changes:
SElinux Enforcing as default enabled
Woke up from my nap and saw this! Amazing!!! Downloading now
Edit: I would like to point out that there will be a mount failed error in TWRP when flashing the build. Ignore the error and be patient. It'll flash! It took about 2-3 minutes.
Edit2: And it has booted! Approx time is 8 minutes. Be patient on your first boot guys!
Very very thanks Hashcode you are awesome!
Always knew we could rely on the master. Flashing asap once downloaded.
Hashcode, I flash it and 5Ghz Wifi works for me
davigar said:
Hashcode, I flash it and 5Ghz Wifi works for me
Click to expand...
Click to collapse
Mines not. It's not detecting my 5Ghz network.
Can confirm the 7/8 minute 1st boot. Must be to do with initialising ART?!
Anyway, now for a play and a few customisations.
Once again, Thank you and hope you managed to find some time to enjoy Christmas!!
I just got 5Ghz to work. At least on mine. So since a lot of my android devices don't detect my 5Ghz I had to do some researching. Changing the 5Ghz channel from Automatic/Auto to 44 or 48 will make it work. Can confirm on my Nexus 4 and the Kindle. Works superbly!
Source
Glad to see you sorted out all of the issues quicker than any of the other developers could. We're not horrible, but there's no matching the talent that you have when it comes to this type of thing.
And we thought we were close ?. At least we learned a lot and more to come! Thanks Hash for putting your time and effort into this.
How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94
Everything seems to be working very nicely so far. Just flashed about an hour ago. Seems much smoother than kit kat did. Thank you very much. Looking forward to the updates.
Sent from my Amazon Tate
cell2011 said:
How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94
Click to expand...
Click to collapse
As the title of thread says, its in Alpha. But may I ask what FC's your'e getting? I'm running the build on my Kindle at the moment and the only FC I get is Bluetooth Sharing. Bluetooth was activated on the main user and when I switch to another user it FC's.
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
Should i reflash just rom and gapps and supersu after i boot up?
cell2011 said:
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
Should i reflash just rom and gapps and supersu after i boot up?
Click to expand...
Click to collapse
There's no need to flash SuperSU . SuperUser is built in already and working. Wipe System, Data, Cache, and Dalvik. Then flash the ROM and gAPPS.
---------- Post added at 04:43 AM ---------- Previous post was at 04:17 AM ----------
Is anyone else getting a bootloop when clicking on reboot? I have to fully power down to be able to make it boot. Also, I'm unable to tick unknown sources when on another user (using Multi-Acc). Don't worry, I'm not downloading pirated apps xD. I download the APK's over at the Android Apps and Games forum.
Awesome work man! Flashing now...
This is great! Thank you Hashcode!
When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)
Is this something to be worried about? It boots just fine.
Random Username said:
This is great! Thank you Hashcode!
When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)
Is this something to be worried about? It boots just fine.
My other problem is that I can't log in with my Google account? Is this maybe related?
Click to expand...
Click to collapse
I get the same error and google account works fine for me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To God be the glory, I finally finished a XA2 Ultra build of Resurrection Remix! It's Resurrection Remix, Pie flavored!
WARNING: This is for phones that are now using the 50.2 firmware base! There is still an old build for the 50.1 firmware base, but I recommend you upgrade to 50.2 firmware.
"We work to make your android experience elegant. Handpicked features beautifully packed into one ROM."
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
A huge thanks to the Resurrection Remix team!
Another huge thanks goes out to @LuK1337 for all of the great development that he does on the Sony Xperia XA2 Ultra! He did most of the heavy lifting by making a great LineageOS build, upon which this RR is based. Please note, this is an UNOFFICIAL ROM.
Disclaimer: Resurrection Remix is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make Resurrection Remix, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
This Unofficial Resurrection Remix Pie ROM was built for H3223 (discovery), but may work on some of the other variants, please try at your own risk. However, if you do try it on another variant, please be sure to let me know in the comments how it worked.
Downloads:
Rom Download link:
WARNING: This is only for those on firmware versions 50.2.xxxxxx, not for those who are on firmware versions 50.1.xxxx. I recommend everyone update to 50.2 firmware!
http://www.mediafire.com/folder/el24nm0l3m38y/50.2_based
WARNING: This is only for those on firmware versions 50.1.xxxxxx, not for those who are on firmware versions 50.2.xxxx and up. This old version is not updated, but works fine.
http://www.mediafire.com/folder/15nb0swbcqcxi/50.1_based
If there is an ENG and USERDEBUG build, the ENG build is marked "ENG" for testing purposes only. You can install anything you want, but I recommend not installing the ENG build.
Gapps link:
http://opengapps.org/
If desired. Personally, I've gone Gapp-less.
Installation instructions:
-Download ROM and gapps, and put them on your removable sdcard storage. (Or leave on your computer and flash with adb sideload.)
-Reboot into the bootloader.
-Fastboot boot your TWRP.
-Backup what you had. (Just to be safe.)
-Wipe everything and format data.
-Install Rom. (Either from adb sideload or from your removable sdcard storage.)
!!!IF YOU GET AN ERROR, MAKE SURE YOU ARE USING THE LATEST TWRP!!!
-Reboot to system and enjoy!
If you also want Gapps:
-Reboot again into the bootloader.
-Fastboot boot your TWRP.
-Install Gapps. - Optional
If you plan to install magisk (good idea), then let the rom boot the first time, then go back to TWRP and flash magisk. This is optional, of course.
What works:
Code:
So far everything that I have tried works, such as
- Camera for pictures and video!
- Phone calls
- Data 3g/LTE
- Bluetooth
- WiFi
- MTP
- FM Radio
etc....
What doesn't:
Code:
- Nothing else that I know of, but if you find something, please let me know so we can try to fix it!
Source Code:
https://github.com/ResurrectionRemix
Official website:
http://www.resurrectionremix.com/
My device trees, vendor blobs, and kernel source:
https://gitlab.com/alaskalinuxuser/android_device_sony_discovery
ROM OS Version: 9.0 Pie
RR version: 7.0.2
ROM Kernel: Linux 4.4.153
Based On: The best of every ROM, but particularly based on LineageOS.
Created 2019-08-16
Last Updated 2019-11-04
Change log:
2019-08-17
RR accepted my commit:
https://github.com/ResurrectionRemi...mmit/db98cc9253b8680005b90122c48b40f633dc04e5
2019-08-16
-7.0.2 stable ENG and USERDEBUG build.
Had to edit a lot of whitelist permissions issues in RR itself to make this work. I created pull requests with RR, but if they don't add them, it makes repo sync difficult as I will have to make my edits all over again.
Rom notes:
As @Ultramanoid pointed out in LineageOS https://forum.xda-developers.com/showpost.php?p=80053444&postcount=219 You can use Open Camera to allow you to switch between all three cameras (one rear, two front).
Want to build your own custom kernels, custom roms, or learn the ins and outs of development? You can check out my video tutorials with over 24 hours of video and explanations here:
https://forum.xda-developers.com/android/general/guide-how-to-build-custom-roms-kernel-t3814251
Thanks given! Thank you so much man! Don't get me wrong I love Lineage but I was ready for some more rom love ?
Question though, I'm on the latest nightly of lineage, can I wipe and drop this gem on it with success?
appleknight said:
Thanks given! Thank you so much man! Don't get me wrong I love Lineage but I was ready for some more rom love ?
Click to expand...
Click to collapse
Yeah, I think @LuK1337 and the LineageOS team does a great job. I just like having a little variety, myself.
appleknight said:
Question though, I'm on the latest nightly of lineage, can I wipe and drop this gem on it with success?
Click to expand...
Click to collapse
You sure can, because that's what I just did. However, you may have to wipe and format data. :good:
Loving the rom keep up the good work? everything works but SD cards which was the same on lineage. Other than that this rom has the rr customization and is smooth like butter!
No issues here!
Yodasgodfather said:
Loving the rom keep up the good work everything works but SD cards which was the same on lineage. Other than that this rom has the rr customization and is smooth like butter!
Click to expand...
Click to collapse
appleknight said:
No issues here!
Click to expand...
Click to collapse
Great! Thanks guys! I used to build roms all the time, back before Oreo, but I took a break for a while and I'm trying to get back into the swing of things. I'll try to chase down that sdcard issue, I didn't have one in the phone to test it.
My usual MO is to build Lineage (already done by LuK1337), RR, AOKP, and SlimRoms (I don't think Slim has a working Pie at the moment), then move on to custom kernel work. We'll see what we can get done here. I also have two of these phones, so I'm hoping to finish building these roms, then update the phone to 50.2 firmware and update the device trees, kernel, and blobs to match and see if we can update the roms for the latest firmware. I can only image that @LuK1337 already tried this, so there must be some hangup in doing so, but we'll see what we can do. No promises, since I'm not the most skilled dev, but that's the overall plan.
Yodasgodfather said:
Loving the rom keep up the good work everything works but SD cards which was the same on lineage. Other than that this rom has the rr customization and is smooth like butter!
Click to expand...
Click to collapse
I just tested my sdcard, and it came right up. I could access the files and I started watching a video from there. What specifically doesn't work for you when you use an sdcard so I can troubleshoot that?
Oh? Well then what am I doing wrong cause for some reason the phone will freeze on setup unless I remove it? I dirty flash and follow the steps mentioned above? Perhaps is their a certain format aosp or certain Roms prefer like exfat or fat32... Etc
Yodasgodfather said:
Oh? Well then what am I doing wrong cause for some reason the phone will freeze on setup unless I remove it? I dirty flash and follow the steps mentioned above? Perhaps is their a certain format aosp or certain Roms prefer like exfat or fat32... Etc
Click to expand...
Click to collapse
Thanks for the info. So a few thoughts and questions, so we can get to the bottom of the issue:
Thought - I highly discourage dirty flashing. You never know what is left over from the last ROM. It makes trouble shooting very difficult.
Question - does it work without flashing gapps or magisk, just when you flash only the ROM? (This works for me here, just a clean install with only the ROM. I don't use gapps anymore, so that may matter.)
Question - if you do flash gapps or not, does it work if you boot the phone without it for the first boot, then power down and put it in for future use? E.g., does it work on subsequent boots, after setup is complete?
Question - what firmware are you running? And what phone variant?
Thanks, these things will help. Also, a huge help is pulling logs with logcat, so I can see the errors about the sdcard.
Question for the group: is anyone else successful in using the sdcard?
Just as a side note, I tried using the lineage addonsu zip(since this is lineage based). It definitely adds root to the developer options menu, but does nothing when an app tries to gain root( no dialog, toast etc..) just in case anyone wanted to know. So I went with magisk ?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
AlaskaLinuxUser said:
Thanks for the info. So a few thoughts and questions, so we can get to the bottom of the issue:
Thought - I highly discourage dirty flashing. You never know what is left over from the last ROM. It makes trouble shooting very difficult.
Question - does it work without flashing gapps or magisk, just when you flash only the ROM? (This works for me here, just a clean install with only the ROM. I don't use gapps anymore, so that may matter.)
Question - if you do flash gapps or not, does it work if you boot the phone without it for the first boot, then power down and put it in for future use? E.g., does it work on subsequent boots, after setup is complete?
Question - what firmware are you running? And what phone variant?
Thanks, these things will help. Also, a huge help is pulling logs with logcat, so I can see the errors about the sdcard.
Question for the group: is anyone else successful in using the sdcard?
Click to expand...
Click to collapse
No issues with sdcard here! H3223
---------- Post added at 06:26 PM ---------- Previous post was at 06:20 PM ----------
Question: is there a hide navbar setting? If so I missed it so I'm using an app called custom navigation bar, which I've had to use in the past, tho for some reason on this rom it's sometimes difficult to get to appear when you swipe up from the bottom, any ideas?
---------- Post added at 06:37 PM ---------- Previous post was at 06:26 PM ----------
AlaskaLinuxUser said:
Great! Thanks guys! I used to build roms all the time, back before Oreo, but I took a break for a while and I'm trying to get back into the swing of things. I'll try to chase down that sdcard issue, I didn't have one in the phone to test it.
My usual MO is to build Lineage (already done by LuK1337), RR, AOKP, and SlimRoms (I don't think Slim has a working Pie at the moment), then move on to custom kernel work. We'll see what we can get done here. I also have two of these phones, so I'm hoping to finish building these roms, then update the phone to 50.2 firmware and update the device trees, kernel, and blobs to match and see if we can update the roms for the latest firmware. I can only image that @LuK1337 already tried this, so there must be some hangup in doing so, but we'll see what we can do. No promises, since I'm not the most skilled dev, but that's the overall plan.
Click to expand...
Click to collapse
Would definitely love to see some slim love ? I developed for the z ultra back in the day. I never have the spare time anymore, full time parent n all
appleknight said:
Just as a side note, I tried using the lineage addonsu zip(since this is lineage based). It definitely adds root to the developer options menu, but does nothing when an app tries to gain root( no dialog, toast etc..) just in case anyone wanted to know. So I went with magisk
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
No issues with sdcard here! H3223
---------- Post added at 06:26 PM ---------- Previous post was at 06:20 PM ----------
Question: is there a hide navbar setting? If so I missed it so I'm using an app called custom navigation bar, which I've had to use in the past, tho for some reason on this rom it's sometimes difficult to get to appear when you swipe up from the bottom, any ideas?
---------- Post added at 06:37 PM ---------- Previous post was at 06:26 PM ----------
Would definitely love to see some slim love ? I developed for the z ultra back in the day. I never have the spare time anymore, full time parent n all
Click to expand...
Click to collapse
Hear you there, I've got three and one in the oven! Kids are great, but they'll keep you busy!
As for the Nav bar, go to settings, RR tools, navigation, navigation, enable nav bar. :good:
There are several options as well, fling, standard, edited, etc. You'd have to play with them to get it all sorted out how you like it.
Congrats man! I meant to autohide the navbar, I don't see an option for it.
It doesn't I'm not able to access it. Doesn't matter if I flash gapps or not the phone will not boot properly with the SD card in and it works fine on stock. It was the same issue on lineage os. The setup will be stuck in a loop say its searching for networks and eventually crash the system. When I inserted it just now it kept saying "phone is starting" and just crashed. Should I try formatting the SD card? I have xa2 ultra h3223 just in case your wondering...
appleknight said:
Congrats man! I meant to autohide the navbar, I don't see an option for it.
Click to expand...
Click to collapse
Thanks! Sorry I didn't understand your request. Yes, the "expanded desktop" option will auto hide the status bar and/or the navbar per your preferences. Settings, display, advanced, expanded desktop. A swipe up brings the bar back. :good:
Yodasgodfather said:
It doesn't I'm not able to access it. Doesn't matter if I flash gapps or not the phone will not boot properly with the SD card in and it works fine on stock. It was the same issue on lineage os. The setup will be stuck in a loop say its searching for networks and eventually crash the system. When I inserted it just now it kept saying "phone is starting" and just crashed. Should I try formatting the SD card? I have xa2 ultra h3223 just in case your wondering...
Click to expand...
Click to collapse
I think formatting the card would be wise. If you used it as "built in" storage before, instead of for transferring files (the initial question it asks when you first put one in) you can run into trouble with it on other ROMs or phones. I have the same phone, and it is working for me and for appleknight, so it must be something with your phone or card. Let me know if formatting helps. :good:
Ah that works, still for some reason though I have to swipe a few times to get it to appear, almost seems like the sensitivity is off or something it's weird
---------- Post added at 12:26 AM ---------- Previous post was at 12:08 AM ----------
So do you think the RR team will make this an official build? ?
appleknight said:
[/COLOR]So do you think the RR team will make this an official build?
Click to expand...
Click to collapse
Not likely.... They'd need a device maintainer. You know, some skilled dev to keep things working and running smooth. As far as I know, LuK is too busy. :silly:
So far I really like this as my daily driver