Database Develop

Booting with Removed SD wreaking havoc. Need help.

I seem to have done some real damage to my phone and I could definitely use the help of fellow XDA'ers. I took my memory card out to put some files on my PC. Phone was off so no problems. I reinsert the SD card and reboot. Now although I'm absolutely sure the card was fully inserted, once the phone fully booted I had the "SD Card removed" icon in the corner and everything started to force close. So I quickly shut the phone off, made sure the card was fully in, and rebooted again. it loaded up again, and while the no SD Card removed error was gone, I was still getting FC's left and right and apparently have no gps, no wifi, and no 3g. So I once again rebooted into recovery, ran the fix permissions and rebooted. Again, booted up and FC's everywhere. So now about 90% of my apps FC on launch (either actual launch of the phone or by pressing the icon), I can't activate WiFi or GPS, and I have no data/3g. What happened and how can I fix this? Thank you so much in advance for your help.
Edit: After a little more fiddling, I find that I can't change any settings. I can't set screen timeout, notification levels, so on and so forth. What happened?

FatBoyExtraordinaire said:
I seem to have done some real damage to my phone and I could definitely use the help of fellow XDA'ers. I took my memory card out to put some files on my PC. Phone was off so no problems. I reinsert the SD card and reboot. Now although I'm absolutely sure the card was fully inserted, once the phone fully booted I had the "SD Card removed" icon in the corner and everything started to force close. So I quickly shut the phone off, made sure the card was fully in, and rebooted again. it loaded up again, and while the no SD Card removed error was gone, I was still getting FC's left and right and apparently have no gps, no wifi, and no 3g. So I once again rebooted into recovery, ran the fix permissions and rebooted. Again, booted up and FC's everywhere. So now about 90% of my apps FC on launch (either actual launch of the phone or by pressing the icon), I can't activate WiFi or GPS, and I have no data/3g. What happened and how can I fix this? Thank you so much in advance for your help.
Edit: After a little more fiddling, I find that I can't change any settings. I can't set screen timeout, notification levels, so on and so forth. What happened?
Click to expand...
Click to collapse
Tried repairing ext file systems?

FatBoyExtraordinaire said:
I seem to have done some real damage to my phone and I could definitely use the help of fellow XDA'ers. I took my memory card out to put some files on my PC.
Click to expand...
Click to collapse
Windoze no doubt. Windoze is HOSTILE to non-MS filesystems and WILL attempt to destroy them.
Other possibility is that you simply didn't click the card in all the way.
Anyways, what has happened is that your phone booted up and was missing a ton of applications that it was expecting. It therefore irreparably destroyed your package configuration.
You MIGHT be able to salvage it if you have a recent backup of the file /data/system/packages.xml.
Try restoring that file, syncing the filesystem, and rebooting via 3-finger-salute INTO RECOVERY ***IMMEDIATELY*** after syncing. Then do a fix permissions and reboot normally.
... and cross your fingers.

r3s-rt said:
Tried repairing ext file systems?
Click to expand...
Click to collapse
I did that, but it was a no go. Everything still FC'd, couldn't change any setings, and it says my phone doesn't have internet permission, so anything requiring data access doesn't work.
lbcoder said:
Windoze no doubt. Windoze is HOSTILE to non-MS filesystems and WILL attempt to destroy them.
Other possibility is that you simply didn't click the card in all the way.
Anyways, what has happened is that your phone booted up and was missing a ton of applications that it was expecting. It therefore irreparably destroyed your package configuration.
You MIGHT be able to salvage it if you have a recent backup of the file /data/system/packages.xml.
Try restoring that file, syncing the filesystem, and rebooting via 3-finger-salute INTO RECOVERY ***IMMEDIATELY*** after syncing. Then do a fix permissions and reboot normally.
... and cross your fingers.
Click to expand...
Click to collapse
I'm guessing I didn't click it all the way in because I have done this 100's of times before and it never happened. Unfortunately, I don't have a recent back up of that file so it's sounding like i am screwed. Would i be able to just wipe the phone, the ext, the cache and start over from scratch?

It seems I may be out of the woods. It's going to be a tedious solution, but at least I won't have to wipe anything or unroot or so on. Basically I have to uninstall and then reinstall everything to end the FC's and restore settings and data. It was actually the Maps update that helped me figure this out. I got the notification that there was an update so i followed it and upgraded. The fact that it notified me and then allowed me to download the new version told me the net was working. I also had another app that needed to be updated that was also fc'ing. So i upgraded that app and viola, no more fc and the 3g was working. So i uninstalled other apps that were giving me trouble with settings and data like Quick Settings and Tweetcaster, reinstalled and now I'm good money. I've got 144 apps installed so it's gonna take a few hours, but it's worth it to have my phone back. Thanks again for the advice.

[Q] infinite boot and many other problems

I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.

so no one has any idea what i'm doing wrong? or has experienced similar problems?

Try to reinstall the drivers in kies.
If that don't work do download
Them from android development site.
It should work.
Try the phone in all mode you can to get the drivers to install right.
Then you can try to fix it with kies or odin.
**DamianGTO Steam kernel. 349MB Ram. 256HZ. ext2. js3 base**

