hi, im new to rooting. i've just rooted my desire with cyanogenmod 7, and the android market doesn't seem to work? i can't download google map or any other apps from it. any help? thanks alot.
any help? thanks
i guess you tried rebooting? that worked the last time I had problems with cyanogenmod, that being said i don't use it daily so I'm no expert
yup, i tried rebooting but it didn't work too..
Try wiping the cache, if that doesn't work, do a factory reset and wipe everything, do a fresh install and put gapps on.
does that mean i have to flash it back to stock rom and start all over again?
Have you tried to flash the G-apps again? Here's the link of the newest one: Google apps choose the CyanogenMod 7 (Gingerbread) version and flash it with Rom Manager or Recovery.
have you modified the .zip file , deleting some files for exemple?
I done it, and removed "Package Installer.apk" one time, so downloads were beginning but stopped each time immediately
Market download issues
I'm having similar issues using GingerVillain 1.9. Small market updates are downloading without issue, larger ones such as the latest Google Maps update are giving the message "download unsuccessful". I had similar issues when the market was updated from the old style, and wonder whether google are tinkering in the background.
Fraize1 said:
Have you tried to flash the G-apps again? Here's the link of the newest one: Google apps choose the CyanogenMod 7 (Gingerbread) version and flash it with Rom Manager or Recovery.
Click to expand...
Click to collapse
i had tried to flash it again before but it doesn't work.
fabulous69 said:
have you modified the .zip file , deleting some files for exemple?
I done it, and removed "Package Installer.apk" one time, so downloads were beginning but stopped each time immediately
Click to expand...
Click to collapse
i don't think i've removed any of those files..
I am having similar problems. I have installed the gapps, but it only installs a couple of google apps. When I try to install from the market some install fine but others (angry birds for example) don't. I see the downloading icon for split second then it goes away and the download stops.
Any ideas?
Well installing DarkTremors script did the trick
http://forum.xda-developers.com/showthread.php?t=715940
cb8rwh said:
Well installing DarkTremors script did the trick
http://forum.xda-developers.com/showthread.php?t=715940
Click to expand...
Click to collapse
how does it help?
i have the same issue , it's stuck with ( Downloading... ) what ever the app is
Hi I have an error , SU user needs to be updated ,I also get SU binary outdated .. and Manifest needs to be updated.
So I update , it fails at the end when remounting ( rw )
however all my "root apps still work " but none are listed in the superuser area, which is new icon. the version did update , as it has done loads of times before, but now it's saying the above error .
my leedriod rom is stable bar that .. thats why i have kept it
Uninstall the update to SU. Download the latest version and adb push it if you really want it
Sent from my HTC Desire using XDA App
rootSU said:
Uninstall the update to SU. Download the latest version and adb push it if you really want it
Click to expand...
Click to collapse
rootSU are you talking about of yourself?
anyway its available also a flashable zip here or directly on the su creator (ChainsDD) page http://androidsu.com/superuser/
andQlimax said:
rootSU are you talking about of yourself?
Click to expand...
Click to collapse
Yes, I need to be desimulated ASAP
That killed my phone
I took a back up .. which its running now...
Can I un install superuser , and reinstall from the market place ?
I have noticed all my " rooted " apps work , cache cleaner , tit backup etc.. so is there any real need in the update anyway?
dgattenb said:
That killed my phone
I took a back up .. which its running now...
Can I un install superuser , and reinstall from the market place ?
I have noticed all my " rooted " apps work , cache cleaner , tit backup etc.. so is there any real need in the update anyway?
Click to expand...
Click to collapse
Its the only way. Either leave as is or flash / adb push replacement.
Hmm I had same issue when I flashed Redux2 rom and tried to restore apps and data with MyBackupPro.
I did factory reset after that and started installing application one by one. That solved my problem.
Sent from my HTC Desire using Tapatalk
simple solution: only flash the damn zip above in recovery
Baby steps. One thing at a time.
By the way all this app does is control access to root for applications. It does this well enough anyway. No real need to update it. Surely any update is "just for the sake of it"?!
Please use the Q&A Forum for questions Thanks
Moving to Q&A
FIXED
All sorted now....
Rolled back the rom to the back up I took previously , un installed the updates..fab
Market place wanted to update it again on the weekend , so like a muppet I said yes... the same error happened
This time I just un installed the update.. all fine...
My wee pirate is working fab once more ...
I don't post outside of the development section often so sorry if there's another thread for this I didn't notice.
I've tried a few different CM based ROMs (fitsnugly builds, crDroid, Carbon ROM) and ever since I've had 4.3 it seems like the default superuser that's in the settings isn't working. I think it might be an issue with the SU binary.
When I try using a root app I do see the accept/deny popup and accept it, but the app still says it does not have root. I've tried restarting the app, it is not isolated to just one root app either. Root access is enabled in Settings and the apps are listed as allowed in Settings.
I'm able to install SuperSU, then after I reboot to update the su binary through recovery root works normally with SuperSU
Is there anyone that can help me figure out why root access isn't working every time I flash a nightly for any ROM? I basically have to re root the phone every time.
Sent from my Galaxy Nexus using Tapatalk 4
It's a known issue with 4.3's security modifications.
Had the same problem, switched to superSU too...
Just an informative message in case people were having same issues I was, reading the posts, I see many are.
The amazing @Chainfire has a working beta method which allows me a simple, fully stock rooted OL1, with deep sleep fixed, and a small tweak to get Titanium Backup (TiBu) working on my sprint galaxy s6 (SM-G920P).
Note that chainfire's site (http://autoroot.chainfire.eu/) as of 1/16/16 had a autoroot version for the G920P that installed the 2.65 NOT the 2.66 (or 2.67) (beta deep sleep fixed versions) of SuperUser SU, so you'll have to TWRP install the 2.66 or 2.67 to get the deep sleep fix
Here's the brief GUIDE how I did it:
1. Download OL1 here's the sammobile link http://www.sammobile.com/firmwares/download/62965/G920PVPU3BOL1_G920PSPT3BOL1_BST/
2. Download ODIN 3.10.6 http://forum.xda-developers.com/showthread.php?t=2711451
3. Download CFautoroot for the Sprint Galaxy s6, and consider donating to @Chainfire https://download.chainfire.eu/785/CF-Root/CF-Auto-Root/CF-Auto-Root-zerofltespr-zerofltespr-smg920p.zip
4. ODIN flash first the Stock OL1 and then the CFautoroot
5. Download and flash THIS TWRP https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html or select appropriate one from https://dl.twrp.me/zerofltespr/ *(note that 3.0.0-0 is now available, but I haven't tried it yet, 2.8.7.0 still working well)
6. DEEP SLEEP FIX Download SU 2.67 Beta https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
*** Note- this beta version of SU works PERFECTLY on my 920P phone, and fixed the deep sleep issue
7. Move the SU 2.67 Beta to your phone's hard drive. Put it somewhere you can find it easily.
8. Boot into TWRP recovery (power, home key and volume up). Click "Install" and select the 2.67 SU Beta zip folder you just downloaded.
OPTIONAL:
9. Fix TiBu: Easy fix- uncheck in SU the "mount namespace separation"
Done.
Finally- pure stock rooted, nearly no crashes, everything seems to work. :good:
UPDATE 2.20.16: Both Beta versions 2.66 and 2.67 SuperSu DID in fact eventually crash, but only after 10 days did i get my first, and after 5 weeks, it has only occurred with Dolphin Browser, and only rarely- so might be a setting related to that app. Still way better and more stable than unikernel method.
that's awesome!
Sent from my S6 using tapatalk
Did it trip Knox?
1619415 said:
Did it trip Knox?
Click to expand...
Click to collapse
I had previously used @djvoleur 's UniKernel v8 and v9, so I already had knox tripped
Saafir said:
It says he Odin'd TWRP so I would assume so. Kind of confused to what good ths method is lol
Click to expand...
Click to collapse
I couldn't find a pure stock with a pure stock kernel way to root. Rooting using the UniKernel method kept me with a very buggy system that repeatedly crashed, no matter what I did to manipulate it.
Once chainfire autoroot became available for the s6, that was great- but it had the deep sleep issue (and also messed with a TiBu setting). His 2.66 update fixed the deep sleep issue, and a simple settings change fixed the TiBu issue.
googling for these answers wasted a lot of my time, and reading posts- I saw that others were struggling with this too-- especially since they weren't sure his methods would work on the sprint version of the s6.
So I just thought I'd save people some time, confirm that the methods work great on the 920P, and give them links to how to do it
I just tried this procedure.
Everything goes ok, but TWRP will not accept input. If I touch the screen nothing happens. After a bit, the screen will lock (and swiping with my finger wont work) and the only alternative is to reset using pwr-home-voldn. I tried TWRP 2.8.7.1 and 2.8.7.2 and both do it. TWRP 2.8.7.0 works ok, but the first time I tried, it put the phone into a boot loop where the animation would start, and then reboot.....
I was running OL1 stock (got the phone two days ago).
Still investigating... Reloading stock ROM.
At least 2.8.7.0 allowed me to input into TWRP. Was able to flash SuperSU. Did not get stuck on boot animation this time.
Huey Driver said:
I just tried this procedure.
Everything goes ok, but TWRP will not accept input. If I touch the screen nothing happens. After a bit, the screen will lock (and swiping with my finger wont work) and the only alternative is to reset using pwr-home-voldn. I tried TWRP 2.8.7.1 and 2.8.7.2 and both do it. TWRP 2.8.7.0 works ok, but the first time I tried, it put the phone into a boot loop where the animation would start, and then reboot.....
I was running OL1 stock (got the phone two days ago).
Still investigating... Reloading stock ROM.
At least 2.8.7.0 allowed me to input into TWRP. Was able to flash SuperSU. Did not get stuck on boot animation this time.
Click to expand...
Click to collapse
Hmm, interesting.
I used twrp-2.8.7.1-zerofltespr.img and that worked just fine.
I only had an issue when I (briefly, mistakenly) tried to use the TWRP from this link http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533/post64613464#post64613464
When I flashed that incorrect TWRP, I got stuck in the same manner you did-- but twrp-2.8.7.1-zerofltespr.img worked fine.
Of note- I fixed the link above to go to the https://dl.twrp.me/zeroflte/ and https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html pages.
Somehow though it seems I have a copy of the sprint version of 2.8.7.1, I can only see the 2.8.7.0 listed on the TWRP sites. I am sure that also should work fine
good luck
**Correction: the newest TWRP is 2.8.7.0 for the G920P
It may well just be something I did. Like I said, brand new phone....
I used ODIN, and I got the downloads from the TWRP site (dl.twrp.me)...
Regardless, I got 2.8.7.0 to work and I have root. Not really sure what the differences are.
Just kind of putting it out there for others....
my phone is already rooted, can i uninstall supersu 2.44 and flash supersu 2.66?
legola said:
my phone is already rooted, can i uninstall supersu 2.44 and flash supersu 2.66?
Click to expand...
Click to collapse
yes- essentially- but because the supersu 2.66 beta is in a zip file (with multiple files for the multiple system architectures in it), you can't (i don't believe) flash through ODIN.
You must download the zip directly onto your phone hard drive (somewhere easy to find), or download on your laptop and transfer to your phone (again, putting somewhere easy to find), then boot into recovery, and install via TWRP. It should replace the supersu file, and automatically fix any deep sleep issue, if you haven't already fixed that previously
spammy l said:
yes- essentially- but because the supersu 2.66 beta is in a zip file (with multiple files for the multiple system architectures in it), you can't (i don't believe) flash through ODIN.
You must download the zip directly onto your phone hard drive (somewhere easy to find), or download on your laptop and transfer to your phone (again, putting somewhere easy to find), then boot into recovery, and install via TWRP. It should replace the supersu file, and automatically fix any deep sleep issue, if you haven't already fixed that previously
Click to expand...
Click to collapse
It actually won't, unless your stock. Unikernel will just keep overwriting it since it's prerooted.
spammy l said:
Hmm, interesting.
I used twrp-2.8.7.1-zerofltespr.img and that worked just fine.
I only had an issue when I (briefly, mistakenly) tried to use the TWRP from this link http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533/post64613464#post64613464
When I flashed that incorrect TWRP, I got stuck in the same manner you did-- but twrp-2.8.7.1-zerofltespr.img worked fine.
Of note- I fixed the link above to go to the https://dl.twrp.me/zeroflte/ and https://dl.twrp.me/zeroflte/twrp-2.8.7.0-zerofltespr.img.tar.html pages.
Somehow though I have a copy of the sprint version of 2.8.7.1, I can only see the 2.8.7.0 listed on the TWRP sites. I am sure that should work fine
good luck
Click to expand...
Click to collapse
actually, AFAIK for our G920P, the latest TWRP is 2.8.7.0.
Your 2.8.7.1 might be named wrongly. could you please check in the TWRP screen?
yaibakt said:
actually, AFAIK for our G920P, the latest TWRP is 2.8.7.0.
Your 2.8.7.1 might be named wrongly. could you please check in the TWRP screen?
Click to expand...
Click to collapse
You are correct- I checked the TWRP screen, and it is in fact 2.8.7.0. My file must be named incorrectly. I edited that post to reflect this. Thanks for pointing this out. :good:
spammy l said:
You are correct- I checked the TWRP screen, and it is in fact 2.8.7.0. My file must be named incorrectly. I edited that post to reflect this. Thanks for pointing this out. :good:
Click to expand...
Click to collapse
:good:
one more thing:
i use your trick and CAN restore apps by titanium backup. thank you.
but, could you confirm for me that: can you uninstall a system app by titanium backup?
for me, when i tap a system app in tita, and uninstall it, then reboot the phone, the app appears again.
i have to use root explorer to delete the app manually.
yaibakt said:
:good:
one more thing:
i use your trick and CAN restore apps by titanium backup. thank you.
but, could you confirm for me that: can you uninstall a system app by titanium backup?
for me, when i tap a system app in tita, and uninstall it, then reboot the phone, the app appears again.
i have to use root explorer to delete the app manually.
Click to expand...
Click to collapse
Hi- Glad the titanium backup trick worked for you- it frustrated me a bit until i found that answer.
Yes- I can confirm that both uninstalling and/or freezing system apps work in TiBu, and they do not re-install. When I uninstall a system app with TiBu, it does stay uninstalled after reboot.
Maybe it is a security issue? I use an english translation of LBE security, but have also used X-privacy, and both those (along with some other programs) block unwanted installations.
spammy l said:
Hi- Glad the titanium backup trick worked for you- it frustrated me a bit until i found that answer.
Yes- I can confirm that both uninstalling and/or freezing system apps work in TiBu, and they do not re-install. When I uninstall a system app with TiBu, it does stay uninstalled after reboot.
Maybe it is a security issue? I use an english translation of LBE security, but have also used X-privacy, and both those (along with some other programs) block unwanted installations.
Click to expand...
Click to collapse
thank you.
how weird over here...
i can freeze apps, but cannot uninstall apps by titanium. it was possible when i root my phone using unikernel v8.
one feedback from here: the battery life is somehow worse than using unikernel v8. yesterday i just had about 3h15' on screen from 100% to 1% battery, compared to about 4h30-5h onscreen with unikernel v8. the usage is normal like everyday of mine.
however im just using this method for 1 day so i will give it some more days to see if there is any improvement...
yaibakt said:
thank you.
how weird over here...
i can freeze apps, but cannot uninstall apps by titanium. it was possible when i root my phone using unikernel v8.
one feedback from here: the battery life is somehow worse than using unikernel v8. yesterday i just had about 3h15' on screen from 100% to 1% battery, compared to about 4h30-5h onscreen with unikernel v8. the usage is normal like everyday of mine.
however im just using this method for 1 day so i will give it some more days to see if there is any improvement...
Click to expand...
Click to collapse
hmmm- bizarre.
Not sure exactly what is going on with your system. As for the battery- mine has been working great (by s6 standards)- way better than unikernel v9, and at least as good as unikernel v8.
Are you sure it is deep sleeping? Positive it is running SuperSU v2.66? (could check on the settings page) Also, though I'm sure you'd know if it weren't deep sleeping, you could try running the "CPU Deep Sleep Info Widget" to double check. https://play.google.com/store/apps/details?id=de.cmweb.deepsleep&hl=en
As for mine- I'm over a week into this method, haven't crashed a single time to lock screen, battery is working great (for a s6), and all apps seem to work smoothly- without all the bugs I was experiencing with unikernel.
Hope your phone gets sorted out soon too
yeah, im sure that all the setting on my phone are the same between unikernel v8 and this method. i use SU v2.66 too.
i havent got any crash on v8 either, so basically i just compare v8 and this method in battery life.
i dont use v9 since it's reported to have lockscreen issue.
but well, i'll being using this method at least till weekend to see. i'll just be able to re-flash the rom if necessary at that time anyway.
thank you.
I have been away from the forums for a few weeks, i was curious if this or any method allows for rooting but retaining knox status? I am rooted (with the old pingpong method) but stayed on OE2 (5.0.2) to keep knox intact. I would love to get updated to the latest OS rooted but keep knox intact still.. not sure if its possible, so i check with yall..
sj
Sent from my SM-T210R using Tapatalk
If i were to skip the custom recovery flash, would i be able to receive ota updates?
Sent from my SM-G920P using Tapatalk
Hi, im having this issue when i press the camera button or launch launch the app is says that it is being used by another app. Has anyone experienced the same issue? I tried factory, reset reinstalling my rom(im on stock rooted rom locked bootloader). Other camera apps work just as they should. It started doing it suddenly, i didnt flash, or change anything. Thanks for your responses
DrtiBarta said:
Hi, im having this issue when i press the camera button or launch launch the app is says that it is being used by another app. Has anyone experienced the same issue? I tried factory, reset reinstalling my rom(im on stock rooted rom locked bootloader). Other camera apps work just as they should. It started doing it suddenly, i didnt flash, or change anything. Thanks for your responses
Click to expand...
Click to collapse
I've gotten that before on custom and experimental roms, but never on stock with a clean install. I can only guess it's an issue with the ROM file. Are you using Flashtool ftf, or pre-rooted, or...?
levone1 said:
I've gotten that before on custom and experimental roms, but never on stock with a clean install. I can only guess it's an issue with the ROM file. Are you using Flashtool ftf, or pre-rooted, or...?
Click to expand...
Click to collapse
I finally solved it by reflashing the rom, i Dont know why restore from recovery wasnt enough