Database Info

[Q] First time rooting.

Couldn't find a very clear tutorial anywhere, just a number of different threads saying different things lol. Anyways, need to know how to root my Droid Charge. Also need to know how to install CyanogenMod after.
I know rooting will void my warranty but I heard from a few people that if I unroot the phone, the warranty will be put back in place. Is this true?
If I somehow manage to brick my phone, I can always unbrick in most cases, correct?
Phone Info:
Hardware version - i510.06
Firmware version - 2.3.6
Kernel version - 2.6.35.7-EP4
Build number - SCH-I510.EP4
Not sure what information is important, but I believe it was mainly the kernel and Android version lol.
EDIT: Never mind about Cyanogen, I just want the best/fastest ROM I can get.

First things first. It's very difficult to hard brick this phone. I had to do a warranty return before and it is easy to go back to stock. If you get a soft brick, you can follow this thread and get it back to stock: http://forum.xda-developers.com/showthread.php?t=1111486
Next thing, you can't install CyanogenMod on this phone. We don't have any AOSP rom on this phone. All we have is repackaged stock roms.
As for how to root, it really depends on what you want. Do you just want root, or do you want a rom?

For right now, I just want to root. I've found out how to do that, kinda. I'm stuck now.
I'm trying to install imoseyon's kernel through CWM but I used the backup option before I installed the kernel. So now when I boot into recovery it oly gives me the optinos to "reboot system now", " apply update from sdcard", "wipe data/factory reset", and "wipe cache partition". I tried to apply update from sdcard and when I selected my kernel zip, it gives me back this:
"
-- Install /mnt/sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.

You need to reflash CWM.
CWM does not survive a reboot unless you're on a custom kernel, or root and remove the updater script. You have to flash CWM and immediately boot into it. If you let it boot up fully on the stock kernel, it will overwrite CWM with the stock recovery, so you'll have to flash it again, and immediately boot in and flash.

Will I keep the backup I made? Or should I just not worry about the backup and use Titanium?

It will keep the backup. It does the backup to SD, and the only folder on SD that CWM will touch in a wipe is .android_secure.

It worked. All rooted, thank you. Any suggestions for themes, apps to get, or ROMs?

ratchetlock2 said:
It worked. All rooted, thank you. Any suggestions for themes, apps to get, or ROMs?
Click to expand...
Click to collapse
The two most are using are TweakStock and Infinity. I strayed but came back to
TweakStock. Dont think it has a true theme available yet but you could atleast do something like Go launcher or something. With Ifininity there is a theme available. Read about both in the Dev section then decide.

Will do. Any OCable kernels yet? Saw someone post on here that there wasn't any yet.

ratchetlock2 said:
Will do. Any OCable kernels yet? Saw someone post on here that there wasn't any yet.
Click to expand...
Click to collapse
No custom kernels at all, other than repackaged stock kernels, but Tegrak Overclock works with any GB kernel. The free version only lets you change clock speeds. The pay version lets you change voltages as well, and lets you apply at boot.

Uh oh, got stuck in an infinite reboot loop. Tried turning my phone on only to come up to the first Samsung post screen, goes to black eventually for a little bit, then goes right back to the Samsung screen. How do I fix it? Can't find a solid answer.
I went into CWM and tried to restore a backup but it said it was missing the MD5 file or something; can't remember what exactly the error was with the restore. I'll try reflashing CWM soon.

Now I can't do anything... Can't put phone in DL mode, recovery, nothing. Won't even say it's charging.
I'm still under warranty, I'm considering bringing it in and saying I need a replacement because I know they won't be able to fix this on the spot.
EDIT: Got into DL mode luckily and I'm getting into DL mode smoothly now. But I still can't power on or get into recovery...
EDIT2: Using this thread to try and fix my problem. http://forum.xda-developers.com/showthread.php?t=1111486
{
"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"
}
Are these the right settings?
Trying to odin this file: http://forum.xda-developers.com/showthread.php?t=1172182
EDIT3: What a headache... Fully back to stock now. Going to try and restore everything that I backed up onto my SD card.

Are you leaving in the battery while flashing?
Sent from my SCH-I510 using xda premium

Nope.
numberfix

ratchetlock2 said:
Nope.
numberfix
Click to expand...
Click to collapse
There's your problem. Once you're in download mode and detected by Odin, pop the battery back in.
Sent from my SCH-I510 using xda premium

