Related
I've got a rooted G1 running CM-6.1.0 stable. Because I'm too lazy to move numerous apps one by one to the SD card by going to system>applications>manage applications, i have decided to write a script that will move all non-system apps that are installed on internal storage to the SD card. This is what i have so far.
Code:
# list=$(ls /data/app/)
# for file in $list
> do
> dir=$(file%.apk)
> mkdir /mnt/asec/$dir
> mv /data/app/$file /mnt/asec/$dir/pkg.apk
> done
my problem is that other than moving the .apk files from "/data/app/" to the appropriate directory in "/mnt/asec/", i don't know what App2SD does. can someone please tell me exactly what other actions are preformed by clicking "move app to SD card"? once i know what it does, then i should be able to finish my script.
note: please do not respond by saying "pm setInstallLocation 2", anything regarding ADB pull/push/install, or by telling me to go install some app off of the market. i already have the install location set correctly, i don't always have a computer near me to use ADB, and I'm not going to waste my time waiting for some goddamn GUI to load just so i can do something that could surely be done more efficiently via a simple script. Thanks.
I'm running stock rooted lagfixed EE4 (PBJ Time), rooted. I was messing with the app "android system info" and saw the following errors showing up under radio:
Can't set 3g_traffic java.io.FileNotFoundException: /mnt/radio/3g_traffic (no such file or directory)
To see these errors I went to:
Android System Info > Logs, then
Menu > Log Category > Radio, and
Menu > More > Logs Verbosity > Warning
Does anybody else have these errors? I used root explorer to create a folder called radio in /mnt and it immediately created a file called "3g_traffic."
Apparently inside this is a small text file that shows either "1" when there is data traffic on the 3g radio and a "0" when it's idle. If I leave the system as R/W the errors stop. If I set the system back to R/O I get these errors:
Can't set 3g_traffic java.io.FileNotFoundException: /mnt/radio/3g_traffic (Read-only file system)
Even if I set all permissions enabled on the file to r/w/x for owner, root, and group, those errors persist.
I'd appreciate it if someone tried to duplicate this experiment and let me know their results. Android System Info is available free in the market. I'd be curious to see if I leave the file system as R/W if I stop losing signal - maybe the logs are filling and crashing the radio.
Thanks,
Dan
"To see these errors I went to:
Android System Info > Logs, then
Menu > Log Category > Radio, and
Menu > More > Logs Verbosity > Warning"
Running same as you, can not find "Android System Info" as a folder in Root Explorer. Looked in /system and /sys but no Android.
I did add the radio folder as directed and it does have a 1 bit file inside.
What is this supposed to fix?
I live in a marginal area anyway, so yesterday I swapped to the EP3HA modem into the phone. I can not tell much difference yet. I did get to watch a 30 min tv program in Netflix after new radio. I think that is progress.
Read carefully
chrstdvd said:
Running same as you, can not find "Android System Info" as a folder in Root Explorer. Looked in /system and /sys but no Android.
Click to expand...
Click to collapse
I reference "Android System Info" as an App and also said it's available for free in the market.
chrstdvd said:
What is this supposed to fix?
Click to expand...
Click to collapse
Many Droid Charge users complain of intermittent data connectivity. The phone will switch from a 4g/LTE signal to 3g to 1x then drop data entirely, or (when set to 3g only) switch from 3g to 1x then drop.
There were a crapload of errors in the log related to this particular folder and that file. Errors = bad. No errors = good. Doing everything as I described
stopped the errors, and stopped my data from dropping. This includes both creating the folder and leaving the system as R/W through root explorer.
My 4g was enabled and I also got a "lte_traffic" file created right away.
Not sure if this had any effect on my data dropping yet. I had a 3g signal while trying it now. Will monitor it some more later.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
i created this list for myself and felt like sharing some info that might help others since my phone seems to be working OK. this is mainly a consolidation of instructions from the youtube site listed at the bottom of this post. if you're feeling generous then consider donating to qbking77, the person responsible for the youtube instructions and download'ables. thanks to everyone that contributed to this.
scott
•0) If your Epic is rooted then create a backup
•1) Open odin 1.85, select pda, select SPH-D700-EB13-8Gb-REL.tar.md5, enter download with phone (hold 1 and power button), uncheck all but auto-reboot, select start
•2) Setup wi-fi, manually update to latest & greatest Android OS (menu, settings, about phone, updates, update android). Obviously, you'll have to reset your phone in between each update.
•3) Open odin 1.85, select pda, select kernel-GB-3a.tar.md5, enter download mode on phone (hold 1 and power button), uncheck all but auto-reboot, select start
•4) Open odin 1.85, select pda, select ACSRecovery5-1.0.0.0-epic4g.tar.md5, enter download mode on phone, uncheck all but auto-reboot, select start
•5) Turn on USB debugging, connect Epic to USB, turn on mass storage
•6) Place Superuser-3.0.7-efghi-signed.zip and GPS_FIX.zip onto sdcard
•7) Note: this is a good place to create a backup so that you have a pre-rooted version of Android EL30 to restore to when future updates are released.
•8) Enter clockwork with phone (hold low volume, camera, and power button), install zip from sdcard, Superuser-3.0.7-efghi-signed.zip, reboot system
•9) Enter clockwork with phone, install zip from sdcard, GPS_FIX.zip
•10) thanks to dshoem01 on sprint.com community for this... If a force close error is displayed when you receive an incoming call, ensure the "reject call with message" set up includes no more than 5 messages. To access these settings, go to Menu > Settings > Call settings > Reject with message, choose the menu key and select 'delete', check the box next to each message to be deleted and select 'delete' again.
Optional: remove power on & power off video & sound:
Open Root Explorer
Go to /system/media
Delete bootani.qmg
Go to /system/media/video
Delete shutdown directory
Go to /system/etc
Delete "Power On.wav"
Optional: Delete Junk:
Open Root Explorer
Delete Nascar:
Delete /data/dalvic-cache/[email protected]@[email protected]
Delete /data/data/com.handson.h2o.nascar09
Delete /system/app/nascar09-prod-release.apk
Delete Asphalt5:
Delete /data/dalvic-cache/[email protected]@[email protected]
Delete /data/data/com.gameloft.android.ANMP.GloftAsphalt5Demo.asphalt5
Delete /system/app/Asphalt5_stub.apk
Delete Free HD Game:
Delete /data/dalvic-cache/[email protected]@[email protected]
Delete /system/app/ FreeHDGameDemos.apk
Optional: Modify Dock Bar:
Click "applications"
Click "applications"
Click the "menu" button.
Click "Edit"
The home/applications is not movable.
Drag in 3 shortcuts of your choice.
Click "menu"
Click "Save"
•11) Create another backup
Note: I typically rename my backups as such (date_version_rootstatus_datastatus): 012912_EL30_prerooted_nodata, 013012_EL30_rooted_data, etc.
More info:
http://www.youtube.com/watch?v=kwFRzzIqouE
This isn't android development. It relates to it, but this doesn't belong here. Flashable content only. You've been a member since 2008, so you should know this already.
I should add that its awesome your sharing this info for people who need it. Not trying to be an a**hole.
Sent from my SPH-D700 using XDA App
I'd suggest the EC05 TAR, to save an update step, and using CWM, rather than ACSRecovery, simply because it's standard. Other recoveries are optional. I'd also omit the GPS fix, as some users find they don't need it.
And I have to agree with the above, though this is much more reasonable to be in the dev section than most that get strewn here.
k0nane said:
I'd suggest the EC05 TAR, to save an update step, and using CWM, rather than ACSRecovery, simply because it's standard. Other recoveries are optional. I'd also omit the GPS fix, as some users find they don't need it.
And I have to agree with the above, though this is much more reasonable to be in the dev section than most that get strewn here.
Click to expand...
Click to collapse
I agree with you on all stated above. Perhaps, OP, create an "optional" section providing instructions for things not necessarily considered standard.
While I do agree that this is borderline belonging in General, I am pleased to see someone eager and willing to help out other users by taking the time to create something as detailed as this thread. The section on things that can be removed is very thorough and I feel that it could help users who want a stock ROM, but still want to enable some better-than-stock functionality.
I say continue doing what you're doing, but do keep in mind that the Epic community is quite, how do you say it, developed. Lots of seasoned users here who have been around for a long while, but definitely still beginners who need a helping hand.
Sent from my SPH-D700 using xda premium
As they said... excellent write up but doesn't really belong in development... but much more so than most of the errant posts that get thrown in here by some... thanks as I'm sure it will help some people...
Sent from my SPH-D700 using Tapatalk
clarity
so this post should go in general forum instead of development forum?
i suggested acsrecovery because that is what the youtube video / download instructed and it worked for me. personally, i don't see much difference between acsrecovery and cwm.
i agree, ec05 would save a reboot...but c'mon ;-)
i'm curious why the gps fix is only applicable to certain circumstances...weird. anyone complain that installing the gps fix negatively impacted their phone? from what i understand, it can only positively impact the gps performance.
yes, i prefer stock over roms; however, i greatly appreciate the ability to root so that i can make minor tweaks here and there (especially to remove sprint's power on video & melody!). if only there was a way to un-root, install an update, and re-root!! until then, my method of reverting to a backup with the most recent update (pre-rooted, minus tweaks of course), installing the new update, and then re-rooting won't take very long.
hello guys, don't know if I'm wrong...maybe push the question into correct section...
But as user flashing hole day different ROM I'm searching for an solution like is at MIUI-ROM integrated (see picture)
Exist a way to put the amount if used traffic?
Thanks in advance...
You can download ZIPme
Press the " + "
Then choose " Data ", -> " Data usage "
-> " Ok " then click " Create "
It will create a flashable zip so you can flash it after installing new rom. And now you have same datq usage as before.
Thanks for your answer...but when I read it correct the tool make the same like titanium backup.
But my intention is to insert the amount manually because sometimes I've got an sudden crash of my ROM and I can not backup my used traffic. you know what I mean? And then I have to look at the support menu of my provider to get data traffic (and then I want to put it manually into ROM settings)
How to get the most complete backup, which is possible with locked bootloader and no #Root?
Hello everybody.
This step-by-step Guide will show you, how to get the most complete backup from a Nexus device,if your bootloader is not unlocked.
Once, i also had some problems and confusion with this backup, but finally i understood. So i'm posting this thread for some other users, which are maybe confused.
First of all, great thanks to @WugFresh for the Nexus Root toolkit, and for the early help.
This can be helpful, if you want to unlock your bootloader, but you still need to back up some important data.
With unlocked bootloader, it's quite easy to take a backup, which doesn't exclude anything. That's the Nandroid w/ Backup.
But with locked bootloader, it's a little bit (much) harder, because the nAndroid/W Backup will not be useful at all.
The problem is, that unlocking bootloader will wipe out all user data/apps/etc., which is present on the device. Locking it again will do the same. There's no way to avoid the wipe, which will make all data unrecoverable, but you can back up as much data as possible.
I recommend to unlock the bootloader, straight away after you buy any nexus device, before saving any data to it, to avoid those restrictions. It's truly worthed it.
The Factory Images of all Nexus Devices can be downloaded from this nice place here, if you want to change your Android Version manually: https://developers.google.com/android/nexus/images?hl=de
Google excludes all 4.4.1 or 4.2.1-Versions on the website, but other version history is included, and the download speed is very fast there.
This is, what the backup will include:
> Full User Data Storage (Without NRT)
> All APK's of Free Apps
> All Data of Free Apps
> Full Data of Paid Apps
> AndroidManifests.XML of Free/Paid/System apps
> SMS
>Call Logs
>Contacts
This is, what the backup will exclude:
APK's of Paid Apps
Data of System Apps
APK's of System Apps
Network Configuration
WiFi-Passwords and SSiD's
A Nandroid w/ Backup does actually include everything, which is on the device, nothing (except. deleted recoverable data) is excluded.
Part 1 (Without NRT) - User Data Storage
For this part, you should do following:
Make sure, your computer supports MTP. Connect your device to your Computer's USB Port.
1. Reboot your device (better to safe mode) - If your computer detects the device, jump to step 4.
2. After Reboot, drop the drop-down-menu by swiping down from the upper screen.
2.1 Go to the USB-Connection-Notification and tap it.
3. If MTP-Connection is not enable, enable it
4. You're now viewing the Internal Storage of the Drive with the File Explorer of Windows.
4.1 Now press STRG+A.
4.2 Now copy or move the data to your desired destiantion (On Android 4.4.2, never move the data from the device, because that can Trigger a full data loss of the internal user storage, due to a software bug. Better →copy→delete.)
4.3 If you've got many files, and the Progress Bar is stuck at zero, wait around up to thirty minutes and see what happened. In those thirty minutes, Windows counts the files and calculates the - this is needed for MTP. Too Bad ;(
4.3.1 If something happened in those thirty minutes, (progress bar) simply wait until the end.
4.3.2 If nothing happened, try not to copy/move all file at once.
5. Make sure, that every desired file is in the output folder. (4.4.2 Software bug might exclude newer files.)
6. Go to [Part 2], to backup the apps with their data.
Part 2 with NRT - Apps, Application Data, AndroidManifest etc.
You have to connect your device to the computer with a MicroUSB-Cable. The length of the cable is not important, but please make sure, that it's attached properly.
Installing the program is possible, without your nexus device itself, but you'll need it.
[Part 2.0 - Preparation and Installation of NRT]
First [i forgot, what i wanted to write here. Will be added by edit, please excuse me ]
You can download the lastest version of NRT right here (Currently, it's 2.0.5, while this text was written)
It's an offline (standalone) installer, so that the Installer does not require any Internet connection to install NRT, if the download of the installer finished. It will not download additional files and it's also free of adware.
Optionally, you can set the installation directory manually.
[Part 2.1 - After Installation]
After finishing the Installation, you will have to open the toolkit. Possibly it will ask you, which device model + Android Version you have got. Auto-Detection only works, if your device is attached to the computer properly.
Probably, a message will show up, which wants you to download the following three things:
→Modified Boot.img
→TWRP (Team win Recovery Project) Recovery
→@ChainFire SuperSU (Currently v2.4.6)
So you have to click on „Download + Update all file dependencies"
After the NRT has downloaded a few files, it will automaticly go to the GUI's Main Page with it's LiveLog.
[Part 2.1.1 - Google Driver Installation]
For this Step, you have to click the big button in the main GUI Page, in the area "Initial Setup", in the upper right corner.
As far, as i know myself, it's recommended to install the Google Drivers. The name "universal drivers" sounds attractive, but i did not test, whether it works, but i think, it does also work fine. But there's also a big number for „Recommended Solution". In my case, the tool recommended me [#1].
[2.2 - GUi]
Now, it will ask you, to enable the USB-Debugging. NRT will tell you, how to do it:
1. Go to the Settings Menu.
1.1 Go to the System Information
1.2 Tap the Build Number (e.g. KOT49H for Android 4.4.2) seven times, to enable the developer options. You can also tap it more than seven times, but this will not have any effect.
2. Open the Developer-Settings.
3. Enable „USB-Debugging"
3.1 If needed, you can confirm to allow your computer. The RSA-Fingerprint of your computer will be displayed.
3.2 For sure, also go to the USB-Connection settings (through the Drop-Down menu or the setting menu), and uncheck MTP or PTP or whatever (everything, which is present.)
You're now on the Main Page of the GUI.
On the left, there's an Area, which is called: „Backup + Restore“.
There are two buttons labeled [Backup] and [Restore].
[Restore] is for restoration purposes, so click on [Backup].
[2.3 - App Backup]
On the area „Backup all Apps", you see 2 tickboxes.
Please do not tick the first one, because the first one would require an unlocked bootloader. If you do, the program would fail
[ ] System apps+data
[✓] Shared Data
After that, just go and click on [Create Android Backup File], which will create an *.ab File. (not *.adb) Later, you can restore the data from the AB file, whenever you want.
After you clicked this button, a window with some relevant information will show up. Please take your time and read it. It can be pretty useful.
Please don't forget to turn Airplane Mode on. I personally recommend being in Safe Mode. (The computer can run normally, but the device should be in fresh safe mode without opening any app.)
After you click on [OK], the program will ask you, where you want to save the .ab-file, and what the filename should be.
The Standard is „MM-DD-YYYY_HH-MM.ab" - I personally use YYYYMMDDHHMMSS, the Timestamp, which is known from the Wayback Machine.
After that, the Toolkit will try to reboot your device. But then it will not boot into safe mode. So please click [save] at the moment, when the device is already rebooting into safe mode.
Make sure, that your Computer's RSA-Key(Fingerprint) is automaticly accepted by the debug mode. The Toolkit will only wait five minutes for the device. If the waiting time has expired without success, an error message will show up. It says: „Notification: Waiting for device operation timed out. [...]"
If your device can't be detected, read the information in the timeout-window. It's worth reading it and will maybe solve your problem.
If your device is detected properly, your device should disply a confirmation message all over the screen. Try confirming fast, otherways NRT will timeout.
But if you want, you can lock it with a password, which you'll need, if you want to read/restore from the backup anytime later on. Please take care about case-sensitivity and to avoid additional problems, it's not recommended to use those emoticons on the KitKat-Keyboard.
Now, the backup starts.
While NRT is indicating, that the backup is running, the device will display, which package is being backed up. Now, please wait, until it's finished.
[2.3.6 - Finish]
The output file is now compressed, so a smaller file size than uncompressed is expected.
There are tools, where you can read those ADB-Files.
Make sure, that the filesize is reliable. If the backup is blank (Zero Bytes) or just a few kilobytes, something went wrong. Retry the backup, if this is the case.
[2.4 - Other things]
Now, you have to do the same with following things, if possible or needed:
> SMS
> Call Logs
> Contacts
> Network Configuration (Root needed on Android KitKat/Higher)
Just give it a try.
Part 3 - VirtualSD-Backup
This is non-urgent, so if it does not work, it's no problem.
You have to go to the Backup Menu again.
This is very similar to Part 1, and easier, but does only work up to Android 4.3(.1).
If you want to do this on 4.4/Higher, you will need an unlocked bootloader. Vicious cycle.
----
@WugFresh, @anybody else; if there's anything i missed, or i described wrong here, like false information, please let me know it by sending me Private Message or better Post in this thread.
If there are problems, feel free posting here No problem is irrelevant here.
I hope, my guide was able to help some people here.
I wish you to have very much fun with NRT‼
Test Device: Nexus 7 2012 - 32 GB IntMem - WiFi - Not mobile - Android 4.4.2 KOT49H
Ask Questions
Please feel free asking questions here. :laugh: