No expert by any means but im really having a hard time wrapping my head around this one. My phone (Blu Life One x2) is rooted (as you can see in the video), i can make changes to it as rooting an android would allude to, but whenever i make a change to system based file, folder permission anything at the root the phone just hard stops and i have to do a hard reboot. I'd love to know whats going on here.
Im trying to follow a tutorial to make my phone ring louder in the video. I get to the media xml, try to change a permission and poof! It also happens if i just open the file and try to edit it. Once i save it, phone does the same thing. No changes committed. Video is a onedrive video. If it gets wonky i'll upload to youtube.
h ttps://1drv.ms/v/s!AlQ2y7AA9o6DjJYlZnmjDFT_zMerJA
anyone have any ideas?
Related
So we all know that for some reason the youtube app doesnt open after a login, we also know that a simple delete of the youtube.xml in shared preferences lets us once again use youtube...(/data/data/com.google.android.youtube/shared_prefs)
I had a been working on a little script to delete that file every time I closed youtube but realized this would get repetitive. I am wondering is this a B&N problem with the way permissions work and where information is stored...similiar to the inability to run shortcuts. Even if you go in and delete from the .xml file your username information or even delete everything in the file but dont delete the physical file, after trying to open youtube it will once again reset. I have been frustrated by this numerous times...where is that data being stored? Does anyone know...
I can't help other than bumping this, but being able to favorite videos is a big part of my youtube experience and I also find this annoying.
On an unrelated note side loading honeycomb youtube apk is wonderful.
Here is where I fail. I have managed to delve further into the youtube.xml file and figure out what exactly is seeming to cause the problem with permission, but I cannot repackage the apk after editing...because I cant sign it. Any thoughts on a solution to this...also it is possible to extract edit then repackage an apk on the nook itself?
Check out this tool. It handles re-signing the APKs.
http://forum.xda-developers.com/showpost.php?p=6703735&postcount=1
I actually came across that tool about 20 minutes before you replied, as an update. I now have youtube where it will allow me to sign in (I do a full quit using task killer) and then restart it with no problems. The problem occurs when I shut down my nook and bring it back...on some shutdowns it just makes me sign in again, others it does the normal process where it does not open up. I dont understand where this thing is storing my permissions or login data, I have erased and looked at most every bit of code that could have anything to do with data storage...maybe it calls some process built in to the nook that I'm missing.
Oh wow...finally got this running on the stook root. I'm having a few friends test it out to make sure I'm not breaking permissions for other things...I'll send out the apk or explain the steps momentarily.
Awesome! Can't wait to try it out. Is this for Froyo or for Nook rooted?
Just for rooted 1.1 though I see no reason it wouldnt work on rooted 1.01 or 1.00...though I'm running into problems. It seems that I wont be able to release an update to the apk but instead will need to include instructions on how to update your own apk which will automatically make it less doable.
Hey guys. as many of you know i am no stranger to the Android system, although i have been pretty much totally absent from the forums since i got a job with limited privelages on my comp.
Before I explain what happened to me, i should say that i have not made ANY changes to my system for at least 4 months, with the exception of build.prop updates, which i my phone has been running fine on for weeks. i found a setup i liked and ive been running it, along with the same root applications, for quite some time.
With that said, heres my timeline of events:
Normal day, doing what i always do on my phone everyday: phone was plugged in to a wall outlet at my desk. streaming music, browsing web, youtube, etc. nothing out of the ordinary
i first noticed something wierd was up when i went to install an old .apk i had saved on my sd card. i opened it through file manager which, naturally, brought up the stock package installer. i clicked ok to install, and it said "installing"..however it nevver finished. it was stuck on "installing" for several minutes. i tried a couple more times, same thing kept happening. i had no idea what was going on.
i went into settings>applications>manage applications. i scrolled down to package installer and clicked on it, with the intention of clearing cache/data, however the values never loaded, it just kept saying "computing". it was doing that for all other apps i checked as well.
then i opened titanium backup and wiped data for package installer through that. operation was performed successfully.
i went to reboot my phone, and thats the last thing it remembers. now whenever i try to turn my phone on, it gets past the kernel splash screen and its all black from there (i have the "no boot anamiation" command in my build.prop). the only response i get at that point is the led buttons will light up if i tap them. i have to pull the battery to turn the phone off/reboot.
i tried pushing packageinstaller.apk to /system/app using adb but that didnt solved anything. i also tried wiping cache/dalvik and fixing permissions through clockwork. nothing has worked.
i am running Froyo Trigger w/ Bali kernel.
sorry for the long post, but i figured id be as detailed as possible to minimize questions.
any suggestions would be great. i ask that no one please suggest factory reset/reflash/odin. i realize that those options are there, but i consider them last resorts. id rather brainstorm a solution than bail immediately.
thanks ahead.
also i forgot to mention, there was nothing wrong with the .apk i was originally trying to install. i have installed it/uninstalled it many times. i tested other .apk files i had, but package installer still behaved the same way
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Br1cK'd said:
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Click to expand...
Click to collapse
not sure if i should be embarrassed to admit this, but ive never used logcat...ill look into that
Your first step there is to get the android sdk setup on your pc, then once adb is part of your command line the simple command is "adb logcat" without it quotes. That will start the log displaying in the command line window.
There are other options with the logcat command, that output the log to a text document and its more in depth, but I dont remember it off the top of my head. Maybe someone can post it for you.
The only caveat is how far your phone is booting before it hangs, I think logcat will show something, but won't know for sure until you try it.
Sent from my ZenDroid, meditating on the XDA App
http://forum.xda-developers.com/showthread.php?t=1319802
Eugenes Froyo that doesn't brick, followed by an Odin to jfd.
Sent from my SGH-T959V using XDA App
I want to start off with a pre-apology for not keeping up on this Android / Smartphone stuff.
Here's the deal:
Never really used my Droid X2 much until it started acting weird after I let a "friend" use it. I find out a little later, Said "friend" used my roommate's computer to help him "cleanup" his files and help secure the wifi. After realizing what might have happened I checked out the roomies PC. I have no idea what he did specifically, but now im trying to download device drivers, look at files through an explorer, etc. and I can't do any administration stuff. I tried using my restriction lock for outgoing calls cuz Skype is goin NUTZ now but I dunno if its actually working when I see the "calls disable" prompt pop up randomly like someones trying to use the line. I have all these program package installer apps running in the background as well as Motorola service apps that I've never downloaded myself.
After research I think he setup his own driver while using my phone and my roomies comp (i honestly was asleep & I trusted chillin wit the kidso I'm sure he saw my unlock code... TOTAL mistake) that has something to do with android SDK and writing code for it and then continuing his "project" (my Droid x2) remote from wherever he was after while somehow maintaining a good network connection either through my Droid or my roomies wifi, which I used everytime I'm home cuz it saved data.
I've learned, or read, a lot... but I don't understand the basics or the foundations here. And everytime I try to follow a step by step process, I'm somehow not permission denied
Plz help
Sent from my DROID X2
I'm not really clear on the issue. But if your friend messed something up on your phone and now you cant do anything on it, I would use this link:
http://forum.xda-developers.com/showthread.php?t=1317707
Basically, you need to do a full factory reset on your phone. Thats the best I can do without knowing what exactly is wrong with your phone.
Im also not sure what your getting at but sbf and a factory reset will set anything back to right. And also most of that stuff you were talking about is part of the phone to begin with.
Rolling AOKP in the north.
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
alljokingaside said:
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
Click to expand...
Click to collapse
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Mevordel said:
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Click to expand...
Click to collapse
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
alljokingaside said:
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
Click to expand...
Click to collapse
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Mevordel said:
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Click to expand...
Click to collapse
No clue. what do you mean by "reboot cleanly"? if by that you mean, did I reboot using the reboot option in the power menu, then yes. always.
After restoring a backup and re-editing build.prop, sleep worked like gamebusters. Except, bluetooth auto-toggled on ("bluetooth is turning on"). After rebooting, it was stuck on the boot animation screen for a few minutes. A reboot after that pretty much boot looped it. I restored my backup afterwards...
Looking in the logcat (after editing), I noticed a ton of errors and permission denials.... Since I don't have much expertise here, I can't say for sure that they're normal but they seem to be abnormal. Wayyy more than I remember seeing when I browsed through before on a "clean" boot. But again, with the lack of expertise (or any functional knowledge for that matter)
==
Now, after having restored the backup before making the edits and rebooting, it seems to be stuck in a bootloop....huh. ok, after rebooting it 2x, it finally seems to have booted up "normally." Both before restoring (w/ edits and BT error) and after restoring (w/o build.prop edits), it's taking a lot longer to boot up than it used to....guesstimating 3-4 minutes. When it boots up, I get/got: "process system isn't responding" (both before and after restores now) and something about alarm error.
I've attached logcats of both pre- and post-event, if you're curious. As to "solving" this,I'm just gonna re-flash the PA ROM and wipe caches to get rid of these problems. ergh. device meets my foot against the wall is next on the checklist.
thanks again. I'd like to say, Stay classy, San Diego, but we all know San Diego and its class
Hey folks,
OK, I'm just a little bit out of my depth here, so here it goes!
This probably sounds dodgy, but it is what it is: my daughter's phone (rooted HTC Desire 816) appears to have been "hacked" by someone at her school - whether its a prank gone wrong or she's a victim of bullying, we don't know and now we're dealing with the fallout.
By hacked what I mean is that the person or persons have somehow managed to find out my daughter's PIN and have then used it to gain access to her phone. Once in, they have turned off the custom lock screen installed (Hi Locker) and turned on the default lock screen and set a PIN which we don't know. Obviously, we're trying to get back into it without wiping it and don't know how to except for trying all 10,000 combinations!
So yeah, does anyone know how I might be able to go about getting back into the phone quicker than trying all 10,000 combos of PINs!?
Like I said, it is a rooted device; I was the one who initially set the phone up for my daughter. So its running TWRP and through TWRP I've been able to do an 'ADB Pull' request and dump the contents of external_sd and sdcard to my laptop so that at least that much data is preserved. I've also backed up the mmssms.db so that hopefully I can restore these databases if needs be. My daughter would like to not have to wipe the phone as she can't remember what other data (if any) might be lost if we do and I said I would try all other avenues before it gets to that.
Anyhow, I thought I would reach out to the community to find out if there is some way that I might be able to disable the lock screen or at least initiate some sort of backup process from the lock screen that would enable us to reset the lock screen. If not: such is life. But, if there is something that could be done, well, that would just be absolutely fantastic.
Thanks in advance folks for your responses and time.
Kind regard,
Dodgy Bob.
Hi folks,
After a bunch of further digging through random blogs and YouTube videos and whatever else, I happened across this site which pointed out a couple of different tricks that hadn't popped up on other sites I had come across. These were:
Safe Mode Option; and
adb shell rm /data/system/gesture.key
Safe Mode Option didn't work for me, because it wasn't the 3rd party lock screen app that was the issue.
However, the gesture.key option did work for me, albeit with a couple of tweaks! Gesture.key wasn't present because the phone is running a newer version of Android, v6.0 (I had forgotten this!), so I had 2 gatekeeper files and 3 db files -and- rather than deleting them, I added .orig to the file names. Once I had done this, I rebooted back into System from Recovery and ta-da, I was back into the phone!
Big thanks to @Helloworld294 for this post here which I found after searching more due to reading this page.
It's all worked out in the end.
Kind regards,
Dodgy Bob