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

[Q] Rooted Droid 2 Global issues

So I recently bought a Droid 2 Global off of ebay. I got the phone and it was relatively fine. It came with the android 2.3.3 system. I decided that I want to flash cyanogenmod onto it. I rooted it and that went fine. I then attempted to open up the cyanogenmod from clockworkmod recovery. This didnt work. I kept getting an error message. So I gave up and did a factory reset and wiped everything. Unfortunately this solved none of my problems. The phone would boot up only to get stuck at the motorola "m". I couldnt go into either the stock recovery or the clockworckmod. I thought maybe if I pull the battery, my sd card, and the sim card things would get better. Nope. The phone wouldnt even turn on after that. Maybe its a battery issue? I let it charge in the wall charger all night. Currently its on only when plugged into the wall and is still stuck at the "m".
I have no idea what to do anymore. Any help would be appreciated!!

reanjo said:
So I recently bought a Droid 2 Global off of ebay. I got the phone and it was relatively fine. It came with the android 2.3.3 system. I decided that I want to flash cyanogenmod onto it. I rooted it and that went fine. I then attempted to open up the cyanogenmod from clockworkmod recovery. This didnt work. I kept getting an error message. So I gave up and did a factory reset and wiped everything. Unfortunately this solved none of my problems. The phone would boot up only to get stuck at the motorola "m". I couldnt go into either the stock recovery or the clockworckmod. I thought maybe if I pull the battery, my sd card, and the sim card things would get better. Nope. The phone wouldnt even turn on after that. Maybe its a battery issue? I let it charge in the wall charger all night. Currently its on only when plugged into the wall and is still stuck at the "m".
I have no idea what to do anymore. Any help would be appreciated!!
Click to expand...
Click to collapse
Have you heard of "sbf" ing?
I'll try to find a link...
SBFing allows you to install a complete stock firmware image - should fix those problems. Factory data resetting only deletes all of your data (everything past the /data partition)
Your android system (OS, firmware, etc, etc) is in the /system partition
If you got an error while installing CM, you may have put it into a bootloop - depending on where the error was at. Installing a rom starts by formatting the /system partition, then copies the CM version of /system from the zip file. If you got an error after the format, then you don't have an os to boot from. Also that means your recovery is gone. That means your only choice is an SBF. (what you did is commonly called soft-bricking)
(any mods/devs may correct me as needed but I'm fairly sure this is right...
---------- Post added at 01:31 AM ---------- Previous post was at 01:09 AM ----------
Links can be found on a text file on my website. It's at ftp:// kd8rho (dot) net (slash) factory_reset_links.txt
I can't post links, so that's what I have to do... I hate these new member restrictions!
Link for rsdLite: link 1 on the text file
rsdLite is the program you need to use to sbf back to stock.
They have instructions on there, but you need to use the sbf file found at link 2 on the text file, instead of the one on their page.
Instructions:
Download rsdLite.
Install rsdLite
download the sbf file above (NOT THE ONE ON CYANOGENMOD'S SITE!!!!!)
use the instructions to flash the SBF
If you get an error or can't flash, follow the instructions on link 3 on the text file

if your phone is stuck at the m
most likely not charging
if battery gets too low, it will be unusable
try ezSBF
{
"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"
}
also lots of links sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my DROID X2 using xda premium

Reference the DROID Wiki for instructions on re-flashing stock firmware and information about the different firmware versions available. Note that if your phone has ever had the newest firmware version installed (4.5.629/Android 2.3.4) it will not boot after flashing any older version.
If you are able to boot into ClockworkMod Recovery, you may still be able to flash CyanogenMod without first re-flashing a stock firmware. Be sure to select a CM build based on the same kernel version as the one installed on your phone (if your Motorola "M" logo during boot is red, you have a Gingerbread kernel; if it's white/silver, you have a Froyo kernel). Official builds of CM target the Froyo kernel only; unofficial builds work with the Gingerbread kernel and are generally better-adapted to the specific model handset you're using. Look in other threads on this forum or on RootzWiki for information on and download links for unofficial builds.

Help needed - Stock Firmware reinstallation via KIES caused Boot Loop

Hi guys.
I have a little problem with my tab now . Originally my machine had a little hiccup ever since I upgraded to Lollipop. The problem was that it tried to upgrade apps to Lollipop every time I did a boot cycle. Usually ending with a message that an app called "a...a" closed. I did not bother me much for a while. But Today I thought it was past time I resolved this so I tired to reinstall the firmware with Kies. Bad idea in retrospect, since it caused a boot loop at first (I did not touch it for 1-2 hour) than after seeing that it did not progressed. I tired a forced restart by holding down the power button. Strangely somehow after 2 or 3 tries it did started to do something. Saying that it has to update 190 apps and it did so, after then I found myself at the first setup page. However it did not worked because a lot of warnings come up constantly like: google process stopped, maps stopped, etc... making it unusable to set up anything, since even if you OK the warning the next comes up constantly. Also Kies no longer detects the phone, so I was forced to use Odin to reflash it. But here's the twist: even after reinstalling the same version of the stock image via Odin the continuous boot loop occurs again and again. (The image I got it from samdownloads de). I'm unsure where the problem can be, the only thing I can suspect is that I only used AP with Odin since the rar did not contain any bl cp csc or anything (I also tired full wipe via recovery but it did not help). So if anybody have any idea as to what direction should I take, please say so. I would really appreciate the guidance.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.

quarros said:
Hi guys.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.
Click to expand...
Click to collapse
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21

Beut said:
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21
Click to expand...
Click to collapse
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?

quarros said:
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?
Click to expand...
Click to collapse
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
{
"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"
}

Beut said:
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
Click to expand...
Click to collapse
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again

quarros said:
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again
Click to expand...
Click to collapse
From my experiences, these things have nothing to do with flashing a firmware:
1- Fresh installed windows, I use XP or Windows 7, there is nothing different as long as you have correct Samsung USB driver.
2- Odin versions have no differences, I use old or new, they are both the same.
3- Home button is not needed to access Download or Recovery Mode
Your problem went away probably from fresh install of the system.

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

Display broken after root

Hi all
I'm having a strange problem with the display after rooting my Galaxy S7. The screen has stripes, is flickering and having weird colors, see image below. The touch functionality is still working.
As it was happening just after the rooting (using CF-Auto-Root), I'm still having the hope that it is a software issue and can be fixed somehow.
What I did:
- the first thing on the brand new device (unknown firmware) was rooting the device using CF-Auto-Root. This was working well.
- I installed Titanium Backup to get rid of the bloatware. Possibly I've deleted too much, after the reboot the device was hanging on the boot logo (bootloop?)
- I've downloaded latest firmware (G930FXXU1APD1 [DBT]) and installed it via ODIN
- Device was again working and everything was looking fine
- I've tryed to root again using CF-Auto-Root with the same file I did it with the shipped firmware. After one of these restarts during root, the problem started.
Except the weird screen, everything looks good so far. I've also tried to flash G930FXXU1APD1 again, but no change. Even on boot logo, in recovery and download mode, the screen looks like that. possibly something with the display driver?
I hope there is another way to fix it than bringing it back to the shop and hope that they will not refuse the repair because of knox flag (the firmware is shown as official).
{
"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'm aware of the risks that rooting brings, but I have the hope that all modifications or problems can be reverted by flashing something fresh, as long as the recovery is accessible [which is]).
Any help is appreciated.

This looks bad. Hope you can fix it!

I seriously doubt that this was caused by rooting or flashing the firmware. You've got a faulty screen.

This has nothing to do with rooting.
This is clearly a Hardware defect. Root is only a Software modification.
Gesendet von meinem SM-G930F mit Tapatalk

Have seen many people with this faulty screen. This should be a hardware issue. Get it replaced
Sent from my Silver Titanium Galaxy S7 Edge

BigMani said:
Hi all
I'm having a strange problem with the display after rooting my Galaxy S7. The screen has stripes, is flickering and having weird colors, see image below. The touch functionality is still working.
As it was happening just after the rooting (using CF-Auto-Root), I'm still having the hope that it is a software issue and can be fixed somehow.
What I did:
- the first thing on the brand new device (unknown firmware) was rooting the device using CF-Auto-Root. This was working well.
- I installed Titanium Backup to get rid of the bloatware. Possibly I've deleted too much, after the reboot the device was hanging on the boot logo (bootloop?)
- I've downloaded latest firmware (G930FXXU1APD1 [DBT]) and installed it via ODIN
- Device was again working and everything was looking fine
- I've tryed to root again using CF-Auto-Root with the same file I did it with the shipped firmware. After one of these restarts during root, the problem started.
Except the weird screen, everything looks good so far. I've also tried to flash G930FXXU1APD1 again, but no change. Even on boot logo, in recovery and download mode, the screen looks like that. possibly something with the display driver?
I hope there is another way to fix it than bringing it back to the shop and hope that they will not refuse the repair because of knox flag (the firmware is shown as official).
(I'm aware of the risks that rooting brings, but I have the hope that all modifications or problems can be reverted by flashing something fresh, as long as the recovery is accessible [which is]).
Any help is appreciated.
Click to expand...
Click to collapse
I agree with what other said. This has nothing to do with rooting. Somehow the bad display showed off it's real colors coincidentally after you root. Only way is to approach Samsung ASAP for warraty repair. Not sure whether they will check the device is in 'modifed' state (rooted) or in 'official' state for any such serious hardware issues. But you gotta say a lie about when this issue popped up. That's it. If you're lucky you will get the LCD replaced.

Hi all
many thanks for all your feedback. under the condition that we believe it is a hardware issue, I can keep my decision about doing the rooting, on the other side I will never understand why it was happing exactly at that moment.
However it seems that I had extremly luck. Today I went to the shop where I've ordered it online and they informed be about the DOA (Dead-On-Arrival) warranty, which is only possible within 7 days after purchase - today was day 7
they did just replace the device with a brand new one, they even didn't had to send it to Samsung before giving me a replacement. I was walking out with a new device :angel: :angel:
To finish here, I tried now exactly the same process as on saturday: first flashed latest firmware G930FXXU1APD1 and then I applied CF-auto-root. You can't imagine how nervous I was during these few reboots and hoping that the same problem does not reappear again (I could not go a second time to the shop with the same issue...). but this time all went well. latest firmware, rooted and now also debloated a bit.
again thanks to all of you.