Hi, i've had my phone for about 6 months and I'm running out of space on the internal memory. It's not an optimus one, but it looks identical to it. It doesn't have much internal memory to begin with. My question is how to unlock it, or how do I delete the locked stuff that clutters it up when I first get it. Diner dash and the stupid little games take up the space that I need.
the simple answer is you need to root. See here for how to. I've had good luck with z4root. When I got my first P509, I rooted but was scared to flash a recovery and rom for fear of bricking my shiny new phone. The fact is though, the only thing that has ever bricked my phone has been KDZ which is an official LG tool.
Once you root, there are many ways that you can go about removing unnecessary bloat. Probably the most popular way is to use Titanium backup which can be downloaded from the market which allows you to uninstall any application on your phone once you grant TiBackup root access.
You could also use Root Explorer (also on the market) which requires that you know a little bit about the phone system itself but will get the job done, if you know what you're doing. Personally I dislike both methods because I don't 'manage' my phone from my phone, too many things can go wrong. Plus, both Titanium Backup and Root Explorer are paid apps. I prefer to use the ADB, but that requires the use of command line which is a big road block for some people.
Should you choose to go the adb route (which assumes that you have installed the Java Development kit available here and the Android Software Development Kit (or SDK) found here
Once you have installed the Android SDK, you can execute the adb (which is in the platform tools folder) from the command line. And no, there is no GUI version, the ADB is strictly a command line tool. To access and modify contents of your phone you will need to gain root access via adb shell. Oh yeah, and don't forget, you need to enable USB debugging on your phone!!!
Code:
adb shell
su
the prompt should change to a pound sign once you have granted "unknown" root access on your phone. once you've gained root access, execute the following command to gain read and write privileges for the phone's system
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
Once you've done this you can delete things from your phone's system, but be EXTREMELY careful because you can mess your phone up pretty bad if you don't know what you're doing.
first, change directory (the command is literally cd) into /system/app which is where all non removable apps are stored on your phone
Code:
cd /system/app
then you can bring up a list of all the files in the folder with
Code:
ls
then you can delete the unnecessary apps with
Code:
rm -rf
I CANNOT STRESS THIS ENOUGH!!!! Be extremely careful about what you delete in here. it is highly recommended that you use the absolute path to the file you are deleting as to minimize accidental cases of
Code:
rm -rf /*
which will probably brick your phone.
in all reality though you're not going to be able to free up much space by removing the games that come with the phone. Plus it is actually safer to simply flash a custom recovery, do a nandroid backup and then flash a custom ROM. The process is simpler, easy to undo and there is very little risk of breaking the system. Modifying the contents of the stock ROM while it may actually seem less extreme than flashing a custom firmware is far more dangerous, simply because you don't have the added security of a good backup to flash back to in case you mess something up. Not only that, but by rooting your phone and removing stock apps already void your warranty so you may as well go ahead and get your money's worth out of the phone.
Once you have installed a custom ROM, you can always use app2sd which is a feature that allows you to install applications to your SD card instead of your phone's internal memory. I don't personally use it because I keep my phone pretty lean, outside of the Android system and default Google apps, I only have maybe 10 or so apps installed; easysms, facebook, twitter, XBMC remote, my bank's app and of course Angry Birds.
N00b-un-2 said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
Click to expand...
Click to collapse
I have this phone and use:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount the system partition
***read up on using android sdk (adb)***
attached are the references I keep for working on my Optimus T:
1. List of /system/app files (says 10L, but 10S is the same)
2. List of files I always remove (change to suit your taste)
PS: Once you take care of removing the crapware, let all the built in apps update through the market, then go back and replace the old versions with the new versions (no need for two versions of the same app, it's a waste of space).
Remove file:
rm {filename}
rm AppPack.apk
Replace old version with new version (or make user app a system app):
cat /data/app/{update filename} > /system/app/{original filename}
cat /data/app/com.google.android.maps-1.apk > /system/app/Maps.apk
**remember to use the EXACT same name as shown in the list (Caps make a difference)
I always factory reset after making the changes to clean up.
Enable root access with adb:
C:\android-sdk\tools\adb devices
C:\android-sdk\tools\adb shell
echo 1 > /data/local/lge_adb.conf
*****MANUALLY REBOOT DEVICE*****
Works with P509 V10s
mar11974 said:
I have this phone and use:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount the system partition
Click to expand...
Click to collapse
Maybe different versions of Optimus handle the file system differently. Also, are you mounting via ADB with the phone in recovery? I don't think I've ever mounted anything except mtdblock1 for /system. Interesting, and to be honest from what I understand about the way the filesystem is supposed to work block 3 should be where /system is, but I've never had any success in gaining r/w privilege by mounting anything but block 1.
mar11974 said:
Enable root access with adb:
C:\android-sdk\tools\adb devices
C:\android-sdk\tools\adb shell
echo 1 > /data/local/lge_adb.conf
*****MANUALLY REBOOT DEVICE*****
Works with P509 V10s
Click to expand...
Click to collapse
I've tried rooting the manual way before always without success. Being a Linux hacker, I'm not afraid of the command line and using a tool like z4root always felt like a cop out. But hey, root is root.
Literally to gain root access you are adding a 1 (an on switch if I'm not mistaken) to the a file called lge_adb.conf? That's crazy!
If all you want to do is root, use gingerbreak. Worked on 2 Optimus T phones. It takes maybe 5 minutes.
After rooting, you can download Titanium backup from the market. It can freeze those unwanted apps. If you suddenly find that you need them, you can defrost the apps.
You should consider using a custom ROM. You can use any Optimus T OR Optimus One ROM. Do not use ROMs for the other flavors of Optimus. If you decide to move your app folder to the SD, you can have an almost unlimited # of apps.
Good Luck
N00b-un-2 said:
I've tried rooting the manual way before always without success. Being a Linux hacker, I'm not afraid of the command line and using a tool like z4root always felt like a cop out. But hey, root is root.
Literally to gain root access you are adding a 1 (an on switch if I'm not mistaken) to the a file called lge_adb.conf? That's crazy!
Click to expand...
Click to collapse
The leaked 2.3.3 thread mentioned the method, checked system.mbn file for V10s and the code is there also. This isn't a "hack", it is built into the rom by the manufacturer.
lge_adb.conf doesn't exist in the rom, so it actually is creating a file lge_adb.conf that contains a 1. The system looks for the file on reboot and sets the root status accordingly.
N00b-un-2 said:
Maybe different versions of Optimus handle the file system differently. Also, are you mounting via ADB with the phone in recovery? I don't think I've ever mounted anything except mtdblock1 for /system. Interesting, and to be honest from what I understand about the way the filesystem is supposed to work block 3 should be where /system is, but I've never had any success in gaining r/w privilege by mounting anything but block 1.
Click to expand...
Click to collapse
You may be right, I have been using mtdblock3 from searches trying to remove the crapware, but it works? When using mtdblock1, if you factory restore your phone (HOME + VOL -) do the removed apps return (changes lost)?
mar11974 said:
You may be right, I have been using mtdblock3 from searches trying to remove the crapware, but it works?
Click to expand...
Click to collapse
If you want to find out what is where on your phone, just run:
Code:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
As far as apps returning once they've been removed I wouldn't imagine so. Once you delete them, they're gone. It's not like the Android system has redundancy built into it. If it did, I would imagine that hacking our phones would be considerably more difficult if every time we rebooted the system returned to stock.
Interesting thought though, because I have a bit of experience installing custom firmware on PSPs before I ever started hacking Android and the similarities between the two are striking, but the PSP firmware is designed with redundancy in mind in order to prevent permanent changes being made to the system like flashing custom firmware, and typically the changes made to the system are stored in volatile memory. I had a PSP-3000, and in order to "hack" it so I could play games from the memory stick, it was like a 5 step process involving a ram disk exploit and any time the system suffered a crash or hard reboot, I would have to repeat the whole process, which was often hit or miss. It would usually take me 2-3 attempts to run the exploit enabling custom firmware. Too bad PSP doesn't have an ADB like tool!
doktornotor said:
If you want to find out what is where on your phone, just run:
Code:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
Click to expand...
Click to collapse
Exactly what mine shows, but mounting mtdblock3 command has always worked for me. WHY???
The only thing I can imagine is that since Android is a variant of Linux, there are both a physical address where data is stored and there also exists a virtual file system. Kind of like how you can access the contents of a mounted disk in Linux at /dev/sdb1 or at /media/your-thumb-drive or /mnt/your-thumb-drive, etc. for example. Perhaps this is not the most apt description of this perceived behavior, but I would venture to guess that I'm not too far off. Maybe the virtual location of the particular block is not necessarily important. It certainly leaves one to wonder
mar11974 said:
Remove file:
rm {filename}
rm AppPack.apk
Replace old version with new version (or make user app a system app):
cat /data/app/{update filename} > /system/app/{original filename}
cat /data/app/com.google.android.maps-1.apk > /system/app/Maps.apk
**remember to use the EXACT same name as shown in the list (Caps make a difference)
I always factory reset after making the changes to clean up.
Click to expand...
Click to collapse
The problem with this on a T-Mobile Optimus T is that all the JUNK games and apps and stuff already in the system apps directory, which is why they cant be uninstalled normally.
You can download SuperManager from the market for FREE and remove them from the system/app directory as well, instead of payign for Root Explorer.
If you factory restore the phone, they all come back.
There's a fairly large list of apps you can delete from the TMo optimus T. the primary ones I recommend are the games and telenav GPS. Dont forget to delete the ODEX file as well if you remove the apk!
Here's a list of all the prinstalled junk I've removed off my Optimus T:
AnalogClockWidget.apk
androidERSEmail.apk
AppPack.apk
BookmarksWidget.apk
Calculator.apk <- Redownload from market for different calc app
CalendarWidget.apk
CarHome.apk
CarHomeLauncher.apk
ClockWeatherWidget.apk
ConnectionManagerWidget.apk
DeskClock.apk
DigitalAlarmWidget.apk
DinerDash.apk
DoodleJump.apk
DriveSmart.apk
DriveSmartHelper.apk
DualClockWidget.apk
Email.apk
Facebook.apk <- Redownload from market for current (removable) app
GenieWidget.apk
Gmail.apk <- Redownload from market for current app
GoogleQuickSearchBox.apk
Maps.apk <- Google Maps, Redownload from market for current app
MemoWidget.apk
MessageWidget.apk
MoviePlayer.apk
Music.apk
PacMan.apk
PhotoWidget.apk
PicoTts.apk
Protips.apk
SelfHelp.apk
SoundRecorder.apk
Street.apk
SwypeTips.apk (left swype, just removed the annoying tips part)
Talk.apk
Telenav.apk
thinkdroid.apk
TtsService.apk
Twitter.apk
VisualizationWallpapers.apk
VisualVoicemail.apk <- Redownload from market for current t-mobile app
VoiceDialer.apk
VoiceSearch.apk
Web2goHome.apk
YouTube.apk <- Redownload from market for current (removable) app
Z4Root is the one I used...all you need to do is go to the market .download 4shared .open it and they should be a link there that would allow you to download the app ..if you want to..now search z4root.apk.the latest version should be on top download it ...turn your phone off after that..back on again. enable debugging..go to the app use what you want there's two option ..you can read no need for me to tell you the two options ..click which one you want. then out runs the process and be alarm if your phone reboots....it needs to ....now if you go back to the app you have a choice of un rooting....if you want..there is a app in the market that will check of you have root access..search ..root checker....oh yea you have a new app called super user....that'd what allows root apps to run.do don't uninstall it ..that goes for z4root to ..also..you can use 4shared to get free apps...just search and there you go..
Sent from my LG-P509 using XDA App
Related
Hello again everybody.
Here is a little tutorial to get rid of the crap thats shipped with the phone
and get it on a sweet diet of slimfast.
If you think to yourself "HEY! that shouldn't be removed!"
I most likely removed it because there is a Market alternative.
*Always be careful when modifying /system*
First we need to remount our phone and make /system/app - R/w
adb remount
then type:
adb shell
*In Shell ($)
su (IMPORTANT)
cd /system/app/
ls
Now you can start removing the bloat.
rm Launcher.* (ONLY IF YOU HAVE AN ALTERNATIVE LAUNCHER INSTALLED!)
rm Maps.*
rm SystemTutorial.*
rm LatinIME.* (MAKE SURE YOU HAVE ANOTHER KEYBOARD INSTALLED)
rm Email.*
rm Calculator.*
rm EmotionWeather.*
rm EmotionPhotoWidget.*
rm EmotionCalendar.*
rm EmotionPhotoAlbumWidget.*
rm EmotionBookmarksWidget.*
rm EmotionEvents.*
rm Twidroid.*
rm EmotionMemo.*
rm EmotionRSSReader.*
rm EmotionVideoWidget.*
rm EmotionClockWidget.*
rm HwIME.*
as always, reboot.
and, as with most things in the filesystem, this can also be done
with Root Explorer
If you messed something up, it probably wasn't meant to be
removed and most likely wasn't listed above. Start over from scratch...
unless you made back-up of course
If i missed anything, shoot me a message!
You honestly consider Calculator, Maps and Email "bloatware"?
raduque said:
You honestly consider Calculator, Maps and Email "bloatware"?
Click to expand...
Click to collapse
if they can be downloaded (and be more up to date from the market) then yeah.
You don't need to delete them to download the updated versions. My tablet prompted me to update them as soon as I connected to wifi and logged into my google account.
Updates take more space
When you update a Android app that is part of the rom it takes up 1.5 to 2x the storage than if you just simply download the newest version.
crispien said:
When you update a Android app that is part of the rom it takes up 1.5 to 2x the storage than if you just simply download the newest version.
Click to expand...
Click to collapse
That honestly means nothing to me. I don't load 500 apps on my devices.
raduque said:
That honestly means nothing to me. I don't load 500 apps on my devices.
Click to expand...
Click to collapse
look, when you delete /system files obviously it doesn't touch the /data... obviously... now your /system is on your INTERNAL partition so removing these files frees up space on your INTERNAL memory, and as for obviously downloading the updated apps from the market does update them YES AND INSTALLS THEM INTO /data, but it does not delete the OLD outdated version which still reside in /system which need to be updated and is taking up space, i hope this helps you understand whats going on... hopefully.
joenilan said:
look, when you delete /system files obviously it doesn't touch the /data... obviously... now your /system is on your INTERNAL partition so removing these files frees up space on your INTERNAL memory, and as for obviously downloading the updated apps from the market does update them YES AND INSTALLS THEM INTO /data, but it does not delete the OLD outdated version which still reside in /system which need to be updated and is taking up space, i hope this helps you understand whats going on... hopefully.
Click to expand...
Click to collapse
Yes, I understand this. But, they are two separate partitions. The S7 does not dynamically resize partitions. /system and /data are completely self-contained, and the size of either does not effect the other.
Space on /system, does not effect space on /data. I don't know how much plainer I can say this. All you're doing is freeing space on /system, but nothing goes there except pre-installed *system* files!
The bolded, underlined, italicized is the part that doesn't make any sense. It's taking up space in /system, which has no bearing on space in /data. Period, end of sentence, full stop. I'm not saying anything more on this matter, because I don't think you're going to get it.
raduque said:
Yes, I understand this. But, they are two separate partitions. The S7 does not dynamically resize partitions. /system and /data are completely self-contained, and the size of either does not effect the other.
Space on /system, does not effect space on /data. I don't know how much plainer I can say this. All you're doing is freeing space on /system, but nothing goes there except pre-installed *system* files!
The bolded, underlined, italicized is the part that doesn't make any sense. It's taking up space in /system, which has no bearing on space in /data. Period, end of sentence, full stop. I'm not saying anything more on this matter, because I don't think you're going to get it.
Click to expand...
Click to collapse
probably not, i can't get through the fog of cocky responses. instead of being a helpful person.
joenilan said:
probably not, i can't get through the fog of cocky responses. instead of being a helpful person.
Click to expand...
Click to collapse
Well, that's an interesting way of saying that you don't understand what I'm saying.
http://forum.xda-developers.com/showpost.php?p=11476068&postcount=9
Repeat after me:
"/system space is completely separate from /data space. One has no bearing on the other"
Once you have saved some room on /system/app, you can then move some of the apps that you have in /data/app to that directory. I have done this for swype, adw, facebook, google apps, documents to go for example, this is saving me an extra precious 40M.
dear joenilan..
pls help..i have remove the home launcher .replace with vtl.
i do factory reset and forgot restore with Titanium before
now face boot loop ..what should i do now.
dont have cwm in my ideos
thx big for advice
rgds
sasmitadani :
Flash a new room,
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html
I would also request that the OP's post be removed, or huge big letters of warnings or better described procedures be added, this can be very harmful and really makes no sense.
This is how i managed to install the Google Maps 5.7.0 ownhere/Brut.all MOD which enables Navigation in countries where originally you cnt use this app. this is a modified version that seamlessly replaces the original app.
i tried to follow the instructions provided in the original thread but i kept facing problems and errors like "Application not installed" when trying to install the app, and "remount failed: no such file or directories", among others.
i also dnt have the Maps app availble in the market in my country, i can only sideload it.
it took me few days of googling to finally make it work on my Galaxy Ace. i'm running a rooted stock 2.2.1
it's simple once you got the right instructions. but as usual, i'm not responsible if your phone just decides to go brain dead on its own
for this you need ROOT access, Superuser, ADB and Titanium Backup
in Titanium Backup, choose Maps and back it up (app+data).
in case things dnt work out, you can always use this backup to restore the original app and data.
in Titanium Backup, choose Maps and wipe data then uninstall.
in Titanium Backup, choose Street View, wipe data and uninstall.
use whatever way to place the maps5.7.0-ownhere.apk file in the root of your sd card.
(i dnt know what's the diffrence between maps5.7.0-ownhere and maps5.7.0-ownhere-testkeyresign. i used the first and it's working fine.)
now connect your phone to your computer and make sure you keep your screen on. that's very important for the next step to work.
launch ADB and enter these commands:
adb shell (in the next line, a $ will appear)
su (when you inter this, Superuser in your phone will prompt you to grant root access. confirm it. a # will appear in the next line)
mount -t rfs -o remount,rw /dev/block/stl9 /system (this will remount your system in Read/Write mode)
cp /sdcard/maps5.7.0-ownhere.apk /system/app/maps5.7.0-ownhere.apk
mount -t rfs -o remount,ro /dev/block/stl9 /system (remount system back in ReadOnly mode)
exit
exit
Maps should appear in your app drawer.
you can now reinstall Street View.
if anything is not clear enough, just ask
I think its more easy to just use root explorer to copy that googlemaps apk to its proper place, because what i understand from that adb command is it copy the googlemaps apk to /system/app folder which could be done in just two or three click with root explorer. Cmiiw
But nevertheless, thanks for this tutorial tho
Sent from your phone
is it working
an0nym0us_ said:
I think its more easy to just use root explorer to copy that googlemaps apk to its proper place, because what i understand from that adb command is it copy the googlemaps apk to /system/app folder which could be done in just two or three click with root explorer. Cmiiw
But nevertheless, thanks for this tutorial tho
Click to expand...
Click to collapse
that was the first thing that came to my mind when installing didnt work. i copied the file with root explorer but the Maps app didnt show up in the app drawer.
i only speak from my own experience, i'm no expert.
thank you for the contrbution
imranaryan said:
is it working
Click to expand...
Click to collapse
it is working on my phone
This is more like a general question for every android device rather then for a specific one. My question is simple. Is it possible to extract the recovery.img (the stock one) so that it can be flashed back onto the custom recoveries?
i have the same question.
I have a Coby Kyros MID7127. I can get to Stock Recovery, now how do I save it? I've flashed CMW V4.0.1.5 and it more or less works.. but the buttons don't match and that makes it so i can't boot into recovery on power up.
if i could get the stock recovery.img, i'm hoping i could find someone to help me/teach me/point me in the right direction to modify CWM to work on my device.
thanks!
I also want to know this. Anyone?
From here http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Your phone has several devices which hold different parts of the filesystem:
Code:
#cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 04380000 00020000 "system"
mtd4: 04380000 00020000 "cache"
mtd5: 04ac0000 00020000 "userdata"
Note that the order is different for different phones! Check yours to make sure you use the right device.
In this tutorial, we will deal with "recovery" and "boot". "system" holds everything that gets mounted in your system/ directory, and userdata/ is everything that shows up in data/ (this is all the apps you've installed, your preferences, etc).
The recovery and boot partitions are at /dev/mtd/mtd1 and /dev/mtd/mtd2, and before you do anything else you should back these up:
Code:
# cat /dev/mtd/mtd1 > /sdcard/mtd1.img
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
(Note added by lxrose: These commands don't work if your phone is not rooted and the permissions are not set.)
The other thing you should do is put your favorite update.zip file into the root directory of your sd card so that if you screw up your boot partition you can boot into recovery mode and re-apply the update. You probably want one of the pre-rooted recovery images found elsewhere on the forums.
There is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1 unbeknownst to you. Watch out.
yes
I only started android kernel dev less than a week ago, but I have managed to successfully modify and update the kernel for my HP touchpad without too many issues.
My issue now is I'm trying to update the kernel on my HTC One XL (AT&T One X), and reading through guides like (h ttp://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images), I need to make a copy of the boot image. However I can't find the boot image!?!?!
The following folder does not exist:
/dev/mtd
or
/proc/mtd
Am I missing something? I'm sure this is a total noob problem, but can't find a solution anywhere.
In my TWRP backup folder I have a 'boot.emmc.win' file, can I extract the boot img from this?
Any help would be great!!
DACcer said:
I only started android kernel dev less than a week ago, but I have managed to successfully modify and update the kernel for my HP touchpad without too many issues.
My issue now is I'm trying to update the kernel on my HTC One XL (AT&T One X), and reading through guides like (h ttp://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images), I need to make a copy of the boot image. However I can't find the boot image!?!?!
The following folder does not exist:
/dev/mtd
or
/proc/mtd
Am I missing something? I'm sure this is a total noob problem, but can't find a solution anywhere.
In my TWRP backup folder I have a 'boot.emmc.win' file, can I extract the boot img from this?
Any help would be great!!
Click to expand...
Click to collapse
It uses emmc now. To check your partitions you can use: adb shell cat /proc/emmc
blazingwolf said:
It uses emmc now. To check your partitions you can use: adb shell cat /proc/emmc
Click to expand...
Click to collapse
:victory: that works!!!
However, now that I can see mounts, how can I copy the required image? For instance the output is:
#cat /proc/mtd
dev: size erasesize name
mmcblk0p23: 000....0 000....000 "misc"
mmcblk0p22: 00500000 00020000 "recovery"
mmcblk0p21: 00280000 00020000 "boot"
etc.
cat /dev/emmc/mmcblk0p21 gives me a file not found error.
There is a '21' folder under /dev/emmc? Assume this is the image??
Something along the lines of this should work: dd if=/dev/block/mmcblk0p21 of=/sdcard/boot.img bs=4096
Make sure the info is correct for your device.
blazingwolf said:
Something along the lines of this should work: dd if=/dev/block/mmcblk0p21 of=/sdcard/boot.img bs=4096
Make sure the info is correct for your device.
Click to expand...
Click to collapse
Ahhhh, the dd command :highfive:
Cheers blazingwolf! Just tried it then, and worked perfectly. Didn't set the block size, but assuming that's okay
Ok, so my wife has a BLU R1 Plus, rooted w/Magisk. She never gets around to telling me what goes on and what problems she's having, but today I had her phone and when I went to charge it, watched a browser window pop up...never a good sign. So I checked it out with MalwareBytes, and yes, kids, there's a trojan, the (in)famous Preinstall Data2, probably installed by BLU itself (although I've had her phone before and never noticed it). Ok, thinks I, this is simple. First freeze it, then rip it from the bowels of the /system directory by the roots (pun intended).
But I can't.
Tried using the paid version of Titanium Backup to freeze it. It reports frozen, but the app is still running and a reboot shows it not frozen. Used Titanium Backup's "open system details" (it doesn't appear in the list of installed apps in the Settings) and used Disable there, with the same results; everything thinks it's frozen until a reboot when it's not again.
So I tried using Root Explorer to make the /system mount R+W, and it couldn't - first time I've ever seen that, and I gotta tell you that concerns me. Next I booted into TWRP recovery and mounted /system there...in this case it WAS writable, which I verified by using TWRP's file manager to move a folder from /system/app to the sdcard partition, checking after a reboot to make sure it was there, then moved it back to /system/app again checking after a reboot to verify it returned. Tried remounting /system with a root terminal, but since there are so many different mount command changes now for the different phones, this one may have been my error.
So apparently I have two separate, and possibly unrelated, issues. Which leads to two questions:
1) Short-term: Since it's intentionally hiding, anyone know what the "Preinstall Data2.apk" is hiding as? (Or does anyone know how to find the location of an APK in the file system from Titanium Backup, either in the UI or inside the backup itself? I poked it pretty hard and can't find it.) If I know it's bogus name, in /system/app or /system/priv-app, I can use TWRP to get rid of the d*mned thing one and for all.
2) Long-term: WTF can I do to fix this thing not allowing me write access to /system ? That's just...wrong, isn't it?
Ok, handled the virus APK...as the folks from TitaniumBackup gently showed me, clicking on the "Current" line in the backup window will show the path to the APK...in this case it was in /data/app, so I didn't need the /system filesystem unlocked to kill the sucker.
Still, would love to know why I can't mount /system R+W...
Even if the app creates something in /data/app/, the real APK is /system/app/preinstallprovider-***_blu_***.apk. You might want to remove it through TWRP.