Database Info

[Q] SystemUi not installing

Im running a rooted transformer overclocked with clemsyn kernel on 8.6.5.9 and i recently flashed the htc jetstream (puccini) system bar and it went without a hitch. Problem came when the new 8.6.5.13 update was released and i had to revert the mod in order to update. I made the mistake of just deleting the systemUi.apk from the /system/app folder by way of root explorer and after a series of force closes i reboot, only to find that i no longer have a system bar. I have tried to manually put the systemUi.apk that i pulled from a system dump back in the correct folder and reboot to no avail. Ive even tried to flash the puccini system bar again, but still no luck. Is there any way to get back the system bar without completely reseting the transformer?

the puccini mod only changed the button images not the system ui apk as a rule of thumb dont delete system apps. you do not have to revert an asthetic mod before flashing. Just re flash whatever rom you are on and you should be fine. also post in the correct section next time

im on the stock rom, i was under the impression that i had to revert the mod i made to the systemui.apk because the update process would not work

if you made changes to the system ui then that means you are rooted if you are rooted you will not get the stock update. you just have to do it manually
go here and get the right one for your model "http://ca.asus.com/en/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download"

tried to flash it through cwm but it wouldnt work i got,
assert failed: write_raw_image("/tmp/blob". "staging")
E:Error in /sdcard/WW_epad-user-8.6.5.9.zip

K i would just suggest flashing a custom ROM like revolver or prime that will fix all of your issues or maby one of the repackaged firmwares
http://forum.xda-developers.com/showthread.php?t=1281161

The repackaged firmware cannot be flashed without the systemui.apk fix and as for flashing a new rom will that erase all my data or will it stay intact?

your data will stay there on a custom rom unless you clear data in cwm but always best to make a backup with titanium before you do it

i just restored my asus to stock from the settings menu and after the process, still no system bar, cwm will not allow me to flash the update you posted above because it "cannot open it". Im not sure what else i can do, maybe somebody had the systemUi.apk i can put back in the correct folder or a flashable .zip

Can't write to system with ICS CWM Roms, can with stock Odin

