Database Info

[HOW-TO] Stock Apps for All!

After two days of fumbling around with adb, numerous nandroid backups, and ultimately wiping my system, I, with the help of my friend Kiraly (his xda username), have successfully installed the stock Messaging, Clock, Calculator and Browser apps onto my phone.
The Messaging app was of particular interest to me because I hate how the HTC Sense Messaging app always loads briefly when you enter a thread of messages, no matter how many messages are in the actual thread. Also, the stock Android Messaging app has a feature similar to BBM in that an icon within the thread notifies you when a message has actually sent.
By following the instructions contained hereunder, you agree to indemnify and hold harmless the original poster (the "OP"). I hereby disclaim all warranties and liability for any harm that may result by following the aforementioned instructions.
Installing these apps was fairly easy once we found out how it needed to be done. You will need the following:
A. Minimal knowledge of adb, or rather knowledge of how to copy and paste adb commands.
B. You will need full root (root and nand unlocked)
C. 1.47 kernel with the modified default.prop file http://forum.xda-developers.com/showthread.php?p=7138666
D. The Root Explorer app (this can be purchased in the Android Market)
E. You will need the following .apk files from BuglessBeast. They are the only apps that I have been able to successfully install. http://forum.xda-developers.com/showthread.php?t=700175
-Mms.apk
-Browser.apk
-DeskClock.apk
-Calculator.apk
STEP 1
Perform a nandroid backup.
STEP 2
Plug your phone into your computer via USB and mount the sd card.
STEP 3
Download the 1.47 kernel with the modified default.prop file. The stock kernel is also contained in the following link, and you can always revert back to it if need be. http://forum.xda-developers.com/showthread.php?p=7138666
STEP 4
Flash the modified 1.47 kernel .zip file to the root of your sd card (for all you rookies out there, simply drag the .zip file onto your sd card).
STEP 5
Reboot into recovery and install the kernel you just flashed. Then, reboot the phone.
STEP 6
Download the BuglessBeast ROM http://forum.xda-developers.com/showthread.php?t=700175
STEP 7
Unzip the BuglessBeast file. Open the unzipped file. Find the folder labeled "System", and open it. Then, find the folder labeled "App", and open it. Find the files labeled Mms.apk, Browser.apk, DeskClock.apk and Calculator.apk. Drag those files to your desktop.
STEP 8
Download and open the Root Explorer app. Scroll down to the bottom and click on the folder labeled "System." Then, at the top of the app, click "Mount R/W." After you click that, open the "app" folder. Each application has two files you need to delete. Do not delete any of the clock files. You will need to delete the following files and then quit the application when you have finished:
-Browser.apk
-Browser.odex
-Mms.apk
-Mms.odex
-Calculator.apk
-Calculator.odex
STEP 9
Open the Command Prompt if you are a Windows user or the Terminal application if you are a Mac user and navigate to the tools folder of the Android SDK. Do not boot into recovery.
STEP 10
Type the following commands in order. We will use the Browser.apk as an example, and I will assume the file is on your desktop:
Code:
adb shell
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Code:
exit
Code:
adb push C:\Users\YourUserName\Browser.apk /system/app
Code:
adb shell
Code:
chmod 6755 /system/app/Browser.apk
Code:
exit
Code:
adb reboot
STEP 11
Rinse and repeat!
Thanks to frankenstein\ for the kenel, laydros for getting me started in the right direction, BuglessPete for the .apk files, and most importantly to Kiraly for all his assistance.
{
"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"
}

<3
10 char

I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.

kpoz said:
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
Click to expand...
Click to collapse
I'm using Ubuntu but I have a Windows lappy around with adb setup, I'll test it out and let you know.

neckface said:
I'm using Ubuntu but I have a Windows lappy around with adb setup, I'll test it out and let you know.
Click to expand...
Click to collapse
Great, thanks. I almost forgot to delete the "./" before "adb" when I was writing the tutorial. For whatever reason, on a Mac the command is ./adb, and on Windows it is simply adb.

kpoz said:
Great, thanks. I almost forgot to delete the "./" before "adb" when I was writing the tutorial. For whatever reason, on a Mac the command is ./adb, and on Windows it is simply adb.
Click to expand...
Click to collapse
Yup, same with Linux.

Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.

kpoz said:
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
Click to expand...
Click to collapse
Push command is correct for windows. It may vary slightly depending on where you placed the apk files.

tehpsyc said:
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
Click to expand...
Click to collapse
Glad it worked for you! Thanks for attaching the Mms.apk.
I'm glad that slow, unresponsive Sense Messages app is long gone. You know there is something wrong with your app (*cough, HTC, *cough) when you get a "Loading" message when opening a thread, regardless of how many messages are in said thread.

initial said:
Push command is correct for windows. It may vary slightly depending on where you placed the apk files.
Click to expand...
Click to collapse
Thanks for confirming.

tehpsyc said:
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
Click to expand...
Click to collapse
What is the sense messenger app called? I can't find anything resembling it.
Here's a list of my HTC programs.
Code:
# ls /system/app/*htc*
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.NewsReaderWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/htcbookmarkwidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/htcsearchwidgets.apk
/system/app/htcsettingwidgets.apk
I see the htc messenger widget but do I have to get rid of that? I don't think that's the messenger application file.

