I just got an OTA update on my a100. I was a bit wary about taking an update, since I could find no information on it on the web, but I figured someone has to take a risk. The device downloaded 2.001.01 and installed it and my system went from Kernal 2.6.36.3 to 2.6.36.3+ and from build number Acer_A100_1.012.05_COM_GEN2 to Acer_a100_2.001.01_COM_GEN2
Other than that, I've noticed no changes, but I did not loose root, which was my main concern.
If this should be in the development section, let me know.
If anyone knows what changes were made in this update, or where I can get more information about it, I'd like to hear about it.
Thanks
I'm pulling it down now, thanks for letting me know I keep root. I was worried about that as well.
Sent from my A100 using XDA Premium App
I hope I catch you in time, but I'm now not sure I kept root. Superuser app came up just fine, but now titanium backup is saying it can't get root. I'll have to investigate further, but it looks like I was wrong before and now I need to see if I can reroot. did iconiaroot ever get updated for a100?
please tell me if it fixed the headphone issue.
Please tell me what the headphone issue is. Then I'll see what I can do.
if you are using the headphones and acer sync starts sound comes from both the headphones and the speakers
I don't use acer sync, so I can't really test that. I'm a bit more concerned about getting root back at the moment, but I might be able to check for you tomorrow, if no one gets to it in the meantime. Good luck.
You guys located in the US? Mine keep saying system up-to-date
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Well, crap, root is gone. I'll try to redo it tomorrow, too sleepy to type right. It also reset my sweet boot animation.
Sent from my A100 using XDA Premium App
wicced247 said:
You guys located in the US? Mine keep saying system up-to-date
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Click to expand...
Click to collapse
Indeed I am in the US. Like the other guy, no Idea what it actually did besides kill root and change my boot animation.
Sent from my A100 using XDA Premium App
yes fl they control it by region in the states i believe. so as not to pull an apple fail
wicced247 said:
You guys located in the US? Mine keep saying system up-to-date
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Click to expand...
Click to collapse
Yeah, California here.
reverendbill said:
Well, crap, root is gone. I'll try to redo it tomorrow, too sleepy to type right. It also reset my sweet boot animation.
Sent from my A100 using XDA Premium App
Click to expand...
Click to collapse
Sorry I jumped the gun on the root call, I really thought superuser would have displayed some kind of error if I'd lost root, but I forgot to check Titanium. I've tried iconiaroot 1.3 and it didn't work, so i'm going to try the adb method. If that doesn't work, I'll just have to wait till someone who knows more about this stuff than me can make some progress.
HA! I fixed it!
I used a terminal emulater to run the root commands, THEN I ran iconiaroot 1.3 (which I assume just installed superuser.apk, since it wasn't able to get su on its own) and I'm rooted once again. I need to update superuser, busybox, reinstall adblock, and get rid of the bloat again, but then I'll be back to normal.
Here's the commands for the emulator btw, I got them from the "how to root" thread. If they don't work for you, try doing it the ADB way. (the best way is to open this page on your tablet,and cut and paste the lines (without the outside quotation marks) into the terminal emulator.)
"/system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`' "
"/system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`' "
"/system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`' "
Edit: BTW I can't tell if it came with the update, or if it self-updated, but I now have a new version of android market which doesn't force you into landscape mode. That always annoyed me.
mine is showing no update either showing kernel 2.6.36.3
max69power said:
mine is showing no update either showing kernel 2.6.36.3
Click to expand...
Click to collapse
So I'm not the only one not getting the update... I wonder why
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Sorry guys, if I'd thought about it before I updated, I would have saved the update file to share with you. It didn't occur to me that some people wouldn't get it right away.
I don't see the update.zip in my sdcard, is there anywhere else they might have left a copy or is it gone after a successful update?
Looks like the issue with sound playing through speakers despite headphones being plugged in was finally addressed, thank god.
skitzles said:
Looks like the issue with sound playing through speakers despite headphones being plugged in was finally addressed, thank god.
Click to expand...
Click to collapse
Woot! This is amazing. This was the only bug that was driving me nuts. Anytime that you plug in headphones before starting music/videos, it would play out of both. I am so happy this has been fixed.
I wonder why I haven't been prompted for the update yet.
I'd imagine it has something to do with them avoiding an "apple fail" as someone stated earlier. Probably rolling out the update to a select region to make sure their is no catastrophic behavior, or bogging down their servers. When I updated to IOS5 they didn't accomidate for the flood of people they received and I had a hard bricked device for just over 12 hours. SOFUN.
skitzles said:
Looks like the issue with sound playing through speakers despite headphones being plugged in was finally addressed, thank god.
Click to expand...
Click to collapse
Nice
Sent from Wicced's rooted A100 16gb HoneyComb 3.2 using XDA PREMIUM
Related
The binaries listed in the thread title (and others, iwmulticall for example) all work on my Viewsonic G-tab.. How much different is the Xoom so that the same binaries will also work? Thats rhetorical, as I'm going to try to get all of my favorite utilities on this tablet (xoom) regardless.. iwconfig can be a big help in diagnosing problems with wifi, and most certainly boostiing performance while the device is asleep (iwconfig <adapter name> power off).
Its quite strange that there is no CWM for this.. as the Viewsonic Gtab has a recovery that mounts the internal sdcard as /sdcard/ (to my dismay).
I had hoped to find things like a multi-core enabled tar/bzip binary included with honeycomb.. haha.. I'm serious.. That said, how do we go about creating such binaries? I don't think its just as simple as compiling an arm linux binary, copying to device, and setting perms... I've tried this with aria2c.. heh.. Think we'll see any multithreaded binaries anytime soon?
At least all of the partitions are ext4 - with the exception of pds.. whatever the hell that is.
I'm not sure if this is the correct section to post this in.. so feel free to move if necessary..
Wait until we get SD card enabled
Sent from my Xoom using XDA Premium App
Ok.. so you're saying they will give us microsd cards loaded up with multithreaded command line binaries? thats awesome. Thanks.
Blades said:
Ok.. so you're saying they will give us microsd cards loaded up with multithreaded command line binaries? thats awesome. Thanks.
Click to expand...
Click to collapse
wow, and you're asking for help? Chill out! I've been working on something like this, I had a Gtab too. IMO it would be easier once we get the SD cards working. However if I find anything I'll post it, but no need for that attitude.
Do you think you can find a copy of swype that would work for the Xoom? That's this tab is missing.. I've trieda few different things to get it on here and working but it always complains about screen resolution and I've found that SlideIT is NOT a decent replacement...
If it matters I have swype 2.6blah on my samsung mesmerize but had nowhere near the res of the Xoom.. I've seen a thread on swype on there gtab.... But I didn't try it since someone reported editing their build.prop caused segfaulting instead of booting and that want something I wanted to have happen unless I havea full day to devote to it..
Any help would be amazing!
Sent from my Xoom using XDA Premium App
mystkrh said:
wow, and you're asking for help? Chill out! I've been working on something like this, I had a Gtab too. IMO it would be easier once we get the SD cards working. However if I find anything I'll post it, but no need for that attitude.
Click to expand...
Click to collapse
What did I say? I still have my Gtab.. What about getting the sdcard working will making things easier? I don't understand what you're talking about, but it could be that ferocious attitude of mine getting in the way of things..
ok. so.. iwmulticall (aka iwconfig, iwpriv, iwlist, iwspy, and iwgetid) work.. busybox kinda works.. find is kinda messed up, as is ls. md5sum works.. tar works.. lsmod works.. and so on..
just mounted the xoom (@/) using sshfs on my linux comp.. works perfectly.. so both sftp-server and dropbear work..
1.16.2 did not seem to work.. but 1.16.1 works. I'll post..
unzip this to the directory that the adb binary resides in..
Blades said:
What did I say? I still have my Gtab.. What about getting the sdcard working will making things easier? I don't understand what you're talking about, but it could be that ferocious attitude of mine getting in the way of things..
Click to expand...
Click to collapse
why don't you just contact koush? he stated on his website that he won't provide CWM publically until moto/google provide sdcard support.
he did say he already has it running on his own device but doesn't want to risk a 800 dollar investment for any of us until sd card support comes through.
The sdcard hardware is in there, correct? This won't be a send-out update like the 4G modem... Can you guys use nvflash on this thing? I forgot to try to put the device into apx mode. I assume its the same procedure... power + vol up + vol down.
I wanted to really start from scratch so I went through some of the Samsung open source code and found that there were some unnecessary modules being loaded. That could be what's causing some problems (although I haven't had much but think it's signal related or Sprint's towers being updated), but with no overclocking and the changes, it could solve everything? Dunno still.
So I tried my best to trip the bloat-code out and try to keep it as stock as possible (no overclock), perhaps some of you can test this out for me.
Changelog
v.1
- CWM 4.0.1.5
- Superuser 3.0 + fixed su, now installs in /system/bin, you can update the binaries with SuperUser app.
- init.d support (/system/etc/init.d)
- Bootanimation support
- fixed Airplane toggle
Things to test:
- LOS?
- Video out? - sorry my video out adapter is still being shipped, I think I enabled it but can't really check???
-Airplane toggle should be fixed
Things I am working on:
- Boot splash logo? Still working on that, if anyone knows how to change it, please let me know.
- Recompiling CWM from scratch, add external SD support, fix wipe issue
- Add infrastructure to wifi tether and USB tether?
Devs, u r free to steal my stuff, or stuff I stole I really don't remember from taking too much energy pills, taking a big white line from Stevie Jobs, "Good artists copy, great artists steal.".
If you have some knowledge to share, plz don't forget to email me at zedomax [at] gmail.com
If this works well, I will build off it or otherwise I will keep optimizing until its fully stable.
Thanks guys, you rock!
Download here:
v1:
ODIN tar:
http://downloadandroidrom.com/file/.../SPH-D710_Zedomax_EpicTouchKernelStock-v1.tar
CWM zip:
http://downloadandroidrom.com/file/.../SPH-D710_Zedomax_EpicTouchKernelStock-v1.zip
Yess!!! Thanks zedo. Will give it a whirl. Permission to use in StarBurst once stable?
Sent from my Epic Touch 4G
Odin'ed it over StarBurst 1.2, seems to work good but only been using it for 2min
Gonna test this out, thanks for all of your hard work, Zenomax!
Flashing now.
Boots up. Will be testing until I can get mine to work, but I think I had the same intent as yours does. Boots into CWM just fine too.
Cool! I'll be trying this when I get home. And I won't be bugging you anymore about the yellow triangle anymore... I have my usb jig coming in the mail.
Samsung Galaxy S II
Thanks and keep up the good work, it's well appreciate it
Sent from my SPH-D710 using xda premium
Flashed fine over 4.1beta. Seems to be working well, airplane mode working. Under 4.1 I seem to suffer routine LOS when on the road but not when at home, so it may take a while to fully test but so far so good.
Thanks for all the hard work.
PhantomHacker said:
Yess!!! Thanks zedo. Will give it a whirl. Permission to use in StarBurst once stable?
Sent from my Epic Touch 4G
Click to expand...
Click to collapse
Yes of course, any time, I thought everything was open source? LOL
zedomax said:
Yes of course, any time, I thought everything was open source? LOL
Click to expand...
Click to collapse
I like to ask anyway. ...Signal strength seems better may be placebo though.
PhantomHacker said:
I like to ask anyway. ...Signal strength seems better may be placebo though.
Click to expand...
Click to collapse
my understanding was that signal strength and quality was taken care by the radios/modems, not the kernel...
frifox said:
my understanding was that signal strength and quality was taken care by the radios/modems, not the kernel...
Click to expand...
Click to collapse
Was talking about wifi.
Sent from my Epic Touch 4G
Root is still messed up for me with your kernel Zedomax, so please make one that doesn't have root or even busybox(unless it's needed for the recovery) as root & busybox can be added through CWM if the user wants
great work zedo! i'll test it out once i get back to work. somehow i left ALL my micro usb cables at work like an idiot.
I had the LOS today, had to restart my phone three times in the span of three hours. So, being frustrated, I booted in to CWM, wiped my davlik and flashed back to v1.1. Then I wiped davlik again, flashed back to v1.2 and rebooted. Haven't have a LOS issue since. So far so good...
Sent from my SPH-D710 using XDA App
My bad, I totally misread the title. I though I was posting in the other kernal thread by Zedo.
Sent from my SPH-D710 using XDA App
ccline84 said:
My bad, I totally misread the title. I though I was posting in the other kernal thread by Zedo.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Should just edit the first one
Sent from my SPH-D710 using xda premium
big thanx zedo.
Calkulin said:
Root is still messed up for me with your kernel Zedomax, so please make one that doesn't have root or even busybox(unless it's needed for the recovery) as root & busybox can be added through CWM if the user wants
Click to expand...
Click to collapse
I personally think CWM is causing some issues right now... no evidence behind it, just a suspicion.
silversx80 said:
I personally think CWM is causing some issues right now... no evidence behind it, just a suspicion.
Click to expand...
Click to collapse
CWM probably can't cause issues since it's in recovery, it doesn't fire up unless u r actually in recovery but CWM we all using right now have issues as they are based off SG2 CWM binaries. Someone has to compile a CWM for Epic4GT from scratch or at least hack it. I am gonna try that soon but compiling kernels is just taking too much time, I've been 24/7 compiling for like a whole week, get no other work done, i seriously need to go out to a rave and get f--ed up for couple days. Then my head will be clear, compiling will be fun.
This is gonna be the thread where I post the CWM I've been working on
First things first, here comes a newb question
Its my first time working with CWM, do i need the entire android source to compile it ? or just the source from koushs github. Also here is my nifty solution for navigation
The linux kernel has a few different types of events, the main two that CWM uses are
EV_KEY which is key event
and
EV_REL which is the trackball usually
the trackball even reads the movement and past a certain threshold fakes an up or down key event.
what I'm doing is adding in EV_ABS (touch event) to the input thread so that when it reads a screen touch it will fake a down key event similar to how the EV_REL works.
Now this is just the initial idea, in the future I want to make the touch event work like the trackball so to go up/down you swipe up/down, but this will do for now.
Controls will be as such
Tap = Move Down
Power = Select
Also once navigation is workin im going to be modifying it to set bootmode before exiting recovery so as to get rid of the current problem of not being able to exit recovery.
correct me if im wrong but here are the bootmodes i need
idme bootmode 0x4000 (normal boot)
idme bootmode 0x5001 (reboot recovery)
update 12/16 9pm
working on fixing some bugs with touch input and fixing rebooting from recovery
system is recognizing touch input properly and recovery boots properly, and when bootmode value is set to normal also boots the system correct.
Update 2
Got Reboot Working correctly from recovery and still workin out some touch nav bugs, will finish up tomorrow hopefully
UPDATE 12/17
Havent had time today t work on it like i planned, still issues with the touch input moving the cursor too far. Working on it now
UPDATE 12/18 1:30am
Touch Icons are drawn and in the correct position, working on mapping to correct functions
update 10:50pm
For some reason cannot get the touch coordinates to line up with the icons, even though the icons should be right over them.....not sure whats going on =/ gonna have to redo a few things to see what might be happening and why a key event isnt being injected
UPDATE 12/19
ReWriting the the input get for my touch controls to simplify it and make it easier to debug. Got work though till 4 so its gonna have to wait
awesome, I was sitting stuck in recovery on my mytouch today and using the trackball thinking of this as well. bravo my friend. seems very feesable
Sent from my HTC Glacier using xda premium
smirkis said:
awesome, I was sitting stuck in recovery on my mytouch today and using the trackball thinking of this as well. bravo my friend. seems very feesable
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Thats the idea, and though there are other touch recovery in development, I've been using CWM for a long time and like and trust its (at least for me) reliability
You have to have the full android source code. it goes in the bootable directory.
death2all110 said:
You have to have the full android source code. it goes in the bootable directory.
Click to expand...
Click to collapse
i figured...syncing now...will let you guys know the progress when there is some.
idme bootmode 4002 is fastboot
Sent from my SPH-D710 using xda premium
If you got questions ask koush he is always on twitter , but you can always go to CyanogenMOD irc on freenode
Sent from my SPH-D710 using xda premium
My understanding is that you need the whole source, but you can build just the recovery by typing: make recoveryimage.
There is a guide here:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Hope you get farther then I did. I must have missed a step somewhere because I cant get it to build.
tecookie whats the issue you're having?
ok guys....touch recovery working...let me work out the kinks then we are good =]
It's weird. Seems like yesterday I was getting a different error.
# make recoveryimage
build/core/product_config.mk:196: *** device/amazon_kindl_fire/boot.img/device_boot.img.mk: PRODUCT_NAME must be a valid C identifier, not "full_boot.img". Stop.
Click to expand...
Click to collapse
I was following this guide and everything seemed to be going well up to the "build/tools/device/mkvendor.sh..." point. I got the "Done" output from that command but also a bunch of other stuff, some of which looked like they might have been errors.
I think I might just re-sync and try again.
---------- Post added at 06:22 PM ---------- Previous post was at 06:17 PM ----------
ECOTOX said:
ok guys....touch recovery working...let me work out the kinks then we are good =]
Click to expand...
Click to collapse
Wo! Awesome! Looking forward to it.
ECOTOX said:
ok guys....touch recovery working...let me work out the kinks then we are good =]
Click to expand...
Click to collapse
WHAT?! This is great news! I'm very excited to hear this! I don't even have a kindle fire yet, but plan on getting one for christmas and I was worried I might not be able to hack it as well as other devices without a usable recovery. But this is great news! Glad to see many talented devs working on the fire, just makes that 200$ a great investment
TWRP
dubt17 said:
WHAT?! This is great news! I'm very excited to hear this! I don't even have a kindle fire yet, but plan on getting one for christmas and I was worried I might not be able to hack it as well as other devices without a usable recovery. But this is great news! Glad to see many talented devs working on the fire, just makes that 200$ a great investment
Click to expand...
Click to collapse
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Poler166 said:
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Click to expand...
Click to collapse
I know, I'm not doing this just for a recovery, i want to see if i can do it =P Also I like CWM
ECOTOX said:
I know, I'm not doing this just for a recovery, i want to see if i can do it =P Also I like CWM
Click to expand...
Click to collapse
Any estimates when it'll be ready for release?
Sent from my Kindle Fire using xda premium
Earliest tomorrow
Sent from my Nexus S 4G using Tapatalk
ECOTOX said:
Earliest tomorrow
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I can help you out if you want?
Poler166 said:
you should check the TWRP it is a more basic recovery that works just like clockworkrecovery and its all touch its been in development but now i balive it is now fully working its just not up yet, you should check it out http://forum.xda-developers.com/showthread.php?t=1356425
Click to expand...
Click to collapse
TWRP is a little better choice in recovery for tablets, but it never helps to have several options
death2all110 said:
I can help you out if you want?
Click to expand...
Click to collapse
Nah, thanks though, you've been alot of help already. I'm exhausted and need to sleep, so when I wake up i'm guessing around 4 more hours work and the initial release will be ready
Sent from my Nexus S 4G using Tapatalk
brett10 said:
TWRP is a little better choice in recovery for tablets, but it never helps to have several options
Click to expand...
Click to collapse
u mean never hurts? how can u claim twrp is a better choice when its not out. cwm is known by many and some just feel comfortable using it. stop trolling, development is development. even if they both got released the same day, people with choice will choose whatever recovery they wanna use. I personally like cwm, but would use whatever is available to our devices that's stable.
Congrats on the progress, can't wait to test it out.
Sent from my HTC Glacier using xda premium
Hi everyone,
A couple of minutes ago I got a really random su request from something called dumpstate. Would anyone happen to know what this could be I've never seen it before.
Does anyone know some way that I could find out what app pushed the request, or possibly help find out if I actually have something malicious on my phone now?
~PsyCl0ne
Edit: running Seanscreams 6.3 release with circle battery and light saber s pen sounds.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Just to add to the above post avast and lookout report nothing was detected. What the hell. I did notice that ad block plus must have dropped and then came back.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
appears to be an issue with the new SuperSU update which pushed today (v1.00).. and possibly the Note2 (and other devices). Happened to me and a few other folks on the CleanROM v4.2.5 thread. I uninstalled the SuperSU Updates ( and rolled back to v0.99), and so far... so good.
DoctorQMM said:
appears to be an issue with the new SuperSU update which pushed today (v1.00).. and possibly the Note2 (and other devices). Happened to me and a few other folks on the CleanROM v4.2.5 thread. I uninstalled the SuperSU Updates ( and rolled back to v0.99), and so far... so good.
Click to expand...
Click to collapse
This is why I love this forum. A noob like myself can search on an issue and most likely find where one of the more seasoned members have more than likely come across it and have a potential fix or workaround! :good:
DoctorQMM said:
appears to be an issue with the new SuperSU update which pushed today (v1.00).. and possibly the Note2 (and other devices). Happened to me and a few other folks on the CleanROM v4.2.5 thread. I uninstalled the SuperSU Updates ( and rolled back to v0.99), and so far... so good.
Click to expand...
Click to collapse
Theres an update out now to correct this issue - check play store
kingofkings11 said:
Theres an update out now to correct this issue - check play store
Click to expand...
Click to collapse
Yup... Chainfire uploaded a work-around update v1.01. (which basically is preventing the infinite dumpstate loop). Thx
Thank you for finding this. I was wondering why I started having random freezes and reboots and dump states, but haven't been able to sit down and figure it out.
Grr
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Hey guys, I'm not sure what to do next. I recently flashed in Jedi Master 14, which I'm loving, amd decided to be ridiculous and theme the entire phone to Star Wars, or as much as possible. DD gave me a Yoda shutdown anim, and I used the in-house boot animation installer from Rom Toolbox to change my boot animation.
Which led me to my sounds. Figured I'd start off easy with the lockscreen sounds, replce the watery splooshes with saber deactivation/ignition. So I did a bit of research amd figured out how to do it.
Found the files, that was easy. Also found an app to convert my downloaded mp3s to oggs, changed them, copied out the original sounds, put the new ones in, chamged the permissions to match their neighbors, rebooted and tested. Silence. I just also tried changing ownership so both list as "root," same as the other oggs, rebooted and tested again. Still nothing.
At this point, I'm wondering about file size/length, but my digging has yet to give anything about that. Do I need those, or at least the sizes, to match the originals? Any help or advice would be awesome.
Tl; dr, I broke things help.
Sent from my SGH-T889 using xda app-developers app
atxhellcat said:
Hey guys, I'm not sure what to do next. I recently flashed in Jedi Master 14, which I'm loving, amd decided to be ridiculous and theme the entire phone to Star Wars, or as much as possible. DD gave me a Yoda shutdown anim, and I used the in-house boot animation installer from Rom Toolbox to change my boot animation.
Which led me to my sounds. Figured I'd start off easy with the lockscreen sounds, replce the watery splooshes with saber deactivation/ignition. So I did a bit of research amd figured out how to do it.
Found the files, that was easy. Also found an app to convert my downloaded mp3s to oggs, changed them, copied out the original sounds, put the new ones in, chamged the permissions to match their neighbors, rebooted and tested. Silence. I just also tried changing ownership so both list as "root," same as the other oggs, rebooted and tested again. Still nothing.
At this point, I'm wondering about file size/length, but my digging has yet to give anything about that. Do I need those, or at least the sizes, to match the originals? Any help or advice would be awesome.
Tl; dr, I broke things help.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Have you tried fixing permissions in recovery? I'm
Sent from the greatest Galaxy
markusf21 said:
Have you tried fixing permissions in recovery? I'm
Sent from the greatest Galaxy
Click to expand...
Click to collapse
Hmmm. This isn't something I've seen yet. How would I go about doing this?
"I'm" what? Did you get attacked by ninjas midpost?
atxhellcat said:
Hmmm. This isn't something I've seen yet. How would I go about doing this?
"I'm" what? Did you get attacked by ninjas midpost?
Click to expand...
Click to collapse
I get attacked by ninjas all the time. I have 2 small boys (ninjas)
You'll find the option to fix permissions in a menu someplace after you boot to recovery. In twrp it's under advanced. Not sure about cwm
Sent from the greatest Galaxy
markusf21 said:
I get attacked by ninjas all the time. I have 2 small boys (ninjas)
You'll find the option to fix permissions in a menu someplace after you boot to recovery. In twrp it's under advanced. Not sure about cwm
Sent from the greatest Galaxy
Click to expand...
Click to collapse
Ahhh, I understand. I have the same. How old?
And thankee. I found the command, backing up first, just to be safe. If this works, I'm going to be so happy.
And on that note, Pandora just starting playing Alestorm. This is a blessed venture, I think.
Backup finished quicker than I thought. Still no dice. Any other ideas?
2 boys 5 and 6 years old.
Unfortunately I'm out of ideas
Sent from the greatest Galaxy
markusf21 said:
2 boys 5 and 6 years old.
Unfortunately I'm out of ideas
Sent from the greatest Galaxy
Click to expand...
Click to collapse
Aaaah, nice. Ours are 6 and 2.
And I also somehow managed to break the lmt service...which I rely heavily on. So now I'm flashing in JM16 and leaving those sounds ALONE.
Yeah, right, let's see how long THAT lasts. Ill just be more vigilant with backups.
markusf21 said:
2 boys 5 and 6 years old.
Unfortunately I'm out of ideas
Sent from the greatest Galaxy
Click to expand...
Click to collapse
Aaaah, nice. Ours are 6 and 2.
And I also somehow managed to break the lmt service...which I rely heavily on. So now I'm flashing in JM16 and leaving those sounds ALONE.
Yeah, right, let's see how long THAT lasts. Ill just be more vigilant with backups.