Database Develop

[Q] Multiple Captivate problems

Today I turned off my Captivate for the first time in a couple days. When I turned it back on, it went through the ATT and Galaxy S animations, then remained at a black screen. It then vibrated on semi-regular intervals, in triplets, kind of like when an app force closes. I went to recovery mode and deleted user data, so now the phone boots into android. It starts with the setting up the phone tutorial, but whenever I get past the Google Location Services page the PhoneSetupWizard crashes then restarts. I cannot seem to get by this into the rest of the OS.
Possible cause: I was messing with a settings database a few days ago to try and enable side-loading. For some reason I feel like I may have accidentally deleted that whole .db file, which is obviously a problem.
What would be the best thing to do so I can get back to using my phone normally again? Would it be easiest to flash a new rom?

Flash stock using odin
Sent from my SAMSUNG-SGH-I897 using XDA App

Alternatly, install any custom rom as an update.zip, or install clockwork recovery zip and install any custom rom zip file.

Thanks I'll probably go the custom rom route. And do you know why the phone setup wizard app would continually crash? Is it possible that clearing user data through the android recovery menu deleted part of it, stopping the phone from functioning? If so, it makes android recovery rather useless. Installing clockwork recovery would be a good choice.

Flash gone wrong

Hi,
I've flashed multiple times before without an issue until today.
First, here's my background information:
Samsung Captivate (ATT)
Was running Continuum 5.4.1 but it felt laggy so I attempted to flash MIUI 1.5.13.
Here's what I did:
I wiped my phone using the Odin One click tool, then flashed CM7's kernel and then performed formats of the cache, system, and data, then installed MIUI RC2. After this step the phone should have restarted, then I planned to shut it down and reboot into recovery and flash 1.5.13 onto it.
My problem(s):
-Boot into recovery/download mode using key combinations is not working.
-The ADB console reports device not found when I try to run adb shell.
-The phone is undetected in Droidexplorer.
-When I attempt to download an app to boot to recovery with the phone says there is no space even though nothing has been installed other then MIUI.
What I would like to do:
Get back to stock with download/recovery modes working.
On a side note: MIUI works, but in a very limited way. I can navigate through it, but it won't allow the installation of applications due to there not being room on the phone (as said before).
Thanks!
Update - my phone was being identified as a Nexus S, so without those drivers my phone could not be debugged via USB. I now have the drivers and can perform ADB commands, however rebooting into recovery and into download mode both result in the phone restarting without going to the download or recovery mode.

Try using ODIN and repartitioning. I have good videos on standard ODIN and Heimdall on YouTube just search them. If you can not get out of this contact me, I have been able to partition debrick in the past and it's actually considered by me far more annoying than standard bootloader JTAG in certain situations. Let's hope yours is easier to bail out of!

First of all thanks for the reply and direction.
Secondly:
After working on this all last night I was able to get the phone recognized by Odin and my computer, now I am stuck at one of two screens depending on what I do.
If the phone is powered off then plugged in, the battery charging screen appears but there is no animation and after unplugging it the battery charging image remains.
If I power the phone on it hangs on the Samsung boot screen.
Repartitioning does sound like the proper direction for me to take, but, when I use Odin it freezes while setting up the connection to the phone.

when the phone is powered off try holding both vol keys and plugging in the cable. That could possibly get you to download mode. If not try vol down/pwr at the same time since you are now on GB bootloaders the keys are a bit different. Let me know what happens and good luck

maybe you should try to build a jig and use it to get into the download mode first. or you can buy it on ebay, just search for "micro usb jig".

I've tried every volume and power combination possible to no avail, I can't get into download mode. I've given in and am exchanging my phone. Thanks for the help anyway guys!

Updating OTA to ICS was successful but root was lost and settings app is frozen.

