Hello forum,
after digging around in plenty of places:
the screen of my S10+ (G975F) does not turn off, during phone calls. it used to work for a while, when i bought it, but one day it stopped.
testing with *#77692# shows a working sensor.
installing Lineage OS 17, i find it working normally. but Lineage is no go, as with the poor coverage here at home, i depend on Voice over WiFi.
so i assume, it's software, not hardware.
i tried about all updates from Samsung, until now, apart from G975FXXU4CTC9. As i read, that there are some quirks with TWRP, i hesitate to install this, as the downgrade isn't possible, after my understanding.
i found out that deactivating google playstore and everything xy.setup keeps the sensor working. it stops, after connecting to playstore and doing updates. so i still think it is definitely not hardware. but what else could be the cause ?
did someone else come across this problem and eventually really solve it ?
thanks for Your help
roland
blackspy_ said:
Hello forum,
after digging around in plenty of places:
the screen of my S10+ (G975F) does not turn off, during phone calls. it used to work for a while, when i bought it, but one day it stopped.
testing with *#77692# shows a working sensor.
installing Lineage OS 17, i find it working normally. but Lineage is no go, as with the poor coverage here at home, i depend on Voice over WiFi.
so i assume, it's software, not hardware.
i tried about all updates from Samsung, until now, apart from G975FXXU4CTC9. As i read, that there are some quirks with TWRP, i hesitate to install this, as the downgrade isn't possible, after my understanding.
i found out that deactivating google playstore and everything xy.setup keeps the sensor working. it stops, after connecting to playstore and doing updates. so i still think it is definitely not hardware. but what else could be the cause ?
did someone else come across this problem and eventually really solve it ?
thanks for Your help
roland
Click to expand...
Click to collapse
Check in setting/running apps,
some apps are using the sensor so you are getting this problem.
If you cannot fix this problem then try wiping cache only not data.
Sent from my P5 mini using premium XDA app
PrashannaGP said:
Check in setting/running apps,
some apps are using the sensor so you are getting this problem.
If you cannot fix this problem then try wiping cache only not data.
Click to expand...
Click to collapse
I wiped everything about a dozen times. it happens after fresh install, when google is doing its first setups and updating the playstore/framework. and also in safe mode, where no apps should be involved.
the only way not to have it, is to deactivate everything "google" and "setup" without SIM and WLAN. re-activating them, later, leads to the same problem again. no additional apps installed.
blackspy_ said:
I wiped everything about a dozen times. it happens after fresh install, when google is doing its first setups and updating the playstore/framework. and also in safe mode, where no apps should be involved.
the only way not to have it, is to deactivate everything "google" and "setup" without SIM and WLAN. re-activating them, later, leads to the same problem again. no additional apps installed.
Click to expand...
Click to collapse
What could be the problem then! I never had this problem ever with same device and same rom too
Check your hardware using
HTML:
CPU-Z apk
PrashannaGP said:
:
Check your hardware using
HTML:
CPU-Z apk
Click to expand...
Click to collapse
as mentioned before: the hardware is ok, otherwise it would not work with *#77692#, nor in lineage OS. an other way to have it working is: re-lock bootloader and unrooted stock. so definitely not hardware
blackspy_ said:
as mentioned before: the hardware is ok, otherwise it would not work with *#77692#, nor in lineage OS. an other way to have it working is: re-lock bootloader and unrooted stock. so definitely not hardware
Click to expand...
Click to collapse
I got the solution
If you have a perfectly working custom ROM or stock ROM then from that rom get
system/lib/hw/sensor.so file something like that and replace the folder that you currently have
And make sure you put the permission as rw-r-r
Use es file explorer
System/lib/hw/sensor....so file
{
"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"
}
Sent from my P5 mini using XDA-Developers Legacy app
PrashannaGP said:
I got the solution
If you have a perfectly working custom ROM or stock ROM then from that rom get
system/lib/hw/sensor.so file something like that and replace the folder that you currently have
Click to expand...
Click to collapse
so, i assume that i grab the file when the phone is still working properly and then replace it, once the problem showed up again - correct ?
blackspy_ said:
so, i assume that i grab the file when the phone is still working properly and then replace it, once the problem showed up again - correct ?
Click to expand...
Click to collapse
grab that sensor.so file and paste in to the /system/lib/hw/..........paste....here
it is not correct because when you replace the file your device will reboot but no worries
when your device restarts
and go to the place where you replace the file /system/lib/hw/........sensor.so.....may be...
and change the permission of the file to
rw-r-r
Click to expand...
Click to collapse
and only this will work.
once you change the permission using ES file EXPLORER or ROOT Explorer
you have to reboot twice.
PrashannaGP said:
and go to the place where you replace the file /system/lib/hw/........sensor.so.....may be....
Click to expand...
Click to collapse
"sensor.so" does not exist, neither in the above path, nor anywhere else on the device
i attached the searchresults for "sensor.so" and just "sensor". the only thing that comes close to what you wrote, is sensors.exynos9820.so. but that is in /vendor/lib/hw.
i'm a bit lost there
blackspy_ said:
"sensor.so" does not exist, neither in the above path, nor anywhere else on the device
i attached the searchresults for "sensor.so" and just "sensor". the only thing that comes close to what you wrote, is sensors.exynos9820.so. but that is in /vendor/lib/hw.
i'm a bit lost there
Click to expand...
Click to collapse
Yes what I am telling you is to replace the sensor file not necessarily it should be in other folder with .....name.....
Only the thing is to change the file carefully and change permission to
rw-r-r
That's all its not necessary where the location is.
Sent from my [device_name] using XDA-Developers Legacy app
PrashannaGP said:
grab that sensor.so file and paste in to the /system/lib/hw/..........paste....here
.
Click to expand...
Click to collapse
unfortunately, replacing
/vendor/lib/hw/sensors.exynos9820.so
and
/vendor/lib64/hw/sensors.exynos9820.so
with the ones from when it was working, did not help.
and yes, i did change to rwx rxx rxx
interesting is, that it works the whole day, until ... 05:20 in the morning - then it stops. after that the problem stays permanently
blackspy_ said:
unfortunately
and yes, i did change to rwx rxx rxx
Click to expand...
Click to collapse
I told you to change from rwx rxx rxx to rw r r
you did this??
rwx rxx rxx
Click to expand...
Click to collapse
which is incorrect
should be this
Code:
rw r r
PrashannaGP said:
I told you to change from rwx rxx rxx to rw r r
you did this??
Click to expand...
Click to collapse
just wrote it wrong: rw- r-- r-- like all the other files.
i'll do some testing now, how to restore to working again. apart from installng from scratch ...
PrashannaGP said:
Code:
rw r r
Click to expand...
Click to collapse
blackspy_ said:
i'll do some testing now, how to restore to working again. apart from installng from scratch ...
Click to expand...
Click to collapse
in fact, it is very hard to get rid of it. resetting the phone, wiping whatever, reflashing, changing version or region of OS don't help at all, custom ROMs neither. aborting a flash, or flashing the wrong firmware neither. the only thing that helped this time, was to insert another simcard.
but after installing two more apps this morning (3C Toolbox and Nova Launcher) the problem is there again.
but this time the SIM-card trick doesn't help. uninstalling the two apps neither. this seems to work only once.
i think i will start from scratch i.e. re-lock/unlock bootloader ...
blackspy_ said:
i think i will start from scratch i.e. re-lock/unlock bootloader ...
Click to expand...
Click to collapse
yes rooting and flashing custom roms means having too many bugs.
And Even sometimes the official software updates have bugs.
No one except the rom developer can fix the problem.
The method that i told you was for fixing general bugs of sensors and camera.
The android is a complex coded Operating System and is attached to every files and empty folder and also if the empty folders are deleted then it will start many proplems.
PrashannaGP said:
The method that i told you was for fixing general bugs of sensors and camera.
Click to expand...
Click to collapse
this and nothing else does help right now. even going to stock with locked bootloader. the phone screen stays on. it only works in lineage OS.
update:
got it working again, by 1st doing an improper rooting i.e. flash stock and then not let it boot up
2nd try to flash the patched AP which aborts 3. flash stock again and root it properly.
then delete all the settings from what's called "setup", "update" and so on - all what is being done at 1st. start. then deactivate all those apps, do another reset from menu, but not boot to TWRP, where the reset will be completed. all this was done without network and playstore and with no simcard.
i don't know at what point it started working again, but right know, it does. will set it up properly now, as i expect it to be working after setup. it will only stop tonite around 05:20 CET --- i hope.
don't know if all this clarifies anything ...
Related
I called one day the Touchscreen USSD #removed for n00bs and I don't know that this destroy you touchscreen #
but i pressed the UPDATE button DONT TRY and.... touchscreen doesnt work ... after... Update completed!!! Touchscreen works!!!
Is this UPDATE button harmful as update Camera firmware, or is will update a bit of touchscreen files for Android?
It works for me but Don't Try it!! I does't will have a touchscreen series brick on XDA-developers
If this Update butten too harmfull, please remove this therad
Please help...
i'm the victim
I think doing that is harmful!! coz it had killed my touchscreen after update fail!!
still lookin for soln!
but by the way! thanx for ur warning!
SOLUTION!!!!!!!
Rutayuga91 said:
I think doing that is harmful!! coz it had killed my touchscreen after update fail!!
still lookin for soln!
but by the way! thanx for ur warning!
Click to expand...
Click to collapse
-Solution-
Before we start, make sure you have Java, if not download from here: http://java.com/en/download
I did the touch screen firmware update on my old S5570, i deliberately took battery out during update as i couldnt care less about the phone and wanted a challenge; and sure enough it was dead... But wait... I managed to successfully fix it.... how?
Well
1. Put a custom recovery on your phone (Preferably CWM) - On my samsung you put it into download mode and flash through odin
2. Download ANY custom ROM for your device (.zip format)
3. Open the downloaded zip on your computer, navigate using WinRAR to /system and find the file build.prop, open that file with WordPad, not Notepad but WORDPAD. Find where it says "persist", and there will be a few that start with that, go to the last line and insert:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
This enables USB Debugging by default, I'll explain why you need this later,
Ok save the build.prop and stick it back in the ZIP archive, now download this: https://www.mediafire.com/?omdol91672ieenr
Extract contents to Java directory C:/Program Files (x86)/Java/<Java>/bin (or C:/Program Files/Java/<Java>/bin for 32-bit)
Run cmd and type cd C:/Program Files (x86)/Java/<Java>/bin
(eg "cd C:\Program Files (x86)\Java\jre7\bin")
Place your modified .zip in the /bin folder and name as "rom.zip"
Run sign_file.bat
There should be a rom_signed.zip file in the /bin directory
Now put your phone in recovery and Mount USB storage, drag your "rom-signed.zip" in the root directory, I imagine you'd know how to flash it, but remember to wipe data and cache before hand
Now here's the fun bit
Reboot phone after ROM is installed, 1st boot may take a while
Plug USB in to your computer and download ADB: http://androidarea51.com/downloads/adb.zip
Extract to C drive, now open CMD and type cd.. and cd.. again, then type adb devices, hopefully your phone's serial should appear, if not you have either not got drivers installed or you have done something wrong
So you see your serial number beside adb devices? Great
Now download this: http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/androidscreencast.jnlp
^^ This requires USB Debugging ^^
And run it, press a button on your phone and it should appear on your pc screen, using your mouse run through the setup proccess, once done open dialer and press "*#2663#" and press Update, then after reboot your phone and...
Touchscreen fixed successfully xD
This worked for me anyway, sorry if some of the instructions are hard to follow, it's my first tutorial so sorry, but please reply if you need any help
Hi, I was trying to follow your tutorial but when I try to install the rom "signed" CWM says that there's an error, I already tried with different recoveries and in some cases it says that the MD5 doesn't exist or the file is not signed or that the rom-signed.zip file can't be opened. I'm using CWM 6.0.4.5 and twrp 2.7.1.0. but I can't install the rom.
Try to recopy
lalo69 said:
Hi, I was trying to follow your tutorial but when I try to install the rom "signed" CWM says that there's an error, I already tried with different recoveries and in some cases it says that the MD5 doesn't exist or the file is not signed or that the rom-signed.zip file can't be opened. I'm using CWM 6.0.4.5 and twrp 2.7.1.0. but I can't install the rom.
Click to expand...
Click to collapse
Hi. Have you tried to recopy the ROM zip file to your sdcard? This usually happens to me also. Maybe the zip was corrupted while copying it from the PC to your sd card. Try to recopy the ROM.
failed to update.
pcwiztech said:
-Solution-
Before we start, make sure you have Java, if not download from here: http://java.com/en/download
I did the touch screen firmware update on my old S5570, i deliberately took battery out during update as i couldnt care less about the phone and wanted a challenge; and sure enough it was dead... But wait... I managed to successfully fix it.... how?
Well
1. Put a custom recovery on your phone (Preferably CWM) - On my samsung you put it into download mode and flash through odin
2. Download ANY custom ROM for your device (.zip format)
3. Open the downloaded zip on your computer, navigate using WinRAR to /system and find the file build.prop, open that file with WordPad, not Notepad but WORDPAD. Find where it says "persist", and there will be a few that start with that, go to the last line and insert:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
This enables USB Debugging by default, I'll explain why you need this later,
Ok save the build.prop and stick it back in the ZIP archive, now download this: https://www.mediafire.com/?omdol91672ieenr
Extract contents to Java directory C:/Program Files (x86)/Java/<Java>/bin (or C:/Program Files/Java/<Java>/bin for 32-bit)
Run cmd and type cd C:/Program Files (x86)/Java/<Java>/bin
(eg "cd C:\Program Files (x86)\Java\jre7\bin")
Place your modified .zip in the /bin folder and name as "rom.zip"
Run sign_file.bat
There should be a rom_signed.zip file in the /bin directory
Now put your phone in recovery and Mount USB storage, drag your "rom-signed.zip" in the root directory, I imagine you'd know how to flash it, but remember to wipe data and cache before hand
Now here's the fun bit
Reboot phone after ROM is installed, 1st boot may take a while
Plug USB in to your computer and download ADB: http://androidarea51.com/downloads/adb.zip
Extract to C drive, now open CMD and type cd.. and cd.. again, then type adb devices, hopefully your phone's serial should appear, if not you have either not got drivers installed or you have done something wrong
So you see your serial number beside adb devices? Great
Now download this: http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/androidscreencast.jnlp
^^ This requires USB Debugging ^^
And run it, press a button on your phone and it should appear on your pc screen, using your mouse run through the setup proccess, once done open dialer and press "*#2663#" and press Update, then after reboot your phone and...
Touchscreen fixed successfully xD
This worked for me anyway, sorry if some of the instructions are hard to follow, it's my first tutorial so sorry, but please reply if you need any help
Click to expand...
Click to collapse
sir it always fails to update. any solution? im using galaxy pocket.
sumtingswong said:
sir it always fails to update. any solution? im using galaxy pocket.
Click to expand...
Click to collapse
What fails to update?
The ROM installation or Touchscreen?
Finally
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.
---------- Post added at 08:33 AM ---------- Previous post was at 08:22 AM ----------
pcwiztech said:
What fails to update?
The ROM installation or Touchscreen?
Click to expand...
Click to collapse
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.
sumtingswong said:
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.
Click to expand...
Click to collapse
Why do you want to do this - there is no benefit and a strong possibility your touchscreen will no longer work if it goes wrong
marcussmith2626 said:
Why do you want to do this - there is no benefit and a strong possibility your touchscreen will no longer work if it goes wrong
Click to expand...
Click to collapse
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.
sumtingswong said:
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.
Click to expand...
Click to collapse
you can try
http://forum.xda-developers.com/showthread.php?t=1505412
the guide is for the galaxy mini but you should be able to adapt it
sumtingswong said:
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.
Click to expand...
Click to collapse
Try this ROM, this should contain the touchscreen binary in the kernel fixing the update fail message: http://www.mediafire.com/download/l570r7dm7545m34/explode+rom+build+5.zip
pcwiztech said:
Try this ROM, this should contain the touchscreen binary in the kernel fixing the update fail message: http://www.mediafire.com/download/l570r7dm7545m34/explode+rom+build+5.zip
Click to expand...
Click to collapse
still no luck sir, still says update fail.
sumtingswong said:
still no luck sir, still says update fail.
Click to expand...
Click to collapse
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage
pcwiztech said:
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage
Click to expand...
Click to collapse
it only have one option sir, just update.
{
"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"
}
please help me sir.
pcwiztech said:
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage
Click to expand...
Click to collapse
sumtingswong said:
it only have one option sir, just update.
please help me sir.
Click to expand...
Click to collapse
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila
pcwiztech said:
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila
Click to expand...
Click to collapse
Okay sir, i'll just try all the custom roms.
pcwiztech said:
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila
Click to expand...
Click to collapse
after 10 attempts still no luck sir. please advice.
sumtingswong said:
after 10 attempts still no luck sir. please advice.
Click to expand...
Click to collapse
Hi, sorry for delayed reply, It's morning here.
Unfortunately i think the only option will be to replace your phones digitizer, this will cost around £15-£25 from eBay
Unless you can find a boot.img (kernel) that has the touchscreen firmware then that's your only choice.
pcwiztech said:
Hi, sorry for delayed reply, It's morning here.
Unfortunately i think the only option will be to replace your phones digitizer, this will cost around £15-£25 from eBay
Unless you can find a boot.img (kernel) that has the touchscreen firmware then that's your only choice.
Click to expand...
Click to collapse
thanks for your help sir, i really appreciated it. £15 is the price of a 2nd hand galaxy pocket here sir, so i guess i should really saved for it. i guess i should give up now, it's been quite sometime since ive been stressing myself because of this. godbless you sir.
DO NOT TRY TO USE THIS TO FLASH CUSTOM ROMS/RECOVERIES/KERNELS. THIS IS ONLY TO INSTALL TWEAKS THAT COME IN THE FORMAT OF A FLASHABLE .ZIP! READ THIS AND THE DEVELOPER'S THREAD BEFORE YOU PROCEED WITH THIS! I'M NOT RESPONSIBLE FOR BRICKS!
I thought all S4 active users should be aware of this -- you CAN flash CWM/TWRP .zip files WITHOUT a custom recovery. Albeit the app is a proof-of-concept/beta. It still does work and people with locked-down xperia phones use it to flash .zips
If you're on a regular S4 you'd be better off using CWM or TWRP so stop reading this.
You also cannot flash custom ROMs with this. Certain system files are critical to maintaining stability and if they are overwritten while the device is powered on it'll crash and you'll have a bricked franken-ROM phone. Don't try to flash kernels or recoveries with this either. You're just asking for trouble.
By clicking "Show" below you agree that I'm not responsible for your phone exploding or bricking when you do this. You could easily end up in a boot-loop and have to restore with odin. As a matter of fact, even if you do everything correctly you could still end up with a bricked phone. It won't be my fault. There is no way to do nandroids as of now so you will have to restore to out-of-box state with odin and start from square one.
From your phone:
1) Visit the developer's thread here
2) Read his thread and make sure you understand any warnings/consequences of using his tool.
3) Scroll to the bottom of the page, download and install the APK
{
"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"
}
4) Download your favorite flashable mod .zips. There's some links at the bottom of the OP.
5) Click "Select zip.." and then use your favorite file explorer to navigate to the location of your .zipped mod/tweak/whatever
6) Flash Gordon will request superuser, choose "accept"
7) Double check that you selected the correct .zip and have the correct options
8) Click "Flash Now!". Don't worry if your phone hangs, give it a few minutes to do its thing. Mine lagged very bad as I flashed acid audio mod. Do not hit the home button or do anything to cause the app to exit.
9) Once flash gordon is done a notification will appear telling you to reboot - Click that notification and your device will reboot. If the app hangs at "Installing" give it a good 10 minutes and if it's still "Installing" just manual reboot. If your mod requires you to wipe the cache partition I reccomend booting to the stock 3e recovery by holding vol up + power + home and wiping it that way so you don't experience FC's from clearing cache while device is running.
10) Once device is powered on it should take you through that "Android upgrading" message and then you can enjoy your mod!
11) Optional: Throw money at/thank "Androguide.fr" for his awesome app.
Confirmed working:
Acid Audio Mod - Use the one here - V7 will bootloop you or cause a glitch where your device is "Upgrading applications" every boot
Going to try more later -- post a picture of your favorite mod/tweak running and I'll add it to this OP!
Thank you for posting this. I am sure it will help many Active users, but I wonder how long it will be before people ignore your warnings and try to flash a kernel or ROM or custom recovery with this?
Please people READ and READ some more so you don't mess up your phones. I don't know if it will do any good but maybe putting that part at the top in Red letters might help.
Again. thanks.
scott14719 said:
Thank you for posting this. I am sure it will help many Active users, but I wonder how long it will be before people ignore your warnings and try to flash a kernel or ROM or custom recovery with this?
Please people READ and READ some more so you don't mess up your phones. I don't know if it will do any good but maybe putting that part at the top in Red letters might help.
Again. thanks.
Click to expand...
Click to collapse
Thanks and done.
I am tempted to see if the following mod will work... http://forum.xda-developers.com/showthread.php?t=2320427
NVM the mod I would really love to see is this http://forum.xda-developers.com/showthread.php?t=2335635 anyone willing to try it out
joshuadjohnson22 said:
I am tempted to see if the following mod will work... http://forum.xda-developers.com/showthread.php?t=2320427
NVM the mod I would really love to see is this http://forum.xda-developers.com/showthread.php?t=2335635 anyone willing to try it out
Click to expand...
Click to collapse
I don't see why it wouldn't work. Just try it
thatbigmoose said:
I don't see why it wouldn't work. Just try it
Click to expand...
Click to collapse
Lol i really want to but I don't feel like re-setting up my phone if it messes up lol.
I have already rooted my parent's S4 Active and regular S4 and I did a lot of mods for them... Just tired of re-setting up my phone. Are you not interested in CM10.1 MMS? It rocks... one of the only stock messaging apps I would like to use all the time
joshuadjohnson22 said:
Lol i really want to but I don't feel like re-setting up my phone if it messes up lol.
I have already rooted my parent's S4 Active and regular S4 and I did a lot of mods for them... Just tired of re-setting up my phone. Are you not interested in CM10.1 MMS? It rocks... one of the only stock messaging apps I would like to use all the time
Click to expand...
Click to collapse
I did 3 Odin flashes today from messing with flash Gordon and trying to install acid audio
I made a bloat killer based off the one found here: http://forum.xda-developers.com/showthread.php?t=2250403
Kills all S-Apps including note, memo, browser, sync services, ATT updater, flipboard, facebook, Samsung stock file explorer, "Simple" launcher, Swype
Leaves allshare play and all the stuff with wifi-direct, all google apps, group play, mobile hotspot, Samsung stock video app, TW launcher, ChatON because that ****er is invincible, Samsung keyboard, all of the apps that looked vital that I couldn't be bothered toying around with
Use this at your own discretion, I could've ****ed up and deleted a bad file, but my system is running great. As usual I'm not responsible for bricks.
Here's a list of ALL the apps it takes care of:
Code:
delete("/system/app/wssyncmldm.apk");
delete("/system/app/wssyncmldm.odex");
delete("/system/app/YPMobile_ATT.apk");
delete("/system/app/YahoostockPhone2013.odex");
delete("/system/app/YahoostockPhone2013.apk");
delete("/system/app/YahoonewsPhone2013.odex");
delete("/system/app/YahoonewsPhone2013.apk");
delete("/system/app/wssyncmlnps.odex");
delete("/system/app/wssyncmlnps.apk");
delete("/system/app/wssyncmlds.odex");
delete("/system/app/wssyncmlds.apk");
delete("/system/app/wssyncmldm.odex");
delete("/system/app/WlanTest.odex");
delete("/system/app/WlanTest.apk");
delete("/system/app/TripAdvisor.apk");
delete("/system/app/TravelWidget.apk");
delete("/system/app/TravelService.odex");
delete("/system/app/TravelService.apk");
delete("/system/app/Telenav_ATT.apk");
delete("/system/app/Swype.apk");
delete("/system/app/S-Voice_Android_phone_J.apk");
delete("/system/app/StoryAlbumWidget.odex");
delete("/system/app/StoryAlbumWidget.apk");
delete("/system/app/SPlannerAppWidget_NAmerica.odex");
delete("/system/app/SPlannerAppWidget_NAmerica.apk");
delete("/system/app/SNoteProvider.odex");
delete("/system/app/SNoteProvider.apk");
delete("/system/app/SMemo2.odex");
delete("/system/app/SMemo2.apk");
delete("/system/app/SmartWifi_vpl_ATT.apk");
delete("/system/app/SHealth2.apk");
delete("/system/app/SecNoteMyFiles.apk");
delete("/system/app/sCloudSyncSNote.apk");
delete("/system/app/sCloudSyncSBrowserTabs.apk");
delete("/system/app/sCloudSyncSBrowserBookmark.apk");
delete("/system/app/sCloudSyncContacts.apk");
delete("/system/app/sCloudSyncCalendar.apk");
delete("/system/app/sCloudQuotaApp.apk");
delete("/system/app/sCloudDataSync.apk");
delete("/system/app/sCloudDataRelay.apk");
delete("/system/app/SBrowser.odex");
delete("/system/app/SBrowser.apk");
delete("/system/app/SamsungWidget_ProgramMonitor.odex");
delete("/system/app/SamsungWidget_ProgramMonitor.apk");
delete("/system/app/SamsungTTS.apk");
delete("/system/app/SamsungMusic.apk");
delete("/system/app/SamsungHubUpdater.apk");
delete("/system/app/SamsungHub.apk");
delete("/system/app/SamsungGames.apk");
delete("/system/app/S_Translator_CSLi.odex");
delete("/system/app/S_Translator_CSLi.apk");
delete("/system/app/PolarisOffice5.apk");
delete("/system/app/PageBuddyNotiSvc2.odex");
delete("/system/app/PageBuddyNotiSvc2.apk");
delete("/system/app/myATT_ATT.apk");
delete("/system/app/MusicPlayerWT.apk");
delete("/system/app/MobilePrintSvc_Samsung.apk");
delete("/system/app/MobilePrintSvc_HP.apk");
delete("/system/app/MobilePrintSvc_CUPS_Backend.apk");
delete("/system/app/MobilePrintSvc_CUPS.apk");
delete("/system/app/MobilePrint2.odex");
delete("/system/app/MobilePrint2.apk");
delete("/system/app/MMAppFramework.odex");
delete("/system/app/MMAppFramework.apk");
delete("/system/app/Match3VS.apk");
delete("/system/app/LiveTv_vpl_ATT.apk");
delete("/system/app/KNOXAgent.odex");
delete("/system/app/KNOXAgent.apk");
delete("/system/app/kieswifi.odex");
delete("/system/app/kieswifi.apk");
delete("/system/app/FamilyMap_vpl_ATT.apk");
delete("/system/app/EasyLauncher.odex");
delete("/system/app/EasyLauncher.apk");
delete("/system/app/EarCare.apk");
delete("/system/app/DriveMode_ATT.apk");
delete("/system/app/digitalLocker_ATT.apk");
delete("/system/app/Com2usPoker_ASGC.apk");
delete("/system/app/attMessages_vpl_ATT.apk");
delete("/system/app/AccuweatherPhone2013.apk");
delete("/system/app/AccuweatherPhone2013.odex");
delete("/system/app/ChatON_feature.apk");
delete("/system/app/Samsungservice.apk");
delete("/system/app/SecCalendar_NAmerica_SPen.apk");
delete("/system/app/SecCalendar_NAmerica_SPen.odex");
delete("/system/app/DioDict3Service.apk");
delete("/system/app/HealthContentProvider.apk");
delete("/system/app/CHS_J_Device_only.apk");
delete("/system/app/SamsungApps_J_Only.apk");
delete("/system/app/SamsungBooks.apk");
delete("/system/app/Flipboard.apk");
delete("/system/app/MusicLiveShare.apk");
This is sweet, big props to the developer on this one. Gonna play with this more tomorrow.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
joshuadjohnson22 said:
I am tempted to see if the following mod will work... http://forum.xda-developers.com/showthread.php?t=2320427
NVM the mod I would really love to see is this http://forum.xda-developers.com/showthread.php?t=2335635 anyone willing to try it out
Click to expand...
Click to collapse
It doesnt even let me flash it. It keep saying "the package is not a flashable zip"
tisaznpimp said:
It doesnt even let me flash it. It keep saying "the package is not a flashable zip"
Click to expand...
Click to collapse
Try installing busybox?
Just search "busybox" on the market.
thatbigmoose said:
Try installing busybox?
Just search "busybox" on the market.
Click to expand...
Click to collapse
Also doesnt work, says the same error.
just to be sure... you did run the busybox installer after you installed it, correct? Both BusyBox apps are just installers. You have to run them and tell them to perform the actual install.
I just tried flashing CM 10.1 with this and now my phone's bricked. Wtf man
aturbs said:
I just tried flashing CM 10.1 with this and now my phone's bricked. Wtf man
Click to expand...
Click to collapse
You have to be trolling. If so, I hope you get banned.
aturbs said:
I just tried flashing CM 10.1 with this and now my phone's bricked. Wtf man
Click to expand...
Click to collapse
Yeah at the very most you softbricked your phone. Which probably means you flashed the wrong zip for the mms. Just odin your phone back...
How can we edit this to keep any apps we want? Thanks !
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
rhkean said:
just to be sure... you did run the busybox installer after you installed it, correct? Both BusyBox apps are just installers. You have to run them and tell them to perform the actual install.
Click to expand...
Click to collapse
awesome, thanks for the info. I successfully flash it. Thank you so much. =))
tisaznpimp said:
awesome, thanks for the info. I successfully flash it. Thank you so much. =))
Click to expand...
Click to collapse
Did you install cm10.1 mms? If so which zip files did you install? Is everything working?
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4 Beta
joshuadjohnson22 said:
Did you install cm10.1 mms? If so which zip files did you install? Is everything working?
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I flashed the one from here: http://forum.xda-developers.com/showthread.php?t=2335635
Make sure you use the 'Pre-MEA_AOSP_MMS_CPA-Poke-v2.zip'. Reboot phone and go to system/app with root explorer and rename KeyguardWidget.apk to KeyguardWidget.apk.bak. Done.
Everything, including both sms/mms works perfectly. You can even theme the conversation list and messages with custom background and different test color. I included screenshot to show you what I meant. =)
attached:
[Q&A] [ROM]【5.0】Google Play Edition 【LRX219】 - 12-24-201
Q&A for [ROM]【5.0】Google Play Edition 【LRX219】 - 12-24-2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM]【5.0】Google Play Edition 【LRX219】 - 12-24-2014. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Screen turns off during call, won't turn back on
This is the first rom I've installed in a while and this is also the first rom installed after rooting.
I am using the SPH-L720 on NG2
After flashed this rom and the sprint framework, whenever I make a call the screen shuts off, like it's supposed to.
My problem is that the screen won't turn back on.
Power button, home button, tapping the screen, nothing seems to work.
Am I the only one with this issue?
Is there a fix out there for this or should I just try and reflash?
Great rom. Stable and have found no bugs since the release. Is there a way to infinite scroll the homescreen and apps panel? And also.. I saw some mention about build.prop edits for the model but didnt see a difinitive answer. Is there a way to change it to sph-l720? It doesnt make anything not work but it takes the rom from perfect to almost perfect lol. Anyway thanks dev!
I'm also getting the no sim card error, on top of that I am unable to connect to LTE. I have flashed this rom three times with full wipes in between. installed the sprint framework. I have LTE on other ROMS. Is anyone else having this issue?
It rocks
Best rom i've tried in a while. Battery lasts about 2 days for me, great performance, no glitches found so far.
Little question, under Developer options, I can't seem to find the advanced reboot options menu. I know there is one under interface > Reboot options, but that one reboots right away and I want it on the menu while clicking the power buttom.
Thank you developers for this awesome rom.
Battery Life
Can someone post screenshots of this ROM's battery life? I have an SPH-L720, and I am trying to decide if I should wait for the TouchWiz 5.0 Samsung Update.
GSM on Samsung Sprint S4
I like to try this ROM, I'm not using CDMA with this phone,, will the GSM works well with this ROM? Thank You,,
RedRover88 said:
Can someone post screenshots of this ROM's battery life? I have an SPH-L720, and I am trying to decide if I should wait for the TouchWiz 5.0 Samsung Update.
Click to expand...
Click to collapse
You will be waiting awhile for the tw 5.0. Battery life is decent. Better then Kk for me at least
ojaNNajo said:
I like to try this ROM, I'm not using CDMA with this phone,, will the GSM works well with this ROM? Thank You,,
Click to expand...
Click to collapse
I would think it would since there are all these options
{
"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"
}
Proximity Sensor
Nevermind, it was a problem with my proximity sensor. I edited build.prop to disable it and it works now.
jtheone said:
This is the first rom I've installed in a while and this is also the first rom installed after rooting.
I am using the SPH-L720 on NG2
After flashed this rom and the sprint framework, whenever I make a call the screen shuts off, like it's supposed to.
My problem is that the screen won't turn back on.
Power button, home button, tapping the screen, nothing seems to work.
Am I the only one with this issue?
Is there a fix out there for this or should I just try and reflash?
Click to expand...
Click to collapse
Pretty much everything working fine here. I love the ROM. My only issues are the following:
I had to turn on LTE in the settings and reboot the phone before it would connect to LTE, but it does fine now.
I'm also getting the NO SIM CARD on lock screen issue as someone else reported, but LTE wouldn't work at all if it really had no SIM card.
The other more major issue I have is that I can't mount folders to the storage/emulated/0/Android/obb folder. A lot of games keep huge files in that folder, so I like to keep those files on my SD card and link them to that folder. I couldn't use FolderMount or create symbolic links just to that obb folder,while other folders link just fine. I tried a lot of different things, but nothing lets me link/mount properly inside this ROM's obb folder. Reading through the FolderMount support thread, I found this: h**p://www.devasque.com/foldermount/kk-support.html They said to have my kernel dev (or ROM cooker) look there, and I believe that is now you
Thanks for putting this all together! Still a great DD even without mounting to the obb folder.
Nahaff said:
Pretty much everything working fine here. I love the ROM. My only issues are the following:
I had to turn on LTE in the settings and reboot the phone before it would connect to LTE, but it does fine now.
I'm also getting the NO SIM CARD on lock screen issue as someone else reported, but LTE wouldn't work at all if it really had no SIM card.
The other more major issue I have is that I can't mount folders to the storage/emulated/0/Android/obb folder. A lot of games keep huge files in that folder, so I like to keep those files on my SD card and link them to that folder. I couldn't use FolderMount or create symbolic links just to that obb folder,while other folders link just fine. I tried a lot of different things, but nothing lets me link/mount properly inside this ROM's obb folder. Reading through the FolderMount support thread, I found this: h**p://www.devasque.com/foldermount/kk-support.html They said to have my kernel dev (or ROM cooker) look there, and I believe that is now you
Thanks for putting this all together! Still a great DD even without mounting to the obb folder.
Click to expand...
Click to collapse
Make sure you have this one ticked for the NO SIM CARD issue
Then you'll see this
elwood said:
Make sure you have this one ticked for the NO SIM CARD issue
Click to expand...
Click to collapse
That's working now. Thanks! Strange part was it kept reverting back to the top after setting it and leaving the screen. I had to switch to the second from the top first.
Nahaff said:
That's working now. Thanks! Strange part was it kept reverting back to the top after setting it and leaving the screen. I had to switch to the second from the top first.
Click to expand...
Click to collapse
Same issue I had. Kept reverting back to the top selection. Glad it's working for you
Phantom Voicemail Icon
Anyway of getting the Phantom Voicemail Icon to go away? Says I have two voicemail which i dont.
xCyberOxide said:
Anyway of getting the Phantom Voicemail Icon to go away? Says I have two voicemail which i dont.
Click to expand...
Click to collapse
Maybe long press on the notification then tap the app info on the right and check block notifications. I haven't had the Phantom VM but I know when I was on an older Kitkat Rom it did the trick
elwood said:
Same issue I had. Kept reverting back to the top selection. Glad it's working for you
Click to expand...
Click to collapse
I found out it goes back after every reboot. I just change it to the second option and then the third after every reboot and I'm good.
Google Play Movies & TV
Every time I try to play a movie or tv episode I get "There was an error". Anyone else getting this issue? Anyone know of a fix?
---------- Post added at 07:00 AM ---------- Previous post was at 06:52 AM ----------
elwood said:
Maybe long press on the notification then tap the app info on the right and check block notifications. I haven't had the Phantom VM but I know when I was on an older Kitkat Rom it did the trick
Click to expand...
Click to collapse
Yeah...thats just an annoying temporary solution.
How to Return to Stock?
I want to try this on my SPH-L720 Samsung Galaxy S4 Sprint phone currently running 4.4.2 Stock TouchWiz Firmware. Can someone point me in the right direction how to get back to Stock after flashing a custom ROM like this? I want to be able to return to my phone's former state, meaning I can get OTA updates when Samsung releases 5.0, no root permissions, and no triangle upon booting. I've done ROM flashing on the S2, but I've read many comments with others having problems going back on the S4. I think those problems are with the AT&T and T-Mobile models, yet I am new to this and want to play it safe. Here's what I've found: qbking77. com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4/ Thanks!
Model number incorrect
I followed the instructions exactly, and I do have Sprint network access, so this may just be a minor thing, but my model number is showing as GT-I9505G instead of the SPH-L720. Is there a way to fix this? I tried using the suggested XML file and putting it in the data folder and rebooting but no dice there, either.
billknust said:
I followed the instructions exactly, and I do have Sprint network access, so this may just be a minor thing, but my model number is showing as GT-I9505G instead of the SPH-L720. Is there a way to fix this? I tried using the suggested XML file and putting it in the data folder and rebooting but no dice there, either.
Click to expand...
Click to collapse
Edit build prop. The eri.xml file was just for framework.
Update: Successfully working atm, survives a hard reboot.
Status: In testing
{
"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"
}
Congrats!! Hard work surely pays off.
Thanks bud. I'm gonna run it for a bit and make sure there isn't any issue that are gonna come about but I doubt it. I could release a IMG out also for people to flash, but I removed a ton of apps I don't ever use, but unsure about the user who will download it.
Sent from my XT1254 using XDA Free mobile app
savagebunny said:
Thanks bud. I'm gonna run it for a bit and make sure there isn't any issue that are gonna come about but I doubt it. I could release a IMG out also for people to flash, but I removed a ton of apps I don't ever use, but unsure about the user who will download it.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah run it all this weekend and hopefully all is well. Dont hesitate About making the IMG but just specify which apps you have removed and what not beforehand on the op when you make the post. Remember there are all types of users out there so don't question who would be interested dont question that who would be interested.
wadamean said:
Yeah run it all this weekend and hopefully all is well. Dont hesitate About making the IMG but just specify which apps you have removed and what not beforehand on the op when you make the post. Remember there are all types of users out there so don't question who would be interested dont question that who would be interested.
Click to expand...
Click to collapse
Well.. Right when I thought I got it, already ran into a issue. What I did BEFORE was I made sure was the V4A .apk in priv-app had 0755 permissions. I installed the driver and worked, but then i did a SOFT reboot. Driver was successful and no issue. I just now did a hard reboot, and the driver gets uninstalled, and the permissions get set to 0666. Whats weird though is in the img in linux, I made sure priv-app folder is 0755 and I just checked and V4A apk is 0755 in the image. Some how along the line it gets changed to 0666 by the system.
tl;dr only way for it to work is set apk to 0755 via root browser, install driver, Do a soft reboot and it works. Doesn't survive hard reboot. unsure why
savagebunny said:
Well.. Right when I thought I got it, already ran into a issue. What I did BEFORE was I made sure was the V4A .apk in priv-app had 0755 permissions. I installed the driver and worked, but then i did a SOFT reboot. Driver was successful and no issue. I just now did a hard reboot, and the driver gets uninstalled, and the permissions get set to 0666. Whats weird though is in the img in linux, I made sure priv-app folder is 0755 and I just checked and V4A apk is 0755 in the image. Some how along the line it gets changed to 0666 by the system.
tl;dr only way for it to work is set apk to 0755 via root browser, install driver, Do a soft reboot and it works. Doesn't survive hard reboot. unsure why
Click to expand...
Click to collapse
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Edit: looks like you may have to add some lines to the build.prop as well
viper
brennam7 said:
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Click to expand...
Click to collapse
hello. am a lover viper. I had on other cell. there is a way to install without root on droid turbo? thank you. greetings: P
brennam7 said:
Figure out where the apk installs the driver and manually insert the driver in that location with the proper permissions in the IMG then flash. Should work then I'd think
Edit: looks like you may have to add some lines to the build.prop as well
Click to expand...
Click to collapse
Ya I'm thinking that too. It's a new day so I'm gonna start digging into it today and see what's up. The only down fall is that I gotta keep sending over that 3.5GB img each time which takes a lot of time into work.
Already added the lines to build.prop also. There may be a few extra ones that could be lingering
pialletti said:
hello. am a lover viper. I had on other cell. there is a way to install without root on droid turbo? thank you. greetings: P
Click to expand...
Click to collapse
Nope, gotta have root due to dependencies needed by the V4A and various other files that need to be written in /system/
Sign me up!
Sent from my XT1254 using XDA Free mobile app
Hello guys, I may have figured out the issue. In V4A options, we can choose High Quality (HQ) and Super High Quality (SQ). From what I've read SQ doesn't use too much battery more than HQ, and we are using quite a powerful CPU. Should I make a image with HQ or SQ driver installed?
savagebunny said:
Hello guys, I may have figured out the issue. In V4A options, we can choose High Quality (HQ) and Super High Quality (SQ). From what I've read SQ doesn't use too much battery more than HQ, and we are using quite a powerful CPU. Should I make a image with HQ or SQ driver installed?
Click to expand...
Click to collapse
SQ! Did you get it figured out so that it survives a reboot?
PerCompLLC said:
SQ! Did you get it figured out so that it survives a reboot?
Click to expand...
Click to collapse
I'm gonna find out once the image flashes over. I'm crossing my fingers I figured it out... only can hope. I'll update this post if it survives a hard reboot
EDIT: Nope, didn't stick. Now during a soft-reboot it doesn't even work now.. Man this is a struggle
Quick updated, with some mind boosting affect from computerfreek274, I was digging into V4A why it wouldn't stay after hard reboot. I've done 3 hard reboots so far and the driver is sticking without the driver install loop. Can't believe it's taken me this long, but its finally done
Have computerfreek274 add it to the IMG he's been uploading! Could be a fantastic addition! Congrats on getting it to work. No better feeling in the world
JakeDHS07 said:
Have computerfreek274 add it to the IMG he's been uploading! Could be a fantastic addition! Congrats on getting it to work. No better feeling in the world
Click to expand...
Click to collapse
Ya me and him have been talking about it. He is in testing phase atm also
Sent from my XT1254 using XDA Free mobile app
savagebunny said:
Ya me and him have been talking about it. He is in testing phase atm also
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Awesome thanks for your work
@savagebunny It sucks how long it takes to flash each time you need to test something. I hope one day we get an unlocked boot loader and some custom recovery so we can just flash shot as we need it.
Thanks @savagebunny for keeping me going this. I am testing now the changes we just talked about we will see if it works. I also did the same things but when I do a full clean wipe and flash it asked for the driver. I am doing a clean and wipe and fresh install if all works good I will post 1.5.2a with ad blocking and V4A.
Thanks buddy now we will need to work on something new after this. lol.
PS 46% like wet paint.
Ya I feel ya. Made some good progress, although it took us longer than usual, seems like there is only a handful of us working on things. Like you said, gotta think of something else good to bake into the images until we get unlocked boot-loader and we can flash all day
I seen a lot of Discussion On this topic, and found a really simple way to disable Forced Encryption and it also removes the warning at boot. This in NO WAY is my work at all. I am sharing this [FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher) which was posted by @gladiac. Absolutely make sure you head over to his forum and hit the Thanks button. This works great
Screenshots Below
I have the option to encrypt the phone as you can see circled. I went into system with Root Explorer and was prompted for R/W access and obviously I granted it. Everything is working great!
{
"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"
}
Preparation
Before proceeding, enable Developer options and MAKE SURE USB DEBUGGING IS ENABLED!!!
1. Download fed_patcher_v7-signed.zip and check here to verify the latest version
2. Download [BETA][2015.10.10] SuperSU v2.52 by @Chainfire
3. Download Whatever ROM you are going to use. I am currently running [ROM]【6.0】LightROM - Marshmallow【MRA58K】- 10/08/15
Instructions
1. Backup your SD Card, during this process, everything will be erased during the process
2. Reboot into TWRP, this is important that you actually have TWRP
3. Perform a Full Wipe by doing the following:
Press Wipe
[*] Press Advanced
[*] Click every check Box
[*] Wipe 3x for good measure
[*] Press Home button
[*] Press Wipe
[*] Press Format Data
[*] Type yes in the box to perform the format
[*] Perform this 3x for a good full wipe
4. Reboot TWRP (Do Not Install Super Su Yet)
5. Once Back In Recovery, On the computer, open My computer
6. Navigate to and open the Nexus 6 Drive
7. Drag the Zip files below to your Phone -
1) fed_patcher_v7-signed.zip
2) BETA-SuperSU-v2.50.zip
3) ROM Zip
If You are Having Trouble, take a look at the screen shots below
You Want to make sure you mount data if it is not, and make sure MTP is not disabled! Thanks @jamiejames and @aliasferno
8. Flash your ROM 1st (DO NOT BOOT AFTER FLASHING)
9. Wipe Dalvick Cache/Cache 3x
10. Flash fed_patcher_v7-signed.zip
11. Wipe Dalvick Cache/Cache 3x
12. Flash BETA-SuperSU-v2.52.zip
13. Reboot and Enjoy with no more red error sign during boot and no encryptionhttps://source.android.com/devices/tech/security/verifiedboot/verified-boot.html#user_experience
Supported Devices
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
[*]v2 - Added Motorola Nexus 6 (shamu) support
[*]v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
[*]v4 - Added support for signed boot-images
[*]v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
[*]v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
[*]v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What Do I need To Make This Work?
A supported device (Your nexus 6)
[*]An unlocked bootloader
[*]An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
[*]A recovery that includes busybox (TWRP, CWM)
How Do I Use it?
Follow Instructions above - This is the basic need to know information
[*]Make a thorough, conservative backup of your data if there is any on your device
[*]Go into your recovery (TWRP, CWM)
[*]Flash fed_patcher-signed.zip
[*]If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is It Dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
All Thanks To:
@gladiac - For Putting the OP together for the Nexus 9 and sharing this
[*]@rovo89 - for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
[*]@pbatard - for making (un)mkbootimg (dunno if he is on xda)
good work mate
Danvdh said:
good work mate
Click to expand...
Click to collapse
Thanks Bro...Thanks for the ROM, I saw it's already updating. Thanks
Thanks for this! :good:
Herk718 said:
Thanks for this! :good:
Click to expand...
Click to collapse
No Problem...
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
TY you for this info. Exactly what I was looking for. Thanks a milion
spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I am decrypted, I have super user ...I was able to restore with titanium backup, I will see if I can edit the build.prop or just mount rw
edit: I was able to mount rw successfully in root explorer no issues
simunovic said:
TY you for this info. Exactly what I was looking for. Thanks a milion
Click to expand...
Click to collapse
No problem
Sent from my Nexus 6 using Tapatalk
spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me
bdorr1105 said:
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me
Click to expand...
Click to collapse
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose
spunks3 said:
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose
Click to expand...
Click to collapse
It won't work unless you remove root
Sent from my Nexus 6 using Tapatalk
Moved this from the development forum as there is no development, this is not your work, and it is a guide for this; this is better suited to a General forum.
Thread reopened on the basis that this is a guided collection of work.
Ok, this OP is more of a guide on how to use this tool, I am going to edit the OP and redirect it to the Forum that was in the Nexus 6...There was a mis-understanding on my part, I did not realize this was in the Nexus 6 Android Development already, this is just how to run it, and the steps to successfully flash and get rid of the warning before booting Android 6.0 and having a force decrypted set up form boot...
bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse
atrix4nag said:
bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse
bdorr1105 said:
atrix4nag said:
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse
atrix4nag said:
bdorr1105 said:
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse
I do not have the warning at boot doing this method. So yes, you should no longer have the warning
Click to expand...
Click to collapse
If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.
Hucklebury said:
If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.
Click to expand...
Click to collapse
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again
bdorr1105 said:
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again
Click to expand...
Click to collapse
ok, thanks for the reply. i have tried many times to get rid of that ugly screen without success, ended up going completely stock M.