[GUIDE/HOW-TO] Beginner's "Getting Started" Guide :: Root, Recovery, Roms etc
Update: Links are dead, mediafire decided to pull them without any notice. However, all important files can be found on my DevHost Account
This guide is made to help newbies get started on the basic customizations they can do to their Galaxy Fit, and with minimum possible risk of bricking it. Plus, recent update will help users to move on from being android newbies to experienced users.
Before you think of posting as ‘copied’, I want to inform you that more than 90% of the guide has been typed by me, using my own experiences with my Galaxy Fit, and has not been simply copy-pasted from anywhere.
Note: Even though care is taken to help you minimize risk of bricking your phone,
no one, except yourself, is responsible for any damage that happens to your phone.
Also, doing most of the modifications below WILL void your warranty.
Do not quote the entire post!
Quote only the part where you are facing problems...
If you completely quote the posts by me, I will not help, since I can safely assume that you are not following instructions as stated.
And do NOT pm me asking help, with regards to this thread...I will not help you there!
If you have questions/problems, ask here...I'll try my best to help you here!
Topics covered in this guide:
Most stuff related to Rooting
Backing up data using Titanium Backup Pro
Installing Stock Roms
Installing Custom Recovery
Installing Custom Roms (Continued in second post)
Creating and Deleting Sd-card Partition
Setting up and using Link2sd
Installing apk’s through “Root Explorer” method
Nandroid Backups (Continued in third post)
Overclocking
Bricked Galaxy Fit
Bootloops (Continued in fourth post)
How to reclaim warranty?
Battery Care
Android Debugging Bridge (In fifth post)
Logcats (In sixth post)
Pre-requisites:
Before you proceed, you need to have the following things ready with you:
Samsung Galaxy Fit S5670 (obviously)
Windows PC (Xp, Vista, 7)
Usb Data Cable
Samsung Usb Drivers installed on your computer (Download)
Usb Debugging Enabled (Enable it from Settings> Applications> Development> Usb Debugging)
A minimum of 50% Battery left for use
Knowledge on how to use a windows pc (optional, but recommended )
A calm mind, and plenty of patience.
Also, remember this:
a.To reboot into “recovery mode”, first shutdown your phone completely, then press and hold power + home button and wait for phone to switch on.
b.To reboot into “download mode”, first shutdown your phone completely, then press and hold power + home + volume down button and wait till phone switches on (you’ll get a yellow triangle with an android inside it, with the word “Downloading” written under it)
Edit: Since a proper "route" to installing custom roms isn't very clear, I'll just add this:-
Let's say you have a stock froyo rom, and want to try some custom rom, then
[OPTIONAL] Root Froyo, if you wish.
Then, you update to Gingerbread.
[OPTIONAL] Root GB, if you wish.
Install ClockworkMod Recovery
Then finally, install the custom rom of your choice.
Hope the "path" is now clearer
1. Rooting
Q) What is “rooting”? What are its advantages and disadvantages?
A) “Rooting” your device means obtaining “superuser” rights and permissions to your Android’s software. With these elevated user privileges, you gain the ability to load custom software (ROM’s), install custom themes, increase performance, increase battery life, and the ability to install software that would otherwise cost extra money (ex: Wi-Fi tethering). Rooting is essentially “hacking” your Android device.
For more info, refer Source
Though, one thing worth mentioning, YOU DO NOT NEED TO BE ROOTED IN ORDER TO INSTALL ANY CUSTOM ROM OR RECOVERY, it is optional but recommended…
People usually root beforehand as it helps them to backup their data…and you won't be able to root after you install a custom recovery, since the scripts are made only for stock Samsung recovery
Q) Okay, now how do I root my Galaxy Fit?
A)
If you are running Froyo (android version 2.2.1), then:
Download SuperOneClick (Source Link)
Make sure your phone is connected to the computer via USB, AND your SD card is NOT mounted.
Run the app
When SuperOneClick launches, you’ll see several large buttons at the top of the screen. Make sure that the debugger can “see” it (activity will start logging).
Click “Root” in SuperOneClick.
If you are running Gingerbread (android version 2.3.x), then:
Download this update.zip file (Link)
Place it on the root of sd card (root here meaning “home directory” of your micro-sd card, i.e. the first folder which you get when you open any file explorer)
Make sure the file’s name is “update.zip” (without the “”)
Now reboot into recovery mode
Select the option: “Apply update.zip”
Wait for it to complete, and you are done!
After you have successfully rooted, you will find an app named “Superuser” in your application menu. If not, you can download it from Play Store.
Also, it is advisable to update the app (as well as the superuser binaries, option present in-app) to the latest version available.
Q) How do I unroot my g-fit?
A) There might be various reasons why you would want to unroot your fit (the main one being to recover/reclaim your warranty)
For unrooting (in Froyo), just run SuperOneClick again, and click option “Unroot”.
For unrooting (in GB), you have a few ways: one is a sure-shot way (install/flash stock rom), another works for some and doesn’t work for some (update.zip), and one more is false un-root.
1.Sure-shot way: This method will work all the time, i.e. you will be able to unroot successfully with this method. All you’ve got to do is flash a stock rom, and you will be back to factory settings (and even get your warranty back)
2.Update.zip method: This method worked for some users, and didn’t work for some. In this, you just need to download this file, rename it to “update.zip” and install it the same way as you did to root, i.e. reboot into recovery and apply update.zip
3.False un-root: This isn’t actually unrooting, but is a little trick I used to get my warranty back.
1. First download and install Audio Manager aka Hide It Pro
2. Then use it to hide all your root-related apps (like superuser, titanium backup etc.), and done!
Note: The false un-root method isn’t actually un-rooting, as anyone with enough android knowledge will be able to tell that you still retain root access. The method only hides the notifications that you receive from superuser, when any app is requesting root access. Exercise caution when using this method, as all apps can have root access, and you wouldn’t even come to know about it.
2. Backing up data using Titanium Backup Pro
Since you don’t need to have root access in order to install any custom recovery/rom, hence one of the major reason left to root is to backup your phone settings and data.
You can find plenty of apps on Play Store which can backup AND restore your data, but barely any other app can do it better than Titanium Backup. The free version also does quite a lot of stuff, but in this guide I’ll be explaining how to use the pro-version (v4.8.2), including how to do one-click backup as well as restore, and scheduling backups to run at a pre-defined time automatically.
First, install Titanium Backup Pro
Then, run the app.
(I recommend going through the app settings so that you can tweak it according to your preference)
Now, you can either backup apps (and their data) one-by-one or just backup all of them at once. In order to backup all of them at once, run the app, press menu button > batch > choose option “backup all apps + system data”, and then wait for the backup process to get over.
To restore backups after a data reset, run the app, press menu button > batch > choose option “restore missing app + all system data”.
Note #1: Restore all system data only if you are doing a data wipe. If you have flashed a new ROM altogether, then do not restore system data, only restore missing apps + data, else you will get force closes.
Note #2: Titanium backup automatically store its preferences/settings on your sd-card, and auto restores them after a wipe, so you do not need to bother about it again.
To set-up schedules, run the app, and then go to the “schedules” pane/tab, and then select the ones which were pre-set, or create new ones according to your need.
Titanium Backup has other uses as well (which you can find on your own), but the main important ones have been covered.
Note #3: Use some other app to backup and restore your contacts/call logs/messages...
I use GO Backup or sometimes, MyPhoneExplorer...
3. Installing Stock Roms
First, download the stock rom of your choice from samfirmware.com
Then download beni.ops and Odin Multidownloader
Remove the sim card and memory card of your phone, and put it in download mode
Next, run Odin, and connect your phone to your windows computer. Odin should respond as detected. Then, select “Ops” as beni.ops. (Doing this would disable all other fields except “One Package”)
After this, select your desired stock rom in “One Package”.
Do not alter any other option other than those mentioned, let them remain as they are.
Make sure that the color of “COM PORT MAPPING” is yellow, and then click “Start”.
Odin will start giving different responses, and the timer in Odin would also start…now all you have to do is wait till Odin completes flashing (You will get a message “Pass”, usually within 10 minutes)
Note: Do not disconnect you phone while the process is on, and till you get that “Pass” message.
After this, it is optional but advised that you reboot into recovery mode and wipe data, otherwise you *may* face bootloops.
4. Installing Custom Recovery
Q) I already have stock Samsung recovery. Why do I need a different recovery for?
A) The stock Samsung recovery has a very limited functionality, while other recoveries offer various other functions, and support other (better) filesystems also.
Also, to install any custom rom, you will need a custom recovery.
The most popular and commonly used recovery for Galaxy Fit is ClockworkMod Recovery v5 built by tj_style.
This recovery works with all custom roms, but it does not support backing up and restoring (Nandroid Backups) of stock roms (since samsung stock roms are of rfs filesystem).
Hence, you CAN install this recovery on stock roms, but you won’t be able to take (and restore) nandroid backups of stock roms.
However, pratyush.creed has modified this cwm5 to support backups of rfs (i.e. stock roms), you can get this from here
But for this guide, we will stick to the popular, tried and tested, cwm5 by tj_styles
Your phone needs to be on gingerbread, as this recovery doesn’t work on Froyo.
Note: Even though rooting is not required for installing CWM, it is recommended to do so before, since you can root only from stock recovery, and CWM replaces the stock Samsung recovery.
To install this recovery:
Download the recovery file from the above link.
Also, download beni.ops and Odin Multidownloader
(Beni.ops and Odin are the same files used, so you don’t need to download them again)
Next, run Odin, and connect your phone to your windows computer. Odin should respond as detected. Then, select “Ops” as beni.ops.
Select the recovery file under “One Package”.
Do not alter any other option other than those mentioned, let them remain as they are.
Click “Start”.
Wait till odin completes flashing (might take upto 10 minutes)
Now, after your device has rebooted, restart into recovery mode to confirm that you have successfully installed ClockworkMod Recovery (CWM).
5. Installing Custom Roms
Though Samsung has possibly tried its best to create the best stock roms (compared to other manufacturers), it still has a lot of potential. Custom roms are made to achieve this potential, helping you get more returns from your Fit.
Q) How to install custom roms?
A) Before proceeding, you will need to have any custom recovery installed, since the stock Samsung recovery cannot be used here. Preferably, use CWM5 by tj_style (the one explained above). Also, remember that your phone’s data (not the one stored on sd-card) will be erased/reset, so be sure to make a backup.
Now, download the custom rom of your choice from the Development Section of our sub-forum.
Optional: Check if the zip file you have downloaded is proper (i.e. not corrupt).
To do this, simply use WinZip (Windows) or other similar program to extract the file on your desktop. If the extraction has completed without any errors, then the file is proper, but if you get any errors while extracting, then the file is corrupt and you will have to re-download it.
Now, copy the file onto your sd-card.
Reboot into recovery mode.
Select “wipe data / reset”.
After this completes, select “wipe cache partition”.
After this, select “advanced”>”wipe dalvik cache”.
Now that you have wiped all data, select “install zip from sd” from the main recovery menu, then “choose zip from sdcard”.
[*] Optional, but recommended: Select “mounts and storage”>”format /system”.
(Important, if you are installing any variation of CyanogenMod 7 (cm7) for the first time, or are moving from a stock based custom rom to a cm based custom rom...else you will be stuck on the "android" text screen)
Now select the custom rom that you had placed on your card, and wait for it to install.
Optional: When the install completes, wipe data, cache and dalvik cache again (steps 5,6,7)
Select “reboot system now”, and be prepared to wait till the phone restarts. (Note: first boot may take upto 10 minutes, so do not panic)
Enjoy your new rom!!!
If you want to get back to your stock rom, you will have to flash the stock rom using Odin.
Also, all custom roms are pre-rooted, so you don’t have to bother with rooting again (though you might have to update superuser and its binaries)
For your first custom ROM, I would suggest sticking to stock based custom roms...
Some sim cards aren't compatible for CM7 and CM9/10 (cm = short for CyanogenMod)...we don't know the cause and effect relationship between them, as of yet...
So, if your CM doesn't boot into the homescreen, try removing your sim card...
If it then boots up without any additional steps required, then unfortunately, you belong to the group of people who can't use CM7 with their current SIM...
The only workaround available are:
Use phone without SIM (unrealistic, since it wouldn't do the primary functions of a phone then)
Change your SIM card
Use stock based custom rom's, and forgo CM entirely
6. Creating and Deleting Sd-card Partition
Partitioning sd-card is basically virtually “dividing” your sd card into parts, so that you can use each one separately for different purposes.
So, in easy words, you can virtually increase your phone’s internal memory and ram (both of which are unsatisfactorily low in our device)
However, there is a disadvantage to partitioning, mainly a slightly slowed phone. This “slowdown” is caused mostly if you:
Have a low-speed (technical word = “class”) sd card
Have moved dalvik cache to sd partition that you have created
Have attempted to use a swap partition
But a lot of people don’t mind this slowdown a lot, since a partition allows them to have access to more apps.
Also, you will lose hot-swapability, i.e. you won’t be able to remove your card from your phone, will the phone is running.
Before you proceed, you SHOULD backup all of your data on your card since it will be deleted, as the card will be formatted during the process.
Q) How to create a sd partition?
A) You will need
• A good micro sd-card, with a class greater than 4
(the class is usually printed on the card itself, it’s the number inside the letter ‘C’)
• A rooted galaxy fit running android 2.3.x (preferably on a stock rom), with ClockworkMod recovery
Steps:
Backup all your data.
Reboot into CWM.
Go under “advanced”>”partition sd card”.
Select the size of your second partition (On my first try, I made a partition of 1024MB but found it too big with a lot of space unused, so I deleted the partition and made a new one of 512MB)
This is your choice, choose one depending on the total size of your card, the no. of apps/games you’ll have etc.
After selecting that, select swap size as 0MB (This one also is your choice, but I’ll explain why to take 0MB, and not anything else)
Now wait till the process is completed, and reboot.
As far as I know, CWM v5 makes a partition of EXT3 format, by default.
Q) Why to select swap size as 0MB?
A) Swap partition is made with the objective of utilizing it as VIRTUAL RAM. Now this may sound as a good thing, but in reality the ram in our fit is way faster than the average class 10 micro sd-card. So, instead of speeding up your system, it will slow down your system horribly after a certain point.
So, in short, you shouldn’t be using a swap partition, hence there is no point in creating one if you are not utilizing it.
You are still free to create a swap partition, but I shall not be providing support for that in this thread.
Q) What if I want to delete all my partitions and get back my sd card the way it was?
A) There are a few ways to delete your partitions and reset your card, and I’ll explain the easiest one.
Backup the data on your card.
Make sure your card is in the phone’s card slot, and that your phone is booted/running.
Go into Settings>Storage, then select option “Unmount sd card”
When the card is unmounted, you will be able to select the option “Format sd card” (which you previously couldn’t)
Select the option and wait for it to complete.
If you want to delete the ext partition, I recommend doing it after a clean install of a stock rom. Else, make sure to move all your apps from the ext partition to your phone.
7. Setting up and using Link2sd
Now that you have created an ext partition, you need to make use of it (duh).
There are a lot of ways and scripts to transfer apps from your internal memory to the sd ext partition, but the most consistent method I found was Link2sd.
This method works across all roms (rooted stock and custom, both) that I’ve tried, even on all variations of CyanogenMod7 (CM7) as well as on ICS CM9 and JB CM10, and is very easy to setup and use.
However, if a custom rom already has DarkTremor's a2sd (a2sdgui app will be present) or any similar script, then DO NOT configure them.
For example: Creeds v3 has a2sdgui, and if i want to use Link2sd, then after flashing Creeds, I SHOULD NOT run a2sdgui, and directly install (and configure) Link2sd...if you run/configure a2sdgui, then it will clash with the working of Link2sd.
Similarly, if any custom rom has any memory hack already implemented, then you cannot use Link2sd...
Steps to setup Link2sd:
Download Link2sd from Play Store (it’s a free app).
After it gets installed, run it, and allow root access.
You will get a message to select the format of your sd partition, select “ext3”.
Link2sd will then automatically create mount scripts that it requires to work, and will then tell you to reboot your phone.
Do a proper reboot, and not a ‘hot reboot’.
After rebooting, open up Link2sd, press menu then select “settings”.
Select/check the options “automatically link newly installed applications to sd”, “auto link notification”, “relink lib files at boot” (and “fast scroll”, if you want).
For “install location” option, select “internal”.
Then go to “auto link settings” and select/check all the three options (you can skip/ unselect “link dalvik-cache file” if you wish)
Done
Now, every new app that you will install will automatically be moved to your sd ext partition.
Link2sd is also an excellent (and fast loading) app manager, with which you can freeze, uninstall, re-install…though you can move only user apps to sd-ext partition.
Also, there is no point in having your entire phone memory empty, so you probably should unlink the dex (dalvik cache) of your apps. I usually link only the apk and lib files, and leave the dex files unlinked and on the phone storage, so as to avoid any sluggishness in operation., though if your phone memory still fills up, you can link the dex of your rarely-used apps, and leave the dex of important and frequently used apps on the phone storage.
Suppose a custom rom has s2e/app2sd pre-implemented, then after a fresh install, FREEZE the app (rather than uninstall), and then install Link2sd...
Also, if you get error "mount script not created", then choose partition as ext4 (rather than ext3 mentioned below), even though your partition might be ext3...(don't know why this happens with some roms )
If on some ROM, you get “device/resource busy”, then you need to format your SD-EXT partition from CWM (should be under “mounts and storage”)
[DO NOT confuse this with deleting and re-creating a partition]
8. Installing apk’s through root explorer method.
At times, some of your apk files won’t get installed in the normal way, so you can use this approach to install them. This method is coomonly referred to as "root explorer method".
For this, you will need:
•A rooted phone
•Root Explorer or any other file manager.
Since root explorer isn’t a free app, you can use this free File Manager (my personal preference).
If you are unable to uninstall a newer version of any app, then first uninstall the old version, and then use this method.
Steps:
Get the apk file of the app that you want to install.
Now launch Root Explorer
On the top left side, it will be written as “Mount as r/w”, click that, and allow root access. (basically mount system as read and write, if you are using other file managers)
Now place the apk file at either /data/app or /system/app (if you want it as a system file)
Now set appropriate permissions (For /data/app, the default permissions are rwx rwx rwx and for /system/app, the default permissions are rw- r-- r--)
Reboot your phone, and then check your app drawer, you will find your app installed.
12. Bootloops:
If you have flashed any custom rom/recovery/hack/kernel/update.zip, and unfortunately, have got stuck in a bootloop (i.e. you cannot reach the app launcher as the phone keeps rebooting again and again), then before asking for help, do try wiping data, cache, and dalvik cache from recovery mode...
This should stop bootloops (in lots of cases)...
13. How to reclaim warranty?
Let's just say you need your warranty back for some reason...but have done any of the above stuff (which voids your warranty)...
Then all you got to do is flash any stock rom (preferably, of your region), and you will have your warranty back
(This, ofcourse, assumes that you had warranty, in the first place)
14. Battery care
A lot of people have said that their battery has swollen. If this is the case, then this could be dangerous for YOUR HEALTH.
If this happens, you SHOULD replace your battery.
Q) Why would the battery swell up?
A) My phone's battery looks safe enough, so I do not know the perfect cause. But from the users who complained about this, I did notice that most of them just leave their phones plugged in, unattended, for more than 4-5 hours at end (Usually, they just leave it to charge overnight)
So, if you do this on a regular basis, then watch out!
Q) How do I know if its swollen?
A) To know if its swollen, just see if the battery surface is smooth or not, from all the sides. If there is any swelling, you will notice it.
Also, if you get REALLY POOR battery life, (only 3-4 on single full charge, with light usage), then this could be an indication that you have battery problems. [Just to confirm, ask other fellow users how much usage they get on that rom and baseband, since this could happen due to ROM and kernel also.]
Q) What do I do if it's swollen?
A) There is no other option but to replace the battery with a new one. I STRONGLY ADVICE to buy them from your local Samsung Service Center. Avoid online sellers, or other 3rd party batteries, as they may not be proper.
Q) Any precautions that can be taken?
A) Yup, DO NOT LEAVE YOUR PHONE TO CHARGE FOR LONG PERIODS, ALL THE TIME.
That's what has been deduced from the people who have complained.
Take Care!!
9. Nandroid Backups
Q) What are Nandroid Backups?
A) Nandroid Backups are like an exact copy image of your phone’s state, saved on your sd card. It stores all your apps, data, settings, sd-ext etc. of the phone (obviously, the state when you took the backup). Nandroid Backups are a very convenient way to restore your data after something has gone wrong (or want to change between roms), and their size can be anywhere starting from 150mb+.
If you want to test some stuff from the development section (like different mods/hacks/scripts), it is advisable to make a Nandroid Backup before you proceed...
Q) How to make Nandroid Backups?
A) Perquisites to make a nandroid backup:
•ClockworkMod Recovery (any version) on your galaxy fit.
•Plenty of free space on your sd card (this depends on how many apps you have, my backups usually average around 450-500 MB)
Steps:
Do a clean reboot into ClockworkMod Recovery (i.e. shutdown properly, then reboot into recovery mode)
Go to “backup and restore”>”backup”
Wait for the process to get completed, and you are done!
The backup that you just made has been saved to your sd-card, in a folder named clockworkmod (complete location is /mnt/sdcard/clockworkmod/backup).
Restoring:
Now, suppose, while flashing any rom, you are stuck in a never-ending bootloop, and you have wiped everything (i.e. data, cache, dalvik cache), and just want to get back the way it was, then just follow these steps to restore:
Boot into CWM
Wipe data, cache, and dalvik cache (optional, but recommended).
Go to “backup and restore”>”restore”, and then select your backup.
Wait for it to complete (time taken depends on the size of your backup, which in turn depends on the number of apps that you had installed), and reboot
You will find that you are now back to last state before you did that backup, with all your apps, settings etc. the way it was left.
If you keep more than one nandroid backup, you may find it confusing to remember which one is what…
So you can rename them in the following way:
Suppose the default name of my backup of a cm7 rom is 2012-03-29.14.04.59 , then I can rename it as cm72012-03-29.14.04.59
In this way, if you ever get a md5 mismatch error while restoring, then you can simply edit it back to the way it was.
However, if you still get an md5 mismatch error, then you can use this method suggested by fellow xda member, arhant. Though if the backup wasn’t created by you (i.e. you took it from someone else), then exercise caution while doing this.
10. Overclocking
Q) What is overclocking?
A) Overclocking refers to running your processor above the “safe” limit set by Samsung (or the manufacturer, in general). This limit is usually set so that the battery life is extended, less overheating problems occur as well as minimum possible damage is done to the processor in the long run.
Why to overclock:
Helps make Fit more “usable”, i.e. makes launcher smooth, games a little less laggy etc.
Why not to overclock (Most of this happens only if you don’t overclock properly):
Poor battery life
Abnormal heating of the phone
Increased instability
Q) How to overclock (oc) Galaxy Fit?
A) In order to overclock Galaxy Fit, you need to have a custom kernel, as the stock kernel doesn’t support overclocking, as well as root access.
Note: Stock roms can be overclocked! They just need another kernel, the in-built kernel cannot be overclocked.
• If you want to overclock on stock (at your own risk), you can flash any kernel from this via cwm (so, obviously you need cwm, stock recovery won’t do).
• Most custom roms have oc kernel in-built, so you usually don’t need to flash anything extra.
After you have a custom overclock-able kernel, you just need to install either No-frills CPU Control or SetCPU for Root Users (No-frills is free ) or any other such app, run them, and select the desired max frequency, governor, and i/o scheduler. (Don’t set the max frequency above 800+ mhz, unless you know what you are doing)
You have to use trial-and-error to find out the combination of governor, i/o scheduler, and max frequency, which suits your need…and you will get different results on different kernels, roms and basebands, so keep experimenting.
11. Bricked phone
Q) What do you mean by a "bricked" phone??
A) A "bricked" phone is a phone which cannot start normally, AND cannot be rebooted into both, the recovery mode as well as the download mode...thus, effectively, it becomes just a paperweight, i.e. a brick
It is more of a "state" your phone can go into, if you do things wrong...
If your phone can enter recovery mode OR download mode, then it is not bricked!
You can try and fix it yourself!
If your phone can enter recovery mode, (and assuming you have a custom recovery installed), then you simply have to flash any custom rom to get your phone back in working condition.
If your phone can enter download mode, then you can install any stock rom (via odin), to get back your phone in working condition.
Note: These solutions are general in nature, i.e. they will work for the majority of cases, but may not work for some.
HOWEVER, IF YOUR PHONE IS BRICKED,
Then there is nothing much that we can do...only the samsng service center will be able to repair it (they replace the motherboard).
15. Android Debugging Bridge (ADB)
To put it simply, adb is two different applications - one running on your computer (Windows, Linux or Mac) and one running on your phone (which you don’t have to bother about). When your phone is connected, and USB debugging is enabled, you can issue commands and communicate with the phone using your computer screen and keyboard.
Your Android phone uses a modified Linux kernel and tools as a base. This means that quite a few Linux commands can be sent via the adb server (the one running on your computer) to the adb client (the one running on your phone) and they will be executed. – Android CentralQ) How do I setup ADB on my Windows PC?
A) With the help of my friend wilfredcool007, I have made a really simple method to use adb and also provided some tools for hassle-free logcats. This method is portable in nature (you do not have to install any untrusted application), does not need large downloads, neither the full Android SDK installation. You will just have to download a small compressed file, which is all that you require.
Thank You Wilfred!
Make sure you have the device drivers installed beforehand. If you have been following this guide since the beginning, you will have it on your computer. If not, just simply refer the beginning of this thread.
Steps:
Download this file: ADB & Logcat Tools.zip
Extract the .zip file to any suitable location, wherever you wish. I extracted it on to C:\Android Debugging Bridge just so that it’s easy to remember where it is.
Now, once you’ve extracted the zip, you will find 7 files in it [of which the 3 files named as “Logcat xxxxxx”, and “dmesg”, will be used in the later part of this guide for making logcats].
To launch ADB, just hold the “Shift” key and right click on a blank area in the folder, and in the drop down menu which follows, select the option “Open Command Window Here”.
And you’re done! Now you can use any of the adb commands that you wish! It really is this simple!
Some common ADB commands are:
Code:
adb devices – list all connected devices
adb push <local> <remote> – copy file/dir to device
adb pull <remote> [<local>] – copy file/dir from device
adb sync [ <directory> ] – copy host->device only if changed
adb shell – run remote shell interactively
adb shell <command> – run remote shell command
adb emu <command> – run emulator console command
adb logcat [ <filter-spec> ] – View device log
adb forward <local> <remote> – forward socket connections forward specs are one of: tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp – list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> – push this package file to the device and install it
adb uninstall [-k] <package> – remove this app package from the device (‘-k’ means keep the data and cache directories)
adb bugreport – return all information from the device that should be included in a bug report.
adb help – show this help message
adb version – show version num
adb wait-for-device – block until device is online
adb start-server – ensure that there is a server running
adb kill-server – kill the server if it is running
adb get-state – prints: offline | bootloader | device
adb get-serialno – prints: <serial-number>
adb status-window – continuously print device status for a specified device
adb remount – remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] – reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader – reboots the device into the bootloader
adb root – restarts the adbd daemon with root permissions
adb usb – restarts the adbd daemon listening on USB
More information regarding some common ones will come soon.
You can also refer Google’s Official Page too.
16. Logcats
A lot of time, you'll see developers asking for logcat. Viewing a logcat is usually the best, and in some cases, the only way to diagnose a problem.
You can do it two ways:
Within the device, through apps like aLogcat or Catlog or any other application that is capable of logging (This is self explanatory, all you got to do is download and run the app, and the app will do the work. Do check out the options to tweak out the settings and other stuff. I shall not be providing help for these in this thread.)
With ADB (explained further)
Thanks to the zip provided in the previous step, it’s really easy to do so via adb.
Steps:
If you haven’t downloaded it already, do download the ADB & Logcat Tools.zip (it’s the same file mentioned above) and extract it to a suitable location.
You have two options now.
You can either run adb as explained above and use the command
Code:
adb logcat >logcat.txt
There will be no further activity on the screen, but the logging will start. Recreate the problem that you wanted, and when you need to stop the logcat, just press “Ctrl” + “C” [Hold Ctrl and press C], and then press “Y” and “Enter” key to stop logging.
You will notice that a file named logcat.txt has appeared, and when you open the file in Notepad, you shall see its contents.
Example:
Code:
--------- beginning of /dev/log/system
I/ActivityManager( 1019): Starting: Intent { flg=0x14000000 cmp=com.whatsapp/.Conversation (has extras) } from pid 18867
D/VoldCmdListener( 891): volume shared /mnt/sdcard ums W/ActivityManager( 1019): Activity pause timeout for HistoryRecord{405690f0 com.whatsapp/.Conversation}
D/VoldCmdListener( 891): volume shared /mnt/sdcard ums
I/ActivityManager( 1019): Starting: Intent { flg=0x14000000 cmp=com.whatsapp/.Conversation (has extras) } from pid 18867
W/InputManagerService( 1019): Starting input on non-focused client [email protected] (uid=10080 pid=18867)
D/VoldCmdListener( 891): volume shared /mnt/sdcard ums
D/VoldCmdListener( 891): volume shared /mnt/sdcard ums
D/MusicControls( 1279): Updating Music Controls Visibility
D/MusicControls( 1279): Music is not active
W/InputManagerService( 1019): Window already focused, ignoring focus gain of: [email protected]
D/MusicControls( 1279): Updating Music Controls Visibility
D/MusicControls( 1279): Music is not active
W/InputManagerService( 1019): Window already focused, ignoring focus gain of: [email protected]
D/StatusBarService( 1279): DISABLE_CLOCK: yes
D/StatusBarService( 1279): DISABLE_NAVIGATION: yes
W/ProcessStats( 1019): Skipping unknown process pid 26719
I/ActivityManager( 1019): Start proc mobi.mgeek.TunnyBrowser:DolphinNotification for service mobi.mgeek.TunnyBrowser/com.dolphin.browser.message.C2DMService: pid=26767 uid=10119 gids={3003, 1015, 1007}
I/ActivityManager( 1019): Process com.google.android.talk (pid 18915) has died.
I/ActivityManager( 1019): Process mobi.mgeek.TunnyBrowser:DolphinNotification (pid 26767) has died.
W/ProcessStats( 1019): Skipping unknown process pid 27439
I/TelephonyRegistry( 1019): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=null interfaceName=null networkType=2
I/TelephonyRegistry( 1019): notifyDataConnection: state=1 isDataConnectivityPossible=true reason=null interfaceName=null networkType=2
I/ActivityManager( 1019): Start proc com.google.android.apps.uploader for broadcast com.google.android.apps.uploader/.ConnectivityBroadcastReceiver: pid=27556 uid=10005 gids={3003}
Logcats get longer the longer they run. So it is advisable that you run the logcat and immediately proceed to recreate the problem.
Also, paste the resulting logcat on sites like Pastebin and share the link to the dev!
Now, you must be wondering what the rest of the files in the Zip were for…
Well, those files are pre-configured commands for logcats to run. All that has to be done is double click the .bat files, and logging shall start. To stop logging, as stated above, press CTRL+C, then Y and ENTER.
Remember: Do delete/rename/move the output logcat file before creating a new logcat with the following files.
Files:
Logcat 1 (Long and Detailed).bat : Normal Logcat command. Same result as the example given above.
Logcat 2 (Short and Errors only).bat : Shorter Logcat command. Omits out Verbose, Debug and Info. Displays/Filters only Warning, Error And Fatal. Useful when logcat duration is very long, as this displays only the error and fault messages. Example:
Code:
--------- beginning of /dev/log/system
11-13 12:13:40.099 1019 1019 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 12:20:34.359 1019 1360 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 12:22:31.069 1019 1045 W ActivityManager: Activity pause timeout for HistoryRecord{4085daf8 com.quoord.tapatalkxdapre.activity/.forum.ForumNavigationActivity}
11-13 12:23:42.009 1019 1402 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 12:28:36.779 1019 28921 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 12:31:20.980 1019 1402 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 12:58:05.899 1019 1057 W ProcessStats: Skipping unknown process pid 29887
11-13 13:06:11.630 1019 1045 W ActivityManager: Activity pause timeout for HistoryRecord{405d5100 com.android.phone/.InCallScreen}
11-13 13:06:14.400 1019 26640 W WindowManager: Layout repeat skipped after too many iterations
11-13 13:06:14.400 1019 26640 W WindowManager: Layout repeat skipped after too many iterations
11-13 13:06:14.400 1019 26640 W WindowManager: Layout repeat skipped after too many iterations
11-13 13:06:14.400 1019 26640 W WindowManager: Animation repeat aborted after too many iterations
11-13 13:06:14.420 1019 1211 W WindowManager: Layout repeat skipped after too many iterations
11-13 13:06:14.750 1019 1211 W WindowManager: Animation repeat aborted after too many iterations
11-13 13:06:21.069 1019 1045 W ActivityManager: Activity idle timeout for HistoryRecord{405d5100 com.android.phone/.InCallScreen}
11-13 13:17:41.240 1019 28924 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:02:27.259 1019 1328 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:06:00.389 1019 1330 W ActivityManager: Scheduling restart of crashed service com.whatsapp/.messaging.MessageService in 5000ms
11-13 14:06:03.459 1019 28922 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:09:21.689 1019 21101 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:09:23.329 1019 1330 W ActivityManager: Scheduling restart of crashed service com.jim2/.UpdateService in 5000ms
11-13 14:09:35.339 1019 1045 W ActivityManager: Launch timeout has expired, giving up wake lock!
11-13 14:09:35.399 1019 1057 W ActivityManager: Process ProcessRecord{406b4718 32036:com.imgurforandroid/10108} failed to attach
11-13 14:09:41.639 1019 1045 W ActivityManager: Activity pause timeout for HistoryRecord{4050c488 com.imgurforandroid/.activity.LaunchUploadUi}
11-13 14:09:41.679 1019 1034 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:10:23.679 1019 1033 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:11:00.629 1019 28924 W ActivityManager: startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { cmp=com.imgurforandroid/.activity.ImageDetails bnds=[0,138][240,189] (has extras) }
11-13 14:11:25.639 1019 1033 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:11:58.979 1019 1045 W ActivityManager: Activity pause timeout for HistoryRecord{408690f0 com.quoord.tapatalkxdapre.activity/.forum.ForumNavigationActivity}
11-13 14:12:26.129 1019 1360 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:13:20.449 1019 1402 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:13:53.159 1019 28922 W ActivityManager: Duplicate finish request for HistoryRecord{407186d8 com.quoord.tapatalkxdapre.activity/.forum.ForumNavigationActivity}
11-13 14:36:20.180 1019 1034 W InputManagerService: Window already focused, ignoring focus gain of: com.andr[email protected]
11-13 14:36:23.110 1019 1034 W ActivityManager: Scheduling restart of crashed service com.imgurforandroid/.ImgurUploadService in 5000ms
11-13 14:36:53.479 1019 26640 W InputManagerService: Starting input on non-focused client [email protected] (uid=1001 pid=1304)
11-13 14:36:56.649 1019 1033 W BackupManagerService: dataChanged but no participant pkg='com.android.providers.settings' uid=10092
11-13 14:36:56.799 1019 1328 W BackupManagerService: dataChanged but no participant pkg='com.android.providers.settings' uid=10092
11-13 14:37:58.840 1019 1330 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
11-13 14:43:51.779 484 509 E ActivityThread: Failed to find provider info for com.opera.branding.BrandingProvider
11-13 14:43:51.779 484 509 E ActivityThread: Failed to find provider info for com.opera.branding.BrandingProvider
11-13 14:43:51.789 484 510 E ActivityThread: Failed to find provider info for com.opera.branding.BrandingProvider
Logcat 3 (Radio related only).bat : Displays only messages related to radio (telephony). Useful whenever your developer asks for a Radio logcat. Example:
Code:
D/RILJ ( 1304): [1876]> QUERY_NETWORK_SELECTION_MODE
D/RILJ ( 1304): Serial: 1875
D/RILJ ( 1304): Error: 0
D/RILJ ( 1304): [1875]< REGISTRATION_STATE {1, 1777, 0000d72a}
D/RILJ ( 1304): Serial: 1876
D/RILJ ( 1304): Error: 0
D/RILJ ( 1304): [1876]< QUERY_NETWORK_SELECTION_MODE {0}
D/GSM ( 1304): Poll ServiceState done: oldSS=[0 home TATA DOCOMO TATA DOCOMO 405039 EDGE CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] newSS=[0 home TATA DOCOMO TATA DOCOMO 405039 EDGE CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] oldGprs=0 newGprs=0 oldType=EDGE newType=EDGE
D/GSM ( 1304): [DataConnection] Stop poll NetStat
D/GSM ( 1304): [DataConnection] Start poll NetStat
D/RILJ ( 1304): [1877]> SCREEN_STATE: false
D/RILJ ( 1304): Serial: 1877
D/RILJ ( 1304): Error: 0
D/RILJ ( 1304): [1877]< SCREEN_STATE
D/GSM ( 1304): [DataConnection] Stop poll NetStat
D/GSM ( 1304): [DataConnection] Start poll NetStat
D/RILJ ( 1304): [1878]> SCREEN_STATE: true
D/RILJ ( 1304): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
D/RILJ ( 1304): Serial: 1878
D/RILJ ( 1304): Error: 0
D/RILJ ( 1304): [1878]< SCREEN_STATE
D/RILJ ( 1304): [1879]> OPERATOR
D/RILJ ( 1304): [1880]> GPRS_REGISTRATION_STATE
D/RILJ ( 1304): [1881]> REGISTRATION_STATE
D/RILJ ( 1304): Serial: 1879
D/RILJ ( 1304): Error: 0
D/RILJ ( 1304): [1879]< OPERATOR {TATA DOCOMO, TATA DOCOMO, 405039}
D/RILJ ( 1304): [1882]> QUERY_NETWORK_SELECTION_MODE
Dmesg.bat : Prints messages from the kernel, useful as tool for debugging drivers and other kernel code. Use this whenever the developer asks to get a dmesg output. Example:
Code:
# c027ce40 : [HSIL] mdp_suspend_sub(1387) will cancel_delayed_work
<4>[34607.196686] [HSIL] mdp_suspend_sub(1391) will flush_workqueue
<4>[34607.196731] [HSIL] mdp_suspend_sub(1395) will atomic_read
<4>[34607.196773] [HSIL] mdp_suspend_sub(1400) will mdp_pipe_ctrl
<4>[34607.196816] [HSIL] mdp_suspend_sub(1402) after mdp_pipe_ctrl
<6>[34607.196854] # c03d7894 :
<6>[34607.196883] # c03d7894 :
<6>[34607.196909] # c03cb4a0 :
<6>[34607.196939] early_suspend: after calling suspend handlers
<6>[34607.205456] early_suspend: after calling sync_work_queue
<6>[34607.205508] early_suspend: abort label / before spin lock
<6>[34607.205564] early_suspend: unlocked main_wake_lock
<6>[34607.205599] early_suspend: end
<4>[34607.205636] [BACLKIGHT] : 17
<4>[34607.205668] Platform V:17, Find V:1
<4>[34607.205714] LCD Backlight re-init - wakeup time tune:1, lcd:32
<4>[34607.205926] [BACLKIGHT] : 15
<4>[34607.205956] Platform V:15, Find V:1
There you have it! Life made simpler, just double click and you are done!
Q) What’s the difference between Logcat and Dmesg?
A) Read this for info.
Hope this guide helped you.
I appreciate feedback and constructive criticism, but please, no “haters”/”trolls”.
Whatever questions/doubts you have regarding this guide, then please post it here itself…I don’t guarantee replying tech support questions via pm .
Do consider clicking on the “thanks” button rather than just posting thanks, and also joining us on our Facebook Group
a.cid said:
...
• If you want to overclock on stock (at your own risk), you can flash any kernel from this via cwm (so, obviously you need cwm, stock recovery won’t do)....
Click to expand...
Click to collapse
Pratyush mentioned in:
http://forum.xda-developers.com/showpost.php?p=24719114&postcount=1387
a cwm for rfs / see download-link, therefore exists in theory the possibility to oc stock-roms.
zcop said:
the first troll here hehe
What is s5670? Can i eat it?
Ok good work for newbie - who messup forum
Click to expand...
Click to collapse
Idk what s is, but 5670 are part of the number series...
You know 1 2 3 4 5 6 7 0
martin_s5670 said:
Pratyush mentioned in:
http://forum.xda-developers.com/showpost.php?p=24719114&postcount=1387
a cwm for rfs / see download-link, therefore exists in theory the possibility to oc stock-roms.
Click to expand...
Click to collapse
Ohhh sorry I totally forgot about that...will update the thread tomorrow from comp...
But I haven't tried it personally :/
And other recoveries (like the touch ones) give errors while flashing a few stuff...
Sent from my g-fit using xda premium
martin_s5670 said:
Pratyush mentioned in:
http://forum.xda-developers.com/showpost.php?p=24719114&postcount=1387
a cwm for rfs / see download-link, therefore exists in theory the possibility to oc stock-roms.
Click to expand...
Click to collapse
Ohhh wait, stock rom can be oc'ed, if you install another custom kernel...
That rfs support is for backups and restore...
The post will be clearer after I'll update it...
Sent from my g-fit using xda premium
Aspire said:
Nice, but the links aren't working.
Click to expand...
Click to collapse
Which ones??
Edit: oh okay, will fix them
Thank you
Sent from my g-fit using xda premium
Aspire said:
Nice, but the links aren't working.
Click to expand...
Click to collapse
Deleting
xn--http-fb7a//
in adress helps!
martin_s5670 said:
Deleting
xn--http-fb7a//
in adress helps!
Click to expand...
Click to collapse
Links updated...
i had typed in this in ms word, and it has messed around with the foramtting...
anyways, if you still find something wrong, do inform me
edit: added pratyush's recovery, as well as updated post to clarify...
a.cid said:
...
edit: added pratyush's recovery, ...
Click to expand...
Click to collapse
Pardon, its not pratyush's recovery, ..its of tj's !, see:
http://forum.xda-developers.com/showpost.php?p=24749890&postcount=1392
martin_s5670 said:
Pardon, its not pratyush's recovery, ..its of tj's !, see:
http://forum.xda-developers.com/showpost.php?p=24749890&postcount=1392
Click to expand...
Click to collapse
I know
The most popular and commonly used recovery for Galaxy Fit is ClockworkMod Recovery v5 built by tj_style.
This recovery works with all custom roms, but it does not support backing up and restoring (Nandroid Backups) of stock roms (since samsung stock roms are of rfs filesystem).
Hence, you CAN install this recovery on stock roms, but you wont be able to take (and restore) nandroid backups of stock roms.
However, pratyush.creed has modified this cwm5 to support backups of rfs (i.e. stock roms), you can get this from here
But for this guide, we will stick to the popular, tried and tested, cwm5 by tj_styles
Click to expand...
Click to collapse
a.cid said:
I know
...
However, pratyush.creed has modified this cwm5 to support backups of rfs
...
Click to expand...
Click to collapse
I said, not prat has modified, its tj's.
first of all I really thank you for this wonderful guide...
btw,the main reason to write this post -
what difference does it make if i select EXT4 instead of EXT3 while partitioning SD card
thnx
yzak58 said:
first of all I really thank you for this wonderful guide...
btw,the main reason to write this post -
what difference does it make if i select EXT4 instead of EXT3 while partitioning SD card
thnx
Click to expand...
Click to collapse
The cwm mentioned in my post doesn't give you the option to select ext3 or ext4
It, by default, partitions it to ext3...
Typed on a small touchscreen
Hey friend.. i m unable to root my mobile...
I have installed "GINGERBREAD.DXKT7 2.3.6"
So please say how can i root this stock rom...
akash6448 said:
Hey friend.. i m unable to root my mobile...
I have installed "GINGERBREAD.DXKT7 2.3.6"
So please say how can i root this stock rom...
Click to expand...
Click to collapse
Can you list the steps you did?
Also check if you have downloaded the update.zip correctly (simply try and extract it on your comp)...
Typed using a small touchscreen
Related
***Informative Threads***Post your question / issue / success story / etc. in the appropriate threads instead of starting a new thread!
Do NOT post a new thread to ask a QUESTION!!!
If your post has a question mark in it, you most likely need to post your thread in the Q&A Section
Please follow xda-developers forum rules and be courteous to all members.
Common sense goes a long way -- if in doubt check out All~G1's pointers on Dev Forum Etiquette
[Build Indexes] - Don't ask which build is best -- choose for yourself based on the features you desire!
androidspin.com
SimonNWalker & a group of Android Community members are maintaining a site which showcases the feature sets of the latest and greatest android builds ("roms" if you prefer). Check here to see "which is best" and try them out for yourself. The site is also ripe with news about Android development and more. XDA Thread
Google Docs Build Spreadsheet - View and edit build info - Google Docs Build Spreadsheet
[Guides/Tutorials/Info]
HTC Dream overview and useful information - Wiki article
Highly recommended for beginners.
In the beginning... There was ROOT
Lots of good definitions, history, and an excellent overview of most things going on here.
SPLs for DREA100 & DREA110 (Orig, Eng, Hard)
Contains information and downloads for SPLs (Secondary Program Loader) for the Dream. A modded SPL is instrumental in restoring from backup, preventing a brick, applying builds designed for foreign markets, etc.
Nandroid v2.0 - Full NAND backup and restore tool
In-depth discussion of your best friend whilst modding your android device. A good Nandroid backup regimen will pay dividends to keep you up and running.
Basic adb/root commands for noobs
Using ADB and terminal commands for your Android phone.
Surviving a Data Wipe / Update (Reduces Force Closes, too!)
Save (most of) your data while switching between builds (wipes are not your enemy!!)
Cyanogen's recovery partition
Amon_Ra's Recovery Partition
Modded recovery and boot images
SDSPLIT repartition your SDcard on phone (w/o a PC) - NOW handles > 2G FAT!!!
An easy way to re-partition your SD card without a PC.
LucidREM's Latest JF mod scripts
The swiss army knife of build customization
Auto-lucid script by tehseano
Let's fix that SPL Pay attention too post 3
Report in here if your phone is unresponsive after applying the 1.33.2005 SPL released by Haykuro. If you can get into Recovery or the SPL bootloader screen (three skateboarding androids), this is not you.
ROM guide for HTC Dream
T-Mobile G1 User Guides/Manuals
HTC Dream Wiki
"Brick" Thread or Technical Think Tank for Bricked G1's
If your phone is stuck at your splash screen (most likely a big white "G1")...if you you think something is broken...if you otherwise think you have a brick, post here instead of starting a new thread and any online members will do everything they can to help you out. (Reading as much as possible of these threads before posting will give you lots of insight as well!!)
Benchmark your build (apps thread)
[HOW TO]
STOCK-2-CYANOGEN / Root, Recovery, Radio, Rom / Partition SD / FAQ
How To Partition SD Card With Ubuntu For Dummies
Partition sdcard w/parted,goto ext3/4 & install rom from adb. no liveCD req'd
UNROOT, get phone to STOCK firmware
Reverting back to stock firmware.
New and improved Apps to SD(more stable, more powerful, etc)
The latest tutorial on how to get apps to SD.
Convert and mount ext2 sd partition ( /system/sd ) to ext3
Tools and instructions to add journaling to your ext sd card partition (apps2sd, etc). trust me, journaling is a good thing!
Register the G1 without a sim or data plan
Increase Max Volume -- Automated, no reboot needed
ADB for Dummies Supported Operating Systems Drivers and SDK
Get Home Auto Rotate on JFv1.51
Unpack, Edit, and Repack Boot Images
Create and edit "recovery" and "boot" .img files -- this thread is not for splash images.
Custom SPLASH Image
Replace that G1 splash logo that displays when your device turns on.
Alternative way to creating a SPLASH image
View Man Pages in terminal / adb shell
Mount SD card in recovery via adb
Use ash as your login shell
[MOD]user configurable userinit.sh V0.1.4.1 for CM
config file for setting up compcache, tweaks, etc. at boot
[How to] mount SD card in recovery.
Ported Hero Programs:
HTC Camera
HTC Music
***Developer Links***
Developers - Instead of maintaining a list of builds, I've changed this list to include links to your publications (blog, twitter, main release thread, etc.) let me know when / if you want these modified or if any should be added -- I'm sure I've missed some of you!
JesusFreke's Blog
Haykuro's Blog
TheDudeOfLife's google code page
Cyanogen's Twitter
TwistedUmbrella's Twitter
justanothercrowd's twitter
Stericson's twitter
For links / info on particular builds, check out the AndroidSpin or the Google Docs Build Spreadsheet
This index will be updated as needed.
Please keep comments on topic!
-Thread Stuck-
Other stickies un-stuck.
Please do not post in this thread unless you have a suggestion on how to improve it. Off topic and dealt with requests will be deleted without warning.
Oh, and thanks alapapa.
Enjoy
Dave
An improvement
The Threads should be in catagories.
Such as:
[How To]
1
2
3
[Guides/Tuts]
1
2
3
[Info]
1
2
3
and so on with different catagories.
something like that would be helpful to this post to quickly find relevent topics.
Thanks for reading.
here is a pretty sweet guide to android OS development, hopefully someone will find it useful
http://pdk.android.com/online-pdk/guide/index.html
I just thought I would whip up a quick informational post here regarding people saying "this does not work", or "this app FCs", etc. Posting something that just says "this is not working" tells us absolutely nothing. We need more information, and that is why God (Google) invented adb and logcat.
I am going to assume that to get to this point, you at least have ADB configured correctly. If not, do it. You can find detailed instructions here: http://forum.xda-developers.com/showthread.php?t=532719.
Once you have that set up and configured correctly, you can begin to post more informative posts in regards to something not working.
'logcat' is your best friend. Do not be afraid to use it. All you need to do is run 'adb logcat' from your command prompt. If ever I am at my desk, I have my phone plugged in and logcat running to see what is going on in the background. Normally, you will just see the standard items such as resource allocation, email queries, and things relating to applications you have running.
At the beginning of each line in logcat, you will see I/, D/, W/, or E/. They designate what type of message it is.
I: Information
D: Debug
W: Warning
E: Error
When an application crashes, you will see a lot of D/ and E/ lines, with some W/ thrown in for good measure. That is the information that is needed to help diagnose the problem, and hopefully create a fix for it.
Here is an example of a helpful logcat that should be posted when you say "it no workie":
Code:
I/ActivityManager( 277): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.androi
d.apps.googlevoice/.SplashActivity }
I/ActivityManager( 277): Starting activity: Intent { cmp=com.google.android.app
s.googlevoice/.LoginActivity (has extras) }
W/ResourceType( 441): No package identifier when getting name for resource numb
er 0x00000000
E/JavaBinder( 441): *** Uncaught remote exception! (Exceptions are not yet sup
ported across processes.)
E/JavaBinder( 441): android.content.res.Resources$NotFoundException: String res
ource ID #0x0
E/JavaBinder( 441): at android.content.res.Resources.getText(Resources.java:
200)
E/JavaBinder( 441): at android.content.res.Resources.getString(Resources.jav
a:253)
E/JavaBinder( 441): at android.content.Context.getString(Context.java:149)
E/JavaBinder( 441): at com.google.android.googleapps.GoogleLoginService$Acco
untAuthenticatorImpl.getAuthTokenLabel(GoogleLoginService.java:586)
E/JavaBinder( 441): at android.accounts.AbstractAccountAuthenticator$Transpo
rt.getAuthTokenLabel(AbstractAccountAuthenticator.java:155)
E/JavaBinder( 441): at android.accounts.IAccountAuthenticator$Stub.onTransac
t(IAccountAuthenticator.java:123)
E/JavaBinder( 441): at android.os.Binder.execTransact(Binder.java:287)
E/JavaBinder( 441): at dalvik.system.NativeStart.run(Native Method)
I/ActivityManager( 277): Displayed activity com.google.android.apps.googlevoice
/.LoginActivity: 158 ms (total 158 ms)
I/DumpStateReceiver( 277): Added state dump to 1 crashes
D/dalvikvm( 894): GC freed 365 objects / 24000 bytes in 132ms
That information may not provide every piece of information we need, but it gives a good starting point as to where to begin to look.
EDIT: If this needs to be put into another location or shouldn't be posted to begin with, feel free to move/delete it.
Custom thread
Threads should be in a bulleted format indicating first the subject which is to be discussed. Under it lies the sub bullets in which gives information to the subject as well as the problem to be solved. Facts should be stated then the resolution would come last. Just like solving a simple problem.
theblogpostwriters.com
Firstly I am posting this with permission of [email protected] Modaco. All props go to him for the origina JIT files - buy him a beer or summat.
Original Thread (Modaco)
For all those asking what JIT is this is a good explanation:
What is JIT for Android
Please don't flood the thread asking what JIT is - Google is your friend.
Disclaimer: I will not be held responsible for any damage to your phone, your PC or indeed your life from following this guide. The steps in this guide worked for me. Doing this kind of thing could affect your warranty and all that so have a long hard think about it before you go ahead. If anything goes wrong and you get into a bootloop or something then use my debricking guide posted in this forum. Make a backup first by Tenfars Clockwork Mod for Defy
After I attempted JIT in a half arsed way previously and not getting good results (force closes etc). Antibyte has done it the right way and compile his "Frozen Eclair" JIT package.
NB: if you have removed apps this will add them back in as it is based on all the apps from the stock rom.
Ok So this is super easy now - one update.zip applied via Tenfars Clockworkmod Recovery Get it Here! - so no excuses not to give it a try! You won't be sorry.
As always start by making a backup via Clockwork Recovery.
There are now 2 packages - Choose the one for the the appropriate stock ROM you use (2.21 or 2.34.1), make sure you choose the right one for godsake or bad things will most probably happen!
Download FrozenEclairDefy_V2.zip Here for 2.21 Stock ROMs
Download FrozenEclair_V2.34.1.zip Here from 2.34.1 No Blur Stock ROMs
Instructions:
Place the FrozenEclair.....zip on the root of your sdcard
Boot into recovery
Select "Install zip from SDCARD"
Select "Choose zip from sdcard"
Select FrozenEclairDefy......zip from the list
Select "YES - Install - FrozenEclair......zip
The above will then install and then you just need to reboot. 1st boot will take longer than usual while it rebuilds the dalvik cache.
For some reason this removes root, so just reroot by Z4Root or your preferred method once the phone has rebooted. This will also mean you will have to reapply your overclock if you use milestone overclock (well it did for me anyways!)
##If you get any untoward things happening like force closes/apps not working my advice is to 1) reflash the .sbf (you follow my guide for this) and if that doesn't work 2)do a full wipe of all data. This is hacking and stuff like that happens all the time so be prepared##
MY Advice if you want to change to 2.34.1 ROM from 2.21. Follow this process:
Back up all user apps/their data by titanium backup.
Boot into recovery and make a backup of your 2.21 ROM.
Then wipe data/cache in the recovery options.
Using the debranding guide, flash the 2.34.1 firmware.
After 1st boot it will be as if you have a new phone.
Install z4root - root the badboy.
Then after reboot install Tenfars ClockworkMod - apply the mod and boot into it
Flash the deodex/JIT package.
After 1st reboot, reroot with Z4root.
Reinstall titanium back up from the market and reinstall you user apps/data.
Reset up your system settings.
Once you've got it back how you like it, boot back into recovery and back up the new rom.
So to reitterate thanks for this go to:
Antibyte @ Modaco for the JIT Files and full Update.zip 2.21 ROM
Paul @ Modaco for the deodexed/optimised app/framework for the 2.21 ROM
Me for the XDA guide and the original Update.zip for V1 and the deodexed app/framework for 2.34.1 ROM, and the JIT update.zip
Sorensiim for the generous hosting of all my files, meaning direct downloads and no shady file sharing sites - good lad!
Changelog:
19/12/10:
Frozen Eclair V1 - JIT For Defy
Tut on deodexing rom
Update.zip for installing JIT
20/12/10:
Frozen Eclair V2 - JIT For Defy
Recompiled and more optimisations
Whole process automated in 1 easy update.zip that includes deodexing and installing JIT.
Tut/OP updated to reflect the above changes
31/12/10:
Frozen Eclair V2.34.1 for 2.34.1 No Blur Stock ROM released
Wow! A preemptive thanks from me to you and the guys at Modaco!
Sent from my MB525 using XDA App
Hey
stupid question maybe, but what is JIT good for?
so what is JIT exactly? ( all i know so far is that it makes your quadrant scores higher so i assume it makes your phone faster in general or onlky in games?) and have you had any problems yet?
Great ! But what's MCR optimised ?
kendael said:
Great ! But what's MCR optimised ?
Click to expand...
Click to collapse
Paul runs the apks through his optimisation process, I don't know exactly what it does, but i trust Paul -but if you don't then just use the standard deodexed apps
For those that don't know I have added a link to the OP which gives a pretty decent explanation for what JIT for android is, or you could google "what is android jit" and you''ll find plenty of info lets use this thread to discuss this mod and any bugs etc.
I just read the introduction of Dalvik JIT. This is really amazing. I will try it later, since it will affect the warranty anyway.
Everythings works well. Quadrant with 900 mhz before JIT= 1175. Quadrant with 900 mhz with JIT installed = 1280. Thanks Paul! Good work. Keep it up.
Wow this sounds great! Thanks.
Can anyone tell me why i get an Unrecognized option '-h' for dalvikvm -h? I wanted to test if JIT is realy enabled.
# dalvikvm -h
dalvikvm -h
Unrecognized option '-h'
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all}
-Xnoquithandler
-Xjnigreflimit:N (must be multiple of 100, >= 200)
-Xjniopts:{warnonly,forcecopy}
-Xdeadlockpredict:{off,warn,err,abort}
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgenregmap
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
Configured with: debugger profiler jit show_exception=1
Dalvik VM init failed (check log file)
-----------------------------------------------------------------
This is the output from that on mine it doesnt mean anything however
Key line is this:
Configured with: debugger profiler jit show_exception=1
however if you do a logcat you will see the following from time to time proving jit is enabled:
12-19 14:53:55.641 1678 1681 I dalvikvm: Jit: resizing JitTable from 4096 to 8192
You are right. I have checked it with logcat.
Thanks Higgsy and everyone else involved. The first few runs on quadrant got about the same scores as before, but it just now returned a 1223.
Zaben said:
Thanks Higgsy and everyone else involved. The first few runs on quadrant got about the same scores as before, but it just now returned a 1223.
Click to expand...
Click to collapse
whats your linpack - are you overclocked?
Higgsy said:
whats your linpack - are you overclocked?
Click to expand...
Click to collapse
Stock 800 Mhz, I haven't messed with that stuff yet. The best I could get out of Linpack is 11.934. Neither Linpack or Quadrant are consistent. Quadrant scores vary from 937 to 1223. I haven't been able to reproduce the 1223 score.
I'm reverting here in a sec. The accounts problem has it where I can't get contacts to open. I may try again next weekend from a fresh reset.
Applied it fine and is working OK so far. Thanks! Quadrant on stock is 1241 now.
Loving the recovery applied zip. I would like to create one for the deodexed/optimised files as well - is there a FAQ about creating these?
A++ on this, defy is a really nice phone, thanks to dev efforts
Version 2 and fully automated update.zip process updated in the OP
whenever i enter recovery, it says "Can't open /cache/recovery/command" and there is no "install ZIP from SD CARD" option only reboot system now, apply sdcard:update.zip, wipe data/factory reset, and wipe cache partition. help
THREAD
"Hi, I've no 10 msg on xda so i can't report bugs to the dev "
Report here your questions/bugs about the rom, don't spam the dev thread with your 11th post :highfive:
I've created this thread without ask permission to HardLight, your warranty is now void :victory:
First of all, a big thanks to HardLight, skinbark and bigsupersquid for the OS2SD mod
AndroidMeda, Conn O'Griofa and other members of androidarmv6 for bringing KitKat to P500
CyanogenMod for sources
Here is the ROM : Link
please, read the first post
and remember:
To wipe clean 100% and install a new rom, in CWM or TWRP
Select “wipe data/factory reset
Select “yes”
Go to “mounts and storage”
Select “format /boot”
Select “yes”
Select “format /system”
Select “yes”
Back out of that menu to the main one again and select “advanced”
Select “Wipe Dalvik Cache”
Select “yes”
Click to expand...
Click to collapse
PLEASE UPDATE THE ROM ONLY WITH OS2SD UPDATES FROM HARDLIGHT'S THREAD
FROM OCTOBER ONLY THE F2FS OS2SD VERSION WILL BE DEVELOPED (best performance)
IF YOU UPDATE IN OTHER WAYS YOUR PHONE WILL BOOTLOOP
Summary:impression
Bugs/strange things
How To (2nd post)
- Minitool tutorial
- Overclock & Performance settings
- Superuser update and titanium backup problem
- Navigation bar with soft key
- Mod power button<-> search button (if your power button is broken)
- Saving battery
- Dialer pad number problem with L theme
- Make any rom an OS2SD rom
Impression, what i've done:
1st time:
with my "old" 8gb class 10 sd, a transcend, i've followed the instructions, with partition TWRP and TB
the first boot it's ok (after 2 min on the CM logo :fingers-crossed
open the options menu, i see lag and slow speed menu,
tried install some apps with TB and some were installed in the sd when i have "1 Gb" free in the internal memory.
Ok there was something wrong, so ... i changed the sd
Click to expand...
Click to collapse
2nd time:
format/wipe with a sandisk 8gb class 10, i've followed the instructions, 6 gb fat32, 380mb ext4, 128 swap, 1,1gb ext4
now everything it's ok, a little lag to launch the dialer and apps, like with the CM 4.1.2,
TB restore all apps in the "internal" memory :victory:
Click to expand...
Click to collapse
Performance
performance settings: cpu 320-650, smartassv2, sio - kms page merging on,
dev options: set to 0,0 all animations,
without a sim or not in aereo mode the phone lag a bit, insert a sim or turn on Aereo
battery use as phone only, sms&call, 2g: yesterday 81% (14h), now 16% (2d 7h)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
battery use as phone, data on 2g mode all the time and 1h gps:..
Click to expand...
Click to collapse
Bugs/strange things:
in call the proximity sensor don't turn off the screen it happens only if you have enabled the loudspeaker or use hearphones
for 3rd part apps use this to enable the airplane mode (with llama is not needed)
sound volume:in sound options play a little with the notify/ringtone level, check or uncheck the separate volume option and play again with notify& ringtone level, to me they change together also with the "separate" options solved in 18/08/14 rom
could i update to the latest normal or ota nightly? NO, you need an OS2SD rom, see the summary to make your os2sd rom
wifi battery drain
wifi hotspot,it need a reboot after use
fm not working
If you use Instagram, download the v.6.3.1: http://instagram.en.uptodown.com/android/download/72905
please refer to this post for instagram downloader and xposed module etc (thanks to xu3sno)
How To:
- Repartition SD card, the minitool partition tutorial:
Now in the first post of the HardLight's thread, under "Installation instructions" there are two beautifull "Partitioning guides", please follow one of them step by step
start minitool partition, chose minitool partition wizard,
select your usb disk (i.e. with my 8gb sd i've selected the disk "basic 7,47 GB" )
if you have also a sd with 2 or more partitions you have to delete all partitions -> select partition and click on "delete" button
when you have all the space in your sd "unallocated" (in gray) you can create the partitions needed
so select your unallocated volume and clic the "create" button
if minitool say "the new created partition cannot be used in win..." click yes
in partition label: leave blanc, don't give it a name (no /system, system or anything else)
in create as select "Primary"
in file system select "fat32"
in cluster size leave default
in size location unallocated space before 0.00 MB
partition size 5900 MB
click ok
do last steps for a second partition: primary, select the file system "ext4", partition space 450MB (You need 380+ mb for system on f2fs.)
the same for 3rd: primary, select the file sistem "linux swap, partition space 128MB"
the same for the 4th: primary; select the file system "ext4", partition space ~1.100 MB
in the end you have to CLICK THE APPLY BUTTON, else nothing happens
partition scheme for F2FS only:
1st: 5850 mb FAT32
2nd: 450 mb EXT4 (before flash the rom you have to change the file system to f2fs in TWRP-> select wipe->advanced wipe->SELECT Data -> click Repair or Change File System->Change File System>F2FS->swipe to change)
3rd: 128 mb linux swap
4th: ~1.100 mb EXT4 (change the file system to f2fs before install the rom)
- Overclock & Performance settings
To enable the performance menu you have to:
go to settings->about phone-> and tap tap tap tap tap tap ... tap on the "build number"
Now you've "dev options" & a "performance" menus at the end of the "settings" menu.
In dev options:
you can find 3 scale animation options, set them to 0,0x
In Performance:
set CPU min freq to 320, max to 729 (check "the set on boot" option) ... warning someone can keep 800+mhz but at long time this can BREAK (really) your phone & use a lot of battery
set Governor to smartassv2
set in I/O scheduler -> SIO or DEADLINE (check the "set on boot" option)
set in Memory -> check the Kernel page merging
uncheck "force high end graphic" (if you don't need a transparent notification bar)
make a reboot after these settings is highly recomended
in Testing PurePerformance mod
- Superuser update and titanium backup problem
if you have Superuser problem with titanium backup: i remember there was a fix to that, but the simple method is to install supersu (via TWRP) from the playstore
- Navigation bar with soft key
edit the build.prop and insert
Code:
qemu.hw.mainkeys=0
to show navigation bar with soft key
update, thanks to xu3sno
Well, for transparent/translucent status bar and softkeys, just edit build.prop, find ro.config.low_ram= true, change the value to false. It will enable translucent status bar.
Still in build.prop add line qemu.hw.mainkeys=0 in order to enable softkeys in navigation bar. Save > exit > reboot system.
Softkeys with L theme, install this module (you need Xposed of course). To enable L theme softkeys, go to Settings > Buttons > Buttons and layout > tap reset. However, once the screen lock and open, softkeys will back to the traditional one. Don't know, may be it's a bug.
Click to expand...
Click to collapse
- Mod power button<-> search button (if your power button is broken)
the search<->power button mod can be applied in the rom zip before to flash, with 7zip open the CM-11-XXXXXXX-NIGHTLY-OS2SD-p500.zip\system\usr\keylayout and you need only to sobstitute the 4 files manually inside the zip ( see in the mod thread -> manual version)
- Saving Battery
refer to this thread
and to this explanation
please don't use tweaks like the parsley
i'll test the wifi.supplicant_scan_interval=180 in the end this build.prop change don't saving power if wifi is connected but when not in range of a known network and you leave wifi on, you can set from 120 to ...3600 (i think is the time expressed in seconds to wake up the wifi and to check if there are known network).
2nd test: the bigsupersquid's patch need a new kernel, not applicable ATM
bigsupersquid patch and dovidhalevi iwconfig suggestion
on the second p500 (yes!, i use it only in aereo and wifi because i've no 2nd sim)
- Dialer pad number problem with L theme
If you see this in your dialer:
there is a problem in the L dark theme, until the theme dev will solve the problem you can click where you usually write phone numbers and swipe to the top.
or in the "speedcall""all contacts""favourite" tabs click on the search bar on top and write a number to call,now you can call the number directly from the search bar or then if you click the pad icon can see the full pad number
- Make any rom an OS2SD rom
Please read the HardLight Guide
try this if you want the latest nightly
Images:
with kitkat original theme and with L theme (Android L - CM 11 Theme, thanks to tung91 )
Thanks, good thread.
By the way you won't be able to flash new nighly, first I need to modify it for sd.
Sent from my LG-P500 using xda premium
HardLight said:
Thanks, good thread.
By the way you won't be able to flash new nighly, first I need to modify it for sd.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
thanks
i see in the updater-script that the mount point is set to this
mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system")
a simple question, if i use this updater script mod with other rom (i.e. rhar****'s omega) and your TWRP could i make my "omega os2sd" or there is something else to change?
ah i pushed the thanks button, but however i want to say Thank you for your work
edit:
added at 1st post the link to the HardLight's os2sd guide
Anyone tried using this rom with a class 4 sd card? I think I'm about to try it, even though I'm pretty sure it'll be slow like hell
brgil96 said:
Anyone tried using this rom with a class 4 sd card? I think I'm about to try it, even though I'm pretty sure it'll be slow like hell
Click to expand...
Click to collapse
a little bit, maybe,however also the internal memory transfer rate is 5-10 mb/s (lower than an usb2 transfer rate), is not like the hdd internal transfer rate (hundreds mb/s) or an ssd (gb/s)
what i can see is that, few apps = the phone is quite fast
much apps need internet connection = the phone is unusable
i've a decent use with Whatsapp on, but is the only app with data necessity unfreezed
the amazon store,appfree, skype, teamviewer etc. are freezed, and i'll unfreeze when needed
wats ths
cm11 or bug fixs
xdema said:
a little bit, maybe,however also the internal memory transfer rate is 5-10 mb/s (lower than an usb2 transfer rate), is not like the hdd internal transfer rate (hundreds mb/s) or an ssd (gb/s)
what i can see is that, few apps = the phone is quite fast
much apps need internet connection = the phone is unusable
i've a decent use with Whatsapp on, but is the only app with data necessity unfreezed
the amazon store,appfree, skype, teamviewer etc. are freezed, and i'll unfreeze when needed
Click to expand...
Click to collapse
For some reason I never thought of freezing data apps, might give it a try.
So I took the bait and installed it. Apart from the obvious delay when opening most apps (which is perfectly bearable so far), the rom runs smooth as silk. However, I don't have any additional apps apart from google's yet, so I still have to try that out. Time will tell.
PS: battery usage seems to be way lower so far (except for the wifi drain) when compared to gingersnap (which I was using before), and that's a first to me. You can barely say this battery is 4 years old (it's actually quite obvious but whatever x) )
Bricked?
I've flashed this ROM with files for broken power button mod and gapps. After first boot everything seemed to be working but I was getting constant keyboard crashes so I've tried all that "reflash gapps, clear cache etc." As it didn't solve the problem I've downloaded a keyboard on PC but I couldn't connect the phone via USB (there was no notification about connection and nothing showing up on PC). Then I turned off the phone and I can't turn it back on and I can't enter recovery. It's completly dead. The only thing that is working is offline charging. However when screen turns off after a few seconds I can't wake it up with any button. What to do?
Przeszczep said:
I've flashed this ROM with files for broken power button mod and gapps. After first boot everything seemed to be working but I was getting constant keyboard crashes so I've tried all that "reflash gapps, clear cache etc." As it didn't solve the problem I've downloaded a keyboard on PC but I couldn't connect the phone via USB (there was no notification about connection and nothing showing up on PC). Then I turned off the phone and I can't turn it back on and I can't enter recovery. It's completly dead. The only thing that is working is offline charging. However when screen turns off after a few seconds I can't wake it up with any button. What to do?
Click to expand...
Click to collapse
Please at this moment don't use the f2fs version, it's only for the brave, in the OP there are 2 kind of rom: a f2fs version and another not-f2sf
keyboard app problem -> go to setting -> app -> select keyboard -> clear data, clear cache (into this menu, not in the recovery or something else)
else you can try with another keyboard, usually i set swiftkey as default.
See you the LG logo and after a black screen?
if you didn't use KDZ or LGMDP to flash roms, usually you can enter in recovery (if somethings go wrong with LGMDP or KDZ you make an hardbrick).
so don't use KDZ by now
how to enter the recovery: pull out the battery, wait 2 sec, reinsert, push power on button (you can see the LG logo) and after keep only vol down and home buttons.
if you can see the recovery then reflash the rom
sometimes after the LG logo you see a black screen, please check if the phone is off or the screen is on but black, if it's black it could be you didn't pressed the vol+home buttons in time
if you have problem contact shinobisoft or HardLight and search the howto unbrick/revive p500 guides in xda (i remember that there were 3 or 4)
brgil96 said:
So I took the bait and installed it. Apart from the obvious delay when opening most apps (which is perfectly bearable so far), the rom runs smooth as silk. However, I don't have any additional apps apart from google's yet, so I still have to try that out. Time will tell.
PS: battery usage seems to be way lower so far (except for the wifi drain) when compared to gingersnap (which I was using before), and that's a first to me. You can barely say this battery is 4 years old (it's actually quite obvious but whatever x) )
Click to expand...
Click to collapse
with latest file system mod (f2fs) it should a bit faster, tomorrow i'll test on my 2nd p500 (actually with omega rom), see the HardLight's thread
I've managed to somehow turn on the phone but i still have 2 problems:
Crashing keyboard app. It has no data and 24.00KB cache. However I don't know if I can clear it because when I tap on "Clear cache" nothing happens and it stays at 24KB.
I can't add Google account. In settings I tap on "Add account" and nothing happens.
Factory reset and reflashing gapps didn't resolve those issues.
Przeszczep said:
I've managed to somehow turn on the phone but i still have 2 problems:
Crashing keyboard app. It has no data and 24.00KB cache. However I don't know if I can clear it because when I tap on "Clear cache" nothing happens and it stays at 24KB.
I can't add Google account. In settings I tap on "Add account" and nothing happens.
Factory reset and reflashing gapps didn't resolve those issues.
Click to expand...
Click to collapse
fix for keyboard issue: the keyboard app is corrupted
fix: http://forum.xda-developers.com/showpost.php?p=55220723&postcount=99
G account: are you with the f2fs rom or not?
Keyboard working.
xdema said:
G account: are you with the f2fs rom or not?
Click to expand...
Click to collapse
Yes I'm using f2fs.
Przeszczep said:
Keyboard working.
Yes I'm using f2fs.
Click to expand...
Click to collapse
the 31/08 seem have some corrupted files, now i'm trying with the bigsupersquid 30/08 rom
Skype 5 is not working on my P500, the previous version 4 worked. Is anyone experiencing the same problem?
I have attached my logcat output below, however I cannot deduct any useful information from that. I am using hardlight's current CM version from 30th august.
Code:
I/Timeline( 686): Timeline: Activity_launch_request id:com.skype.raider time:65250488
I/ActivityManager( 426): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.skype.raider/.Main bnds=[82,191][148,264]} from pid 686
V/Zygote (20585): Switching descriptor 31 to /dev/null
V/Zygote (20585): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20585 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20585): handleBindApplication:com.skype.raider
D/ActivityThread(20585): setTargetHeapUtilization:0.25
D/ActivityThread(20585): setTargetHeapMinFree:524288
V/ActivityThread(20585): com.skype.raider white listed for hwui
D/dalvikvm(20585): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d0760
D/dalvikvm(20585): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d0760
D//Ln.java:218(20585): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20585): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d0760
E/CrashAndAnrHandler(20585): Dumping stack for signal 7
E/CrashAndAnrHandler(20585): Dumping stack for signal 11
D/Zygote ( 134): Process 20585 terminated by signal (11)
I/ActivityManager( 426): Process com.skype.raider (pid 20585) has died.
V/Zygote (20600): Switching descriptor 31 to /dev/null
V/Zygote (20600): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20600 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20600): handleBindApplication:com.skype.raider
D/ActivityThread(20600): setTargetHeapUtilization:0.25
D/ActivityThread(20600): setTargetHeapMinFree:524288
V/ActivityThread(20600): com.skype.raider white listed for hwui
D/dalvikvm(20600): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d1670
D/dalvikvm(20600): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d1670
W/ActivityManager( 426): Launch timeout has expired, giving up wake lock!
D//Ln.java:218(20600): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20600): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d1670
E/CrashAndAnrHandler(20600): Dumping stack for signal 7
E/CrashAndAnrHandler(20600): Dumping stack for signal 11
D/Zygote ( 134): Process 20600 terminated by signal (11)
I/ActivityManager( 426): Process com.skype.raider (pid 20600) has died.
V/Zygote (20615): Switching descriptor 31 to /dev/null
V/Zygote (20615): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20615 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20615): handleBindApplication:com.skype.raider
D/ActivityThread(20615): setTargetHeapUtilization:0.25
D/ActivityThread(20615): setTargetHeapMinFree:524288
V/ActivityThread(20615): com.skype.raider white listed for hwui
D/dalvikvm(20615): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d2590
D/dalvikvm(20615): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d2590
D//Ln.java:218(20615): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20615): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d2590
E/CrashAndAnrHandler(20615): Dumping stack for signal 7
E/CrashAndAnrHandler(20615): Dumping stack for signal 11
I/ActivityManager( 426): Process com.skype.raider (pid 20615) has died.
W/ActivityManager( 426): Force removing ActivityRecord{423a5838 u0 com.skype.raider/.Main t41}: app died, no saved state
D/Zygote ( 134): Process 20615 terminated by signal (11)
W/InputMethodManagerService( 426): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
I/Timeline( 686): Timeline: Activity_idle id: [email protected] time:65269779
xdema said:
the 31/08 seem have some corrupted files, now i'm trying with the bigsupersquid 30/08 rom
Click to expand...
Click to collapse
about this problem,
i have tried f2fs builds from 8/30, 9/5 and 9/8 ... and i cant get gapps to work in any of those ...
however gapps are working fine on ext4 version ... tried two latest from hardlights drive
is it possible that gapps are just not working on fresh install f2fs builds?
and upgrading from ext4 version to f2fs with converting data partition should work ?
/edit
well nevermind, hardlight uploaded new version of gapps and f2fs build works for me now
thank you hardlight & everyone affiliated
Flo.de said:
Skype 5 is not working on my P500, the previous version 4 worked. Is anyone experiencing the same problem?
I have attached my logcat output below, however I cannot deduct any useful information from that. I am using hardlight's current CM version from 30th august.
Code:
I/Timeline( 686): Timeline: Activity_launch_request id:com.skype.raider time:65250488
I/ActivityManager( 426): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.skype.raider/.Main bnds=[82,191][148,264]} from pid 686
V/Zygote (20585): Switching descriptor 31 to /dev/null
V/Zygote (20585): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20585 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20585): handleBindApplication:com.skype.raider
D/ActivityThread(20585): setTargetHeapUtilization:0.25
D/ActivityThread(20585): setTargetHeapMinFree:524288
V/ActivityThread(20585): com.skype.raider white listed for hwui
D/dalvikvm(20585): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d0760
D/dalvikvm(20585): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d0760
D//Ln.java:218(20585): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20585): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d0760
E/CrashAndAnrHandler(20585): Dumping stack for signal 7
E/CrashAndAnrHandler(20585): Dumping stack for signal 11
D/Zygote ( 134): Process 20585 terminated by signal (11)
I/ActivityManager( 426): Process com.skype.raider (pid 20585) has died.
V/Zygote (20600): Switching descriptor 31 to /dev/null
V/Zygote (20600): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20600 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20600): handleBindApplication:com.skype.raider
D/ActivityThread(20600): setTargetHeapUtilization:0.25
D/ActivityThread(20600): setTargetHeapMinFree:524288
V/ActivityThread(20600): com.skype.raider white listed for hwui
D/dalvikvm(20600): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d1670
D/dalvikvm(20600): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d1670
W/ActivityManager( 426): Launch timeout has expired, giving up wake lock!
D//Ln.java:218(20600): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20600): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d1670
E/CrashAndAnrHandler(20600): Dumping stack for signal 7
E/CrashAndAnrHandler(20600): Dumping stack for signal 11
D/Zygote ( 134): Process 20600 terminated by signal (11)
I/ActivityManager( 426): Process com.skype.raider (pid 20600) has died.
V/Zygote (20615): Switching descriptor 31 to /dev/null
V/Zygote (20615): Switching descriptor 10 to /dev/null
I/ActivityManager( 426): Start proc com.skype.raider for activity com.skype.raider/.Main: pid=20615 uid=10118 gids={50118, 1006, 3003, 3002, 1028, 1015}
D/ActivityThread(20615): handleBindApplication:com.skype.raider
D/ActivityThread(20615): setTargetHeapUtilization:0.25
D/ActivityThread(20615): setTargetHeapMinFree:524288
V/ActivityThread(20615): com.skype.raider white listed for hwui
D/dalvikvm(20615): Trying to load lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d2590
D/dalvikvm(20615): Added shared lib /data/app-lib/com.skype.raider-1/libSkypeAndroid.so 0x419d2590
D//Ln.java:218(20615): main Configuring Logging, minimum log level is INFO
D/dalvikvm(20615): Trying to load lib /data/app-lib/com.skype.raider-1/libSkyLib.so 0x419d2590
E/CrashAndAnrHandler(20615): Dumping stack for signal 7
E/CrashAndAnrHandler(20615): Dumping stack for signal 11
I/ActivityManager( 426): Process com.skype.raider (pid 20615) has died.
W/ActivityManager( 426): Force removing ActivityRecord{423a5838 u0 com.skype.raider/.Main t41}: app died, no saved state
D/Zygote ( 134): Process 20615 terminated by signal (11)
W/InputMethodManagerService( 426): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
I/Timeline( 686): Timeline: Activity_idle id: [email protected] time:65269779
Click to expand...
Click to collapse
skype 5.0.0.49715 it was ok for me on os2sd (not the f2fs version) now i've installed latest version from playstore, click the icon did nothing, so back to v4 (last titanium backup)
microphone is really silent in the latest build ... at normal setting no one can hear me, when i put it on speaker i have to hold it right next to mount to get my voice barely hear-able......
nesty1990 said:
microphone is really silent in the latest build ... at normal setting no one can hear me, when i put it on speaker i have to hold it right next to mount to get my voice barely hear-able......
Click to expand...
Click to collapse
reported to HardLight's thread
My skyrocket won't boot. It displays both Samsung logos (the plain and fancy ones) and the AT&T globe (with the flash animation thing) and plays the boot sound, but doesn't get past the globe-on-white screen. Log seems to indicate that boot sequence hangs at Account Manager. That is: The PackageManager sequence has problems, but seems to at least complete: log has both "[email protected]" and "[email protected]". Then there's "I/SystemServer( 519): Account Manager", but there's nothing like "[email protected]" (though I'm not sure whether there should be). That's where things kind-of stop, though dalvikvm's garbage collector keeps running like a champ.
I was updating some apps (4, I think) in Google Play Store when device suddenly rebooted. I don't even remember which apps were being updated. It looks like /data/system/users/0/package-restrictions.xml is corrupted. It also looks like the permissions got corrupted, too.
Any ideas? I believe I could flash a new ROM (adb, fastboot, recovery, download mode all work fine), but I'd like to fix this if I can. Also, I don't want to lose any data, and the tarballs from recovery don't even seem to work (data tarball @ 990 MB extracts to only 153 MB of actual files).
Device info: Rooted (SuperSU, Busybox). Custom recovery (PhilZ Touch). ROM is stock. Also: Xposed, Xprivacy. Again, recovery and download modes work fine.
Code:
D/Xposed ( 164): Starting Xposed binary version 58, compiled for SDK 16
D/Xposed ( 164): Phone: SAMSUNG-SGH-I727 (samsung), Android version 4.1.2 (SDK 16)
D/Xposed ( 164): ROM: JZO54K.I727UCMC1
D/Xposed ( 164): Build fingerprint: samsung/SGH-I727/SGH-I727:4.1.2/JZO54K/I727UCMC1:user/release-keys
I'm happy to post the entire logcat output, but it's 3354 lines. Some of the weird things in log:
Code:
...
I/Xposed ( 164): java.io.FileNotFoundException: /data/data/de.robv.android.xposed.installer/conf/modules.list: open failed: ENOENT (No such file or directory)
...
D/Kies ( 153): fail to get sys.boot_completed
...
W/Zygote ( 164): Class not found for preloading: android.database.sqlite.SQLiteCompiledSql
(MULTIPLE OF THESE)
...
W/ResourceType( 519): Failure getting entry for 0x7f020003 (t=1 e=3) in package 0 (error -75)
(LOT OF THESE)
...
E/PackageManager( 519): Error reading stopped packages: org.xmlpull.v1.XmlPullParserException: unterminated entity ref (position:TEXT @1:313 in [email protected])
...
I/dalvikvm( 519): Zip is good, but no classes.dex inside, and no .odex file in the same directory
W/PackageManager( 519): Exception reading jar: /system/framework/twframework-res.apk
W/PackageManager( 519): java.io.IOException: /system/framework/twframework-res.apk
...
I/BootTime( 519): Fail Safe scanning for:/system/app/SetupWizard.apk
(LOTS OF THESE)
...
E/Atfwd_Sendcmd( 231): Could not obtain AtCmdFwd service
(LOTS)
...
W/PackageManager( 519): Removing dangling permission: com.qualcomm.permission.ACCESS_LOCATION_API from package null
W/PackageManager( 519): Unknown permission android.permission.ACCESS_DEV_STORAGE in package com.sec.android.gallery3d
(LOTS OF THESE)
...
i think ur only option is to reset in recovery,, or if that fails a system wipe and then reflash rom, yup that sucks
do a backup first but that might corupted backup of the rom which might be useless but worth a shot.
vincom said:
i think ur only option is to reset in recovery,, or if that fails a system wipe and then reflash rom, yup that sucks
do a backup first but that might corupted backup of the rom which might be useless but worth a shot.
Click to expand...
Click to collapse
Thanks for replying. I was afraid you'd say that. I'll give that a shot, but I'm trying to back up some data first. Most stuff (e.g., contacts, calendar) is remote, so no problem there.
I'm having trouble with some local stuff, though. I've got voice memos and MMS/SMS. But I can't find:
+ call history / log ... Where is it? /data/data/com.android.[providers.]contacts only contain subdirs lib/. There are no files. Is it in with the mmssms.db? I can't even tell. Is this stored in the cloud, too?
+ text memos ... /data/data/com.sec.android.app.memo only contains lib/. There are no files. (Same with /data/data/com.sec.android.widgetapp.memo.) (I MAY have used OpenIntents Notepad, but its default directory is empty, too.)
Any ideas/suggestions/etc on where to find text memos and call history? And how about seeing what icons were on my home screen?
Also, the weird thing about the CWM tarballs is that they don't appear corrupt -- tar gives no errors, no warnings, etc. But the size of the data actually extracted is ridiculously less than the size of the tarball.
system = 567.1 MB ... extracts to 13.6 MB
data = 990.2 MB ... extracts to 153.3 MB
The extracted sizes change if I do another backup. And I used adb to push the data out, and it looks like I've gotten it all. This is just kinda strange.
In Android ROMs' developments, I always start with AOSP. It is the root and if I want to do it right, I have to make it work for AOSP first. Putting the AOSP tests in my kernel thread is getting messy. As I would continue my work here for a while. Starting a thread for AOSP seems reasonable.
Here is for sharing of experiences and discussions.
There would be no nightly, weekly or monthy. I would follow the releases of AOSP and keep it as genuine as possible. If you are looking for a feature, there are many nice ROMs out there.
Known Issues:
1. AOSP Camera App The AOSP Camera2 app is not working with the Nexus 7 (2012) which is the only (I think) Nexus device with a Front Camera but not the Back Camera. The new Camera2 app set the back camera as default. I can make the preview shown by a simple overlay configs. But, make it really work would be quite a work. In the app market(s), there are many camera apps already taking care of that and would work flawlessly. I see no reason to waste time on that. 2. "E:unknown command [log]" If you got this message when flashing, don't panic. It's the new "block_image_update()" in recovery cause that. It would do no harm and it would be gone in the next TWRP. 3 Please report.
Tips:
1. DT2W At deep sleep, the idled CPU takes time to resume. If the taps are too close, it might not be recognized. Delay the duration between taps would give you better results. 2. Built-in File Explorer There is an built-in file explorer in AOSP. We can explore the files as well as installing apks.
Its in: Settings > Storage > Explore (under the storage you want. In case of Nexus 7, only the internal and OTG exist.)Change log:
Code:
[COLOR="Blue"]2017/5/3[/COLOR]
- Android-7.1.2_r11 (NHG47L)
[COLOR="Blue"]2017/4/9[/COLOR]
- Android-7.1.2_r5 (N2G47J)
- PerformanceControl: boot up settings fixed
- Fix Wifi hotspot
- Performance patches
[COLOR="Blue"]2017/3/8[/COLOR]
- Android-7.1.1_r28 (N6F26U)
[COLOR="Blue"]2017/2/8[/COLOR]
- Android-7.1.1_r21 (NOF26W)
[COLOR="Blue"]2017/1/6[/COLOR]
- Android-7.1.1_r13 (N6F26Q)
- Camera: Fix video recording
[COLOR="Blue"]2016/12/16[/COLOR]
- Android-7.1.1_r6 (NMF26Q)
- SEPolicy update
[COLOR="Blue"]2016/12/7[/COLOR]
- Android-7.1.1_r4 (NMF26O)
- Fix the Camera
[COLOR="Blue"]2016/11/11[/COLOR]
- Android-7.1.0_r7 (NDE63X)
[COLOR="Blue"]2016/10/24[/COLOR]
- Android-7.1.0_r4 (NDE36P)
- Remove every recovery related resources
[COLOR="Blue"]2016/10/14[/COLOR]
- Android-7.0.0_r14 (NBD90Z)
- Shield the occasional crash in MTP Document provider
- USB and Bluetooth Tethering support enabled
[COLOR="Blue"]2016/9/23[/COLOR]
- Android-7.0.0_r6 (NRD90U)
- latest DC kernel (Android-7.0 branch)
- PerformanceControl: version 2.1.6
- Find a way to fix the hwcomposer for video/audio playback, need to review later
- A few sepolicy patches for Gapps and Mediaserver
- SELinux: Enforcing
Downloads: :highfive:
Hosts: Android File Host MEGA mirror: 百度网盘
Note: I only tested it in TWRP 3.0.2.
PerformanceControl app requires ROOT access.
Root access can be obtained by the systemless SuperSU from @Chainfire.
Gapps: opengapps (pico) and BaNKs Gapps for 7.0 are tested
Sources:
Sources in github
Credits: :good:
** Definitely the AOSP
** The AndroidFielHost provide a FREE host with no limits and expiration.
** All the developers who help the Nexus 7 (2012) development
** All those who donate and/or help the developers. Giving us the resources and reason to carry on.
Donations: :angel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Discussions
Anyone has any idea are welcome to post here
DT2W
Sometimes it won't wakeup after a long DEEP_SLEEP
When volume buttons are also enabled for wakeup. It won't work too. Seems there are situations "soft pwr button press" won't work.
Fail after reboot
Code:
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
Some of you might encounter the above message after reboot. I never encountered before but there is definitely something wrong.
@millosr found that it was the recovery being replaced. I think that make sense and I want to study why.
I looked into the source. In the original AOSP, an OTA might come with a recovery patch. Stated in the build/core/Makefile "boot.img + recovery-from-boot.p + recovery-resource.dat = recovery.img"
It would generate the "recovery.img by the above formula itself. Custom ROMs usually won't carry a recovery and this part was usual ignored.
There is a warning in TWRP before reboot. Some of you might not read clearly and slide to continue immediately. In that case, the above mentioned recovery.img will be generated and flashed to the /recovery partition. Everything seems normal but after reboot.
When the script kick in, it would execute the "new" recovery. As a normal recovery, it would load the fstab and try to mount the partitions. The current fstab version is API 3. Almost all ROMs (no matter how close to AOSP) would have F2FS support. When we open a typical fstab:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,nodiratime,discard,inline_xattr,inline_data,inline_dentry wait,check
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,journal_async_commit,errors=panic wait,check
Note that the second line is the declaration for the /cache in f2fs. Stock AOSP recovery doesn't support f2fs. That's why the above error shown. Since it fail to mount /cache, the last_locale is not loaded and recovery would hang.
How to recover?
Naturally, you have to flash TWRP again.
First of all, you need to boot into bootloader (fastboot mode)
Some init.xxx.rc might start adbd earlier and in this case "adb reboot bootloader" would do the job.
If adbd was not started before the hang, the command won't work. In this case you can only use the pwr+vol. down combination.
If it is still hanging, the buttons might not work. Press the power button continuously might lead to repeatedly reboot. It is better to make sure the device is OFF first.
1. Connect to a charger.
2. Press the power button until you see the charging image
3. Release the power button immediately.
4. After that, press the volume down button first, and then the power button.
It would go to the bootloader.
Note: /system is not really formatted during flashing. To make sure no residue left in /system, it is better to wipe the /system before flashing.
For ROM builders, there is a flag BOARD_USES_FULL_RECOVERY_IMAGE. Set it to true will stop the generation of recovery-resource.dat (in /system/etc) and break the above formula.
Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.
Nintonito said:
Does D2TW require the digitizer to remain permanently on? Trying to guage the impact of such a feature before I turn it on.
Click to expand...
Click to collapse
obviously.
---------- Post added at 09:52 AM ---------- Previous post was at 09:46 AM ----------
@daniel_hk good to see a separate thread. Will test this build this weekend as i am already on grouper.
：手指划线：
Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.
ho0o0o11111 said:
Thanks for bringing nougat to our beloved Nexus 7!!!
I just flashed but no matter which gapps I use, I can't make playstore and google play services installed.
Any hints?
Thanks.
Click to expand...
Click to collapse
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.
daniel_hk said:
If you want anyone to help, you have to provide details.
The tested Gapps' are listed in OP. "No matter which gapps" ?
Can you tell us which one and version you actually tried?
What's your flashing procedures? etc.
Click to expand...
Click to collapse
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.
ho0o0o11111 said:
Procedures (clean flash)
- rom
- gapps
- supersu
- reboot
- no playstore/play services have been installed after reboot
I used explorer to check and found that those gapps are installed (e.g. Vending.apk) but their sizes are all in 0kb.
the gapps I used were opengapps PICO and Banks. (I tried both. All after clean flash)
Finally I got playstore installed as follows
- flash rom/gapps/supersu
- reboot
- uninstall some system apps I don't need
- flash gapps again
then the playstore appears in app drawer. (And it works)
However, I have another big problem after reboot.
My device is now stuck in bootloop after splashscreen.
It just shows message as follows and I can't enter recovery/bootloader.
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
In the following page I found a solution "adb reboot bootloader" but I can't even enter bootloader/fastboot mode.
http://forum.xda-developers.com/nex...ip-linux-tegra-nv-3-4-bringup-t3128195/page46
still trying...
Any helps would be appreciated.
Thanks.
Click to expand...
Click to collapse
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!
daniel_hk said:
I think you are not using the Official TWRP. There are similar reports having the same problem for other MM ROMs too.
You may try the Official TWRP 3.0.2 here (follow the link if you have a Tilapia) and flash everything again.
You might have corrupted your /cache and /data. It is better format them (to ext4 or f2fs) in the Official TWRP again.
Good luck!
Click to expand...
Click to collapse
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.
ho0o0o11111 said:
Thanks for your suggestion but the TWRP I used were downloaded from TWRP's official website, so I supposed it is official version.
I can't flash TWRP again as I am still struggling to enter bootloader mode.
Click to expand...
Click to collapse
Which version? eariler version might have a wrong fstab which have issue on f2fs.
Make sure you got the latest version 3.0.2
You can't go to boot loader?
That means you press pwr+vol down and it won't reboot to bootloader?
That's strange.
"adb reboot bootloader" only work if the adbd is up. That means you can use "adb devices" to check the existance of your device.
You may try this:
1. connect to the charger
2. pressing the pwr button for > 8 seconds.
See if the tablet reboot. If yes, it would boot into charging mode. Pwr+vol down again would work.
If it doesn't reboot after you pressed say 20 seconds, you need to remove the battery.
Good luck!
@daniel_hk
Thanks for the new AOSP build Daniel. Nice work fixing the hardware decoder, my Netflix is now working and I was able to play one of my MP4 movies with BS Player in HW mode. I've been changing back and forth between your first AOSP 7 build and your DU 7 build with dirty flashes. With this build I decided to clean flash and at first things were very sluggish but settled down after a reboot and probably after Google finished whatever it does in the background. LOL Aside from a few occasional random force closes, it's running pretty well.
A couple of observations:
As mentioned, I did a clean install with this build. I'm using official TWRP 3.02 and installed the rom and 7.0 Open Gapps nano 20160915 at the same time and when it booted up for the first time, there were no gapps installed. I powered down and then went back into TWRP and reflashed the gapps, this time they were there upon reboot. Surprisingly, I didn't have to set permissions for Google Play or Play Store, as they were already correctly set??? I did run into a snag when trying to download apps from PS, clearing the data for the download manager app solved that problem for me.
I installed a camera app (HD Camera) from Play Store and it works but when I use my phone's camera, it reminds me how crappy the N7 camera is. LOL
After setting things up, I wanted to try phhsuperuser (no Magisk) to root and it went fine. All of my apps that require root worked...except Titanium Backup. I tried uninstalling/reinstalling both phhsuperuser and Titanium but couldn't get it to work. I rely on Titanium quite a bit, so I flashed Supersu 2.78 and all's well.
Thanks again.
Mike T
Do games work on this rom?
Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work
Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?
Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.
paasoares said:
Hi,
This is the best 7.0 ROM so far !!!
Smooth, video HW decoding is working, games work perfect.
As webdroidmt said I also had to reflash GAPPS to have GAPPS installed and i had to give proper permissions on Google Play service to stop seeing the "google play service stop" message.
All Apps/games that i installed are working properly.
Thanks Daniel_hk for your work
Click to expand...
Click to collapse
In any case, it's a good practice to read the console after flash anything. There might already be essential messages which not necessarily in red.
I also experience SuperSU need to flash again. I just found out something that might help. Seems SuperSU would use the cache to start a checking process in the next boot. I don't know if it would help gapps too.
1. Try factory reset before flashing.
2. Flash ROM+Gapps+SuperSU
3. After that don't do wipe cache/d-cahce again. (factory reset already include this action)
Good luck!
3yan said:
Many thanks Works like a charm !
Is SEpolicy restrictive in your build? (I cannot see it from Settings -> about tablet)
.
Can you post your manifest on Your Github for easier building ?
Click to expand...
Click to collapse
I think you meant "Enforcing". Yes, it is enforcing. Only some Custom ROM would show this in About but not AOSP.
There is a shell command "getenforce" which you can check the SEPolicy status.
If you read the OP, you would know its an AOSP without any mod/tweak, just porting. You can get the manifest and all the helps in https://source.android.com.
Good luck!
fat-lobyte said:
Hi, currently testing your ROM, looks awesome!
When Browsing the web with Chrome, loads and loads of SELinux denials, mostly when the page loads:
Code:
09-26 13:34:20.990 4424 4424 W Thread-4: type=1400 audit(0.0:174): avc: denied { ioctl } for path="socket:[45348]" dev="sockfs" ino=45348 ioctlcmd=8b1b scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:untrusted_app:s0:c512,c768 tclass=udp_socket permissive=0
This message times * 100 for every page load.
Click to expand...
Click to collapse
Chrome has many versions and it should not be an untrusted app. I'm testing the CarbonROM which has a bloated Chrome and being treated as isolated app. It might take time for those UID's being properly handled.
I already included some extra permissions which would be include in my later builds.
Anyway, we would encounter denials more often in apps. That's what newer Android intent to do.
Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
I wanted to try this 'Sept 23' ROM as it should play video OK: in the end I got it to work, and I can now indeed play video in some video based apps that did not work before. I used the older DU ROM and also the nAOSP ROM of millosr. There video does not work yet.
But with this Sept23 ROM I had a fight with Gapps to get it to work... First the Gapps I normally use failed to install in TWRP. At least, that is what I think I saw: the progress bar suddenly jumps ahead as if the install process was broken off somehow. So I again clean wiped all and now used opengaps-pico. That installed fine, but on first boot, no gapps. So I again installed opengapps and now finally I had working playstore. Strange, I never ran into something like this before (I am mostly active on Xperia S with nAOSP).
But the story ends well, as my video now works: great job !
fat-lobyte said:
Code:
09-26 19:14:02.119 189 344 D hwcomposer: hotplug_thread: processing control fd
09-26 19:14:02.119 189 344 I hwcomposer: hotplug: connected = 0
09-26 19:14:03.469 503 579 W AlarmManager: Unrecognized alarm listener [email protected]
09-26 19:14:03.469 503 579 E WifiScanner: listener cannot be found
09-26 19:14:03.478 677 677 E wpa_supplicant: wlan0: Failed to schedule PNO
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: PNO state change to true failed
09-26 19:14:03.481 503 581 E SupplicantWifiScannerImpl: Failed to start PNO scan
09-26 19:14:03.484 503 581 W SupplicantWifiScannerImpl: No PNO scan running
09-26 19:14:03.486 503 579 E WifiConnectivityManager: PnoScanListener onFailure: reason: -1 description: pno scan failed
This is repeated every 5 minutes during deep sleep. I'm not an expert, but this probably doesn't help with battery drain
I'm also having some touch sensitivity issues when coming out of deep sleep or off the charger. I have to do some more testing, then I will have more details.
Click to expand...
Click to collapse
Did you set "keep wi-fi on during deep sleep" to NEVER?
My tablet drain 5% during this night (about 8 hours), so i guess this is normal/acceptable