Long time lurker, first time poster. I have the Droid Razr Maxx and I used Voodoo OTA Rootkeeper to update like a good boy from GB to ICS. So my phone is just fine.
My technologically daft friend has the Droid 4 which I rooted for him when it was running GB. In my absence he decided to freeze some things without consulting me using App Quarantine. He froze settings (like the one in red) among other things. When the OTA update for ICS came, instead of calling me (at which point I would have talked him through updating with Voodoo to keep root) he went ahead and updated. The update somehow did not fail and now he has ICS running but all the frozen apps he froze with App Quarantine are still frozen. I can't unfreeze them because he lost root in the update and I can't root the phone because I can't get into settings, or get the phone out of USB mass storage when I connect to PC (the option is there in the notification bar but when you tap it nothing happens). I tried using RSD Lite 5.7 to flash the latest Fastboot file for the Droid 4, it goes through the process successfully but when the phone reboots nothing has changed.
I'm looking for advice on how to unfreeze the apps frozen with App Quarantine without root access. Or how to root the Droid 4 running OTA ICS without being able to get to the setting menu or change out of USB mass storage mode. Or worst case scenario how to get it back to stock and start from scratch.

Use rsdlite to fastboot back to stock. Do a search in this forum, there are lots of instructions
Sent from my XT894 running ICS

danifunker said:
Use rsdlite to fastboot back to stock. Do a search in this forum, there are lots of instructions
Sent from my XT894 running ICS
Click to expand...
Click to collapse
The OP did say: " I tried using RSD Lite 5.7 to flash the latest Fastboot file for the Droid 4, it goes through the process successfully but when the phone reboots nothing has changed. "

silver6054 said:
The OP did say: " I tried using RSD Lite 5.7 to flash the latest Fastboot file for the Droid 4, it goes through the process successfully but when the phone reboots nothing has changed. "
Click to expand...
Click to collapse
Oops, missed that part. If that's the case, then a factory reset will do the trick. You can perform a factory reset in recovery, power off the device, then press and hold both volume rockers while pressing the power button, choose recovery. When recovery loads up, press both volume rockers simultaneously, then choose erase our wipe data. Another way might be to press posting the menu button on the home screen and choose manage apps. From there go to all apps, and locate the frozen settings app. I think the frozen apps are at the bottom. Good luck!
Sent from my Nexus 7 using Tapatalk 2

danifunker said:
Oops, missed that part. If that's the case, then a factory reset will do the trick. You can perform a factory reset in recovery, power off the device, then press and hold both volume rockers while pressing the power button, choose recovery. When recovery loads up, press both volume rockers simultaneously, then choose erase our wipe data. Another way might be to press posting the menu button on the home screen and choose manage apps. From there go to all apps, and locate the frozen settings app. I think the frozen apps are at the bottom. Good luck!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I will see if I can create a shortcut on the homescreen first, but since settings itself is frozen I don't think it will load up no matter how I try to access it. I can't quite understand how he was able to use his phone without being able to get to settings, that is beyond me. I wish there was a method to root the phone without changing out of USB mass storage mode, that would effectively solve my (his) problem because then I could unfreeze everything. I know USB debugging is enabled. Anyway, he is coming over tonight after work and factory reset will most likely be the last (and only viable) resort.

Okay... I think I know where you're getting at... If you want to play with some other stuff, you can try doing adb shell then typing the following commands:
am start com.android.settings/.UsbSettings
this is the command to get to the settings menu, not sure of if will work if settings is disabled but it's worth a shot.
You can also try to get to the settings main menu by
am start com.android.settings
and the manage apps list is
am start com.android.settings/.Settings$ManageApplicationsActivity
all these am start commands need to be issued from an adb shell window.
Good luck!

danifunker said:
Okay... I think I know where you're getting at... If you want to play with some other stuff, you can try doing adb shell then typing the following commands:
am start com.android.settings/.UsbSettings
this is the command to get to the settings menu, not sure of if will work if settings is disabled but it's worth a shot.
You can also try to get to the settings main menu by
am start com.android.settings
and the manage apps list is
am start com.android.settings/.Settings$ManageApplicationsActivity
all these am start commands need to be issued from an adb shell window.
Good luck!
Click to expand...
Click to collapse
I couldn't get into settings no matter what I tried, had to do a factory reset. After that I rooted and installed Safestrap and Voodoo OTA Rootkeeper with the Droid 4 ICS Utility. And had a lesson with my friend on what never to freeze and to never update a rooted phone without consulting me or the internet first. All is well.

