Database Info

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

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

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

Question Massive system storage use on Stock OnePlus 9 5G

Hey everyone. I've been looking through Forum posts everywhere and can't seem to see anything recent concerning this issue that actually solves it.
My system data is taking up an extremely abnormal amount of space. So much so that I have to routinely prune my already limited photo, video, and file storage or my device runs out of space to store temp and application files. Has anyone found a decent way to fix this outside of starting from scratch?
I have a stock OnePlus 9 5G running Android 12 (LE2115_11C.48), tho it had been an ongoing issue since before Android 12...
{
"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 seems like a known issue that has no resolution but factory reset and switch to a non-OOS ROM.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
There is some suggestion that it's dump files being constantly created.

Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.

dallen.baldwin said:
Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.
Click to expand...
Click to collapse
Not that I'm aware of. Temp root exploits are closed pretty quickly once discovered and the act of unlocking the bootloader causing the phone to be wiped is a security mechanism since having an unlocked bootloader could potentially give way to an easier method of extracting your data off of the device.

until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.

jmadiaga said:
until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.
Click to expand...
Click to collapse
What's scary about it? It's really not that bad as long as you read the instructions. I have flashed this thing 3 or 4 times now and it's no worse than any other phone I have ever had.

That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?

dallen.baldwin said:
That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?
Click to expand...
Click to collapse
If you can type fastboot commands into command prompt, it's really not that difficult. I actually often found flashing with TWRP to be more irritating because of weird errors and sometimes it would refuse to factory reset and make a really big mess for me.
Now you just download the ROM and the recommended recovery, flash the recovery, boot to recovery, flash ROM, and you're done. Obviously read each ROM's instructions though because some like StagOS require you to do other stuff (you have to flash a partition file with that one).
I personally recommend StagOS. The only thing I found wrong with it was that it didn't support Verizon (no signal with a Verizon network SIM) but the dev is working on that and the fingerprint sensor icon wasn't lined up properly which apparently not everyone had that problem. I have tried a few others and had different issues with each of them. Derpfest is pretty good too but sometimes my apps act like I have never run them and I had a weird crash when swiping down on the status bar earlier. I plan to go back to StagOS. In fact, I am going to just go ahead and do that right now.
If you want to save yourself some annoyance, if the phone doesn't have OOS 12 on it when you get it, don't flash it to OOS 12 or you'll have to downgrade it to make sure you have a firmware match.

Dang.. I thi k I already went to OOS 12 since I'm on Android 12

dallen.baldwin said:
Dang.. I thi k I already went to OOS 12 since I'm on Android 12
Click to expand...
Click to collapse
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.

EtherealRemnant said:
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.
Click to expand...
Click to collapse
When you go back to os 11 you will experience duplicate media storage issue.. I just flashed os13 stable currently shows 7GB of data on ' others ' , don't know if will continue grow..keep my eye peeled..