Related
Is there any site or source on the web that provides downloads of old versions of Android Market apps? This would be for apps that are now updated or no longer available on the Market? I am looking for a site similar to "OldVersion.com" which has some old/classic PC software (but this would be something for android apps instead)?
Thanks if anyone knows of a source or sites.
CustomShortcut gone?
The app that I am looking for in the above post was a free one called CustomShortcut APK. I now have it on one of my two phones (the other phone had it but was lost and replaced). I have tried looking for a developer page for this app but no luck as everything seems to point back to android market as the source link for download.
Does anyone know of a way or source for me to get this APK back on my other phone? Is there a way to copy it from one phone to the other? I am assuming that it was removed from the market because it may not be compatible with ICS but I am not running ICS. The application was made by appli.club.
Are you rooted? If so use root explorer to look for the .apk in the /system/app folder and copy or email it to the other phone and install it.
85gallon said:
Are you rooted? If so use root explorer to look for the .apk in the /system/app folder and copy or email it to the other phone and install it.
Click to expand...
Click to collapse
No sadly I am not rooted. Is that how this could be done? I have an HTC phone (Sensation) and I like my "sense" gui. Don't want to wipe it out by rooting (that is what would happen, right?) If access to the apk is possible with rooting, then I guess my question would be, does anyone else here have CustomCut on their rooted phone? (Or possibly know of any website that would have those apk's available for download). I would be willing to pay if someone would take the time to send me a replacement copy.
just google for any app you want like this:
"title" "versionnumber" "apk" "download"
for example:
android market 2.9 apk download
mojosingle said:
No sadly I am not rooted. Is that how this could be done? I have an HTC phone (Sensation) and I like my "sense" gui. Don't want to wipe it out by rooting (that is what would happen, right?) If access to the apk is possible with rooting, then I guess my question would be, does anyone else here have CustomCut on their rooted phone? (Or possibly know of any website that would have those apk's available for download). I would be willing to pay if someone would take the time to send me a replacement copy.
Click to expand...
Click to collapse
Rooting will not wipe out your phone or change it other than giving you super user privileges. That way you will have access to get to the system apps folder.
I notice apktop keeps old versions around. But part of the reason I like Titanium backup is because I have a fail safe if a new update to an app is bad, as I can just restore from the last backup the older version.
85gallon said:
Rooting will not wipe out your phone or change it other than giving you super user privileges. That way you will have access to get to the system apps folder.
Click to expand...
Click to collapse
Well I am not really too concerned about it wiping out my phone, but I thought I had read many posts here talking about once you root your phone the native skin from the manufacturer is eliminated (for HTC that would be the "Sense" user interface). Can you please confirm? Is this not true? HTC Sense will remain exactly the same after rooting my phone?
The other thing that has made me cautious is that my phone runs perfectly now and I see so many threads on the xda boards here and over at various android forums that start off with "My ____ app is not working right since I rooted...." Just a little daunting for a newbie like myself.
spunker88 said:
I notice apktop keeps old versions around. But part of the reason I like Titanium backup is because I have a fail safe if a new update to an app is bad, as I can just restore from the last backup the older version.
Click to expand...
Click to collapse
Thanks very much for the site suggestion. I have been trying to search for the CustomShortcut APK over there but no luck ...so far (the site search is not that easy to use). I have even tried to seach the site externally using google but, unfortunately, still no luck.
Wait for someone else to confirm on the htc, but nothing changed on my droidx. I just had superuser privs. All of the "this app quit working" is when people flash custom roms. You don't do that when you just root. But you have to be rooted in order to do things like that. Lol.
Rooting gives you the power to do that if you want to.
When I rooted my droidx, I did it just so I could have the power to do other things if I wanted. I am still on factory rom. But I am able to get to parts of the phone that are off limits if I wasnt rooted. I made it where I could tether, later I got rid of bloatware, etc.
85gallon said:
Wait for someone else to confirm on the htc, but nothing changed on my droidx. I just had superuser privs. All of the "this app quit working" is when people flash custom roms. You don't do that when you just root. But you have to be rooted in order to do things like that. Lol.
Rooting gives you the power to do that if you want to.
When I rooted my droidx, I did it just so I could have the power to do other things if I wanted. I am still on factory rom. But I am able to get to parts of the phone that are off limits if I wasnt rooted. I made it where I could tether, later I got rid of bloatware, etc.
Click to expand...
Click to collapse
Thanks once again for the reply. Now that you mention it, I remember reading the terminology "flashed" rom and thought they were similar or the same thing as rooting. One other question, once a phone is in a rooted state, if I was to go in and copy the APK for my replacement phone and put it on there could I then "unroot" lol ...sorry if this is not a word... so that my phone was no longer open? I had read somewhere (perhaps I heard it on a TWIT or Android podcast) that when your phone is in root state that anyone (ie: potentially bad software) has easier access to your phone's vunerable areas.
mojosingle said:
Thanks once again for the reply. Now that you mention it, I remember reading the terminology "flashed" rom and thought they were similar or the same thing as rooting. One other question, once a phone is in a rooted state, if I was to go in and copy the APK for my replacement phone and put it on there could I then "unroot" lol ...sorry if this is not a word... so that my phone was no longer open? I had read somewhere (perhaps I heard it on a TWIT or Android podcast) that when your phone is in root state that anyone (ie: potentially bad software) has easier access to your phone's vunerable areas.
Click to expand...
Click to collapse
yes you can unroot. As for easy access after you are rooted to vulnerable areas, they can only get access if you let them. If an app wants super user privileges, you will get a pop up from su(the super user apk) telling you that some app is wanting privileges. You can grant or deny access. The only things on my phone that have ever given me a pop up are things that i downloaded and know need su access. Wifi tether, root explorer, adfree, etc.
I have found a site that keeps older version of an android app. It's called Android Drawer.
Hope it helps
I have multiple questions pertaining to root and ROMs, any advice on any one of them would be appreciated. My questions surround a Samsung Galaxy S 4G, and a Nexus 7 (2012).
Samsung Galaxy S
ROM Manager
The SGS4G XDA forums have coined it as the "ROM Mangler", my model of Galaxy S is not a compatible device. However, every ROM I've flashed so far has included Clockworkmod5 or Clockworkmod6 (which are only accessible through Recovery). I naturally want to use this app to manage my ROMs on this device, but am wondering if I should or if I will be able to?
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
I read a comment from a guy on Youtube that said he rooted his Nexus 7, but eventually received a software update from Google. He said he had to re-root his device after this. I am assuming the notification never went away, and he decided to install the update. How would I prevent something like this from happening? Should I install a ROM immediately after rooting??
Internal Storage
My Nexus 7 doesn't have an SD card, but has 32GB of internal storage space. My file explorer shows that the device has an 'sdcard' folder, but wouldn't that folder be wiped if I decided to root and flash a ROM on this device?? How would I prevent this scenario from happening?
General
Busybox
What is Busybox, and should it be installed? I watched a Youtube video suggesting to install it anyway, but I highly doubt I will ever use or need it. After rooting my Galaxy, I noticed Busybox was automatically installed. However after flashing several ROMs, I notice that some of them don't come with Busybox pre-installed.
Cyanogenmod
I currently have an unofficial Cyanogenmod 10.1 (w/Android 4.2.2) ROM installed on my Galaxy. But what is Cyanogenmod exactly, and why is it a big name in the ROM community? I've heard a lot about AOKP too.
SuperUser
My current ROM is missing a Superuser app. Should I install a Superuser app, and does it matter which one I choose?
If a Superuser app has already been pre-installed with a ROM, is updating to the Play Store version a good idea? Are there any consequences to installing a different superuser like Super SU or SuperUser from Clockworkmod? Is uninstalling one Superuser for another a good idea?
bump
Double44 said:
I have multiple questions pertaining to root and ROMs, any advice on any one of them would be appreciated. My questions surround a Samsung Galaxy S 4G, and a Nexus 7 (2012).
Samsung Galaxy S
ROM Manager
The SGS4G XDA forums have coined it as the "ROM Mangler", my model of Galaxy S is not a compatible device. However, every ROM I've flashed so far has included Clockworkmod5 or Clockworkmod6 (which are only accessible through Recovery). I naturally want to use this app to manage my ROMs on this device, but am wondering if I should or if I will be able to?
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
I read a comment from a guy on Youtube that said he rooted his Nexus 7, but eventually received a software update from Google. He said he had to re-root his device after this. I am assuming the notification never went away, and he decided to install the update. How would I prevent something like this from happening? Should I install a ROM immediately after rooting??
Internal Storage
My Nexus 7 doesn't have an SD card, but has 32GB of internal storage space. My file explorer shows that the device has an 'sdcard' folder, but wouldn't that folder be wiped if I decided to root and flash a ROM on this device?? How would I prevent this scenario from happening?
General
Busybox
What is Busybox, and should it be installed? I watched a Youtube video suggesting to install it anyway, but I highly doubt I will ever use or need it. After rooting my Galaxy, I noticed Busybox was automatically installed. However after flashing several ROMs, I notice that some of them don't come with Busybox pre-installed.
Cyanogenmod
I currently have an unofficial Cyanogenmod 10.1 (w/Android 4.2.2) ROM installed on my Galaxy. But what is Cyanogenmod exactly, and why is it a big name in the ROM community? I've heard a lot about AOKP too.
SuperUser
My current ROM is missing a Superuser app. Should I install a Superuser app, and does it matter which one I choose?
If a Superuser app has already been pre-installed with a ROM, is updating to the Play Store version a good idea? Are there any consequences to installing a different superuser like Super SU or SuperUser from Clockworkmod? Is uninstalling one Superuser for another a good idea?
Click to expand...
Click to collapse
To answer your questions:
Samsung Galaxy S
ROM Manager
ROM Manger has been buggy for a while now and can cause a lot of problems on certain devices, I would personally avoid it for the time being. That being said the best way to manage your ROM's (And any other Kernel, or MOD's you may want to flash) is too boot your device into recovery mode by using the key combination described in this post, or by running the following command from ADB on your computer:
Code:
adb reboot recovery
Once in recovery, you can flash any ROM that you pushed to your phones sdcard. Make sure to always perform a NANDROID backup of your current setup in recovery mode, before installing a new ROM, Kernel, or other MOD (Such as editing your build.prop file). Also before flashing anything in recovery make sure it is intended for your device and that you read and re-read, and re-read again the instructions on how to properly flash the file.
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
It is always assumed that any OTA update you apply will break root and that you will have to re-gain root access by re-rooting your device. You can disable OTA updates a couple of different ways. One method is to use an app such as FOTAkill to prevent OTA updates from happening. Another method is to use an app such as Titanium Backup to freeze and disable certain system apps that control OTA updates from being sent and received. Lastly, you can install a custom ROM to prevent OTA updates from being pushed to your device.
Internal Storage
This is a great question. The way the Nexus 7 and other devices that don't have an actual physical sdcard slot handle this is the sdcard folder you see in the file explorer acts as an emulated sdcard. So this way when you go to install a custom ROM in recovery mode when the ROM installation requires you to wipe everything the contents of the emulated sdcard will be untouched and remain as if it were a actual physical sdcard.
General
Busybox
Busybox is a series of stripped down GNU utilities and command line applets, you can find more about Busybox and what it is here. As far as needing it in the beginning you might not need it but as you get more familiar with modifying devices is comes in very handy for performing certain operations and tasks and is worth installing just to have for it's functionality. A lot of root programs push the su binary, a Superuser.apk, and often times the busybox binary. Not all ROM's choose to include busybox but it's handy to have like I mentioned for it's functionality.
Cyanogenmod
Cyanogenmod is an aftermarket firmware distribution you can find more about it here. As for why is it famous it was one of the first well know custom ROM's and soon grew to include support for a vast amount of devices you can find more about the history of Cyanogenmod here. AOKP is another well know ROM that stands for Android Open Kang Project, it first came about when Android 4.0 Ice Cream Sandwich was released you can learn more about AOKP here.
SuperUser
If your current ROM is missing a Superuser app you may install one from the Play Store, it does not matter which one you choose it is personnel preference but I would use either Chainfire's SuperSU app or Koush's Superuser app. Updating a pre-installed Superuser app to the latest Play Store version is fine. There are no consequences to installing one Superuser app and uninstalling another one it's a matter of personnel preference which one you want to use. Keep in mind if you uninstall one Superuser app and then install a different one it may ask you to update the su binary (Which it should ask you if you want to do that once you launch the app for the first time) before it will function properly.
If you have any other questions let me know I'll be happy to answer them or elaborate on anything that may still be unclear to you.
After a few torturous months on a Note 3 (screw AT&T for locked boot loader!), I've decided to switch back to the glorious M7. In the meantime, I've started new job which requires usage of Good for Enterprise. I've been a CM nightly junkies when I was using the M7 but with this email client that won't work with root, I'd like to see if anyone else has experience and effective strategies to work around the root detection.
From researching on other forums, it seems like removing SU, busybox, com.noshufou.android.su, and XBIN folder then GFE should work. That is a bit of work to do it every day though. Has anyone tried simpler something like Hide My Root and would that get past GFE root detection?
lc084302 said:
After a few torturous months on a Note 3 (screw AT&T for locked boot loader!), I've decided to switch back to the glorious M7. In the meantime, I've started new job which requires usage of Good for Enterprise. I've been a CM nightly junkies when I was using the M7 but with this email client that won't work with root, I'd like to see if anyone else has experience and effective strategies to work around the root detection.
From researching on other forums, it seems like removing SU, busybox, com.noshufou.android.su, and XBIN folder then GFE should work. That is a bit of work to do it every day though. Has anyone tried simpler something like Hide My Root and would that get past GFE root detection?
Click to expand...
Click to collapse
You could create two scripts that you could keep stored in the phones memory. One script will remove the files and place them in a temp location. The other script will put the files back in their proper location when you are not at work.
There is an xposed module that, rootcloak I think it is that will make the app think you're not rooted
Sent from my HTC One using XDA Premium 4 mobile app
RootCloak used to work until recently. As far as I can tell, it might have stopped working after the most recent SuperUser update, because I don't recall installing a Good for Enterprise update.
Thanks for the responses. I'll try to remove those files before installing Good for Enterprise. Trying not to tip off IT that my phone isn't stock.
I haven't not gotten around to switch back to the M7 since I made up my mind to do it. Work has finally slowed down a little so I read up on the instructions again and there are a few points that I'd like to see if someone is kind enough to clarify for me.
Here are the instructions I found on mydroidworld forum for the Droid X by _Matt (http://www.mydroidworld.com/topic/7904-good-for-enterprise-work-around/:
"1. INSTALL Good For Enterprise Last, its the last thing you install.
2. Be sure DX2 Boot Strap is installed.
3. ROM and setup your phone however you want.
4. Create a backup just in case
5. remove these files, SU, BUSYBOX, com.noshufou.android.su, XBIN Folder
6. Reboot
7. Install GFE and activate
8. If you need to make O/S changes learn how to make flashable .ZIP files through bootstrap. Works perfectly and I have no issues with GFE.
If you change ROM's you will need to do these steps to keep GFE working.
1. In GFE app turn off persistent mode.
2. Go Offline
3. Quit app
4. Install Root.zip that you made before unrooting
5. Freeze or back up GFE with Titanium back up
6. ROM your device
7. set it up
8. restore apps
9. remove these files, SU, BUSYBOX, com.noshufou.android.su, XBIN Folder
10. Reboot
11. Start GFE"
On the first set of instruciton, what is the equivalent for the second point "Be sure DX2 Boot Strap is installed." on the M7? And on point 8, what is does it mean by making .ZIP files through bootstrap?
I'm guessing point 4 in the second set of isntruction is to flash the zip file through a custom recovery. Am I correct in thinking that? Thanks for the help!
I'm guessing boot strap is an old recovery. All the readings I could find are from a few years ago.
So I think it's using a custom recovery to make a backup before installing GFE for the first time, do all necessary changes, remove the files related to root then install and activate GFE.
When it's time to change ROM, completely shut down GFE, flash the rooted backup, freeze/backup GFE with titanium backup, flash new ROM, remove the root files again, restore GFE.
Am I on the right track about this? If that's how it's supposed to work then if I just want to update to a new CM nightly, I can probably just shut down GFE, flash, remove files and start GFE again.
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.