Im actually in the same boat... well, almost... i rooted GB used voodoo, temp unrooted so i can update to official 6.16.217... finally updated after 6 epic fails. i was stuck in a half root/ unroot phase where the su app was there and so was voodoo but root rights were gone and so was my root back up... i have tried using the droid 4 utility but all i get is errors. no matter what option i use, it doesnt do anything... usb debugging is on, set to camera, only one instance of adb is running, nothing works... i even tried z4root while in half root to see if maybe it would help... (which it didnt, figuered i would try) did a wipe and factory reset, nothing is still working. any ideas? does the utility only work on the ics leak and not the official ota?

[Q] Hopefully Soft Bricked [fixed]

Hello.
I was playing around a bit, and made a bad decision on disabling a sys app, with a root uninstaller app.
Now my phone starts up, but stays on the 'samsung' splash-screen.
My home doesn't seem to get loaded, so its stuck there.
I do, however, get notification sounds from text-messages and push-services.
My phone is rooted, but had no recovery installed, neither did I run busybox.
Not sure wether it runs 4.1.1 or 4.1.2, but I guess 4.1.1 because there's no intern recovery I can activate...
I tried flashing the recovery package with odin, still can't seem to get inside recovery... (Yes I can get into Download Mode)
I tried to reboot into the recovery via adb, but my phone - logically - doesn't respond to those.
Apparently, my USB Debug is not activated also... The phone connects, but I can't even do something with tools like GS3 Mini Toolkit.
Kies doesn't seem to connect either (even when the phone is on)... probably services that don't get started due to a battery saver app...
Long Story Short
Is there a rom & kernel, that can fully wipe my phone, via Odin, cause Download Mode seems to be my only option in recovering my phone.
Or any solutions that you could come up with.. because I already tested so much things,
and it's still stuck on the samsung 'lighting up' logo and a black screen.
The phone is for work & personal use... and I don't have the option to replace it atm.
I really need to get it working again... it was the only smartphone I ever had a decent battery life with (avg. 2.5days)
Thanks in advance!
- Fixed, I got into recovery mode, I forgot to stop pushing the powerbutton... so it rebooted. YAY :highfive:

Stuck in 'Phone is starting...' screen

Hi all.
So this is quite strange (i think).
I managed to root my s20 fe 4g using magisk with the help of some people from here and a guide.
I have played around with it, installed some stuff, uninstalled some apps (using titanium backup) and was all well.
When I went to restart the phone to give it a clean break, it now wont load up again. Just gets stuck on the 'Phone is starting...' screen. Now this isn't a huge problem, i thought I couldjust flashthe stock firmware again and root the same way and perhaps it will be well. The problem is it wont boot into download or recoery because it is stuck in a cycle of trying to start itself. I can force it to restart by holding the vol- and power button, but that is the only combination that will make it restart, it instantly restarts before i can change the keys held to try and get it into download mode.
Does anyone know what I can do to try and remedy this so it will start again?

UPDATE:
I think i stupidly must have deleted the one ui launcher by mistake... Now I am trying to get an APK to the phone, but ADBdoesn't recognise it at the 'phone is starting' screen. My phon is at dead stage, so i can get it to boot into download now, but it doesnt seem to want to go into recovery, and i think its stock recovery, so not sure if ADB will work?
Any other suggestions to get the launcher apk pushed and installed?

if you can get download mode flash the rom again, hopefully you still have it from rooting.
don't use titanium backup to uninstall system apps. even using it to freeze apps can be a problem if it's not gonna boot up.
get a copy of a safe debloat list and stick only those listed packages that others have found to safe to deactivate.