updating from software crash - cyangoen mod

got a samsung galaxy captivate i897
bought it rooted running cyanogen mod & miui
was fine for about a year then the software kept crashing (everything was force closing)
in the this time i didnt do anything that would have caused this issue. i didnt update anything the only thing i did was install or uninstall apps. so i dont know why it occured. i dont even know if it happened as a result of having been rooted (if something became unstable - i wouldnt have thought so since it worked for a year with no problems)
anyways i now have new phone since that one become unreliable but i'm now looking at how i could fix the issue so i can use it as a spare phone if needs be.
it runs cyanogen mod android version 2.3.7 and i'd be looking at how i could go about updating to ice cream sandwich or jellybean, whichever has a stable build.
how would i go about doing this? (in simple terms - i'm a noob!)

neonflash said:
got a samsung galaxy captivate i897
bought it rooted running cyanogen mod & miui
was fine for about a year then the software kept crashing (everything was force closing)
in the this time i didnt do anything that would have caused this issue. i didnt update anything the only thing i did was install or uninstall apps. so i dont know why it occured. i dont even know if it happened as a result of having been rooted (if something became unstable - i wouldnt have thought so since it worked for a year with no problems)
anyways i now have new phone since that one become unreliable but i'm now looking at how i could fix the issue so i can use it as a spare phone if needs be.
it runs cyanogen mod android version 2.3.7 and i'd be looking at how i could go about updating to ice cream sandwich or jellybean, whichever has a stable build.
how would i go about doing this? (in simple terms - i'm a noob!)
Click to expand...
Click to collapse
Im glad you asked for ICS or Jellybean, CM 11 (Kitkat) is terrible looking. if you still know how to flash roms, we should probably figure out what version of CWM you have. other than that, if you have CWM 5.x.x.x or higher you can go ahead and download the top version here first http://download.cyanogenmod.org/?device=captivatemtd&type=stable and This Gapps for CM 10.2 http://goo.im/gapps/gapps-jb-20130813-signed.zip and put them both on your External micro SD card. boot into CWM and flash CM 10.2 first and then the Gapps after.

Trozzul said:
Im glad you asked for ICS or Jellybean, CM 11 (Kitkat) is terrible looking. if you still know how to flash roms, we should probably figure out what version of CWM you have. other than that, if you have CWM 5.x.x.x or higher you can go ahead and download the top version here first http://download.cyanogenmod.org/?device=captivatemtd&type=stable and This Gapps for CM 10.2 http://goo.im/gapps/gapps-jb-20130813-signed.zip and put them both on your External micro SD card. boot into CWM and flash CM 10.2 first and then the Gapps after.
Click to expand...
Click to collapse
problem is i dont know how to flash!
yeah sorry i'm a total noob
if there's step by step instructions though that'd be great

neonflash said:
problem is i dont know how to flash!
yeah sorry i'm a total noob
if there's step by step instructions though that'd be great
Click to expand...
Click to collapse
so do you at least know how to boot into Recovery? i haven't touched my Captivate in awhile but i imagine that its (turn off your phone first) hold volume up first then power button until the Samsung logo apears and tell me all the information thats on the screen. when your done you can use the volume buttons to navigate to reboot phone.

vol up & down and power yep :]
here's the options:
reboot system now
apply update from sd card
wipe data/factory reset
insall zip from sd card
backup and restore
counts and storage
advance
power off
go back
i selected reeboot now & have been left with a hat like this on screen :/ (dunno if that's good or bad!)
{
"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"
}
it's just the hat nothing else and has been like that for about 30mins......
phone's ****ed isnt it ?
optop of the options it say cwm based recovery v5.0.2.7

[Q] Paranoid Android OTA Problem

I installed the OTA update for the Android Paranoid ROM. When checking for updates, it mentioned something about not being able to check GApps update or something like that. I then downloaded the update and installed it through the OTA app. The phone rebooted and went into recovery mode, installed, and then shut down, it did not reboot. Now when I try to boot it, all I get is the Samsung letters, and then the phone shuts down again. I installed this rom on July 5th, and had installed an OTA update about a week ago.
What did I do wrong? What do I need to do to get it to boot and work again?
Any help is appreciated. Thanks!

tataocb said:
I installed the OTA update for the Android Paranoid ROM. When checking for updates, it mentioned something about not being able to check GApps update or something like that. I then downloaded the update and installed it through the OTA app. The phone rebooted and went into recovery mode, installed, and then shut down, it did not reboot. Now when I try to boot it, all I get is the Samsung letters, and then the phone shuts down again. I installed this rom on July 5th, and had installed an OTA update about a week ago.
What did I do wrong? What do I need to do to get it to boot and work again?
Any help is appreciated. Thanks!
Click to expand...
Click to collapse
You're going to have to factory reset it. Something broke in this update, as far as I can tell. The July 8th one is the one you should stay on until somebody from PA takes a look at why it's happening on the Skyrocket. Post about this in the Paranoid Android thread in the Android Development
forum for the device. I'm trying to throw together a bug report, but that'll take a couple hours until I get back to a computer.

crayonhead said:
You're going to have to factory reset it. Something broke in this update, as far as I can tell. The July 8th one is the one you should stay on until somebody from PA takes a look at why it's happening on the Skyrocket. Post about this in the Paranoid Android thread in the Android Development
forum for the device. I'm trying to throw together a bug report, but that'll take a couple hours until I get back to a computer.
Click to expand...
Click to collapse
Thanks for the help...I ended up doing the factory reset and installing the first rom I used back on July 5th along with the gapps from back then. Then I installed the July 8th update and haven't installed the latest update. I'm going to stay with this version for now.

tataocb said:
Thanks for the help...I ended up doing the factory reset and installing the first rom I used back on July 5th along with the gapps from back then. Then I installed the July 8th update and haven't installed the latest update. I'm going to stay with this version for now.
Click to expand...
Click to collapse
Hey! So update on this matter. There's been a new OTA update pushed out (pa_skyrocket-4.44-20140722.zip). That update works over OTA, so feel free to update to that version of Paranoid Android. Checked and running
{
"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"
}

S6 Fingerprint Reader Error after Update

I have a Galaxy SM-G920A S6 fully stock that was on 5.0.2. I recently got a update OTA for it to 5.1.1. Of course this update failed to load for some reason. I then downloaded the stock update 5.1.1 unmodified firmware and flashed it via Odin. Worked perfect. Then I tried using it for my fingerprint and this error came up.
{
"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"
}
I've tried rebooting of course. I tried resetting through recovery and wiping cache but it the error still pops up when I use anything related to the fingerprint reader.
Methods that I tried to use to Fix:
I read on a past thread, that if you disable the fingerprint service in application manager and then reboot and then enable, it fixes the issue. I tried that and it was the same thing. I've been reading a few Xda threads and it seems like there is no real fix for this.
This is the name of the file I installed: G920AUCU3BOI2_CL5527015_QB6363222_REV02_user_low_ship
I'm not aware if a newer version popped up, then I guess I could flash that and update.
Thanks in advance.

KillTheSprint said:
I have a Galaxy SM-G920A S6 fully stock that was on 5.0.2. I recently got a update OTA for it to 5.1.1. Of course this update failed to load for some reason. I then downloaded the stock update 5.1.1 unmodified firmware and flashed it via Odin. Worked perfect. Then I tried using it for my fingerprint and this error came up.
I've tried rebooting of course. I tried resetting through recovery and wiping cache but it the error still pops up when I use anything related to the fingerprint reader.
Methods that I tried to use to Fix:
I read on a past thread, that if you disable the fingerprint service in application manager and then reboot and then enable, it fixes the issue. I tried that and it was the same thing. I've been reading a few Xda threads and it seems like there is no real fix for this.
This is the name of the file I installed: G920AUCU3BOI2_CL5527015_QB6363222_REV02_user_low_ship
I'm not aware if a newer version popped up, then I guess I could flash that and update.
Thanks in advance.
Click to expand...
Click to collapse
Flash proper bootloader. Simple as that.

Rakcoon said:
Flash proper bootloader. Simple as that.
Click to expand...
Click to collapse
Sorry I'm really a noob at this. Proper bootloader? What do you mean by that? I'm trying to keep it stock.
Is the firmware I flashed wrong?

what's your model? Country?

Rakcoon said:
what's your model? Country?
Click to expand...
Click to collapse
It is model SM-G920A
Full length name is SM-G920AZDEATT
I'm in the united States.

Rakcoon said:
what's your model? Country?
Click to expand...
Click to collapse
I flashed only the AP file in Odin when I updated. Should I have updated the other files as well?

I fixed it by not being an idiot, and flashing all the files in update.
D:

Hahaha good!

can you tell me how to fix it? where did you download the file? what are you using for the installing? pleasee i want to know i have the samew problem

S7 battery life issues on Oreo, Nougat, Stock, Superman etc.

Hello all,
Whilst there are many posts like this about battery issues, I thought I'd make my own because I've already tried all the approaches I can think of and I'd like to avoid any unnecessary confusion between posters.
I have less than 3 hours screen-on time on my Samsung S7 SM-G930F (international model) and horrific standby time, meaning I'll run out of battery before the end of the day even if I don't touch the phone at all. When I first got the phone, I got 4-6 hours screen on time and I see no reason why this should have changed so drastically. This is a somewhat recent occurrence, over the last 2-6 months (I believe it was gradual, so I can't quite pick out the time it started happening).
{
"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"
}
So far, I have tried:
Factory reset
Uninstalling all unnecessary (non-core) apps
replacing the battery
draining and recharging the battery fully
underclocking the processor
a multitude of different stock ROMs, both Nougat and Oreo
a few different Kernels
At best, playing around with these options has net me maybe a 5-15% improvement overall, much less than the 70-100% improvement I need to get back to what I had during early Nougat / late Marshmallow days.
Bar literally just getting a new phone, I would appreciate any advice you can give me.
EDIT: System2 log:

Was the flashing of different ROM's via TWRP or Odin?

Beanvee7 said:
Was the flashing of different ROM's via TWRP or Odin?
Click to expand...
Click to collapse
TWRP

I'd recommend making a full backup in TWRP, saving it to your PC, then doing a full Odin flash using all 4 firmware files. It's the only method that ensures a complete fresh start.
It will mean you have to install TWRP again, but then you can at least be sure that you've cleaned out literally everything.

Beanvee7 said:
I'd recommend making a full backup in TWRP, saving it to your PC, then doing a full Odin flash using all 4 firmware files. It's the only method that ensures a complete fresh start.
It will mean you have to install TWRP again, but then you can at least be sure that you've cleaned out literally everything.
Click to expand...
Click to collapse
I formatted internal storage via TWRP more than once though. I would have thought that would have fixed it.

I've added a System2 log for extra information in the OP

Well if you're leaving behind a modified bootable custom recovery, the device isn't clean, and could still have corrupted, fragmented, or badly partitioned boot files that affect all subsequent installs.
A full Odin flash is the closest thing to an out of the box system, it fixes almost all software bugs and issues. I can't guarantee it will fix your issue, but it's the only thing you've not done.

Beanvee7 said:
Well if you're leaving behind a modified bootable custom recovery, the device isn't clean, and could still have corrupted, fragmented, or badly partitioned boot files that affect all subsequent installs.
A full Odin flash is the closest thing to an out of the box system, it fixes almost all software bugs and issues. I can't guarantee it will fix your issue, but it's the only thing you've not done.
Click to expand...
Click to collapse
Ok. Thanks a lot. I'll try it and report back in a few days.
I'll probably need to get the latest files from Sammobile (more like Sam-slow-bile).

samfirm tool still works for obtaining the latest firmware files, and I get max speed using it on my internet (100mbs down)
For older versions you might have more luck with updato.com, for me I get almost full speed if I use a download manager, but it does have a bit of a slow start period.

hey bro i have the same issue in oreo so its not worth downgrading to 7.0 ? .... these samsung have the most lowest battery life from all phones ... god btw what is that app your using ?

dengiz-islam said:
hey bro i have the same issue in oreo so its not worth downgrading to 7.0 ? .... these samsung have the most lowest battery life from all phones ... god btw what is that app your using ?
Click to expand...
Click to collapse
Change battery in Samsung service

Finnishman said:
Change battery in Samsung service
Click to expand...
Click to collapse
Hey, I was about to open a new topic, but maybe you could answer me here I was about to change the battery I installed an app called AccuBattery when I go to health it shows that my battery health is 48% and the estimated capacity 1.429mAh is the battery dead? I don't know if those are also acurate stats what you think? when I calculated how much I lose me with apps and stuff it exactly comes out like 1.400mAh huh? ...