[Q] Password at first boot while flashing stock rom - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
I'm trying to flash my gf's phone and while flashing
GT_I9000_XXJVK_XXJVK_OXAJVK via Odin (pit,pda,phone,csc)
at the first boot I'm getting a "Enter your password" thingy.
Must be some sort of a PIN? She claims her phone isn't pin protected (or atleast that she can't recall doing so ).
I've flashed the exact same thing yesterday to another phone and it worked perfectly.
Any help would be appreciated

SOLVED. Entering wrong combination multiple times wipes everything
Thanks

Related

Help Encryption unsuccessful error

So to set the story i had came home and rooted jb via linux method. Then presumed to use bootstrap as a recovery. I installed it and it said success. Then i presumed to change the bootloader unknowing if it was locked. So i reboot and i am stuck at Encryption unsuccessful screen and the only option is to power off or reset. What do i do ive tried to reset but it doesnt work also i tried to do a hard reset via stock recovery this also didnt work im unsure where to go about this problem now. Please help Im panicing! From what ive researched i think its soft bricked. Also there appears to be a fix on House of Bionic but it isnt clear. Lastly, I believe the problem resides with bootstrap but im unsure its just a hunch. All options will be tried.
You can use fastboot -w to wipe it and start over but you can't use the Bootstrap recovery any longer with 4.1.2 as it causes the corruption you are seeing.

[Q] Not able to flash anything via Odin

First, hello to all as this is my first post and please excuse my bad english.
I've a GT-I8190 that I'm trying to flash via Odin, but some strange things are happenning. All the process goes fine, but when I finish the upload nothing changed. I know how to use Odin (this is not my first time flashing a device), and I know what to expect from each option of the program, so I'll go to the main point.
As far as I cannot flash anything (I repeat, all the process goes fine and SUCCESS appears on Odin, so no NAND write errors, no connection errors, etc ...), I tried to do the last thing I could do to check my thoughts: I performed a "Nand erase all" (Odin 3.09). No PIT file, no CSC, no PHONE, no BOOTLOADER, only CWM on PDA. As far as I understand, doing this I'll loose bootloader, radio, EVERYTHING, and I won't be able to turn on the phone as far as it won't have a valid bootloader... so, when all process finished ("Erasing NAND" message appeared on log, and SUCCESS again when finished), I started the phone and... it booted exactly as if I did anything with Odin!
I tried to make a reset to factory defaults from OS, but results are the same: nothing changed on reboot (still have my apps, contacts, EVERYTHING). Manually uninstalled Facebook and AVG, but when I restart the phone they are still there!
So, question is, is there something I can do with this phone? It seems that NAND is write protected or something like this... Is there any eFUSE that prevents to write to NAND?
I don't know if there is another case similar to this one in the forum, I've searched a lot but find nothing.
Any help will be appreciated.
PS: BTW, I cannot acces to recovery menu
PS2: ADB reboot-bootloader does not work, it restarts the phone normally. I cannot test fastboot oem lock / unlock commands
Did you realize any solution? I have similiar problem.
try flashing with odin 3.07
Dont desconnect phone untill you see the main screen of your phone I mean past boot up
Let the glash finish phone restart with cable plug in
Same here
I'm having exactly the same problem. HELP! i haven't tried changing the battery because i haven't been able to do it, but there's something that should work

[Q] can't modify anything on device

hello everyone, this thread might seem like a repost to some of you, but since the answer has yet to be found on the other thread, might as well try asking about it myself
so i've got a galaxy s3 mini (the i8190 version, not the l or the n) it's in stock 4.1.2 international version. yesterday, out of nowhere the phone just keeps on rebooting after a few minutes of booting up ( it got to the lockscreen and home screen just fine, but it keeps rebooting after that). and i think, well might as well just flash something on top of this stock rom so i decided to get the cm11 from novafusion, along with odin and tried to flash it. it all goes well in odin, no problem at all (odin flashes green passed sign).
but the strange thing is, when the phone rebooted, it goes back to the stock rom, with all the apps intact and with stock recovery. so far, i've been trying to flash almost everything into this phone via odin and odin always says it succeeded but nevertheless, everything stays the same, i've tried flashing some custom roms, custom recoveries but it doesn't seem to work. and the flash counter never goes up, it still says "custom binary download : no"
i've also tried to go to stock recovery and tried to wipe data / factory reset the phone which it said it has done successfully but when i booted in, nothing changed. i'm still logged on as my account with all the apps and files intact.
this problem has also been asked here but no definitive answer seems to have surfaced there.
please, any help would be appreciated

"Custom Binary (BOOT) blocked by FRP Lock" After updating to 5.1.1