initial said:
What is the sense messenger app called? I can't find anything resembling it.
Here's a list of my HTC programs.
Code:
# ls /system/app/*htc*
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.NewsReaderWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/htcbookmarkwidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/htcsearchwidgets.apk
/system/app/htcsettingwidgets.apk
I see the htc messenger widget but do I have to get rid of that? I don't think that's the messenger application file.
Click to expand...
Click to collapse
The Sense Messenger app is called Mms.apk. Delete the Mms.apk and Mms.odex files. It's in the OP
Do not delete htcmessengeruploader.

kpoz said:
The Sense Messenger app is called Mms.apk. Delete the Mms.apk and Mms.odex files. It's in the OP
Do not delete htcmessengeruploader.
Click to expand...
Click to collapse
Oh didn't realize it was the same. I'm using DamageControl's ROM and assumed HTC had a different label for some reason. Thanks for clearing that up.
In any case, I got a few FCs here and there and MMS is failing to send on the DC ROM. I'll tinker with it some more and see if I can figure something out.
btw, if anyone is doing this on DC's ROMs then don't bother looking for any *.odex files since his rom is de'odexed.

initial said:
Oh didn't realize it was the same. I'm using DamageControl's ROM and assumed HTC had a different label for some reason. Thanks for clearing that up.
In any case, I got a few FCs here and there and MMS is failing to send on the DC ROM. I'll tinker with it some more and see if I can figure something out.
btw, if anyone is doing this on DC's ROMs then don't bother looking for any *.odex files since his rom is de'odexed.
Click to expand...
Click to collapse
Originally, Kiraly and I tried pushing these files and then using a shell to install them, but it resulting in a ton of force closes. We couldn't open any of the apps.
Regrettably, I'm not savvy enough to attempt to fix this issue for you if you are running a ROM like DC, especially a deodexed ROM. Best of luck to you.
Maybe the install command will work for you where it failed for me.
Try the following:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
exit
adb push :\Users\YourUserName\Browser.apk /sdcard
adb shell
install /sdcard/Browser.apk /system/app
exit
adb reboot

Droid 2 Deodex and Zip Aligned System & Framework Files

This is the stock Droid2 System and Framework files deodexed and zip aligned. This first of two packages that contains my Black (HTC) Status Bar Theme that looks like this. The next package will be the stock Droid2 deodexed and zip aliagned with stock status bar.
{
"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"
}
( Picture from my Droid2 Theme for Droid 1. Status bar is exactly the same. Too lazy to update pic )​
It contains all original Droid2 files so if you have renamed or removed files it will replace them. This includes all Droid2 widgets and bloatware. If you have removed or renamed files then you can rename or remove the files from the app folder you placed on your memory card so you do not have to go back after install to clean up.​
A couple of apk files have been modified so the status icon matches status bar better. I still need to fix up a few more apk files and will post them as an update.zip file.​
I will have a update.zip file soon so it can be installed with clockwork. If you would like to test it for me please message me to let me know.​
Root Privilege:
You must have Root Access to install the files.
Check this thread and this thread on how to root your phone.​
ADB:
You also need to have The Android SDK installed so you can use adb commands.​
Clockwork Recovery:
Download from Android Market or check here and make donation after you download.​
Download:
Droid2 Deodexed Black Status Bar Command Line Install​
Droid2 Deodexed Stock Status Bar Command Line Install​
Install Instructions - Recommended Method - Command Line:
Prep
Download the archive from above, extract file to your compter. Place app and framework folders from archive on the root of your sd card (/sdcard/app /sdcard/framework).​
Make sure your phone is plugged into the USB cable and PC Mode is selected and that you have debugging enalbed on the phone application settings.​
Open DOS prompt and type the following commands or paste them at the DOS prompt.
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot​
Install Instructions - Clockwork:
Coming Soon!​
After reboot it will take a few minutes too boot up so be patient. Your phone has not hung on boot unless the droid eye stops moving.​
Launcherpro:
Download themed LauncherPro 0.7.9.0 here.
Extract the com.fede.launcher.apk file and place on root of SD Card.
Make sure your phone is in PC Mode and Debugging is enalbed in Applications settings on phone.
Open command prompt on pc and type following commands.
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/com.fede.launcher.apk /system/app/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot​

Looking forward to the clockwork package. This is the mod I've been waiting for.

wsfanatic said:
Looking forward to the clockwork package. This is the mod I've been waiting for.
Click to expand...
Click to collapse
Go with the command line for now. Having adb will be better in the long run and have to figure out how to write a script for update.zip to delete all the odex files when installing from clockwork.

If I've already deodexed, would I still need the script to remove the *.odex files?

I think its worth noting that your phone needs to be in PC Mode when plugging it in, with debugging on. If your in mass storage, it won't work because adb won't be able to access the sdcard while its mounted on the computer. These commands should also work via Android Terminal, although I imagine it's easier copying and pasting with a mouse and keyboard.
I know this may be obvious to some, but when you have people not knowing what they're doing in the first place, they assume that certain instructions were omitted intentionally.

