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] Why does it do this?

Every ICS ROM that I have flashed on my phone has done this. I never hear anyone discussing this and I can't be the only one. Why and is there a fix?
{
"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 get it in the app drawer as well.

Have you done a full wipe and is hardware acceleration enabled?

Not So Strange...
Well,it backs to several things:
Did You Fully wipe?
What's device current Recovery?
What was your previous Firmware?
Did the Roms you use,support GPU rendering ?
How is your device like with official firmware?
And several other things...

peter_dizai said:
Well,it backs to several things:
Did You Fully wipe?
What's device current Recovery?
What was your previous Firmware?
Did the Roms you use,support GPU rendering ?
How is your devce like with official firmware?
And several other things...
Click to expand...
Click to collapse
Yes, I always do a full wipe when flashing roms.
5.0.2.0
It does it eventually, regardless of the previous firmware.
I believe so, all roms that I flash come from here.
I just flashed a root access version of the IMM76D ROM and it happened on that one.
It only happens every so often, and a reboot is in order to correct it.
Thanks guys.

Now,It's Better...
kazerak2 said:
Yes, I always do a full wipe when flashing roms.
5.0.2.0
It does it eventually, regardless of the previous firmware.
I believe so, all roms that I flash come from here.
I just flashed a root access version of the IMM76D ROM and it happened on that one.
It only happens every so often, and a reboot is in order to correct it.
Thanks guys.
Click to expand...
Click to collapse
Ok,first try to flash latest official firmware which I think is:
Ics 4.0.4
Baseband Version: D720SPRKH1
Build Number:IMM26
and here is a how to:
http://www.techzek.com/how-to-update-sprint-nexus-s-4g-on-android-4-0-4-ics-firmware/
Afterward flash following recovery:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo.img
Then try to flash:
http://bigota.d.miui.com/2.3.30/miui_NS_2.3.30_c1e078377e_4.0.zip
or
a cyanogenmod 9 and report back please...

^ Is that the correct firmware to flash for the 4G nexus s?

That looks like a launcher problem to me. Are you using an aftermarket launcher or are you restoring it from a previous install?

wild1z said:
That looks like a launcher problem to me. Are you using an aftermarket launcher or are you restoring it from a previous install?
Click to expand...
Click to collapse
Stock launcher, I've never used a different launcher other than stock on all my ICS ROMs.

I Edit the firmware,check and flash it.

Update, my phone did it again and I thought I would check the launcher. I did a "force stop" on the launcher and that resolved it. I have always used the stock ics launcher what would cause the launcher to behave this way?

kazerak2 said:
Update, my phone did it again and I thought I would check the launcher. I did a "force stop" on the launcher and that resolved it. I have always used the stock ics launcher what would cause the launcher to behave this way?
Click to expand...
Click to collapse
See my signature for proper FULL wipe. Something tells me you're not wiping system.

I'm having the same problem with one of 2 Nexus S 4G's I flashed with IMM76D. I did a full proper wipe on both of them, but one seems to corrupt the text like in the picture. It happens after it's been running a while and a reboot fixes it temporarily.I wiped it fully again and reloaded the ROM and its still doing it.
Next thing to try is re downloading the ROM. Maybe a corrupt download? Any ideas?

[email protected] said:
I'm having the same problem with one of 2 Nexus S 4G's I flashed with IMM76D. I did a full proper wipe on both of them, but one seems to corrupt the text like in the picture. It happens after it's been running a while and a reboot fixes it temporarily.I wiped it fully again and reloaded the ROM and its still doing it.
Next thing to try is re downloading the ROM. Maybe a corrupt download? Any ideas?
Click to expand...
Click to collapse
I too have done a full proper wipe with that same rom and still have the issue from time to time. Next time you get it try to fore stop the stock launcher. That fixes it for me, until it happens again. But for me its something with the stock launcher.

[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.

[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"
}

"No SIM card - 31000" - Galaxy S5 G9000P

Recently I have flashed my S5-G9000P for the first time with the Resurrection OS RR-O-v6.0.0-20180405-klte-Official.
After working alright for the first day or so, texts would not send. Then, at the top of my screen it says "No SIM card - 31000". I don't really know much about modding phones, so here is what I tried so far:
- Resetting the phone
- Removing the SIM card then reinserting, then resetting the phone again
- Resetting my mobile data options
So far these above options haven't helped the problem. I have looked at similar threads to this and none seem to have the same problem based on their descriptions.
Thanks for your time.
Phone - G9000P Galaxy S5
Android Version - 8.1.0
Kernel version (if that's important) - 3.4.113-lineageos-g592be94 (gcc version 4.9.x 20150123 (prerelease) (GCC) ) [email protected] #1 Thu Apr 5 13:41:19 CEST 2018
{
"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"
}

Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.

Well I can State the Facts... has happened here tooooo..... on LineageOS 16 and 15.1. The only fix that I have done, which may help, is Rebooting the Phone.
Yep, tat was the only thing I actually have done, When and IF it happens.
Same thing though, "NO SIM Card" " Corrupt Sim Card" and I Tink there was another one too. All if which, (Knowing that it was running correctly, prior this) I just rebooted. maybe once, maybe like 3-4 times. before it actually goes away.
Now, knowing the phone was running correctly is the Key , I believe. IF your in the process of Flashing, yep, maybe restart that. However, if its running right an all, no reason to do any flashing. why--- Well, was built in the First run batch of them. the phone is rather good and all, cant even see me spending over a $1,000.00 for a new phone, that's Ficking Nutz !!! I am sure, they did built it to last a life time, but what is it, a cell phone built in 2012. Before my warranty was over, I rooted, and got rid of all thre Samsung crap. Ran smooth. Been Flashing ever since.....

E.4.113-LineageOS-g592be94 mobile data not working
Hippie459MN said:
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Click to expand...
Click to collapse
You have in your signature a new rom, does that rom is working ok? The only thing that is driving me nuts is that I can’t have my data usage, I installed RR-O-v6.0.0-20180405-klte-Official on my gsm900M what do you suggest!?
Edited, i found it! just needed to edit the APN settings! i google them for my case that is Mexico, and now i have mobile data!!

Im still running lineageOS. I just havent updated my signature yet. I am going to be getting a new phone in the next week or so though. Pretty sure the motherboard (Internal storage) is taking a dump on me. Phone will work great sometimes for 2 weeks then apps start crashing like mad and only way to fix is to uninstall and reinstall and only way to fix it is to do a full wipe and reinstall the rom. Sometimes it will even start messing up within an hour or two. Things like google play services, the stock dialer, and bluetooth will randomly crash. I have tried just about everything. Different roms, going to stock software, nothing works. And when it tries to do do a backup in TWRP, it always fails in the data partition and always at different points saying it cant read the data partition or some junk. I forgot but I am giving up on it. I have another S5 but wont have it for another week or two.