Hello, i have been researching for this issue that i have for over a month now, and yet i haven't found any solution or even a clue on how to fix it, and im sure lots of people are having the same issue that im having, let me explain what exactly happened to my phone and what i exactly tried
i was running on 5.0.1 G920TUVU1AOCG, and at that time "Ping Pong Root" was not yet available, so the only way to root the phone was to flash the "g920t_of6_aou_kernel_v1.tar" witch i did and installed SU using "g925t_of6_aou_twrp_recovery_v13.tar" and the phone worked perfect after that, and after the 5.1.1 lollipop came out, i decided to upgrade to that, so i flashed stock 5.1.1 odin firmware and flash the custom kernel "g920t_of6_aou_kernel_v1.tar" to get it out the bootloop since it was flashed previously on it, it worked and booted up and all seemed to be fine, i also wanted to perform a factory reset, and here is where the PROBLEM started, i forgot to turn on OEM Unlocking in Dev options, so after the factory reset, the phone got stuck on the bootloop "Samsung galaxy s6; powered by android" and the only way to make it bypass this bootloop is by flashing the "g920t_of6_aou_kernel_v1.tar" again, but i cant flash that because i forgot to turn on the OEM Unlocking in the dev options, and every time i try for flash any custom recovery or custom kernel and will give me "Custom Binary (BOOT) blocked by FRP Lock", so now im stuck on the bootloop, i cant access the phone to turn on the OEM Unlocking, Phone is basically STUCK.
I have tried flashing all stock firmwares that are, i have tried flashing all available kernels, i have tried Factory resetting the phone and wiping the catch, i have tried every guide on XDA and nothing ever worked for me.
i apologize for the long explanation, but i just dont want people to think that i am repeating the same question over and over since a similar question was asked by other members on XDA previously.
Thank you very much for taking the time and reading my question.
Do you still have recovery mode?
EDIT: In this thread: http://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-t3152054 every person that had the problem fixed it by flashing the stock firmware. make sure you're flashing the stock firmware that's the exact same as the firmware when your phone worked. So if you were on OI1 for example, you have to flash OI1 firmware or it wouldn't work. Try a couple times too, I've heard ODIN can be wonky sometimes.
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
ameenz77 said:
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
Click to expand...
Click to collapse
Try to factory reset in recovery and flash the tar trough ODIN again. If that doesn't work, try to restore it with SmartSwitch. A lot of people have success restoring their phone that way. If that doesn't work then I don't know.

Cannot flash any custom recovery - help needed

The problem: Although I was able to do it perfectly before, now for some reason I cannot flash a custom recovery on my K3 Note. I tried doing it according to this tutorial https://forum.xda-developers.com/k3-note/general/sp-flash-tool-tutorial-to-install-twrp-t3346041 and the process looks like it finishes successfully with the Download Ok message, but when I actually boot into recovery it is the still the one from the stock rom (In my case, it just displays the message "Have been in media mode, long press the power button and the [sic] normal boot").
The background: I have been doing a lot of things with my phone, and so unfortunately it's hard to say when exactly the problem started and what caused it. But here is how the story goes:
1. I kept flashing lots of different roms and testing them. Often, I would do this without inserting the sim card, but when I did get to it, it would connect to the network and work fine.
2. When I finally thought I found the perfect rom, I insert my sim and... it won't connect to the network. It is seen by the device and even displays my operator's name and my phone number, but I can't make calls or use data.
3. At first I think it may be a problem in the rom. So I try another similar rom: same thing. I then download another rom I've never tried before, and when I flash that, the phone becomes soft bricked and shows no signs of life.
4. I am able to revive the phone by flashing the stock. But the sim still doesn't work, even though it definitely used to work on this rom before. Already at this point, I replaced the stock recovery.img with the custom one I used. I discover that the sim not connecting is a problem with the IMEI.
5. One apparent solution to the IMEI that I read about was to open Flashtool, go to the Format tab choose Auto Format Flash/Format whole flash except bootloader, check the "Validation" box, and start the formatting process. I do this and then re-flash stock, but the IMEI problem persists.
6. I find instructions online that tell me to root my phone (I used KingRoot for this), install the Engineering Mode app, and enter the correct IMEI using the command AT+EGMR=1,7,”Your IMEI Number”. I try it and it doesn't work. When typing "AT+EGMR..." the error is "This command is not allowed in userbuild", if I type "AT +EGMR...", it becomes AT command is sent: Error".
7. I decide to go back to a pre-rooted rom that has worked quite fine in the past and re-try this procedure from there, and that's where I discover that my custom recovery hasn't installed and would't do so when I tried flashing it again.
So yes, I pretty much have two problems in one here. My priority is to solve the recovery problem, but if someone knows how to fix the IMEI one, please let me know too.

Categories

Resources