Natty_lite said:
I think its worth noting that your phone needs to be in PC Mode when plugging it in, with debugging on. If your in mass storage, it won't work because adb won't be able to access the sdcard while its mounted on the computer. These commands should also work via Android Terminal, although I imagine it's easier copying and pasting with a mouse and keyboard.
I know this may be obvious to some, but when you have people not knowing what they're doing in the first place, they assume that certain instructions were omitted intentionally.
Click to expand...
Click to collapse
Thanks! It's there under the install instructions.

Natty_lite said:
These commands should also work via Android Terminal, although I imagine it's easier copying and pasting with a mouse and keyboard.
.
Click to expand...
Click to collapse
It isn't a good idea to try installing system files from the phone especially in terminal when there is a "stop" command because this will hault the GUI and the system so you'd be stuck.
Please stick to ADB for this at least. A strong suggestion.

newk8600 said:
It isn't a good idea to try installing system files from the phone especially in terminal when there is a "stop" command because this will hault the GUI and the system so you'd be stuck.
Please stick to ADB for this at least. A strong suggestion.
Click to expand...
Click to collapse
I was just going to suggest that too...
-----------
LauncherPro has been updated to 0.7.9.0 Check bottom of first post for download link and install instructions.

MotoBoy said:
I was just going to suggest that too...
Click to expand...
Click to collapse
LOL great minds think alike!

newk8600 said:
It isn't a good idea to try installing system files from the phone especially in terminal when there is a "stop" command because this will hault the GUI and the system so you'd be stuck.
Please stick to ADB for this at least. A strong suggestion.
Click to expand...
Click to collapse
You're right. I didn't think about that. I'll make sure I remember that for future reference. Thank God I used ADB
MotoBoy said:
Thanks! It's there under the install instructions.
Click to expand...
Click to collapse
No problem at all. Very clean work. I'm running the black status bar on my phone as we speak.

Natty_lite said:
You're right. I didn't think about that. I'll make sure I remember that for future reference. Thank God I used ADB
No problem at all. Very clean work. I'm running the black status bar on my phone as we speak.
Click to expand...
Click to collapse
Cool...so I take it that theme install went well.

MotoBoy said:
Cool...so I take it that theme install went well.
Click to expand...
Click to collapse
Yep, thanks to you. I had issues getting the Deodex tool to work properly on my W7 64 bit machine. This file made life easier.
Someone just upped a D1 theme in the Theme and Apps subforum. Shouldn't I be able to replace the .apks from your file with those? (I'm trying to get the stock Android icons back for browser, music, dialer, sms, and calendar)

Natty_lite said:
Yep, thanks to you. I had issues getting the Deodex tool to work properly on my W7 64 bit machine. This file made life easier.
Someone just upped a D1 theme in the Theme and Apps subforum. Shouldn't I be able to replace the .apks from your file with those? (I'm trying to get the stock Android icons back for browser, music, dialer, sms, and calendar)
Click to expand...
Click to collapse
That should work...

Would this work if I have already installed a custom rom? Or would it mess things up?
Thanks!
-John

What exactly is theme in the launcherpro? Sorry to have to ask but couldn't the image be provided for the app drawer from the screenshot? Thanks for the great work!

mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Questions:
1. Could you explain the Mount line?
2. When you "rm" the odex files what happens. I mean have you done something to the associated .apx files?
If not, does that mean I could just use these commands and remove my .odex files and I would be what is called deodex'ed?
3. What is the benefit of de oxed' ing?
I am keeping an text file with abd instructions for different categories and do not understand some of the commands like the mount line that is the same in most of the procedures.
I have been googleing around trying to find a tutorial or lesson plan for adb and keep bookmarks on sites I find. Most of the info on the net that I find, you can get by typing adb help. That is fine, except it does not really explain what the commands mean or do.
Understand you are busy man, so if you do not have time for this, I'll understand. I am retired and have nothing else to do. Ha!

This is probably more information than you wanted to know, but you seem to be interested in learning so...
chrstdvd said:
Questions:
1. Could you explain the Mount line?
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
Click to expand...
Click to collapse
This line mounts the /system partition in read-write instead of the default read-only. In linux, hardware has special device files that are housed in the /dev/ directory. These devices get "mounted" for use to a mount point which usually has a nice, human-readable name. In this case, "/system". The "-t ext3" part defines the file system type. Typical linux file systems are ext2 and ext3. Winblows file systems are things like FAT32 and NTFS.
So, the command spelled out is something like this: remount in read-write mode the block device at "/dev/block/mmcblk1p21" to the mount point "/system" using the file system type "ext3".
2. When you "rm" the odex files what happens. I mean have you done something to the associated .apx files?
Click to expand...
Click to collapse
Yes something has been done. Deodexing is a lengthy process that, in part, converts the .odex files back to .dex files and reincorporates that data back into the associated .apk file. This is necessary for theme creation and some other kinds of development. The .odex files tend to prevent modification of .apk's, which is required for things like themes. The default .apk's are also signed zip files with a signature to prevent against tampering. In other words, although you can rename an .apk to .zip and extract it, you can't decompress an .apk, modify its contents (change an image or icon, for example) and then recompress without some consequences. Deodexing removes the signature stuff, making it far easier for developers to get at the guts of the content within the .apks.
If not, does that mean I could just use these commands and remove my .odex files and I would be what is called deodex'ed?
Click to expand...
Click to collapse
No. Simply removing the .odex files without replacing the .apk's with modified (deodexed) versions would leave you with non-functioning applications. The .odex files contain code that has been removed from the .apk files by developers in an effort to compress data and speed up the initial boot process.
Basically, when you phone boots for the first time, a lot of information is being decompressed into the /data directory for easy, quick access. The .odex files help streamline this process. With their data reincorporated into the .apk's, booting takes longer, but the benefits, like themes and other fixes that probably won't ever be available to non-deodexed phones, usually far outweigh the drawbacks.
3. What is the benefit of de oxed' ing?
Click to expand...
Click to collapse
For now, the ability to install custom themes is the main benefit. However, community developers are often able to provide fixes to problems on deodexed phones that the official devs will not, like the HTC Hero's stock lock screen issues.
If you're interested in learning more about adb, you will probably want to swan dive into some linux documentation. Without a linux background, the adb stuff will seem pretty foreign. I'd include links to some sources, but I'm new here and that's been restricted.

