Requesting update.zip for Tianshi-Digiland DL701Q Tablet, Several threads on this forum and several people have the update.zip but as of yet no one is willing to share it.
Most people have no ideal what the update.zip is, it's a patch that updates one's tablet, but the real use of the update.zip is it includes all the files needed to make a stock rom that is flashable via custom recovery.
My version is beyond the updates, I have the latest version, which is even newer than the update.zip
so I can't download the update.zip if I could, I wouldn't ask for it. Several people have requested or are looking for an stock rom, none is available they have to be made from installed system.
But to install stock rom requires the files from the update.zip it contains the correct permissions, update-binary and updater-script.
vampirefo said:
Requesting update.zip for Tianshi-Digiland DL701Q Tablet, Several threads on this forum and several people have the update.zip but as of yet no one is willing to share it.
Most people have no ideal what the update.zip is, it's a patch that updates one's tablet, but the real use of the update.zip is it includes all the files needed to make a stock rom that is flashable via custom recovery.
My version is beyond the updates, I have the latest version, which is even newer than the update.zip
so I can't download the update.zip if I could, I wouldn't ask for it. Several people have requested or are looking for an stock rom, none is available they have to be made from installed system.
But to install stock rom requires the files from the update.zip it contains the correct permissions, update-binary and updater-script.
Click to expand...
Click to collapse
update.zip
Sorry for the delay on this, I haven't been on for awhile, should contain what you need. Posted it in reply to your original request in the guide as well.
Thanks,
Proto
Protocol 9 said:
update.zip
Sorry for the delay on this, I haven't been on for awhile, should contain what you need. Posted it in reply to your original request in the guide as well.
Thanks,
Proto
Click to expand...
Click to collapse
Been busy, compiling recovery, and converting system and cache to EXT4, also setting up dual boot, I left data as UBIFS, Thanks for uploading the update.zip, will look at update.zip as soon as I am done fixing tablet to suit me.
Code:
[email protected]:~/Desktop$ adb remount
remount succeeded
[email protected]:~/Desktop$ adb shell
[email protected]:/ # busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 237.1M 128.0K 237.0M 0% /dev
none 237.1M 0 237.1M 0% /sys/fs/cgroup
tmpfs 237.1M 0 237.1M 0% /mnt/secure
tmpfs 237.1M 0 237.1M 0% /mnt/asec
tmpfs 237.1M 0 237.1M 0% /mnt/obb
tmpfs 237.1M 0 237.1M 0% /storage/emulated
/dev/block/mtdblock16
1007.9M 753.0M 254.9M 75% /system
/dev/ubi0_0 5.2G 703.8M 4.5G 13% /data
/dev/block/mtdblock17
126.0M 4.6M 121.4M 4% /cache
/dev/block/loop0 1.2M 1.2M 0 100% /mnt/cd-rom
/dev/fuse 5.1G 703.8M 4.4G 13% /mnt/shell/emulated
/dev/block/vold/179:1
9.8G 6.4G 3.4G 66% /mnt/media_rw/sdcard1
/dev/fuse 9.8G 6.4G 3.4G 66% /storage/sdcard1
[email protected]:/ #
I built a stock rom using the update.zip, haven't been able to test it yet, my current system is EXT4. I do see several differences between your tablet and mine, based off the build.prop.
Sent from my Venue 8 3830 using Tapatalk
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