Hey guys,
I love my 101it and can't wait for full root.
in the mean time I've been using z4oot like everybody else.
But since yesterday that stopped working for me.
I've been running z4root and it said that temp root has been granted.... but it hasn't.
I've tried rebooting. Enabling and disabling USB debugging,but nothing works.
I feel like I'm skipping some stupid step.
Anybody has any idea?
Thanks!
Check free memory using ATK or any other app killer. My Z4 was giving me the same issues till I fixed the free memory. My issues started when memory went below 49MB. So I uninstalled some apps and no issues so far.
Some said that you need more space for it (100MB free out of 300MB).
Some also said that it only works after they moved all their apps back to the 300MB storage after they used app2sd (and may or may not have uninstalled it before they rooted).
Some said clearing the data/cache of and reinstalling superuser/z4root worked for them.
Also, once you got it rooted, don't reboot, use hot reboot to keep your root while booting.
For me, I haven't tried the second solution, and I had to reinitialize the entire system... Thankfully appmonster backup, titanium backup, and appbrain sync makes it easy to reinstall all the apps I had.
Thank you guys.
I was able to release 78mb on my internal, cleared data and cache on both but its still not working.
I would consider formatting but since I have no root I can not backup using TB...
Ill try to clear more space later and retry.
Will post results here.
Any other ideas?
Thanks!
Consider backing up with appmonster, swiftp, usb, appbak (list of app, if app monster don't do that already), and appbrain (for quick reinstall).
I believe appmonster let you backup apks, and app list. And with appbrain, you can just copy your synched app list to the new install and tell it to install them.
I had the same problem before and as MoonPhantasm suggests... moving all apps back to the phone from internal storage let me root again. Give that a shot.
The problem is that I have way too many Alps to keep in the measly 256mb on this device...
I ended up formatting the device and now it works.
lets see how long I can go without a full reboot
Thanks all.
madhouze said:
The problem is that I have way too many Alps to keep in the measly 256mb on this device...
I ended up formatting the device and now it works.
lets see how long I can go without a full reboot
Thanks all.
Click to expand...
Click to collapse
There is over 300 MB for "Alps" on the device unless you move them to SD in which case there is nearly 8 GB. There is 256 MB of RAM which only comes into play when you swap applications to background. Formatting is like swatting a fly with a grenade launcher but then if you don't know RAM from flash...
I'm finding the tablet pretty responsive without upping the CPU limit but I would prefer a more clear and workable solution than formatting every time I reboot.
sequitur said:
There is over 300 MB for "Alps" on the device unless you move them to SD in which case there is nearly 8 GB. There is 256 MB of RAM which only comes into play when you swap applications to background. Formatting is like swatting a fly with a grenade launcher but then if you don't know RAM from flash...
I'm finding the tablet pretty responsive without upping the CPU limit but I would prefer a more clear and workable solution than formatting every time I reboot.
Click to expand...
Click to collapse
I have autocorrect to thank for the "Alps"
I agree - there are 300mb for apps, but I use a lot of apps on my device, and some are rather big (it adds up) and most of these unfortunately do not allow to move to SD Card. I can force some of them to SD using Titanium Backup, but then again once I go under a certain threshold I cannot root and therefore cannot use TB.
I would love to have more than 300mb for apps. It seems kind of stupid that out of 16GB on the device they partitioned only 300mb for apps.... Unless I am missing something... in which case please feel free to correct me.
I do appreciate the opinion though.
Ohad.
madhouze said:
I would love to have more than 300mb for apps. It seems kind of stupid that out of 16GB on the device they partitioned only 300mb for apps.... Unless I am missing something... in which case please feel free to correct me.
Click to expand...
Click to collapse
You have to remember that the folks that frequent these boards are not the typical end-user. I had read that the average user installs 8 apps. I have 64, and you are probably around the same high number. The space allocated to the system apps area is not available for content storage, so to most users even the 300MB seems like too much wasted space.
I got 90 apps installed myself, and only have about 30-40MB free right now. Was full for a bit, before I uninstalled a few things... :/
It is pretty ridiculous to only have 300MB for app, when there are 8GB total space. My first time reaching that limit shocked me quite a bit.
About average users installing 8 apps, that sounds impossibly low. Over time, even average users are going to accrue quite a lot of apps. I don't think average users are good at 'uninstalling' things that they don't use til they have to.
Had the problem too and some of it was due to app2sd. Plus, apps keep disappearing when using app2sd, so this feature, one of the most important of froyo, isn't working at all.
Read in another forum that it might be a good idea to first stop all apps by using TaskControl or a similar task manager, before trying to root.
I can't seem to get Z4 to work at all now after doing the firmware update. Tablet seems a lot more stable than it was before the update but would still like to be able to use setCPU to bypass the CPU lock.
jagpoag said:
I can't seem to get Z4 to work at all now after doing the firmware update. Tablet seems a lot more stable than it was before the update but would still like to be able to use setCPU to bypass the CPU lock.
Click to expand...
Click to collapse
In the latest patch they fixed the options that were allowing temp root. This was mentioned in other posts. Right now there is no root for this device.
Faldiin
Instructions I use to root my A70 IT 8 GB
Hello,
I've been using z4root on my A70 IT 8 GB, since I discovered the ping command requires root access on the Archos Gen 8 line. In the meantime, I found additional reasons to use root mode, such as:
1) MyBackupPro supports root mode for full application and data backup.
2) Swap to increase the memory on these 256 MB devices. While swapping to a SD Card isn't a good idea, I'm looking to do it on the 250 MB version.
3) 1 Ghz fix, which once I can go to the 2.0.71 firmware won't be necessary.
4) Run applications that use the ping command.
I'm using these instructions for running z4root on my system. They assume you already have z4root installed on your system. As for validating rooting was successful, there are a couple of ways on the Archos Gen 8 devices:
1) Run setCPU
2) Run the Terminal Emulator and try to use the su command. If it exists you're golden, if not then it failed.
Steps I use:
1) Let the boot process complete, but don't start additional commands.
2) Make sure USB Debugging is on and (if you want) see if there is at least 100 MB of storage left.
3) Start z4root
4) Select temp root
5) Confirm the notice about USB debugging. If it doesn't appear, something isn't right.
6) z4root will take you to the settings. At this point select development from the opened settings, disable and then enable USB debugging. Confirm the message about USB debugging.
7) Return to the home page.
8) Go back into settings -> Applications -> Manage Applications -> All Applications (tab). Go to the bottom of the list, find z4root and select it. Once there you need to:
8A) Do a Clear Data. This is important.
8B) If z4root is running do a Force Close.
8C) Return to the home screen.
9) Start z4root again.
10) Select temp root and in 5 seconds or so you should see a White flash and the text on the screen should change to say the application is finishing up.
Allow it to finish. See notes below should these steps fail to produce temporary root.
z4root will tell you it was successful whether it was or not. I don't know why. At least on the Gen 8 line checking is as simple as seeing if the "su" command exists on the system. If it does, you're golden and if not then something failed and you can't access root.
To validate success, I'll use one of the following methods:
TERMINAL EMULATOR: Start the Terminal Emulator application and issue the "su" command. If this fails, you don't have root. (Note: If this is the first time running terminal emulator in root, you'll get a message asking to give your permission for terminal emulator to have root access. If the message fails to appear, you don't have root. Again this is the first time only.)
setCPU: Start setCPU and if it is the first time ever using the command, run the Device Selection choosing "Autodect Speed Recommended." If you get a screen asking permission to add setCPU to the list of application, you're golden. If you don't get the prompt or setCPU says it failed to get root, you don't have root.
Subsequent times you use setCPU and adjust the maximum speed, you'll see a message flash on the screen about setCPU gaining superuser permission. This message is from the Superuser application. NOTE: You may see the message even before you adjust anything on subsequent uses of setCPU during the same session.
TROUBLE SHOOTING z4root:
Should z4root fail, you should try it a second time after doing a Clear Data and Force Close. If this fails, do a reboot and try again.
Should it fail all the above retries, I go back to square one. I'll uninstall it, download it again from XDA-Developers, and install it with reboots between each step. I have yet to have this last method ever fail on me.
Typically, though, I don't need to go beyond a second try with a reboot.
Should it again fail, my best success has been to uninstall z4root, reboot, reinstall, reboot, and then follow the instructions.
Good luck and hopefully your mileage will be as good as mine.
If you hear of a version working with firmware 2.0.71, please, let me know.
BGMArchos,
i'm not sure to understand you... you have root your 70it with which firmware ?
not the latest firmware. He said once he can go to the .71 firmware the 1GHz fix from rooting wont' be necessary.
But I find unrootable android device pretty ridiculous. I'll be trading this archos for another device at this rate.
I am sure perm root will come, it's just a matter of time.
Btw what alternative is there for the archos in its price range.
I use the 71 firmware and i am pretty happy with the archos at the moment.
When root comes it will just get better.
But for now I can live without root.
Biggest improvement in think is the way it handles the ram. I don't need to kill any tasks anymore like before. That was one of the most annoying things about the tablet.
Not like it was really much of an issue. You can always reboot every a while too as it reboot pretty fast.
Related
I have the CM10 [skang jellybro] fascinate rom installed, and coming from a cm9 rom, all my apps didn't fit because they switched the partition around [making the app partition only 468MB, and the system partition 1.5 GB].
So anyway I had to move a lot of apps to the sdcard. So I just downloaded a newer version of my rom, and wiped cache/dalvik, nandroid backup, then I installed the new zip.
Then I rebooted, and it had to 'optimize' apps [create dalvik cache?] and after that finished...I only had about 15-20 apps show up in my app drawer. [I have probably around 40] So I clicked on Zedge, on my homescreen, and it said "App isn't installed." I then started to worry..:S I googled apps on sdcard disappearing.. and so I opened titanium backup, and under Batch operations, it said "Restore missing apps (6)," and they were 6 apps that I'd uninstalled but didn't delete the backup. so then I wasn't sure what to do next, because I did not create a fresh titanium backup prior to updating my rom [because I did a nandroid instead..] so then I went to Manage Apps, and then.. for some reason, all my apps showed up again! all the ones on my sdcard.
I tapped Zedge again on my homescreen, and it loaded up! So my question is, what happened? Why did my apps disappear, and then just show up again? was it loading titanium backup? or did the rom just scan the sdcard for apps?
Sounds like it just messed up the media scan of the sdcard which I have heard happens from time to time... not sure if that's related to your issue, but now are all your apps installed or are you still missing some? Next time I would just reboot again and let it re-scan to see if it helps
Crawshayi said:
Sounds like it just messed up the media scan of the sdcard which I have heard happens from time to time... not sure if that's related to your issue, but now are all your apps installed or are you still missing some? Next time I would just reboot again and let it re-scan to see if it helps
Click to expand...
Click to collapse
ah.. yes they are all there, but I was just wondering why did they disappear, and then why did they just show up all of a sudden?
I guess if it is the media scan thing, that would explain it.
Fast Boot option may be the culprit
mvmacd said:
ah.. yes the [apps] are all there, but I was just wondering why did they disappear, and then why did they just show up all of a sudden?
Click to expand...
Click to collapse
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNE3D5NrpiSqCRSof-ou1mn6iyeGVg
(I am copying this original post (without edits) to other relevant threads, but will not post anything further elsewhere -- only here. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
EDIT 2012-12-26-a:
Nearly all of the 100+ apps on my HTC DINC (Droid Incredible) continue to behave normally after the "fast boot OFF" fix. (No disappearing act.) However, I did find one that appeared to be installed but really was not: ASTRO File Manager. I used Titanium Backup Pro to reinstall app+data from a backup. It only took a couple of minutes, and after that all went normally.
The only other noticeable issue right after the fix is that nearly all of my installed, functioning apps were listed as "missing" by Titanium Backup in its Batch scenario list (although they were NOT counted in the total number of apps listed with the scenario -- that number was 61, and it should have been nearly 170 based on the number of apps actually in the physical list). After about a day or so of regular usage, a re-check of the "missing apps" Batch scenario found all the functioning apps no longer listed; the 61 missing apps were valid -- they were all from earlier ROMs belonging to the original HTC setup and another phone (MOTO OG Droid). Since I have kept the MOTO as an emergency backup smartphone, I might conceivably want to revive some of these apps.
EDIT 12-26-b:
Some other potentially useful points I have gathered in my survey of this topic across XDA:
1. This problem happens most often when using the "Disk drive" option in the USB Debugger system app. It also happens after physically returning the sdcard to the phone after removing and inserting it into a PC.
2. Those who have wiped the app data cache also report serious problems.
3. Wiping the dalvic cache while in Recovery mode automatically triggers a rebuild of that cache, which may make apps behave oddly or disappear until the rebuild is complete, which reportedly "takes time"
Personally, I did only #1 myself, and the fast boot removal fix seems to work well for that one.
I cannot confirm the others, but they seem to make sense to me, and I doubt the fast boot removal fix would have any influence on them.
4. There are some signs that apps installed to internal phone storage can behave in the same way. This may mean that the fast boot OFF tweak may prove beneficial to any storage area, since they all come on-line after the OS loads from phone memory.
EXT4ALL (aka Convert2ext4) = final fix for dalvik cache related bugs (?)
Further investigation of the Dalvik cache reveals a significant connection between it and a number of odd and unpleasant behaviours, including Low Disk Space warnings and disappearing apps.
Fortunately, there are some excellent XDA forum threads about dealing with the Dalvik cache.
The best recent place to start seems to be here:
[Q] Incredible running CM7.2 "Low on space" message (launched 2012-12-14)
http://forum.xda-developers.com/showthread.php?t=2047424
It is not because of the focus on the Droid Incredible or CyanoModGen in this thread, but the attention paid to the more universal fix "EXT4 4 ALL" aka "EXT4ALL" or "Convert2Ext4". (Thanks to Senior Member cmlusco for his post #9 on the thread that got me started in the right direction!)
Files can be found at these locations:
Goo.im site http://goo.im/devs/tiny4579/mods
DINC.does-it site http://dinc.does-it.net/EXT4_Mods/
One version of this fix (Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip) moves the Dalvik cache from the default, limited 150MB internal partition to the "unlimited" (or at least maximum) 750MB internal partition.
Any phone with a kernal installed that supports ext4 can utilise this fix.
[ I personally use gingertiny 2.6.35.14-v2+ (2012-02-13), which has supported ext4 since late 2011]
My own experience has been to flash the "no data limit normal dalvik" zip file using ClockworkMod 5.x Recovery -- this was entirely painless. I just downloaded the file into my phone's downloads folder on the sdcard using a web browser, then ran CM Recovery (with a little assist from ROM Manager), selected "install a zip from sdcard" and navigated to the file. It was all done in 5 minutes. After manually rebooting a second time, everything seems to be working normally after about half a day of regular use.
For those who flash a new or updated ROM sometime in the future, you would need to flash this fix after doing so.
There is plenty of information contained on the main threads of this topic. Links aplenty can be found; just follow the ones provided in the thread I suggest here to get started.
Hopefully, this brings an end to my struggles with my phone's storage issues, and to others of you reading this post and following the links to the threads and downloads.
FYI -- My storage values changed as follows after running the fix:
Total Internal memory: 748MB --> 770MB (22MB increase)
ROM free space: <1MB --> 20MB (close to the value change of total internal memory)
Used internal memory: ~335MB --> 464MB (close to 128MB increase)
Remaining internal memory: ~420MB --> 306MB (close to 128MB decrease)
So, it seems that my ROM was being used to cache app data, which would explain why the value kept declining even though I NEVER added anything to it (using Titanium Backup Pro or anything like it). When free space on my ROM literally ran out, Android OS hit the proverbial panic button and warned me to free 512kb minimum to allow Gmail to download new mail. Now, it has 20MB free (and will hopefully stay that way, since I NEVER intend to transfer anything into the ROM!) -- The internal memory usage jump of 128MB probably indicates the Dalvik cache.
SUMMARY:
1. Turning off "fast boot" in Android settings helps some, but it does not get to the heart of the issue. It will NOT make a Low Disk Storage warning go away.
2. Once you have a Low Disk Storage warning, you MUST uninstall enough apps to make it go away (keep track of what you take away, because you can reinstall them very soon!)
3. With no LDS warnings showing, flash the "Convert2ext4 no data limit normal dalvik" zip file. THIS APPEARS TO BE THE REAL SOLUTION!
4. Reinstall your recently removed apps, and you should be good to go! :fingers-crossed:
PS>>> One last unresolved issue: I am still unclear exactly WHERE the dalvik-cache ends up, since my Astro file browser cannot locate anything containing the word "cache" that does not now report "EMPTY". There are a large number of "com." folders containing software I have installed found in the /mnt/asec/ folder. The total size of the contents of this folder (362 MB) is within 100MB of the amount of internal memory reported in use. Does that 100MB represent the current size of the Dalvik cache files, or at least include them? If so, where are they located? If anyone can help me figure this bit out, I would be grateful! :fingers-crossed:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.
Hey guys....here's my situation.
I bought a Blu Touch Book 7.0 plus off of Amazon. Got it two nights ago. It's a true phablet. 512 RAM / 512 ROM - I was a little concerned but figured as long as I could root it, I was good to go.
Anyways - no I am not looking for a root. I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed. I threw in a class 10 SD, and modded Android so all apps would be downloaded/installed to my SD card (I did this using the SDK & command prompt in USB debugging mode). I had researched apps previously and began to furiously download and tweak. I threw in a T-Mobile SIM, and everything was going well, I was very happy. It actually seems to be a well made device, though it's a little bulky and the phone function works much better with a bluetooth headset.
Then, I deleted Phone.apk. Despite all apps being downloaded/installed to my SD card, space was still at a premium and I had downloaded a third party dialer. I figured worst case, I could do a factory reset and/or could simply re-download the file (I was actually about to download a good backup program tonight after work, I've been busy the past two days and my anxiety to set up other stuff got the better of me). There was no immediate issue, but shortly later I got the dreaded 'com.android.apk has stopped' (or what not) message popping up constantly. I reset the device, it booted up but it was not reading my sim, and was missing icons. That's when I did something stupid-er. I found a Phone.apk file on the net, downloaded to my device, and copied it to the relevant directory.
Since then, when I boot up, first it shows that Android is upgrading, then it shows the 'unfortunately, the process com.android.apk has stopped.' I click 'Okay,' and it keeps popping up. I wasn't able to delete the wrong Phone.apk as there was not enough time for a longpress between error messages. I was able to initiate a factory reset - I was rather relieved - I had learned a bit the past day or two via trial and error, and I would be able to re-do everything perfectly this time.
But the factory reset did not revert to the right 'Phone.apk' file. So the problem still exists....
If anyone can help me, I would be oh so grateful....thanks...
A factory reset clears all user data & apps. If you deleted the phone app from system, you will have to reflash a stock zip, which I'm assuming you don't have, or find the stock apk and put it back in the right place as a system app.
If you have Titanium Backup you can use that to do it, provided you can find the stock phone apk.
Well, a problem is, I doubt that I will be able to find any ROMs or Phone.apk's for my device. At least not for a little while. There are some ROMs out there I believe for the original Blu Touch Book - but the original has a diff processor and is running Froyo rather than ICS.
Now, if I somehow can find a workable Phone.apk or a workable ROM, how do I go about flashing/copying? I can hook up to a PC (though I'm not aware of any USB storage mode that I can turn on), but the phone itself is just about unusable unless I can manage to delete the wrong Phone.apk file, as long as the file is simply missing it will boot up without the relevant features. And - let me repeat that I did a factory reset to try and fix this - it didn't fix my problem but it erased my apps and my root access....I can probably restore root but it won't stop the warning notification from popping up non-stop.
I was able to boot into safe mode previously - but it didn't help. If there is an applicable recovery mode, I can't figure that out. To my knowledge, there is no USB Mass Storage option that I can turn on.
I purchased from Amazon, so luckily I can return the item, and worst case they review it's condition and charge a restocking fee. Of course, I was looking forward to receiving this device for more than a week and have been obsessed with it since it's arrived...and I am also temporarily back to using Sprint (in Phoenix) on a 3.5" Windows Phone (I am an ex Windows Mobile fan boy, Windows Phone disappoints) after experiencing 6 MB/s 3G speeds on T-Mobile for a day or so (on a 7 inch screen and on a prepaid plan far cheaper than what I pay Sprint). I was about to port my number. Basically I am depressed. An irony here - I'm pretty sure Amazon sold me a used device that was advertised as new. On initial boot, the Android set up program did not launch. Upon my first factory reset, the set up program launched, and the dialer skin was different than what it was out of the box. The 'refuse product if this seal is broken' sticker on the packaging was partially broken, too, although it appeared to be partially in tact. But now if I try to play that angle, I come off like a scam artist...
Anyways thank you very much for your reply...all attempts to help are appreciated quite a bit...
Taking things one step at a time, let me simplify my request:
How can I delete (or replace) a system file from my device (in this case, the incorrect Phone.apk) remotely via a USB connection? I have the sdk installed on my computer, I can connect the device to my computer, but I can't really use the device until the file is deleted. Is it possible to push via ADB? Something to that effect? Will the 'push <local> <remote>' command work even if I do not have root access? What syntax is used to specify the path? Is it possible to simply delete a file without replacing it?
Does the Phone.apk file have to be specific to my device or could it be specific simply to my mobile carrier/frequency bands and/or ICS? I realized the Phone.apk file I copied to the device earlier was for the Huawei m835, a CDMA phone running Froyo...
Or, am I simply SOL?
Thanks....
One of the things about Android devices, as a former Windows Mobile user also, is that factory resets work differently as you've found out the hard way. In WM you could delete any system file you wanted and a hard reset would restore it. On Android if a required /system file is deleted you are SOL unless you have a way of restoring a backed up version. Its highly recommended IMO to have a working recovery like CWM, TWRP and a backup before you go messing around with /system files. But with a generic android device its probably not possible to find a recovery to install. You cannot write to the /system directory without root access, adb will give you an error. You may be able to use a phone.apk from another device with the same version of android.
I did find a Phone.apk from a device with the same manufacturer, on the same frequencies, with the same screen res, running the same version of Android. I have the full System/App folder if needed.
And I may have restored root access using UnlockRoot (I have read iffy things about the program but again it's all that worked for me initially). (EDIT - I do now have root access, I was able to verify the Superuser app on the device)
However when I load the SDK and type in 'adb root,' after the 'daemon started successfully,' I quickly get an 'error: closed.' And then when I try to push the Phone.apk file to the relevant folder, I get 'failed to copy / permission denied' (EDIT as I was warned of)
Is there anything I can load onto my SD card to help? I can run probably install an APK off of my storage card. Although I am very limited in what I can do - between error messages I can only get in one quick touch of the screen (and it usually takes a few tries per touch)...I can't do anything that requires a long-click...and I had also deleted the stock keyboard and the stock browser...limits me further...
Now, if I can delete my current Phone.apk and upload the stock keyboard, I am certain I can figure this out. There has to be some way to do this....
EDIT// I packed it up to return to Amazon. If there was a solution out there, oh well...
Like I said you may have been able to use Titanium to install it as a system app and that may have taken care of things once you set it as the default app and/or removed the faulty one.
^^ Right, but the challenge was installing Titanium Backup, and then using it while the error notification popped up on the screen every split second. Unless I am missing something, only way to download it would have required me to buy a Bluetooth keyboard and struggle to pair it so I could type (I had a USB keyboard that didn't work), maybe reassociate my device with my Google account (struggling to type letter by letter between each 'OK' click), have the apk sent to my device over unsecured wifi, put the .apk on SD (or just delete the wrong apk and reboot), and then hope that I could use Titanium backup to do the trick without the ability to press anything on the screen for longer than a half second or so...
Actually, I guess that could have worked, provided the Bluetooth keyboard worked. Of course, there's the chance that the Phone.apk I found for the similar device, might not have worked. Anyways, late now. I have a new one on the way, and I was shipped a slightly used one to begin with anyways, might be for the better. I kinda feel bad that the phone is now 'defective' as a result of my impatience/etc but then again I didn't do anything that the instruction manual warned against, not to mention the instruction manual says a factory reset restores factory data, which I think infers that it restores essential system components. And as much as I was an idiot, I don't do anything which should have caused a nearly non-recoverable error. That's on Google's end. Google doesn't even really discourage rooting and if you allow Android on a device with 512MB rom...
Learning experience. One of the first things I do when I get my new one, I download a backup program and find out if there is a recovery mode. In any event, I won't make the same mistakes twice. Thanks to those who replied or considered replying. Anybody has tips for the future, that aren't obvious or easily found, feel free...
If u r rooted this is very easy.
Open sdk and type su if u get "#" then u r rooted.
If so let us know
---------- Post added at 10:05 AM ---------- Previous post was at 09:34 AM ----------
as a rethought I see u deleted system app so u were rooted
---------- Post added at 10:21 AM ---------- Previous post was at 10:05 AM ----------
Firstly adb pull the file "/proc/mounts" open it using notepad and see how system is mounted.
then remount system as rw using
"mount -o remount,rw -t yaffs2 /
<path to your system> /
system"
Now u can delete stuff or add new stuff without perm error
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
Or just download this . Maybe it'll work http://www.totalcmd.net/plugring/android_adb.html
caponer said:
Or just download this . Maybe it'll work http://www.totalcmd.net/plugring/android_adb.html
Click to expand...
Click to collapse
Eh, I already sent the phone back to Amazon. This, however, looks like a useful something to have access to in the future. Thank you for the link...
No way. Come on,why did u send it to amazon when u had me right here we could have fixed this so easily.
thref23 said:
Hey guys....here's my situation.
I bought a Blu Touch Book 7.0 plus off of Amazon. Got it two nights ago. It's a true phablet. 512 RAM / 512 ROM - I was a little concerned but figured as long as I could root it, I was good to go.
Anyways - no I am not looking for a root. I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed. I threw in a class 10 SD, and modded Android so all apps would be downloaded/installed to my SD card (I did this using the SDK & command prompt in USB debugging mode). I had researched apps previously and began to furiously download and tweak. I threw in a T-Mobile SIM, and everything was going well, I was very happy. It actually seems to be a well made device, though it's a little bulky and the phone function works much better with a bluetooth headset.
Then, I deleted Phone.apk. Despite all apps being downloaded/installed to my SD card, space was still at a premium and I had downloaded a third party dialer. I figured worst case, I could do a factory reset and/or could simply re-download the file (I was actually about to download a good backup program tonight after work, I've been busy the past two days and my anxiety to set up other stuff got the better of me). There was no immediate issue, but shortly later I got the dreaded 'com.android.apk has stopped' (or what not) message popping up constantly. I reset the device, it booted up but it was not reading my sim, and was missing icons. That's when I did something stupid-er. I found a Phone.apk file on the net, downloaded to my device, and copied it to the relevant directory.
Since then, when I boot up, first it shows that Android is upgrading, then it shows the 'unfortunately, the process com.android.apk has stopped.' I click 'Okay,' and it keeps popping up. I wasn't able to delete the wrong Phone.apk as there was not enough time for a longpress between error messages. I was able to initiate a factory reset - I was rather relieved - I had learned a bit the past day or two via trial and error, and I would be able to re-do everything perfectly this time.
But the factory reset did not revert to the right 'Phone.apk' file. So the problem still exists....
If anyone can help me, I would be oh so grateful....thanks...
Click to expand...
Click to collapse
Could you share how you did a factory reset please?
wizardofkoz said:
Could you share how you did a factory reset please?
Click to expand...
Click to collapse
Settings/Backup & reset/Factory data reset
Rooting Help
"I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed."
Can you tell me how did u root it exactly because i am trying all new ways and nothing is working they just cant pick up this phablet.
androidhelp1234 said:
"I was able to root it relatively easily after an initial failed attempt which required a factory reset - if anyone is interested, it required PDANET+ & UnlockRoot, SuperOneClick and other methods failed."
Can you tell me how did u root it exactly because i am trying all new ways and nothing is working they just cant pick up this phablet.
Click to expand...
Click to collapse
I installed PDAnet+ on my phone & PC (as a means of installing a driver for the TB Plus). Then, I ran a program called 'UnlockRoot,' followed instructions, and I had root. UnlockRoot v3.1 is what is installed on my computer.
I moved on awhile ago to the Galaxy Tab 3 7.0 (Galaxy Tab 4 7.0 would be my best recommendation for a budget phablet). The Touch Book plus only held up so well (though I still have it and it still works albeit with no speaker and a screen that needs to be color-filtered due to a mysterious type of screen damage).
DOH!
thref23 said:
I installed PDAnet+ on my phone & PC (as a means of installing a driver for the TB Plus). Then, I ran a program called 'UnlockRoot,' followed instructions, and I had root. UnlockRoot v3.1 is what is installed on my computer.
I moved on awhile ago to the Galaxy Tab 3 7.0 (Galaxy Tab 4 7.0 would be my best recommendation for a budget phablet). The Touch Book plus only held up so well (though I still have it and it still works albeit with no speaker and a screen that needs to be color-filtered due to a mysterious type of screen damage).
Click to expand...
Click to collapse
After so many weeks of hunting around and asking help on forums *which no one was able to help* i stumbled across this which i hope other will find and find useful to them to!
mobiledriverfree.blogspot.com/2015/09/blu-touchbook-g7-pc-suite-and-usb.html
This not only aloud FULL root access within 3 mins, but also gave full super user, was able to retreive lost files, rebuild the software, and reboot the phone. (not to meantion remove ALL the bloatware freeing up half the phones storage)
Enjoy!!!
LeeMarden said:
After so many weeks of hunting around and asking help on forums *which no one was able to help* i stumbled across this which i hope other will find and find useful to them to!
mobiledriverfree.blogspot.com/2015/09/blu-touchbook-g7-pc-suite-and-usb.html
This not only aloud FULL root access within 3 mins, but also gave full super user, was able to retreive lost files, rebuild the software, and reboot the phone. (not to meantion remove ALL the bloatware freeing up half the phones storage)
Enjoy!!!
Click to expand...
Click to collapse
You do realise that this thread is 3+ Years old , right ?
So I used the ACS/Shabbypenguin root method (do a Google search, I can't post links...) and followed the directions exactly. Well almost exactly, I knew of some issues so this is what I did...
First I downloaded Superuser & Superuser Elite (I previously paid for it on a different phone).
Then I downloaded the drivers and Odin and both kernals.
I installed the drivers and put my phone into development mode.
Next, I turned off my phone then turned it back on in download mode and flashed the pre-rooted kernal as per the instructions there.
Finally, I went through the process again to flash in the stock kernal.
Now the other users had issues with USB connection and the phone not being recognised, the answer to that was on page 11 of the above linked thread (editing the vold.fstab file). I did this (using ES Root Explorer) as per the instructions and restarted.
Things seemed fine for half a day. Now my phone randomly restarts, but not always randomly. I can perform specific actions to cause it to freeze and reboot (example, simply opening the vold.fstab file does this EVERY TIME, but I was able to copy/paste it to the SD card and then open and edit it and even copy/paste it back, all using ES root explorer, and no crash/reboot unless I open it specifically and yes, that's with having the system mounted as R/W).
Another thing I noticed since rooting, and it still has maintained the rooted status, is that any time my phone restarts or I restart it, I open the system tray and this stupid "tip" toast message comes up that, prior to rooting, only came up once. Now, it comes up only once after a restart but resets every time.
I tried to sign up for the ACS forums but for some reason, I've not gotten a single registration e-mail from them and messaged half their admin with no response (the fact that the site has no cancel account and no re-send activation option troubles me enough as it is and in my opinion, should be internationally illegal).
Anyway, that's the issue, I need to resolve these random restarts, which may or may not be caused by this vold.fstab file.
Also, I connect now (before when I did the fix, it worked), the computer doesn't recognise the phone so I can't even re-flash using Odin, but the phone works (until randomly restarting which is a pain...), so I am at a loss as to what the actual cause was and since nothing I change sticks when it restarts, I have no idea what the deal is.
Some more information...
Nothing I change sticks. I have programs that I uninstalled, but they still show up in the system tray after a reboot (if I click it, it says that the program is not installed, but it still shows up).
I tried swapping back the original build.prop - didn't stick.
I tried factory data reset - didn't do anything.
I tried a restore in BusyboxPro (stericon or something is the dev) - restored but there were some "errors".
Tried temporarily unrooting (Superuser Elite) - nothing.
I read about a power button issue - my power button is fine.
There is something wrong specifically with the OS in some way that certain actions cause it to freeze and restart. I have a game, "Deathworm" that I can play with no issues or freezes. I can do a few things but:
if I get on the mobile browser, sometimes it will freeze and reboot.
if I run AppManagerPro III, sometimes it crashes when calculating the cache size (always when it gets to 70/125 or whatever the total is, but always at 70 if it DOES crash).
Now I went into task manager and went through and cleared all the app data individually app per app. Before when I tried to do this (before restoring in Busybox, before restoring the original build.prop, etc), it would crash when I went into the downloaded tab of the thing to clear the cache. This time it didn't crash on me.
Other root stuff I have installed which was working before the random rebooting issue:
Script manager (free) and V6 supercharger (also unsupercharging wouldn't stick, which I tried before restoring the build.prop manually)
SuperUserElite
App Manager Pro III
SD Maid Pro
ES File Explorer (free version I think)
BusyBox Pro
SU Update Fixer
Screenshot It
After everything I just did, it seems to (for the moment) be working again, I am just waiting to see if it crashes again. So far I have opened and closed App Manager Pro III a few times and it calculated cache sizes with no crash. Right now, SD Maid Pro hasn't crashed yet open, hide certain tabs (clearing the data so I had to reset those options), close, reopen, scanned with system clean and app clean and actually did the app clean, so far no crashes (my phone would normally have crashed by now), cleared databases and no crash.
Also while I was in there, two programs I uninstalled via the system tray (menu button, edit, uninstall) that kept coming back were a buld.prop editor and some wonkey game (Fall down) or something, anyway those were in the downloaded section of task manager and I uninstalled them through there. Maybe that did it?
And no... still freeze, reboot and not saving any changes.
So far I've also tried uninstalling practically everything I installed and those changes aren't persisting (the uninstalled apps remain uninstalled, but reappear in the system tray or on the home screen if I had an icon there for it).
No changes I make to anything persist except things I save or copy to the SD card.
Tried factory reset again, still didn't stick.
So apparently SOME others have this issue without rooting, I can't tell, there's not a ton of reviews that I can find beyond "F*** STRAIGHT TALK CUSTOMER SERVICE THIS PHONE IS CRAP".
I hate to keep bumping this, but every time I have an issue, I am highly detailed in things and I NEVER EVER have EVER gotten a response EVER on this site, EVERRRRRRRRRRRRRR.
I really really really don't want to waste another ~$200 for nothing.
I would appreciate even a response of "yeah I have this problem too".
I don't want this to die like all the other threads I started...
Does anyone even have a clue as to where I can begin attempting to troubleshoot this on my own then?
What tools should I look into or what logs in what folders?
I know this post is very outdated but there may still be someone tinkering with these older phones still as I am.
Over the past few days I have been trying to get this Straight Talk Samsung Galaxy Proclaim rooted and working just for something to do.
I'm not one to ask for help to often so I end up doing a lot of reading and a lot of trial / error.
In my reading I have seen quite a few posts / comments around the net stating not to use the Shabbypenguin root method
as it is very buggy and unstable.... I can not tell you from experience so please do not quote me. I ended up using the TeamProlusion
root method and all has went very well other than a few minor problems I need to work out.
In all honesty I'm not real sure what I may post or may not.... ( Yes I need to REread the rules for sure ) but I
will leave this link for anyone that may be in need... Mods / Admins please feel free to edit this post if this is not permitted and
please accept my apologies.
Please google androidarea51
Ok, I'm new here and this is my first post, please be nice
Just got me a Guomi F3 (in Chinese, 国米 F3) and I'd like to do a clean install in English. I didn't know much about Android but I have been searching and learning to handle this situation I'm under..
I lost backup ROM and can't find a compatible one on the net yet.
This phone seems to be very new (and very minor) so I can't find a manufacture ROM or even manufacture's website..
Currently it keep showing an error message "System was damaged, The system will be unstable!"
The OS seems to belong to China Mobile (in Chinese, 引領3G生活) and it won't let me fastboot but I can access fastboot mode by ROM manager app.
Here's the spec of this phone;
- Platform: Android
- Android ver.: 4.4.4
- Android SDK ver.: 15 (Android 4.0.3)
- Kernel: Linux 3.0.8
- CPU: MT6592 2GHz Octa Core
- Root access: Yes
- RAM: 421MB
- System storage: 2.07GB
- Internal storage: 0.97GB
- External storage: 0.97GB
- GPU ver.: OpenGL LS 2.0 Spreadtrum Build
I need a custom ROM for the phone, any help would be very appreciated, thanks!
You should have done a backup before!!
Now you're helpless unless you get a stock rom or a custom rom
Use yuweng's recovery porting tool to get a custom cwm recovery(dont know whether it'll work on mt6592)
Then port a custom rom using a rom porting tool and try it
It'll be a long process but at the end of the day you'll get rid of the error and will have a custom rom too
Press thanks :good: if I've helped :highfive:
Hi arnabbiswasalsodeep, thanks for your reply :good:
I tried MT65xx Lewa OS Porting Tool but can't proceed it.. as there's no compatible lewa ROM, fails to install USB driver (Mediatek Driver Auto Installer) due to no unsigned drivers for win7.
I just hope that someone can modify or create ROM for this phone soon.. :fingers-crossed:
Use mtk firmware adapter
Many even port roms fron mtk6577 to mtk6589 using it
Press thanks :good: if I've helped :highfive:
chloem said:
Ok, I'm new here and this is my first post, please be nice
Just got me a Guomi F3 (in Chinese, 国米 F3) and I'd like to do a clean install in English. I didn't know much about Android but I have been searching and learning to handle this situation I'm under..
I lost backup ROM and can't find a compatible one on the net yet.
This phone seems to be very new (and very minor) so I can't find a manufacture ROM or even manufacture's website..
Currently it keep showing an error message "System was damaged, The system will be unstable!"
The OS seems to belong to China Mobile (in Chinese, 引領3G生活) and it won't let me fastboot but I can access fastboot mode by ROM manager app.
Here's the spec of this phone;
- Platform: Android
- Android ver.: 4.4.4
- Android SDK ver.: 15 (Android 4.0.3)
- Kernel: Linux 3.0.8
- CPU: MT6592 2GHz Octa Core
- Root access: Yes
- RAM: 421MB
- System storage: 2.07GB
- Internal storage: 0.97GB
- External storage: 0.97GB
- GPU ver.: OpenGL LS 2.0 Spreadtrum Build
I need a custom ROM for the phone, any help would be very appreciated, thanks!
Click to expand...
Click to collapse
I got the same phone. Ｉ tried and root the phone successful. Somethings went wrong in the process and the massage shows up "System was damaged, The system will be unstable!".
Have you fixed the problem? appreciate your help. Thanks
wl224 said:
I got the same phone. Ｉ tried and root the phone successful. Somethings went wrong in the process and the massage shows up "System was damaged, The system will be unstable!".
Have you fixed the problem? appreciate your help. Thanks
Click to expand...
Click to collapse
Don't worry, your phone is perfectly fine. The system is NOT damaged at all. This iRoot chinese superuser crap is what is sending the scary message. The scare tactic occurs because you deleted some other chinese bloatware which came down via the iRoot software during the rooting process. There is one chinese app in particular which when deleted will download and reinstall itself. It is the one that pops up annoyingly every 10 seconds. It's like an appstore that's trying to force you to download chinese apps. You can uninstall it by putting the phone in airplane mode and uninstalling it.
When the chinese superuser sees that that particular chinese crapware is absent, it starts to send that annoying message that the system was damaged. Just ignore it. Of course, it is hard to ignore because it flashes constantly in the middle of the screen. But you can work through the nuisance.
You see, at this point, the phone is actually properly rooted! So what you do next is simply download a root file manager (Uninstall Master or ES File Manager for example), do whatever you needed while rooted then after you've done whatever you wanted to do in the first place, just use the root file manager to delete the chinese superuser program. It's called RL King or some such non-sense. THIS WILL SAFELY UNROOT THE PHONE. In other words, you will lose root, but it will get rid of the annoying fake message that your system was damaged.
Or you can root the phone, accept the chinese crapware and be happy. Me? i unrooted my phone. I don't want any chinese crapware on it. Who knows what other sneaky stuff iRoot is doing on there. I don't speak chinese so I have no idea what all the visible crapware was for. And if they get so upset that you delete the crapware that they would spitefully put this annoying message permanently on the phone, then I DO NOT TRUST THEM!!!
My advice is TO NOT USE iRoot or vRoot for rooting your phone. You will have no idea what nastiness they are inserting directly into the root of your system with superuser privileges!
Volte4G+ CPU: MT6589 4GB RAM, 120GB ROM 2.048GHz???
I have a message every 2 second saying "System is damage, please check!!!". The system is 100% OK besides this error message.
I have used iRoot. I have installed Uninstall Master to delete KingRoot but it does not help. There must be some more bugs?
The technical spec seems to be a fraud as well.
Please advise.
stentmartin
stentmartin said:
I have a message every 2 second saying "System is damage, please check!!!". The system is 100% OK besides this error message.
I have used iRoot. I have installed Uninstall Master to delete KingRoot but it does not help. There must be some more bugs?
The technical spec seems to be a fraud as well.
Please advise.
stentmartin
Click to expand...
Click to collapse
What is your phone make and model? Can't help you unless you provide this info.
Sent from my Nexus 7 using XDA Free mobile app
System is damage, please check!!!
My Phone is a " Volte4G+". It is made by Spreadtrum.
The phone information is giving me the following info:
1. CPU: MT6589 (Spreadtrum 4G SC8830?).
2. ARM V7 architecture.
3. 8 cores
4. 2..048GHz
5. 4GB RAM
6. Internal Storage 120GB
7. 512GB micro SD Card (Installed by me)
The phone is bought from Malaysia.
Works perfect, but I can not find any tech spec that match this phone internal spec (can be fake?).
I have uninstalled KingRoot and it has nothing todo with the problem. I don't think iRoot or KingRoot is the problem (mybe emidiator). I have deleted all suspissios programs but there is of course hundreds other apps that can couse this problem!
You are absolute right about your assumption that a deleted malware program have triggered this messages.
stentmartin said:
My Phone is a " Volte4G+". It is made by Spreadtrum.
The phone information is giving me the following info:
1. CPU: MT6589 (Spreadtrum 4G SC8830?).
2. ARM V7 architecture.
3. 8 cores
4. 2..048GHz
5. 4GB RAM
6. Internal Storage 120GB
7. 512GB micro SD Card (Installed by me)
The phone is bought from Malaysia.
Works perfect, but I can not find any tech spec that match this phone internal spec (can be fake?).
I have uninstalled KingRoot and it has nothing todo with the problem. I don't think iRoot or KingRoot is the problem (mybe emidiator). I have deleted all suspissios programs but there is of course hundreds other apps that can couse this problem!
You are absolute right about your assumption that a deleted malware program have triggered this messages.
Click to expand...
Click to collapse
I guarantee you that iRoot or KingRoot were indeed the source of the problem. What I said was, one of those programs downloaded the culprit without your knowledge. I know it for a fact because my own phone was completely free of all malware. I had a brand new, clean stock ROM flashed. I then tried to root with iRoot or vRoot. Immediately after rooting, I deleted a Chinese app that got installed by the rooting program. And as soon as I deleted that program, the annoying message began. So it had to be via the rooting process and it was because I deleted that crapware.
It's possible that it's an app that cannot be deleted even by AppMaster, or the root browsers even with root permission. This is because some of the virus apps install themselves into the system partition with an attribute of i (immutable) or a (annex only). You first have to remove the "i" or "a" attribute with a terminal emulator such as Terminal Emulator from PlayStore (but your phone needs to be rooted). The problem with those attributes is that a program like AppMaster, SD Maid or Root Browser will tell you the app was deleted, but once you reboot, you will quickly find out that the app was not deleted at all. Once you remove these attributes, you can delete the offending apps permanently. So to do this, you'll have to reroot your phone. Don't be afraid to reroot because once you're rooted, you can get rid of all the crap. Also, once you're rooted, make sure you also install busybox (download and install Busy Box X from PlayStore) because it gives you access to a better suite of Linux commands that you can use via the terminal emulator app.
There is another possibility for the problem. The annoying message may be a service and not an app. In that case, you need to discover what service it is and use the app called Disable Service to permanently stop that service from running (but your phone needs to be rooted). So you'll have to reroot and then use Disable Service.
Anyway, you have an absolutely beautiful phone. Love the specs. I wonder it it uses MTK or Spreadthrum architecture. If it's MTK you can easily and quickly flash back to stock with SP Flash Tool. Otherwise you have to use the Spreadthrum tools. You will need to find your stock ROM and flash it. That's the other way to deal with it.
Let me know how it goes. I can help answer questions at each step of the way. Just remember to take screenshots to help explain what's going on if you need help.
Sent from my Nexus 7 using XDA Free mobile app
System is Damage
First. My goal withe phone is to install Ubuntu Mate and have a combined phone & Ubuntu computer.
On all tests this powerful phone have extremely low score. Reason, the tests can not handle 4G phones @ 2GHz and 8-cores or the phone is a fake or scam?
I have contacted the Seller on eBay about the Stock ROM. Normally they don't know anything..
Also I am a normal user with some computer knowledge, not a hacker or aUnix programmer.
I have downloaded and tested all programs you have suggested. Note! my phone is rooted.
The problem:
1 To use Service Disable or Uninstall apps in settings I need to know what app is causing the problem and I don't have a clue witch app I shall disable.
2. I can not find the Stock ROM to my phone.
3. I believe the my phone is a MT6589 SoC MTK device with 8-cores 2048MHZ and 120GB local storage.
At least that is what the phone is telling me.
Anyway, this is the future of computer/phones.
Possible Solutions
1. Buy another similar phone. Cost only $52 on eBay.
2. Take. backup of the new phone ROM and restore the backup to the old damage phone (delete internal storage first to get rid of malware?)
3. Compare installed apps on the phones and delete the differences on the old damage phones..
Can I use the therminal emulator to find the program causing my problem? You told me they have the "i" and "a" attribute in the mode. Can I look for some distinct features in the mode and use RM to remove the app.
In what directory shall I look?
Please advise
stentmartin
stentmartin said:
First. My goal withe phone is to install Ubuntu Mate and have a combined phone & Ubuntu computer.
On all tests this powerful phone have extremely low score. Reason, the tests can not handle 4G phones @ 2GHz and 8-cores or the phone is a fake or scam?
I have contacted the Seller on eBay about the Stock ROM. Normally they don't know anything..
Also I am a normal user with some computer knowledge, not a hacker or aUnix programmer.
I have downloaded and tested all programs you have suggested. Note! my phone is rooted.
The problem:
1 To use Service Disable or Uninstall apps in settings I need to know what app is causing the problem and I don't have a clue witch app I shall disable.
2. I can not find the Stock ROM to my phone.
3. I believe the my phone is a MT6589 SoC MTK device with 8-cores 2048MHZ and 120GB local storage.
At least that is what the phone is telling me.
Anyway, this is the future of computer/phones.
Possible Solutions
1. Buy another similar phone. Cost only $52 on eBay.
2. Take. backup of the new phone ROM and restore the backup to the old damage phone (delete internal storage first to get rid of malware?)
3. Compare installed apps on the phones and delete the differences on the old damage phones..
Can I use the therminal emulator to find the program causing my problem? You told me they have the "i" and "a" attribute in the mode. Can I look for some distinct features in the mode and use RM to remove the app.
In what directory shall I look?
Please advise
stentmartin
Click to expand...
Click to collapse
It's really difficult to tell which app is causing whatever problem you might experience on your screen.
There are a couple things you can try:
First look in Settings> Applications and flip over to the Running tab. Look for apps with strange names. Then find the app in the All apps tab and try to disable it.
Next, use a root browser and check the /system/app and /system/priv-app folders. Again, you are looking for apks that have strange names. You have to be really careful because there are some system apps that have strange names but they will often have an odex file with the same name right next to them. You can ignore these apps that have an odex sibling. WARNING: Don't delete any of the apk files in the system folders. First try to rename them to whatevername.bak. Be sure you have root permissions. If you can rename the file, then it is NOT the one you're looking for. Rename it back to whatevername.apk and try another suspicious file. If you cannot rename the file, it will throw a message like "operation failed"... THIS IS THE CULPRIT. And there could be several of them. These are the virus files that cannot be deleted by normal means because they have their attribute set to immutable or annex or both. (I'm assuming that you already deleted all the virus apps that can be deleted using a system app manager like App Master and only these stubborn ones are left).
I use ES File Explorer for my root browser. Just long click on the file you want to delete and select Properties. There on the file properties screen, I have the option to Copy Full Path. Click that to save the name of the file including the path (it will save something like /system/app/filename) so you don't have to manually type it later.
Then go to the Terminal Emulator app. Type su to get superuser privileges. Then type chattr -i -a /system/app/filename. This will remove the i and a attributes if they were on the file. Next type rm /system/app/filename. Obviously you can just paste the filename you copied to the clipboard instead of typing the whole thing and making mistakes on these tiny keyboards. Anyway, this is how to delete virus files that refuse to let you delete them. Lol. I have had to do this with infected phones that had 10 or more viruses permanently installed. This is why the copy full path is excellent. It removes the need for a lot of typing.
Let me know how it goes. But I did like your solution which was very effective....If these phones cost only $50 bucks, just buy a new one and extract the stock ROM from it. The only thing that concerns me is how could a phone so powerful only cost $50??? Sounds like a fake. I see a lot of Samsung Galaxy clones that show they have many GB of internal storage in the Settings. But if you run an app like Diskinfo on them, you'll see that they have very little RAM and very little internal memory. Some are so bad that you can't even install any apps on them because you'll get an insufficient memory error.
Sent from my Nexus 7 using XDA Free mobile app
ROM for corrupted phone
I have tried everything and can not find the virus.
Is not in the /Syste/app or /System/pri-app. If I delete all apps and goes to safe mode the virus is still there so it most be on the root level. The seller can not give me a new phone, they are out of stock and they are totally fake. They are even programmed to deceive you and the test program, a deliberate fraud or crime. It is 479MB not 4GB RAM and 1.2GB ROOM not 128GB. The CPU is a 4-core 1GHz not 8-Core 2GHz. And it is the same with all the Chinese phones I have seen. However they are nice low end phones payed by the ads you have big problems with. And as in my case, when you try you have this message "System is Damage" you can't get rid of blinking every 2 seconds.
The only way I can see now is to find a Stock ROM that works and that is not east to an MT6589 CPU.
Any suggestions?
stentmartin said:
I have tried everything and can not find the virus.
Is not in the /Syste/app or /System/pri-app. If I delete all apps and goes to safe mode the virus is still there so it most be on the root level. The seller can not give me a new phone, they are out of stock and they are totally fake. They are even programmed to deceive you and the test program, a deliberate fraud or crime. It is 479MB not 4GB RAM and 1.2GB ROOM not 128GB. The CPU is a 4-core 1GHz not 8-Core 2GHz. And it is the same with all the Chinese phones I have seen. However they are nice low end phones payed by the ads you have big problems with. And as in my case, when you try you have this message "System is Damage" you can't get rid of blinking every 2 seconds.
The only way I can see now is to find a Stock ROM that works and that is not east to an MT6589 CPU.
Any suggestions?
Click to expand...
Click to collapse
If it's not one of the apps that shows up in your listings of Running apps, then it is a service which you need to halt.
There is a root app called OS Monitor which you can download from the PlayStore. It will tell you exactly which apps and services are running at any given moment. Use it to identify which service(s) is(are) running when this message pops up.
Then use Disable Service (also a root app from PlayStore) to block/turn off those services, thereby permanently stopping the message from appearing.
Sent from my Nexus 7 using XDA Free mobile app
y320
my friends huawei y320 u10 gapps and many other process keep crashing (android core is one of it). and its spamming error message
tried factory reset, it said reset success, but all my data is still there and the crashing persist.
tried flashing the stock firmware, it said success, but everything from before the flash is still there, and the crashing error persist. (tried adb ,and sd card)
and i also found that in the storage setting , there is an internal storage and phone storage. and i found that everything that is usually sdcard0 on my other phone.
there is an option to delete phone storage, but it also doesn't work (altough it said success.)
i also can't uninstall any app on that phone (currently there is : piano tiles, farm quest saga, instagram, weibo). everytime i tried to uninstall, launcher,setting,and nearly everything else crashes,
adb (at pc ) can't read the phone unless its doing install update from adb option (at the phone).
tried using ubuntu,kali , windows, mac (pc) and tried a lot of different usb cables)
help
elyas2u said:
my friends huawei y320 u10 gapps and many other process keep crashing (android core is one of it). and its spamming error message
tried factory reset, it said reset success, but all my data is still there and the crashing persist.
tried flashing the stock firmware, it said success, but everything from before the flash is still there, and the crashing error persist. (tried adb ,and sd card)
and i also found that in the storage setting , there is an internal storage and phone storage. and i found that everything that is usually sdcard0 on my other phone.
there is an option to delete phone storage, but it also doesn't work (altough it said success.)
i also can't uninstall any app on that phone (currently there is : piano tiles, farm quest saga, instagram, weibo). everytime i tried to uninstall, launcher,setting,and nearly everything else crashes,
adb (at pc ) can't read the phone unless its doing install update from adb option (at the phone).
tried using ubuntu,kali , windows, mac (pc) and tried a lot of different usb cables)
help
Click to expand...
Click to collapse
Is the device rooted? Is it encrypted? Is the bootloader locked (by operator)?
Your EMMC may be corrupted. Forget factory reset. Hold down the volume DOWN key and then press power till the phone boots. You should see a menu. Select Clear or Wipe EMMC. Let us know what happens.
Sent from my Nexus 7 using XDA Free mobile app
I'm facing the same problem,system damaged,pleasw check.After re-root nothing happen,the massage still pop up.Try using Os monitor,cannot find weird apps running the massage.Only system running..please someone help
Qiba said:
I'm facing the same problem,system damaged,pleasw check.After re-root nothing happen,the massage still pop up.Try using Os monitor,cannot find weird apps running the massage.Only system running..please someone help
Click to expand...
Click to collapse
The message about "system damaged" comes from a virus process that is installed by certain rooting applications. That application is triggered when you attempt to delete certain apps installed by the rooting app. Nothing is wrong with your system.
What phone do you have have bro? Can't help you unless you state the make and model of your device. Also, what did you root with?
Sent from my Nexus 7 using XDA Free mobile app
stentmartin said:
I have a message every 2 second saying "System is damage, please check!!!". The system is 100% OK besides this error message.
I have used iRoot. I have installed Uninstall Master to delete KingRoot but it does not help. There must be some more bugs?
The technical spec seems to be a fraud as well.
Please advise.
stentmartin
Click to expand...
Click to collapse
If you put the phone in english and after you use iRoot. Try this:restore factory seting and root again but not change the lenguage