Stephan_ said:
What exactly is theme in the launcherpro? Sorry to have to ask but couldn't the image be provided for the app drawer from the screenshot? Thanks for the great work!
Click to expand...
Click to collapse
All that is themed in launcher pro are the icons when you long home press the home screen. So Shortcuts, Widgets, Folders and Wallpapers are using the same icons as Blur Home. Also the people and phone icons have been replaced to match the blur icons when you are using the default icons.

goliathvt said:
This is probably more information than you wanted to know, but you seem to be interested in learning so...
This line mounts the /system partition in read-write instead of the default read-only. In linux, hardware has special device files that are housed in the /dev/ directory. These devices get "mounted" for use to a mount point which usually has a nice, human-readable name. In this case, "/system". The "-t ext3" part defines the file system type. Typical linux file systems are ext2 and ext3. Winblows file systems are things like FAT32 and NTFS.
So, the command spelled out is something like this: remount in read-write mode the block device at "/dev/block/mmcblk1p21" to the mount point "/system" using the file system type "ext3".
Yes something has been done. Deodexing is a lengthy process that, in part, converts the .odex files back to .dex files and reincorporates that data back into the associated .apk file. This is necessary for theme creation and some other kinds of development. The .odex files tend to prevent modification of .apk's, which is required for things like themes. The default .apk's are also signed zip files with a signature to prevent against tampering. In other words, although you can rename an .apk to .zip and extract it, you can't decompress an .apk, modify its contents (change an image or icon, for example) and then recompress without some consequences. Deodexing removes the signature stuff, making it far easier for developers to get at the guts of the content within the .apks.
No. Simply removing the .odex files without replacing the .apk's with modified (deodexed) versions would leave you with non-functioning applications. The .odex files contain code that has been removed from the .apk files by developers in an effort to compress data and speed up the initial boot process.
Basically, when you phone boots for the first time, a lot of information is being decompressed into the /data directory for easy, quick access. The .odex files help streamline this process. With their data reincorporated into the .apk's, booting takes longer, but the benefits, like themes and other fixes that probably won't ever be available to non-deodexed phones, usually far outweigh the drawbacks.
For now, the ability to install custom themes is the main benefit. However, community developers are often able to provide fixes to problems on deodexed phones that the official devs will not, like the HTC Hero's stock lock screen issues.
If you're interested in learning more about adb, you will probably want to swan dive into some linux documentation. Without a linux background, the adb stuff will seem pretty foreign. I'd include links to some sources, but I'm new here and that's been restricted.
Click to expand...
Click to collapse
He took the words right out of my mouth
Thanks!

Thank you so much for the info. Linux huh, guess I will dive right in. My background is Basic, FORTRAN, COBAL AND Visual Basic for Apps (Excel only). I quit trying to keep up with Visual Basic because Object Oriented Programming was really starting to irritate me. I was fairly good in DOS back in the day. These adb commands remind me of DOS, so hopefully I will catch on and understand.
At least in the olden days you got a manual to explain the commands with some examples.
Anyway, Thank you. I will start Googleinh Linux.
Found this site and I am in pig heaven. Thanks again, things are starting to make sense, from the "old days perspective".
http://www.linux-tutorial.info/

[Q] Nexus S voice/sound recorder hidden and not installed?

Hi,i was searching for the stock voice recorder in Ice Cream Sandwich,but i did not find it...
So I've searched into phone memory (root /system/app) and i found Soundrecorde.apk ,bu if i try to install it,installation aborts saying "This application cannot be installed".
Why?

No one use voice recording on Ics?
Neo on Nexus S with Tapatalk®

bump?.......

.:Crack:. said:
bump?.......
Click to expand...
Click to collapse
???
Neo on Nexus S with Tapatalk®

..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
There is not much compatibility for this kind of apps and Ics...
Stock Sound recorder was perfect for me on Gingerbread,i don't understand why it's not compatible anymore...
Neo on Nexus S with Tapatalk®

not sure how you tried to install but you cant install system apps like other apk you have to sign it first....anyways i signed it and installed fine but dont give an option to open after install and still don't see it
edit
just for future reference if you edit an apk or want to install a system app like a normal apk
download Sighnapktic from the market its free and it does it right from your phone really easy to use
https://market.android.com/details?id=com.stericson.signapktic&hl=en