Another approach
I too cannot get odin or kies (or usb mass storage) recognized on the PC. I tried for a long time and gave up.
Are you rooted or can you access the root dir? If not can you access the external SD card or market so that you can root?
Do you have clockwork mod or similar?
I can only base my experience never using odin or a pc...
If you can get into recovery mode and start using (if you do not have it already)clockworks mod (and/or steam recovery - which I highly recommend as it can access the removable sd card which is useful to load stuff on to when things go sideways see why in my post http://forum.xda-developers.com/showthread.php?t=929020 ).
Then you can flash whatever you want from the root directory or with steam from the external SD car (root dir there) no odin or pc required (directly).
Then I'd start with stock or at least a custom rom that is based on your carriers stock and go from there.
G

wastedkila said:
I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.
Click to expand...
Click to collapse
Hey!
I've had the EXACT same problem as you. did you try to put your phone into DOWNLOAD MODE (Close phone, then hold volume down, then home, then power) to see if it connects to odin? Also, before you do anything, make sure you turn on odin first and then select all the files you want. After thats done, then put your phone into download mode, then connect the phone to your computer thru the USB.

[Q] Problem with computer recognizing phone?

After much searching and work on fixing my bricked captivate, i broke down and bought a jig from mobiletechvideos.com. It works perfectly as intended, except for the fact that my pc is not recognizing the phone after it enters download mode. As a side note, i may have royally screwed up when i did something in clockwork recovery, where now i cant even get past the ATT World phone boot screen. Im afraid i may have deleted anything that can mount the phone to the pc. I have already installed the proper drivers, I think. Anything i can do to fix this?

So it shows the world phone screen a bunch of times? Plug it into an outlet see if the green battery comes up, just wait for it, the Gray battery will do a short of loop a few times... Once its at the green battery try to turn the phone on, be patient too, if you get the phone on, go to settings> privacy then factory data reset, make sure you backup to external or computer first
Your welcome
Now you say/press thanks
Teaching manners one person at a time

Thats not gonna work... nothing i know of can be done to it. it doesn't move past the att screen. No animation, not sound. Just ATT World Phone. i can get into download mode, but cant connect to computer. Thats the problem right there.

Try restarting your computer? I've had similar issues on a yucky iPhone, and I've read about other Captivate users with it as well, and a restart helped resolve the problem.

Go under your drivers and uninstall them and reinstall them it helped when I finally had got mine "back to his construction job" (lol download mode) it should then work
Sent from my SAMSUNG-SGH-I897 using XDA App

Ive already tried another PC and Uninstalling and reinstalling the drivers to no avail.
It just like the phone isn't even there. It will charge, but wont mount to the PC.

Not trying to insult your intelligence or anything (I might actually be insulting my own) but you have Odin open, right?
Just trying to think of anything lol

Yeah, but it wouldnt matter anyway if the computer doesnt know its there.

Try cleaning the mini usb port. Or switch the usb cord connector the samsung factory one tends to break the data + and -.
As for not getting past the at&t screen. The kernel you installed cannot read the system partition probably corrupted or the kernel you installed cannot read ext4.
If you cannot get it to be recognized send it back to your carrier for repair, should be under warranty.

Thats what im doing now. Thanks for the help, though.

Palen222 said:
After much searching and work on fixing my bricked captivate, i broke down and bought a jig from mobiletechvideos.com. It works perfectly as intended, except for the fact that my pc is not recognizing the phone after it enters download mode. As a side note, i may have royally screwed up when i did something in clockwork recovery, where now i cant even get past the ATT World phone boot screen. Im afraid i may have deleted anything that can mount the phone to the pc. I have already installed the proper drivers, I think. Anything i can do to fix this?
Click to expand...
Click to collapse
You sure you have the proper drivers installed for your phone? The links for them are on the odin forum in captivate development
Sent from my SAMSUNG-SGH-I897 using XDA App

Retrieving Data on Broke Phone

Need someone with tons of knowledge here to help me out
I'm currently dealing with a Nexus 6, unrooted, stock.
The phone was dropped and the screen was destroyed. During the drop something internally must have been damaged as the phone starts the At&t music up and resets immediately and will keep looping until the power dies or I put it into the fastboot screen to shut it up, in which the phone stays on that screen. (or at least theres where im assuming its going)
The thing is, my computer recognizes the phone as an android device and shows the android device bootloader on my device manager on my cpu. Every time I try to get into recovery (or at least how I recall doing it without a screen to assist) the phone just restarts to the at&t music once again...
Is there any hope here for retrieving my data on this thing? I figured I could do something with adb although im not too savvy with it. Just assuming since the computer does recognize the device in some way, it is possible hopefully.
Btw I dont think debugging is on atm.
Any help would be super appreciated. Even willing to donate to anyone that may be able to assist me in this.

If and when Mobiletechvideos gets back up and running, they can more than likely save the entire device and if not at least get your data. But unfortunately because of the high demand for their services, they have gone into a temporary work hold until all current orders are complete. Either way, I would try to get ahold of them and see if they can assist or can point you in the right direction.

If it is unrooted with stock recovery and not booting up to android, there will be no easy way to get your data off.
It is possible, though very unreliable and extremely difficult to unlock the bootloader, flash a custom recovery, create an image of the data partition and scan that on a computer with data recovery software, but that really isn't worth doing.

hi ... how r u .... i have this problem too .... broken screen ... screen totally black ..... stock rom no root no recovery ...... debuging not enabled
http://forum.xda-developers.com/showthread.php?t=2786395&nocache=1
this guy said in his thread i can access the phone via computer but i need to enable debugging which i donno how to do with screen totally black
any suggestions is really appreciated

Recovery without losing data

I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions

There is no chance for you to recover your data in this mode.

WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again

Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.

Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.

phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...

How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future

phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...

mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.

First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.