Related
I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootloop?
EDIT: N/m... thought it was the app, looking closer at adb logcat, looks like it isn't... and I found a way to delete the app but the issue remains.
Going to switch ROMs, the one I'm using now is fast, but appears to be way too buggy.
lotherius said:
I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootlopp?
Click to expand...
Click to collapse
omgggggggggg
http://forum.xda-developers.com/showthread.php?p=4529707
if you have apps2sd
Code:
adb remount
adb shell
rm /system/sd/app/xxxx.apk (or if that doesn't work put -r after rm)
if you dont have apps to sd, i believe apps are in /data/app
B-man007 said:
omgggggggggg
http://forum.xda-developers.com/showthread.php?p=4529707
if you have apps2sd
Code:
adb remount
adb shell
rm /system/sd/app/xxxx.apk (or if that doesn't work put -r after rm)
if you dont have apps to sd, i believe apps are in /data/app
Click to expand...
Click to collapse
i think my crappy typed-at-work commands have been quoted lol. I need to start a whole series of typed at work commands.
Also @lotherius what rom were you using?
Enomther's Rogers. May not have been the ROM but I am a bit frustrated as I have had several problems with it, and just went back to Cyanogen 4.0.4 for now. Thanks for the info.
Hi lotherius,
I'm in the same situation; How did you delete the app within the recovery? I have a Cyanogenmod 10.1 (android 4.2.2) based custom ROM with TWRP recovery right now.
Thanks in advanced!
lotherius said:
I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootloop?
EDIT: N/m... thought it was the app, looking closer at adb logcat, looks like it isn't... and I found a way to delete the app but the issue remains.
Going to switch ROMs, the one I'm using now is fast, but appears to be way too buggy.
Click to expand...
Click to collapse
adb uninstall badapp.apk
Or if this won't work try
adb shell
adb rm /data/app/badapp.apk
Or system app or wherever it is (may be able to just delete the data of the app too
Sent from my Nexus 4 using xda premium
Wow, thread necromancy
I'm just a guy, not a techophobe so I have no idea how to get to the shell inorder to type those commands. My daughter's Macbook Pro just endlessly restarts itself unless I put it in Recovery mode or Safe mode. I suspect it is 3rd party apps causing this, but I can't delete apps from Rec. or Safe mode and no one here has put it in layman's terms.
Ever since I switched from JF 1.51 to rooted TMO 1.6, my SU app has been broken. It just hangs while staying black and eventually force closes. As you can imagine, this is a big hassle because I can't give any apps permission.
Does anyone have a solution? Thanks.
hettbeans said:
Ever since I switched from JF 1.51 to rooted TMO 1.6, my SU app has been broken. It just hangs while staying black and eventually force closes. As you can imagine, this is a big hassle because I can't give any apps permission.
Does anyone have a solution? Thanks.
Click to expand...
Click to collapse
Are you sure you didn't load the wrong rom and you lost root?
supremeteam256 said:
Are you sure you didn't load the wrong rom and you lost root?
Click to expand...
Click to collapse
Uhh, yeah. I have root, all the apps id already given permission to still work. Its new ones that do not.
Have you tried to push su back or run enable superuser to see if that will help?
supremeteam256 said:
Have you tried to push su back or run enable superuser to see if that will help?
Click to expand...
Click to collapse
I don't know what either of those means. If you could provide some instructions (terminal commands, etc) that would be great.
Thanks in advance.
Try this first.
Code:
turn on your phone by holding the home+end(power) key
press alt+x to enter the recovery console and then press enter when it asks you
next type:
mount data
rm /data/data/com.koushikdutta.superuser/databases/superuser.sqlite
if you have the problem where it says this file does not exist, type:
rm /data/data/koushikdutta.superuser/databases/superuser.sqlite
Alright, I will try that in a little while when I am at a computer. Thanks
hettbeans said:
Alright, I will try that in a little while when I am at a computer. Thanks
Click to expand...
Click to collapse
Also in the mean time you can try the superuser whitelist in the market to see if that will work.
Hey, formatting my SD card seems to have fixed it, but thanks for the help.
no problem
First off, I am not sure if I am posting this in the correct forum or not. If it is the wrong forum, I do apologies.
Now on to the problem...
I have a T-Mobile G1 running on Rogers (currently running CyanogenMod-4.0.1 with Firmware version 1.5). The problem I am having is that my G1 got soaked a while ago and the Send/Call and Home buttons no longer work whatsoever. I have mapped my send/call button to the camera button, so I can still answer calls. However, I am unable to install any new ROMS (updates) through any of the current bootloaders since they all require you to confirm the install/update with the send/call button.
I have now since been informed by Rogers that since I am running 1.5, my data will be cut off if I do not update to 1.6. Normally this would be no problem, but since my send/call and home buttons do not work, I am unable to do this (I know how to boot into recovery using terminal I just am unable to confirm anything once there).
I was wondering if anyone out there is able to make a new recovery or customize either Cyanogen's or Amon_RA's recovery so that I can confirm a installation/update by using either the Menu, trackball, back, End, or camera button INSTEAD of the Send/Call button?
Any help would be GREATLY appreciated.
Thanks,
Thomas
definetly the wrong section
if you have the relevant .img files you can flash through adb (in theory, never done it for a full rom, just boot.img and recovery.img)
adb flash_image boot /sdcard/boot.img
for example
or get the source to the recovery images and try and edit it manually
or....suck up amon_ras ass and try and get him to make you one
good luck
you might want to think about buying a junker off of ebay for spare parts tho...
Dude go on the Market. Download Quickboot.
It lets you reboot into recovery and more.
Then you can do everything like before
if its possible to install ROM's through the Recovery Screen Console then do it that way. idk how just a suggestion.
the problem is that he needs to hit home to confirm - which he cant
wrong section. But they are just checking the build.prop so make another one and adb push it that will tell them your running 1.6
but also get your phone fix when your phone goes into water you gotta take it apart right away and use a blow dryer
garok89 said:
the problem is that he needs to hit home to confirm - which he cant
Click to expand...
Click to collapse
is there a way to flash a ROM via Recovery Console though? jc
and hmm maybe you should just wait until your fone is fully dried. Thats happened to me with my old fones where they get wet and some didnt even turn back on until they fully dried.
how long ago was this?
The phone is fully dried... this happened in the summer (couple of months ago). It was in my backpack while biking home, got caught in a sudden down pour. When I got home, I found my phone in a pool of water on the home screen fully frozen. I took out the battery right away (this was about 30min later after I got caught in the down pour) and put the phone in some rice for 24hours. I then let it air dry some more under some fans for another 24hours. Sadly, I think water got into the circuit board through the SD slot and fried those 2 connections (the send and home buttons).
How do I pull the build.prop from my phone and then push it back? That should fix the problem, but it would still be nice to have the option to install other ROMS or even have the ability to wipe my phone.
szuba said:
The phone is fully dried... this happened in the summer (couple of months ago). It was in my backpack while biking home, got caught in a sudden down pour. When I got home, I found my phone in a pool of water on the home screen fully frozen. I took out the battery right away (this was about 30min later after I got caught in the down pour) and put the phone in some rice for 24hours. I then let it air dry some more under some fans for another 24hours. Sadly, I think water got into the circuit board through the SD slot and fried those 2 connections (the send and home buttons).
How do I pull the build.prop from my phone and then push it back? That should fix the problem, but it would still be nice to have the option to install other ROMS or even have the ability to wipe my phone.
Click to expand...
Click to collapse
You put it in rice? hmm never would have thought of that one lol
to pull and push respectively:
Code:
adb pull /system/build.prop \<the location that you want to put it in>
adb push \<the location that you put build.prop in> /system/
i usually just copy it to the android-sdk-windows\tools directory on my computer because its easier to get to it.
Macrophage001 said:
You put it in rice? hmm never would have thought of that one lol
to pull and push respectively:
Code:
adb pull /system/build.prop \<the location that you want to put it in>
adb push \<the location that you put build.prop in> /system/
i usually just copy it to the android-sdk-windows\tools directory on my computer because its easier to get to it.
Click to expand...
Click to collapse
Done, but when I try to push the file back, I get the follow error;
Code:
adb push desktop/build.prop /system
failed to copy 'desktop/build.prop' to '/system/build.prop': Read-only file system
szuba said:
Done, but when I try to push the file back, I get the follow error;
Code:
adb push desktop/build.prop /system
failed to copy 'desktop/build.prop' to '/system/build.prop': Read-only file system
Click to expand...
Click to collapse
Sorry forgot to tell you to type in:
adb remount
before you do it.
so do this:
Code:
adb remount
adb push desktop/build.prop /system
should work. just tried and it did for me.
Thanks Macrophage001... I edited and the pushed the build.prop successfully. Here is how my build.prop now looks;
Code:
# begin build properties
ro.build.version.release=1.6
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=F1_New_SMS.ogg
ro.com.google.locationfeatures=1
ro.com.android.wifi-watchlist=GoogleGuest
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.com.google.clientidbase=android-tmobile
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
keyguard.no_require_sim=true
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Google's checkin service. I don't like it, but it's required for the SetupWizard -cm
#ro.config.nocheckin=1
ro.modversion=CyanogenMod-4.0.1
When I go into Menu, Settings, About Phone it still shows my Firmware as 1.5, is that ok?
szuba said:
Thanks Macrophage001... I edited and the pushed the build.prop successfully. Here is how my build.prop now looks;
Code:
# begin build properties
ro.build.version.release=1.6
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=F1_New_SMS.ogg
ro.com.google.locationfeatures=1
ro.com.android.wifi-watchlist=GoogleGuest
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.com.google.clientidbase=android-tmobile
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
keyguard.no_require_sim=true
ro.config.sync=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# Google's checkin service. I don't like it, but it's required for the SetupWizard -cm
#ro.config.nocheckin=1
ro.modversion=CyanogenMod-4.0.1
When I go into Menu, Settings, About Phone it still shows my Firmware as 1.5, is that ok?
Click to expand...
Click to collapse
Its most likely because you are running an old version of Cyanogen. If that's the case then yeah your ok
Glad to be of Help
old school recoveries...
I dont think you have to press home in JF recovery or the first cyan recovery... just the trackball but i dont remember, its been so long... search for those recoveries and try them out... you gotta name the file update.zip to flash... it cant hurt right?
junkdruggler said:
I dont think you have to press home in JF recovery or the first cyan recovery... just the trackball but i dont remember, its been so long... search for those recoveries and try them out... you gotta name the file update.zip to flash... it cant hurt right?
Click to expand...
Click to collapse
I thought it was the Call button? but yeah I cant remember anymore either =/
@szuba
if everything's working now, you should totally get the latest ROM from Cyanogen lol or Super D or whichever you want....just you know...Get a more recent ROM lol
Macrophage001 said:
I thought it was the Call button? but yeah I cant remember anymore either =/
@szuba
if everything's working now, you should totally get the latest ROM from Cyanogen lol or Super D or whichever you want....just you know...Get a more recent ROM lol
Click to expand...
Click to collapse
I would LOVE a more recent ROM, however I still have not found a work around to install a ROM without using the Send/Call key to confirm the install...
I will try to find JF's or Cyanogen's previous recovery and maybe that will let me.
szuba said:
I would LOVE a more recent ROM, however I still have not found a work around to install a ROM without using the Send/Call key to confirm the install...
I will try to find JF's or Cyanogen's previous recovery and maybe that will let me.
Click to expand...
Click to collapse
ok well hope you find a way good luck =)
Found JF's original recovery, downloaded Super D's latest ROM and renamed it to update.zip, rebooted into recovery, hit Alt-S and what do you know... WORKED LIKE A CHARM!!!
Thanks a lot guys, it is greatly appreciated!
Great and np.
beautiful... Glad I could help... I made a 1.o theme a while back.. that would be cool to have with JF's original Recovery..
mad props to JF and Cyangen for such great work...
So I flashed SuperD yesterday, and all is cool. Its not my first time using roms, and everything went smooth.
But then today I wanted to change the keyboard layout back to the German layout. So I went to Terminal Emulator and began to edit the layout using this method (tested, working from these forums)
su
mount -o rw,remount /system
cp /sdcard/trout-keypad-v3.kcm.bin /system/usr/keychars
Anyway, once I finished, it said that this operation isnt possible. Then I realized that I forgot to put the file on sd card. So I added the file, but then the strange part came....
I then again went into terminal emulator and typed "su" to start the process again but now im getting the "permission denied error! 5 min ago I didnt have this error and could mount just fine! The phone is running fine, but it seems like I ve lost root.
Do I need to reflash the rom or the spl to reverse this? I really just need access to Terminal again. Anyone know how to fix this? I tried rebooting just to see if it was some type of bug, but even after reboot Im still getting permission denied.
Could really use some help on this!
Use adb shell. Try clearing the saved options in the SU application. Try a different terminal program. Lastly, try to just reflash the rom.
evilkorn said:
Use adb shell. Try clearing the saved options in the SU application. Try a different terminal program. Lastly, try to just reflash the rom.
Click to expand...
Click to collapse
I installed a new Terminal, and it seems to work fine. Might seem like a dumb question, but Im really not sure if I have root or not?!
If it worked what's the question?
evilkorn said:
If it worked what's the question?
Click to expand...
Click to collapse
Your right. Was a dumb question. It just confused me, as one terminal is giving me access, and another wont. Guess its just a bug.
Anyway, I reflashed the rom, and all is perfect. Thanks for the help though guys.
I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...
Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.
z4root will work and install superuser for you.
mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.
Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.
axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!