i used Sanity with gingerbread, but I don't know if it still works with ICS
https://market.android.com/details?..._result#?t=W251bGwsMSwxLDEsImNyaS5zYW5pdHkiXQ..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.

XK72 said:
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.
Click to expand...
Click to collapse
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®

..

(THE REAL) Neo said:
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
{
"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"
}
Correct.
Election Day said:
Probably yes. I'm trying to modify the xml's at the moment, but I can't get any usable output.
If I can get it to work I'll post the modded apk here.
Click to expand...
Click to collapse
Directly after this line:
Code:
<action android:name="android.intent.action.MAIN" />
Add:
Code:
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />

..

You also just can use anycut from market and create a homescreen shortcut to soundrecorder.apk

Election Day said:
I guess this should be it. I unpacked the apk with apktool, added the lines, packed it again, unzipped it, added META-INF and rezipped it.
You can flash it with "adb push SoundRecorder.zip /system/app".
Click to expand...
Click to collapse
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®

(THE REAL) Neo said:
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®

jitzbox said:
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied
Click to expand...
Click to collapse
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
(THE REAL) Neo said:
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.

XK72 said:
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.
Click to expand...
Click to collapse
Using this apk,the phone shows me an app called "Recorder" in the app drawer,but i can't tap it,and all the icons showed in the same page of the app drawer.If i change page,icons of other pages are selectable...weird thing...
Now i'm rolled back to previous apk file and everything works...so scary...
Neo on Nexus S with Tapatalk®

[DIY-TUT/HOW-TO] Debloat and Save Battery

