Hi All,
(Reposting this as previous post was on more generic forum... I've read tons of Threads here, but not yet found a solution).
My Galaxy Tab 10.1 is useless right now as it cannot write to internal storage.
Lots of apps crashing on use and doing a factory reset from the recovery menu does not help (Tablet is in exact same state aon reboot).
So, I've been using adb:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Here's the mount information from shell
[email protected]:/mnt/asec $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Click to expand...
Click to collapse
So, I've tried to mount manually from adb shell:
[email protected]:/ $ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]:/ $
[email protected]:/ $ mount -o remount,rw -t rfs /dev/block/stl9 /system
mount -o remount,rw -t rfs /dev/block/stl9 /system
mount: Operation not permitted
Click to expand...
Click to collapse
But, I have no SU command:
[email protected]:/ $ su
su
/system/bin/sh: su: not found
Click to expand...
Click to collapse
I've got the su binary from downloading off aforum, but I cannot copy that up either (even to seemingly writable mount points)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push su /cache
failed to copy 'su' to '/cache/su': Permission denied
Click to expand...
Click to collapse
So then I followed a guide I found linked on a forum to get the Tablet Restocked to factory settings.
However, when I try to write via Odin, I get an error message on the tablet in Red:
Bct_sync_Odin: Error to NvBuBctUpdate![err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DownloadPartition![err:0x140005]
Click to expand...
Click to collapse
Is my tablet bricked ?
Cheers,
Ro
Same issue here. Every reboot resets it to the same state.
froalskiner said:
Same issue here. Every reboot resets it to the same state.
Click to expand...
Click to collapse
why don't you just download new firmware from sammobile.com abdominal flash it via odin..
Enviado desde mi GT-P7500 usando XDA Premium HD app
msedek said:
why don't you just download new firmware from sammobile.com abdominal flash it via odin..
Enviado desde mi GT-P7500 usando XDA Premium HD app
Click to expand...
Click to collapse
Doesn't look like that will work as the disk is mounted in read-only mode.
Using Odin, I get an error message on the tablet in Red:
Bct_sync_Odin: Error to NvBuBctUpdate![err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DownloadPartition![err:0x140005]
Click to expand...
Click to collapse
Do you have an already flashed cwm recovery?If yes try going to advanced/fix permissions.
nighthawk696969 said:
Do you have an already flashed cwm recovery?If yes try going to advanced/fix permissions.
Click to expand...
Click to collapse
Nope, never flashed the Tablet.
robilco said:
Nope, never flashed the Tablet.
Click to expand...
Click to collapse
Then maybe it's a hardware failure. Claim warranty from Samsung.
Panos_dm said:
Then maybe it's a hardware failure. Claim warranty from Samsung.
Click to expand...
Click to collapse
Yep, in an ideal world I'd deffo do this.
But I bought a refurbished Tablet so only came with a 90-day warranty.
Plus, I bought it in the US and I live in Ireland, so European service centre's won't touch it.
My only option is to ship it to a company in Texas, for €60 then attempted repair for $199 + $80 shipping back to Ireland.
Its a little too much .... So, I'm on the lookout for a smashed tablet that I can buy and recover a mainboard from.
Hi robilco,
Did you ever find a solution to your problem? I'm experiencing this exact problem. In fact, I've tried just about everything you did mentioned in this thread and more including trying to an upgrade/restore from Kies and no luck.
I can't do anything from Odin because I'm getting the same errors as you. Can't write or transfer anything via adb just like you. Since it's not rooted, I can't change permissions and because everything appears to be read-only, I can't root it!
It was working fine until the end of June. I turned off my tablet for an extended period because I was not using it. When I turned it back on I noticed that it was taking a long time to start up. It was stuck on the Samsung Galaxy Tab 10.1 logo for about 10 minutes before it finally proceeded to the load up. When it finally starts up, it will start to run all the updates after which it will freeze up and stay frozen until the battery drains or I force a hard reboot, after which again it will stay on the Samsung Galaxy Tab 10.1 logo for another 10 minutes when I turn it on again.
I was able to get around the update freezing by immediately shutting off the internet once it loads up and turning off all automatic updates.
Also every time it starts up, it will start back up in the same state it was before. That is, if I change any settings, adjust the date/or time, install any new software, or anything like that, it will reset to the previous state once I restart the tablet again. I suspect the operating system is stuck in some sort of read-only state since I cannot make any permanent change.
I also cannot perform any factory reset on it. I've tried both the software reset through the Android settings menu and doing a factory hard reset by going into the Android System Recovery <3e> mode and it always returns to the same state it was mentioned earlier.
I also cannot perform the Ice Cream Sandwich update because after it downloads, it needs to reset and again it will be stuck on the logo for about 10 minutes before returning to the aforementioned state. I've tried the upgrade about 3 times now.
The issue is definitely not related to the battery since it is always fully charged when I try making changes and I have 12.68GB space left on a 13.11GB capacity.
Yep - Looks like we have the EXACT same issue and tried all the same resolutions.
I've also been trying the 'nvflash' tool but no luck there (yet)
I've been told the only option is to return it to samsung and get it fixed.
But since I bought my table in USA and I'm now in Europe, Samsung Europe have no interest in helping me and it would cost too much to get it repaired.
I'm on the lookout for a smashed tablet that I can get on eBay or a replacement mainboard so I could just switch out the component.
Ro
sienarot said:
Hi robilco,
Did you ever find a solution to your problem? I'm experiencing this exact problem. In fact, I've tried just about everything you did mentioned in this thread and more including trying to an upgrade/restore from Kies and no luck.
I can't do anything from Odin because I'm getting the same errors as you. Can't write or transfer anything via adb just like you. Since it's not rooted, I can't change permissions and because everything appears to be read-only, I can't root it!
It was working fine until the end of June. I turned off my tablet for an extended period because I was not using it. When I turned it back on I noticed that it was taking a long time to start up. It was stuck on the Samsung Galaxy Tab 10.1 logo for about 10 minutes before it finally proceeded to the load up. When it finally starts up, it will start to run all the updates after which it will freeze up and stay frozen until the battery drains or I force a hard reboot, after which again it will stay on the Samsung Galaxy Tab 10.1 logo for another 10 minutes when I turn it on again.
I was able to get around the update freezing by immediately shutting off the internet once it loads up and turning off all automatic updates.
Also every time it starts up, it will start back up in the same state it was before. That is, if I change any settings, adjust the date/or time, install any new software, or anything like that, it will reset to the previous state once I restart the tablet again. I suspect the operating system is stuck in some sort of read-only state since I cannot make any permanent change.
I also cannot perform any factory reset on it. I've tried both the software reset through the Android settings menu and doing a factory hard reset by going into the Android System Recovery <3e> mode and it always returns to the same state it was mentioned earlier.
I also cannot perform the Ice Cream Sandwich update because after it downloads, it needs to reset and again it will be stuck on the logo for about 10 minutes before returning to the aforementioned state. I've tried the upgrade about 3 times now.
The issue is definitely not related to the battery since it is always fully charged when I try making changes and I have 12.68GB space left on a 13.11GB capacity.
Click to expand...
Click to collapse
robilco said:
Yep - Looks like we have the EXACT same issue and tried all the same resolutions.
I've also been trying the 'nvflash' tool but no luck there (yet)
I've been told the only option is to return it to samsung and get it fixed.
But since I bought my table in USA and I'm now in Europe, Samsung Europe have no interest in helping me and it would cost too much to get it repaired.
I'm on the lookout for a smashed tablet that I can get on eBay or a replacement mainboard so I could just switch out the component.
Ro
Click to expand...
Click to collapse
I've found a few posts from users with what sounds like the same issue as ours but no solution either. I've also tried going through the Samsung route but at this point they haven't been very responsive. Their only response was a canned message asking me for my contact info -- something I already provided them with when I submitted my trouble ticket. They haven't even followed up with that or my repeated attempts to get a response.
Way to go Samsung.
Related
why does my hero boot up in safe mode?
been flashing new roms and some seem to force phone to boot in safe mode, tried wiping phone and all ext all re flashing?
any ideas..
and what is "safe mode"? first time i hear of a hero running in "safe mode"...
when in safe mode, it seem to run as bare rom no installed apps can be seen and no apps can be installed
you do know that a rom can wipe your phone during flashing?
what happens when you try to install an app, why does it not work etc...
edit: i might have an idea, give me the output of these three commands (while your phone is in "safe mode"):
Code:
adb shell mount
adb shell df -h
adb shell ls -al /data/
cheers when installing the just dont show in launch or shortcust but market shows they installed. when typrin mount get
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p2 /system/sd ext3 rw,noatime,nodiratime,errors=continue,data=
ordered 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
hope the above means something to someone, I've no longer in Safe Mode flash ahearo v4 and back normal for now.
but clues on how to get out Safe Mode as its happened a few time
I think most on here (including me) are still confused on what this "safe mode" actually is.
Lennyuk said:
I think most on here (including me) are still confused on what this "safe mode" actually is.
Click to expand...
Click to collapse
exactly. i am still 100% convinced there is no such thing as safe mode, and it was just something gone wrong with his phone. but since people just want help and are not able and/or willing to follow instructions here we will probably never find out...
kendong2.. next time i get safe mode what do you want? I tried to mount and posted the reply. the phone displays Safe Mode in bottom left of the screen
kendong2 said:
exactly. i am still 100% convinced there is no such thing as safe mode, and it was just something gone wrong with his phone. but since people just want help and are not able and/or willing to follow instructions here we will probably never find out...
Click to expand...
Click to collapse
It most certainly does exist!
See here.
Power off and reboot whilst holding down "Menu" all the way to the home screen to get into safe mode.
Regards,
Dave
cheers foxmeister, ive possible got bad button then andits not result of bad flashing as i dont need hold any button down and phone was booting into safe made
ive got it out of safe mode your suppose to just old menu and power while it boots.
after many attemptrs got out by removing battery and holdt phone menu and power while it boots completely
foxmeister said:
It most certainly does exist!
See here.
Power off and reboot whilst holding down "Menu" all the way to the home screen to get into safe mode.
Regards,
Dave
Click to expand...
Click to collapse
so i stand corrected... good find, and interesting stuff! anybody knows how it works? and how and what for we can abuse it?
foxmeister said:
It most certainly does exist!
See here.
Power off and reboot whilst holding down "Menu" all the way to the home screen to get into safe mode.
Regards,
Dave
Click to expand...
Click to collapse
Edit: I just give it a try and... My thumb aches really bad... I finally find the watermark. Thanks.
jokies said:
Safe mode? I think it's called recovery. Since it's developer call it so...
Click to expand...
Click to collapse
I suggest you *try* it before commenting further, because it clearly calls itself "Safe Mode" and it totally unrelated to the recovery console!
Regards,
Dave
i cant update my dell streak 5
cant do any recovery ..
error message
current mode : clockmod recovery v.2.5.0.1
E.Cant find MISC :
E.Cant find MISC :
E.Cant find MISC :
i tried to factory reset
error message : no app2sd partition found.skipping format of /sd-ext.
my friend told me to restore it .
then i tried it also ..
it came out error meassage : MD5 mismatch
E.Cant find MISC :
E.Cant find MISC :
E.Cant find MISC :
what can i do ?
[email protected]
whiteordark said:
current mode : clockmod recovery v.2.5.0.1
Click to expand...
Click to collapse
we here normally dont use cmw because it has known issues...
how bout trying DSC 1.0? all of the required file to upgrade is there ... including the streakmod recovery...
what is DSC 1.0 ? can elaborate more .. coz i rely stupid at this ..
now my dell can even recovery reset .. oh my god ..
read this till the end and make sure you understand fully... before doing anything...
http://forum.xda-developers.com/showthread.php?t=1394866
and read other thread as well...
error message
i read everything .. and i did it but
there is a problem here ..
the error message state
E: can't mount /dev/block/mmcb1k1p5 or mmcb1k1p1
E: can't mount sdcard:update.pkg
You need to use StreakMod recovery, not ClockWork.
http://forum.xda-developers.com/showthread.php?t=840326
help
Edrill said:
You need to use StreakMod recovery, not ClockWork.
http://forum.xda-developers.com/showthread.php?t=840326
Click to expand...
Click to collapse
thank man, recovery is ok but it display error message
e: can not mount / dev / block / innersd0p5
e: can not mount CACHE: recovery / log
e: can not open CACHE: recovery / log
e: can not mount / dev / block / innersd0p5
i search for possible repair, i borrow few micro sd from friends and tried.
it came out with the same error message .. is there any other ways ?
it cant update.pkg ..
here is another error message
E:Can't mount /dev/block/innersd0p5
(Invalid argument)
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/innersd0p5
(Invalid argument)
W:Can't unlink CACHE:recovery/command
please help.
Hello, all, Sorry for my english.
I am trying to port ClockWork to a Huawei Vision U8850
when i run recovery mod, have a some errors:
1) E: can't find misc
2) E: can't mount /cache/recovery/commnad
3) E; can't mount /cache/recovery/log
recovery.fstab
Code:
# mount point fstype device [device2]
/boot mtd boot
/cache ext3 /dev/block/mmcblk0p11
/data ext3 /dev/block/mmcblk0p8
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk1p1
/system ext3 /dev/block/mmcblk0p7
/sd-ext ext4 /dev/block/mmcblk0p2
mounts point on device
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p7 /system ext3 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p10 /hidden ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p9 /hidden/data ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p11 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,
allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,
allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/ru.dublgis.dgismobile-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,i
ocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
where i can mount misc and what happens with cache? If used sdcard for mount /misc did work it?
clockwork has known issues with streak... that is why streakmod is the best...
deysmacro said:
clockwork has known issues with streak... that is why streakmod is the best...
Click to expand...
Click to collapse
is streakmod is the best, where i find source code for port, and or whatever the problem with /misc partition?
I've got this issue as well. Plus a system UIDs inconsistent error as well. More over, a lot of apps force close immediately.
Judging by what I've researched about this error amongst Android devices is that it seems to be an hardware issue. I've tried re-flashing ROMs, factory resetting, wiping data etc but it either masks the problem so the device is usable (just Google Play always force closes) or it randomly resets itself, but very weirdly, the apps remain but the data is missing.
I also may have read somewhere that in fastboot you can do a SD check? I fear that that the internal SD is damaged, could possibly have been from dropping the device a few times in the last few weeks?
If anyone does have any ideas to help, the device is now stuck at the Dell logo, I've tried reflashing a rom (PCM7) which has worked
absolutely fine before to no avail. I've tried restoring an old nandroid backup from December 12 which was done with none of these problems had been occuring, again, no success. In fact, when I do a full nandroid restore, it doesn't say it has completed sucessfully,
just comes up with the can't mount cache error etc etc
I can get into recovery and fastboot, just done an SD test through fastboot and the internal SD has passed.
Any suggestions?
Did you receive pop up mention something about UID inconsistent and have to wipe cache partition? And in the bottom said something like I'm feeling lucky?
If yes, pull out battery for a while, then change recovery (cwm, twrp or cwm by hpa). Wipe data, cache partition, dalvik cache. Reboot then wipe again. Flash any rom you want, wipe again, Fix permission then reboot.
Sent from my DELL Streak using Tapatalk 2
nom051205 said:
Did you receive pop up mention something about UID inconsistent and have to wipe cache partition? And in the bottom said something like I'm feeling lucky?
If yes, pull out battery for a while, then change recovery (cwm, twrp or cwm by hpa). Wipe data, cache partition, dalvik cache. Reboot then wipe again. Flash any rom you want, wipe again, Fix permission then reboot.
Sent from my DELL Streak using Tapatalk 2
Click to expand...
Click to collapse
That's exactly right. And I will do as you suggest.
My initial fear that the internal SD might be damaged and therefore need replacing kind of went out the window when I did the SD test which it passed.
SuperKeeper said:
That's exactly right. And I will do as you suggest.
My initial fear that the internal SD might be damaged and therefore need replacing kind of went out the window when I did the SD test which it passed.
Click to expand...
Click to collapse
Some said that is a malware and maybe streakmod recovery did not perform totally wipe / clean wipe.
Sent from my DELL Streak using Tapatalk 2
nom051205 said:
Some said that is a malware and maybe streakmod recovery did not perform totally wipe / clean wipe.
Sent from my DELL Streak using Tapatalk 2
Click to expand...
Click to collapse
Well it seems to have worked! Flashed a ROM sucessfully at the first attempt, so far so good!
And that point does make sense because when the device re-booted itself, the data went but the apps remained.
Any reason why I should go back to streakmod recovery? Generally around here everyone favours streakmod over clockwork mod.
SuperKeeper said:
Well it seems to have worked! Flashed a ROM sucessfully at the first attempt, so far so good!
And that point does make sense because when the device re-booted itself, the data went but the apps remained.
Any reason why I should go back to streakmod recovery? Generally around here everyone favours streakmod over clockwork mod.
Click to expand...
Click to collapse
So, how it go now? Any reboot again or stuck on dell logo?
Sent from my DELL Streak using Tapatalk 2
nom051205 said:
So, how it go now? Any reboot again or stuck on dell logo?
Sent from my DELL Streak using Tapatalk 2
Click to expand...
Click to collapse
Well I did manage to get a ROM flashed successfully and the device booted fine.
BUT- not too long after, it decided to reset itself but the apps remained therefore some are decided not to work, even an uninstall and reinstall didn't work. Also, can't install anything from Google Play either, get a package file is invalid error. So I'll have to do what you suggested again. Still think there is an underlying problem somewhere even though there isn't that system UIDs inconsistent error and cache loading error in recovery mode.
I get an error of sorts when wiping data- E:format_volume: make_extf4fs failed on dev/block/mmcblk1p2 but it also says that the data wipe is complete
tl;dr
What I really would like is some way to move a file from my phone's internal storage (it's in /data/data/...) to my computer when it's connected via USB. I'll settle for a way to find my SD card directory and move it there. Alternatively, I'd be okay with putting it somewhere that survives a factory reset from recovery mode.
I'm bad with technology. I can only get my phone into recovery and/or download modes, and I want to pull a few files off it before I factory restore. I am on the default firmware (though my phone IS rooted) and I have no interest whatsoever in doing things like putting CWM on here. Thank you in advance for not suggesting anything of the sort!
I have adb installed. My computer "sees" my phone just fine. I can use adb shell and muck around, but I get "permission denied" when I try to look at anything other than the root directory or do anything. How do I change these permissions, or copy an entire folder despite them? I tried looking into it more and got "adbd cannot run as root" as an error, which I don't understand because my phone is rooted and Superuser is installed. Is it just because I can't turn the damn thing on?
I can get to the files (and see them) if I open ADB and use "su -" and remount the system as RW, which I figured out thanks to Google. I can see the file just fine, I just don't know the command to move it. Is it "cat"?
edit: it does seem to be "cat", for moving internally, but I can't move it anywhere that I can figure out how to access. I have an SD card in my phone, and /sdcard and /sdcard1 both seem to exist, but using cat to move a file to either of them won't make it actually show up on my SD card. Also, using ls on /sdcard doesn't display anything at all, so I don't see /sdcard/external_sd which google maybe suggested I should.
edit2: this is what "adb shell mount" returns. I don't think it's seeing my SD card at all:
C:\Users\User>adb shell mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p9 /system ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
Click to expand...
Click to collapse
if I use "cd /mnt" and "ls" it doesn't return anything, so it doesn't see anything there.
edit3: I can also move the file with "dd". What a journey of discovery I'm having here! I just can't figure out how to move it somewhere that actually gets it off the phone. I tried exiting the shell (via Ctrl-D) and then using pull, but it just gave me permission denied again. I have it in /sdcard/ and I tried using "adb shell cat" and I created a file that has the only contents "permission denied"
I would also accept a way to just rip every single file, since I know the location of the thing I want, I just can't DO anything to it.
Thank you again in advance, I'm really bad with this stuff and I appreciate it.
Probably a total jerk move to bump this, but I've managed to narrow the topic down significantly, and maybe everyone will think there's a reply and flock in to read it and one of those people will be able to help me!
Greetings,
I'm looking for help in the following scenario: some days ago I found that my Galaxy Note had rebooted, and got stuck at the Samsung logo. The phone has the stock rom, it is not rooted and is running Jellybean.
Recovering from this situation hasn't been possible. I tried:
- pulling the battery
- rebooting from recovery mode
- wiping cache partition.
I haven't tried a factory reset because the problem appeared as I was on vacation and there are some some photos I'd like to recover.
Taking this also as a learning experience, I have read several documents on recovery mode, adb, etc. So far I have managed to access via ADB. I could successfully run adb pull, however it seems not all data came through.
I don't have /mnt visible, no DCIM folder, and sdcard or sdcard1 have no contents. I've attached the screenshot of the Android Device Monitor.
For example, adb pull /sdcard returns 0 files.
I think maybe something is not properly mounted...? I tried to search similar issues it's not clear to me how to proceed. Anyway this is the output of 'mount' in case is helps:
[email protected]:/dev $ mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p9 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
Thank you in advance for your help!
So after spending some time experimenting and reading about filesystems, ADB, sideloading, recovery mode (even went to a Samsung repair centre (they answered straight "no" regarding getting data from the internal memory)), I had to go with the factory reset.
So I answered 'yes' to all the warnings about losing all data, took a deep breath and waited...
Phone turns back on, usual out-of-the-box wizards etc, and then I start realising some options are the same as I had them... then I open the camera and notice a known picture in the gallery thumbnail... so, in a Christmas miracle, all my photos and personal files were NOT touched by the factory reset! It all lies inside /storage/sdcard0 and apparently this isn't touched by the reset.
Hi guys! I need help because I have a problem that I do not manage to give it to an end. I think (hope not) I bricked my phone.
I have a Kyocera Brigadier (Verizon edition), where after many attempts, I succeeded to root it with Kingroot. I was very glad that I could to customize it like the old Nexus One. I installed Xposed and some modules like Gravity... All good. I was away in vacation and I said to test it more. I installed Busybox and Super Rom Tools. I did Install in BusyBox and in the morning I did not manage to wake the phone. I did a soft reset (keeping pressed power button 20 sec.), all good until I put it on sleep. It was the sleep of death. And again I had to forcibly restart. At one point it appeared above applications the default wallpaper, and oscillate when the home screen, when default wallpaper. An error message appear after few moments: Unfortunately, the process com.android.systemui has stopped. I went into Recovery (stock) and wanted to delete the cache but mistakenly (stress and nerves) gave reset phone, meaning Restore to factory settings. Besides the fact that I lost pictures and videos from vacation, I lost all applications and settings ... I said this is it, this happens if you don´t have your head on your shoulders. I was installed Titanium but I had not done any backup yet.
I tried now to uninstall applications imposed by Verizon, and try to eliminate the annoying message "This year SIM card is from unknown source" so I deleted one by one all applications and services that belonged to Verizon and Kyocera. I must say that after factory reset, remained the root and custom boot screen. Seeing that fail to get rid of that message, I said I'll try again when I get back home from vacation. I did again reset to factory default and surprise, it no longer occurs any application from Verizon or Kyocera, all I wiped disappeared. I did reset again and nothing. The custom boot screen was put to me, but not appears the Setup Wizard of the phone. I said this is it and so I do not want them ... After setting up my Gmail account when I tried to install applications from Google Play it gives me unknown error "-110". OK, I tried from the SD card and send it to me: For security .... bla bla ... block installation of apps obtained from unknown sources , but this setting is gray and I can not to mark off. I thought it was something from the root, and I did clean root from Kingroot but gave me error and gone and application and root. In settings of the phone it says at Root status - unknown (before it said rooted or unrooted)
Now I got home, I connected the phone to the computer and try to do adb install to see if it works. Recognizes it at adb devices, but if I give adb install any app it gives me this error:
C:\Android\sdk\platform-tools>adb install kingroot.apk
3221 KB/s (6649985 bytes in 2.015s)
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please fix.
pkg: /data/local/tmp/kingroot.apk
Failure [INSTALL_FAILED_INTERNAL_ERROR]
I tried to root it again with desktop version of Kingroot, Kingoroot, Rootgenius but no success...
What I noticed:
- all phone applications have 0.00B and at storage stays at Calculating...
- system time I think it's not correct, although it looks right it is set at 13/01/1970...
- whole system memory is read only. I cannot change anything, all apps data and settings are stored in the RAM flash not in ROM memory
I done before some roots and install custom recovery and ROMs of several phones like Nexus One, Galaxy Nexus, SII, SIII, Nexus 4, Motorola Xoom but I´m not a developer, I´m a firefighter so my knowledge of programming are limited... I just helped some friends to customize their phones and use their phone at max capacity.
So please can someone give me some solution to try? Some adb commands....
btw the bootloader is locked by Verizon
I have another friend with same phone, can I make a nand backup and flash it on my phone? How?
Thank you for your time!
Best regards!
THE SOLUTION!!!
I attach some screenshots maybe it help...
BUMP
Over 40 views and no solution to try?!
I played more today with ADB and I attach some results...
I tried to root it again with Kingroot PC version but no success...
Anyone knows how to make system read/write? Because I think this is the big problem.... If I can install apps maybe I can root it again with Kingroot apk...
In bootloader appear the sunken Android and an little 1 in the top left side and that´s all, tried fastboot oem unlock but failed, other commands like flash didn´t tried.
Please, any idea?
Best regards!
Hi,
I bought last week, the European Brigadier aka Torque KC-S701 and i had to root it but any success for now !
I read about your issue and i'm asking regarding your adb command's results :
C:\SDK\sdk\platform-tools>fastboot oem unlock
...
FAILED (status read failed (Too many links))
finished. total time: 1602.805s
1) What was your aim doing that ? Unlocking the Brigadier ?
- a) Your bootloader had to be unprotected
- b) adb reboot-bootloader
- c) Fasboot devices
???
- d) If something apeared then
fastboot oem unlock
Vol UP to select opened cadenas and Vol Down to check it
- e) Reboot with
fastboot reboot-bootloader
2) What about now with the following command "adb shell' and 'll' or 'ls -al' ? did you compare with the first time as in your txt file ?
3) Maybe an idea : 'adb reboot recovery' ?
In all the cases, the real challenge is to mount /system in rw to push the 'root files' ...
Let us know about your tries ...
If Kyocera can flash your phone from scratch, that means it's able for us/someone to do the same ... :fingers-crossed:
the adb commands working perfectly...
- adb reboot-bootloader - phone reboots in bootloader (it appear sunken android with a little 1 in top left corner and that´s all)
- adb reboot recovery - phone reboots in recovery (you have only 3 options in recovery: reboot phone, restore to factory settings clean up cache memory)
With fastboot oem unlock command nothing happened on screen. Tried some combination of Vol UP, Vol Down, power button but nothing (I thought the options was hide from user viewing)... On nexus devices and other few, at this command you´ll be asked for Bootloader unlock but in this case Verizon make something well done...
In no one screen mode (recovery, bootloader, safe mode and normal) any command adb shell, adb remount, adb fastboot which contain /system failed for write mount... read only... (maybe I didn´t write the commands well)
Kyocera can flash the phone because they have the tools... I talk with a friend which told me that there is a chance by disassemble 2 phones (mine and one working good) and make a connection on the motherboard with some special cables with Box tool but it´s a risky operation.... There is chance to brick both phones and then Kyocera Service Center cannot do anything. Beside, opening the phones it´s hard to resealing again for water protection.
The only easy chance is to unlock bootloader and flash then original or custom ROM. but...
Obsy said:
the adb commands working perfectly...
- adb reboot-bootloader - phone reboots in bootloader (it appear sunken android with a little 1 in top left corner and that´s all)
- adb reboot recovery - phone reboots in recovery (you have only 3 options in recovery: reboot phone, restore to factory settings clean up cache memory)
With fastboot oem unlock command nothing happened on screen. Tried some combination of Vol UP, Vol Down, power button but nothing (I thought the options was hide from user viewing)... On nexus devices and other few, at this command you´ll be asked for Bootloader unlock but in this case Verizon make something well done...
In no one screen mode (recovery, bootloader, safe mode and normal) any command adb shell, adb remount, adb fastboot which contain /system failed for write mount... read only... (maybe I didn´t write the commands well)
Kyocera can flash the phone because they have the tools... I talk with a friend which told me that there is a chance by disassemble 2 phones (mine and one working good) and make a connection on the motherboard with some special cables with Box tool but it´s a risky operation.... There is chance to brick both phones and then Kyocera Service Center cannot do anything. Beside, opening the phones it´s hard to resealing again for water protection.
The only easy chance is to unlock bootloader and flash then original or custom ROM. but...
Click to expand...
Click to collapse
Well, I read you and sommething seems to be intersting ... Whenyou go into recovery, you found 3 options then 'Restore to factory settings' and your will be back alive ! I suppose ... :laugh:
I think thius is the only way to 'recover' a working phone because seing your pictures ... your phone dis not respond correctly !
Give you a try ... :good:
Lol, if you didn´t observe it I did it few times - restore to factory setting but unfortunately the programs and services which I delete it was from eprom memory so now is nothing to restore. And now with the system files blocked on read only I cannot push it them back....
So, unable for you to restore but what happened when you did a : 'adb shell && ll '?
What did you see compare to your txt file ? The same or not ?
This is ADB shell from today. What's curious is that date and time are prehistorical and nothing change except the dev and data files... What should be mentioned is that system file is locked to 15.05.2015 the time when phone went crazy....
Obsy said:
This is ADB shell from today. What's curious is that date and time are prehistorical and nothing change except the dev and data files... What should be mentioned is that system file is locked to 15.05.2015 the time when phone went crazy....
Click to expand...
Click to collapse
The date are not prehistorical ... i have the same date about on my Torque KC-S701 as 1970-01-01. Which could be intersting seemed to be the different date for some directories (1970/01/01 21h36 to 1970/01/03 02h43) ... WEIRD !
Take a look on mine.txt in attachment.
So try to go on /system and make a ll to compare 'permissions' with mine.
I think you made a recovery with weird present recovery in your phone. Weird because different to the original ...
So, you told us /system was now RO, did you try to re root your phone by the same way used your first time ? This could be give you the right to put in RW that you want and to get from someone which have the same phone, the original directories which are differantly dated as your first ...
This is just an idea ... :silly:
Rood i did with Kingroot.apk but now I cannot install any app nor Play Store (error -110) neither SD card (cannot pass by unknown source)... I tried the desktop version of Kingroot but no success...
I did cd /system and here it is.
All seems to be good ...
USB debugging is active because you can use adb without any problem.
Did you try a adb shell fix_permissions ? I saw you tried to install kingroot by adb but did you try to re-ionstall kingroot.apk with adb.exe -r kingroot.apk ?
So, on your screenshots, we can see calculating place taking by apps but whitout any results ... Did tou try to see sommething by adb shell df just to see if you can see something in /data ?
So, what about adb shell mount ?
In all the cases, without root, you can't mount /system in RW !
I hope you'll get more further info to solve your issue without sending your phone for flashing to Kyocera !
....
zegoo said:
All seems to be good ...
USB debugging is active because you can use adb without any problem.
Did you try a adb shell fix_permissions ? I saw you tried to install kingroot by adb but did you try to re-ionstall kingroot.apk with adb.exe -r kingroot.apk ?
So, on your screenshots, we can see calculating place taking by apps but whitout any results ... Did tou try to see sommething by adb shell df just to see if you can see something in /data ?
So, what about adb shell mount ?
In all the cases, without root, you can't mount /system in RW !
I hope you'll get more further info to solve your issue without sending your phone for flashing to Kyocera !
Click to expand...
Click to collapse
adb.exe don´t work...
adb install -r kingroot.apk same error...
adb shell df and mount > this is the results:
C:\SDK\sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 926.4M 132.0K 926.3M 4096
/sys/fs/cgroup 926.4M 12.0K 926.4M 4096
/mnt/asec 926.4M 0.0K 926.4M 4096
/mnt/obb 926.4M 0.0K 926.4M 4096
/system 1.4G 959.0M 515.2M 4096
/data 11.6G 352.3M 11.2G 4096
/cache 845.6M 13.6M 832.0M 4096
/persist 7.8M 4.1M 3.8M 4096
/firmware 64.0M 56.9M 7.1M 16384
/sysprop 7.8M 5.0M 2.8M 4096
/carrier 39.3M 4.0M 35.3M 4096
/mnt/shell/emulated 11.6G 352.3M 11.2G 4096
/storage/emulated/legacy 11.6G 352.3M 11.2G 4096
/data/DxDrm/fuse: Permission denied
/mnt/media_rw/sdcard1: Permission denied
/storage/sdcard1 14.8G 7.5G 7.3G 8192
C:\SDK\sdk\platform-tools>adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=948676k,nr_inodes=181731,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=948676k,nr_inodes=181731,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=948676k,nr_inodes=181731,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=948676k,nr_inodes=181731,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/sysprop /sysprop ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/carrier /carrier ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=1013,group_id=1000,allow_other 0 0
/dev/block/vold/179:64 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso88591,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
C:\SDK\sdk\platform-tools>
If u can understand something... o.0
Thanks!
Why did you say 'adb.exe' does not work ?
'adb' or 'adb.exe' is the same ...
So you wrote that your memory is in Read Only, i don't understand ... Were you talking about /data because /data is ReadWritable ?
I know we have not got the same phone but there is my 'mount result command' in attachment. /data is in RW as it should be and /system in RO as too.
You should compare this two files, may be you'll find something instersting to solve your issue ... So is there someone which have the same phone which could give you the same command result to compare ? :good:
adb.exe no such command
On mount beside some numbers I have this line in addition to yours
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=1013,group_id=100 0,allow_other 0 0
Yes, the /data is RO or corrupted
C:\SDK\sdk\platform-tools>adb shell
[email protected]:/ $ cd /system
cd /system
[email protected]:/system $ ll
ll
drwxr-xr-x root root 2015-05-18 23:45 app
drwxr-xr-x root shell 2015-05-18 23:45 bin
-rw-r--r-- root root 6120 2015-05-15 21:25 build.prop
drwxr-xr-x root root 2015-05-10 08:08 csc
drwxr-xr-x root root 2015-05-15 20:40 etc
drwxr-xr-x root root 2014-07-13 22:18 fonts
drwxr-xr-x root root 2014-07-13 22:18 framework
drwxrwx--x root root 2014-07-13 22:18 kcjprop
drwxr-xr-x root root 2014-07-13 22:18 lib
drwx------ root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2015-05-16 22:42 media
drwxr-xr-x root root 2015-05-18 22:39 priv-app
drwxr-xr-x root root 2014-07-13 22:18 tts
drwxr-xr-x root root 2015-05-09 17:40 usr
drwxr-xr-x root shell 2014-07-13 22:18 vendor
drwxr-xr-x root shell 2015-05-18 23:45 xbin
[email protected]:/system $ cd /data
cd /data
[email protected]:/data $ ll
ll
opendir failed, Permission denied
255|[email protected]:/data $
255|[email protected]:/data $ df
df
Filesystem Size Used Free Blksize
/dev 926.4M 132.0K 926.3M 4096
/sys/fs/cgroup 926.4M 12.0K 926.4M 4096
/mnt/asec 926.4M 0.0K 926.4M 4096
/mnt/obb 926.4M 0.0K 926.4M 4096
/system 1.4G 959.0M 515.2M 4096
/data 11.6G 938.7M 10.7G 4096
/cache 845.6M 13.6M 832.0M 4096
/persist 7.8M 4.1M 3.8M 4096
/firmware 64.0M 56.9M 7.1M 16384
/sysprop 7.8M 5.0M 2.8M 4096
/carrier 39.3M 4.0M 35.3M 4096
/mnt/shell/emulated 11.6G 938.7M 10.7G 4096
/storage/emulated/legacy 11.6G 938.7M 10.7G 4096
/data/DxDrm/fuse: Permission denied
/mnt/media_rw/sdcard1: Permission denied
/storage/sdcard1 14.8G 7.5G 7.3G 8192
1|[email protected]:/data $
BTW u have LTE working on Orange?
Humm, about 'adb.exe', you are under windows and when you write 'adb' or 'adb.exe', this is the same. Juste take a look inside the directory where 'adb.exe' is located.
So, under Linux, for my mind, i wrote 'adb ' ...
Regarding your '/data', i can read:
'/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc, data=ordered 0 0' in the result of your mount command, that's meaning '/data' is correctly mounted in 'RW' as it had to be.
Regarding the line(s) which is(are) different between our each 'mount command', i don't know more further ... Weird !
Regarding the 'll command' when you to see in '/data', i have exactly the same ... This is a Kyocera protection ! Sucks !
The only weird thing i saw regarding your different command are as your phone was in its first stage when you bought it that's why i have an advice ...
Try to get 'root' again ! You had to succeed to push the files needed in '/data/local/tmp' as it was done before. :good:
For LTE, your right, the Torque KC-S701 is for European market and is able regarding LTE French network aka Orange for Free network for my mind ... as it should be regarding your Brigadier if Verizon and Kyocera respected the law ... We have the same equipment, the only difference is the screen, better is yours ! Lucky guy !
Today from nothing, the "sleep of death" and "the process com.android.systemui has stopped" come back.... Clear cache from fastboot didn´t help, only restore to factory settings.....
I played with some adb commands and this is the results. If someone have time to watch it and maybe have an idea.... Thanks!
So... Hear is very clearly what u need to do. But before I tell u I want to make somethings clear.
Root access alone will not make /system rw.
You have to mount system as rw.
Apps that relay on root access will do this for u if they modify the /system which exposed would have.
Also removing/uninstalling /system apps is not ever recommend for many reasons. If there were ever an update you would not be able to apply the update.
You have titanium back up. Use the freeze option instead. This allows u to restore the app if ever needed.
Now on to your issue. Please forgive me as your OP is a bit of a run on and broken English.
From what I can understand (and with a bit of guessing) one of your xposed mods cause a FC of the system UI. Which lead u to hunt down issues in the wrong place (even if u hadnot factory reset clear cache would have done no good)
Xposed is.... OK... But has many fundamental flaws in a nut Shell it replaces a few native .jars with hooks built into them (this in of itself modified files in the /system of which the normal end user has no idea which files so right off the back you will never be able to update your system if ever and OTA comes for it)
Secondly the biggest flaw in exposed... The modules. Way to much trust is given to the creator of said module and many of the modules I inspect have modules active by default. This is a HUGE no no because say a certain aspect of this module does not work with your current rom(version of Android altered by OEM and carrier) well guess what happens... You have just created a device that when it boots it runs that module which causes the system UI to crash and now u can not access or use your phone. And because your rooted but not unlocked (bootloader not carrier unlocked) you have no custom recovery and therefore no way to restore the /system partition of your device... Welcome to your house hold another paper weight brick.
So you or any average Android "tinkerer" thinks (and rightfully so because its says EVERYWHERE a factory reset will restore my phone to like the day I got it) I can restore my phone with a reset. Well that is true to an extent. If you never touched the /system partition of your device a factory reset just erases all data in /data (user data partition) and presto phone is back to new... However the simple act of rooting a device touched the /system to place two files in there. The su binary and the supersuer apk.
Anyways. To continue on. I hope the above info enlightens you to your current issue. You need to restore your /system partiton... How do I do this you ask.. Well IF you had root you could replace every file you modified or touched or removed (with the exact same file that comes preloaded can not be a copy of an apk from the play store and another device that's "close enough")
Each file must be signed from your OEM.
OK so you say well **** I don't have root access any more.
Still not the end of the world. You could fastboot flash (or whatever means of bootloader communication Kyocera uses)
However because your bootloader is locked you can not just flash the /system with anything. It must be an image signed by OEM and or carrier.
And sense most oems do not have just a system img to flash you will need to locate the entire package they flash, and it must be for your EXACT DEVICE if you flash say an AT&T package on your vzw device you will only cause fastboot flash failures due to signing mismatch or worse.
So I leave you with this.
Google
Fastboot OEM files for (insert device name/brand/carrier)
And may I wish u the best of luck
Sent from my Nexus 6 using Tapatalk 2
Thank you too much for your time!
English isn´t my primary language.. and I don´t use Google translate.... only when i don´t remember something... The biggest mistake I did was to unroot the phone, I get an error and from then /data was corrupted
The phone worked well one week with Xposed modules until I installed Busybox. Next day the mess begin. So I blame Busybox. Now I don´t have root and any other apps installed, xposed or modules and I het again that systemui error? Why?
I can´t find any OEM files for Kyocera Brigadier... so can I get one from a functionally phone? Like I said, I had 2 friends with same phone, one rooted and one not
Which commands should I use for it? Did you see the last adb commands I used? one post before?
Thanks again!
Obsy said:
Thank you too much for your time!
English isn´t my primary language.. and I don´t use Google translate.... only when i don´t remember something... The biggest mistake I did was to unroot the phone, I get an error and from then /data was corrupted
The phone worked well one week with Xposed modules until I installed Busybox. Next day the mess begin. So I blame Busybox. Now I don´t have root and any other apps installed, xposed or modules and I het again that systemui error? Why?
I can´t find any OEM files for Kyocera Brigadier... so can I get one from a functionally phone? Like I said, I had 2 friends with same phone, one rooted and one not
Which commands should I use for it? Did you see the last adb commands I used? one post before?
Thanks again!
Click to expand...
Click to collapse
You will have xposed installed tho. Not the apk but remember the app xposed installs and replaces files inside the system.
The system UI failure is likely due to on the the apks u uninstalled via titanium backup.
To hunt the exact reason u have the UI fc preform a logcat
Boot phone...
Connect to pc
From your directory with adb open comand promnt on pc (assuming your using Windows)
Type
adb logcat > systemuifc.txt
Cause the UI to crash...
Wait 30 seconds then close the command prompt
This will create a text file of the logcat in the directory.
Look thru the logcat to find what caused the UI to crash.
U can email it to me and I can browse it
My user name at g mail dot com
Sent from my SHIELD Tablet using Tapatalk 2
---------- Post added at 02:26 PM ---------- Previous post was at 02:07 PM ----------
I thought I read somewhere... But I looked back and didn't see it. Is the su binary anywhere in /system/xbin/
Because unless u removed it manually or used some kind of app to remove it, it should still be there...
If it is. And we can find the issue for UI crash and what apps u need, I'm sure it's fixable...
But the larger issue is fixing the corrupted /data
I would preform a factory wipe in recovery, then in fastboot mode use command prompt
fastboot erase userdata
That would be the only thing I could think of to try and correct the corrupt data
Once u get the data corruption issue dealt with. You "could" pull any missing apks from your friends phone. Then push them to yours once u get your data partition fixed, and re root
Sent from my Nexus 6 using Tapatalk 2