Woke up this morning turned on my slide with the wonderful KKDS 1.3 from Emmanuel U, dont think this is a rom issue at all as have been using this rom for a very long while.
Anyhow so i get this "
System UIDs Inconsistent" Error popup that reads :
-------------------------
System UIDs Inconsistent
UIDs on the System are Inconsistent you need to wipe the Data partition or your device will be unstable
<im feeling lucky button>
----------------------------------
so whats the exact cause of the issue, if i re flash my twrp backup will this fix my problem? why does this issue arise & is there any other way to fix?
steve_77 said:
Woke up this morning turned on my slide with the wonderful KKDS 1.3 from Emmanuel U, dont think this is a rom issue at all as have been using this rom for a very long while.
Anyhow so i get this "
System UIDs Inconsistent" Error popup that reads :
-------------------------
System UIDs Inconsistent
UIDs on the System are Inconsistent you need to wipe the Data partition or your device will be unstable
<im feeling lucky button>
----------------------------------
so whats the exact cause of the issue, if i re flash my twrp backup will this fix my problem? why does this issue arise & is there any other way to fix?
Click to expand...
Click to collapse
I wonder if it is talking about different owners of files in /data...
...unless UID means something different than User Identification. I just opened a terminal emulator (on TBalden's 10.1) and did:
ls -l /data
ls -l /data/data
This shows all the folders and files in the respective directories with the assigned UID and GID (Group Identification). There was no consistent pattern. Even in /data/data, it looks like there was a different user assigned to every folder.
Which unfortunately means the easy way, 'chown -R root:root /data' is out.
Probably the cleanest solution HERE
Related
Okay, I'm getting saddened by my continuous fails in ROM porting... I had it down before, but now it seems that nothing is going right.. after wiping /system, and using the wipe data and cache option from the main menu in Clockwork, and flashed to test. here's what happened in recovery.
http://pastebin.com/0gyXJACG
it looka all sucessful and cool, until this happens (when looked at via logcat in adb )
exec '/system/bin/sh' failed: No such file or directory (2)
Yet, I check there and the file is present, and busybox is in so why could it be happening?
I have used CyanagenMod 10.0 STABLE ROM without any issue for several days until this Morning where my Google Play kept giving error "insufficient storage space" for some reason. I read from several discussions abt this as none of them fix my problem so I decided to do followings:
Using ClockModRecovery 6.0.2.3:
1. wipe data/ factory reset
2. wipe cache
3. wipe dalvik cache
test: still got same problem
4. wipe data from the last option where there are four icons shown (Recovery, Android, USB/fast boot/ Wipe Data icons)
5. access recovery mode again and do followings
6. format system success
7. format /staging - success
8. format /data - ERROR mounting /data!
9 reboot device and still stuck at booting (THE CyangenMod logo kept showing)
10. access recovery mode again -> mount /data and /emmc FAIL
When I click the USB icon duriing initial boot, my PC (Win 7) could not detect my tablet device but when I chose Recovery mode, my PC was able to detect the device with some errors. The folder structure is shown below.
H:\Downloads\Android\TF700 Rooting>adb shell
~ # ls
ls
btmac init sys
cache init.rc system
data proc tmp
default.prop res ueventd.cardhu.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
etc sdcard
fstab.cardhu staging
When I access the system folder, there is nothing there/ I tried using below config to flash the CM10.0 ROM again and wish to fix my problem:
H:\TF700 Rooting>adb push update.zip /root/update.zip
1333 KB/s (169361362 bytes in 124.049s)
It seemed the file had been transferred but the issue remains.
I have two questions:
1. Is there anyone who knows how to enable USB debugging from clockmode recovery? I might not enabled this earlier. I s there a way to check from ADB command?
2. Any suggestion to help me recover my OS? The bad thing is that I backup my ROM to internal EMMC and now it is not mountable for some reason
Further the ADB outputs are below:
H:\Downloads\Android\TF700 Rooting>adb devices
List of devices attached
015d2XDXXXXXXXXXX device -> serialno is hidden purposely
H:\Downloads\Android\TF700 Rooting>adb get-state
device
H:\Downloads\Android\TF700 Rooting>adb get-serialno
015d2XDXXXXXXXXXX -> hidden purposely
H:\Downloads\Android\TF700 Rooting>adb root
H:\Downloads\Android\TF700 Rooting>adb shell
[email protected]:/ $ su
su
Permission denied
1|[email protected]:/ $ superuser
superuser
/system/bin/sh: superuser: not found
127|[email protected]:/ $
I hope I did not brick my tablet since I am still able to view the root folders and access the clockMod Recovery consistently. please correct me if I am wrong "whew".
PLZ HELP..
Problem Fixed. I managed to fixed my own problme by flashing with Stock ROM.
Managed to fix my own problem eventually by Flashing to Stock ROM.
Hopefully this helps whoever gets same problem as mine.
Hey Guys,
For the past few weeks, I have been suffering from file system corruption on my /data partition, and have been trying to fix it. The phone gives me SOD's and random reboots (kernel related) and the last kmsg.logs tell me about ext-4 fs errors and journal corruption ( something along the lines of that). I have ran e2fsck on /data, /cache/, and /system and it always fixes all the errors but after time they always re-appear and I know because of an SOD or reboot, and lather, rinse, and repeat. I came to the conclusion that maybe there are newly developed bad blocks on the internal NAND which continuously corrupt the filesystem by reading and writing to them, and I want to get them marked. Running e2fsck -c gave me: Badblocks not found, and so I searched on what to do. I came across a thread that said push the Badblocks binary to sbin and tried that, but now I get "Illegal Instruction" instead of No Badblocks Binary. What can I do to mark these blocks? Is there an alternative to at least check to see if bad blocks are present? Thanks in advance.
Symptoms:
Phone stucks at boot animation screen (4 color balls rolling)
adb devices command shows device is represent.
adb logcat shows no fatal error, no obvious cause
kernel message shows no fatal error
Cause:
Content inside /data/system/sync is corrupted(?)
Fix:
Rename or remove folder /data/system/sync
Below is the full story and how I figure it out:
3 days ago when I woke up, i find that my phone was rebooting and the screen showing boot animation. After waiting a long time, I find that the phone was stuck on boot animation. I can use adb shell to connect the phone and adb logcat to retrieve the log. The log shows nothing special or fatal, just some minor errors.
My phone is rooted, unlooked and relocked bootloader, CWM Recovery 6.0.4.4
The apps I installed that have root access included, but not limited to:
Xposed FrameworkAndroid Tuner aka 3C ToolboxGravityBoxiFontXprivacyGreenifyAFWall+BusyBoxSuperSucom.avast.android.mobilesecuritycom.avast.android.antitheft (Root install)
After Googled a few hours, 99.9% of the result tell you factory reset your phone is the fix, and i am not satisfied with that. So I used CWM recovery to made a complete backup, and tinkering with the files and system.
At first I cleared cache and dalvik-cache in recovery as this is easiest, but no luck.
Then I suspect this might be a flash memory chip problem , so I boot into recovery, use adb shell to connect console, however, adb shows that device unauthorized, so I do a factory reset and reboot recovery, then adb shell again and success, and in recovery, restore /data backup. Then I use command
Code:
%path to android platform tools folder%> adb push adbkey.pub /data/misc adb/adb_keys
, then adb is authorized after reboots.
To check if the flash memory is okay, i used the command:
Code:
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/cache
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck -fv /dev/block/platform/msm_sdcc.1/by-name/system
The result seems fine, and no signs of hardware failure.
After reading logcat, the system seems nearly finished the booting process, and stucked at end of System service, and never signal Boot_Completed. Using Android Device Monitor, system_process main thread is still running and doing something unknown.
At this point, i think kernel and /system should be normal.
Then I suspect that the apps i installed might be the cause, I renamed the folders like:
Code:
mv /data/data /data/data.old
mv /sdcard/Android /sdcard/Android.old
mv /data/app /data/app.old
to see if the OS can boot normally, but no luck.
I also renamed many other app folders and reboot, but none of this can solve the bootloop problem.
Then I renamed /data/system and reboot, from the logcat, i can see the system is regenerating the content inside the system, and I waited for a moment, the OS booted successfully with many "xxx process stopped" error message on the screen. So at this moment I realized that content in /data/system might be the root of all evil. As Home screen is not usable with a lot of process stopped messages, I used this command to start the apps i want.
Code:
adb shell monkey -p com.yourpackage.name -c android.intent.category.LAUNCHER 1
(Need to use some game points )
Next I used command
Code:
find /data/system -mtime -3
to find out which files were altered within last 3 days. I get a list of files and folder and then I rename the folders one by one and reboot. Finally, /data/system/sync folder is confirmed as the cause of the problem.
I restored the full backup in recovery, and renamed the /data/system/sync folder to /data/system/sync.old and reboot. Phone boots normally, everything seems fine.
I don't know what, why, how exactly causing the boot problem, but the problem is solved anyway. Hope this information can help someone.
I used 40+ hrs to figure it out, and another 2+ hrs to summarize and write this.
fxxk.
Nice work!
Sent from my Nexus 5 using Tapatalk
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, what should I do for this, Thank you in advance for your Help.
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, then im trying to open bootloader but it is not responding. what should I do for this, Thank you in advance for your Help
TUPANGPUTi23 said:
Sir my Samsung J2 Core is stuck on BootAnimation, because of the new System Webview that i installed on Magisk, then im trying to open bootloader but it is not responding. what should I do for this, Thank you in advance for your Help
Click to expand...
Click to collapse
Probably best to ask in your devices forums. This is for the Nexus 5, not the Samsun J2 Core.
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
Ciome said:
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
Click to expand...
Click to collapse
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
rzr86 said:
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
Click to expand...
Click to collapse
No he just told me to get the last version for my phone.
Ciome said:
No he just told me to get the last version for my phone.
Click to expand...
Click to collapse
actually i am saying the same thing