I installed overcome 2.3.3 and due to access policies for my outlook mail I am required to use a screen lock password. but after a some days of usage the screen locks me out and wont accept my password.
I flashed the tab and it worked for a while and the same thing happened. Went through the same flashing period and after some days I am locked out again.
Just wondering if it is a bug with the overcome kernel and if there is a way of accessing the tab without flashing
You can use ADB to pull the settings, delete the password, and push it back.
I'm not going to tell you how to use ADB, because I just recently started using it again and frankly, no one told me crap, I just did a lot of research.
The command is :
adb pull /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
After you pull it, open it in sqlight program and I believe remove lockscreen.password_xxx I'm not sure what they are named, as I haven't had to do this in some time... I'm also pretty sure there are two of them that require removal.
After you delete them, push that file back to the same spot and poof, no more password.
..
That's all I got
thanks, though I have used clockwork recovery to do a restore. I would try the adb method if it happens again.
After doing some more reading, it seems a lot of people have this problem. Judging from what I can tell, outlook is the culprit... Somehow.
Sent from my "better than an iPad" tab... Running Overcome GINGERBREAD!!!
Related
I apologize first off for another boot problem thread.
First, I have never messed with my rom. I never flashed it or anything. The most I have done is load KaiserTweak and TomTom. Basic stuff.
I went to turn on my phone this morning and it stayed on the AT&T boot screen. It just freezes. I kept trying to soft reset the phone and at one point it loaded with like the default settings but nothing worked. The start menu only had the Today listed. The phone wouldn't work either. From then on, it always sticks on the AT&T boot screen.
I tried removing the battery and the sim card for a few hours and that didn't help. I tried turning on without the sim.
I am hoping to fix without a hard reset. I don't want to lose all of my contacts and all the data saved on the phone. Is there any way to save this stuff?
That's why you should always have scheduled backups at least once a week. I don't see this being fixed without a hard reset. You did everything that i would have personally suggested (taking out battery and everything for a few minutes). If all fails, you can always go into bootloader mode and reflash the ROM.
Is there no safe mode way to access the device? How about any work around so the computer can access the flash data without the device being in active sync mode?
Highly doubt it and i've never read anything about accessing the device when it's not on. It seems so sporadic and from the looks of it, only a reflash will get you going again.
This reminds me of back when I was trying to flash my Kaiser to 6.1... had exactly the same issues. Even worse actually since the problem started when I flashed a ROM wrongly, also without having an original to fall back to. Cue a night of trying to flash over my mistakes!!
I recall having some success with some specific mtty commands... argh, I'd bookmarked hundreds of threads on it back then but have since lost them all. All I know is there are a few commands you can type which may just get the phone booting again. Bit useless of me but it's a start!!
Ah, check these threads:
http://forum.xda-developers.com/showthread.php?t=371154 This one will erase all data
And post #2 demonstrates use of using the mtty boot command here:
http://forum.xda-developers.com/showpost.php?p=1765045&postcount=2
Those kinds of commands I managed to get my phone working with.
I figured out how to boot to the tri-color boot screen. The computer regonizes it and the boot command in mtty just does the same thing as turning it on.
Since my computer is now linked to the phone, isn't there some way to access files? Any commands in mtty that will work? Any other program out there that might help access the memory?
No one has any ideas about how to access the memory?
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
vigilante_xix said:
Did you manage to fix this in the end?
Got the very same problem with mine which hasn't been flashed in any way.
Click to expand...
Click to collapse
Never was able to figure it out. I had to reload from scratch.
Good luck with your issue. Hopefully some of the suggestions around here and elsewhere will get you back up and running.
First off I would like to say that this is one of the best forums I have ever seen as the amount of support and helpful users and creativity put into these phones are staggering. I was going to go to Windows mobile for my next phone but I now doub it with this site or at least maybe I will dual boot.
So I am sure I am asking questions that have already been answered but my problems with the phone (USA G1) are many and the answers to some of the problems are so fragmented that I had at one point 14 tabs open for reference to solve just a few issues. I am 70% noob with the G1. I have had the phone for a year with no major issues just the annoying Force Close that seemed unecessary for the commonality of the app that had problems. Texts were annoying because I could not tell if they had been sent the previous day or recently as service at my home is come and go and my older Verizon phone had envelope information and even said if the person had read it or not so no annoying duplication. However, otherwise it was stable and would last about a day and a half with the double size battery.
Recently, however I had rebooted from the power button prompt and it got stuck (I can't remember on what screen) and figured installing a different ROM and other files would fix the problem. By the way, I had bought the phone rooted and I believe it was using JF 1.42 and a Cyagen mod (forgive my spelling). So I followed step by step from this forum the wiki on the lastest stable Cy ROM. I followed the instructions to the T.
Being new to the software, it was a slow process with a lot of repeating of steps discovering little details that were not mentioned like naming something update instead of update.zip like instructed or adding the .img as an extension. So I had nearly made it and then I came to the DangerSPL and other files to be loaded on the phone in order via fastboot. Despite, several attempts I could not get the skateboarding droids or the rainbow screen to come up so I finally decided to just continue as I had been using Amon-RAs 1.7 update zip feature to follow the instrucions and install the software in order. All was well until I got to flashing the actual ROM which said something about how it said the E: [insert file name here] was not correct so it aborted everytime but it did show some progress on the yellow bar.
Next came the issue of the G1 screen hanging up after the above problem and for some reason I could get to the 1.7 screen but only by holding the button required to access Amon RA longer than usual other wise it would say the build of Amon RA at th ebottom with no commands and the reboot itself or hold it longer and finally get to the Amon RA but it would not load my recovery files as I had made many along the way.
I nearly gave up but then came across this solution which worked by using method 1 at well I am not allowed to pu the websit in here but I am not allowed by the mods. but it is the 4th one down if you google "how to fix a soft brick g1" and the link is titled Unbrick - android-roms - How To: Recover your G1 from a bring ...However, it did get stuck at the rainbow screen as it finally let me do the fastboot and I saw the Androids skateboardig but it hung at the rainbow screen. It was here I noticed that my 32A phone was now a 32B. I took the battery out and powered it up and lo and behold it was asking me to put in my google information and I finally made it to the home screen.
I thought "Yes!". Now, I can try again since it will fastboot now which was what was recommended at the final steps but I was mistaken. I could not searc the market for common apps like wave secure and it frequently said it does not exist. I saw that my terminal app was gone and when I was finally able to download it from the market and my superuser app was gone and the termina would not respond as before to the input of SU.
Then, I noticed my phone's screen would randomly come on and only sometimes go off. When I pressed menu it was as if it the call button was stuck and it would either repeatedly bring up voice dial or call someone. The buton does not appear to be stuck otherwise. When it would briefly stop, acting like the call button was in turbo mode it would give me the option to mount the SD card as I had lost my micro sd card reader but never give me a chance to mount it before the call button interrupted with google dial or calling some number.
I do not believe this to be a hardware issue because as far as I remember the call button worked normally during the steps as it was requently used. So my questions, at the moment, are these:
1. How do I tell if the call button problem is a hardware or software issue?
2. Once I find my card reader and will I be able to use the factory bootloader to go through the updates.
3. Obviously I have derooted my phone (or maybe I can delete the diag from sd card and it will operate as it is derooted), will I be able to reroot my phone by using my backups of nandroid basically leaving me at whatever step I was on to the road of recovery?
4. How do I use my nandroid backup to recover especially if I am stuck with the factory bootloader?
5. I copied my SD card before I did the wipe originally so will I be able to find a .xml from handcent with my texts? (I text myself my mileage for work as with my hours, it is easier than using an app plus it saves space for other apps)? Should I load that backup nandroid first and start over?
6. Is there a quicker way to root like...a program?
7. What is your advice for the future other tha obviously backing up my texts more?
8. When did wave secure start costing money? I think I might have backed up everything a few days before the crash but I have no access to it now.
9. What other key combinations can I later use for the fast boot?
10. When formating the card to fat32 what allocation do you use and do you use quick format?
11. What is lost dir. and why is it empty?
12. In Amon RA 1.7 there are several caches which I cleard all of them when asked to clear the the cache in the wiki directions? Should I clear all of them and what are the seperate caches, espicially the davik one?
I am sure I am missing some question but I will post more as I try to follow your directions or attempt other methods. I apologize for the long, long story but I wanted make sure I did not leave out any detail so this can be resolved ASAP because I am sure I am receiving texts and calls and people are probably thinking I am ignoring them (no one leaves voicemails anymore so how can I know if they called or texted during the phone's sickness). I also apologize if I have broken any forum rules or posted in the wrong section or violated some. Thanks guys in advance. I miss the fat little thing so much.
Oh My god! Sorry but that's too long for me to read, my attention span isn't all that great =p
I will try to help with your questions but I didn't read the whole intro so my answers might be a little redundant.
1.Run "adb logcat" from a cmd prompt on your computer and see if pushing the button registers on the computer
2. um ok??? not a question
3. you will have to re-root but your backups will still be usable after you gain back root
4. boot to recovery (home+power), scroll down to backup and restore, select restore, and select the file
5. I'm not familiar with handcaent so can't offer help there.
6. It's not hard. Downgrade with DREAIMG.nbh to RC29, use update.zip to upgrade to 1.5, install one click root, use it, flash a recovery, and flash a rom.
7. You should write shorter paragraphs =p
8. Again, not familiar with it.
9. HOME + POWER, and BACK + POWER
10. No clue....
11. It's a folder automatically created when you don't unmount your phone before disconectiong the usb. It's useless and you can delete it.
12. When installing a new rom, just wipe everything. It saves you trouble later on.
Hope I helped...
Thanks I will give it a try later today and probably come back with more questions and longer paragraphs
Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.
If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p
Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.
Yikes, can't help you with the obvious then (just pushing framework-res.apk again).
Yeah, I was really hoping to somehow get in there with adb
As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.
hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html
Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.
So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!
He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App
Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.
to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time
Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.
Hey Guys,
I've updated to Cognition and it worked fine; i had to do a hard reset on the phone becuase my time stamp was wrong so i thought it would of fixed it. Now i lost my Andorid Market and Rom Manager :S
Does anybody know how i can get this back.
Thanks.
This happened to me when I tried switching my wife's and my SIM cards so she could use my Captivate while I worked on hers. Both phones lost the Android Market app which of course makes it difficult to do anything else.
I ended up flashing mine back to stock which solved the issue as expected.
I have no idea why Market disappeared. I wouldn't think it had anything to do with the SIM cards.
How would you flash to stock? I lost Rom Manager as well when i did factory defaults
Use the Odin one click at http://forum.xda-developers.com/showthread.php?t=731989
That will put your phone back to stock. Read that thread to get a good idea of what's going on, but here's the simple part that you will end up doing.
To use it:
1. Make sure phone is not plugged into computer.
2. Open the Odin one click program.
3. Make sure phone is turned off.
4. Hold the volume down and volume up keys.
5. While the volume keys are being held, plug in your USB cord.
That should bring you to the Download screen with the robot digging and stuff. You can then click the start button in the Odin program.
If after step 5 you don't get into the Download screen then you need to do some more research in that thread, or read the steps and try again to follow them exactly as stated.
edit: I see you're on Rogers. I don't know, but I've seen separate threads pop up for people using Rogers so possibly things are different for you so make sure you research!
Thanks for your help; once i got to recovery mode i spent some time going through the menu and found out i could load my OS from there because i left the zip file on it.
I got a little nervous since i thought i screwed up a 2 day old phone lol....but all is well. Now i need to find another Rom to put on it
I remember reading about an app that let you read your market ID # and restore the ID# after you flash. Doesn't Cog give everyone the same market ID# when you flash it?
baseballfanz said:
I remember reading about an app that let you read your market ID # and restore the ID# after you flash. Doesn't Cog give everyone the same market ID# when you flash it?
Click to expand...
Click to collapse
App to read Device ID, is called Android Device ID.
App to change Device ID is called Android ID Changer.
Cognition before 2.3b4 (including 2.4.x) changed everyone to the same Device ID.
To get your real Device ID flash back to stock and use Device ID. Save that somewhere.
Then you can change it if you are not running Cognition 2.3b4, using Android ID Changer.
Cognition 2.3b4 has a script to make a random device ID if you don't have one.
If you do have your device ID, you need to insert it in a file called "udpate.id" in the Internal SD cards root directory. Then a reboot should put that Device ID back on your phone via the script.
Once you have a good device ID, clearing the Market cache and restarting should get things going again.
Well that's interesting ... I wish somebody told me to save my Android ID before i Flashed it. At least i know what that Android ID is for now lol
I did make a backup of my original; i'll try to pull it out of my phone and store it on my PC just in case i do something stupid and delete it lol.
Thanks guys for the info.
This is what I read, finally found it again.
http://adaptiveeng.blogspot.com/
So, when I was flashing my device's stock ROM back onto my tablet, I made the rookie mistake of letting the screen on my Windows PC time out during the installation phase on Odin. And because life is a cruel mistress, this meant that my flashing got corrupted, and I messed up my tablet's software pretty bad.
Luckily, I was able to reflash the software successfully. But the problem came when the thing finished booting up; I was greeted with an all-black screen, and a message that said, "To start up your device, enter your password."
And there's where the problem begins, I don't have a password. Before I got into this big mess, I didn't have a password lock on my device, and never got any other password.
The only thing that I can think of that would give one a password of this type, would be the Smart Switch application that the device prompted me to use after I messed up the first flashing. I did try to use Smart Switch, but it wouldn't detect my tablet, so I ended up using Odin again.
If anyone familiar (or not) with this kind of situation could give me some pointers, I'd be greatly appreciative, since now I have a $500 paperweight sitting on my desk. Kudos!
PHP:
[img]https://goo.gl/photos/5rmwj3agDmVhPNEF9[/img]
Player Slayer said:
So, when I was flashing my device's stock ROM back onto my tablet, I made the rookie mistake of letting the screen on my Windows PC time out during the installation phase on Odin. And because life is a cruel mistress, this meant that my flashing got corrupted, and I messed up my tablet's software pretty bad.
Luckily, I was able to reflash the software successfully. But the problem came when the thing finished booting up; I was greeted with an all-black screen, and a message that said, "To start up your device, enter your password."
And there's where the problem begins, I don't have a password. Before I got into this big mess, I didn't have a password lock on my device, and never got any other password.
The only thing that I can think of that would give one a password of this type, would be the Smart Switch application that the device prompted me to use after I messed up the first flashing. I did try to use Smart Switch, but it wouldn't detect my tablet, so I ended up using Odin again.
If anyone familiar (or not) with this kind of situation could give me some pointers, I'd be greatly appreciative, since now I have a $500 paperweight sitting on my desk. Kudos!
PHP:
[img]https://goo.gl/photos/5rmwj3agDmVhPNEF9[/img]
Click to expand...
Click to collapse
Try: default_password
This has occured because you have flashed the HOME_CSC, if the above doesnt work reflash only CSC not HOME_CSC.