Related
Hi All,
i have an issue - i installed custom ROM, custom kernel, all is working except root.
I have two root apps - superuser (standard) and one from ROM supersu. One came with ROM, and i flashed another (standard) just after flash (not sure why really)
So - I have two supersusers - bot don't have root... irony
Any suggestion how to fix that? Also, how should i delete superuser (standard) from system/app folder (without root apparently)?
Thanks all!
"This app cannot be uninstalled if it was installed with your ROM or root. If there is no uninstall option, it's because you placed it in /system/app, not me. It is impossible for an app to be installed in /system/app by the Play store. In fact, the entire /system partition is read only at runtime. The only way for an app to be placed in /system/app is via a rooting process (which usually installs Superuser), or by remounting the system partition as read/write and manually putting it there."
this is from the play store page. I guess you could try using root explorer to delete it but don't know if it will work
The more important question is why don't you have root? You have two root apps installed on a custom ROM. You should be able to run SuperSU and let it update the su binary. Then you can use ROM Toolbox or TB to remove Superuser.
Posted using Tapatalk 2
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Jsparta26 said:
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Click to expand...
Click to collapse
That's already been suggested in the ROM thread on another site, but he seems to be trying to get around it without reinstalling the ROM. He said over there that he doesn't know why he installed SuperUser since the ROM came with another su app and neither do I. He should just go ahead and reflash the ROM.
For some reason this guy seems to want to do things differently from standard practices and then ask for help when it doesn't work. His latest post in the other thread was asking if he could flash the ROM after removing the kernel (boot.img)!
I'm not sure where he comes up with these ideas but he seems to be off doing his own thing even though he is new at this stuff. I'm not suggesting that you don't help him, but wanted you to be aware that he may be creating problems for himself.
ramjet73
Thanks for the heads up. Your right, it don't make sense to try something different if what we suggest to somebody has been a better and usually a full proof way of fixing a problem. But like you said if he wants to add to his own problems that's on him. Let's make this clear to him too since he is new. Nobody on this site or other sites are responsible if you blow up your device, your gf leaves you, or you burn down your house and get fired. :highfive:
It took nearly 24 hours to upload due to my dreadful internet connection but here it is, the latest Android version for the galaxy Mega I9200 AKA Kit Kat I9200XXUDNE4, repacked with a full Knox free bootloader.:good:
DISCLAIMER
I'm not responsible for anything, as usual procede only if you know what you do, and make a backup beforehands in case things go out of control.
This said since this ROM is Knox free you will be able to get back to 4.2.2 or to whatever ROM you want in case you don't like Kit Kat.
IMPORTANT
You can flash this ROM ONLY if you come from a non Knox Rom.
It means that if you were on a ROM that had Knox, like the latest 4.2.2 versions, you can't flash this ROM and in that case you'll have to go for the regular 4.4.2 Knox version available at sammobile.
BEFORE TO FLASH
Get a custom recovery, cuz this ROM comes without any recovery.
Why?
Because at the time I was testing it I kept my custom recovery to see if I could reuse it with Kit Kat, and since it worked, and since I don't want to loose again 24 hours to upload an other ROM with a recovery, you'll have to go like this.
There are plenty of custom recoveries on the forum, as for me I use that one:
http://forum.xda-developers.com/showthread.php?t=2415294
but you can use any one you like, it doesn't matter as long as it has been installed BEFORE to flash Kit Kat.
Edit
If for some reasons you want to stick to stock recovery head to post #5, I've attached it there with some instructions.
THE FLASH
Download the ROM, unrar it and you'll get a tar.md5 file.
Open ODIN 3.04, put the file in the PDA section.
On your phone, enter download mode (press volume down and start at the same time), then connect it to your computer.
Once it has been recognized by Odin (it gets blue on the left upper case) start the flash.
It will take approx 5 mns before it reboots, that's it.
If everything goes ok it will reboot twice and then it will enter the set up wizard.
It could be that some app forces close and that it reboots one more time, in that case you'll have to enter recovery and format /data (and since you have a custom recovery you can do so without erasing your sd card contents).
ROOT
Easy, download the latest SuperSU_1.94.zip from the master chainfire, flash it from recovery, reboot, voila.
REMOVING THE LAST KNOX TRACES:
This has to be done manually (I could have done it and repacked/uploaded a new pre rooted ROM with everything done but sorry, my connection is too slow )
There are some Knox apps in the /system/app folder and in the system/priv-app folder:
-the ones that have Knox in their name are easy to guess;
-one is called KLMSAgent and should be deleted as well, and so too ContainerAgent.apk, ContainerAgent.odex, ContainerEventsRelayManager.apk and ContainerEventsRelayManager.odex.
In the /system/lib folder delete libknoxdrawglfunction.so.
Delete completely the system/preloadedkiosk folder and the system/preloadedsso folder.
In data/data delete the com.sec.knox.seandroid folder and the com.sec.knox.store, and the other com.sec.knox whatever folders there are.
Enjoy!!!:silly:
Stay tuned, in the coming days I will put some mods here...
I already made a deodexed version but I don't think I will upload it since it takes too long (24 hours again), so if anyone with a better connection feels like doing it he or she is welcome!
THE LINK?
Here it is:cyclops::
https://mega.co.nz/#!6lhzGaab!zIFiED3APN7_lHAT5YRPbgJqb6lyrLZJwjs-gw9kLEQ
CREDITS
@SilviuMik for the tuto
@Chainfire for the root
@XDA for the opportunities it gives to all of us
Reserved, for some hopefully soon to come stuff
I'm guessing we can't jsut flash this in recovery, right?
unclefab said:
-cut-
Get a custom recovery, cuz this ROM comes without any recovery.
Why?
Because at the time I was testing it I kept my custom recovery to see if I could reuse it with Kit Kat, and since it worked, and since I don't want to loose again 24 hours to upload an other ROM with a recovery, you'll have to go like this.
-cut-
Click to expand...
Click to collapse
I expect you are ready for udate and version WITH recovery already started to upload? Please be serious of your work!
trurl3 said:
I expect you are ready for udate and version WITH recovery already started to upload? Please be serious of your work!
Click to expand...
Click to collapse
Yep, I have to be serious:cyclops: so here it is, I packed a stock recovery in case someone needs it for some reason (s).
It took (only) 15 mns to upload (not bad for a 10 mb file )...
Download the file, open Odin 3.04, put the file in PDA, flash, now you have KK's stock recovery, boooooo:laugh:
http://d-h.st/PGb
@bnb25
nope, you can't flash the ROM from recovery.
If some people are interested I can upload the deodexed version in the coming days when I have time, unless someone else does it before
I flashed somr stock rooted Rom awhile ago on the gf's phone. I been waiting on this update b4 doing anything. The phone acts up. Performance issues. She keeps ot close to full. Moving to sdcard doesn't work anymore. (That broke b4 filling the phone up. But didn't know that when we bought a 16gb sdcard.) So....thus has knox removed. You mentioned stock recovery as an option. You mean the stock kitkat recovery for the phone? Meaning that will introduce knox if you choose it? And if you do choose stock recovery with knox it can be rooted right? Just saying cause usually when first comes out it takes a lil time for someone to root it.
Sent from my SM-N900P using Tapatalk
i try this rom for 10 minutes and it keep restarting..
so i flash again with ODIN 3.04, and it keep restarting again..
i have wipe data and cache+dalvik, i use twrp recovery.
can you troubleshoot this problem?
thank you :good:
sorry for my bad english...
Works fine for me. I had latest official 4.2.2 rom; I then flash a custom recovery and a rooted rom before I flash this rom via odin. After flashing this rom, I wiped it factory reset. All is well for me. 24hrs now. Thumbs up me general.....
Sent from my GT-I9200 using XDA Premium 4 mobile app
@ninja_unmatched:
the recovery I attached is the stock KK recovery, and AFAIK it doesn't have Knox in it. About rooting a Knox cursed ROM, some people say it's easy but I don't have any personal experience on that matter.
But anyway, why don't you want to use a custom recovery?
I kept the CWM I had on 4.2.2, and after I upgraded to 4.4.2 it took me 2 minutes to root with Chainfire's SuperSu_1.94.zip...
So now I'm on Knox free KK, with custom recovery and root.
@congquer:
do a full factory reset and see if it helps.
@fpage:
nice to read that it works fine for you!:good:
@all:
if you are rooted and want to enable quad multi windows view (up to 4 apps opened at once on the same screen, fully resizable), check my thread in the themes and apps section..:
One of the best KK's new features cool:...
works like a charm, i've installed via odin, but lost root for some reason
Well the girl is like any other nooby internet user. She knows enough to get it infected over and over....lol. Knox actually helps a lil with that. I used to use my phone (Note 3) to check questionable sites out for clients. Knox would do its pop ups alerting me to there being something going on that I do not want. It has actually helped....weird thing sort of. Now of course it doesn't do that anymore but for her......it might lower my headaches if you know what I mean?
But...no I'm about to try it out now anyways after I backup her phone.
Sent from my SM-N900P using Tapatalk
It could be that some app forces close and that it reboots one more time, in that case you'll have to enter recovery and format /data
This step right here causes the same boot loop mentioned. An app forces closes just like you said. soon as you format /data after a reboot it goes into a boot loop. I am also using TWRP 2.7
You have to clear cache not data. Even with that alot of apps just force close.
Sent from my SM-N900P using Tapatalk
I am rooted and working like a charm. Quad window working and alot of modules via xposed installer.
Sent from my GT-I9200 using XDA Premium 4 mobile app
Well it didn't work for me. And the supersu only caused freezing then reboot. I just went and flashed stock. Maybe I'll root it later. The process also messed with the sdcard. Made it unreadable. So I used an app (Called Photorec) to recover some of the files from the 16gb sdcard she has.
Sent from my SM-N900P using Tapatalk
whenever I want to delete knox from system/app, it always failed to delete.
I wonder why?
@ninja_unmatched:
your girl seems to be like mine, willy to use the phone but messing it all the time, and then calling her man to fix it:cyclops:.
But you are worse tham me cuz you use her phone as a guinea pig!
The problem with SuperSu is that at first you can't install it a a system app.
In order to fix this you'll need either twrp recovery or aroma file manager ( http://forum.xda-developers.com/showthread.php?t=1646108 ) and do as follows:
-download SuperSu zip,
-extract the app from the zip but keep the zip intact,
-flash the SuperSu zip,
-do not reboot but go to your file system while still in recovery, either from the twrp menu or by flashing the aroma file manager file,
-delete SuperSu from the system/app folder,
-reboot,
-install the SuperSu apk manually as you would with any apk.
Now you are rooted, and your SuperSu being on your data/app folder it doesn't force close anymore.
Later you can convert SuperSu into a system app from the apk's settings.
But this force close is a problem on KK, cuz everytime an app FC (not only SuperSu) the phone reboots, pretty annoying and definitely a deal breaker for me.
The messing with the files is another problem, it's because somehow KK uses another format than JB. But this one is easy to overcome, just connect your phone to your computer and copy the files to it, or you can copy them from recovery/aroma file manager (that's what I did, at first I thought it was gone but nope, it's just a format stoy) to anywhere on your phone.
@fpage:
I'm happy for you if everything works:good:
@serpentlord:
salaam manis dari Jowo!:laugh:
Are you rooted? Sorry if the question sounds obvious, but if you are then deleting the Knox apks shouldn't be a problem.
Otherwise if it doesn't work, use aroma file manager (see above, and don't forget to push thanks for @amarullz our dev from Bandung!) and delete the Knox stuff from within recovery.
That said I went back to 4.2.2, this KK is plagued with bugs and I don't like the new multi windows implementation, so until they make a more stable version and until I find out whether I can implement some of JB's multi windows functions in it or not I'll stick to 4.2.2...
I'll make soon a thread about specific KK's bugs, hopefully sammy will listen but don't hold your breath
A guinea pig....lol. yeah. Only thing I ever did was flash a stock 4.2.2 rooted Rom. For wifi tethering purposes. It was fine for awhile. She starts complaining about it....I find she filled the thing up. Apps, apps, apps, mad games. I move some of the apps to the 8gb card. That helped. Later she fills it up again. I get a 16gb card and then find out it won't move anything to the card. Broke that somewhere after the 8gb card move. She goes on facebook and clicks on those questionable site posts and jave you sign up while giving them permission to post on your profile and all sorts if sites I find are questionable. That and apps from blackmart and from that site that offers hacked android games/apps.
So far now she seems fine on the stock official 4.4.2. It has a few widgets and apps in Russian. I've seen a few bugs that clear up on their own.
1. The lock screen took a bit to update. (What I mean is this. I know when playing music will say Milk it will show also on the lock screen. It wasn't doing that. Had to reboot to get that going.)
2. There is an app called Wish. It allows you to send something you think another person would be interested in that also has wish. That feature doesn't work to well. You can choose facebook or google+. FB no work at all. I think that is some other reason for that one. Google+ works but only if you choose the regular browser. Through chrome the page doesn't pop up woth the option to use the app to open the link.
And generally I've just run into these lil quarks that eventually just start working. Or partially work enough to get by.
Sent from my SM-N900P using Tapatalk
unclefab said:
salaam manis dari Jowo!:laugh:
Are you rooted? Sorry if the question sounds obvious, but if you are then deleting the Knox apks shouldn't be a problem.
Otherwise if it doesn't work, use aroma file manager (see above, and don't forget to push thanks for @amarullz our dev from Bandung!) and delete the Knox stuff from within recovery.
That said I went back to 4.2.2, this KK is plagued with bugs and I don't like the new multi windows implementation, so until they make a more stable version and until I find out whether I can implement some of JB's multi windows functions in it or not I'll stick to 4.2.2...
I'll make soon a thread about specific KK's bugs, hopefully sammy will listen but don't hold your breath
Click to expand...
Click to collapse
Salam manis dari Jakarta! :laugh:
Yes, my device is rooted. I've tried root browser, root explorer and soon. but it ends with the same result. I wonder why.
And my device also keep restarting every 10 minutes. Is it a bug?
@ninja_unmatched:
I can't tell about this wish.apk and widgets, at the time I was still on 4.4.2 I had stripped the Rom down to only about 20 system apps.
I allways do this on my ROMs cuz I don't like stock apps, I rather uninstall all that stuff and replace it by third part apps that are easier to manage and not so much on the spying/bloatware side...
@serpentlord:
what happens is probably that you have an app that forces closes, and this is what makes the phone reboot. I had the same problem and in my case it was youtube, in your case it could be any other app.
Just start your phone and keep an eye on it until it says "sorry app whatever has closed". Then if it reboots you know from wish app it comes and you can uninstall it and/or replace it with another app or another version from the same app.
I have a Note 2 (obviously), and I have rooted my phone the first day I got it and have never updated the phone since I purchased it. So, I am still on 4.1.2. My phone has been super laggy and I want to take the oppurtunity the when I reset my phone that I can take advatages of the new features that mobile phones have by upgrading all the way to 5.1.x.
So, I downloaded CM 12.1 by wilson3q with 5.1 system. I first tried the 5.0 version since the 5.1 looked too new, and did not have time to deal with the bugs. When I flashed the 5.0 version, I got errors of not being able to flash gapps for 5.0 and that I lost my root. I tried downloading the new TWRP to see if I can get a newer version that would work better, but no luck. I got an error saying that I lost my root privileges and did I want TWRP to fix it. I slid yes to fix, but no luck.
The same problem occurred when I tried with 5.1.
So, I ended up restoring my nandroid backup and I am back on 4.1.2 again with root working again.
I am thinking that I am probably supposed to 'step up' the updates, but not sure. Does anyone have a solution or a link to the solution that they can help with?
PS: I did not like the camera that came with the new mod. I do like the stock one. Are there flashes of cameras that I can use as well when I do end up upgrading?
Thank you in advance!!!
geske001 said:
I have a Note 2 (obviously), and I have rooted my phone the first day I got it and have never updated the phone since I purchased it. So, I am still on 4.1.2. My phone has been super laggy and I want to take the oppurtunity the when I reset my phone that I can take advatages of the new features that mobile phones have by upgrading all the way to 5.1.x.
So, I downloaded CM 12.1 by wilson3q with 5.1 system. I first tried the 5.0 version since the 5.1 looked too new, and did not have time to deal with the bugs. When I flashed the 5.0 version, I got errors of not being able to flash gapps for 5.0 and that I lost my root. I tried downloading the new TWRP to see if I can get a newer version that would work better, but no luck. I got an error saying that I lost my root privileges and did I want TWRP to fix it. I slid yes to fix, but no luck.
The same problem occurred when I tried with 5.1.
So, I ended up restoring my nandroid backup and I am back on 4.1.2 again with root working again.
I am thinking that I am probably supposed to 'step up' the updates, but not sure. Does anyone have a solution or a link to the solution that they can help with?
PS: I did not like the camera that came with the new mod. I do like the stock one. Are there flashes of cameras that I can use as well when I do end up upgrading?
Thank you in advance!!!
Click to expand...
Click to collapse
Try Phiz recovery, I've never had trouble with "[I605][CWM Advanced Edition] PhilZ Touch". If I recall we had to start using that one when kit-kat was released (i reserve the right to recall poorly)
I have a link to download mirror here:
http://forum.xda-developers.com/showpost.php?p=60899023&postcount=146
from your new recovery, you should be able to install CM12.1 and 5.1 gaaps recommended in the Wilson3Q i605 thread. from here:
http://forum.xda-developers.com/note-2-verizon/development/rom-unofficial-build-i605-t3069506
FWIW, I am on the 20150803 build and still using the GApps Minimal Edition 2015-04-04 for Android 5.1 (91 MB) from here:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
with no issues to report.
You may also need to track down updated radios (to flash from CWM). I think you can find a link to the updated ND7 Modem/Baseband here:
http://forum.xda-developers.com/showthread.php?t=2765021
somewhere in middle of first post
Good Luck!
PS you may want to flash superSU from recovery... get the zip from chainfire's xda thread here:
http://forum.xda-developers.com/showthread.php?t=1538053
(I've been dirty flashing for so long I dont' remember if the rom came with SuperSU or superuser... as such I can't recall if I had to flash this zip or not, but I probably did if I had issues with root)
Note you may also need to enable root from the settings menu after enabling developer mode.
there should be a "root access" option (or somehting like that there)
PPS are you also remembering to wipe data & clear cache/dalvik?
I have found zoot's mega wipe useful...
http://forum.xda-developers.com/showthread.php?t=1983489
it is for the N7100/N7105, butI have used it on the i605 quite a bit. Initial test result reported here:
http://forum.xda-developers.com/showpost.php?p=44093932&postcount=117
that said zoot's script is probably overkill
jheide44 said:
Try Phiz recovery, I've never had trouble with "[I605][CWM Advanced Edition] PhilZ Touch". If I recall we had to start using that one when kit-kat was released (i reserve the right to recall poorly)
I have a link to download mirror here:
http://forum.xda-developers.com/showpost.php?p=60899023&postcount=146
from your new recovery, you should be able to install CM12.1 and 5.1 gaaps recommended in the Wilson3Q i605 thread. from here:
http://forum.xda-developers.com/note-2-verizon/development/rom-unofficial-build-i605-t3069506
FWIW, I am on the 20150803 build and still using the GApps Minimal Edition 2015-04-04 for Android 5.1 (91 MB) from here:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
with no issues to report.
You may also need to track down updated radios (to flash from CWM). I think you can find a link to the updated ND7 Modem/Baseband here:
http://forum.xda-developers.com/showthread.php?t=2765021
somewhere in middle of first post
Click to expand...
Click to collapse
I assume that you are giving steps in order, BUT I feel that I should flash the radio to 4.4.2 first, in which the link was broken. I have spent a couple hours trying to find another link, but I am afraid that I may be using an incorrect one. Do you have a good link for that, please?
Also, I have ready the newest Samsung 3.10 Odin downloaded and installed, as well as the USB driver installed and downloaded the ADB fastboot. If I remember correctly, I am supposed to move this onto C: and run it to access the device (Note 2). It has been since Android first came out since I have used the ADB though. So, I apologize for the ignorance. So, do I just make sure the adb is in the same directory and run Odin or did I not need ADB and just run Odin?
I also assume that I run the Philz touch after I have gotten to 4.4.2 rooted first. Am I correct by assuming that?
jheide44 said:
Good Luck!
PS you may want to flash superSU from recovery... get the zip from chainfire's xda thread here:
http://forum.xda-developers.com/showthread.php?t=1538053
(I've been dirty flashing for so long I dont' remember if the rom came with SuperSU or superuser... as such I can't recall if I had to flash this zip or not, but I probably did if I had issues with root)
Note you may also need to enable root from the settings menu after enabling developer mode.
there should be a "root access" option (or somehting like that there)
PPS are you also remembering to wipe data & clear cache/dalvik?
I have found zoot's mega wipe useful...
http://forum.xda-developers.com/showthread.php?t=1983489
it is for the N7100/N7105, butI have used it on the i605 quite a bit. Initial test result reported here:
http://forum.xda-developers.com/showpost.php?p=44093932&postcount=117
that said zoot's script is probably overkill
Click to expand...
Click to collapse
Yes, I have done a cache/dalvik wipe a few times (because I have tried reflashing to get it to work with no luck).
I have downloaded the .zip version of superSU as well, and gapps minimal 5.1 with wilson3q's 5.1 ROM. So, I am almost ready to go with the exception of the correct radio upgrade file.
Thank you so much for your help!!! Much appreciated!
PS Will my old WifiTether apk files still work with 5.1 or do I need to get a new one?
Thanks Again!
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
jheide44 said:
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
Click to expand...
Click to collapse
I will try this later. Thank YOU! I have to take kids to practice now.
jheide44 said:
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
Click to expand...
Click to collapse
Sorry to bother you, but I still am getting errors with Failed root access for Titanium Backup Pro. I also cannot find Developer Options in the settings menu.
I have tried flashing the radio before and after wiping and installing the ROM then gapps then superSU. I get into superSU and it asks me for root access and I grant it, but Titanium Backup Pro still says that it has no root access.
Any ideas? Thank YOU!!
geske001 said:
Sorry to bother you, but I still am getting errors with Failed root access for Titanium Backup Pro. I also cannot find Developer Options in the settings menu.
I have tried flashing the radio before and after wiping and installing the ROM then gapps then superSU. I get into superSU and it asks me for root access and I grant it, but Titanium Backup Pro still says that it has no root access.
Any ideas? Thank YOU!!
Click to expand...
Click to collapse
with SuperSU installed, you may need to just need to update binaries. open SuperSU and it should prompt you if necessary. the "normal" option should work (no need to flash from recovery)
for TiBu...
--within SuperSU settings you may need to disable (uncheck) "mount name separation".
--You may also have to enable unknown sources (under settings, security).
-- there might be something to enable for USB debugging as well (TIBU should prompt for it)
FWIW, you can restore user apps/data... but I would not attempt to restore any system data. Personally, I have found it best to get to know a fresh ROM for a while before trying to restore crap from an older ROM . there might be value in re-configuring apps manually and/or restoring them one at a time (after making sure the ROM is working properly) i.e. you won't need any of those aforementioned WiFi tether apps since it is built into the ROM now.
Instructions on enabling developer options in CM ROM, from here: http://wiki.cyanogenmod.org/w/Doc:_developer_options
1- In the Settings app, select About Phone (or About Tablet).
2- Scroll down, and tap the Build number entry seven times. On the seventh tap, you will be notified that "You are now a developer."
3- Return back to the main Settings menu. Developer options and Performance entries should now be visible.
Click to expand...
Click to collapse
(that is likely how to enable superuser that is "baked" into the rom, given you already installed SuperSU it may only complicate matters)
You may be rooted and just having TiBu issues. If all else fails you can check with an app. A long time ago, I've used "Simple Root Checker" by SimoneDev to check root/busybox. It is still in the play store.
Good Luck!
jheide44 said:
with SuperSU installed, you may need to just need to update binaries. open SuperSU and it should prompt you if necessary. the "normal" option should work (no need to flash from recovery)
for TiBu...
--within SuperSU settings you may need to disable (uncheck) "mount name separation".
--You may also have to enable unknown sources (under settings, security).
-- there might be something to enable for USB debugging as well (TIBU should prompt for it)
FWIW, you can restore user apps/data... but I would not attempt to restore any system data. Personally, I have found it best to get to know a fresh ROM for a while before trying to restore crap from an older ROM . there might be value in re-configuring apps manually and/or restoring them one at a time (after making sure the ROM is working properly) i.e. you won't need any of those aforementioned WiFi tether apps since it is built into the ROM now.
Instructions on enabling developer options in CM ROM, from here: http://wiki.cyanogenmod.org/w/Doc:_developer_options
(that is likely how to enable superuser that is "baked" into the rom, given you already installed SuperSU it may only complicate matters)
You may be rooted and just having TiBu issues. If all else fails you can check with an app. A long time ago, I've used "Simple Root Checker" by SimoneDev to check root/busybox. It is still in the play store.
Good Luck!
Click to expand...
Click to collapse
Thank you! It ended up being my version of Titanium Backup. I downloaded a new version and it is good. As far as restoring is concerned, I do not even want the apps themselves restored from there, because there may be a new version and would like a fresh install of those apps. I just want my data restored. For example, I have a surveillance software that I would just like to restore the entries (IP's usernames and passwords). I would like my email settings to be there, so that I do not have to re setup my 7 email addresses. My Text/SMS messages and my alarms. So, I am not trying to do a full restore.
On another note, I am trying to get my calendars back into my phone with no luck. I cannot install google calendar and get my google calendars to populate into my task widget, and the ROM is not letting me set up my POP email addresses. Also, I see no ringtones, so I have no ringers to ring my phone nor tones for my alarm clock. I flashed gapps for 5.1 and I see nothing extra from the ROM. I thought gapps was google apps. Am I trying to do stuff differently than you? There seems to be a few problems in that manner that I am trying to work with.
I am thinking of downgrading to 5.0. Maybe the 5.1 is too new?
Again, THANK YOU for your help!
geske001 said:
Thank you! It ended up being my version of Titanium Backup. I downloaded a new version and it is good. As far as restoring is concerned, I do not even want the apps themselves restored from there, because there may be a new version and would like a fresh install of those apps. I just want my data restored. For example, I have a surveillance software that I would just like to restore the entries (IP's usernames and passwords). I would like my email settings to be there, so that I do not have to re setup my 7 email addresses. My Text/SMS messages and my alarms. So, I am not trying to do a full restore.
On another note, I am trying to get my calendars back into my phone with no luck. I cannot install google calendar and get my google calendars to populate into my task widget, and the ROM is not letting me set up my POP email addresses. Also, I see no ringtones, so I have no ringers to ring my phone nor tones for my alarm clock. I flashed gapps for 5.1 and I see nothing extra from the ROM. I thought gapps was google apps. Am I trying to do stuff differently than you? There seems to be a few problems in that manner that I am trying to work with.
I am thinking of downgrading to 5.0. Maybe the 5.1 is too new?
Again, THANK YOU for your help!
Click to expand...
Click to collapse
I wouldn't downgrade, nobody is actively working on 5.0.2 anymore.... that thread is basically dead. Also, it is likely less "stable"/mature than what you have installed now (that is currently being maintained). i.e. you have the ROM that I would stick with.
like I said I wouldn't restore any thing into system (apps or data)... you can do whatever you please. (but it could be causing you more issues than just biting the bullet & configuring manually) i.e. restoring accounts might result in unanticipated issues, you came from a much older version of android.
all I had to do was install google calendar from play store and then the CM12 calendar stuff all worked (I might have had to restart and/or install the google calendar prior to setting up primary gmail). you might need to remove all your accounts and load them again (a factory reset might be faster though.)
also you might have to update google services and the play store before certain things "play nice".
I know you don't want to hear this but...
from here on out i'll likely point to all your issues being based on restoring system data. (based on my limited knowledge and personal experience). FWIW, I'd try to reconfigure/setup everything manually and you will likely have much better results.
jheide44 said:
I wouldn't downgrade, nobody is actively working on 5.0.2 anymore.... that thread is basically dead. Also, it is likely less "stable"/mature than what you have installed now (that is currently being maintained). i.e. you have the ROM that I would stick with.
like I said I wouldn't restore any thing into system (apps or data)... you can do whatever you please. (but it could be causing you more issues than just biting the bullet & configuring manually) i.e. restoring accounts might result in unanticipated issues, you came from a much older version of android.
all I had to do was install google calendar from play store and then the CM12 calendar stuff all worked (I might have had to restart and/or install the google calendar prior to setting up primary gmail). you might need to remove all your accounts and load them again (a factory reset might be faster though.)
also you might have to update google services and the play store before certain things "play nice".
I know you don't want to hear this but...
from here on out i'll likely point to all your issues being based on restoring system data. (based on my limited knowledge and personal experience). FWIW, I'd try to reconfigure/setup everything manually and you will likely have much better results.
Click to expand...
Click to collapse
I figured that, and feared that and the same time. So, what am I flashing onto the phone with gapps then? Also, one of the reasons I was wanting to go back was because there are a few apps that are not 'compatible' with this system. Meanwhile, I am going to wipe and reset again, and do what you suggested and just reconfigure.
Thanks again!
geske001 said:
I figured that, and feared that and the same time. So, what am I flashing onto the phone with gapps then? Also, one of the reasons I was wanting to go back was because there are a few apps that are not 'compatible' with this system. Meanwhile, I am going to wipe and reset again, and do what you suggested and just reconfigure.
Thanks again!
Click to expand...
Click to collapse
GAaps are the google apps... good read:
http://wiki.rootzwiki.com/Google_Apps
(hopefully I am not out of line for posting a link to that wiki)
many ROMS like CM don't' include gaaps due to licencing/legal issues. which is why the AOSP roms devs often have you flash the GAAPS package separately (also you can pick your package for your fact pattern... full gaaps/minimal gaaps/etc.).
Also the gaaps zip files you flash from recovery install the files into system. a lot of folks like the minimal editions of GAaps because it doesn't force all the apps into system. instead it just gets you up and running with the play store and a few essentials... that lets the user install all the other google apps as user apps, from the play store.
basically taking the "debloat" mentality as far as you can... keep stuff out of system and let the user decide what to install.
EDIT: Problem is resolved. After I learn very much:
I made a video, cause there is no helpful video with Safestrap 4. Only with Version 3 and this way is wrong now!
I also write a blog about that helpful storry and links that will help other's.
Hello,
i started to root my Apollo 8.9/LTE with Tutorials from here and a translation in german. I live in germany.
http://www.android-hilfe.de/thema/r...r-kindle-hdx-8-9-apollo-fire-os-4-5-2.693547/
http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
Root Tool
Thats what i do
Rollback to OS 3.2.8 was great
Update to 4.5.2 was also ok
I rootet my Apollo, it works - i tested it
After that i renamed the DeviceSoftwareOTA.apk from Kindle in the priv-app
Now i copied all needed GAPPS files to the system Folder except the descripited
After that i restart my Apollo and now the Problems start
After restart
{
"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"
}
Google Folder with Images
The Google Assistent start immediately after restart
I have to choise a Language but there was no german
Also i had no WIFI Connection, so the Assistent start the Option to connect with WIFI
This work, but at the wifi there is a X and in the Assistent i habe no Internet connection
I use my SIM Card to get a internet connection (This work) but the Assistent need a WIFI
Also i lost my root and get Denied when i try to copy/change with a older version befor April 15 or delete the GAPPS Files in the system Folders
I can start/install Apps with apk, at the apollo i only can use the settings. I have no menu or keys
Thats what i tried
I can use adb and install ES Datei Explorer or SuperSu
I used KingRoot, it dosn't work
I copied the mod Rollback to 3.2.8 bin File in the root folder, but Apollo dont use this file, maybe cause i renamed the OTA Systemfile
I made a reset of the Apollo, but the google Assistent is in the systemfiles and start even after a reset
My Apollo
Has Fire OS 4.5.2
The DeviceSoftwareOTA.apk is renamed
I only can Read NOT Write in the system folders
I can use adb and connect to the Apollo
I tried so much the last 2 days so i hope you got a hint for me.
Gatam77 said:
Hello,
i started to root my Apollo 8.9/LTE with Tutorials from here and a translation in german. I live in germany.
http://www.android-hilfe.de/thema/r...r-kindle-hdx-8-9-apollo-fire-os-4-5-2.693547/
http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
Root Tool
Thats what i do
Rollback to OS 3.2.8 was great
Update to 4.5.2 was also ok
I rootet my Apollo, it works - i tested it
After that i renamed the DeviceSoftwareOTA.apk from Kindle in the priv-app
Now i copied all needed GAPPS files to the system Folder except the descripited
After that i restart my Apollo and now the Problems start
After restart
Google Folder with Images
The Google Assistent start immediately after restart
I have to choise a Language but there was no german
Also i had no WIFI Connection, so the Assistent start the Option to connect with WIFI
This work, but at the wifi there is a X and in the Assistent i habe no Internet connection
I use my SIM Card to get a internet connection (This work) but the Assistent need a WIFI
Also i lost my root and get Denied when i try to copy/change with a older version befor April 15 or delete the GAPPS Files in the system Folders
I can start/install Apps with apk, at the apollo i only can use the settings. I have no menu or keys
Thats what i tried
I can use adb and install ES Datei Explorer or SuperSu
I used KingRoot, it dosn't work
I copied the mod Rollback to 3.2.8 bin File in the root folder, but Apollo dont use this file, maybe cause i renamed the OTA Systemfile
I made a reset of the Apollo, but the google Assistent is in the systemfiles and start even after a reset
My Apollo
Has Fire OS 4.5.2
The DeviceSoftwareOTA.apk is renamed
I only can Read NOT Write in the system folders
I can use adb and connect to the Apollo
I tried so much the last 2 days so i hope you got a hint for me.
Click to expand...
Click to collapse
Nice post; well documented.
You made some serious mistakes (come back to that later) and have a challenge ahead recovering your device. Based on others experiences there is some type of conflict between gapps and the stock launcher. That is probably why you are not seeing soft buttons, keyboard, etc. The only known solution is to temporarily use a different launcher to regain control of your device long enough to reroot. Problem is your device will revert back to the stock launcher on a number of different events including pressing the home key which frequently doubles as 'back' on FireOS. You then have to reinstall the non-stock launcher or find some way to make FireOS treat it as primary.
General overview:
- grab a copy of Nova or Apex (other launchers will probably work too)
- install via 'adb install' (research if unfamiliar)
- if all goes well you should regain temporary use of soft buttons and keyboard
- stay away from home key if possible as it will immediately restore the compromised stock launcher
- attempt to reroot your device with Kingroot. This should be safe given OTA is blocked. You many need to install Kingroot via adb. Once launched Kingroot needs an internet connection to do its magic; hopefully it will pick that up via your sim card
- you can also try rooting with CVE-2014-4322 exploit.
Once you are rooted there are several paths that can be pursued. Since you have a LTE device installing Safestrap and a different ROM probably isn't the best option. Nor is reinstalling gapps on FireOS as you will face an ongoing series of battles (conflicts) between Amazon and Google frameworks. You may need to roll back and upgrade again to fully resolve the launcher conflict.
Discussion for a different post. See if you can get rooted first.
Davey126 said:
You made some serious mistakes (come back to that later)
Click to expand...
Click to collapse
maybe you mean in a later post. Or do you mean, that i crash some Fire OS Framework with the GAPPS framework
Davey126 said:
Apex
Click to expand...
Click to collapse
I take Apex, i am familar with it.
Davey126 said:
You many need to install Kingroot via adb. Once launched Kingroot needs an internet connection to do its magic
Click to expand...
Click to collapse
i install kingroot 4.1 allready on the Apollo and also the software in my pc. Then i start the windows software but root didn't work. - Maybe because i dont have a internet connection on the Apollo??
Davey126 said:
you can also try rooting with CVE-2014-4322 exploit.
Click to expand...
Click to collapse
I used the cve20147911.apk from here (it work one time, bevor the GAPPS), but i try this one.
Davey126 said:
You may need to roll back and upgrade again to fully resolve the launcher conflict.
Click to expand...
Click to collapse
I couldn't rollback now. Is the reason that i dont have root?
Gatam77 said:
I couldn't rollback now. Is the reason that i dont have root?
Click to expand...
Click to collapse
You can't change FireOS versions because you previously blocked OTA by renaming DeviceSoftwareOTA.apk. This file is required to perform rollbacks/upgrades. You will need to obtain root permissions to restore the original filename.
Davey126 said:
You can't change FireOS versions because you previously blocked OTA by renaming DeviceSoftwareOTA.apk. This file is required to perform rollbacks/upgrades. You will need to obtain root permissions to restore the original filename.
Click to expand...
Click to collapse
OK. With this file the update Start. But befor the Update load from amazon Website this takes first a look on the SDCard. Wright?
Gatam77 said:
OK. With this file the update Start. But befor the Update load from amazon Website this takes first a look on the SDCard. Wright?
Click to expand...
Click to collapse
After enabling OTA put your device in airplane/flight mode to prevent updates from downloading. Make sure your device is stable (starts/functions normally) before attempting a rollback/update. I also advise allowing your device to upgrade to 4.5.5 (you will loose root) and then restart the rollback procedure from there.
Davey126 said:
Nice post; well documented.
You made some serious mistakes (come back to that later) and have a challenge ahead recovering your device. Based on others experiences there is some type of conflict between gapps and the stock launcher.
Click to expand...
Click to collapse
Thx for your words.
I installed a launcher and restart but also had no buttons. But a other way was it.
I GOT IT!!
I dont have permission on system folder with ES Datei Explorer, but now i use adb.
I found a post here how to change permission with adb
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Now i rename the file with mv MYNAMEOFOTA to DeviceSoftwareOTA.apk
After i used the gifroot Files But i got a message that it wouldnt work with this kernel.
So i dont know exactly which way was it.
But now to my serious mistakes. Can you tell me please what you mean? Cause I love this amazon hardware but I hate the amazon Fire OS and i love GMail, sheets, Maps, and other good apps from Google. So i need root.
All works bevor i push the GApps. So what is the better way. I know I have to read much more bevor i start again. Cause the Apollo is tricky.
I wait for a answer of you bevor i rollback to 3.2.8. I can wait.
Gatam77 said:
Thx for your words.
I GOT IT!!
I dont have permission on system folder with ES Datei Explorer, but now i use adb.
I found a post here how to change permission with adb
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Now i rename the file with mv MYNAMEOFOTA to DeviceSoftwareOTA.apk
After i used the gifroot Files But i got a message that it wouldnt work with this kernel.
So i dont know exactly which way was it.
But now to my serious mistakes. Can you tell me please what you mean? Cause I love this amazon hardware but I hate the amazon Fire OS and i love GMail, sheets, Maps, and other good apps from Google. So i need root.
All works bevor i push the GApps. So what is the better way. I know I have to read much more bevor i start again. Cause the Apollo is tricky.
I wait for a answer of you bevor i rollback to 3.2.8. I can wait.
Click to expand...
Click to collapse
Congratulations! Glad you were able to make some progress. Unfortunately, you are not out of trouble yet. Do not change permissions on any other files as FireOS is very sensitive and sometimes will not start if permissions are not as expected. Especially on 'system' files and folders.
Two concerns with the approach you took:
- using an outdated mod guide not published on XDA. Some of the techniques are old or no longer recommended
- attempting to install GApps on FireOS. Amazon and Google frameworks do not play nice together. While some have got it to work acceptably there are almost always problems, some quite serious.
A better approach is to use a twrp (recovery) emulator called Safestrap. Once installed you can install a limited selection of high quality ROMs that offer full access to the Google Play store. You may be familiar with the names: Nexus and CM11. They essentially turn your Kindle into a generic android tablet. You can even use native Amazon apps like Kindle reader.
The downside is LTE is not well supported by these roms. If you use your tablet off WiFi and need LTE then you have a tough decision to make:
1) Forgo LTE in favor of a rom with full Google Play access
2) Retain LTE and FireOS with limited access to Google services and apps
You don't have to make that decision now. First step is to rollback to 3.2.8, upgrade to 4.5.2, obtain root and block OTA. In a previous post I suggested upgrading to 4.5.5 first. I am stepping away from that suggestion to streamline the process. However, there is additional risk going from 4.5.2->3.2.8 because if anything goes wrong you could end up bricking your device. Going from 4.5.2->4.5.5 is less risky but adds another step.
There are many posts on XDA detailing the rollback/upgrade/root/blockOTA/Safestrap/rom process. Start here and spend some time reading. I did not pick this thread because it was the 'best'; just one I happen to remember contributing to in recent days. But it will lead you to other helpful posts that lead to even more posts ...
As always:
- ask questions if unsure; never assume or guess
- keep WiFi off (airplane/flight mode engaged) to prevent OTAs when upgrading or rolling back. Consequences are large: an OTA can (and likely will) permanently brick your device.
- make sure you fully understand the procedures, expected outcomes and recovery options if things go wrong
- only use files posted on XDA (links ok too)
- a fresh mind helps; take a break when tired. Your device will wait.
Good luck.
Davey126 said:
Two concerns with the approach you took:
- using an outdated mod guide not published on XDA. Some of the techniques are old or no longer recommended
- attempting to install GApps on FireOS. Amazon and Google frameworks do not play nice together.
The downside is LTE is not well supported by these roms. If you use your tablet off WiFi and need LTE then you have a tough decision to make:
1) Forgo LTE in favor of a rom with full Google Play access
2) Retain LTE and FireOS with limited access to Google services and apps
As always:
- ask questions if unsure; never assume or guess
- a fresh mind helps; take a break when tired. Your device will wait.
Good luck.
Click to expand...
Click to collapse
The again a lot.
I need my Mobile Internet. Not really LTE but at least 3G! But LTE get better here in Germany so it would be nice.
I like CM. I already flashed my Samsung S3, my wife S3 Mini, and my 2 Amazon's Tate.
That's why I bought the Apollo and hope after 1 year or so there will be a custom ROM with LTE working. So if someone interested I will flash a Custom Rom, life a time without Mobile Internet and help the developer with sending log files, or other needed things.
No I started reading! But I will post again here that other can read and learn from my mistakes.
Gatam77 said:
The again a lot.
I need my Mobile Internet. Not really LTE but at least 3G! But LTE get better here in Germany so it would be nice.
I like CM. I already flashed my Samsung S3, my wife S3 Mini, and my 2 Amazon's Tate.
That's why I bought the Apollo and hope after 1 year or so there will be a custom ROM with LTE working. So if someone interested I will flash a Custom Rom, life a time without Mobile Internet and help the developer with sending log files, or other needed things.
No I started reading! But I will post again here that other can read and learn from my mistakes.
Click to expand...
Click to collapse
FYI - you can find the Safestrap compatible CM11 rom thread here. As I recall some aspects of LTE/3G work ok. Skim through the posts for more detail. Might be a non-issue for your needs.
Davey126 said:
You don't have to make that decision now. First step is to rollback to 3.2.8, upgrade to 4.5.2, obtain root and block OTA. In a previous post I suggested upgrading to 4.5.5 first. I am stepping away from that suggestion to streamline the process. However, there is additional risk going from 4.5.2->3.2.8 because if anything goes wrong you could end up bricking your device. Going from 4.5.2->4.5.5 is less risky but adds another step.
Click to expand...
Click to collapse
After i was short befor to brick my Apollo, maybe I would first Going from 4.5.2 > 4.5.5 and then 3.2.8 > 4.5.2.
But i dont read a hint with a link to 4.5.5. Can I download ist from here Davey?
Also i take a look in my router and he block some IPs when I used Kingroot on my PC yesterday.
14.17.41.155
202.77.59.49
163.177.71.157
120.198.203.149
103.7.29.30
They come from Hongkong and Bejiing. Is it possible that that was the reason Kingroot couldn't root my Apollo?
Gatam77 said:
After i was short befor to brick my Apollo, maybe I would first Going from 4.5.2 > 4.5.5 and then 3.2.8 > 4.5.2.
But i dont read a hint with a link to 4.5.5. Can I download ist from here Davey?
Also i take a look in my router and he block some IPs when I used Kingroot on my PC yesterday.
14.17.41.155
202.77.59.49
163.177.71.157
120.198.203.149
103.7.29.30
They come from Hongkong and Bejiing. Is it possible that that was the reason Kingroot couldn't root my Apollo?
Click to expand...
Click to collapse
I can't speak to what IPs Kingroot uses. There have been various reports of it being slow or temporarily not working. Perhaps due to network congestion. Usually clears up after a few hours.
If you have restored DeviceSoftwareOTA.apk you can simply enable WiFi (disable airplane/flight mode) and allow the device to receive an OTA and self-update to 4.5.5. This is actually a good test OTA functionality is working which is also required for manual rollbacks/upgrades.
There is another option that does not involve rollbacks/upgrades: If you can obtain root you can then attempt to install Safestrap v4 followed by CM11 or Nexus v4 (you can also 'repair' FireOS using this method). Both Kingroot and Safestrap require interactive access. You don't need to type anything (so keyboard doesn't need to display), just tap an on-screen button or two. You would need to install apks via adb and then have enough control over your device to launch the app. Not easy or intuitive.
I will caution there is risk with either path (upgrading FireOS or installing Safestrap on a dysfunctional device). You have to weight the risks and take the course the feels most comfortable. There are no guarantees.
Reminder: do not do a 'factory reset' from the native recovery menu unless recommended by an experienced contributor, especially after rooting or installing Safestrap.
Now all is ok again. I am so joyful.
First Download Safestrap from here
Downloaded and Follow the instructions here
Now i can start with a new and clean Android on a good Amazon Hardware
Installed Safestrap on my damaged Fire OS 4.5.2
Than install a recovery in the Safestrap APP
After that i made a slot with 1200 System/1500 Data/1000 Cache
Active the slot
go into Wipe Menu and Swipe to perform a factory reset
Go in the Install Menue and install CM11, GAPPS and SuperSu
Now i started in CM11
Again thx to Davey126.
My stock ROM is still the damaged where I mixed amazaon and google framework. What can i do?
Active the Stock slot, start into my damaged Fire OS
Push with adb a Fire OS 4.5.5 to the sdcard
Or make a OTA over the WLAN from amazon?
Or (in the video says: NEVER touch the stock at Safestrap) Install a Fire OS bin in Safestrap to witch slot?
Gatam77 said:
Now all is ok again. I am so joyful.
First Download Safestrap from here
Downloaded and Follow the instructions here
Now i can start with a new and clean Android on a good Amazon Hardware
Installed Safestrap on my damaged Fire OS 4.5.2
Than install a recovery in the Safestrap APP
After that i made a slot with 1200 System/1500 Data/1000 Cache
Active the slot
go into Wipe Menu and Swipe to perform a factory reset
Go in the Install Menue and install CM11, GAPPS and SuperSu
Now i started in CM11
Again thx to Davey126.
My stock ROM is still the damaged where I mixed amazaon and google framework. What can i do?
Active the Stock slot, start into my damaged Fire OS
Push with adb a Fire OS 4.5.5 to the sdcard
Or make a OTA over the WLAN from amazon?
Or (in the video says: NEVER touch the stock at Safestrap) Install a Fire OS bin in Safestrap to witch slot?
Click to expand...
Click to collapse
Excellent - glad to hear the progress!! However, there are some important changes needed that will greatly improve your CM11 experience (battery life, performance, stability). Some of this contradicts information in the video and recommendations from other versions of Safestrap.
The use of secondary slots is not recommended in Safestrap v4:
WiFi only works with CM11; Nexus v4 and Stock FireOS will fail to make a connection
Only 2 of 4 CPU cores are utilized resulting in poor performance under load
CPU runs at maximum speed at all times (no throttling) resulting in high battery use when idle
GPU does not throttle
Device never enters 'deep sleep'; radios remain active at all times
Backups can not be migrated between slots; flashing a secondary slot backup to the stock slot will brick device
Slot storage must be allocated in advance and can not be adjusted (must delete/recreate/reflash rom)
Recommended path:
Delete secondary slot (this will destroy your CM11 installation)
Flash CM11, GApps, SuperSu in stocki slot; this will overwrite FireOS in stock slot
This means your device will be running CM11 with no access to FireOS. However, if needed you can replace CM11 with FireOS 4.5.2 from this thread. Note the images are customized for Safestrap; flashing a unmodified stock image will brick your device.
Miscellaneous:
NEVER perform a 'factory reset' from the native recovery menu; your device will brick
Make a backup of the stock slot from within Safestrap (it will be large); move to a host PC for safe keeping
Always keep a flashable copy of CM11 image on the device (in the root of sdcard) for emergency recovery. Safestrap v4 can not communicate via wifi, bluetooth or tether. If CM11 fails to boot your only option is to reflash an OS (CM11, Nexus or FireOS) from within Safestrap recovery. If a Safestrap compatible/flashable image is not already on the device you can not recover from this type of failure.
Safestrap may appear to be a full blown recovery but it is actually a TWRP emulator that runs within the system partition and has dependencies on other Amazon components (bootloader, native recovery, etc) that remain on your device from the previous FireOS 4.5.2 installation. Be careful with advanced tools that run at a low level. It is possible to 'damage' your device to an extent that it can not be recovered. Ask first if uncertain.
questioning asking
This is so interesting. So sorry for my allways following questions. You said I should ask, but maybe also other can have a answer for me. This also cost your time.
So if you can't answer its ok. Or if there are only some hint words that will be a help for me to find out more. Whatever.
I am more than thankfull for that help to find out more about Android.
Davey126 said:
However, there are some important changes needed that will greatly improve your CM11 experience (battery life, performance, stability). Some of this contradicts information in the video and recommendations from other versions of Safestrap.
Click to expand...
Click to collapse
Ok, a next thing that i can search for.
I see some of my Apps close very often. Special Play Store
Davey126 said:
Delete secondary slot (this will destroy your CM11 installation)
Flash CM11, GApps, SuperSu in stocki slot; this will overwrite FireOS in stock slot
Click to expand...
Click to collapse
With secondary slot you mean the ROM Slot 1, cause the Stock will be the first slot maybe?
I don't will go back to the Fire OS cause i have a Fire TV Stick and a Raspberry for that. If i still think so in some months i also can flash the Stock Rom with a CM Image? But its not necessary cause i have my CM11 or maybe in the future CM13 in the ROM Slot 1. Or are they more reasons for that step?
Davey126 said:
NEVER perform a 'factory reset' from the native recovery menu; your device will brick
Click to expand...
Click to collapse
Whats do you mean special with "native recovery"?
That i start with the StockRom into my FireOS and after that i make a factory reset?
Davey126 said:
[*] Always keep a flashable copy of CM11 image on the device (in the root of sdcard) for emergency recovery. Safestrap v4 can not communicate via wifi, bluetooth or tether. If CM11 fails to boot your only option is to reflash an OS (CM11, Nexus or FireOS) from within Safestrap recovery. If a Safestrap compatible/flashable image is not already on the device you can not recover from this type of failure.
[/LIST]
Click to expand...
Click to collapse
I will do this! But...
I dont know, at this time, so much from safestrap. But i take look in it, and i can use ADB Sideload, Mount a USB Storage. Maybe also to reboot into the Download.
Is a push from adb or a Backup on a USB not also a way to restore a damaged Custom ROM.
Like
Start into Safestrap
Wipe my Slot with the CM11 or delete ist and create it again
Push with adb a new file of CM11, GApps, SuperSu into my data permission
And after that flash it to the Data Partition
Davey126 said:
[*] Safestrap may appear to be a full blown recovery but it is actually a TWRP emulator that runs within the system partition and has dependencies on other Amazon components (bootloader, native recovery, etc) that remain on your device from the previous FireOS 4.5.2 installation. Be careful with advanced tools that run at a low level. It is possible to 'damage' your device to an extent that it can not be recovered. Ask first if uncertain.
[/LIST]
Click to expand...
Click to collapse
How i can find out what Low Level tools are?
I think a recovery like TWRP is one.
I also use Tasker or BusyBox. They can make also deep things on my system. Also Low Level?
When ends the Low Level and start the Deep System?
Gatam77 said:
With secondary slot you mean the ROM Slot 1, cause the Stock will be the first slot maybe?
Click to expand...
Click to collapse
Yes - delete all ROM slots (1-n) that you created. Bottom line: you only want to use the Stock slot.
Gatam77 said:
I don't will go back to the Fire OS cause i have a Fire TV Stick and a Raspberry for that. If i still think so in some months i also can flash the Stock Rom with a CM Image? But its not necessary cause i have my CM11 or maybe in the future CM13 in the ROM Slot 1.
Click to expand...
Click to collapse
You do not want to maintain multiple slots (ROM images) in Safestrap v4. When you switch ROMs you overwrite the existing ROM in the Stock slot. You can overwrite CMxx with FireOS. At present CM12 and CM13 are not compatible with Safestrap v4. Do not attempt to flash any ROM image other than those specifically listed as "Safestrap Compatible".
Gatam77 said:
Whats do you mean special with "native recovery"?
Click to expand...
Click to collapse
"Native recovery" is the one supplied by Amazon accessible via <power> + <vol-up> from a cold start. NEVER use the 'factory reset' function from this menu when Safestrap v4 is installed; your device will brick.
Gatam77 said:
I dont know, at this time, so much from safestrap. But i take look in it, and i can use ADB Sideload, Mount a USB Storage. Maybe also to reboot into the Download. Is a push from adb or a Backup on a USB not also a way to restore a damaged Custom ROM.
Click to expand...
Click to collapse
None of these features work with Safestrap. Think of Safestrap as a virtual machine with ROMs running inside (technically inaccurate but conceptually convenient). You can only make full use ADB after portions of the ROM are up and running. If the ROM is damaged/unbootable you must do all repairs from within Safestrap. At present Safestrap v4 can not communicate with the outside world; all repair tools/images must be 'on board' (preloaded).
Gatam77 said:
Start into Safestrap
Wipe my Slot with the CM11 or delete ist and create it again
Push with adb a new file of CM11, GApps, SuperSu into my data permission
And after that flash it to the Data Partition
Click to expand...
Click to collapse
Probably repetitive but you do not want to recreate ROM Slot 1. Delete it and then flash CM11 (or Nexus v4 or FireOS) to the Stock slot.
Gatam77 said:
How i can find out what Low Level tools are?
I think a recovery like TWRP is one.
I also use Tasker or BusyBox. They can make also deep things on my system. Also Low Level?
Click to expand...
Click to collapse
- You can not use 'native' TWRP on your system as the bootloader is locked and can not be unlocked. Safestrap emulates TWRP.
- Tasker and BusyBox are fine
- Be careful with Xposed modules or other 'tweaks' that might cause your device to become unbootable.
Bottom line: enjoy CM11 and the apps that can be installed from the Play Store. Resist the temptation to customize further. If your device freezes or becomes unbootable you may not be able to recover.
Davey126 said:
Yes - delete all ROM slots (1-n) that you created. Bottom line: you only want to use the Stock slot.
Click to expand...
Click to collapse
Short Post
Oh my god. Again I trust a old Video. More later
So i install again.
First i make a backup (over WLAN) from my Stock Rom. I didn't get connection over USB at my PC neither connect a USB Stick to the Micro USB Slot. That's may what you mean that Sfestrap works like a virtual mashine.
So i CHECK if all files are at my root folder in the stock
After that i Wipe the Stock Rom
After that Flash all needed files and install like the last time but this time into the Stock Rom
Gatam77 said:
Short Post
Oh my god. Again I trust a old Video. More later
So i install again.
First i make a backup (over WLAN) from my Stock Rom. I didn't get connection over USB at my PC neither connect a USB Stick to the Micro USB Slot. That's may what you mean that Sfestrap works like a virtual mashine.
So i CHECK if all files are at my root folder in the stock
After that i Wipe the Stock Rom
After that Flash all needed files and install like the last time but this time into the Stock Rom
Click to expand...
Click to collapse
Good! Please confirm that you are now running CM11 in the Stock slot.
Assuming 'yes' you can (and should) remove all other slots if still present. Benefits:
- recover 3-4 Gb of permanent storage on your device and return it to the stock slot
- avoid potential confusion while in Safestrap recovery which could possibly lead to a bricked device
Once everything is stable boot into CM11 and move the large backup files to a host via tether (fastest), WiFi or Bluetooth. You do not need to keep backups on your device for recovery purposes; only the smaller ROM image.
You can not attach a flash/thumb drive or any other USB device (including keyboards/mice) to the micro-USB port as HDX devices lack OTG support at the hardware level. An unfortunate design choice by Amazon and can not be fixed via software or special cables.
Keep in mind the HDX is a sensitive device. After flashing a ROM there rarely a need to return to the Safestrap recovery environment. Exceptions:
- flash a newer version of ROM (release release notes carefully)
- make periodic backups of your existing system and data partitions
Davey126 said:
Good! Please confirm that you are now running CM11 in the Stock slot.
Click to expand...
Click to collapse
I will do. At the moment it is still in Slot 1 and i recharge battery to 100%.
Maybe tomorrow . Because there is no video with this, i try to make a movie while making all this steps.
Assuming 'yes' you can (and should) remove all other slots if still present. Benefits:
- recover 3-4 Gb of permanent storage on your device and return it to the stock slot
Click to expand...
Click to collapse
So i Flash my CM11 to the Stock Rom. And AFTER That i remove the other Slots.
After that I can recover storage back to the Stock ROM?
You do not need to keep backups on your device for recovery purposes; only the smaller ROM image.
Click to expand...
Click to collapse
After all works with the Custom Rom on the Stock Rom, i leave the ZIP file on my device after the flash. All other like GAPPS i also can thether later, if i need this again.
Gatam77 said:
So i Flash my CM11 to the Stock Rom. And AFTER That i remove the other Slots.
After that I can recover storage back to the Stock ROM?
Click to expand...
Click to collapse
Correct. Although the goal is to delete all secondary (non-stock) slots there is no benefit to removing the slot that is currently hosting CM11 until you have confirmed the reflash of CM11 to the stock slot. This leaves you with a working ROM should something go wrong.
An 'idle' secondary slot does not present a problem just being there. However, it consumes considerable space and increases the possibility of making a fatal mistake while working in Safestrap recovery. Ultimately the decision is yours whether to keep or discard secondary slots. However, you want your primary slot to be stock. Hope this makes sense.
Gatam77 said:
After all works with the Custom Rom on the Stock Rom, i leave the ZIP file on my device after the flash. All other like GAPPS i also can thether later, if i need this again.
Click to expand...
Click to collapse
Correct.
Want to update to CM13? Read this first!
Welcome to my upgrade guide that will allow users to painlessly upgrade from an earlier version of android to CM13.
Background info:
Our Cyanogenmod maintainer, Lysergic Acid, started bring alpha builds of Cyanogenmod 13 since October of last year. Now, we have official nightlies on our device which just proves how strong of a device we have and how strong we are as a community on XDA. With all of the exciting new features Marshmallow brings to the table, people have been flashing CM13 without reading any precautions or information about the possible consequences of not doing a particular step or procedure. With this guide, you will learn how to successfully flash CM13 on a device, everytime!
This guide will assume you are on a rooted custom ROM with a working custom recovery. It will not guide users how to update from stock ROM to CM13. If you haven't rooted your phone yet or are on stock ROM, use a different guide to install a rooted custom ROM (KK or LP preferred) then follow this guide.
Another important tip is to read the issues post before flashing the latest build of CM13. There could be issues that you could encounter so make sure to read before flashing!
How to install:
CM13 is available to install for CM12.1 users via the OTA updater. However, updating to CM13 via OTA updater is buggy and will remove gapps and Isorec Recovery. If you receive notifications about the CM13 update, don't use the OTA updater! Use this guide below instead.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the upgrade process or you don't like CM13 in general. If you are using Cyanogen recovery from CM12.1, you should flash a isorec recovery from this thread. TWRP or CWM are both fine. Note: If you are using a build earlier than 20160119 nightly or not using one of Lanchon's isorec kernels, you will not be able to use a isorec recovery. This will not apply to people on older versions of android (for older versions of android, KK compatible recovery or higher is all you need).
If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section. It is required for users to re-partition their system partition to 1GB to prevent issues when flashing gapps. Please also note that when upgrading from an older ROM, you must flash a newer Gapps to keep Gapps on your phone.
Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
If you are in CWM, while on the main menu, choose factory reset. Then go into mounts and storage and select format system. If you are in TWRP, go into the wipe menu, select advanced wipe, check wipe system, data and cache, then swipe the bar to wipe.
Flash the CM13 zip.
(Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
(Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken.
I will repeat what I said earlier but with more explanation. Why don't I have a guide on how to update to CM13 via OTA? OTA update from CM12.1 to CM13 is broken! You will lose gapps and it will cause a lot of problems to user. Just follow the above guide to flash update manually and no issues will be encountered.
Gapps on Android Marshmallow:
Recommended Gapps: OpenGapps Pico
What to select on OpenGapps page: ARM>6.0>Pico
While flashing Gapps is an optional step during the upgrade process, many people require the Google Play store to install all of their apps. It is required for people who want to flash gapps to increase their system partition to 1GB (or more). Stock partition sizes have a system partition size of about 500MB which is not enough to hold even the smallest gapps packages available!
Re-partition guides
You can re-partition your device by following my guide (Requires PC): http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
If you have working recovery, use Lanchon's guide (second link). Otherwise, my guide (first link) will work for everyone else.
Please note that re-partitioning your device via ODIN (first link) will delete all of your data, including your internal storage which contains all of your personal files. You must backup all of your files to an external sd card or PC if you want to keep them! However Lanchon's guide (second link) keeps all of your personal data but requires a working custom recovery!
Please also note about the naming of the zip/pit files!
If you get error 70 while flashing Gapps, make sure you are using the re-partition guides properly, you may have missed a step or forgot to do something. If you didn't bother reading all of the information I've given and decide to post about your error, you will be told to read the information properly and nothing else. All help was given already If you get some other error, read the OpenGapps FAQ.
Stock Cyanogen Recovery:
CM13 Stock Cyanogen Recovery is a basic recovery that allows you to flash zips from your internal and external sd storages. It provides wipe options and ADB flashing support, but was only designed to provide the basic tools for flashing. Although it works fine in recent builds of CM13, it is highly recommended that you use an Isorec Recovery like TWRP.
Update: Cyanogen recovery has fixed mounting support for internal and external sd as of the 5th of October nightlies. The steps below now only apply to people who want to use older CM13 builds.
If you have build 20161005 or later, you can now easily switch to an Isorec recovery simply by flashing it via Cyanogen recovery. You can not do this in older builds!
Isorec install on builds older than 20161005
1. ADB Sideload Method (requires PC)
This is the easiest and quickest method to restore Isorec Recovery on your device. However it will require ADB/Fastboot tools to be installed on your computer. You also need to enable ADB debugging and enable root access for ADB in the development settings to use this method. If you don't have ADB/Fastboot tools installed, download it from this thread
Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
Reboot your phone into Cyanogen recovery
Select apply update from ADB sideload
In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
Select open command line menu here
Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
Cyanogen recovery should begin flashing TWRP recovery
Once completed, reboot your device
2. ODIN method (requires PC)
This method requires ODIN to be installed on your computer. You will be connecting your phone to the computer which may or may not be a problem for some users.
Put your phone into download mode (Power key, home button, Volume Down button)
Connect your phone to your PC
Open ODIN. Make sure that it detects your device. If it doesn't, check if you have the right drivers installed and if the usb cable/port is damaged
Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4 Don't worry if it isn't CM13 kernel, you will have to reflash CM13 anyway! If you don't know which one to choose, the TWRP CM12.1 kernel is fine.
Select the CM12.1 kernel as PDA (or AP)
Make sure you untick auto-reboot
Start the flash.
Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
Get into recovery mode (Volume Up, Power Key, Home button)
Repeat CM13 flashing guide above without any backup.
If you have linux, use JOdin instead of ODIN.
3. Terminal method (Doesn't require PC)
This method requires a terminal emulator. Either download one from the google play store or enable the in-built terminal emulator in development settings. Follow the guide carefully. You can use this method if your USB port is broken.
See Lanchon's post: http://forum.xda-developers.com/showpost.php?p=65164875&postcount=1002
As mentioned in Lanchon's post, IF YOU MAKE A MISTAKE IN ONE SINGLE CHARACTER YOU TYPE IN THE TERMINAL, YOU COULD BRICK YOUR PHONE FOREVER!!!
Root on Android Marshmallow
CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.
You may be familiar with the root tool, SuperSU, and it may have been installed in CM12.1 or earlier versions of android. Android Marshmallow has a different way of rooting the device. It is not compatible with older versions of root.
Currently, SuperSU doesn't work on CM13. Do not attempt to install it with system method and don't try to install it with systemless method.
How to update to a newer build of CM13
1. OTA Updater method
This method of updating Cyanogenmod is usually preferred by many users because it is ready-to-use and is quite simple to do.
Go into settings>about phone>system updates
If there is a new build available, press the download button. The OTA updater will now download the update to your phone
Once it finishes downloading, it will prompt you if you want to install the update. Confirm that you want to update and your phone should restart
Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
2. CyanDelta Update method (Popular method)
This method of updating Cyanogenmod is most beneficial to people who want to save bandwidth and/or want to download the update via their mobile data. This method typically saves around 200MB of data which makes it a quick way of updating, without sacrificing stability.
Download Cyandelta from the google play store
Download from CyanogenMod website the .zip file of the ROM you are using. Please note that if you haven't saved a copy of your current build onto your phone, the Cyanogenmod Downloads server usually deletes old nightlies. Update: The Cyanogenmod downloads page is gone, instead download from here.
Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
If you are stuck using the CyanDelta update method, check out their FAQ on their website.
3. Manual method (Recommended)
If you have issues using the other methods to update CM13, you can also install the update manually via recovery. This method usually has the greatest success rate.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the update process. If you don't have Isorec TWRP or CWM, use the guide above to reinstall CM13 with a working recovery!
Download newer CM13 build from the official cyanogenmod downloads page onto your phone. Note: Old cyanogenmod nightlies are usually deleted from the Cyanogenmod server if you haven't downloaded your current build onto your phone yet. Update: The Cyanogenmod downloads page is gone, instead download from here.
Flash the CM13 zip
Wipe cache
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken. If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
New users are encouraged to post questions about CM13 here and not in the CM13 Development thread, this will leave everyone happy and everyone gets what they want
Thanks to Lysergic_Acid for CM13, Cyanogenmod team, CyanDelta team, arnab for his TWRP isorec recovery, Lanchon for his Isorec kernels, repartition script, Isorec recovery and guides.
Updated on 02/02/17
Since the wiki for our device hasn't been updated yet, here are a list of some issues on CM13:
Issues marked with red are recent issues you will experience in any current build of CM13.
Ongoing issues:
MX Player can not use HW+ decoder. Instead, use HW or SW decoder. The developer of MX player is working on a fix.
Cyanogenmod OTA Updater sometimes can be buggy. MD5 errors, download errors, installation errors. Although it is working fine for most people, I still recommend just to flash manually via recovery!!!
Internal storage and external storage is not labelled correctly and has a random name. This is not a bug but a feature of one of the mounting ways of MM.
Screenrecorder works for some users, however it seems that you can not playback them on your phone. Workaround: Play the videos using your PC.
Some apps may have trouble detecting internal/external storage.
Some bluetooth devices may not behave properly or connect
Multiple issues with F2FS. Please note that this FS is still relatively new for our device so bugs are likely to be experience. Stay on ext4 for best stability!
Some people have reported that they have lost connection to their mobile network. This usually can be fixed by resetting APNs. If this doesn't help, you may need to downgrade back to stock 4.1.2 ROM.
MMS video file (.3pg format) will not play on the default video player. Workaround: Play the video through MX Player on SW renderer.
Hardware button is always on until screen is switched off. Workaround: After installing the BLN MOD and synapse, you can control the timeout values.
You may experience reboots when you receive phone calls
More to be added later
Fixed issues:
(from latest issue solved to earliest)
Cyanogen Recovery can not mount internal and external storage. You can not flash zips via internal or external storage. ADB sideload or other methods of flashing can be used instead. Fixed in nightly 20161005
Battery Percentage Incorrect and Causing Constant Low Battery Warnings. Fixed in nightly 20160818
As of the 20160722 nightly, decryption of /data partition is broken. Keyboard can't be switched to enter digits. Fixed in nightly 20160724
As of the 20160722 nightly, setup wizard is broken. When you press next, the notification bar drops down instead of the next screen showing. Fixed in nightly 20160724
Some people have reported that the youtube app (play store version) displays green lines during playback.
Front camera errors in recent builds
Phone dialer is currently broken Workaround: Use google dialer from Google Play Store
Live lockscreen has multiple issues being experienced in recent builds.
Nightly 20160326 is experiencing Google Play Launcher FCs. Please stay on a earlier build until this is fixed. Fixed in nightly 20160329
People who are using a non-english language may experience Clock app FCs. This problem is under investigation. Update: Fixed in nightly 20160325
Doze feature can not optimize any apps. This is not a bug, doze is disabled on our device! Please ignore this menu! Update: Fixed in nightly 20160325. Note: This is the app standby feature that is now working and not motion sensor doze!
Nightly 20160323 is experiencing CM file manager FCs Fixed in nightly 20160325
Nightly build 20160216 is currently affected by the no signal bug and dialer issues. Update: Calling issues have been fixed in nightly builds 20160218 or newer. If you are on build 20160216, you should update immediately to fix this issue.
FAQ
Q: What is cyanogenmod?
A: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device. CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Q: What version of android is CM13 based on?
A: Android Marshmallow 6.0.1
Q: What is Gapps?
A: Google Apps (Gapps) is an app package containing the Google Framework which is required for most apps from Google to function. This will include the Google Play Store and other Google apps and services depending on what setup you select (it varies on what Gapps package you select, I recommend OpenGapps).
Q: Is this ROM pre-rooted?
A: CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for adb too because this can help you recover from some problems that may occur in the future.
Q: I get error 70 when flashing gapps. What can I do to solve it?
A: Error 70 means that you have insufficient space available in the system partition. Your device does not have sufficient space available in the system partition to install the Open GApps package. As I have said in my guide, you will need to repartition your system partition using one of the links in the gapps installation section of my guide. Then only you will be able to install gapps on your phone.
Q: Help me! My phone says that sdcard0 is corrupted! What can I do to solve it?
A: If you've re-partitioned your device recently using the ODIN method, it is highly likely that you forgot to format your internal sd card. You can do this in the recovery by selecting sdcard0 or internal sd, format as vfat (fat) or default (CWM). Alternatively, you can use your computer to format it manually by mounting your phone's storage via recovery then using a formatting utility such as the built-in windows formatting tool.
Q: Does xyz app work with CM13?
A: I don't know. Check the app's website, check the google play store, check other users comments. Google is your best friend. If not, try it out for yourself! Some apps require selinux to be set to permissive, you can do this in apps like SELinuxModeChanger.
Q: Does SuperSU work on CM13?
A: While there are ways to get SuperSU working, this guide is only here to provide basic procedures. I do not recommend new users to install SuperSU on any Android 6.0 ROM.
Q: My apps that require root say that I need busybox to use the app. What should I do?
A: You do what it tells you to do. Download busybox installer from the app store, install busybox and your app will hopefully work as it should.
Q: What happened to busybox? It was available on older android versions but why do I have to install it myself on CM13?
A: Busybox was replaced with toybox in CM13. As a result, you can not run apps that require busybox so you need to install a busybox installer from the google play store.
Q: Does GPS work well on CM13?
A: Reports have shown that GPS is still not reliable like in CM12.1.
Q: Does CM13 have Isorec Recovery Support?
A: Yes, it does. However CM13 comes with CM recovery as the default recovery.
Q: Does xposed work on CM13?
A: Yes it does. Use the latest installer (xposed-v80-sdk23-arm or newer) and make sure selinux is set to permissive.
Q: Which is better, CM13 or CM12.1?
A: CM13 is still new for our device. Naturally, there will be bugs experienced by users. Over time, the ROM will mature and it will become stable for everyone to use. Try it out for yourself and see which one is best for you
Q: Can I install CM13 on {different S2 model}?
A: If it is just a carrier/region variant of the international s2 i9100, it should work without problems. If it is different physically (hardware), then it will not work!
Q: Battery life sucks on CM13! What happened to doze mode?
A: Our device lacks the (low power) sensors that take advantage of this feature, therefore making it useless so it was disabled. Don't forget our device (s2) is quite old now, it shouldn't be a surprise that we can't take advantage of new features like this.
Q: Battery life sucks on CM13! (General)
A: Download and install betterbatterystats onto your device. Check what app is the culprit to your poor battery life. If there are no apps that are behaving strangely, try reflashing your current ROM and making sure to factory reset and format system partition. A lot of battery problems are created by the user, maybe brightness is set too high, change the screen timeout delay, etc.
Q: Can I update to CM13 without a computer?
A: Yes you can. I have included guides/steps that are not computer dependent if you haven't noticed already. If you have a broken USB port, you need to get it fixed ASAP because if anything happens during the flashing process, your phone is useless!
Q: My device runs slow on CM13. Can I do anything to make it go faster?
A: Make sure to close all apps that are not needed. Change swappiness to a lower value or 0. Change CPU governor parameters: Up threshold, sampling rate. Make these values smaller to give more performance. Remove apps that may be hogging up your CPU/RAM. Reboot, it helps
Q: What does android security patch level mean?
A: Google regularly updates their newer android versions with security fixes. Cyanogenmod will apply those fixes to their ROM so you will stay protected as well.
Q: Why is xyz feature not available in CM13 when it was available in CM12.1?
A: It is a good possibility that Cyanogenmod are not ready to add the feature yet. It could still need more internal testing or other more important features have to be added first for adding it to the ROM.
Q: Why can't I install gapps?
A: Now before you post this, have you read the post given by the users on the CM13 thread? I have said in my guide that in order to flash gapps, you will need a larger system partition. Please re-read the guide and make sure to read carefully before posting questions.
Q: What is BLN?
A: BLN (Backlight Notification) is a feature which uses your phone's hardware button lights to notify you whenever you receive a notification such as SMS, email, etc.
Q: How do I use BLN?
A: BLN is disabled by default. You need to use Synapse to configure it. See this thread
Q: How do I change the behavior of BLN?
A: See this thread
Q: Will BLN drain my battery?
A: BLN (not BLN without wakelock) prevents your CPU from going to deep sleep mode (low power CPU mode to save battery) which will drain your battery quicker versus having it disabled. Lighting up your hardware buttons will also use a little more power, so please take these factors into account before posting about poor battery life.
Q: Why is my button backlight always on?
A: See this thread
Tuning guide
For performance
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Change CPU governor to PegasusQ
Change swappiness to 20
Change I/O scheduler from CFQ to Deadline
Decrease CPU governor sampling rate to 40000
Decrease CPU governor up threshold to 60
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Change entropy read threshold to 512 and write threshold to 256
Disable entropy for internal and external sd
Disable iostats for internal and external sd
For battery life
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Kernel Adiutor
Change CPU governor to PegasusQ
Change swappiness to 40
Change I/O scheduler from CFQ to SIO
Increase CPU governor up threshold to 90
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Decrease vfs cache pressure to 60
Change entropy read threshold to 512 and write threshold to 256.
Disable entropy for internal and external sd
Disable iostats for internal and external sd
Greenify
Enable aggressive doze (beware, you may lose notifications!)
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
rolves1899 said:
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
Click to expand...
Click to collapse
Repartition is highly recommended, otherwise you will have a hard time finding a gapps package that will work. Use lanchon's guide linked in the OP now that you have a working recovery.
gsstudios
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Draky50110 said:
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Click to expand...
Click to collapse
You have good luck then However, it still needs to be worked on.
Although it is not required to reflash isorec, I include it anyway in the steps to prevent issues that may occur anyway. That way, users are 100% sure that they don't end up with cyanogen recovery.
gsstudios
stylemessiah said:
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Click to expand...
Click to collapse
Thanks, will add this to the guide soon.
gsstudios
Thanks for your work and this nice guide.
In this guide in the repartition part where is instructed
to flash kernel with ODIN, i would instruct to set the option
for AUTOMATIC RESET after flash to OFF, and pull battery after flash.
Because the flash happens so quickly and its a little difficult to
do the 3-finger boot then.
Best regards.
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.
I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.
I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.
So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?
Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?
I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
OP updated with recommendations from other users. Thanks for the suggestions!
Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.
gsstudios
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
fireburner-de said:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
Click to expand...
Click to collapse
Already in the OP. It is the second link for the repartition section
gsstudios
AT LAST ! Now they will not spam the official thread of cm 13!
gsstudios said:
Already in the OP. It is the second link for the repartition section
gsstudios
Click to expand...
Click to collapse
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
UsualSuspectReaL said:
AT LAST ! Now they will not spam the official thread of cm 13!
Click to expand...
Click to collapse
I fear, they still will
fireburner-de said:
Well I know, that the link is there. Just 2 lines after the links you write in read that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
I fear, they still will
Click to expand...
Click to collapse
Yes, I forgot to change that. Updating now... I read your post wrong
gsstudios
Edit: Done. Thanks!