Develop Bugs

CM 11 4.4 kitkat issue

I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?

mr. ya-di-da said:
I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?
Click to expand...
Click to collapse
Flash it from cwm... but after the flash completes, reboot recovery and do you're wipes ( again ) and flash kitkat from it's recovery. Then reboot.
Let it chill for a few minutes, then boot back to recovery and flash you're 4.4 gapps.
This process always worked for me on 4.3 and I'm assuming it will work on 4.4. But I've not flashed 4.4 yet. So proceed with caution.
Good luck...

I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?

mr. ya-di-da said:
I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?
Click to expand...
Click to collapse
I'm not sure about the mobile Odin issue... are you making sure the tar file for the kernel is a good download and that it is compatible with the Android version and rom you're trying to run...?
Try downloading the Directboot EL29 kernel from rwilco12's repo.. ( make sure you get the Directboot EL29 kernel and not the stock el29 kernel )
After you have it and the rom you want on you're sdcard... use mobile Odin to flash the el29 db kernel.. it should boot to recovery on it's own..
Push volume up, volume down, volume up... this enables the power button as the select button...
Do you're wipes... and flash 4.4...reboot recovery... do wipes.. ( data, cache, dalvik, and format system )...flash 4.4 again.. reboot.. settle in for a few minutes and then boot recovery and flash gapps 4.4...reboot.
Let me know how it goes... I'll stick around tonight until we get ya up and running...

It failed.. (status 7)

mr. ya-di-da said:
It failed.. (status 7)
Click to expand...
Click to collapse
Ok... I'll try to get to it tomorrow... but Thursday at the latest.

OK thx. I saw that other people where getting the same fail (status 7) let me know what u find.

Status 7 is a syntax error in the updater script... Probably missing a semicolon or something silly like that.
{
"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"
}

Not related to this issue, unsure if it would be better etiquette to make my own thread for this, but an issue I'm having with dastins CM11 ROM (12-04-13 version) is that I have two "Internal Storages" instead of one (I do not own/use a SD card)
On CM10/10.1/10.2 I had one internal storage, but on CM11 I have a 2GB internal storage and then a second internal storage (that things seem to not be installed to at all) with the remainder of my devices space.
One of the applications I used a lot on stock TouchWiz and earlier versions of CM is larger than two gigs, so on CM11 I can't even install it because it says I have insufficient storage. Is there a way I can combine the two internal storages into one, so it functions like it did on CM10.2 so I can use all of my devices space instead of only 2GB?
---------
Another question, and this one I'm probably just being blind and not seeing it, or maybe this setting is in a different location in KitKat, is my phone is set to USB mass storage instead of MTP. Normally I head over to Settings > Storage > hit the menu key and change USB connection type to MTP, but the menu key doesn't seem to do anything anymore on the Storage page. Where would I change to MTP instead of Mass Storage, or how can I just disable Mass Storage, I honestly don't care about being able to get any files on/off the device, but 90% of the time I'm charging on USB and I just don't want a full screen prompt showing up every time I touch my phone saying "Hey! It's Plugged In! Do you want to turn USB Storage on?"

You need to flash cm11 with the newest cwm... The old regular way of the"safe" recovery doesnt work... The easy way Is to download the blasphemy kernel and install it then boot back into recovery... It will be cwm 6.0.4.5... Flash the rom with this and no status 7...
Hope this helps...
Sent from my SPH-D710 using Tapatalk 2

I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.

kitkat 4.4.1
I rooted my device using rwilcos fl24 method although I was on a fd24 model. After root I flashed a custom recovery using Odin I believe it was agats...I then proceeded to flash a ROM cm10.1 then upgraded to cm 10.2. Now running KitKat 4.4.1 12/7 edition I believe and works like a charm...thought I had a battery problem because it wouldn't charge right it would take forever. I didn't I jus had to stop oc/uv ...BTW using the kernel that came with the rom flashed using cwm recovery from cm10 which was on jb not ICS and works fine little bugs here and there such as attempting to open incognito window fc browser the battery read when phone was off was inconsistent versus when the device is off but other then that KitKat is great if I can help anyone I'll be more then glad to I don't mind helping people that don't know I don't give attitude and noon user friendly,after all I was there once....besides all the guys who really know what thier doing are busy creating Roma and tweakimg programs to keep us happy let's make it a little easier on them like I said I don't know everything but I have some knowledge and if I'm able to point you in the right direction without wasting your time I will

