[Q] Bricked? HELP settings.db - Captivate General

i was trying to allow it to use 3rd party apps BUT, on root explorer, i deleted the original settings.db and pressed paste and a lil popup came up that was too quick to read and dissapeared, and nothing happenned. So i restarted my phone and after the loading of the purple/blue S the screen goes black but the capacitive buttons glow?i still have the settings.db backed up. Is there anyway to fix this?i just need to somehow get into the phone to put it back there. Thanks NOTE: i know this is the wrong thread but i dont have the priveledge to post there

Since the system won't boot all the way up, sideloading is not going to be an option for you. I recommend to flash back to stock firmware, as this usually fixes most brick issues.
See this thread...
http://forum.xda-developers.com/showthread.php?t=731989
Also, this video tutorial will help you...
http://www.youtube.com/watch?v=UDtxnH4lFuk

wasssabi5 said:
i was trying to allow it to use 3rd party apps BUT, on root explorer, i deleted the original settings.db and pressed paste and a lil popup came up that was too quick to read and dissapeared, and nothing happenned. So i restarted my phone and after the loading of the purple/blue S the screen goes black but the capacitive buttons glow?i still have the settings.db backed up. Is there anyway to fix this?i just need to somehow get into the phone to put it back there. Thanks NOTE: i know this is the wrong thread but i dont have the priveledge to post there
Click to expand...
Click to collapse
Do not worry! This happened to me when I tried this.
Go into recovery and do a Factory Reset.
You'll be good to go

You say to "do a factory reset" but I'm confused -- when I go to recovery (`adb reboot recovery`), I have four options, reboot, install packages, delete cache, and delete user data. Is "delete user data" the same as a factory reset? Is that going to solve the problem I created by hosing my settings.db?
I tried to do this: http://samsungcaptivate.wikia.com/wiki/How_To_Enable_Non-Market_apps_for_Captivate -- and though I thought I followed the whole process to a tee, I rebooted to find the same symptoms as the OP: regular boot logo, then a black screen with my buttons backlit. I can still `adb shell` and everything, just no UI on the phone itself...

