Hi.
Thanks to everyone who might give me some help.
I have a new quad-core phone with android 4.2.1, that is now useless. It can not boot, it freeze at second bootlogo, before animation.
It is rooted, and i have made some changes to build.prop. It worked fine, but after some time i realized the gallery and camera app was gone.
Then i did following:
Installed updated standard gallery+camera apk found online, both in the same app. from here http://forum.xda-developers.com/showthread.php?t=2341080
Works great, but i wanted to make it a system app, so did that with titanium backup.
After that, the camera app is gone. Gallery app is still working.
So i tried to change it back to user app, again with titanium, but did not stop working. After some time i took out the battery.
Now it freeze before boot animation.
I tried "wipe data/factory reset" and "wipe cache partition", in system recovery but still not booting!
I tried to backup user data from another phone, same model, and restore on this one but says "Error: checksum compare fail".
Do i need to flash a new rom to the phone with my pc? I have not tried this before, and i want to keep stock rom.
I have read this page:
http://www.chargeforums.com/forum/d...-flashing-roms-return-stock-odin-picture.html
But i can not get it in download mode, with those hotkeys?
If it is to any help, i have acces to other working phones of the same model.
Flashing new? It's look like this. How? I don't know because I have no information over ur phone.
Gesendet von meinem Xperia SP
joke19 said:
Flashing new? It's look like this. How? I don't know because I have no information over ur phone.
Gesendet von meinem Xperia SP
Click to expand...
Click to collapse
Its a noname phone imported from China.
The model is called A999M or Android Grand 1.
I can go in system recovery with volume up + power. But not helping. The only other boot menu i can acces, is only sometimes with volume down + power, i will get a menu but all en chinese.
I managed to get the bad build.prop file from the phone with adb, and see the error in it. But i can not get write acces to change/replace the file.
I compared the build.prop i modified on crashed phone, with working phone and the difference is following all changed to a OEM name (with Capial first letter, that gives problems):
ro.product.name=hexing89_we_jb2
ro.product.device=hexing89_we_jb2
ro.product.board=hexing89_we_jb2
ro.build.product=hexing89_we_jb2
"adb root" returns "adbd cannot run as root in production builds" and all other options like remount for r/w acces gives "remount failed: Operation not permitted"
The phone was rooted with framaroot:
http://forum.xda-developers.com/showthread.php?t=2130276
Would be very glad for some help. If you have the answer to fix it, i might even pay a little for your time.
So adb connects right?
Try this
adb shell
ls -l /dev/block/partitions
And from here keep searching and try to find by name (we are looking for system partition here)
If you can't find it from a shell try
cat /proc/partitions
Or just simply
Mount
If you find system then run this
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
Or whatever path to /system is
Then
You can simply push or use dd commands to push new build.prop and then chmod permissions to 644
Let me know what comes of this, as I know nothing about your phone but it sounds very fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So adb connects right?
Try this
adb shell
ls -l /dev/block/partitions
And from here keep searching and try to find by name (we are looking for system partition here)
If you can't find it from a shell try
cat /proc/partitions
Or just simply
Mount
If you find system then run this
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
Or whatever path to /system is
Then
You can simply push or use dd commands to push new build.prop and then chmod permissions to 644
Let me know what comes of this, as I know nothing about your phone but it sounds very fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi.
I can not do that. First i already found the build.prop file. I can simply put "adb shell", and "cd /system", and "ls -all", and then i see the build.prop file.
I can also go youre way and do "mount -o rw,remount /dev/block/mmcblk0p5 /system", but it says "mount: Operation not permitted"
Remember i can not do adb root. I get "adbd cannot run as root in production builds".
I can also not do "su" inside adb shell. Everytime i do, prompt freezes. I think my phone is suposed to prompt me for Su acces, but shows nothing but the boot logo.
So for now, the problem is i have only read acces. No write acces.
Were not looking to list everything in system partition, rather trying to fin the block, I just wrote some random block that I'm sure is not yours unless you have some old mtd phone
In other words don't ls /system but rather /dev/block..... Until you find the block or use cat or mount or whatever to find it so you know what to mount
Also can you get to recovery and use adb there? If so I would recommend this as your system is already goofed up
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Were not looking to list everything in system partition, rather trying to fin the block, I just wrote some random block that I'm sure is not yours unless you have some old mtd phone
In other words don't ls /system but rather /dev/block..... Until you find the block or use cat or mount or whatever to find it so you know what to mount
Also can you get to recovery and use adb there? If so I would recommend this as your system is already goofed up
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi.
If i just write "mount" i get:
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
If i just write "ls -all" i get:
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p7
I hope i got the info you wanted. What should i write next?
Well we know its ext4 file system but we still don't have the block location
Try
ls -l -a /dev/block/platform
And see what you get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Not near a PC so just ran a terminal emulator so I can show you what we hope to find
If you have a by-name directory you're golden, if not we will keep looking
(Hit __ twice by accident in screen shot)
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Well we know its ext4 file system but we still don't have the block location
Try
ls -l -a /dev/block/platform
And see what you get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Inside "block" i get:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk1
mmcblk1p1
platform
vold
Inside "platform" i get:
mtk-msdc.0
mtk-msdc.1
Inside "mtk-msdc.0" i get:
by-num
mmcblk0 -> /dev/block/mmcblk0
mmcblk0boot0 -> /dev/block/mmcblk0boot0
mmcblk0boot1 -> /dev/block/mmcblk0boot1
mmcblk0p1 -> /dev/block/mmcblk0p1
mmcblk0p2 -> /dev/block/mmcblk0p2
mmcblk0p3 -> /dev/block/mmcblk0p3
mmcblk0p4 -> /dev/block/mmcblk0p4
mmcblk0p5 -> /dev/block/mmcblk0p5
mmcblk0p6 -> /dev/block/mmcblk0p6
mmcblk0p7 -> /dev/block/mmcblk0p7
mmcblk0p8 -> /dev/block/mmcblk0p8
Inside "mtk-msdc.1" i get:
by-num
mmcblk1 -> /dev/block/mmcblk1
mmcblk1p1 -> /dev/block/mmcblk1p1
Sorry I'm blind, your mount showed /system is being called android, so you need to change the mount command from earlier to mmcblk0p5 from mtd....
Also did you try running adb from recovery mode?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Sorry I'm blind, your mount showed /system is being called android, so you need to change the mount command from earlier to mmcblk0p5 from mtd....
Also did you try running adb from recovery mode?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried:
[email protected]:/ $ mount -o rw,remount /dev/block/mmcblk0p5 /system
mount -o rw,remount /dev/block/mmcblk0p5 /system
mount: Operation not permitted
I think its because i can not do "su". Its just stops when i write it, and waiting on an empty line.
In system recovery i tried "wipe data/factory reset" and "wipe cache partition". But it does not help, since it will not recover system files like build.prop that is faulty. I also tried to "apply update" from zip and adb with the correct build.prop. But it can not apply it.
What recovery do you have? Stock? Custom?
Have you tried adb through recovery?
After you hit su does the prompt change from $ to # ?
Actually if you copy and paste all input/output from cmd/terminal when you try them out it is easier to help fix
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
What recovery do you have? Stock? Custom?
Have you tried adb through recovery?
After you hit su does the prompt change from $ to # ?
Actually if you copy and paste all input/output from cmd/terminal when you try them out it is easier to help fix
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe its just stock recovery. When im in recovery menu, i can not connect with adb.
C:\Users\Dennis>adb shell
[email protected]:/ $ su
su
-waiting on this empty line-
Mmm.... Does the oem have a website, often if you can find it there will be stock firmware/software with instructions on how to flash it. Like through fastboot or some download mode (maybe that Chinese writing screen - try getting a photo of it and see if someone will be nice and translate it for you)
Often there is some flash suite for these no-name devices like rockchips have as well as some well known OEMS
But without root access and no oem software this may be more difficult than I hoped, check around a bit and let me know what you find
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Mmm.... Does the oem have a website, often if you can find it there will be stock firmware/software with instructions on how to flash it. Like through fastboot or some download mode (maybe that Chinese writing screen - try getting a photo of it and see if someone will be nice and translate it for you)
Often there is some flash suite for these no-name devices like rockchips have as well as some well known OEMS
But without root access and no oem software this may be more difficult than I hoped, check around a bit and let me know what you find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay thank you. Im thinking if its possible to take a nandroid backup from a working phone (my girlfriend have one too), and recover on this one. But dont know if i can recover without root acces?
No worries, does your recovery have a nandroid backup and install function? If so then this would be ideal! The other option maybe to use dd commands to take her system.img and restore to yours through dd, but to me this is always a last resort as dd didn't get/the nickname disk destroyer for nothing! (_although it is safe so long as you don't mistype)
But start by looking for oem software and a flash mode if your recovery doesn't have backup restore options
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
No worries, does your recovery have a nandroid backup and install function? If so then this would be ideal! The other option maybe to use dd commands to take her system.img and restore to yours through dd, but to me this is always a last resort as dd didn't get/the nickname disk destroyer for nothing! (_although it is safe so long as you don't mistype)
But start by looking for oem software and a flash mode if your recovery doesn't have backup restore options
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There is no oem software, i have to work it out myself. The stock recovery only have options to backup and restore "user date". Not the system. But still i already tried to restore a backup from another phone, but get checksum error. I tried a few workaround for this, but didnt help.
I think i need to learn how to do a full nandroid copy. But i just hoped it was possible to just copy the one file i need, and not everything.
...if its just data partition then this won't help. The only ways I know how to do a nandroid is with a custom recovery (you don't have)
Adb http://forum.xda-developers.com/showthread.php?t=1021625
But as you can see requires root
Some apps - you have no os
Utilities like android commander or droid explorer -_ need root
So this leaves dd commands, but maybe keep digging for stock website or getting someone to translate that screen for you (may be what you're after)
Best of luck!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
CelticWebSolutions said:
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
Click to expand...
Click to collapse
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes
mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify ro
Thank you!
hwong96 said:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes .....
Click to expand...
Click to collapse
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Jack_Rover said:
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Click to expand...
Click to collapse
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. Anyway, since you have asked I'll answer. The mount point for /system is different on each phone model. There is no one standard /system mount point. On the Nook Tablet and Nook Color it is mmcblk0p8. On your device it is different, so the command you tried will not work.
You need to find out what the /system mount point is for your phone.
Open terminal from phone and type su.
Press enter.
At the # prompt type cat /proc/mtd
Press enter.
Look at the output on the screen and see what the mount point is for /system.
A the the # prompt type mount -o rw,remount -t ext4 /dev/block/enteryoursystemmountpointhere /system
Note: replace enteryourmountpointhere with your mount point from the previous step.
Change /system to ro when done. Hope this works for you.
Also download root checker app to ensure you rooted properly.
hwong96 said:
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. ......
Click to expand...
Click to collapse
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Jack_Rover said:
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Click to expand...
Click to collapse
Did you use the root checker app to verify for proper root?
hwong96 said:
Did you use the root checker app to verify for proper root?
Click to expand...
Click to collapse
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Jack_Rover said:
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Click to expand...
Click to collapse
Don't know what else to suggest, except maybe contact Chainfire on G+.
.
Hi all,
I'm after a system.img that's going to allow me to run adb shell sessions as root. That's all I need. I don't need any of the normal phone fuctions or devices. I'd imagine disabling these would overcome any incompatibility issues... but I don't know.
Naturally, it'd be easier if such an image already existed, but I should be able to follow instructions on how to reconfigure a normal system and pack it to yaffs2 image.
How about the ramdisk of most custom recoveries- or is that too spare? It will give you a kernel, adb, and busybox if you are lucky.
sent from my android tablet
gee one said:
How about the ramdisk of most custom recoveries- or is that too spare? It will give you a kernel, adb, and busybox if you are lucky.
Click to expand...
Click to collapse
As long as I can do an adb shell as root then it's good enough.
I haven't found any compatible custom recovery images that I can flash. Everything I read seems to endup point to clockworkmod and I can't find flashable images for that. It seems to be flashed through rom manager only. I'm probably wrong though.
Depending on your device, there are several ways to flash. These may or may not apply to you:
1) some recovery installer app that you can download, similar to rom manager, or even rom manager itself!
2) a zip file that you make or modify yourself
3) flash through the staging partition, which may or may not be available on your device
4) copy directly into a recovery partition
5) who knows?
What device are you using and what rom and recovery are you using?
Sorry, I should have given you some info about my situation.
My phone is a chinese mt6516 iClone: W008+. It's currently without a working system partition so I flash images via pc using Mediatek flash tool.
For a recovery, I'd need an image file to flash directly. For a system partition I could flash and image file or I can pack a dir structure into a yaffs2 image file for flashing.
That seems above my paygrade... when you say image file, do you mean a packed boot.img that starts with ANDROID!
sent from my cyanogen(mod) vision
gee one said:
That seems above my paygrade... when you say image file, do you mean a packed boot.img that starts with ANDROID!
Click to expand...
Click to collapse
Well, a boot.img would go on the boot partition for booting into android normally. A recovery.img would also start with ANDROID but would go on the ... er... recovery partition. A system image would be different starting something like:
Code:
03 00 00 00 01 00 00 00 ff ff
Ok, it looks like the system.img is yaffs.
I was asking about the boot partition because most recovery images are just boot.img's with the recovery binary in the ramdisk. I made a boot.img once from a recovery partition and flashed it, so I had two recoveries on the same device, and no system! I thought this might be something of what you are looking for. You won't have or need a system since everything will load from the boot.img.
sent from my cyanogen(mod) vision
Yes, anything that gives me a root shell via adb would be good. It's just a question of finding something appropriate to try...
Are there any roms or system images available for your device now? Or can you pull the boot.img from your current device.
sent from my cyanogen(mod) vision
I can't find anything 3rd party for it. But I do have a boot.img that I extracted.
Send me a link and I'll poke around. Do you have a way to flash the boot.img?
sent from my cyanogen(mod) vision
Nice one.
This was ripped with dump_image:
boot.zip
OK, I extracted the ram disk- it was in an odd format. They sure talk funny.
ramdisk_2bb4ad9697.tar
So all the inits are for a fully working system, which you don't have. I guess the next step would be to strip out the inits to just a few basic mount points and then have it start adb. After that, add busybox and whatever goodies, repack it, and then flash away.
I really don't know my way around the init files, so it's mostly hack and slash. If you have any insight on how to strip them down, let's hear it. I'll try to read up on how linux boots. Also, knowing the partition mounts would be helpful, although I suppose you could figure that out with adb, if this actually works.
Cheers for that. Looks quite intriguing... I'm going to need a good deal more reading to make use of it though.
OK, here is a first stab- I modified the default.prop and added busybox and su. I did not touch any of the init's.
Here is the default.prop- insecure and adb enabled. I didn't change the inits, but it does look like they will start adb. They will probably fail to start everything else that it expects to find in system and frameworks, so your syslog will probably be littered with error messages, if there is even a syslog.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
Here is the ramdisk. I added busybox and su. I'm not sure if these will be helpful, but I figured it couldn't hurt.
edit: I just realized that /xbin is not in the path. "export PATH $PATH:/xbin" should fix it?? "/xbin/busybox --install /system/xbin" should install busybox to /system/xbin.
Code:
total 212
-rw-r--r-- 1 root root 20175 2012-03-08 18:26 advanced_meta_init.rc
drwxrwx--x 2 root root 4096 2012-03-08 18:26 data
-rw-r--r-- 1 root root 118 2012-03-08 20:11 default.prop
drwxr-xr-x 2 root root 4096 2012-03-08 18:26 dev
-rwxr-x--- 1 root root 107436 2012-03-08 18:26 init
-rwxr-x--- 1 root root 5828 2012-03-08 18:26 init.factory.rc
-rwxr-x--- 1 root root 1677 2012-03-08 18:26 init.goldfish.rc
-rwxr-x--- 1 root root 2263 2012-03-08 18:26 init.mt6516.rc
-rwxr-x--- 1 root root 20514 2012-03-08 18:26 init.rc
-rw-r--r-- 1 root root 5529 2012-03-08 18:26 meta_init.rc
drwxr-xr-x 2 root root 4096 2012-03-08 18:26 proc
lrwxrwxrwx 1 root root 11 2012-03-08 18:34 res -> /system/res
drwxr-x--- 2 root root 4096 2012-03-08 20:16 sbin
drwxr-xr-x 2 root root 4096 2012-03-08 18:26 sys
drwxr-xr-x 2 root root 4096 2012-03-08 18:26 system
drwxr-xr-x 2 root root 4096 2012-03-08 18:06 temp
drwxr-xr-x 2 root root 4096 2012-03-08 20:16 xbin
./data:
total 0
./dev:
total 0
./proc:
total 0
./sbin:
total 368
-rwxr-x--- 1 root root 138372 2012-03-08 18:26 adbd
-rwxr-x--- 1 root root 107436 2012-03-08 18:26 advanced_meta_init
-rwxr-x--- 1 root root 103116 2012-03-08 18:26 meta_init
-rwxr-x--- 1 root root 18012 2012-03-08 18:26 meta_tst
./sys:
total 0
./system:
total 0
./temp:
total 0
./xbin:
total 828
-rwxrwxr-x 1 root root 821340 2012-03-08 20:14 busybox
-rwsr-sr-x 1 root root 22364 2012-03-08 20:15 su
I did not change the kernel at all. The kernel and ramdisk have a 512 byte header file- it seems to have a file marker, size of package, and type of partition encoded into it. I'm not even sure this is android? I am certainly NOT an expert at this. For the record, I know nothing about the device that you have. I didn't even google it to see if was indeed an android phone.
All that being said, I will be surprised if this works and I would not be surprised if you end up with a brick. If it were my device, I would only flash this if I had a 100% bulletproof way to flash the stock boot.img externally without relying on the software on the phone. There is no system or frameworks, so it will most likely look like a stuck boot, but adb should be enabled. There is no boot animation or friendly little green android to greet you. I don't know if more stuff is needed in bin or sbin?
Now the disclaimers-
Code:
[SIZE="5"][COLOR="Red"][B]ALL WARRANTIES REGARDING
MERCHANTABILITY AND FITNESS OF PURPOSE,
EXPRESSED OR IMPLIED, ARE DISCLAIMED.
Flashing this boot image can cause
loss of data, loss of device, inability to use device,
spontaneous bricking, and other grave consequences.
Use at your own peril.
If anything bad happens, it's not my fault.[/COLOR][/B]
[/SIZE]
.
Good Luck! If in doubt, don't flash it!
https://rapidshare.com/files/1856533633/boot_adb_4026ab44b0.img
Well, I can't say I understand what you've done here but...
I've now got a working phone with root adb. Brilliant!!! Thanks.
I had to flash another system image (meant for a different phone) so that I could get a shell working otherwise I'd get a 'can't find /system/bin/sh' error. But having done that, it works a treat. The system still needs a bit of work to get my phone as it should be but that's another story.
I'm really interested in how you've managed to do this. How do you unpack/repack the boot.img? I'd love to mess about with this and see how long it takes to blow my phone up. I tried to follow one guide on the net but it just wasn't happening.
Ok, I found the ROOTFS section and pulled it out. So I can see how it all fits together.
According to 7zip, this is a 'Cpio' archive inside a 'Gzip' archive. What's 'Cpio'?
That's the funny part- there is a 512 byte header that has a few id characters, the file size and then "ROOTFS". The kernel image is similar. All the android parts that I've pulled apart didn't have the 512 byte header.
If you strip that out, then you will have a gzipped cpio archive. You can extract it with "gunzip -c <the ramdisk> | cpio -i"
To recompress it, "find . | cpio -o -H newc | gzip >> ../your-new-ramdisk"
You'll have to reattach the 512 byte header and adjust the file size.
sent from my cyanogen(mod) vision
Well I got round to having a little play with this. Thanks for the info Gee, it's been filed safely.
I looked at the recovery image and the init.rc doesn't do alot; Ideal starting place. Nothing is mounted by default so I put a couple of commands to mount /sdcard and /system normally just to test it. I also had to enable adb in the default.prop file as you did before. This was pretty straight forward and worked. I got into adb shell with root, no problem.
Now I thought it would be ideal if I could mount the sdcard as /system and put '/bin/sh' on the sdcard. Androids sh isn't a link like it is on Linux so I thought this should work. It didn't! On issuing the 'adb shell' command, I got:
Code:
link_image[2030]: failed to link /system/bin/sh
CANNOT LINK EXECUTABLE
So I thought I'd try the cache partition. I copied /bin/* to /cache, put the mount commands for /sdcard and cache as /system and this time... I got the same error. I'm surprised the cache partition didn't work. I was able to 'adb pull' the /system/bin/ files from it so I don't know why adb couldn't just execute one of them???
I don't know what to try next as I don't want to be forced to have the system partition mounted just for the sake of adb finding sh. I wouldn't mind if I could just umount it once I'm in the shell... but that would be to easy, wouldn't it.
I used http://forum.xda-developers.com/showthread.php?t=1136261 to unlock and root my atrix. would like help to unroot it.
Thanks
What you say is to unlock the bootloader and did you root for and want to remove the cel cel the root?
If this is so you must flash the SBF for your version of GB and your phone if AT&T
I believe there is a script called "SuperOneClick" that allows you to unroot it.
The rooting method listed in your link is the preinstall method. To unroot the preinstall method:
from here
1. Open adb
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
Click to expand...
Click to collapse
I unrooted my phone using the above steps back when I did the update to OTA 141. I don't think the superoneclick unroot works for the preinstall root.
I also found and tried that method but for some reason when i type the 2nd line it says mount: mounting /dev/block/mncblk0p17 on /preinstall failed: No such file or directory
PS. I'm not using AT&T
2147483647 said:
I also found and tried that method but for some reason when i type the 2nd line it says mount: mounting /dev/block/mncblk0p17 on /preinstall failed: No such file or directory
PS. I'm not using AT&T
Click to expand...
Click to collapse
are you copy/pasting into adb? It's mmcblk0p17 not mncblk0p17
gnahc79 said:
are you copy/pasting into adb? It's mmcblk0p17 not mncblk0p17
Click to expand...
Click to collapse
i dont copy and paste. But correcting the n to m did nt help
Any help?
2147483647 said:
Any help?
Click to expand...
Click to collapse
you should have both directories, try root explorer or some file manager to make sure you have the following directories:
/dev/block/mmcblk0p17
/preinstall
IMO copy/paste those commands to avoid typos.
gnahc79 said:
you should have both directories, try root explorer or some file manager to make sure you have the following directories:
/dev/block/mmcblk0p17
/preinstall
IMO copy/paste those commands to avoid typos.
Click to expand...
Click to collapse
/preinstall
diectory nt in my root explorer.
2147483647 said:
/preinstall
diectory nt in my root explorer.
Click to expand...
Click to collapse
You should have that directory, it could be you manually removed the entire preinstall directory at some point. I'm not sure what impact that has if for future OTA updates (might soft brick).
in adb issue the following command and you should be unrooted.
rm /system/bin/su
then uninstall the superuser app.
I just installed a new rom formatting my phone, including the internal memory. It is normal to have a hidden folder called System Data? And this increase and decrease weight by installing or uninstalling apps??
I just see this with a playstore app called DiskUsage, because in Windows Explorer don't show this folder...this is very Annoying because Each time I have less storage space for each installed application ... is a bug in my phone only?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9300 using xda app-developers app
Factory reset and remove all apps .
Install no apps ever again and you have plenty of space .
jje
Hello,
This is pretty normal.
The internal storage is not only the "storage" you can see in windows explorer when you connect your phone, but also of the following:
Code:
ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx root root 2013-04-09 16:26 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-04-09 16:26 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-04-09 16:26 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-04-09 16:26 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-04-09 16:26 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-04-09 16:26 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-04-09 16:26 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-04-09 16:26 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-04-09 16:26 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-04-09 16:26 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-04-09 16:26 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-04-09 16:26 USERDATA -> /dev/block/mmcblk0p12
That means, that all of them are filling the internal storage.
And according to mount:
Code:
....
/dev/block/mmcblk0p12 /data ext4 ...
....
Every single App and Cache are located there, too.
JJEgan said:
Factory reset and remove all apps .
Install no apps ever again and you have plenty of space .
jje
Click to expand...
Click to collapse
That means it's normal? So always turn to fill that space to install applications?
Sent from my GT-I9300 using xda app-developers app
whitepaw said:
Hello,
This is pretty normal.
The internal storage is not only the "storage" you can see in windows explorer when you connect your phone, but also of the following:
Code:
ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx root root 2013-04-09 16:26 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-04-09 16:26 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-04-09 16:26 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-04-09 16:26 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-04-09 16:26 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-04-09 16:26 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-04-09 16:26 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-04-09 16:26 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-04-09 16:26 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-04-09 16:26 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-04-09 16:26 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-04-09 16:26 USERDATA -> /dev/block/mmcblk0p12
That means, that all of them are filling the internal storage.
And according to mount:
Code:
....
/dev/block/mmcblk0p12 /data ext4 ...
....
Every single App and Cache are located there, too.
Click to expand...
Click to collapse
So is normal xD thanks for your explain, There are ways to reduce the weight of that folder or partition? I have at most 20 applications installed and I think it exaggerated the size of this.
Sent from my GT-I9300 using xda app-developers app
someone can answer me please?
I'm not sure what exactly "System Data" is collecting.
On my phone System Data is 3GB (might be some zombie files in there which aren't used anymore).
It definitly is caused by apps you install.
The "System Data" part is not one explicit folder as far as I understand, but the collection of multiple folders.
Have you installed an android 4.2 ROM?
If yes:
I had a problem where my storage was nearly filled completly and I was not able to find where the data is.
I noticed, that after installing the 4.2 Leak, the MTP Mountpoint was moved to another folder inside the "normal" storage partition cause of the "emulated" multiuser support. (I don't have my phone connected right now, so the foldersmight be wrong) As far as I remember, the original /storage/sdcard was moved to /mnt/shell/legacy (which contained my previous sdcard files and a folder called "0") and the new /storage/emulated/legacy and /storage/emulated/0 (first and only user for mobilephone android 4.2) where linked to that folder "0".
That means the rest of the files in /mnt/shell/legacy where "hidden" and I was not able to find them via windows explorer and some android storage tools. After I moved the files from /mnt/shell/legacy to /mnt/shell/legacy/0/old via adb, I was able to detect them correctly and remove unwanted files for cleanup. However I'm not quiet sure if that folder counts, cause it is not part of /data.I tend to say, that it does not count.
If <4.2 or if the above is not the case:
I think 1GB isn't much. I might be wrong and maybe it's a good idea that someone else can share the "System Data" size of their diskusage result. I myself might not be digging deep enough into android filesystem management, but it depends on what "System Data" is showing. if it's really showing every little system data, then it contains the apps, the configurations, the databases, the recovery, the rom (which alone is around 500MB), the sounds, the wallpapers...etc.
I think it also depends on the device what data is shown here, you can't compare the result of your device with for example a HTC Device cause it might have a complete difference partition and mount table.
The best idea might be to connect the phone to the Computer, start an adb shell and get root (I hope your phone is rooted) by typing:
Code:
su
You might need to allow that on the phones screen.
Now type:
Code:
df -h
This will tell you which mountpoint takes how much space.
Example of another device:
/dev/block/mmcblk0p12 3.0G 958.2M 2.1G 31% /data
I'm not sure about the output on android, but it should show the mountpoint (a folder without /dev)
If you can only see something with "/dev" it's not the mountpoint but the device itself. You can find the according mountpoint by typing "mount".
Maybe you can find your 1GB here.
Change into each directory you want to check (type: "cd /data" for example) for the size and execute:
Code:
du -sh *
and you will get a list of each folder and file in there including it's size (not only the folder size (which will be displayed with "ls -la" to 4KB (cause the folder itself isn't big), but also the files within that folder).
Now go on and dig deeper and deeper until you find the big files.
That's the best way in my opinion to "hunt" down big files.
If that does not help you, then maybe you can post the result of "df -h" and "mount" here.
whitepaw said:
I'm not sure what exactly "System Data" is collecting.
On my phone System Data is 3GB (might be some zombie files in there which aren't used anymore).
It definitly is caused by apps you install.
The "System Data" part is not one explicit folder as far as I understand, but the collection of multiple folders.
Have you installed an android 4.2 ROM?
If yes:
I had a problem where my storage was nearly filled completly and I was not able to find where the data is.
I noticed, that after installing the 4.2 Leak, the MTP Mountpoint was moved to another folder inside the "normal" storage partition cause of the "emulated" multiuser support. (I don't have my phone connected right now, so the foldersmight be wrong) As far as I remember, the original /storage/sdcard was moved to /mnt/shell/legacy (which contained my previous sdcard files and a folder called "0") and the new /storage/emulated/legacy and /storage/emulated/0 (first and only user for mobilephone android 4.2) where linked to that folder "0".
That means the rest of the files in /mnt/shell/legacy where "hidden" and I was not able to find them via windows explorer and some android storage tools. After I moved the files from /mnt/shell/legacy to /mnt/shell/legacy/0/old via adb, I was able to detect them correctly and remove unwanted files for cleanup. However I'm not quiet sure if that folder counts, cause it is not part of /data.I tend to say, that it does not count.
If <4.2 or if the above is not the case:
I think 1GB isn't much. I might be wrong and maybe it's a good idea that someone else can share the "System Data" size of their diskusage result. I myself might not be digging deep enough into android filesystem management, but it depends on what "System Data" is showing. if it's really showing every little system data, then it contains the apps, the configurations, the databases, the recovery, the rom (which alone is around 500MB), the sounds, the wallpapers...etc.
I think it also depends on the device what data is shown here, you can't compare the result of your device with for example a HTC Device cause it might have a complete difference partition and mount table.
The best idea might be to connect the phone to the Computer, start an adb shell and get root (I hope your phone is rooted) by typing:
Code:
su
You might need to allow that on the phones screen.
Now type:
Code:
df -h
This will tell you which mountpoint takes how much space.
Example of another device:
/dev/block/mmcblk0p12 3.0G 958.2M 2.1G 31% /data
I'm not sure about the output on android, but it should show the mountpoint (a folder without /dev)
If you can only see something with "/dev" it's not the mountpoint but the device itself. You can find the according mountpoint by typing "mount".
Maybe you can find your 1GB here.
Change into each directory you want to check (type: "cd /data" for example) for the size and execute:
Code:
du -sh *
and you will get a list of each folder and file in there including it's size (not only the folder size (which will be displayed with "ls -la" to 4KB (cause the folder itself isn't big), but also the files within that folder).
Now go on and dig deeper and deeper until you find the big files.
That's the best way in my opinion to "hunt" down big files.
If that does not help you, then maybe you can post the result of "df -h" and "mount" here.
Click to expand...
Click to collapse
You are the best! simply the best!! thanks for your support!, i install a new rom (Based on android 4.1), making a'' full'' factory wipe, the system data folder space was reduced to approximately 500MB, here I leave the command catches you explained, (i never update my phone to android 4.2)
Then, you also have this folder or partition? (as comets, would be nice if someone could pass a screenshot of System Data folder space with DiskUsage)
Never touched it, a hundred apps installed. Using _null Rom.
Striatum_bdr said:
Never touched it, a hundred apps installed. Using _null Rom.
Click to expand...
Click to collapse
Thanks! but, the directory is different, in the application DiskUsage, if I use the first option at first (sd card space) the size of the System Data folder is very small, but if you use the path /storage/sdcard0 (with root) is where this System Data folder that greatly increases its size...
could you post a screenshot of your / storage/sdcard0 please?
Any? Please, upload a screenshot of your phone in DiskUsage ^^/
Sent from my GT-I9300 using xda app-developers app
Do not bump a thread before 24 hours has passed. Next time I will report you.
Why does this even matter? There are hidden partitions. Oh well. Use your phone and move on with life.
b-eock said:
Do not bump a thread before 24 hours has passed. Next time I will report you.
Why does this even matter? There are hidden partitions. Oh well. Use your phone and move on with life.
Click to expand...
Click to collapse
24hs after, bump... any?
Bumps mean that no one is interested.
Actually you're right, but you're wrong.
Size is not the same (much bigger in the second case) but you're wrong (the folder didn't increase, as the free disk space is the same).
It just means you're not seeing the same thing. And you can't do anything for that, as it's part of jelly bean filesystem design.
You can try to play a little with terminal emulator to understand why.
I would like to bring this back up. All my pictures, Titanium Backups, etc are on this internal card, but I cannot find them. I flashed a ROM and did a factory reset, but for some reason it only backed up some old files in the 0 folder in my internal storage. That folder was actually one level down from the root-below the card's default storage spot, so not sure how it happened. When the OS loaded up and I saw everything was gone, I had a tiny heart attack. Couldn't find it with Solid Explorer, but saw that there was only 3GB of space left on the internal card, and this was a clean flash with literally no apps installed or data on the internal storage card. I knew my data must be somewhere on it! I installed Disk Usage and sure enough, there was a huge amount of data in a System folder. Can anyone help figure out how to access this data? I know the stuff is there, just not sure how to get to it.
Read the sdcard on 4.2 link in my signature
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Read the sdcard on 4.2 link in my signature
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I'm sorry, but I don't see how this applies for me? I don't have the 0 folder now, there's nothing in the data/media folder, & all my data is in some hidden System folder, where I cannot access it via file manager. It's like some blocked off partition. Do you have some way I can find/get into that data?
you need to read it once again. your data is in /data/media
Glebun said:
you need to read it once again. your data is in /data/media
Click to expand...
Click to collapse
You are right...I had accidentally denied Solid Explorer root privileges earlier, and didn't realize it wasn't going into the root folder, I am in there now, thank you so much!
Quick question, once I get my stuff out of there, can I delete that folder without causing any system harm?
tlogank said:
You are right...I had accidentally denied Solid Explorer root privileges earlier, and didn't realize it wasn't going into the root folder, I am in there now, thank you so much!
Quick question, once I get my stuff out of there, can I delete that folder without causing any system harm?
Click to expand...
Click to collapse
no, you can't. your internal SD right now is /data/media/0, so deleting /data/media will delete the sdcard. you can remove the contents, but don't touch the 0 folder
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