easyrider77 said:
I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.
Click to expand...
Click to collapse
There's a tread that might use your assistance
Sent from my d710 using XDA Premium 4 mobile app

CM 4.4.1 build 2013-12-07
Hey guys...Been rocking this build for a month now with no real problems. Only a couple of things i have noticed and thought I would drop in and mention since I haven't heard about it talked about in the main thread or here yet.
1. Every once in a while I will be showing full 3g bars and wont connect to the internet (says "no connection") I have fixed this with just toggling off and then back on the Sprint Radio Toggle in the drop down window. The phone will then immediately connect after.
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
SPH-D710 EL26.....flashed to Boost Mobile with working Hangouts MMS and SMS from day one (no fix)
Build; 4.4.1 2013/12/07
Everything else is just ROCK SOLID, and love this ROM.

adjday said:
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
Click to expand...
Click to collapse
This Camera Fix worked to get my camcorder working perfectly. Have you tried it? http://forum.xda-developers.com/showthread.php?p=48620791&highlight=3a04f599232ee62c6b63a6e4f1d3f7d3#post48620791

You can uninstall the gallery app (using titanium backup)
Then download and install a different Kit Kat gallery app...(just search google, it's everywhere Lol)

[d710][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy S2 Epic 4G Touch - SPH-D710 (d710)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse

Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
First off let me say thank you for bringing this amazing recovery to our phone I just flashed it and everything seems good so far,,i'll let you no if i run into any issues
Well using this recovery on mokee the rom will not boot just goes to a black screen so i guess it has to be built with the mokee stuff if you can give me the issues your having i can get it to work,,unless you can give me the source or let me know how to get it and i can make a build using the mokee trees

Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
Does this work for touch wiz?

It is only for CM based ROMs under KitKat
AOKP ROMS could or could not load
TW will not
For non working roms, you just have to ask someone to repack it with matching kernel zImage

This recovery is pretty awesome, flashed CM11, Vanir, & Commotio successfully.
My new default recovery. :]

HighxVoltage said:
This recovery is pretty awesome, flashed CM11, Vanir, & Commotio successfully.
My new default recovery. :]
Click to expand...
Click to collapse
What was your install method ? I'd like to try it . Did you just flash it with the cwm you already had ? Next question . After you install it and when you flash another rom does it get over written or can you reinject it each time ? thanks

SuperGoober said:
What was your install method ? I'd like to try it . Did you just flash it with the cwm you already had ? Next question . After you install it and when you flash another rom does it get over written or can you reinject it each time ? thanks
Click to expand...
Click to collapse
Yes. & it does get overwritten, I just flash it after flashing the ROM / Gapps. No biggie though. Haven't found an option to make it stick after flashing a ROM like in TWRP.
Sent from my SPH-D710 using Tapatalk

HighxVoltage said:
Yes. & it does get overwritten, I just flash it after flashing the ROM / Gapps. No biggie though. Haven't found an option to make it stick after flashing a ROM like in TWRP.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I seem to be in a vicious cycle . Recovery flashes fine . When i reboot screen goes black after splash screen . Go back into recovery have to reflash rom but then reflash this and back to black screen on reboot . I don't get what the advantage is if you can't stick it and be able to boot . It would be great if it would stick and boot .

Phil3759 said:
It is only for CM based ROMs under KitKat
AOKP ROMS could or could not load
TW will not
For non working roms, you just have to ask someone to repack it with matching kernel zImage
Click to expand...
Click to collapse
Can you build the recovery using this kernel and vendor files because when CM made there graphics update it caused video issues on our device this kernel and vendor revert that update
https://github.com/mtb3000gt/android_kernel_samsung_d710
https://github.com/mtb3000gt/android_vendor_samsung_d710
https://github.com/mtb3000gt/android_vendor_samsung_d710-common

mtb3000gt said:
Can you build the recovery using this kernel and vendor files because when CM made there graphics update it caused video issues on our device this kernel and vendor revert that update
https://github.com/mtb3000gt/android_kernel_samsung_d710
https://github.com/mtb3000gt/android_vendor_samsung_d710
https://github.com/mtb3000gt/android_vendor_samsung_d710-common
Click to expand...
Click to collapse
yes, but please, no need to post multiple times
once is enough

