Hello all!
i'm new to the Droid X, but a long time windows mobile phone user. so, i'm a bit lost on trouble-shooting the android os.
my phone came with 2.3.151 installed. i overclocked with jrummy16's overclock program, rooted with z4root, and installed bootstrap recovery program. at this point in time....all was well. phone dialer application worked fine.
then...OTA upgrade to 2.3.340...everything i checked worked just as before upgrade. the only broken app was the phone dialer. when launched, the screen goes black for a second or two, then the home screen re-appears, and an alert sound is made. also, iin the task bar/title bar at the top of the screen, where the signal strength bars are displayed...this is replaced with a circle with a line through it (the "not" symbol).
fortunately for me, before the OTA upgrade, i had done a bootstrap backup. so when the dialer stopped working, i did a bootstrap recovery advanced restore and restored only the "system" from the 2.3.151 backup.
when it was done, again, everything i checked was working fine AND now the phone dialer application launches normal also.
i decided to experiment. i used bootstrap recovery to restore the "system" only from a 2.3.340 backup i had made immediately after the OTA upgrade. the phone dialer failed to work as i described above.
so, to fix this, i downloaded a dialer app from the "Market" and it works fine. so at this point i have no issue EXCEPT i want to know what happened to the phone dialer when the 2.3.340 upgrade is applied?????
has anyone else seen this behavior? does anyone have any ideas?
Marvin
UPDATE:
so after some experimenting, i have found the problem...i think. at least i can reproduce the problem and fix it 100% of the time.
it appears that 2.3.340 build.prop sets the lcd to 200. 2.3.151 sets it to 240.
i know this because i explored the Droid X/2 overclock utility's "extra" features and did the "get current LCD setting" and 240 was displayed in a text message.
when the OTA 2.3.340 was done, i ran the overclock utility and did a get current setting and 200 was displayed.
so, with .340 installed, and the phone dialer NOT working, i changed the lcd to 240, the phone rebooted, and yep-you guesssed it, the phone dialer app worked just fine. i reset the lcd to 200 and the dialer won't work.
i restored a 2.3.151 backup, ran the overclocker utility, set the lcd to 200 and the dialer won't work. reset it to 240, and it works.
seems to me that the OTA .340 broke the phone dialer by changing the lcd density. or is it just my phone?
has anyone else experienced this?
marvin
It is not just your phone. LCD density and the dialer are a known issue. If you keep up with the custom rom threads it is mentioned several times. You need to keep the LCD density set to stock.
If I understand you correctly though you are saying that you thought your setting were stock and wouldn't work?
I would search around the forums and see what the stock settings are. Just to let you know - my build prop says 240 for the lcd density and the dialer works.
hope that helps.
*edit I am pretty sure that 240 is stock and the .340 update build prop sets it to 240. I am not sure what happened in your case.
Related
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
lwright84 said:
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
Click to expand...
Click to collapse
I think you might be overreacting here.
First, I haven't flashed the SBF yet but I do remember seeing the fail screen on original Droid SBF flashes and it was something you could ignore. You booted back into Android, right? That means it worked.
Second, the Superuser app is supposed to show a blank screen because the purpose of it to manage apps to which you have granted to superuser permissions. If you just installed it, there would be nothing listed.
Third, Froyo restores apps if you have "back up my data" checked under Privacy settings.
Fourth, you never mentioned the Droid 2 bootstrapper. I wouldn't expect ROM Manager to work properly without it.
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
lwright84 said:
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
Click to expand...
Click to collapse
Captivate is not a Droid 2. I'd be surprised if it works without the bootstrapper, since that's the only way to flash anything on a Droid 2.
My suggestion is to keep trying the SBF. Once you get it to work, get the SW update and then root. From there, I wouldn't go messing with anything in ROM Manager until you confirm the files are 100% legit for the Droid 2. As far as I know, only a few themes are working without issue on the Droid 2 - the ROMs all have bugs.
The same thing happened to me. I am assuming we were using the same instructions to flash the .sbf. Here is a link to instructions I followed.
http://forum.xda-developers.com/showthread.php?p=8245826#post8245826
I did not heed the red flag I got when I unzipped the .jpg file. I saw some error message and ignored it, and went ahead with the procedure to end up as many others with "fail".
Long story short, I deleated the .jpg file and downloaded it again.
When I used 7 Zip to extract the files, this time I had no error msg and everything went smoothly.
Well, I did it.
Unrooted my nook (turned off, turned on pressing both lower side buttons, cleared everything, logged in, deregistered, logged in again), installed update (went fine) and rerooted (using touchnooter 1.6.24).
Launcher is working, button saviour too, but I can't get market to download anything at all... I wanted to use astro file manager to sideload a newer version of the market, but no success at all. But wifi is working fine with standard browser. I'll try to adb the market apk later...
And the Serial Number for my nook went to 00000000000!
I hope I can get myself out of this mess.
Updaters beware!
Thanks for sharing! hmmm, definitely sounds like it brings more issues than it solves so far...
Well, SN is back again, but still nothing on market.
Is there a way to do the touchnooter with the newer version of the market?
And maybe include the ad-hoc hack would be good!
Update is OK
Hi, I updated my Nook Touch twice due to some glitches when I did a backup. I don't have any problem at all. Everything is fine, including market.
Droid X
Android: 2.3.4
System Version: 4.5.621.MB810.Verizon.en.US
I've tried both the direct root method for .621 and the one referred to as "flashing a Milestone X .604 image" (not allowed to link to the post...)
Neither work but I think it's something to do with this phone. It seems to restore itself at each reboot. For example I clear the call log in dialer, reboot, and it's populated again. If I enable USB debugging and reboot, it goes back to disabled. Uninstall an app, reboot and it's back. I don't see any software running other than the verizon backup assistant so I don't think there is installed anything that would be causing this. I should also mention that even doing a factory reset has no effect. It reboots to the bootloader at which point wiping data/cache report success but make no actual changes to the phone. Call log, contacts, apps, they all remain unaffected. Has anyone seen anything like this? Suggestions?
Bump please.
Hi Guys
Just joined the forums yesterday. I was enjoying tinkering with my S4, I rooted it and had some fun with it, installing cool apps and such like.
I downloaded titanium back up, and proceeded to remove (what I thought was) bloatware..... (yes...schoolboy error, I know) I didn't remove any crucial system files though, I aint that gung-ho. But what I did do, was remove Flip-Fonts (I didn't know that the little "f-f logo in the circle" was flipfonts.
Anyway, this was still ok. I downloaded a font app from the play store, and installed a new font. I deliberately chose a font that was annoying to look at, and barely legible, simply so I could instantly see that the install had worked. So I rebooted my S4, and when it booted up, I noticed immediately that it had worked. Thus I knew the install proocess was working, and then I chose the font I wanted to install. BRILLIANT!!!
Then I noticed the issue. My system fonts were ok, however, when I was surfing the web, it was still using the annoying, barley legible font I initially installed as a tester. Gmail was using it, yahoo, chrome. I tried to uninstall and change the font. I could change it, but again, the fonts in gmsail etc were the annoying one that I didn't want. I could see no way to change this. So I did a factory restore this morning, through the normal channels (setting/accounts/back-up and reset) thinking this would reset.
When I booted the phone back up, when I was guided through the initial phone set up tutorial (time, accounts, device name etc ect) I noticed that the system font was set as the annoying one I don't want. So I downloaded iFont, and changed it. Again, it changed the font to the one I wanted, but again, when I went online it was still that (by this time) INCREDIBLY ANNOYING FONT!!!
So I went in to SuperSU and chose to unroot the device. I then went through the root process I initially used I re-rooted using this method. Again, when I booted up, the initial set-up wizard that guides you through had that IRRITATING, PESKY, SUICIDAL FONT!!!
So my good android friends, I require your assistance. How do I get round this pesky issue? I was thinking I would have to roll back to the factory ROM? Or is there some simple setting I am missing This is really really getting to me now. I have been tikering with the fone, not too in depth may I add, just installnig root apps and such. I was willing to venture in to the custom ROM's avenue sometime soon.....although after this little episode, I may think twice.
I do not have a nandroid back up. I have been advised on another forum to reinstall the factory ROM. However, I know there are different methods for different versions. So below is the info from my device. Whats the best plan of action for me. I still want to root my phone again, I just want shot of this annoying font.
In About Device:
Model Number: GT I9505
Android Version: 4.2.2
Baseband Version: I9505XXUDMH8
kernel Version: 3.4.0-1220396 Then below it says se.infra @0210-03 1
(or something like that. I can hardly read it because of that annoying font)
Build Number: JDQ39.19505XXUDMH8
And i'm in the UK. my carrier/service provider is O2
Please Help!!!!!!! :crying:
bullitproofmunk said:
Hi Guys
Just joined the forums yesterday. I was enjoying tinkering with my S4, I rooted it and had some fun with it, installing cool apps and such like.
I downloaded titanium back up, and proceeded to remove (what I thought was) bloatware..... (yes...schoolboy error, I know) I didn't remove any crucial system files though, I aint that gung-ho. But what I did do, was remove Flip-Fonts (I didn't know that the little "f-f logo in the circle" was flipfonts.
Anyway, this was still ok. I downloaded a font app from the play store, and installed a new font. I deliberately chose a font that was annoying to look at, and barely legible, simply so I could instantly see that the install had worked. So I rebooted my S4, and when it booted up, I noticed immediately that it had worked. Thus I knew the install proocess was working, and then I chose the font I wanted to install. BRILLIANT!!!
Then I noticed the issue. My system fonts were ok, however, when I was surfing the web, it was still using the annoying, barley legible font I initially installed as a tester. Gmail was using it, yahoo, chrome. I tried to uninstall and change the font. I could change it, but again, the fonts in gmsail etc were the annoying one that I didn't want. I could see no way to change this. So I did a factory restore this morning, through the normal channels (setting/accounts/back-up and reset) thinking this would reset.
When I booted the phone back up, when I was guided through the initial phone set up tutorial (time, accounts, device name etc ect) I noticed that the system font was set as the annoying one I don't want. So I downloaded iFont, and changed it. Again, it changed the font to the one I wanted, but again, when I went online it was still that (by this time) INCREDIBLY ANNOYING FONT!!!
So I went in to SuperSU and chose to unroot the device. I then went through the root process I initially used I re-rooted using this method. Again, when I booted up, the initial set-up wizard that guides you through had that IRRITATING, PESKY, SUICIDAL FONT!!!
So my good android friends, I require your assistance. How do I get round this pesky issue? I was thinking I would have to roll back to the factory ROM? Or is there some simple setting I am missing This is really really getting to me now. I have been tikering with the fone, not too in depth may I add, just installnig root apps and such. I was willing to venture in to the custom ROM's avenue sometime soon.....although after this little episode, I may think twice.
I do not have a nandroid back up. I have been advised on another forum to reinstall the factory ROM. However, I know there are different methods for different versions. So below is the info from my device. Whats the best plan of action for me. I still want to root my phone again, I just want shot of this annoying font.
In About Device:
Model Number: GT I9505
Android Version: 4.2.2
Baseband Version: I9505XXUDMH8
kernel Version: 3.4.0-1220396 Then below it says se.infra @0210-03 1
(or something like that. I can hardly read it because of that annoying font)
Build Number: JDQ39.19505XXUDMH8
And i'm in the UK. my carrier/service provider is O2
Please Help!!!!!!! :crying:
Click to expand...
Click to collapse
Have you tried looking for your firmware here and restoring via odin?
bullitproofmunk said:
Hi Guys
Just joined the forums yesterday. I was enjoying tinkering with my S4, I rooted it and had some fun with it, installing cool apps and such like.
I downloaded titanium back up, and proceeded to remove (what I thought was) bloatware..... (yes...schoolboy error, I know) I didn't remove any crucial system files though, I aint that gung-ho. But what I did do, was remove Flip-Fonts (I didn't know that the little "f-f logo in the circle" was flipfonts.
Anyway, this was still ok. I downloaded a font app from the play store, and installed a new font. I deliberately chose a font that was annoying to look at, and barely legible, simply so I could instantly see that the install had worked. So I rebooted my S4, and when it booted up, I noticed immediately that it had worked. Thus I knew the install proocess was working, and then I chose the font I wanted to install. BRILLIANT!!!
Then I noticed the issue. My system fonts were ok, however, when I was surfing the web, it was still using the annoying, barley legible font I initially installed as a tester. Gmail was using it, yahoo, chrome. I tried to uninstall and change the font. I could change it, but again, the fonts in gmsail etc were the annoying one that I didn't want. I could see no way to change this. So I did a factory restore this morning, through the normal channels (setting/accounts/back-up and reset) thinking this would reset.
When I booted the phone back up, when I was guided through the initial phone set up tutorial (time, accounts, device name etc ect) I noticed that the system font was set as the annoying one I don't want. So I downloaded iFont, and changed it. Again, it changed the font to the one I wanted, but again, when I went online it was still that (by this time) INCREDIBLY ANNOYING FONT!!!
So I went in to SuperSU and chose to unroot the device. I then went through the root process I initially used I re-rooted using this method. Again, when I booted up, the initial set-up wizard that guides you through had that IRRITATING, PESKY, SUICIDAL FONT!!!
So my good android friends, I require your assistance. How do I get round this pesky issue? I was thinking I would have to roll back to the factory ROM? Or is there some simple setting I am missing This is really really getting to me now. I have been tikering with the fone, not too in depth may I add, just installnig root apps and such. I was willing to venture in to the custom ROM's avenue sometime soon.....although after this little episode, I may think twice.
I do not have a nandroid back up. I have been advised on another forum to reinstall the factory ROM. However, I know there are different methods for different versions. So below is the info from my device. Whats the best plan of action for me. I still want to root my phone again, I just want shot of this annoying font.
In About Device:
Model Number: GT I9505
Android Version: 4.2.2
Baseband Version: I9505XXUDMH8
kernel Version: 3.4.0-1220396 Then below it says se.infra @0210-03 1
(or something like that. I can hardly read it because of that annoying font)
Build Number: JDQ39.19505XXUDMH8
And i'm in the UK. my carrier/service provider is O2
Please Help!!!!!!! :crying:
Click to expand...
Click to collapse
As the other guy suggested, but instead of using that link, try http://www.samfirmware.com type in GT-I9505 into the device search bar and find United Kingdom (o2).
Flash it using Odin and you should be all good! I'd also recommend you take care when messing about with your phone, especially with system files. I would also recommend you flash a custom recovery such as TWRP and make backups of your device. It's saved me a load of times already!
Just wipe, flash new rom (stock rom or any rom you want). As long as you don't do anything crazy you can always use download mode to flash roms.
Howdy,
I got a new Note 4 from Bell Mobility about a month ago...
I updated the software, rooted it and installed the Wanam modified Xposed framework.
I have lost the automatic rotation, except for the built in camera software. Nothing else will auto-rotate. Checked the gyroscope and checked a few 'leveler' applications - all tests pass. Oddly I noticed the camera software still auto-rotates, no idea why it is special.
I tried the Wanam Xposed module to 'Enable all rotation angles' it has made no difference. With screen rotation software, currently have "Rotation - Orientation Manager by Pranav Pandey" installed. Auto-Rotate On and Forced Auto-Rotate neither option will rotate the screen when I turn my phone. If I choose Forced Landscape, it will go into Landscape mode. The only way to return to Portrait though is to use one of the Force Portrait options though.
My other issue is with turning on Device Encryption... Using SuperSU Pro for su..
If I just go through the prompts without changing anything, it reboots but doesn't encrypt.
First I tried installing as a system app so I could use the Disable function in the Android Application Manager, as I did with my Note 2, SuperSU tells me "Not (currently) available in system-less root mode".
If I turn off "Enable Superuser" in SuperSU, encryption enables properly, but I am unable to turn the "Enable Superuser" again, it says it has to update, but the fails. Suggests a reboot and try again. Sadly, this did not help.
I had success with one of the exploit root methods, KingRoot. While this worked when my phone was encrypted, it wasn't stable and kept popping up stuff. I tried to replace it with SuperSU, there are a few guides written to do just that, but they all indicate that it is very hard to get rid of, regardless, none of the guides worked for me. I ended up resetting the phone and starting over...
I tried the CLI command to start the device encryption from a # prompt..
vdc cryptfs enablecrypto inplace password 1234567890abcdef
The phone rebooted a couple times, but took a very long time (hour plus) to come back to the Android Lock-Screen.. But still a non-encrypted device. If I intrupted the process because I thought it had crashed, it started up and immediately told me something when wrong with the encryption and I need to use Recovery to reset the device..
As for root methods, I was using the CF-Auto-Root at first, trying to look for solutions to both issues, I tried a few ways of getting SuperSU installed.. The last time I reset I tried the "SkipSoft Unified Android Toolkit" method. 'Grasping at straws' to get SuperSU installed into /system so can use the Applicaiton Manager to disable and enable it...
My mobile's specifics, if it matters..
Samsung Galaxy Note 4
Model number - SM-N910W8
Android Version 5.1.1
Baseband version - N910W8VLU1COK3
Build number - LMY47X.N910W8VLU1COK3
Currently have the Team Win Recovery Project v2.8.7.0 recovery software installed.
I am looking for suggestions for both issues, but really want to avoid resetting the phone if I can at all possible... Yes, I have Titanium Backup Pro installed, but have never actually gotten a restore to properly restore all my applications and data... I rely on it now just for the Uninstall and Freeze features.
For an update,
I also noticed that rotation works on the Lock Screen and in the camera applicaiton.
If I rotate my screen on the Lock Screen, the red handset picture and camera icons rotate.
If I rotate in the camera application, nothing changes position, but all the icons rotate as well.
I'm still completely stuck though, open to suggestions...
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
uchihakurtz said:
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
Click to expand...
Click to collapse
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
kevinds said:
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
Click to expand...
Click to collapse
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
kevinds said:
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
Click to expand...
Click to collapse
This is amazing, can you please post the odin flashable file? I am having this exact problem right now because I removed it in TB. Is it just the facebook file that are flashed? Thanks so much in advance, you're saving my life here