Related
Hi All,
Not too familiar with Samsung development methods but bought S3 Korean SHV E210S, Luckily got 4.4.4 update, so for all those seeking to
1) Fix SMS 160 characters limit
2) International looking Dialer
3) Samsung Boot animation
4) SD card Write enabled
5) Removed Samsung apps, Knox , Korean Apps
All these stuff in one go in Flashable Zip without going through lots of hassle.
Also for those looking for Root and Recovery too, I have included guide below
Guide for those who have not yet flashed 4.4.4:
1. Download the Rom from sammobile from below link and flash using Odin (i used 3.09) in Downloadmode
http://www.sammobile.com/firmwares/download/35411/E210SKSUKNI3_E210SSKTKNI3_SKT.zip
2. Once Rom is booted, enter your accounts etc and then reboot into download mode again and download Flash TWRP Recovery from below link and flash using Odin (its for i9300- works for us)
http://techerrata.com/get/twrp2/i9300/openrecovery-twrp-2.8.0.1-i9300.tar
3. Now boot into recovery and flash the All in One Fix that I made
4. Stay in recovery and flash UPDATE-SuperSU-v2.13.zip to obtain root. You can download from link below
http://download.chainfire.eu/567/SuperSU/
5. Once you boot into system, open SuperSU, it might ask for updating binary, do it and reboot again
Thats it..
Additionally you can use Wanam Xposed from PlayStore which is very useful for all other mods.
Have fun..
PS: I dont have any problem if Mods want to mix it with the Huge S3 Koreans thread. It was a bit too congested so i thought i should make a separate thread
DOWNLOAD for All in One Fix :
https://www.mediafire.com/?shdxdw6hw3ayvjx
Thanks to
Chainfire
TWRP Team
Desamsungtizer script i used from S4 development from this thread which I Edited to include many other bloatwares specific for E210S
Thanks a lot, I have been searching for months for these fixes. I have posted questions on the "huge E210S" thread but had not obtained any response until now. This is exactly what I needed!
However, after running your fix on my rooted E210S with stock 4.4.4 ROM, the debloating also removed many non-SKT apps such as the "ordinary" Video and Music apps, and also Voice Dialer gone as well! I don't know whether this was supposed to happen or is it a specific problem for me...
jjdoctor said:
Hi All,
Not too familiar with Samsung development methods but bought S3 Korean SHV E210S, Luckily got 4.4.4 update, so for all those seeking to
1) Fix SMS 160 characters limit
2) International looking Dialer
3) Samsung Boot animation
4) SD card Write enabled
5) Removed Samsung apps, Knox , Korean Apps
All these stuff in one go in Flashable Zip without going through lots of hassle.
Click to expand...
Click to collapse
sonyxx said:
Thanks a lot, I have been searching for months for these fixes. I have posted questions on the "huge E210S" thread but had not obtained any response until now. This is exactly what I needed!
However, after running your fix on my rooted E210S with stock 4.4.4 ROM, the debloating also removed many non-SKT apps such as the "ordinary" Video and Music apps, and also Voice Dialer gone as well! I don't know whether this was supposed to happen or is it a specific problem for me...
Click to expand...
Click to collapse
you can always get those from PlayStore :fingers-crossed:
:good:
jjdoctor said:
Hi All,
Not too familiar with Samsung development methods but bought S3 Korean SHV E210S, Luckily got 4.4.4 update, so for all those seeking to
1) Fix SMS 160 characters limit
2) International looking Dialer
3) Samsung Boot animation
4) SD card Write enabled
5) Removed Samsung apps, Knox , Korean Apps
All these stuff in one go in Flashable Zip without going through lots of hassle.
Click to expand...
Click to collapse
Thanks you so much for sharing. You are very kind. God bless to you!
thank you so much, you are the best sire ! Mebay u could try make the zip file, odin flashable (.tar) so we wont have why to install recovery !
jjdoctor said:
you can always get those from PlayStore :fingers-crossed:
Click to expand...
Click to collapse
Hi @jjdoctor,
I did a fresh new install of the stock ROM on my device and then followed the steps to run this fix. Everything worked just fine, except for the SMS fix!
I tried reflashing again and re-installing the ROM before re-flashing still no success...
I don't remember what I did previously but I can't seem to be able to get the SMS limit fix anymore! Please, any ideas on what I can do here?
agree with sonyxx, except for sms limit fix everything work as fine as mentioned here
sonyxx said:
Hi @jjdoctor,
I did a fresh new install of the stock ROM on my device and then followed the steps to run this fix. Everything worked just fine, except for the SMS fix!
I tried reflashing again and re-installing the ROM before re-flashing still no success...
I don't remember what I did previously but I can't seem to be able to get the SMS limit fix anymore! Please, any ideas on what I can do here?
Click to expand...
Click to collapse
salluhassan said:
agree with sonyxx, except for sms limit fix everything work as fine as mentioned here
Click to expand...
Click to collapse
You guys are right, I will fix it sooner but a quick fix is to install Wanam Xposed from playstore, it will ask to download Xposed installer, do it, then reboot and in Modules select Wanam Xposed. Then open Wanam Xposed and messaging option in it, select disable Sms to Mms conversion.
I will fix it, just give me time
jjdoctor said:
You guys are right, I will fix it sooner but a quick fix is to install Wanam Xposed from playstore, it will ask to download Xposed installer, do it, then reboot and in Modules select Wanam Xposed. Then open Wanam Xposed and messaging option in it, select disable Sms to Mms conversion.
I will fix it, just give me time
Click to expand...
Click to collapse
yup that actually did it, now i am able to send more than 160 characters, thanks doctor.
If my shv-e210s phone is already on 4.4.4 and rooted, do I just need to flash your All In One Fix and that's it?
jshare said:
If my shv-e210s phone is already on 4.4.4 and rooted, do I just need to flash your All In One Fix and that's it?
Click to expand...
Click to collapse
yes..............
jjdoctor said:
yes..............
Click to expand...
Click to collapse
My e210s is on Sena rom v6. That dialer has Korean letters and doesn't include voicemail right now, so I flashed this mod but although the flash was successful, I didn't see any changes after a system reboot, so I removed it.
jjdoctor said:
yes..............
Click to expand...
Click to collapse
well jjdocktor, if you could make this file into a tar (odin flashable) would be awsome, i dont like flashing recoveries :crying:
help me..
Thnk a lot.by the way can u give this fixing zip in sparated files?(sms fix zip,dialer fix zip etc) .as well can u give a fix for activating sms delivery reports.its a big help..plz i look forward to hearing from you as early as possible.again thnk you!
SMS limit still 160 Characters
Dude 160 characters limit still not fixed everything worked well but sms :'(
Update: I edited the zip file and added edited xml files for the sms fix. Already tested working. Wipe cache/dalvik cache after flashing. Thanks. Credits to jjdoctors.
http://www.mediafire.com/download/96jn8e36jo5s8oh/SHV_E210S_4.4.4_EDITED.zip
Bro the original music player app is also deleted ? Can you take it back ?
Johny Van said:
Bro the original music player app is also deleted ? Can you take it back ?
Click to expand...
Click to collapse
Get it from here sir. They are already deodexed. Just copy to same folder and set proper permissions.
http://www.mediafire.com/download/2dcdiay55gmfl11/system.zip
Many thanks to you bro. GREAT WORK !
Hello everyone, I tried searching the forum for a solution but have not found any. I'm in a little predicament and I need some help!
Summary: I recently rooted my Verizon S5 using Towelroot and have safestrap installed. I am trying to install CM11 Rom and so far it hasn't been working for me. Everyone I boot up the rom for the first time I get the Samsung S5 boot screen and it is just black. Vibrates twice, and then loops back to the samsung boot screen.
Phone: Verizon Samsung S5 (G900V)
Android Version: 4.4.4
Baseband: ANI2, Kernel 3.4.0
Rooted with Towelroot, with safestrap 3.75 installed for verizon.
So far this is the procedure I have tried to install CM11:
1. Boot into recovery via safestrap.
2. Activate my ROM SLOT that I have created for custom ROM's.
3. Do a wipe (Cache, Data, Dalvik) and I have also tried wiping System also prior to installing CM11.
4. Flashing CM11 (downloaded from this thread: http://forum.xda-developers.com/gal...t/rom-cyanogenmod-11-0-android-4-4-4-t2864288) via buildbot mirror. I downloaded the latest release named: cm-11-20141104-UNOFFICIAL-kltevzw
5. After, flashing GAPPS also downloaded from the thread above for CM11.
6. They both successfully flash and I reboot the phone. (And yes I have tried wiping after flashing these two and rebooting but it still doesn't work)
7. The phone reboots, I see the Samsung S5 boot screen, then the splash screen for Safestrap, and then the screen goes black. The phone vibrates twice and then loops back to the Samsung S5 boot screen.
Does anyone know how to fix this? Thank you so much!
If your phone isn't a Dev Edition it will not work. CM Roms use AOSP and you can't run those or custom kernels on a retail edition phone.
Sent from my SM-G900V using XDA Free mobile app
Xaede said:
Hello everyone, I tried searching the forum for a solution but have not found any. I'm in a little predicament and I need some help!
Summary: I recently rooted my Verizon S5 using Towelroot and have safestrap installed. I am trying to install CM11 Rom and so far it hasn't been working for me. Everyone I boot up the rom for the first time I get the Samsung S5 boot screen and it is just black. Vibrates twice, and then loops back to the samsung boot screen.
Phone: Verizon Samsung S5 (G900V)
Android Version: 4.4.4
Baseband: ANI2, Kernel 3.4.0
Rooted with Towelroot, with safestrap 3.75 installed for verizon.
So far this is the procedure I have tried to install CM11:
1. Boot into recovery via safestrap.
2. Activate my ROM SLOT that I have created for custom ROM's.
3. Do a wipe (Cache, Data, Dalvik) and I have also tried wiping System also prior to installing CM11.
4. Flashing CM11 (downloaded from this thread: http://forum.xda-developers.com/gal...t/rom-cyanogenmod-11-0-android-4-4-4-t2864288) via buildbot mirror. I downloaded the latest release named: cm-11-20141104-UNOFFICIAL-kltevzw
5. After, flashing GAPPS also downloaded from the thread above for CM11.
6. They both successfully flash and I reboot the phone. (And yes I have tried wiping after flashing these two and rebooting but it still doesn't work)
7. The phone reboots, I see the Samsung S5 boot screen, then the splash screen for Safestrap, and then the screen goes black. The phone vibrates twice and then loops back to the Samsung S5 boot screen.
Does anyone know how to fix this? Thank you so much!
Click to expand...
Click to collapse
Since you're using SafeStrap, I'm assuming you have a retail edition Verizon S5 (non-developer edition).
1. Retail cannot use CM ROMs. Ever.
2. Safestrap does not flash any partitions other than cache, data, and system. Meaning even if you had a DevEd with safestrap, it would never flash a kernel.
BigBot96 said:
Since you're using SafeStrap, I'm assuming you have a retail edition Verizon S5 (non-developer edition).
1. Retail cannot use CM ROMs. Ever.
2. Safestrap does not flash any partitions other than cache, data, and system. Meaning even if you had a DevEd with safestrap, it would never flash a kernel.
Click to expand...
Click to collapse
Thank you for the quick replies, and also for clarifying. So would it be possible to run a custom ROM on a retail edition phone? What possibilities are possible (in terms of customization, root options, etc) for a retail edition phone?
Do XPOSED Framework Modules on retail verizon versions?
Xaede said:
Thank you for the quick replies, and also for clarifying. So would it be possible to run a custom ROM on a retail edition phone? What possibilities are possible (in terms of customization, root options, etc) for a retail edition phone?
Do XPOSED Framework Modules on retail verizon versions?
Click to expand...
Click to collapse
Any of the ROMs located in the Verizon Galaxy S 5 Android Development subforum as long as it states compatible with retail edition.
BigBot96 said:
Any of the ROMs located in the Verizon Galaxy S 5 Android Development subforum as long as it states compatible with retail edition.
Click to expand...
Click to collapse
And in terms of customization?
Xaede said:
And in terms of customization?
Click to expand...
Click to collapse
That's up to you depending on what you're looking for. The most customizable, tough, is Alliance. Each ROM offers the devs own take on "custom rom". Just gotta find one you want to use.
BigBot96 said:
That's up to you depending on what you're looking for. The most customizable, tough, is Alliance. Each ROM offers the devs own take on "custom rom". Just gotta find one you want to use.
Click to expand...
Click to collapse
Thank you alot BigBot!
Xaede said:
Thank you alot BigBot!
Click to expand...
Click to collapse
Yo, only problem is that they just dropped support for the S5 in favor of the N6 I really thought there was hope for the work on the bootloader or even the N12 build update Really gonna miss that Rom
kemerystudios said:
Yo, only problem is that they just dropped support for the S5 in favor of the N6 I really thought there was hope for the work on the bootloader or even the N12 build update Really gonna miss that Rom
Click to expand...
Click to collapse
you can thank vzw/samsung for locking the BL down so good for that lol
elliwigy said:
you can thank vzw/samsung for locking the BL down so good for that lol
Click to expand...
Click to collapse
Yep, locked bootloaders SUCK!!! Samsung and Big Red can lick my...
Ummm... Popsicle! Almost forgot this is a family friendly environment.
elliwigy said:
you can thank vzw/samsung for locking the BL down so good for that lol
Click to expand...
Click to collapse
Good News though! Beans may pass permission down to Goldie and others so that progress can continue! Im all in for that, and my friend and I have been "experimenting" with a couple theories that may help future phones, boot loaders and other stuff.. So yeah, happy Modding!
---------- Post added at 03:08 AM ---------- Previous post was at 03:03 AM ----------
ludeawakening said:
Yep, locked bootloaders SUCK!!! Samsung and Big Red can lick my...
Ummm... Popsicle! Almost forgot this is a family friendly environment.
Click to expand...
Click to collapse
Hey, I blame Samsung for Knox amd other bloat/crap, but in honesty they are a company that makes these phones for crowds that buy them for the crap they put on them. BIG RED the world fattest *****iest carrier (excuse the language) makes me extremely... Angry... For lack of other words... They are CDMA, bootlock their phones, slow updates down, and charge a ****ton for it! They are bad. Just bad. Fix that crap Verizon, just fix it. No more begging for you to stop torturing me, I swear another slip up and I quit! TMobile here I come, also Ludeawaking, I hope you get the rights from beans and good luck, and Elliwigily (sorry i forgot how to spell you name :| ) great debloat, still is a great daily driver! Happy Modding!
I own a Coolpad Note 3 running on Android 5.1 Lollipop and packs MT6753 MediaTek 64-bit octacore processor and 3GB RAM. After rooting this device, when I installed Xposed Framework, though it installed successfully but shows a message that this version isn't supported yet. What is this message and when is this platform going to get supported. This was heartbreaking because the major reason of rooting the device was this Framework.
What version of Xposed did you attempt to install? What method did you use to install? What does it say in the log file? We cannot help you without this information.
Details of installed version of Xposed Framework
Spott07 said:
What version of Xposed did you attempt to install? What method did you use to install?
Click to expand...
Click to collapse
First, I tried official version of Xposed Installer for lollipop devices. It was a failure(a message popped out after installing that Xposed is not yet supported on this processor platform). Then I referred to the blog Android Beat(How to install Xposed framework on Android 5.1 Lollipop) and downloaded this file "xposed-v78-sdk22-arm64.zip". I flashed it using custom recovery based on CWM. I was stuck in a boot loop after that. Then I was left with no option but to flash my stock ROM as I had no backup at that time.
TheGuyIsHere said:
First, I tried official version of Xposed Installer for lollipop devices. It was a failure(a message popped out after installing that Xposed is not yet supported on this processor platform). Then I referred to the blog Android Beat(How to install Xposed framework on Android 5.1 Lollipop) and downloaded this file "xposed-v78-sdk22-arm64.zip". I flashed it using custom recovery based on CWM. I was stuck in a boot loop after that. Then I was left with no option but to flash my stock ROM as I had no backup at that time.
Click to expand...
Click to collapse
Please refer to the official Xposed for Lollipop thread, especially post #2. There you'll find an FAQ about common issues and a table to identify the correct Xposed version. You need to flash the correct .zip file through recovery (as you have done before) and install the Xposed_Installer_alpha3.apk afterwards. After flashing, wipe cache&dalvik, as Xposed alters a lot of files in your system, so this step is highly recommended. If this does not solve your issue, search the thread, there have been several questions about Mediatek compatibility before.
Your initial error (Xposed not compatible) was due to the fact that you tried to install the old Xposed installer for KitKat, which is not compatible with Lollipop.
Noted.
I am definitely going to refer to that thread and will update here after that. Thanks for your precious time.
Some advancements
A guy using Coolpad note 3 tried a method to install Xposed and it worked(to some extent though). What he did was he installed busybox, flashed the Xposed zip files. After rebooting, he still got caught in a bootloop but after 15-20 boot loops(seems like it depends on no. of apps installed as each time his phone booted, percentage of optimising apps increased), he was finally able to start his phone. Now under Xposed settings, he checked disable resourced hooks and rebooted. He got Xposed Framework active status after rebooting. A no. of apps which modify UI like gravitybox, xblastools, greenify in root mode etc were not working. But a few others worked quiet well. Could anyone throw some light on this issue?
TheGuyIsHere said:
A guy using Coolpad note 3 tried a method to install Xposed and it worked(to some extent though). What he did was he installed busybox, flashed the Xposed zip files. After rebooting, he still got caught in a bootloop but after 15-20 boot loops(seems like it depends on no. of apps installed as each time his phone booted, percentage of optimising apps increased), he was finally able to start his phone. Now under Xposed settings, he checked disable resourced hooks and rebooted. He got Xposed Framework active status after rebooting. A no. of apps which modify UI like gravitybox, xblastools, greenify in root mode etc were not working. But a few others worked quiet well. Could anyone throw some light on this issue?
Click to expand...
Click to collapse
Unless you're the one trying it, and you can supply full logcats for the entire multi-reboot process, we probably can't know for sure.
Spott07 said:
Unless you're the one trying it, and you can supply full logcats for the entire multi-reboot process, we probably can't know for sure.
Click to expand...
Click to collapse
I will try it myself and hopefully provide logcats for the entire multi-boot process.
Can you please share which version of xposed you used because I did the same and it was stuck on bootloop then I realized that the % of starting up apps was increasing gradually but after 3-4 attemps it went down and started from zero and so I flashed it again.
I think the issue is that i used xposed arm64-v78 sdk22 but my device is arm64-v8a, and I guess xposed is not yet released for arm64-v8a sdk22 devices.
So finally with this thread I got a hope to try it again and please share as much info as you can coz its gonna help others a lot
I came back here to give the good news that I did it.
But glad to know that we already got the tutorial.
One problem: donkey guard module is not working, showing unfortunately donkey guard has stopped working.
Any solution???
Btw thank you so much coz know a lot of people have been searching for it from aaa long time.
mukeshkhan2008 said:
I came back here to give the good news that I did it.
But glad to know that we already got the tutorial.
One problem: donkey guard module is not working, showing unfortunately donkey guard has stopped working.
Any solution???
Btw thank you so much coz know a lot of people have been searching for it from aaa long time.
Click to expand...
Click to collapse
DonkeyGuard module won't work on lollipop. Any app that changes system behaviour seems to have not worked on this platform yet. Refer to this post for more info:
https://m.reddit.com/r/Android/comments/2vt70q/xposed_for_lollipop_is_out_lets_get_a_list_of/
mukeshkhan2008 said:
I came back here to give the good news that I did it.
But glad to know that we already got the tutorial.
One problem: donkey guard module is not working, showing unfortunately donkey guard has stopped working.
Any solution???
Btw thank you so much coz know a lot of people have been searching for it from aaa long time.
Click to expand...
Click to collapse
can u please tell me how to install xposed in cp3?
Using which phone?
mukeshkhan2008 said:
I came back here to give the good news that I did it.
But glad to know that we already got the tutorial.
One problem: donkey guard module is not working, showing unfortunately donkey guard has stopped working.
Any solution???
Btw thank you so much coz know a lot of people have been searching for it from aaa long time.
Click to expand...
Click to collapse
U used it on Coolpad Note 3???
TheGuyIsHere said:
I own a Coolpad Note 3 running on Android 5.1 Lollipop and packs MT6753 MediaTek 64-bit octacore processor and 3GB RAM. After rooting this device, when I installed Xposed Framework, though it installed successfully but shows a message that this version isn't supported yet. What is this message and when is this platform going to get supported. This was heartbreaking because the major reason of rooting the device was this Framework.
Click to expand...
Click to collapse
Hello I have the same phone too but how did you root it
Rooting method
arjithpraison said:
Hello I have the same phone too but how did you root it
Click to expand...
Click to collapse
Here is the step-by-step guide to root Coolpad Note 3:
http://www.anythingultimate.in/2015/10/how-to-root-coolpad-note-3.html?m=1
Follow the guide and you will be successfully able to root your phone. Best of luck!
Do hit thanks if this post helped you.
wanting xposed un istaller for coolpad note 3
Hey i m installing xposed version 78 running good but u want to fully un root & un install xposed frame work for getting new android version update marsh mallow 6.0 for this mobile in next week so i want to update thats why i want fully un root also ( im using super su ) so plz help.me suggeat which vesion of unistaller i want to use for rempving xposed frame work
santosh reddy 143 said:
Hey i m installing xposed version 78 running good but u want to fully un root & un install xposed frame work for getting new android version update marsh mallow 6.0 for this mobile in next week so i want to update thats why i want fully un root also ( im using super su ) so plz help.me suggeat which vesion of unistaller i want to use for rempving xposed frame work
Click to expand...
Click to collapse
You can find the uninstaller in the same thread where you have found the correct Xposed framework version for your device. Use the same specs (SDK version, ARM version) as for the Xposed framework for the uninstaller and flash it. Don't forget to wipe cache&dalvik afterwards.
I installed xposed but when I click reboot it says
de.robv.android.xposed.installer/cache/busybox-xposed: not found
sxda7 said:
I installed xposed but when I click reboot it says
de.robv.android.xposed.installer/cache/busybox-xposed: not found
Click to expand...
Click to collapse
did you install busybox?
Nergal di Cuthah said:
did you install busybox?
Click to expand...
Click to collapse
yes but i don't know why it keeps saying that everytime i try to reboot xposed
Hello hello,
So I reverted to my old i337 (ATT) because my S6 is defect and Samsung are hanging me out to dry (whole other story there). That being said, this i337 was on CM 11 4.4.4 but had the home-brew version, a slew of issues and so on. It did have root though.
I managed to install TWRP 2.8, CM 12.1 official build and it works flawlessly up until now. Except, I lost root. I'm puzzled too because running Motochopper tells me it's already rooted, and if I install Superuser form Play it seems to recognize the root, but then tells me I need to update, which fails. If I try to install any root app, nothing works.
Interestingly, I had to temporarily downgrade to CM 11 throughout this to troubleshoot a bug with GApps, and even after "losing" root to CM 12, in 11 I still had root! Back to CM 12 and out the root again. I've looked through threads and the only thing I found remotely close was to go back to 4.2.2 stock, then flash, then upgrade again... I'm trying to find another way since everthing else works fine...
Seems like it's a question of root method having changed in Lollipop, but that's really the extent of my knowledge.
As always, any help would be appreciated!
Denis
Edit: BB is I337UCUAMDL
Did you enable developer options, then go down to root access and enable it from there?
njf789 said:
Did you enable developer options, then go down to root access and enable it from there?
Click to expand...
Click to collapse
That is such a noob comment!! Did I enable... pfff! Of course... I... uh... oh. Yeah I guess that's a new option then, is it? *nervously whistling away*
PS: thanks! had no idea that was a thing I've updated my sig to celebrate.
DenisEhm said:
Hello hello,
So I reverted to my old i337 (ATT) because my S6 is defect and Samsung are hanging me out to dry (whole other story there). That being said, this i337 was on CM 11 4.4.4 but had the home-brew version, a slew of issues and so on. It did have root though.
I managed to install TWRP 2.8, CM 12.1 official build and it works flawlessly up until now. Except, I lost root. I'm puzzled too because running Motochopper tells me it's already rooted, and if I install Superuser form Play it seems to recognize the root, but then tells me I need to update, which fails. If I try to install any root app, nothing works.
Interestingly, I had to temporarily downgrade to CM 11 throughout this to troubleshoot a bug with GApps, and even after "losing" root to CM 12, in 11 I still had root! Back to CM 12 and out the root again. I've looked through threads and the only thing I found remotely close was to go back to 4.2.2 stock, then flash, then upgrade again... I'm trying to find another way since everthing else works fine...
Seems like it's a question of root method having changed in Lollipop, but that's really the extent of my knowledge.
As always, any help would be appreciated!
Denis
Edit: BB is I337UCUAMDL
Click to expand...
Click to collapse
Wait! So you have CM12 on your ATT S4?
I spent 6 hours yesterday and managed to instal golden eye 53. But I'd like to try installing cm12.
Can you point me the link of the relevant thread?
Thanks
Sarfarash said:
Wait! So you have CM12 on your ATT S4?
I spent 6 hours yesterday and managed to instal golden eye 53. But I'd like to try installing cm12.
Can you point me the link of the relevant thread?
Thanks
Click to expand...
Click to collapse
Yes and I can say that aside from very minor bugs (such as I can't get weather to work) it's by far the best ROM I've had on this phone! The nice thing too is it's officially supported.
First you can download the ROM here; I used the last stable release for 12.1, right at the top.
For instructions I would suggest to go on the official wiki for the jflteatt, but make sure you are using TWRP version 2.8.7.0. I was on a CWM custom recovery which worked fine for 4.4.4, but when I flashed 5.1 it was plagued with crashes and GApps were completely useless - even if it did technically work. Trust me, this will save you a lot of time and it's not really mentioned anywhere.
Also stay away form TWRP version 3.0; when I tried to install it it re-locked my boot loader (somehow) and I had to fiddle-fsck around a lot with it to bypass it again.
But outside this, it was a flawless install for me! Hope this helps.
DenisEhm said:
That is such a noob comment!! Did I enable... pfff! Of course... I... uh... oh. Yeah I guess that's a new option then, is it? *nervously whistling away*
PS: thanks! had no idea that was a thing I've updated my sig to celebrate.
Click to expand...
Click to collapse
No problem man. There is also a setting in Super User to override the CM root setting iirc. Just FYI
njf789 said:
No problem man. There is also a setting in Super User to override the CM root setting iirc. Just FYI
Click to expand...
Click to collapse
Yeah I had tried that but it wouldn't do anything. I've followed your advice and now it works perfectly. Thanks again!
DenisEhm said:
Yes ......
For instructions I would suggest to go on the official wiki for the jflteatt,
..... I was on a CWM custom recovery which worked fine for 4.4.4
Click to expand...
Click to collapse
Thank you very much,
I got excited for few minutes, then I followed the instructions link, and saw that big red banner of warning saying only MDL and MDB can use it.
And I am on OC3 (5.0.1) so I guess I'm out of luck!
Sarfarash said:
Thank you very much,
I got excited for few minutes, then I followed the instructions link, and saw that big red banner of warning saying only MDL and MDB can use it.
And I am on OC3 (5.0.1) so I guess I'm out of luck!
Click to expand...
Click to collapse
Ah yes that's true, I'm on MDL... bummer...
Hi guys,
Just rooted my S8 and installed TWRP, using STOCK Samsung ROM, AQH3. I noticed in the Camera that "Selective Focus" is not working anymore. I didn't change anything else, just rooted the device and installed Notorious Kernel, before doing this the Selective Focus was working OK. So does anyone know what happened? Any help would be highly appreciated, I really like this shooting mode. Thank you!
EDIT: To clarify: before this I got sometimes the error, but mostly of the time it worked well. Now after rooting the phone and installing TWRP it doesn't work at all in any conditions, even with different subjects.. I've heard someone reporting this issue in another thread, but I can't remember at all
Root these days is nothing but problems.
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
blak24 said:
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
Click to expand...
Click to collapse
Flash stock firmware through Odin and then check again if this solve the issue.
Also which method of root? Magisk or SuperSu?
I used Magisk. Anyway if I'll flash stock firmware through Odin I'll lose TWRP and root and everything else right?
blak24 said:
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
Click to expand...
Click to collapse
Seems like kernel related issue
Mmmh so you suggest to try changing kernel and/or flashing the stock one to see if the issue persists?