do i go to recovery and flash this? i am on android 2.3.6, the current recovery only has 3 menu items to do (flash, wipe and wipe)
my goal is to flash the lastest 4.4.3 rom

When I try to flash philz_touch_6.19.3-d710.tar.md5 with Mobile Odin, I get the error "partition could not be found in file". I've done a hash check on the file.

unknownsoldierx said:
When I try to flash philz_touch_6.19.3-d710.tar.md5 with Mobile Odin, I get the error "partition could not be found in file". I've done a hash check on the file.
Click to expand...
Click to collapse
Did you ever get the right file? If not, let me know. I tried to flash it through Mobile Odin and it dosen't even see the files. The best bet is to boot into recovery, flash Philz, reboot into recovery, flash until tired.

Never did get philz_touch_6.19.3-d710.tar.md5 to work. The zip version flashed fine from StockCWM-EL26. I was hoping to get the tar.md5 to work so I could skip StockCWM-EL26.
Then I learned Philz doesn't work properly for nandroids, Since I need to use StockCWM-EL26 for nandroids anyway, the tar.md5 version of Philz is not needed.

unknownsoldierx said:
Never did get philz_touch_6.19.3-d710.tar.md5 to work. The zip version flashed fine from StockCWM-EL26. I was hoping to get the tar.md5 to work so I could skip StockCWM-EL26.
Then I learned Philz doesn't work properly for nandroids, Since I need to use StockCWM-EL26 for nandroids anyway, the tar.md5 version of Philz is not needed.
Click to expand...
Click to collapse
OK. If your on stock, that should be TouchWiz. I would try to install AGAT's as a regular recovery. All the TW ROMs I flashed, had AGATs already installed. The only time I had to use EL26 or EL29 was to go to a different ROM. Have you tried his repository?
here ya go.
http://www.rwilco12.com/downloads.p... (SPH-D710VMUB)/Kernels/Stock (TW) Kernels/JB

CWM-EL26 has worked fine for me, so I haven't used Agat's, Doesn't matter since I don't keep anything installed. I flash a recovery, flash a rom, to see if things are working well enough to use. After not being able to get text or mms to work reliably, I go back to stock completely. GB28 everything.
If there was a custom recovery with a GB28 kernel, I'd keep that installed.

unknownsoldierx said:
CWM-EL26 has worked fine for me, so I haven't used Agat's, Doesn't matter since I don't keep anything installed. I flash a recovery, flash a rom, to see if things are working well enough to use. After not being able to get text or mms to work reliably, I go back to stock completely. GB28 everything.
If there was a custom recovery with a GB28 kernel, I'd keep that installed.
Click to expand...
Click to collapse
Like these?
GB27 will work flawlessly on Virgin and Boost models

Still having a ton of problems with this recovery. It's the only one I can find that will flash the Liquid Smooth rom for me.
The backup/restore seems to be completely broken. Others have said to use another recovery for that. So I flash a recovery, reboot to that, then flash Philz, then flash KK rom.
Today I flashed Liquid Smooth, had some problems with it so decide to restore a backup. I booted into Philz, used it's convenient "wipe for new rom" to make sure everything was clean for restore. Then I needed to flash the recovery I used to make my backup, but when I tried to do that I just got an error 7. I tried flashing different recoveries, roms, modems. All gave errors.
Saw a tip suggesting to untick the "Don't allow old update-binary " option, but that didn't fix it.
Had to hook it up to the computer and flash a recovery using odin.

This
Phil3759 said:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
download link doesn't work any more.
Can anybody please provide me with an alternative download link?
Thanks!

I found working versions for the SPH-D710 here
I just flashed CM11 with the philz_touch_6.19.3-d710.zip and it worked just fine (I think the lower version did not work ...).

[INFO] Recoveries for the Samsung Galaxy Ace II X