Note: This is not a ready made script that will do things for you. If you are looking for a script/tool to debloat your phone head here. This is a very basic guide, many of you might be aware how to do it already. This is for the absolute newbies like me who like learn by doing it themselves. So lets start!
First, What is Debloat? What are the benefits?
Ans: A new device (except the nexus family) always comes pre-loaded with a lot of manufacturer apps. Most of the times these apps are utterly useless to the end-user considering that there are better alternatives available on the play store. Such apps constitute the phone bloatware. Often these apps are part of the system partition on your phone ie they are system apps and cannot be uninstalled or removed like normal apps. The process of removing these apps is called as debloating!. Savvy?
Fine, Moving ahead. Whats more problematic about these apps is that many of these apps load at system start-up and keep running in the background using precious cpu and other resources apart from eating up memory. This often leads to poor performance and battery life. So once you get rid of these apps you will start experiencing better performance AND AN AWESOME BATTERY LIFE(personal experience)
Wow, I want to get rid of those stubborn apps...show me how to do it.
Sure
PRE-REQUISITES:
1. You should be rooted
2. Your phone should have the ClockWorkMod (CWM) Recovery installed.
3. You should have adb up and running
4. Turn on usb debugging.
{
"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"
}
OPTIONAL:
1. You may want to create a Nandroid Backup through CWM before doing any of the steps listed below.
2. Install abdb insecure by chainfire to run adb commands as root(insecure boot image). This will allow you to boot in to recovery through adb. Once installed the app should look like this
The PROCESS:
1. Ensure that the pre-requisites are met.
2. Connect the phone to the computer through the USB cable
3. To check whether you have properly installed adb do this
Open a command prompt window (start>run>cmd) and type this
Code:
adb devices
If adb is set up and running it should list your device in the list of attached devices some thing like this
Code:
List of devices attached
42801c7449ff097 device
4. Now use the following command to make a backup copy of all the system apps on your phone
Code:
adb pull /system/apps C:\* destination of your choice *
This will ensure that you can install back any app that you remove using this process and also it serves as a reference to the list of system apps. Look at the apps and make a list of apps that you want to get rid off. This (thanx to winwiz for compiling it)might help you to decide which one's are important and which are not, which one's can safely be gotten rid of and which should not be touched. Play carefully. Here is a list of apps that I have safely removed with great benefits to boot-up time, battery and overall performance.
Dlna.apk
Dlna.odex
BuddiesNow.apk
BuddiesNow.odex
Days.apk
Days.odex
Email.apk
Email.odex
EmailWidget.apk
EmailWidget.odex
GameHub.apk
KiesAir.apk
kieswifi.apk
kieswifi.odex
Kobo.apk
MusicHub_N1.apk
MusicHub_U1.apk
PressReader.apk
ReadersHub.apk
ReadersHub.odex
SamsungApps.apk
SamsungAppsUNA3.apk
SamsungIM.apk
SamsungWidget_News.apk
SamsungWidget_News.odex
SamsungWidget_StockClock.apk
SamsungWidget_StockClock.odex
SevenEngine.apk
SnsAccountFb.apk
SnsAccountFb.odex
SnsAccountLi.odex
SnsAccountTw.odex
SnsAccountLi.apk
SnsAccountTw.apk
SnsDisclaimer.apk
SnsDisclaimer.odex
SnsImageCache.apk
SnsImageCache.odex
SnsProvider.apk
SnsProvider.odex
SocialHub.apk
SocialHub.odex
Zinio.apk
Click to expand...
Click to collapse
You may want to add/remove apps to/from this list.
5. Moving on, Once you have decided the apps to remove reboot into CWM recovery. Use this command to do that through adb.
Code:
adb reboot recovery
Note: You must have an insecure boot image for this to work (See point number 2 in optional points)
else
use any of the common methods to boot into recovery. Use key presses or CWM Manager or do whatever, just get in to that ******g recovery.
6. Next, Once you are into the recovery type this command in the command prompt
Code:
adb shell
This will get you into the linux shell on your android device so that you can use all the linux shell commands like in a regular linux shell
7. You must now see a # or $ at the prompt (doesn't make a difference) indicating that now you are into the linux shell. Type the following command in the prompt.
Code:
mount /system
This will load the system partition into memory so that you can play around with its contents.
8. Now to the most important step. Removing the apps. Use the following command in the prompt
Code:
rm /system/app/****.apk
or
Code:
rm /system/app/****.odex
Replace **** with the name of the apk or odex file that you want to remove.
Repeat the command for all the files that you want to get rid off.
Note: Remember to press enter after each command
9. Once you have finished removing all the bloatware just type
Code:
exit
in the prompt. Thats it.
Reboot! (You may use
Code:
adb reboot
for that purpose).
You will now be greeted with a faster performing, responsive, battery conserving and most importantly a bloatware free phone.:good:
10. Thank me if this helped and don't hesitate to ask questions.
As a supplementary note I would like to recommend this app [Requires Root]. Once installed use its corpse finder feature to eliminate all the left over files belonging to the bloatware apps that we just removed. It is as easy as Search and Clean. This will free up more space in your system partition.
Troubleshooting:
Q. I removed Kies Air using the method above but it is still present in the app drawer. What to do?
Ans: This happens if you have updated Kies Air through the play store.
Go to Settings>Applications>Manage Applications
Scroll down to Kies Air --> Select it ---> Uninstall updates
Reboot!. Thats it. Kies Air is gone for good.
A Very Important Note:
I haven't tried it on a Non-Rooted phone. But I think it should work as far as you have adb working and can boot into the recovery(Stock recovery in case of Non- Rooted phones) by some means you are good to go from step number 6.. Have a list of apps to be removed before hand, speeds up the process.
Battery Saving Tips:
Coming Soon.....!

RESERVED!!

Buddy we are already having automated tool for removing bloats ...

mj.vikram said:
Buddy we are already having automated tool for removing bloats ...
Click to expand...
Click to collapse
I'm aware of that buddy. I have even mentioned it in my post.:good: As I said this method is for people who would like to understand whats happening behind the scenes...rather than just flashing a script package.

The-Droidster said:
I'm aware of that buddy. I have even mentioned it in my post.:good: As I said this method is for people who would like to understand whats happening behind the scenes...rather than just flashing a script package.
Click to expand...
Click to collapse
Thanks for taking time and writing this :good:....
Nice guide and just one more alternative for user's if you feel this is difficult process for you, using Root explorer or similar app's got to /system/apps/ and delete the required file's (as mentioned by The-Droidster in the above) and restart the mobile...

What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
ICS = I SEE ASS Lol
++##» GALAXY R «##++

gitanshu said:
What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
Click to expand...
Click to collapse
its same buddy, both are same but this for the people who want to learn how to use ADB they can use this because this very well explained :good: ....

gitanshu said:
What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
ICS = I SEE ASS Lol
++##» GALAXY R «##++
Click to expand...
Click to collapse
I don't see any problem in doing that....but you may experience force closes if you do this when the system is online because the apps that you are removing are still running in the background. So it is better if you do it by mounting the system through recovery.

if uu have rooted phone than u can remove bloat using titanium backup or rom toolbox pro

+1 for using Adbd insecure. It's a great debugging tool on stock roms.
Sent from my GT-I9103

Adam77Root said:
+1 for using Adbd insecure. It's a great debugging tool on stock roms.
Sent from my GT-I9103
Click to expand...
Click to collapse
Yeah its like unleashing a new side of adb. Makes it all the more valuable

Please Help This Has Ruined My Day. Accidentally Disabled or Deleted I Don't Know which one com.android.systemui

Please Help This Has Ruined My Day. Accidentally Disabled or Deleted I Don't Know which one com.android.systemui
So I have a OnePlus 6 with Lineage OS, TWRP and Magisk all installed and i was just looking at apps in App Manager and i accidentally press the same area twice and Disabled or Deleted I don't know com.android.systemui and the screen went black so i rebooted the phone and it says "Android Is Starting" and never fully boots up and I don't know how to fix It without losing my files I tried to flash the Lineage OS image again but didn't work also I have a password (I Know The Password but can't decrypt my files in TWRP) and I don't want to lose my files, i won't reset the storage without decrypting and backing up my files, also pm command In ADB shell does not work it says its "inaccessible or not found". Is there a way i can decrypt my files and move them off my phone or a way i can fix com.android.systemui this has ruined my day please help if you smart. Also maybe i could Reinstall/Reenable com.android.systemui by changing some config file or doing something else just help please If someone can help me get my files off of my phone and/or fix it without a reset I would be so happy and you would be a really good person
My First Thread on this please reply to this that one if you can https://forum.xda-developers.com/t/...-know-which-one-com-android-systemui.4480157/

This is what is in com.android.systemui/cache/
a file called lockscreen_capture_port.png but the image might be different for you device.
{
"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"
}

Raffles727 said:
This is what is in com.android.systemui/cache/
a file called lockscreen_capture_port.png but the image might be different for you device.
View attachment 5686769
Click to expand...
Click to collapse
so what do i do to fix it? do i delete some file or what do i do

If you accidentally deleted the folder I suggest to re-create it and then put the png image , try my image but it is for a Samsung, it may not be the correct dimensions. On my device (Samsung) the folder only had the .png image in it. The full path is Android > data > com.android.systemui > cache > which contains the image lockscreen_capture_port.png
You can try connecting the device to your computer in order to do this.

Oh, so you killed your Android subsystem? What do you need that for? (Just a little joke.)
You do have ADB? Is it rooted? #?
If you can get to ADB, the first thing to do is:
Code:
C:\>adb shell
# stop
# logcat
That stops the Android subsystem from trying to start. Then the logcat will show you what it doesn't like.
You don't have to be a rocket scientist to see what it's complaining about.
===============================
Are you trying to get photos off /sdcard or data in Whatsapp?
Code:
# adb pull /sdcard/Books
Or whatever.
In short, getting stuff off /sdcard is easy, getting application data off requires root.
===============================
Then there's the question of fixing this.
As @Raffles727 says, you need to recreate the directory and the two subdirectories (cache and code_cache).
It's not certain thay you have both, but it wouldn't hurt.
On my device there is /data/data/com.android.systemui/gestures_config
I don't think that any "cache" files are that important, although a missing directory could cause crashes.
A missing XML JSON file could make it unhappy, what does logcat say? Here's my gestures_config:
Code:
{"displayIndicator":false,"enable":true,"enableBehindKeyboard":true,"guestConfigMap":{"gestures_bottom_left":"BACK","gestures_bottom_middle":"HOME","gestures_bottom_right":"TASK_SWITCH","gestures_left_bottom":"NONE","gestures_left_middle":"NONE","gestures_left_top":"NONE","gestures_right_bottom":"NONE","gestures_right_middle":"NONE","gestures_right_top":"NONE","gestures_top_left":"NONE","gestures_top_middle":"NONE","gestures_top_right":"NONE","slide_gestures_left":"VOLUME","slide_gestures_right":"WARM_LIGHT"},"indicatesHeight":50,"indicatesTransparency":50,"indicatesWidth":50,"preventMiscontact":false,"slideEnable":false,"slidingDistance":100}
(Although, since this is JSON, I kind of doubt that you have this.)
Try to fix something, then reboot.

Raffles727 said:
If you accidentally deleted the folder I suggest to re-create it and then put the png image , try my image but it is for a Samsung, it may not be the correct dimensions. On my device (Samsung) the folder only had the .png image in it. The full path is Android > data > com.android.systemui > cache > which contains the image lockscreen_capture_port.png
You can try connecting the device to your computer in order to do this.
View attachment 5686775
Click to expand...
Click to collapse
i think that path is encrypted so i cant do that

Renate said:
Oh, so you killed your Android subsystem? What do you need that for? (Just a little joke.)
You do have ADB? Is it rooted? #?
If you can get to ADB, the first thing to do is:
Code:
C:\>adb shell
# stop
# logcat
That stops the Android subsystem from trying to start. Then the logcat will show you what it doesn't like.
You don't have to be a rocket scientist to see what it's complaining about.
===============================
Are you trying to get photos off /sdcard or data in Whatsapp?
Code:
# adb pull /sdcard/Books
Or whatever.
In short, getting stuff off /sdcard is easy, getting application data off requires root.
===============================
Then there's the question of fixing this.
As @Raffles727 says, you need to recreate the directory and the two subdirectories (cache and code_cache).
It's not certain thay you have both, but it wouldn't hurt.
On my device there is /data/data/com.android.systemui/gestures_config
I don't think that any "cache" files are that important, although a missing directory could cause crashes.
A missing XML file could make it unhappy, what does logcat say? Here's my gestures_config:
Code:
{"displayIndicator":false,"enable":true,"enableBehindKeyboard":true,"guestConfigMap":{"gestures_bottom_left":"BACK","gestures_bottom_middle":"HOME","gestures_bottom_right":"TASK_SWITCH","gestures_left_bottom":"NONE","gestures_left_middle":"NONE","gestures_left_top":"NONE","gestures_right_bottom":"NONE","gestures_right_middle":"NONE","gestures_right_top":"NONE","gestures_top_left":"NONE","gestures_top_middle":"NONE","gestures_top_right":"NONE","slide_gestures_left":"VOLUME","slide_gestures_right":"WARM_LIGHT"},"indicatesHeight":50,"indicatesTransparency":50,"indicatesWidth":50,"preventMiscontact":false,"slideEnable":false,"slidingDistance":100}
Try to fix something, then reboot.
Click to expand...
Click to collapse
adb does not work (it says "adb: no devices/emulators found when i run" adb shell) unless in twrp but in twrp /sdcard is encrypted and twrp cant unencrypt lineage os for some reason also its not a missing driver issue im on linux witch has all android drivers by default when you install platform tools

Renate said:
Oh, so you killed your Android subsystem? What do you need that for? (Just a little joke.)
You do have ADB? Is it rooted? #?
If you can get to ADB, the first thing to do is:
Code:
C:\>adb shell
# stop
# logcat
That stops the Android subsystem from trying to start. Then the logcat will show you what it doesn't like.
You don't have to be a rocket scientist to see what it's complaining about.
===============================
Are you trying to get photos off /sdcard or data in Whatsapp?
Code:
# adb pull /sdcard/Books
Or whatever.
In short, getting stuff off /sdcard is easy, getting application data off requires root.
===============================
Then there's the question of fixing this.
As @Raffles727 says, you need to recreate the directory and the two subdirectories (cache and code_cache).
It's not certain thay you have both, but it wouldn't hurt.
On my device there is /data/data/com.android.systemui/gestures_config
I don't think that any "cache" files are that important, although a missing directory could cause crashes.
A missing XML JSON file could make it unhappy, what does logcat say? Here's my gestures_config:
Code:
{"displayIndicator":false,"enable":true,"enableBehindKeyboard":true,"guestConfigMap":{"gestures_bottom_left":"BACK","gestures_bottom_middle":"HOME","gestures_bottom_right":"TASK_SWITCH","gestures_left_bottom":"NONE","gestures_left_middle":"NONE","gestures_left_top":"NONE","gestures_right_bottom":"NONE","gestures_right_middle":"NONE","gestures_right_top":"NONE","gestures_top_left":"NONE","gestures_top_middle":"NONE","gestures_top_right":"NONE","slide_gestures_left":"VOLUME","slide_gestures_right":"WARM_LIGHT"},"indicatesHeight":50,"indicatesTransparency":50,"indicatesWidth":50,"preventMiscontact":false,"slideEnable":false,"slidingDistance":100}
(Although, since this is JSON, I kind of doubt that you have this.)
Try to fix something, then reboot.
Click to expand...
Click to collapse
sould i try to run adb shell wile booted into twrp and cd to /data/data and use mkdir to make a new /data/data/com.android.systemui

Is /data even mounted?
Code:
# cd /data
# ls -l
Didn't you have ADB enabled on your normal system?
Do you see the normal bootanimation?
Is the USB showing anything in normal system? MTP?

iwanttoroota11walmart said:
sould i try to run adb shell wile booted into twrp and cd to /data/data and use mkdir to make a new /data/data/com.android.systemui
Click to expand...
Click to collapse
never mind it says required key not available so i cant modify /data/data so am i just screwed

Renate said:
Is /data even mounted?
Code:
# cd /data
# ls -l
Didn't you have ADB enabled on your normal system?
Do you see the normal bootanimation?
Is the USB showing anything in normal system? MTP?
Click to expand...
Click to collapse
no i cannot access my phone on my pc from the normal system only in twrp and it shows my normal boot animation

Right, but in TWRP /data is not mounted, it's encrypted and TWRP can't decrypt/mount it?

iwanttoroota11walmart said:
no i cannot access my phone on my pc from the normal system only in twrp and it shows my normal boot animation
Click to expand...
Click to collapse
its liveboot so i can see my logcat when the phones turning on could that help at all

Renate said:
Right, but in TWRP /data is not mounted, it's encrypted and TWRP can't decrypt/mount it?
Click to expand...
Click to collapse
it is encrypted and if i try to do adb pull /data only a coupple folders can copy over to my pc and when i try to decrypt when turning it on it cant decrypt also i have a pattern set and a fingerprint set if that helps at all

iwanttoroota11walmart said:
it is encrypted and if i try to do adb pull /data only a coupple folders can copy over to my pc and when i try to decrypt when turning it to twrp on it cant decrypt also i have a pattern set and a fingerprint set if that helps at all
Click to expand...
Click to collapse

iwanttoroota11walmart said:
it is encrypted and if i try to do adb pull /data only a coupple folders can copy over to my pc and when i try to decrypt when turning it on it cant decrypt also i have a pattern set and a fingerprint set if that helps at all
Click to expand...
Click to collapse
and /scard (where my files are that i need off of it before i would reset the phone) is encrypted

iwanttoroota11walmart said:
and /scard (where my files are that i need off of it before i would reset the phone) is encrypted
Click to expand...
Click to collapse
also i can boot other recoverys if there is a recovery that can decrypt lineage os stuff

Encrypted data makes life awfully difficult.
Yeah, liveboot could give us some info. Does it just keep running and restarts by itself?
Is the bootloader unlocked?
Was ADB enabled before it died?
Was this Magisk'ed?
I can think of two solutions
1) Force ADB to run
2) See if adding the directories to a ramdisk would work.

Renate said:
Right, but in TWRP /data is not mounted, it's encrypted and TWRP can't decrypt/mount it?
Click to expand...
Click to collapse
also twrp can mount /sdcard to mtp but its encrypted

Renate said:
Encrypted data makes life awfully difficult.
Yeah, liveboot could give us some info. Does it just keep running and restarts by itself?
Is the bootloader unlocked?
Was ADB enabled before it died?
Was this Magisk'ed?
I can think of two solutions
1) Force ADB to run
2) See if adding the directories to a ramdisk would work.
Click to expand...
Click to collapse
liveboot runs until the boot animation is over
the bootloader is unlocked i could wipe and reinstall the os but then i lose my data that i really really do not want to lose
adb was enabled before it died and also when the phone is turned on to system it shows "Android is starting' but it never stops doing that
it has magisk installed yes
how would i force adb to run?