Database Info

Hard reset not working (among other things) on samsung captivate - please help!

I got carried away there, so I'll summarize:
Yesterday most of the apps on my phone started crashing. I tried clearing from recovery mode, but nothing went away. Today, I've tried to reflash to stock to get the phone completely clean, but also no good. Even using master clear and reflashing the rom doesn't clear the phone out. Everyone says it works, but the applications are all still there after the reboot, except now they all crash, including launcherpro, leaving me no way to do anything at all on the phone
I'm desperate because my phone is currently unusable. Please help!

Update: I found another method for doing it, listed below, which worked. Still no data though
Anyone have any ideas what might have happened/how I can fix?
2.- :::: CAPTIVATE HARD RESET :::
captivate must be powered OFF to perform this reset, If the device is on, turn it off
- Press and hold both volume buttons + -
- While holding down volume buttons + -, press the power button while maintaining the volume buttons pressed in for around 5 seconds
- Release volume buttons but, keep the power button pressed
- you'll see at&t start up animation release power button
- menu appears
- follow instructions using volume buttons
delete cache data, press power
delete all user data, press power
reboot system, press power
*** (optional) turn off the phone, put my sim card back, turn the phone on

Holy crap... I don't know what's wrong now... I did "Delete user data" and "delete cache" from the boot menu, and STILL everything is there!
What is wrong with my phone?

reflashing to stock... hopefully this does the trick...

ok I went through the process of flashing to stock, and it said it worked, but the old applications are still there!
Now, when I reboot, I get a ton of force close messages; presumably everything that normally would be launching on startup.
how do I actually clear this device and get it back to stock?!
for reference, here's the page I used:
http://forum.xda-developers.com/showthread.php?t=731989

I having the same exact problem where I tried to flash back and I have all these process error message thats dont let me do anything really need some help on this one been at it for hours

seps1816 said:
I having the same exact problem where I tried to flash back and I have all these process error message thats dont let me do anything really need some help on this one been at it for hours
Click to expand...
Click to collapse
Hey there,
I'm afraid this won't help much, but in the end I had to call the AT&T warranty department and get a replacement phone. There's a 1 year on the phone, and while I had to jump through some hoops, they did replace it. If you're within 30 days then you're definitely in luck, as you can take it back to the store you bought it at
Good luck!

Force Close Loop Help!

Hi Folks. It seems that it only took me 4 days to get a brand new G-Tablet bricked. I installed dxTop Pro and it crashed my unit. When it came back up I am in a Force Close loop for dxTop Pro since this is the shell I was using.
I can't seem to get the unit into safe mode. Is there a way to do this on a G-Tablet? I am running the stock TapnTap with just the Enhancements Pack.
Any Help would be appreciated.
Also, this unit seems to be a hackers dream and a users nightmare. I am a big techie and I don't mind hacking around with this thing to get it setup properly. However, I would like to get it to a point where it runs reliably. I am starting to think that this is not going to be possible. Has anyone had a G-Tablet running where it is not problematic? If this thing is just going to be a hackers testbed then I am going to return it before it's too late.

Try holding down the + volume button and then hold down the power button. Keep both pressed in until you see "recovery key press detected" (or something like that). That will boot you into recovery mode. I use clockwork recovery, so I don't remember what the stock recovery looks like. There might be a cache wipe there. If so, try that first. There should be a factory reset there. If you factory reset, you get a tablet like it was fresh out of the box (you'll lose your settings and data from the last 4 days).
To answer your other question...this is not a perfect out-of-the box, everything-works tablet like iPad is. However, there are ROMs and tweaks here that give you a pretty awesome user experience. Some of them are exactly what you said--a playground for techies. My opinion is TNTLite is the best way to go for the user who isn't as excited about all the techno gack. Read the first page of this post:
http://forum.xda-developers.com/showthread.php?t=842004
It takes some reading to get it done right. And there are weird things that happen from time to time. It's impossible to ruin the tablet, but some of the fixes are deeper-tech and it can get frustrating. Mine is running great, TNTLite is stable, the hardware is very good, very fast. This tablet is much less expensive than the other ones that will be coming out this year. But the reality is that many of those will have a much better user interface and a better out-of-the-box experience.