Work in Progress
List of Custom Recoveries for the Samsung Galaxy Ace II X
For all things rooting and installing, a custom recovery is often needed. New things are being developed day and night. Thus, I find it necessary for there to be a list of all the recoveries that are compatible with the Samsung Galaxy Ace II X. Some are better than others, though it is a matter of preference. Anyways, commencing the list...
1. ClockworkMod 5.5.0.4 - not my work
ClockworkMod recovery, usually abbreviated as CWM or CWMR, is a custom recovery based off of AOSP source, created by Koushik Dutta (known by the nickname "Koush").
Bugs - Mount USB doesn't work.
Download
2. ClockworkMod 6 - not my work
Bugs - Mount USB doesn't work, "dancing screen," SOME USERS REPORT THAT INSTALLING CWM6 CAUSES THE DEVICE TO BOOT INTO RECOVERY INSTEAD OF THE ROM
Download
3. TeamWin Recovery Project 2.6.3.0 - my work
TeamWin Recovery Project, often abbreviated as TWRP, is a custom recovery that has a fully touch-driven interface. Aside from the uniquity of being 100% touch controlled, it also contains an ubiquity of features. It has a built-in file manager, support for sideloading via ADB, support for backups and restoring backups, a completely theme-able interface, and more sorts of customization.
Bugs - Mount USB doesn't work.
Download
Changelog:
Release 2 - backported some features from TWRP 2.7, fixed color tint issue, implemented internal storage
Release 1 - initial release
4. TeamWin Recovery Project 2.7.1.0 - my work
Download
Bugs - None reported.
{
"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"
}
Changelog:
Release 4 - Upgraded to 2.7.1.0 (customized to build on a JB-based tree: removed mouse support via USB OTG, removed text wrap for now), fixed internal storage
Release 3 - Fixed color tint issue
Release 2 - Fixed USB Mass Storage
Release 1 - Initial release *TWRP 2.7.1.0 has some mount issues. Don't use it.
5. TeamWin Recovery Project 2.8.1.1 - by @draekko
Check his post here for details and download links.
This list will be updated regularly as recoveries are updated, new recoveries are built, or for miscellaneous reasons. If there are any bugs I haven't mentioned for any of the recoveries, let me know and I'll add it to the OP.

Nice thread.
keep up the good work.

Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app

CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:

Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
AndroidAssassin said:
Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
Seb269 said:
CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:
Click to expand...
Click to collapse
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?

Codename13 said:
Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?
Click to expand...
Click to collapse
They are the same.

Bug report (TWRP 2.7.0.0)
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.

gregory678 said:
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.
Click to expand...
Click to collapse
The latest release? I have no such problem. TWRP is configured so that the settings are stored on the external sdcard. So if you don't have one, your settings won't be saved. I considered setting the cache partition as the TWRP settings storage, but cache is often wiped when installing ROMs and packages. The same with system, data, et cetera. I've considered setting the recovery partition as a settings storage partition; however, whenever a new build of TWRP is installed, the recovery partition will be overwritten. I could try splitting the cache partition up so there is the cache partition and a new 12mb partition, but then there would either be errors when installing firmwares via Odin, or the new settings storage partition would be wiped. Unless you have any better ideas than the sdcard being the settings storage, don't complain. I'm not sure what's causing your issue - perhaps it's because you only insert your sdcard when you boot into TWRP? Enlighten me, and tell me a bit about your device setup (ROM, kernel, size of sdcard, etc).

OMG, I'm such dumb, I just noticed that settings file is hidden. I was wondering why it's always left empty folder after rebooting from recovery mode, now I discovered a hidden settings file in it, I'm Scherlock of the year . Sorry for bothering you, can someone delete these ashaming posts?

Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?

I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Jeremicus said:
Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?
Click to expand...
Click to collapse
Delete /system/etc/install-recovery.sh then try installing a recovery again and booting into it.

Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk

