Related
I REALLY need some assistance, think I screwed my phone, really want to avoid a hard wipe.
I installed Lockbot the other day, has some issues with dual lock layers (i.e. the lockbot app wasn't disabling my HTC lock so I had two unlocks.). emailed dev and he sent me a beta version to hopefully correct issue. I only received an apk file from him.
FYI I am on fresh 1.1, rooted.
I used the kitchen to puch this file: "LockBotPro_1.10.0_beta.apk" to /system/app.
The install went successfully, but later after a reboot I face a HUGE issue. The lockbot app is hanging upon reboot and will not unlock. At first I thought i would still be okay, I had ATK and Advanced Task manager both running at start up, so I can enter both of them through my notification drop down menu. I used both to kill the task-to no avail it is still locked. I tried to use advanced task manager to uninstall lockbot - to no avail, it cannot be removed.
Then I tried to pull back the file through kitchen, to no avail.
I don't know what to do. I cannot get my phone to unlock and i cannot pull the file off through adb or kitchen. DOES ANYONE HAVE ANY IDEA ON HOW TO FIX THIS??????
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
wtphoto said:
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
Click to expand...
Click to collapse
I have tried to pull the file in both adb and in kitchen. Would it have installed as something other than the name I pushed it under?
Even if the phone is hard locking (kind of rare of android. even in all the stupid f'd up things I've done I've only hard locked my phone to the point that I couldn't even get in to adb once or twice) then the file system is still completely accessible while it's booting up. You can use the "pull any file" from the kitchen and check off that you want it to delete it after it's done. Just get it all queued up in the kitchen and then power on your phone. Once it gets passed the HTC logo wait a few seconds and then run the pull file from the kitchen. Should work just fine for you.
The alternative (if you are comfortable with adb) would be to boot your phone in to recovery (can also be done through the kitchen, even when it's in the middle of booting) and then type the following from a command prompt:
adb shell mount /system
adb shell rm /system/app/your-application.apk
FYI for future reference you should push these types of applications to /data/app. Your hard locks could either be caused by the fact that the beta just broke things, or it could be that you have a copy of it in both /data/app and in /system/app.
the problem is that you dont want to just pull the file all that does is create a copy of the file where ever you pull it to you need to use the rm cmd to actually remove the file and have you tried to do this from the recovery menu before the phone boots? I mean I am by no means an expert but commonsence says that if you do it in the recovery menu that it would be gone when the phone actually boots and the problem would be gone.
edit: sweet im not a complete noob anymore I was right about removing from the recovery. flipz explained it better though.
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
TF1984 said:
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
Click to expand...
Click to collapse
I'll be here.
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
You have a nandroid backup... don't you? Actually what you can try doing is flashing fresh right on top of itself. You won't lose any settings and it will overwrite everything in /system/app.
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
TF1984 said:
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
Click to expand...
Click to collapse
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Flipz I swear one day I am going to make a sizeable donation to you. If I can only find some extra money.
I think you have helped in every issue I have had after rooting, there haven't been many but you are always helpful when I run into trouble.
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
TF1984 said:
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
Click to expand...
Click to collapse
Might be worth it for you to try clearing your dalvik-cache to see if it fixes your FC's. If that doesn't work then my guess is you are using apps2sd and the symlink got broken somewhere along the way.
And no problem.
Yes I am using apps2sd. I tried the davlik clear cache in kitchen earlier today in attempt to fix the lockbot (I don't know, figured maybe it would work since i have no idea what that does to begin with).
Question, I did pull my sd card out earlier while the phone was off. Then booted and it only went into a boot loop, is that likely to have caused the FCs?
Does that mean that I cannot ever remove the sd card at all or will always cause this problem...cause that would friggin suck a big one!
flipzmode said:
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4942088&postcount=2 -- post #2 from the fresh rom thread from back in november.
The reason I don't like it is because it puts your phone at a huge risk of having problems once anything goes wrong. If you install a program that causes issues, a nandroid backup will not resolve the issue because the application is installed on your SD card not your phone. If your phone starts going crazy as reported here and here, then even just a restore possibly won't fix it. You might need to go as far as to wipe your SD card too. If you are lucky enough to have a restore fix your problems you will still need to reinstall every app, even if you didn't wipe your card. And on top of that when you try to reinstall any app it will think it's still installed, even though you restored your phone. But when you click "uninstall" it will just freeze half the time because there's nothing on the phone for it to actually install. I have also read many threads that say if you happen to boot the phone up without the SD card in then it will screw everything up.
Click to expand...
Click to collapse
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
TF1984 said:
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
Click to expand...
Click to collapse
Make sure you aren't forgetting the leading slash. /data/app not data/app. But no, nothing special. That should work. Although if using apps2sd you might want to push to /data/sd/app. It should work regardless because a2sd sets up a symlink but if your stuff is messed up then it might not be working right.
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
Type this command in to mount:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
That will mount the /system volume and put it in read-write mode.
Once you are finished deleting the file, type:
umount /system
Then reboot the phone.
Edit: If you want to mount the /data volume, type: mount -o rw -t yaffs2 /dev/block/mtdblock5 /data
So it's part of the system and doesn't show up under Manage APP settings? Do you just push the apk into the /system/app folder?
SiNJiN76 said:
So it's part of the system and doesn't show up under Manage APP settings? Do you just push the apk into the /system/app folder?
Click to expand...
Click to collapse
What's part of the system?
If you are saying that you want to install a random app you grabbed somewhere and the Applications Manager won't allow you to install it, you are correct. That is used to uninstall applications
You can install apps a few different ways. Personally, I only install apps while connected to my computer. So I simply...
Code:
adb install applicationName.apk
If I have a bunch of apps I wish to install, I use android commander (http://forum.xda-developers.com/showthread.php?t=622873)
Beyond that, you also have this option (http://android.modaco.com/content/s...e-clicking-on-your-pc-with-installapk-beta-1/) and there are also file managers (http://www.androidtapp.com/linda-file-manager-formerly-android-file-manager/) that will allow you to install apps.
Hope this helps!
Android Commander looks nice...and useful. Thanks for the links. I'll look into those programs to see if it does what I want it to do.
To elaborate on what I wanted...I took the IM.apk from enoms rom and installed it onto cy's rom using root explorer...but it shows under app manager...it's not 'flashed' into the system ROM. So I'm wondering how to install the IM.apk so that it looks like it came preinstalled with the ROM.
Hope nobody says that I need to make an update.zip... cause I think that would be a bit over my head.
Anyway...off to read up on the link you provided. Thanks!
SiNJiN76 said:
Android Commander looks nice...and useful. Thanks for the links. I'll look into those programs to see if it does what I want it to do.
To elaborate on what I wanted...I took the IM.apk from enoms rom and installed it onto cy's rom using root explorer...but it shows under app manager...it's not 'flashed' into the system ROM. So I'm wondering how to install the IM.apk so that it looks like it came preinstalled with the ROM.
Hope nobody says that I need to make an update.zip... cause I think that would be a bit over my head.
Anyway...off to read up on the link you provided. Thanks!
Click to expand...
Click to collapse
ooooh! gotcha.
Push any system replacements over their original...so IM.apk, Mms.apk, etc all get pushed into /system/app as you originally thought. Sorry, I didn't quite understand what you were asking.
But through my confusion, you got reading material...
Let me apologize first of all as I come from 5 years of using Windows Mobile knwoing what I am doing (cooking ROMs included) and now just got my Galaxy /Android a couple weeks ago and am blank at all of it.
After messing up with some system files and (useless) stock applications (like I removed stk.apk and other stuff) I decided to do a full hardware reset as the phone started getting random crashes.
But after the full reset things only got dramatically worse. I quickly realized all the missing system apps are still missing (I thought they'd be "restored") and basically nothing works, just crashes one after the next, cant use anything.
So, a hardware system reset on the galaxy, doesnt really reset anything except user installed apps and settings... amazing
Can someone please tell me (the idiot here, I know) how to do a real full restore where all system files, all missing files and positively everything gets back in the Tab as it was originally?
What a flippin' nightmare... Thanks in advance very much!
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
bartito said:
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
Click to expand...
Click to collapse
OK, first of all a big thanks for both file and info. Aside from the Stk.apk, the biggest thing that made me run into problems was trying to update my Contacts.apk:
http://forum.xda-developers.com/showthread.php?t=907399
things didnt work out for me and even after restoring the original files (Contacts.apk and Contacts.odex) nothing really worked again, reason for wich I tried a system reset.
Now, do I need to re-root the Tab or its still rooted, and can I perform the operations easily with Root Explorer like I did before? You mentioned to use adb and set permissions to 644 after push but, sorry again for the ignorance, I have no clue what adb is nor what/how to set permissions. Pathetic to be ignorant huh?
My last 2 questions are, where could I find the original Contacts.apk and Contacts.odex and if needed a full ROM to do a total restore?... hopefully I wont need to get to that point?...
Thanks a million again.
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
bartito said:
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
Click to expand...
Click to collapse
Hmmmm thanks again but I think Im beyond all this. I dont have a file manager on my system, just realized I deleted the useless stock one and had repalced it with Root Explorer and ES File Explorer. I have them on my External SD Card to install them again but withou a file manager or an app installer cant get to them. And I tried download an app installer from the Market and get Framework errors non-stop and downloads do not initialize... I think Im beyond a quick fix... how do I get my hands on a stock full ROM to restore everything... and how? What a nightmare... gotta tell you, I love Windows Mobile... I love it... never ran into anything like this in the past 5 years of using it... never...
Thanks again!
use "adb" in order to access to your tab from your desktop pc.
bartito said:
use "adb" in order to access to your tab from your desktop pc.
Click to expand...
Click to collapse
Cant. Dont even know if I need Kies installed or not (I did have it installed) but adb just asks me to connect the phone and thats it... its connected aready... this is desperating...
OK I did manage to connect with adb but, how to I install applications? I can navigate to my SD card where I have ES File Explorer and Root Explorer but dont seem to be able to install them... Also if i try to copy Stk.apk I get immediately an failute message... this is crazy...
OK so I managed to install ES File Explorer and Root Explorer with adb... crazy process. It seems my phone is still rooted after the reset. From the phone I copied Stk.apk back to /system/apps where it was before deleted.
But needless to say nothing got fixed... not sure if Stk.apk is now "actually" installed or just there in the folder. But still nothing works and crashes every 10 seconds... logs provider, dialer, phone, framework, contacts... its all a firework of crashes...
Given that you've hard reset your device already, you are pretty much wasting your time trying to "fix" what you broke by messing with /system, and you should really just flash another ROM.
My suggestion would be to follow the advice on this thread.
Regards,
Dave
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
VeEuzUKY said:
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
Click to expand...
Click to collapse
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
foxmeister said:
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
Click to expand...
Click to collapse
Yes Dave you are right, right and right again!!! Thank you for the wisdom and advice!!!
The main thing I have understood with today's messy experience was that the actual ROM files are never deleted or damaged as long as you dont access them via a rooted tool and start deleting them. Now I understand that Titanium Backup, Sprint Backup (my favorite), My Backup Pro and others, only back-up and restore what the user installs on top of the ROM itself. So a full "reset" wipes all that data but leaves the ROM files as they always were. If they got damaged in the process, they'll still be damaged till a a full ROM restores all system data, now I get it.
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Till I find an app or way to do a simple one-click "backup everything" and then "restore evertything" I always feel vulnerable to changes I make to the Tab that may get it unstable or corrupt and then not being able to be restored properly without a full ROM Flash and then re-installing all from scratch.
With WinMo, I could do all sorts of crazy experiments and tweaking and after that, a registry restore or back-up restore would bring me back my phone to exactly like it was with all my stuff and configuration in a matter of seconds or minutes. Thats what I need to find out with this Tab/Android and then Im ready to be able to explore messing up with this knowing I can always easily go back within minutes to the state I had before with all my apps and settings.
This is what I need to learn next how to do! Trampoline without a safety net is not a good idea. Ive alwways loved WinMo for the ease of backing up and restoring whatever I was doing on my handsets withjout ever worrying to put myself at risk to loose it all. I need to learn this on Android and its definitely more intricate!
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
instechgainza said:
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
VeEuzUKY said:
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
Click to expand...
Click to collapse
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
instechgainza said:
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Where is the modaco kernel section you refer to? I can search for hours and find zilch... these blogs are endless...
VeEuzUKY said:
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Click to expand...
Click to collapse
What you want is a Nandroid backup, which you can only make from a recovery image like Clockworkmod recovery.
Essentially, this does exactly what you want, but you need to flash a new kernel (e.g. the MoDaCo kernel) which supports Clockwordmod.
Regards,
Dave
bartito said:
deletion of Stk.apk causes FC's in phone and acore.
Click to expand...
Click to collapse
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
b0ricuaguerrero said:
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
Click to expand...
Click to collapse
When I delete stk.apk (for me useless useless useless) the first thing that happens immediately is that when I hang-up on a call made or received, the Tab vibrates then freezes for about 5 seconds then tells me the phone application has crashed. I tried this with 2 ROMs now as a test and its guaranteed. More even, if you use a program like SYSTEM APP REMOVER you can emulate the removal of an app by disabling it... it only takes me to disable STK and a reboot for the phone not to work. cant get rid of it, that simple
Hello Everyone,
So I unfroze all of my apps in Titanium Backup and flashed the OTA that is posted in the development forum for the Droid 3 and it seems to have worked great other than one small problem. Every time I try to use the camera or camcorder they will open for about 2-3 seconds and then they close and I end up back at my home screen. Does anyone have any ideas on what I can try to make my camera apps work again?
EDIT: Sorry, forgot to mention that I did try rebooting the phone as well as clearing the cache for the camera app, no change. Also Camera Zoom FX stays open but just has black where the camera image would normally be.
Thanks!
Maybe you... forgot to unfreeze the camera app lol.
No but id check what you do have frozen, maybe there's a service the camera app is dependent upon you might have accidentally frozen (assuming you rerooted after update)
Sent from my DROID3 using Tapatalk
I did re-root after applying the OTA update and then I froze about 15 apps that I found to be annoying/un-needed, however even after unfreezing all of them, any app involving the camera still isn't working. I also just noticed that my flashlight app that worked before the OTA is not working either.
First thing I would try is "clear data" for the Camera app and reboot.
rtbrjason said:
First thing I would try is "clear data" for the Camera app and reboot.
Click to expand...
Click to collapse
Tried that a couple of times but no change. I just also noticed that the camera app flashes a small message up at the bottom of the screen really quickly stating that the camera is unable to initialize.
Uninstall any third-party app that uses the camera (if you have any) the try again.
kishin14 said:
Uninstall any third-party app that uses the camera (if you have any) the try again.
Click to expand...
Click to collapse
Thank you for the suggestion, I hadn't thought of that. Unfortunately that did not work either. No change, still getting the same message for about a second or two and then it closes.
Try re-uploading the camera apk and odex files, might need to set permissions the same as the other system apps.
Unzip and use something like rootexplorer, delete current BlurCamera.apk and BlurCamera.odex, set write access on system/app folder then copy these.
-smc
The problem is the camera firmware, amongst other things, is first deleted and then replaced during the OTA update - if something happens, that firmware is never copied back causing the camera to fail.
The problem I had was too much stuff installed in /system and it simply ran out of space. This also caused my recovery to fail to update which then failed checksum if I tried to boot to recovery.
I had a bunch of binaries I installed in /system/xbin taking up several MB of space. I deleted them - including busybox - and reran the update. Now everything works fine.
If your recovery is hosed, I posted how to fix in the update thread.
If you need help and haven't wiped /cache yet, post /cache/recovery/last_log
limaxray said:
The problem is the camera firmware, amongst other things, is first deleted and then replaced during the OTA update - if something happens, that firmware is never copied back causing the camera to fail.
The problem I had was too much stuff installed in /system and it simply ran out of space. This also caused my recovery to fail to update which then failed checksum if I tried to boot to recovery.
I had a bunch of binaries I installed in /system/xbin taking up several MB of space. I deleted them - including busybox - and reran the update. Now everything works fine.
If your recovery is hosed, I posted how to fix in the update thread.
If you need help and haven't wiped /cache yet, post /cache/recovery/last_log
Click to expand...
Click to collapse
also, one note, i'm seeing alot of people reporting issues with the stock apps AFTER they've removed bloat (any method). the first thing people should do is put the bloat back, or in worse case scenario, do a wipe to see if there's really something wrong.
i froze an email service and it cause my text messenger to stop working. you don't know what libraries are shared with what. freeze with caution.
640k said:
also, one note, i'm seeing alot of people reporting issues with the stock apps AFTER they've removed bloat (any method). the first thing people should do is put the bloat back, or in worse case scenario, do a wipe to see if there's really something wrong.
i froze an email service and it cause my text messenger to stop working. you don't know what libraries are shared with what. freeze with caution.
Click to expand...
Click to collapse
I agree, and would suggest to anyone to use the script for removing and replacing the bloat - it makes it much easier to do (especially from adb when you foul it up) and keeps track of what you've done.
That said, I highly doubt that is the issue here. The update script first checksums everything that needs to be patched and deletes everything that is to be replaced. So if you have anything removed, it will either cause it to fail (if the file is to be patched) or not matter (if it is to be deleted or simply isn't touched). In other words, if you have anything missing that is needed, the update wouldn't touch anything.
Furthermore, I don't think any of the commonly removed bloatware serves as a dependency for the camera. At least not as far as I can tell.
I can tell you that /system is filled to the brim with all of the bloatware. The current ROM is just barely shoehorned in there. Many 'for-root-users' apps like to install stuff to /system and since the updater script doesn't check for free space, it may very well fail to extract in the middle of execution even though it already deleted a bunch of files.
So I think more importantly than restoring bloat, you should remove anything you added.
I tried your directions and re-ran the update after fixing recovery, however my camera still doesn't work because of the same basic issue, running out of space before the update completed. Upon re-rooting and going in to my system directory with root explorer I noticed that I now only have 195k free there. I checked the xbin folder and do not see busybox or anything else there that I recognize that I could delete to free up space. How can I tell what is safe to delete and what isn't so I can free up enough to fix my recovery again and hopefully get the update to work properly?
You can see a breakdown of disk usage with this command:
Code:
du -sh /system/*
Here's mine with busybox removed:
Code:
147.6M /system/app
7.5M /system/bin
11.0K /system/build.prop
5.5M /system/etc
5.1M /system/fonts
35.5M /system/framework
75.7M /system/lib
1.0K /system/lost+found
19.2M /system/media
0 /system/preinstall
304.0K /system/recovery-from-boot.p
4.6M /system/tts
8.3M /system/usr
135.0K /system/xbin
And my free space is
Code:
$ df /system
Filesystem Size Used Free Blksize
/system 320M 317M 2M 1024
Other than su, the only files you need in xbin are (don't worry about the symlinks)
Code:
backup dexdump drm1_func_test run_backup run_restore ssmgrd
I think the only extra bits I now have on /system is su.
I also found the system dump from this post to be very helpful.
Whenever I'm trying du It's saying that the command wasn't found. What are you using for your terminal access?
Hmm it seems du isn't a standard binary even though I have it in bin. I sure don't remember putting that in there...
Anyway, I use adb or Better Terminal Emulator Pro, depending what mood on in.
To use adb, you'll need to install busybox to /data somewhere (I have mine in /data/local/bin) and use
Code:
$ /data/local/bin/busybox du -sh /system/*
BTEP has a fairly complete set of CLI tools included - such as du - so you don't need busybox.
I figured out how to do the command through busybox and have come up with some interesting results...
I am over yours on...
Code:
153.8M /system/app
1.9M /system/xbin
I am under yours on...
Code:
4.7M /system/bin
4.9M /system/etc
71.8M /system/lib
And I match yours on...
Code:
11.0K /system/build.prop
5.1M /system/fonts
35.5M /system/framework
1.0K /system/lost+found
19.2M /system/media
0 /system/preinstall
304.0K /system/recovery-from-boot.p
4.6M /system/tts
8.3M /system/usr
This is with busybox installed in the xbin folder so that is probably why I am over on that one, however the app folder is quite a bit over as well but I can't figure out why. The only file that I can find in there that doesn't seem to belong is Superuser.apk but it is only 191k.
UPDATE: I finally found a large app that wasn't present in the system dump that you had mentioned before. I backed it up to my sd card and removed it, went through the update, and now my camera is working. Thank you very much to everyone who helped, especially limaxray!
Glad I was able to help!
This is a great example for why we should always wipe data/cache before any rom update.
dsw361 said:
This is a great example for why we should always wipe data/cache before any rom update.
Click to expand...
Click to collapse
That wouldn't have helped here at all. If anything, it would have made it impossible to use adb in case of a boot loop.
These are not like community ROM updates and don't need anything wiped.
limaxray said:
That wouldn't have helped here at all. If anything, it would have made it impossible to use adb in case of a boot loop.
These are not like community ROM updates and don't need anything wiped.
Click to expand...
Click to collapse
Exactly. the last thing I would do is wipe data/cache if we encountered a bootloop. Adb is so important to us right now because we don't have a custom recovery or an sbf.
Sent from my DROID3 using Tapatalk
Hi everyone
I'm trying to get the infamous GPS Location Spoofer installed as a system app on my rooted HTC phone, but so far no luck, so I figured I would try to ask for help here, in case anyone went through a similar situation, or knows what I've been doing wrong. This is what I tried so far:
Installed the app from Google App store, and using File Explorer with root , tried to move the app folder to /system/app or /system/priv-app, , but pasting the folder there would result in an instant reboot and the app would not be there.
So I installed lucky patcher , and using apk downloader, downloaded the apk file from the App Store, copied it over to the phone, and used the "Rebuild and Install" option, choosing the option to install it as a system app , and it would process it and say that the installation was sucessfull, needs to reboot to complete, but after the reboot the app would not be there (not only not showing on the apps list, but navigating to the /system folder with File Explorer and checking app and priv-app I could verify that it was not installed).
SO I tried to use adb shell to do the work , and this is what I did:
mount -o remount /dev/block/mmcblk0p35 /system
to mount the /system filesystem as read write , and it did
cp /sdcard/Download/com.incorporateapps.fakegps.fre-55.apk /system/app
to copy the file under /system/app
chmod 644 com.incorporateapps.fakegps.fre-55.apk
to set the permissions as required
and reboot the phone, but after the reboot, the file would not be there. I tried also to create a folder under /system/app named com.incorporateapps.fakegps.fre-55, move the apk inside; installing normally , changing the mount point to read-write and moving it from /data/app to /system/app or /system/priv-app using the shell and chaning ownership / permissions , but the app will not stick , either rebooting or just re-mounting the filesystem as read-only again will cause everything that was done to be lost; and after trying any of the above one time, doing it for a second time would cause the phone to reboot.
I figure that there must be an image of the /system mount point somewhere , which gets installed every time there is a remount to read-only or reboot , or something of that nature, that will cause any changes made under /system to be lost. Maybe I'm wrong but it seems to be related to HTC phones, since there's load of people doing it on other models without issues, or maybe I'm doing something wrong, since I'm no android expert
Does anyone knows what could be the issue, or what can I do ? I searched the net quite a bit for a solution to no avail (here as well), any help is appreciated
Thanks
sasteck said:
Hi everyone
I'm trying to get the infamous GPS Location Spoofer installed as a system app on my rooted HTC phone, but so far no luck, so I figured I would try to ask for help here, in case anyone went through a similar situation, or knows what I've been doing wrong. This is what I tried so far:
Installed the app from Google App store, and using File Explorer with root , tried to move the app folder to /system/app or /system/priv-app, , but pasting the folder there would result in an instant reboot and the app would not be there.
So I installed lucky patcher , and using apk downloader, downloaded the apk file from the App Store, copied it over to the phone, and used the "Rebuild and Install" option, choosing the option to install it as a system app , and it would process it and say that the installation was sucessfull, needs to reboot to complete, but after the reboot the app would not be there (not only not showing on the apps list, but navigating to the /system folder with File Explorer and checking app and priv-app I could verify that it was not installed).
SO I tried to use adb shell to do the work , and this is what I did:
mount -o remount /dev/block/mmcblk0p35 /system
to mount the /system filesystem as read write , and it did
cp /sdcard/Download/com.incorporateapps.fakegps.fre-55.apk /system/app
to copy the file under /system/app
chmod 644 com.incorporateapps.fakegps.fre-55.apk
to set the permissions as required
and reboot the phone, but after the reboot, the file would not be there. I tried also to create a folder under /system/app named com.incorporateapps.fakegps.fre-55, move the apk inside; installing normally , changing the mount point to read-write and moving it from /data/app to /system/app or /system/priv-app using the shell and chaning ownership / permissions , but the app will not stick , either rebooting or just re-mounting the filesystem as read-only again will cause everything that was done to be lost; and after trying any of the above one time, doing it for a second time would cause the phone to reboot.
I figure that there must be an image of the /system mount point somewhere , which gets installed every time there is a remount to read-only or reboot , or something of that nature, that will cause any changes made under /system to be lost. Maybe I'm wrong but it seems to be related to HTC phones, since there's load of people doing it on other models without issues, or maybe I'm doing something wrong, since I'm no android expert
Does anyone knows what could be the issue, or what can I do ? I searched the net quite a bit for a solution to no avail (here as well), any help is appreciated
Thanks
Click to expand...
Click to collapse
Are you using stock kernel?
donkeykong1 said:
Are you using stock kernel?
Click to expand...
Click to collapse
Yes, kernel is the default that comes with the phone (3.4.10.g96cae32 , android 5.0.2)
sasteck said:
Yes, kernel is the default that comes with the phone (3.4.10.g96cae32 , android 5.0.2)
Click to expand...
Click to collapse
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
donkeykong1 said:
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
Click to expand...
Click to collapse
oh I see.. didn't know about that , thanks! I'll check about disabling system write protection , otherwise look for a custom kernel, never did it before but will give it a try
donkeykong1 said:
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
Click to expand...
Click to collapse
Shhhhhh, don't help him, he's going to steal everyone's pokemons
Sent from my HTC One using XDA Labs
alray said:
Shhhhhh, don't help him, he's going to steal everyone's pokemons
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Ooooohhh... That's why he's trying the spoofer.... If I knew, I wouldn't help at all [emoji6]
donkeykong1 said:
Ooooohhh... That's why he's trying the spoofer.... If I knew, I wouldn't help at all [emoji6]
Click to expand...
Click to collapse
Sorry you feel that way, but I appreciate the help anyway. This is something that I never tampered with before, so I still had some doubts about the process, but I am liking the whole thing and will install a custom rom on my own phone, been reading about the Ressurection rom and it looks very nice, will try it as soon as I'm better informed
sasteck said:
Sorry you feel that way, but I appreciate the help anyway. This is something that I never tampered with before, so I still had some doubts about the process, but I am liking the whole thing and will install a custom rom on my own phone, been reading about the Ressurection rom and it looks very nice, will try it as soon as I'm better informed
Click to expand...
Click to collapse
That was a joke mate. I don't care what you do with your phone, but I'm here to help if I can [emoji6]