The best thing to do is install Clockwork recovery. The stock recovery is worthless. This tab is virtually unbrickable. Install clockwork from this link and dont use Rom Manager.
http://forum.xda-developers.com/showthread.php?t=865245
Clear data/cache after installing clockwork

Force close loop
Ok, I cannot get back into recovery mode. When power button + volume up button pressed simultaneously the viewsonic then gtablet pics will come up but then screen goes blank then nothing. I have to shut it off to try again.
If I let it run, everything boots up then finally into vtl but I can never access the main menu because of all the force close windows and then finally the vtl force close window keeps popping up to no end.
What can I do???? Please help, I have researched site but to no avail.
Jerry

Unsuccessful Root of HTC One M7 Need Advice

I have a Tmobile HTC One M7 that I paid $300 for. It was awesome! However, I wanted to root it. So I successfully unlocked the bootloader, installed TWRP and then proceeded to attempt to root. Something went wrong and now this thing is useless! I cannot tell you where it went wrong because when the first sign of trouble appeared I started doing all kinds of **** to try and fix it, none of which worked and I have lost track of what I did in the process of trying to root and then subsequently trying to fix. I know there were some wipe cache, wipe dalvik cache, install zip from SD, I may have even tried to flash a custom ROM without the thing being rooted. I have been reading for days, trying this, trying that to no avail. The phone is brand new, without a scratch. It will power up like normal, but when it gets to the lock screen where you swipe the little lock in the bottom tray to use the phone it will not respond at all! It recognizes the network because it is displayed in the notifications bar up top, it can see the signal strength, it knows what time it is, it knows what the date is, but it will not get past the damn lock screen. ADB sideload works. I was able to push a zip and flashed it, even said android is upgrading when I rebooted, but it did not solve my problem. It will not power off, but when I hold the power button down, to turn it off the back arrow < and home symbol flash and after about 10 seconds a dialog box pops up that says to restart your phone continue to press and hold the power button and starts a countdown. Once the countdown gets to zero it restarts. If I hold the volume down button while doing this it will go into the boatloader and I can get into recovery. Apparently there is no backup to restore because when I try a restore I get the same exact same thing. I thought I had done one, I must have erased it somehow. I have been trying to resolve this for weeks now and am at my wits end. Any suggestions please !?!? Will anyone on this forum take it if I ship to them and fix for a fee? Otherwise this things going in the trash.

[SOLUTION] How To Fix "CM Lockscreen Has Stopped Working" Error in OnePlus One 38R

[SOLUTION] How To Fix "CM Lockscreen Has Stopped Working" Error in OnePlus One 38R
DISCLAIMER: I do not guarantee that this method will work for you, but it doesn't require ROOT or a custom recovery, etc. So, it's safe.
So, three days after OTA updating my OPO to XNPH38R, I randomly got the "unfortunately, CM Lockscreen has stopped working" error, and my phone became virtually unusable. I was devastated! I didn't want to wipe my phone. So, I decided to just got into Recovery and wipe the cache. But my custom recovery was freezing, so I decided to boot up my computer and try to re-flash recovery... And while I was waiting for my computer, I stumbled upon this work-around. I hope it helps someone.
WORK-AROUND METHOD:
Step 1.) Reboot your phone. (You'll have to hard reset it by holding the power button down for 5+ seconds.)
Step 2.) After the phone restarts and you're faced with the persistent error of death again, just press the power button once to turn off the screen. Then, turn the screen back on.
Step 3.) When you turn the screen back on in Step 2, the screen should be totally black with the capacitive buttons still lit. If this doesn't happen, try repeating Step 2 until it does.
Step 4.) Just leave the phone on with a blank screen and lit capacitive buttons for 20+ seconds. This seems to be an important step.
Step 5. Turn your phone screen off and back on again. For me, this fixed the persistent error. Yay! Hopefully it works for you. However, for me, the error came back again in only 5 minutes, and I had to repeat the entire procedure. Which is why we need Step 6.
Step 6.) Disable the lockscreen. This can be done by going to System Settings > Lockscreen > Screen Security > Screen Lock, and then choose "none" to disable the lockscreen entirely. This has kept the persistent error from recurring for me for 12+ hours.
And, that's it! That's all. You get to keep your data and information. And you get to keep the latest OnePlus One software version... However, unfortunately, you lose all lockscreen Security. But, you could maybe try installing a third-party lockscreen like "GO LOCKER" until OnePlus recognizes this problem and fixes it in the next update.
Good luck everyone! Lemme know if this works for anyone else besides me.