I was thinking about the advantages of TWRP 2.7 over 2.6. I knew that if I looked in the commit history for 2.7 on Github, I would be bound to find the commits that brought in some of my favorite features of TWRP 2.7.0.0. That, along with I having just discovered that Github commits can be download as patches, will bring the best version of TWRP for us yet. So far, I've successfully backported haptic feedback (along with the settings for it) and a bit more. I've also fixed internal storage in TWRP. I plan to backport the smoother scrolling, USB Mass Storage (it only works in 2.7 at the moment because 2.7 added in a different way to handle and mount UMS. I'll backport the different way of handling and mounting UMS), and add in some other bits of fun. It's going to be really cool, and it really isn't time consuming, so I should be able to bring it to you all very soon.
AndroidAssassin said:
Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk
Click to expand...
Click to collapse
Just download Recovery Tools from the Play Store.

It dont have nething for ace2x
Sent from my GT-S7560M using XDA Premium 4 mobile app

Codename13 said:
I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Click to expand...
Click to collapse
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:

husokal said:
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:
Click to expand...
Click to collapse
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.

Codename13 said:
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.
Click to expand...
Click to collapse
Im sorry i dont know much things about SELinux
As i see 2.7.0.0 Forces SELinux which i dont know what can be problem about it.
and 2.6.3.0 Mount Storage not working.
So im using 2.7.0.0 for my stock. Cause i need this function sometimes.
Sorry for noob question but what can be problem about Enforcing SELinux for 4.0.4
Edit:
Got it! : http://forum.xda-developers.com/showpost.php?p=52013947&postcount=5392

There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.

s7560m said:
There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.
Click to expand...
Click to collapse
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
EDIT - It seems that there's also a new version of TWRP out. It seems to be quite minor, but I'll see if I can port it. It's been bumped up to version 2.7.1.0 now.

Codename13 said:
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
Click to expand...
Click to collapse
Definitely twrp is the best! Never had any issues with it whatsoever, and has a great ui. If you could though, it would be awesome to try and port philz touch and cwm touch as well, just in case those who like cwm want that touch feature, or like the theme and features of philz touch . And I really hope the usb mounting issue can be fixed, as it can save so much time, rather than downloading to my computer, transferring to phone external storage, and then booting into recovery. Those who are lazy don't want to do all of that lol. Anyways, keep up all of the good work, and hopefully these bug fixes and new recoveries are implemented in future notice!

Need help flashing cutom rom

Hey guys so i've had a rooted note 2014 for awhile now and want to get into custom roms. I'm on stock 4.4.2 and i'm trying to flash liquidsmooth but have a couple of questions. So on the installation guide it says
"First time installing LiquidSmooth to your Samsung Samsung Note 10.1 (2014), or coming from another ROM:
- Make sure you're running latest Recovery
- Copy GApps zip, SuperUser zip and Liquid ZIP to your internal SDCard
- Boot into Recovery
- Flash Liquid zip from internal SDCard
- Flash GApps zip from internal SDCard
- Reboot
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!"
It seems simple enough but how do I know if i'm running the latest recovery? Also is there any other things I need to do or know before I attempt this?

Dachank said:
Hey guys so i've had a rooted note 2014 for awhile now and want to get into custom roms. I'm on stock 4.4.2 and i'm trying to flash liquidsmooth but have a couple of questions. So on the installation guide it says
"First time installing LiquidSmooth to your Samsung Samsung Note 10.1 (2014), or coming from another ROM:
- Make sure you're running latest Recovery
- Copy GApps zip, SuperUser zip and Liquid ZIP to your internal SDCard
- Boot into Recovery
- Flash Liquid zip from internal SDCard
- Flash GApps zip from internal SDCard
- Reboot
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!"
It seems simple enough but how do I know if i'm running the latest recovery? Also is there any other things I need to do or know before I attempt this?
Click to expand...
Click to collapse
Hi. Did you flash TWRP? I rooted then used flashify to install TWRP 2.8.5.0. I have had success using TWRP 2.8.5.0 but for some people issues this version and the have to use 2.6.3.1.
LiquidSmooth maintainer for d2usc/vzw & p600

Orion116 said:
Hi. Did you flash TWRP? I rooted then used flashify to install TWRP 2.8.5.0. I have had success using TWRP 2.8.5.0 but for some people issues this version and the have to use 2.6.3.1.
LiquidSmooth maintainer for d2usc/vzw & p600
Click to expand...
Click to collapse
I actually just went ahead and put 2.8.6.0 on there with odin and flashed your rom and it worked out alright. Do you happen to know what problems people were having with 2.8.5.0? Great ROM btw

Dachank said:
I actually just went ahead and put 2.8.6.0 on there with odin and flashed your rom and it worked out alright. Do you happen to know what problems people were having with 2.8.5.0? Great ROM btw
Click to expand...
Click to collapse
Wiping data and cache mainly. And thank you.
LiquidSmooth maintainer for d2usc/vzw & p600

Roms, Updates, Anything

SO, Is there ever going to be any custom roms or anything of the sort?? I check the site at least 2-3 times a week and nothing seems to ever change. Is this phone dead to the modders now??

Dirty unicorns said they are adding weeklies for the Z2 force starting the 6th. That's all I've heard other than the unofficial build of lineage os

AOSiP has an official build on their site. I'll get a thread going in a bit for detailed install instructions. The ROMs still aren't stable enough for official status. Gapps need to be baked in until they fix that, LTE still doesn't work for sprint. Video recording has no audio, VoIP traffic stutters... There are too many issues to release a "stable" build.

Edit:
Can the AoSip be installed from TWRP just as any other. There is also a kernel (Elemental Kernel in the nash download page.)Must this be used or can we still use pantheon. Can this not be installed from twrp as a regular rom? Boot twrp, Flash Rom, Flash Gapps, Flash Kernel, Reboot??? I am so ready for this. I did lots of rom porting, bug fixing on my old device. I feel if I can get in I can be some help.

Due to my impatience went ahead and tried to flash the latest AOSiP official from 3/28 Apparently I missed something because I am stuck at the boot animation. Here was my process exacly.
Pre Flash.
I was running the Tmo 8.0 27.1 December Security Patch. Pantheon Kernel. Twrp 3.2.1.1 on device.
Booted to twrp on device. Wipe Cache/Data/System. Flashed AOSiP 3/28/2018.zip . Elemental boot image. Reflash Twrp to device. Reboot to twrp. Flash OpenGapps 8.1 . Reboot to system.
Stuck at boot animation.
Apparently Im missing a step or doing things out of a particular order. Because I get no further than the boot animation.
Edit: After Playing with it a bit and wiping data and reinstalling gapps i get to a welcome screen with "google services has stopped" and bootloop repeatedly to that point. Wrong Gapps perhaps?

mr.duck254 said:
Due to my impatience went ahead and tried to flash the latest AOSiP official from 3/28 Apparently I missed something because I am stuck at the boot animation. Here was my process exacly.
Pre Flash.
I was running the Tmo 8.0 27.1 December Security Patch. Pantheon Kernel. Twrp 3.2.1.1 on device.
Booted to twrp on device. Wipe Cache/Data/System. Flashed AOSiP 3/28/2018.zip . Elemental boot image. Reflash Twrp to device. Reboot to twrp. Flash OpenGapps 8.1 . Reboot to system.
Stuck at boot animation.
Apparently Im missing a step or doing things out of a particular order. Because I get no further than the boot animation.
Edit: After Playing with it a bit and wiping data and reinstalling gapps i get to a welcome screen with "google services has stopped" and bootloop repeatedly to that point. Wrong Gapps perhaps?
Click to expand...
Click to collapse
Have you tried wiping the dalvik cache?

41rw4lk said:
Have you tried wiping the dalvik cache?
Click to expand...
Click to collapse
I am wiping it prior to flashing anything. Should I do it at another point also?

mr.duck254 said:
I am wiping it prior to flashing anything. Should I do it at another point also?
Click to expand...
Click to collapse
I usually wipe the dalvik cache after I flash an upgrade or anything major, that way I'm booting into a cleaner slate.

mr.duck254 said:
Due to my impatience went ahead and tried to flash the latest AOSiP official from 3/28 Apparently I missed something because I am stuck at the boot animation. Here was my process exacly.
Pre Flash.
I was running the Tmo 8.0 27.1 December Security Patch. Pantheon Kernel. Twrp 3.2.1.1 on device.
Booted to twrp on device. Wipe Cache/Data/System. Flashed AOSiP 3/28/2018.zip . Elemental boot image. Reflash Twrp to device. Reboot to twrp. Flash OpenGapps 8.1 . Reboot to system.
Stuck at boot animation.
Apparently Im missing a step or doing things out of a particular order. Because I get no further than the boot animation.
Edit: After Playing with it a bit and wiping data and reinstalling gapps i get to a welcome screen with "google services has stopped" and bootloop repeatedly to that point. Wrong Gapps perhaps?
Click to expand...
Click to collapse
try it without flashing gapps

mr.duck254 said:
I am wiping it prior to flashing anything. Should I do it at another point also?
Click to expand...
Click to collapse
Don't flash gapps for one. After a flash to any AOSP based ROM, you need to boot back into bootloader "AFTER" the flash and do a "fastboot -w" this will wipe your whole internal SD but is needed to avoid any idiosyncrasies between how the 8.1 AOSP ROMs handle data over stock.

Uzephi said:
Don't flash gapps for one. After a flash to any AOSP based ROM, you need to boot back into bootloader "AFTER" the flash and do a "fastboot -w" this will wipe your whole internal SD but is needed to avoid any idiosyncrasies between how the 8.1 AOSP ROMs handle data over stock.
Click to expand...
Click to collapse
I will try these when I get home from work. So just to clarify.
Twrp->wipe->rom->kernel->reboot to fastboot->fastboot -w from fastboot->reboot->profit?
At what point do I flash gapps? Reflash twrp?
Thanks in advance guys.

mr.duck254 said:
I will try these when I get home from work. So just to clarify.
Twrp->wipe->rom->kernel->reboot to fastboot->fastboot -w from fastboot->reboot->profit?
At what point do I flash gapps? Reflash twrp?
Thanks in advance guys.
Click to expand...
Click to collapse
Stock kernel will not work. Here is the AOSP kernel: https://drive.google.com/file/d/1nypgskfAoSOpOa_E-pfyaRO_mp_JWFxw/view?usp=drivesdk
Edit: gapps is included, no need to flash... Yet
Edit 2: reflash twrp right after flashing ROM if you want twrp on your boot images.

{
"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"
}
Worked like a charm. Thanks for the help guys. Time to take it for a test drive
Uzephi said:
Stock kernel will not work. Here is the AOSP kernel: https://drive.google.com/file/d/1nypgskfAoSOpOa_E-pfyaRO_mp_JWFxw/view?usp=drivesdk
Edit: gapps is included, no need to flash... Yet
Edit 2: reflash twrp right after flashing ROM if you want twrp on your boot images.
Click to expand...
Click to collapse

mr.duck254 said:
Worked like a charm. Thanks for the help guys. Time to take it for a test drive
Click to expand...
Click to collapse
Let us know the stability and what you've had issues with and what works!

Koohara947 said:
Let us know the stability and what you've had issues with and what works!
Click to expand...
Click to collapse
It was stated in the first page what's the issues with the roms.

Just got a z2 force on tmo. Unlocked and rooted already and now I've got the itch to flash something. Any recommendations on which rom to try out first? Preferably the most stable

raphi809 said:
Just got a z2 force on tmo. Unlocked and rooted already and now I've got the itch to flash something. Any recommendations on which rom to try out first? Preferably the most stable
Click to expand...
Click to collapse
All aosp ROMs currently out are based off the same, so they will have the same stability. They are stable, just features aren't working, like audio recording is hit and miss on apps

Uzephi said:
All aosp ROMs currently out are based off the same, so they will have the same stability. They are stable, just features aren't working, like audio recording is hit and miss on apps
Click to expand...
Click to collapse
Any special instructions as far as flashing goes. Since the rom section is kind of dead right now information seems to be kind of all over the place. My device is currently already on the stock Oreo rom. Can I just flash whatever rom zip and be good to go right now or do I have to worry about things like gapps, firmware and modem? Thanks for replying btw.

raphi809 said:
Any special instructions as far as flashing goes. Since the rom section is kind of dead right now information seems to be kind of all over the place. My device is currently already on the stock Oreo rom. Can I just flash whatever rom zip and be good to go right now or do I have to worry about things like gapps, firmware and modem? Thanks for replying btw.
Click to expand...
Click to collapse
In ROMs section, I got permission by the maintainer to create a thread for AOSiP, it has detailed instructions. All ROMs have the same install instructions.
I am open to any clarification, just post any issues you have with the instructions given. (say which number and what needs clarified).
Edit: firmware flashing will always be needed. You need the same firmware on both slots for seem-less updates to work on that ROM.

Update, any build after 05/05 will have the sprint LTE fix. I.E. you will have LTE on boot without any trickery.