I'm one of those who seems to still have problems with all the ROMs that I don't when Odining the stock. I still have the shutdown lockup no matter what I do when flashing ROMs (tried mhx's SuperLite and NexusMod).
But the one that's really driving me nuts is that despite superuser permissions seemingly working fine, I can't modify/remove system files. Can't replace my build.prop, system apps, anything. If I paste something new or rename a file it'll act like it worked but it won't have done anything. If I paste over something it says not enough space.
Has anyone else observed this issue? Is there a fix?

Do you have an insecure kernel? If not you won't be able to write to system from within ICS.

mohan_kr or romracer unsecured ics kernels,

promiseofcake said:
Do you have an insecure kernel? If not you won't be able to write to system from within ICS.
Click to expand...
Click to collapse
Yeah, they both use romracer's kernel, so that must be in. Any downside to flashing the stock kernel?

Now that you mention it, I am having a hell of a time writing /system from within ICS too. I am using romracer's kernel as well. In addition, my sysrw, sysro, remount etc system/xbin files (pushed via recovery ADB) keep disappearing. I'm stumped.

Frogacuda said:
I'm one of those who seems to still have problems with all the ROMs that I don't when Odining the stock. I still have the shutdown lockup no matter what I do when flashing ROMs (tried mhx's SuperLite and NexusMod).
But the one that's really driving me nuts is that despite superuser permissions seemingly working fine, I can't modify/remove system files. Can't replace my build.prop, system apps, anything. If I paste something new or rename a file it'll act like it worked but it won't have done anything. If I paste over something it says not enough space.
Has anyone else observed this issue? Is there a fix?
Click to expand...
Click to collapse
promiseofcake said:
Now that you mention it, I am having a hell of a time writing /system from within ICS too. I am using romracer's kernel as well. In addition, my sysrw, sysro, remount etc system/xbin files (pushed via recovery ADB) keep disappearing. I'm stumped.
Click to expand...
Click to collapse
Hey guys take a look at this post.
http://forum.xda-developers.com/showpost.php?p=24740309&postcount=37

galaxyuser88 said:
Hey guys take a look at this post.
http://forum.xda-developers.com/showpost.php?p=24740309&postcount=37
Click to expand...
Click to collapse
galaxyuser88 said:
1. Odin the 1-Click ICS rom.
2. Flash CWM (any version, they all work).
3. Flash SuperUser.
4. Install BusyBox <<<< make sure you add busybox before you flash your favorite rom. Otherwise you will have problems.
5. then flash your favorite Rom.. Enjoy.
Click to expand...
Click to collapse
I don't really know how that would help, for example when you get to step 5, many roms wipe /system, /data, /cache, etc. What good would doing these flashes first be? I don't see how it could honestly do anything.

This is a longshot, but what are you using to write files? I don't remember which rom I used, but when I used Root Explorer, it didn't work. But, when I switched to ES Explorer (turn on root explorer option), it did. Maybe try another file explorer?

jedah said:
This is a longshot, but what are you using to write files? I don't remember which rom I used, but when I used Root Explorer, it didn't work. But, when I switched to ES Explorer (turn on root explorer option), it did. Maybe try another file explorer?
Click to expand...
Click to collapse
Root Explorer is no go. But I am talking about mounting rw over adb.
EDIT:
Why don't you try to use SuperSu instead of Superuser. I am getting perfect reboots now with the SuperSu binary. I will try the /system mounting.
EDIT2:
Mounting /system failed, boo.

I am having the same issue with NexusMod ICS 3.

U can not adb push to system while device is running.
Shutdown bootup cwm non touch recovery mount system then u can push to system all u want......but u can use root explorer to write to system as well iffffffffffffffffff
---------- Post added at 01:46 AM ---------- Previous post was at 01:44 AM ----------
You flash this in cwm http://forum.xda-developers.com/showpost.php?p=21750986&postcount=1
Reboot
Open new SuperSU app and let it update binary

AROMA file manager that works on Explorer? [SOLVED]

Is there any version of AROMA file manager that works properly on the Explorer? I have discovered that I have some how lost the busybox binary from /system/xbin and now I need to replace it, which I think would probably be easiest by copying from /system/bin with AROMA FM. (If there's a better way, please let me know and I'll do it instead).
(At the moment, my phone won't boot, so it's kinda urgent...)

Isn't easyer to just flash the rom that you already have, with wiping only cache?

shortyoko said:
Isn't easyer to just flash the rom that you already have, with wiping only cache?
Click to expand...
Click to collapse
No, seeing as that wouldn't fix anything...I'm on stock ROM which does not include busybox, so flashing it would achieve nothing. (To clarify, busybox is required by some script(s) I have installed)
EDIT: Turns out that the latest version of AROMA FM works fine. Booting is certainly getting further now than it did before

then flash something new

TUDVAD said:
then flash something new
Click to expand...
Click to collapse
No thank you. I have fixed the issue now, without needing to flash a new ROM or anything silly like that (my current setup is exactly what I want, there is no point in me changing it and having to go through the hassle of restoring all my apps, setting up all my accounts again etc.).
All I needed to do was use the latest AROMA FM to copy busybox from /system/bin to /system/xbin. Took all of about 20 seconds once I got a card reader and the latest version of AROMA. Compared to the time required to download and flash a new ROM, and all the app restoring that would be required following doing so (and I don't even have completely updated backups, so I'd be missing some apps/data), I think my solution was better.

....
SifJar said:
No thank you. I have fixed the issue now, without needing to flash a new ROM or anything silly like that (my current setup is exactly what I want, there is no point in me changing it and having to go through the hassle of restoring all my apps, setting up all my accounts again etc.).
All I needed to do was use the latest AROMA FM to copy busybox from /system/bin to /system/xbin. Took all of about 20 seconds once I got a card reader and the latest version of AROMA. Compared to the time required to download and flash a new ROM, and all the app restoring that would be required following doing so (and I don't even have completely updated backups, so I'd be missing some apps/data), I think my solution was better.
Click to expand...
Click to collapse
if u found it can u plz post the link/.......:good:

bid4sumit said:
if u found it can u plz post the link/.......:good:
Click to expand...
Click to collapse
Like I said, the latest version of AROMA FM (1.8 was the version I used) works fine as-is. Here's a link to it: http://forum.xda-developers.com/showthread.php?t=1646108

Trying to set write permissions on /system ends in bootloop

hi,
i did a big mistake. I wanted to install some vpn apps, which requires write permission on /system. I downloaded root explorer und tried to set all permissions for the system folder. But the app stills lacks the wanted permissions, so i started root explorer again and additionally checked the checkboxes under "special permissions". After doing that android crashed, the "systemui" process crashed and restarted and crashed ...
I rebootet the device, but i only see "google" and then comes a reboot and the device boots into recovery (TWRP 2.6.3.4). I already tried the "fix permissions" under advanced, but it didn't helped.
Is there any way to fix whatever i did wrong and not lose any data?
Any help would be greatly appreciated
Greetings k1x1987

Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk

d
jyuuken said:
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. I don't want to miss something this time and complety brick my device. Could you/anybody tell me exactly what and how do flash to recover my device?
I did all the rooting stuff with the "Nexus Root Toolkit" program and followed strictly guides, except this time
Do i have to flash the rom with ADB? which file(s) should i flash system.img only? Or i have to flash more files?
A short noob guide would be really appreciated :good:
Greetings k1x1987

So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.

es0tericcha0s said:
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
Click to expand...
Click to collapse
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987

k1x1987 said:
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
Click to expand...
Click to collapse
Just flash the system.img in fastboot.

Most devs recommend wiping /system first.
fastboot erase system
fastboot flash system system.img
I would also erase cache too.
fastboot erase cache
That will clear the cache, not the dalvik, but think that should be enough to get going.

...and once it is fixed, never change system permissions again.... Same a Linux, never change permissions at /root

.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks

k1x1987 said:
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
Click to expand...
Click to collapse
Using fastboot, flash the cache image from the factory image, fastboot flash cache cache.img

^ That should do the trick. If not, well, let's not go there yet. The cache should fix it. If that does, do yourself a favor and back up your EFS folder and save it somewhere safe. Either use TWRP or flash the EFS backup tool from here: http://forum.xda-developers.com/showthread.php?t=2514095

build.prop modification caused loss of root, now stuck with bad build.prop

Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery

memrah said:
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
Click to expand...
Click to collapse
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop

-Hope- said:
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
Click to expand...
Click to collapse
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.

memrah said:
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
Click to expand...
Click to collapse
Clear cache

-Hope- said:
Clear cache
Click to expand...
Click to collapse
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help

memrah said:
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
Click to expand...
Click to collapse
Updato.com
Sammobile.com < official site

Thanks. I flashed my Note3 with stock Lollipop ROM downloaded from Sammobile.