Marvelite said:
DISCLAIMER: I do not guarantee that this method will work for you, but it doesn't require ROOT or a custom recovery, etc. So, it's safe.
So, three days after OTA updating my OPO to XNPH38R, I randomly got the "unfortunately, CM Lockscreen has stopped working" error, and my phone became virtually unusable. I was devastated! I didn't want to wipe my phone. So, I decided to just got into Recovery and wipe the cache. But my custom recovery was freezing, so I decided to boot up my computer and try to re-flash recovery... And while I was waiting for my computer, I stumbled upon this work-around. I hope it helps someone.
WORK-AROUND METHOD:
Step 1.) Reboot your phone. (You'll have to hard reset it by holding the power button down for 5+ seconds.)
Step 2.) After the phone restarts and you're faced with the persistent error of death again, just press the power button once to turn off the screen. Then, turn the screen back on.
Step 3.) When you turn the screen back on in Step 2, the screen should be totally black with the capacitive buttons still lit. If this doesn't happen, try repeating Step 2 until it does.
Step 4.) Just leave the phone on with a blank screen and lit capacitive buttons for 20+ seconds. This seems to be an important step.
Step 5. Turn your phone screen off and back on again. For me, this fixed the persistent error. Yay! Hopefully it works for you. However, for me, the error came back again in only 5 minutes, and I had to repeat the entire procedure. Which is why we need Step 6.
Step 6.) Disable the lockscreen. This can be done by going to System Settings > Lockscreen > Screen Security > Screen Lock, and then choose "none" to disable the lockscreen entirely. This has kept the persistent error from recurring for me for 12+ hours.
And, that's it! That's all. You get to keep your data and information. And you get to keep the latest OnePlus One software version... However, unfortunately, you lose all lockscreen Security. But, you could maybe try installing a third-party lockscreen like "GO LOCKER" until OnePlus recognizes this problem and fixes it in the next update.
Good luck everyone! Lemme know if this works for anyone else besides me.
Click to expand...
Click to collapse
This is not working for me as i cant get my phone to the stage where the screen is black with only the buttons lighting up

Alternative solution
I too faced the same problem with the lockscreen after changing my wallpaper.
However the method mentioned above did not work for me.
I tried this instead.
1. Restart your phone by holding down the power button for a few seconds.
2. Turn off the screen.
3. Use the play music gesture: swipe down 2 fingers to start the music player. (tried the camera gesture but did not work).
The lockscreen problem disappeared since then. I have also turned off the lockscreen in the settings in fear of it reoccurring.
Hope this helps any of you suffering from the same problem.
Cheers!

I found another way to get your phone unlocked
So the solution that was provided by Marvelite did not work for me. I tried many many MANY times, but to no avail.
After looking around the interweb, I found some other instructions to root my phone (FYI I had no experience in rooting) and I was able to fix it without flashing or re installing anything.
So... what did I do. All I did was unlock my phone. I got my phone and remember saying it was unlocked, as you could use any carrier. That is not what I mean by unlock. What I mean by unlock is you cannot flash it or erase it. See the command line window below saying the phone is not unlocked and that is why I cannot flash it. I thought I had to flash it or erase it to get everything working. Just unlocking it fixed the CM Lockscreen Has Stopped Working error.
So what will you need to install on your computer and do to your phone.
1) Download adb-setup- 1.3.exe (if you type "adb-setup- 1.3.exe" into google, you will find a download) and install ADB system wide on your computer.
2) Put your phone in Fastboot mode and plug it into your computer. To do this, have your phone completely off and then hold the volume up and power button. You will see the screen of your one plus one in fastboot mode.
3) open up a command line window (as in my attached picture) and type fastboot oem unlock
THIS WILL RESET YOUR PHONE! After I typed in fastboot oem unlock, my phone reset itself and it was though I had hit the factory reset.
You can see from the command line window attachment, that I tried to flash my phone based on this workflow (http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061), but I did not even need to do this, because my phone was not unlocked. Then when I unlocked my phone, the problem was fixed.
I hope this works for those that have this horrible bug.

