Hi,
I am a rather experienced user when it comes to flashing/using odin and I had successfully updated to JVK from JV1 and had been using it for a few days. I decided I wanted to use a ROM now, so I went to http://romkitchen.org/beta/ and downloaded a no-wipe rom. I was already rooted but needed CWM so I flashed the new version of CF-Root. Everything worked fine so I used CWM to flash the rom. It started an endless boot cycle (Just the galaxy s i9000 words over and over again) so I decided to just repartition and flash JVK with Odin again as I had a backup and wouldn't lose anything. That worked normally but once the phone started restarting (before it got to any boot image) it went to a password entry box. These were the exact same files that I had used to to flash gingerbread before and I have never had this happen to me before. The only physical button that does anything is the menu button which dims the screen. Pulling out the battery/restarting/reflashing JVK or JV1 doesn't help. Froyo (JS5) does work though so I am using that now. I have tried 3 different versions of Odin, going to JV1 then JVK, different .pit downloads, bootloader and non bootloader version of JVK, none of them make a difference, always the password. I have tried all my passwords, and none of them work.
Anyone have any ideas?
Thanks
I have the same problem. Tried a lot of variants without any luck. Currently running JPU instead.
I've started to wonder if the phone is actually asking for a unlock code, as if the phone was locked to specific operator. But anyway there is a digit code you can check if your phone is locked, and mine is not.
Please anyone know how to work around this and what is causing this password prompt?
Rooting or putting a modded kernel on jvk does not help either, still asks for password.
First of all try 'samfirmware.com' as the password, may be a long shot but maybe the rom originally came from there.
if that doesnt work, i would send doc or stefunel a PM (or check thread) incase some one else has had this issue, they may no the password considering it was downloaded from their kitchen.
Tried that before, didn't work. It's not their rom anymore, just the stock JVK.
Did you try some common pre-set passwords on electronic devices like '0000' or '1234' ? Maybe this is just something like on a dvb receiver...
Sounds unlikely but since you've tried the 'normal' ways...
very strange. Try Samsung , Gingerbread , 0000 , 1234 , I don't know anything else .
BUT AT YOUR OWN RISK!!!
no idea if it will even work
hacksome said:
FIX for anyone having "Confirm Password" issue on Boot:-
1) Just enter some wrong password multiple times
2) Then a Warning message will appear telling you it will remove all SD Card data
3) Type something wrong again!
4) Let the SD Card get wiped.
5) Then the system will bootup properly next time.
I just did one more *2767*3855# Full wipe after bootup.
Click to expand...
Click to collapse
link to the original poster http://goo.gl/hyzin not sure it will work
PAGOT said:
BUT AT YOUR OWN RISK!!!
no idea if it will even work
link to the original poster http://goo.gl/hyzin not sure it will work
Click to expand...
Click to collapse
Thanks!!!!!!!!!! It worked! Now to install Darkys Rom.
It works
Thanks Pagot, that worked and didn't erase my internal SD card (I have no external one).
just enter many wrong password it'll no erase your internal or externe sd card
Tested on JVO
It Works
Had installed deodexed JVP(2.3.4) via CWM, decided to reset and erase the internal SD card. Got the dreaded confirm password on boot, typed in the wrong password multiple times, the phone rebooted, internal SD card was formatted.
Could that be the encryption password!!???
I was testing my device against a MDM (Mobile device management) system called Afaria, where I work and have enabled encryption in the policy applied to the device. When I got the enter password dialog box I entered the encryption password and the device accepted the password...
this saved my life ahah
works fine with 2.3.5 too
thanks
Very helpful thank you. Worked for me on my Infuse. Took about thirty tries and waiting through about 4-5 30 second timeouts for incorrect password but finally said it would wipe data in accordance with security policy and bam back up running Entropy's DD deodexed and rooted. Thanks fellas. You guys sure helped a noob out.
2992
Thought to update:
Worked for me too - happened every now and then on my lost EFS'ed i9000, as I was trying to install different roms.
Entering it wrong enough times wiped the sd card (that I could careless about)
Cheers!
Settings->Security Causes Settings to FC After Setting Password Lock [Chroma 1/18/16]
Hello, I bought a Nexus 6 off the recent Amazon sale, rooted it and flashed Chroma (and the recommended GApps) on it. It has been great so far, until this morning when I decided I wanted to have it password locked. After doing that Settings FCs. If I go to Settings again everything is fine, until I select Security, it FCs again. The password lock is in place, but I can't change it, or disable it.
I tried a cache/Dalvik Cache wipe and reboot.
I tried the solution outlined here: http://forum.xda-developers.com/nexus-4/help/settingsecurity-force-close-t2161674
I tried a complete wipe and clean flashed Chroma and GApps a couple of times. This removes the password lock, but if if I try to set a password again the same thing happens.
I updated the radio.
I am back to where I was this morning, no password, but unable to set one.
I haven't tried a pattern or PIN lock.
Any help would be appreciated.
Please do not make threads when there is already one open on the topic.
Thread closed.
I had setup fingerprint on S5 and it didn't work out well, so I switched to PIN, today when I tried setting up fingerprint again, it asked for previous fingerprint, i tried it several times but failed and it started asking for alternative password which I can't remember. If I reflash the stock ROM will the alternative password will be gone? I don't care about the data being wiped though.
Help?
Here is my situation (this started a couple weeks ago and I am a little fuzzy with some exact details).
My phone was running a little slow, so I restarted it. After the phone rebooted, it no longer worked. I can't remember for certain if the error message "sim not allowed: mm#3" was showing at that time, but I do remember that not only was the phone not working, but the phone's imei had been replaced with a meid. I found this out when going into settings, then about device, and then into status. I don't remember when exactly the meid dissappeared and the phone started showing its imei again, but yes the imei has returned. Even though that issue cleared up, the phone still isn't right.
What's going on now.. Sometimes I get the error message "sim not allowed: mm#3" and sometimes I don't. When the message does show, maybe 50% of the time with a simple restart of the phone the message will go away and the phone will partially work (making calls/text but no data.. wifi works). The other 50% of the time I can typically get it to accept the sim by entering the code "*#*#4636#*#* and then changing the preferred network type (the same network type does not always work). When the phone will work (again, that's only partially working) it will now only use the edge:2 network type.
It goes without saying that everything I have done attempting to fix this issue has failed. I have us.d odin to reflash the firmware packs and even the modem file. The list of files I flashed are G900A_Downgrade_to_NCE.tar.md5, AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5, CP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_ATT_G900AATT1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5,
and these files did all flash successfully. I attempted to flash G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 but the process failed. Unfortunately I don't remember the error message when it failed, but I will be happy to reflash it so I can get the error code for you.
I even went as far as flashing the ported tmobile rom and then flashing back to at&t, and yet again the problem was not fixed.
Just before starting this post I followed the steps listed in http://forum.xda-developers.com/galaxy-note-3/help/sim-allow-mm3-solution-t2921741 hoping this may work, and it doesn't appear to have made any difference.
fix for sim not allowed mm#3
rooted the phone, preformed a nv item rebuild and the issue seems to be fixed.... phone is running 4g currently. no repeat of the error code yet
"there was a problem connecting to fonts.gstatic.com" error during initial startup
new max 2, white, from banggood, first boot, google asks me things... i enter the passw for my wifi, then i encounter this error "there was a problem connecting to fonts.gstatic.com" and there is no way to go out... to go into os, i am STUCK at this error!
i bypassed the problem i don't know why, but also if at the moment i am in the OS, i still have problems with google cccount. i can't add a google account i read always the same problem!
i also updated the rom because i found an OTA but nothing changed. i would not root and change the rom of the phone BECAUSE it is not for me but for a friend and i would keep it STOCK 100%
any solution please