Answering my own question: yes, "delete cache" then "delete user data" did a factory reset and fixed my problem. This time, I used the [http://forum.xda-developers.com/showthread.php?t=803682 SuperOneClick] de-crippler; worked in seconds. Thanks!

Related

[Q] [Help] Stuck in boot on Google

Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?

[Q] Boot Loop after Cyanogen Mod install. Help me please.

Hey folks,
I could desperately use some help here...
I rooted my Droid Incredible using UnRevoked, which was painless and easy. After that, I downloaded Rom Manager, then backed up my current Rom.
Then I downloaded Titanium, and backed up all apps and system data.
Using Rom Manager, I downloaded Cyanogen mod 7.0.2, checked google apps, DID NOT check wipe data or cache, and then clicked OK to let it work it's magic.
The system turned on and off a bit, and then the CyanogenMod boot screen came on, ran the arrow around the droidbot a few times, then the droidbot dissapeared, came back across the screen, and the arrow resumed circling. This happened about 20 times, before I gave up and powered off by removing the battery.
Then I loaded Hboot, and attempted to access items in Clockworkmod, but even though I could click on an item, it would show the top hat with no change in status for many minutes. I eventually tried almost all options.
My Hboot screen shows:
HBOOT - 0.92.0000
Radio- 2.15.00.07.28
I am unable to click on Fastboot, Recovery leads me to busted Clockwork menu, Clear Storage causes restart into looped Cyanogen Mod screen, haven't tried Simlock, and Factory Reset also goes to broken Clockwork Menu.
I downloaded the RUU file from Doug, changed the title as directed, and put it on the SD Card. It gave me the option to Update, which when restarted afterwards continued to loop in Cyanogen Mod screen. Or, if I went to Clockwork Mod screen, the font was now Green instead of Orange. Also, when I click an item in the Clockwork Mod menu, it simply goes to a black screen until I hit the power button to bring me back to the menu,
I'd love to just get the phone to a factory state, so I can possibly use it for it's purpose of calling and sexting (just kidding.)
Please help, any advice would be greatly appreciated.
Oftentimes, ClockworkMod Recovery has an error at the bottom stating:
E:Invalid command argument
I have to go to bed for a bit, but will be back on around 10:30am EST. Thanks for any and all help!
In ClockworkMod, I can now access and start an operation by selecting it with the volume buttons, and then hitting the joystick button. This wasn't working previously. So, I've tried some of the obvious options such as Factory Reset but it's not doing anything. I've tried multiple solutions, which means I've probably messed it up on many levels. Is there any way I can just start from scratch or get a system restore done?
After utilizing that update from Doug, and then going into Clockwork Mod, clearing all caches and system data, and then trying to restore to a previous flash for the 7th time... I think it might be working!
Thanks to anyone who looked at this.

[URGENT] Every reboot results in a factory reset

So today my droid started messing up, home and recents button didnt work. Google play store and whatnot couldnt access data, the signal status bar at the top was just grey.
So i factory reset it. During the reset it just sat there on the little screen with the spinning hexball thing for like an hour so i shut the phone off. Now every time the phone boots it just tries to wipe it again unless i go into the boot menu and hit normal boot.
Running stock rom and whatnot, but im rooted.
I know that theres a flag somewhere that it reads on boot saying to wipe it, but dang if i know what to change.
Thanks in advance
Well i unrooted my phone and tried to let it redo the factory reset again, and it still just wont do anything.
jombo2323 said:
home and recents button didnt work
Click to expand...
Click to collapse
When this happens to me, it's because of a bad flash and a factory reset won't fix it. I would suggest reflashing stock...
coolloser said:
When this happens to me, it's because of a bad flash and a factory reset won't fix it. I would suggest reflashing stock...
Click to expand...
Click to collapse
I dont have a custom recovery or an unlocked bootloader.
I managed to get the problem sorted out through some unrooting and some non stock system file deletion. Installed safestrap and got blurry hd running on it now.
Thanks.

Issues flashing stock with odin J700t

I have a question, dont really know where to ask. I have the tmobile j700t, and I've tried restoring with odin, (with the j700t firmware of course) and im not sure if its doing everything. Everything seems to go fine in odin, flashes boot, modem, system etc. reboots, rebuilds cache, then it just goes to my original lock screen with my custom wallpaper and all my apps still on. I can do a factory reset after, but it doesnt seem to do anything but clear the cache. Am I missing something? I enables OEM UNLOCK and USB debugging before hand.
The inability to make write changes sounds like a bad NAND issue, you could try flashing with a .pit file but the phones internal memory could be physically damaged.
Andromendous said:
I have a question, dont really know where to ask. I have the tmobile j700t, and I've tried restoring with odin, (with the j700t firmware of course) and im not sure if its doing everything. Everything seems to go fine in odin, flashes boot, modem, system etc. reboots, rebuilds cache, then it just goes to my original lock screen with my custom wallpaper and all my apps still on. I can do a factory reset after, but it doesnt seem to do anything but clear the cache. Am I missing something? I enables OEM UNLOCK and USB debugging before hand.
Click to expand...
Click to collapse
Try clicking the Nand erase all box and unclicking auto reboot. Flash the factory ROM and when it completes hold volume down, home and power buttons until the screen goes black. This is important, as soon as the download screen is gone you need to hold the recovery buttons (volume up, home and power) so the phone can erase all system data and update itself the way it's designed to after flashing a factory update. If the device reboots before you enter recovery you have to start over. Hit thanks if this helps bro.
Metabolic12 said:
Try clicking the Nand erase all box and unclicking auto reboot. Flash the factory ROM and when it completes hold volume down, home and power buttons until the screen goes black. This is important, as soon as the download screen is gone you need to hold the recovery buttons (volume up, home and power) so the phone can erase all system data and update itself the way it's designed to after flashing a factory update. If the device reboots before you enter recovery you have to start over. Hit thanks if this helps bro.
Click to expand...
Click to collapse
well that seems to have fixed it, weird though, when I rebooted into recovery like you said, it did an update, there was a progress bar, then it rebooted, and rebooted AGAIN, did an "update" and then rebooted. Weird, I usually see it say "updating" but then it will stop and you can bring up the recovery menu. Never seen a progress bar and then it just reboot twice. Well anyway it seems to have worked so thank you!
Andromendous said:
well that seems to have fixed it, weird though, when I rebooted into recovery like you said, it did an update, there was a progress bar, then it rebooted, and rebooted AGAIN, did an "update" and then rebooted. Weird, I usually see it say "updating" but then it will stop and you can bring up the recovery menu. Never seen a progress bar and then it just reboot twice. Well anyway it seems to have worked so thank you!
Click to expand...
Click to collapse
Whenever you flash back to stock or update a stock firmware through official means, it automatically boots into recovery and erases the system you have in place, very similar to TWRP. If you try to flash a stock firmware without erasing everything you will always run into some kind of incompatible memory error. The screen you're thinking of is just the stock recovery checking your system and OTA's for an official upgrade. Glad I could help man.

bricked (?) with "phone is starting"?

this morning, my gps wasn’t working and i did a reboot, since then my phone won’t start anymore. originally: bootloader unlocked, twrp installed, magisk as well.
after typing in the security pin, it was stuck. i assumed there was some problem with that, so i went into twrp and deleted those lock settings files, reboot, now i’m at "phone is starting" after each reboot now and i can access settings and basic stuff, but no home or anything, and tapping on system update tells me that the app is not responding ("settings keeps stopping"). booting into twrp asks for a pin which does NOT work anymore (neither my original one, nor 0000 or default_password).
i used magisk uninstaller (sideloaded), and reflashed what i assumed was an OTA-zip from the oneplus website, so i’ve got stock recovery installed now (bootloader still open), but otherwise not much changed - after booting i can basically only access settings (from the quick settings bar), nothing else works.
i ASSUME it has got something to do with not being able to decrypt data anymore. i also assumed i can just reflash the 2gb-zip from oneplus and that would include a fresh system/boot img and deleting those lock files from twrp would remove decryption, but i guess i was wrong.
other that formatting data now .. any recommandations/suggestions? any help would be greatly appreciated. :/
could be stock launcher is frozen or disabled?
it did this to me, even if I had another launcher.
virtyx said:
could be stock launcher is frozen or disabled?
Click to expand...
Click to collapse
thanks for your guess - but, no, not disabled, i can see it in the list of apps. the only app "disabled" was the oneplus gallery, switched that back on, no effect ..
frank93 said:
thanks for your guess - but, no, not disabled, i can see it in the list of apps. the only app "disabled" was the oneplus gallery, switched that back on, no effect ..
Click to expand...
Click to collapse
wipe cache in recovery
virtyx said:
wipe cache in recovery
Click to expand...
Click to collapse
tried that, didn’t work. and even after a "factory reset", starting from the "hello!"-page from scratch, everything stopped on the next page ("just a sec ..") - so i guess there was something seriously wrong with my data partition. not sure why though.
after formatting data (and crying during those few seconds) it "worked" again, now, and fortunately i had some kind of app backup at least, but ..
yeahwell.
frank93 said:
tried that, didn’t work. and even after a "factory reset", starting from the "hello!"-page from scratch, everything stopped on the next page ("just a sec ..") - so i guess there was something seriously wrong with my data partition. not sure why though.
after formatting data (and crying during those few seconds) it "worked" again, now, and fortunately i had some kind of app backup at least, but ..
yeahwell.
Click to expand...
Click to collapse
very strange
maybe the restricted. XML file was stuck
no point trying since you formatted
four hours later, fresh setup - it’s starting to happen again, sudden "hangs" and "phone is starting .." out of nowhere, then "system ui is not responding", force reboot, .. working right now, but there’s something really fishy and i’m starting to assume it’s a hardware thing.
I'm having the same issue after rebooting to fix gps/mobile data issues. Any other solutions?

Categories

Resources