Related
I was running DCv2.06 and thought a2sd was working fine until one day i got a out of space error when updating Nesoid Lite (NES emulator.) Took a look at available space and it said ~30mb. Not exactly out of space but whatever, weird, moving on.
• Went in and started totally fresh wiping everything and, repartitioning and then successfully activating a2sd. free space = 101mb.
• My Nesoid shortcut said the app was no longer installed upon pressing it. Market says there's an update available and that it IS installed.
• When I try to update it tells me I'm out of space.
• When viewing the app in market my only option is to update. Uninstall button is grayed out.
• I can install any app on the market, even big ones like google earth with no problem, except Nesoid Lite.
• Nesoid Lite is not under Setting > Applications > Manage Apps.
• Tried to install Nesoid Lite from an old backup, same Out of Space error.
• Downloaded Nesoid Lite from a website and tried to install via a couple different app installers and ES File Explorer - same error.
• App is still in my market list.
• WIPED FULLY and started over. Same app, same error... and still in Market list under Downloaded. Still says Update Available.
how in the world does the app's market link survive a total wipe!?
what the f.
EDIT:
Just cleared market cache and the problem persists.
Cleared market upldater cache - problem persists.
I can install other emulators, like Gearoid Lite, by the same developer: "yongzh"
scirio said:
• My Nesoid shortcut said the app was no longer installed upon pressing it. Market says there's an update available and that it IS installed.
Click to expand...
Click to collapse
Start by making sure the market isn't running (task manager of your choice, or settings->applications->manage applications, Market, 'Force Stop' button).
Then open a terminal and type
Code:
su
rm -r /data/data/com.android.vending/*
Restart market, if the button is still grayed out then reboot your phone.
results were the same. Thanks for you reply.
scirio said:
results were the same. Thanks for you reply.
Click to expand...
Click to collapse
I don't know what the name of the apk is, but if you can find it, you can manually remove it in /data/app (if you have a2sd running, it'll redirect you to /system/sd/app). If it isn't there, try /data/app-private. Last place to work is /system/app.
Once you remove it, reboot the phone and see if you can install it again.
tkirton said:
I don't know what the name of the apk is, but if you can find it, you can manually remove it in /data/app (if you have a2sd running, it'll redirect you to /system/sd/app). If it isn't there, try /data/app-private. Last place to work is /system/app.
Once you remove it, reboot the phone and see if you can install it again.
Click to expand...
Click to collapse
The app is in fact uninstalled (foir the most part) and is in neither of those directories.
I used to have superuser/root running fine on my Vibrant. Busybox, titanium backup, everything worked.
I went to install RyanZA's lag fix (specifically the update.zip pack with a new superuser app, different busybox, etc someone else made) and started having troubles. The superuser requests were not working.
Now, I tried to go back to the original update.zip on this thread. I have the original Ninja superuser icon, etc. Now, when programs request SU, I can click allow or deny, the program hangs, and then I get:
"Sorry!
The appication Superuser Permissions (process com.noshufou.android.su) has stopped unexpectedly. Please try again."
And my root access is denied.
I've restarted, used different superuser update.zips, all about 10 times each in different combinations. I can't get past this error.
Question: How can I erase all the root crap I have on my phone and start over fresh? I can't even terminal "SU" to enable superuser.
lag fix...? vibrant isnt fast enough for you?
sigeltek said:
lag fix...? vibrant isnt fast enough for you?
Click to expand...
Click to collapse
I like my Vibrant like my women...not slow.
shadow300z said:
I like my Vibrant like my women...not slow.
Click to expand...
Click to collapse
QUOTE OF THE DAY!!!
As for your issue, you may try contacting the person whose update.zip you used and ask what it modifies/any reported issues like yours, and how to fix it. That's your best bet I think.
Have you tried using Clockwork ROM Manager and restoring to a pre-lag fix state? This same problem happened to me when I tried to install the lagfix from an update.zip file that I tried to access by rebooting the phone while holding down the volume and power keys.
The only way I got the lagfix to install properly was to use Clockwork to restore using nandroid, then used the one-click method (connected to the pc, in debugging mode, etc.). Now everything is working perfectly.
BTW, I have read some folks posting that they can't tell the difference between stock and lagfixed... My experience is exactly the opposite. The Vibrant is *much* faster when lagfixed.
scpieps said:
Have you tried using Clockwork ROM Manager and restoring to a pre-lag fix state? This same problem happened to me when I tried to install the lagfix from an .apk.
The only way I got the lagfix to install properly was to use Clockwork to restore using nandroid, then used the one-click method (connected to the pc, in debugging mode, etc.). Now everything is working perfectly.
Click to expand...
Click to collapse
Clockwork was unable to work because superuser kept crashing. I couldn't do ANYTHING root related.
I did solve the problem though, so for anyone else that has the same issue with SU FCing:
Goto: Menu - Settings - Applications - Manage Applications - Menu button - Filter, Choose to show "all" - Find & choose Superuser Permissions in the list - CLEAR DATA.
This fixed the problem for me, hopefully this will help someone else!
shadow300z said:
Clockwork was unable to work because superuser kept crashing. I couldn't do ANYTHING root related.
I did solve the problem though, so for anyone else that has the same issue with SU FCing:
Goto: Menu - Settings - Applications - Manage Applications - Menu button - Filter, Choose to show "all" - Find & choose Superuser Permissions in the list - CLEAR DATA.
This fixed the problem for me, hopefully this will help someone else!
Click to expand...
Click to collapse
I had this same problem (Clockwork couldn't fix permissions because Superuser Permissions kept FC'ing, and lots of google searching resulted in no help until I found this. Saved me from losing a few days of important text messages because I'm an idiot and hadn't backed up prior to doing a cognition update that didn't go well the first time around. THANK YOU!
worked! you the man my gee
Thanks man..
It seems that it happened when I uninstalled some apps. after that I connected my rooted Desire Z to PC, typed "adb shell" and "su" and.... "permission denied" appeared!
Went through some other apps, and none of them had root access! After rebooting phone, Superuser app crashed, and it kept crashing...
I cleared application data for Superuser app, and - voila! I got my root back again!
Thanks!
Have the droid charge. Superuser stopped working. All my apps started failing with "the application superuser has stopped unexpectedly". Clearing the data didn't do anything. I finally cleared data, uninstalled the superuser app and reinstalled it. Back up and running. Thanks everyone!
Been having issues with the most recent few ARHD ROMs (HTC Sensation), superuser force closing, etc. cleared SU data and all is well again! thanks.
I could bring these out in a rom, but there are just way too many chefs in the Thunderbolt right now. So why not release a package that will tweak your current rom just as much?
What will this package do?
-Enable init.d support for scripts on startup.
-Enable usb debugging on a clean wipe.
-Add adb root at all times.
IO tweak
-Remount your filesystems(system, data, cache) with less overhead, so you can increase our already incredibly inflated IO score in quadrant. Does it increase real world performance? You be the judge.
Minfree tweak
-Will allow you to keep a higher mount of ram free before Android starts cannibalizing apps to free ram.
rw on boot
-Will allow you to boot at all times with system in rw mode. Handy for adb pushing files to system.
ro on boot
-Self explanatory.
How to use:
Flash kernel via HBoot.
Put PG05IMG.zip on sdcard, and with adb type:
adb reboot bootloader
This will boot to fastboot. All you need to do is hit power to enter bootloader, and it will scan the package and ask to load it. You will know if you have the right package if it says boot.
Note: If you do not have busybox installed, use this:
http://dl.dropbox.com/u/2056318/busybox_1.19_3.zip
Once you have rebooted, take the second package and flash it via clockwork.
When you reboot, all tweaks will be applied for filesystem and minfree. To use rw at boot time:
In adb or terminal emulator, type:
rw_boot (will require you to type su beforehand if in terminal emulator.)
Next reboot will be rw.
For ro:
ro_boot (same thing, type su first if using terminal emulator.)
Next boot will be ro.
In regards to the two above scripts, do not worry if either gives a file not found error. It will still work.
Extra scripts:
sysrw --mounts system as rw.
sysro --mounts system as ro.
Tweaks that did not make the cut:
SD card speed tweak:
I see a lot of rom cooks adding this, but lets face it, HTC added this tweak in before the phone was shipped. I checked. No need to reapply the same thing again. Right, guys? *crickets*
Framework speed up by removing transitions:
Framework isn't eye candy.
Zipalign every boot
Apks can be zipaligned only once. No point in doing this every boot.
Download kernel:
http://www.mediafire.com/?ob2i992sza9y260
Download cwr package with scripts:
http://www.mediafire.com/?7u69f950indjiqe
I will be adding more as time goes on.
good work bud this is gonna be usuful for a lot of people. =)
Sorry for the noobish question but what does "adb root at all times" mean? If I've done the whole rooting process aren't I fully rooted?
Every time i see adryn post something new i pee a little. Guys we are a week in today and already have some great devs.
Sent from my ADR6400L using XDA App
NeutronBomb said:
Sorry for the noobish question but what does "adb root at all times" mean? If I've done the whole rooting process aren't I fully rooted?
Click to expand...
Click to collapse
I have the same question.
ksizzle9 said:
Every time i see adryn post something new i pee a little. Guys we are a week in today and already have some great devs.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Hahahah. Great post.
asshole..you made me buy a new phone
Can I flash this on top of the Virus Rom or no?
Sent from my ADR6400L using XDA Premium App
Well it does say ANY Rom so I would imagine you'd be safe flashing it
Sent from my ADR6400L using XDA App
NeutronBomb said:
Sorry for the noobish question but what does "adb root at all times" mean? If I've done the whole rooting process aren't I fully rooted?
Click to expand...
Click to collapse
Yes, you're fully rooted - which is to say, you have the ability to su and become root - very little that is running is actually running as root.
If you're running stock kernel, when you adb shell, you'll get a $ prompt ... i.e. you're not root yet, but can become so with a quick su. (Oh, and SuperUser will pop up asking you to allow it.) Nothing you do via the adb command (push, pull, etc) happens as root.
If you're running the patched kernel, when you adb shell, you'll get a # prompt ... i.e. you're root now. (No SuperUser prompt either.) Everything you do via adb (push/pull) happens as root.
Point being: yup, you're root'd - but you ain't root until you're root
I will apply this in my next update and will be standard in all my roms. If that's okay with u
Sent from my ADR6400L using XDA Premium App
Jaywan said:
I will apply this in my next update and will be standard in all my roms. If that's okay with u
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Sure, have at it.
does this kernel retain the ability to fastboot, I keep having trouble with it not working and I am trying to narrow it down.
Thanks Adryn!
This + your debloat + LauncherPro = I'm 100% happy with my TBolt.
You rock dude, I just bought you a beer. =)
Much appreciated.
destroyerbmx said:
does this kernel retain the ability to fastboot, I keep having trouble with it not working and I am trying to narrow it down.
Click to expand...
Click to collapse
fast boot, or fastboot?
fastboot is a feature of hboot, not the kernel.
fast boot is buggy and only works on wifi or 4G. NOT 3G.
Odinist said:
Thanks Adryn!
This + your debloat + LauncherPro = I'm 100% happy with my TBolt.
You rock dude, I just bought you a beer. =)
Click to expand...
Click to collapse
When i get to work here in a bit, Imma try that out. Since I will probably have nothing else better to do haha.
gonna Load this on top of Perfect Storm first and see how it goes.
Everytime adrynalyne posts, an angel gets its wings...
and i tinkle a little bit...
Is there any reason why we couldnt flash the pg05img through CWR?
Other than it not being setup for cwr, and cwr doesn't work to flash kernels yet?
No.
Is it already in your rom?
Sent from my ADR6400L using XDA Premium App
I just started using DX and then i tried to use system app remover to delete something and then it says my phone is not rooted? i still have superuser and rootexplorer works. Busybox cannot be installed because its not rooted?
Any suggestions?? i need to root again or what??
Weird because root explorer works..and superuser is still there.
you have to root it again,
it wont remove any files
so if you did it once a second time wont be as hard
I also use Ginger DX, and have the same problem as yours. System App Remover seems not compatible with GingerDX. I suggest u to use Titanium Backup to uninstall system app. It works well with GingerDX.
This is a known bug... please refer to this thread..
http://forum.xda-developers.com/showthread.php?t=1205566
Let's just hope the fund raiser is a success and DX will get a new X8 soon
1. try to get in terminal emulator (if you have one) and type there "su"
and check if ($ goes to # )
2. you might delete some essential app which helps system work in rooted mode so try to reinstall ROM. if still doesn't work try to root that again. (it's quite easy with super user one click)
just root it again.. only 1 click
No no no guys! It's a bug in the GingerDX series. Just wait for doixanh to fix it.
Thanks to @kryz who managed to generalize the Dirty Cow exploit, XT1528 now has a way to get temporary root : link Notice that the /system will still be read-only, but at least full access to /data is available. Given the state of XT1528, this looks like a pretty good progress!
Steps to get temp root (in Lollipop):
0) uninstall SuperSu apk if you have it installed, see thisfor the reason to uninstall
1) install Croowt.apk, use the 2nd option in the menu : "Get root"
2) install SuperSu apk from the playstore (don't update the binary)
3) install RootChecker apk from the playstore
4) enjoy temporary root (until hard reboot)
I've tested this on 5.0.2, but should probably work on 5.1.1 as well (as long as it was not patched since the end of Oct). Here is the output of Root Checker (where everything looks nice and green !) :
Device: XT1528 (MOTO E Verizon prepaid)
Android Version: 5.0.2
Additional - SELinux
Status: NOT enforcing
Status stored in /sys/fs/selinux/enforce
SuperSu works (untill hard reboot) !!!
@9acca9, @dreyeth, @Whoareyou, @bendrexl, @docna, @caspar347, @Dishe, @hp79
This is great!
Thank you @kryz
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
jcpowell said:
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
Click to expand...
Click to collapse
This looks like the old Kingroot behavior - temp root which is highly unstable. Once after a Kingroot attempt I had to factory reset the device due to the "junk" left behind, at least here it's all nice and clean ! I wonder if forcing a soft reboot right after root may help to make it more stable ... Or perhaps something else is going on ?
No idea if anyone is looking into unlocking this phone's bootloader still but hopefully this leads to it. Happened with my Droid Turbo. The initial process was use Kingroot for temp root and sunshine to unlock.
Tried sunshine and after second test it gives an error. Won't even try
jcpowell said:
Tried sunshine and after second test it gives an error. Won't even try
Click to expand...
Click to collapse
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
bibikalka said:
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
Click to expand...
Click to collapse
There is a bug if you have SuperSU is installed before get the root, the restore init function will not work properly.
So the instructions in this post should be changed, and clarify that is required uninstall it.
Also ive fixed another bug related to clean the state of the system, the apk is updated in the main post.
Really after the restore clean the phone should be in a clean state, but if supersu is installed i don't know why is denying the access to the app.
Can you check this issue please?
@kryz I'm actually finding it more unstable with the updated app.
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Idk, as soon as I attempt to use my phone after root it freezes and reboots. If I let it sit it'll last an hour at least, lol
jcpowell said:
@kryz I'm actually finding it more unstable with the updated app.
Click to expand...
Click to collapse
Let's see what's going on
-Are you using the apk or adb script?
-If you use the apk and don't restore init what happens?
-If you restore init is laggy or reboot?
-Can you try the adb script and tell me if you also get a reboot?
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Regards,
---------- Post added at 01:33 AM ---------- Previous post was at 01:16 AM ----------
fenlon said:
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Click to expand...
Click to collapse
First about the sdcard, i will look after that bug that i know what's happening,please don't remove/mount/umount for now.
Do you have a computer to do some checks?
You say that with the new version there is not reboot but laggy, can you check if there is some process eating the cpu with top:
Code:
/data/local/tmp/busybox top
I suspect there is the last process restauring init that is eating the cpu, check for this or ;
Code:
ps | grep dirtycow
If that is the case kill it and we will know if is the responsible of that lag.
In other hand can you attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Guessing that you are using the apk, what happen if you don't restore init?
Is laggy or just unstable, don't start wifi/bluetooth you can't change settings are like locked.
Have you tried the script adb version, can you try and tell me if you have the same issue?
Best regards,
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
jcpowell said:
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
Click to expand...
Click to collapse
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
kryz said:
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
Click to expand...
Click to collapse
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
jcpowell said:
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
Click to expand...
Click to collapse
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
kryz said:
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
Click to expand...
Click to collapse
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
jcpowell said:
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
Click to expand...
Click to collapse
If it reboots just checking permissions the problem is the fsck_msdos process not the shellcode in init, i saw in the files that you attach all is ok.
I've updated the apk in the main post, now it will release the sdcard, please check that version in the same way, first before get root, click "check perm" wait to see the results and work with the phone to see if reboots again for a while.
If all is working with "check perm" and you don't get reboot, try get root, is very probably that now doesn't reboot.
I think with the adb script will work because it overwrites run-as, anyways ive updated the apk for release the sdcard check process and it'll return ok status.
The instructions for the rar and adb.
First you need adb installation in your computer, i mean connectivity with the device via adb.exe.
When you have adb working you need to put all the content of the rar in the path /data/local/tmp/.
So extract the rar in your computer in a folder and with adb push copy all the files to that folder:
(in the folder of the rar contents)
Code:
adb push * /data/local/tmp/
Then get a shell with adb:
Code:
adb shell
Execute the script to exploit it:
Code:
cd /data/local/tmp
./exploit.sh
Wait the logs and if all is ok execute:
Code:
run-as -s2
Wait 5 seconds and:
Code:
su
If all is ok you will have a root shell, this method is more stable even doesn't clean the init you can do it in the app, but test all before.
That last apk causes me immediate reboot. Maybe it was not the fsck_msdos cause I was able to do a check and not get a reboot with the debug apk you gave me. I am trying the adb method but I think I am messing up some steps. Will let you know when I get through it.
@kryz I should have some time tomorrow to test the shell commands. Thank you again for taking your time to do this.