[Completed] [Q] A Tough Bootloop Problem...

Good day to all. I'm here resorted to ask about my problem here because I really can't handle it. I been googling for days. I'm ran out of resources from both google and tablet. So, I hope you can help me here. Note I'm going to write this in FULL detail here, so expect this to be a extremely long post. (I been warning you) So here goes....
Anyone uses the brand Ramos?(kind of unpopular brand) I use Ramos W21, it's been using it around 1 year and a half, and it endured a lot of problems, but fixed by researching on online forums and apply various methods there. Now, I think it's finally gave up...
One time, when I opened it and play my usual apps and browsing, it caused the errors " unfortunately
google.process.gapps has stopped", unfortunately browser has stoped",and "unforturnately google play has stopped". Then, I tried to clear data the similar apps in settings as usual, and even disabling them. Then more errors exploded, and "unfortunately launcher has stopped" appears. The menu screen(where the usual wallpaper and shortcut apps are located) turns black, while my running apps are still there running. When I pressed the back key to exit the app, now only tons of errors from the launcher appears endlessly(while the screen is black.
The time I finally turned it off by hard reset it made its way to the main problem: the bootloop.
Okay, here's where the thing gets real. It opens with the usual ramos logo, but the next one is a silver flashing android logo instead of enlarged ramos logo with spinning fire from the letter o(which is NOT my usual boot up screen) When I turned it off, it reopens again up to flashing silver android logo and the cycle repeats, even with pin reset until battery dies out. No recovery mode, so I can't use it to fix this. USB connections can't be recognized when inserted to PC. And no, the tablet is not rooted, and I don't customized anything, no mods, and no fancy roms. Just using a stock rom.
So now what? All I have here is just a sd card slot, which I think there's hope in there. Right now it has two options, deal with it and fix with all of might, or repair it in the nearest repair shop(something that is pretty risky, a lot of fakes and robbers here)
Well, this is the first time I post here, so sorry for anything that goes wrong. Thanks in advance.

Hi, thank you for using XDA Assist. It sounds like a rouge app has replaced your boot animation. Rather than try to chase that down and try to fix it I'd flash the stock firmware and start all over. Unfortunately there is very little about your device on XDA. So you'll probably have to google that.

Solved!!!
Update: I FINALLY FIXED IT!!! IT WAS A MIRACLE!!! O.O
After I keep on wrecking it's power buttons and volume buttons, I discovered something decisive!
This tablet actually HAS RECOVERY MODE! Again, it has a recovery mode! However, the way how to input it is very unique compared to most devices, including other devices from the same brand!
Now having the power of recovery state, I first selected "wipe data cache". The old large Ramos logo with spinning fire appeared again! But it's still bootlooping. So I went back on recovery state, selected "factory reset" and boom, IT BOOTS LIKE BRAND NEW!!! (sacrificing my old data though)
Okay, I don't want this recovery mode powers to be kept only by me. So I'm going to share it to all Ramos users,especially the model W21, like right now!
1. To do this, you need power button and volume up button.
2. While bootlooping, hold the power button and volume button at the same time and it will turn it off(Then expect it to turn on back up again automatically)
3. When it opens up again to the small Ramos logo(no fire animation), now RELEASE the POWER BUTTON ONLY, and keep holding the volume up button. Note, this is important! If you do anymore than this, it will either black out, go bootlooping once again, or ultimately, nothing.
4. Keep holding the volume up button, then the ramos logo will disappear, and now it will enter to our holy grail, RECOVERY MODE! Congratz!
Now when you finally have a normal working Ramos tablet again, you may go there again by turning it off by "Power Off" (assuming that your tablet is open) then holding the power and volume up(then follow above!)
I hope this will help a ton for Ramos users! :laugh:

I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem

jd1639 said:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
Click to expand...
Click to collapse
Well thank you then for the link. Gotta go there!

Thread closed.