Related
Hi everyone. I have a samsung galaxy s vibrant on android 2.2. I am a total noob with any modifications but am going overseas next month and wanted to unlock my phone. After looking into rooting etc. I downloaded odin and darky's ROM resurrection edition. I followed the prompts to go into recovery and wipe etc. and remove battery and turn back on. After using odin and restarting my phone now just flashes the start screen showing galaxy s GT-I9000. I can't enter recovery mode just download mode. I'm unsure what to do and even tried mounting another recovery file on odin which lead me to the same point. Any help would be greatly appreciated.
Try re-flashing it and see if that works, sometimes that's all it takes. It's possible you just had a bad flash.
I've tried about 5 times now and it seems to keep failing to boot after flash and sticking on the initial boot screen and flashing on and off. Is there a way to download and flash an original ROM and mount on odin to start over?
Try getting into download mode. Hold and continue to hold up & down volume controls while holding in the power button. When the Vibrant logo comes up release only the power button. If you do get into recovery that way scroll down to install zip from sd card and install whatever rom you've got on there that you want to use. Let me know if that works or not.
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Spike84 said:
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Click to expand...
Click to collapse
Look for a hard surface... concrete for example.. now take your phone and throw it as hard as you can... Just kidding don't do that, that's a permanent reboot. I know the frustration, I've been there many times. You may want to go back and read through the noob guide, I'm not sure what else to suggest. Hopefully someone else will read this and have a better suggestion. Good luck.
haha yeah the thought crossed my mind. I appreciate your help. I'm still reading through the forum. Most instructions seem to require me to reach recovery mode or usb debugging. My phone is no longer being recognized on the computer but odin is obviously still recognizing so I'm going to try a fresh 2.2 on odin and see if that works.
Good luck, I'm rooting for ya. If that does not work and your close to a T-mobile store I'd just run it in and have them check it out, they may have to replace it.
Thanks again. I'm actually in Canada and using a sub provider from bell "virgin mobile".
My tab is stuck in Factory Mode. I have tried factory resetting it many times. Clean wiping it many times. (ODIN...Recovery) nothing seems to get it out of this mode. Stupid app that looks like the calculator is there to put in codes (Its the 1st pic in the link below)
Pics are in this thread http://forum.xda-developers.com/showthread.php?t=1322816
My Tablet is the P7510 16GB WIFI ONLY model in Canada.
I have tried the factory reset code *2767*3855# that resets the tablet but again its still there.
Can anyone give me the code to get out of this mode.
(Taken from the other posted link above as I have the same problem) I have an app called factory mode that seems to launch some sort of calculator. I am unable to lock the screen at all now. No matter what lock screen setting I try the screen never locks. Pushing the power button powers down the device in an instant. No more popup asking if I want to power down. I've tried a factory reset, but during the reset it's complaining about not having access to some directory. After the factory reset runs its course I'm back to square one. I'm not asked to setup wifi, create an account or anything.
Please I need that code to get out of this mode.
I have tried re flashing the stock 3.1 and 3.2 through recovery and ODIN
Nothing is working for me.
UPDATE:
I returned it to Samsung and got it fixed. Funny thing is that my tablet is now running 3.2 stock Samsung firmware.
I know for fact in Canada we don't have the 3.2 update for the wi-fi tablet. I must say I was impressed with Samsung's support team and the replacement unit I got back in return.
Can anybody help me out with this please!
Did it come in "factory mode" when you bought it?? Never heard of this...
No it wasn't until recently that it has that factory mode app on the home screen after a fresh reset everytime. I called Samsung about it and they said send it in. I hope they just re flash it or give me a new tab 10.1
Does anyone know how to do this? Same thing has happened to me in the UK. Has been sent back to me after repair with the bootloader unlocked and factory mode running.
I really dont want to send it back as ive already done that twice
i dont know what Factory mode is, but my 2 cents are as follows:
Fastboot flash a custom recovery and just flash a stock rom. that's what i would try first. i would imagine that would essentially format the device back to stock.
That's what I have tried. I used CWM then flashed a stock EU and US rom. Still factory mode. Any other ideas?
Can anyone help out on this? Where would this 'Factory Mode' be set? NVFLASH?
ricki_b said:
Can anyone help out on this? Where would this 'Factory Mode' be set? NVFLASH?
Click to expand...
Click to collapse
is there a solution to this? i have the same problem.
flash newest cwm, restock to nov ver. stock firmware, let it boot then reflash to newest stock, let it boot.
then finally put the overcome 2.1.1
don't forget to wipe all in between install
it should do the trick.... in theory at least... but hey nothin to lose right?
robobear said:
flash newest cwm, restock to nov ver. stock firmware, let it boot then reflash to newest stock, let it boot.
then finally put the overcome 2.1.1
don't forget to wipe all in between install
it should do the trick.... in theory at least... but hey nothin to lose right?
Click to expand...
Click to collapse
Do you mean flash an old firmware then let it update itself? Then the team overcome custom rom?
i don't think this will work. this "factory mode" is set somewhere "by Samsung" and is not changed whenever we put new rom or kernel or recovery. it seems to me that this happens on very few instances, but all mentioning it was returned that way coming from hardware related repair "from Samsung".
seems to me there are others who have this "unlockable" issue.
http://forum.xda-developers.com/showthread.php?t=1322816
did anybody took some time to seriously think about this? can samsung be the only ones that can remove this factory mode?
Just my overdue update on this thread.
I haven't been to Samsung to have them take off the Factory Mode. I don't think I will be entertained there for this issue.
I flashed the "Galaxy Task 13 Slim" custom ROM, which can be obtained from
http://forum.xda-developers.com/showthread.php?t=1340064
The latest version there as of this post is already Galaxy Task 14, but when I attempted it I lost the lock screen again, hence I reverted back to version 13.
Galaxy Task 13 fixes the missing lock screen issue. So far that's the only solution I know, but "factory mode" still remains even after rom installations, so still stuck on that mode. Anyways aside from that icon (which can be removed), no difference. Unless more knowledgeable devs here can say what advantage are to be in "Factory Mode".
Here we go again.
No sooner did we do a factory reset on my son's phone, but it stopped on us again.
To refresh your memory, my son's phone is a dead stock T Mobile HTC One, never unlocked, never rooted, dead stock.
A week or so ago, it went into a boot loop from which we could not recover. We did a factory reset and everything was fine, for a moment. My son went about reassembling his contacts, music, etc., making sure they were properly backed up this time.
After the factory reset, everything seemed to work fine, for a time. But then the first time my son powered off his phone, charged it overnight while off, and tried to power on again, the PIN unlock screen won't come up, so he can't open his phone.
We can get to the bootloader and to the recovery. Tried wiping the cache from recovery mode, but that didn't help.
Is it time for another factory reset? Is there anything that would have potentially caused both problems loading Android/Sense (the boot loop from before and the failure of the unlock keypad this time) that we should investigate?
I love my own HTC One, but my son's opinion of his is quite different, and it's straining family relationships.
Any thoughts? Thanks in advance.
GenerousDad said:
After the factory reset, everything seemed to work fine, for a time. But then the first time my son powered off his phone, charged it overnight while off, and tried to power on again, the PIN unlock screen won't come up, so he can't open his phone.
Click to expand...
Click to collapse
Only info I can find on this suggests another Factory reset.
Do you have any idea what apps he may have installed? I have seen that there is some "beta" keyboard software out there that upon expiration will fail to appear, making it all but impossible to unlock. Of note regarding that is Swiftkey beta software. Their forums have quite a few posts regarding this issue.
Sorry I couldn't be more help. I know of no other way around the pin other than a factory reset.
If you can get the device into fastboot mode plugged into a Windows 7 PC perform the following:
fastboot erase cache
use the volume keys to select bootloader and power to active.
use the volume keys to select factory reset and power to activate.
I will talk to him about apps, but I believe he was using the stock HTC Sense keyboard.
If it's an offending app, will removing the app via his Google account using his laptop and then restarting the phone solve the problem?
Any thoughts as to why this might happen so fast on the heels of the boot loop problem described in my other thread?
Does the Fastboot Erase Cache command do anything different from the Wipe Cache Partition option on the stock Recovery menu? I've tried that already without success.
Thanks for your response.
PhoenixPath said:
Only info I can find on this suggests another Factory reset.
Do you have any idea what apps he may have installed? I have seen that there is some "beta" keyboard software out there that upon expiration will fail to appear, making it all but impossible to unlock. Of note regarding that is Swiftkey beta software. Their forums have quite a few posts regarding this issue.
Sorry I couldn't be more help. I know of no other way around the pin other than a factory reset.
If you can get the device into fastboot mode plugged into a Windows 7 PC perform the following:
fastboot erase cache
use the volume keys to select bootloader and power to active.
use the volume keys to select factory reset and power to activate.
Click to expand...
Click to collapse
I
GenerousDad said:
f it's an offending app, will removing the app via his Google account using his laptop and then restarting the phone solve the problem?
Click to expand...
Click to collapse
Worth a shot, I suppose. Do not know for sure.
GenerousDad said:
Any thoughts as to why this might happen so fast on the heels of the boot loop problem described in my other thread?
Click to expand...
Click to collapse
Coincidence most likely. Really really really bad luck.
GenerousDad said:
Does the Fastboot Erase Cache command do anything different from the Wipe Cache Partition option on the stock Recovery menu? I've tried that already without success.
Thanks for your response.
Click to expand...
Click to collapse
Same. Erases the /cache partition. I use fastboot personally because, well...ok, I really have no idea why I prefer it. Just one of those things, ya know?
Good luck! :good:
I recently went to unlock my phone via Z3X box, my phone was on 4.3 they said to downgrade to 4.1, I followed the steps using Cygwin Terminal in making a custom firmware, I flashed it via Odin and it passed, however was stuck at the Samsung Logo, no usally in this case I would boot into recovery and wipe data and cache, however my Home Button does not work, so I used my Jig to force in to download mode and flashed stock I747m 4.3, went to boot and same thing stuck at the Samsung logo???? any ideas what's wrong here???
mza2k9 said:
I recently went to unlock my phone via Z3X box, my phone was on 4.3 they said to downgrade to 4.1, I followed the steps using Cygwin Terminal in making a custom firmware, I flashed it via Odin and it passed, however was stuck at the Samsung Logo, no usally in this case I would boot into recovery and wipe data and cache, however my Home Button does not work, so I used my Jig to force in to download mode and flashed stock I747m 4.3, went to boot and same thing stuck at the Samsung logo???? any ideas what's wrong here???
Click to expand...
Click to collapse
Tried to factory reset after the 4.3 upgrade? Sounds like you might have borked your EFS partition with the z3x box, if a reset doesn't help...
http://forum.xda-developers.com/showthread.php?t=2471421
Some info from there might be helpful if you are still stuck. I know it is for the Note 3, but many of the same ideas apply, though the mount points are most likely different thus you can't just copy and paste those commands and hope it works (might even make it worse if the partitions are that different).
Is the Home button broken or just stopped working after trying to do this stuff?
Yeah the Home button just doesn't work when you press it that's why I needed the Jig to get in to Download Mode, and the phone was fine after trying with Z3X box it didn't do anything with Samsung tools because I was on 4.3 it started when I created that custom firmware and flashed it, haven't been able to get it to boot since that even with Stock Firmware..
Think you might need to check out this thread then:
http://forum.xda-developers.com/showthread.php?t=2549068
Sounds like an issue with the downgrade / bootloader deal. No Home button sounds like it might really cause some issues here though. Owning a repair shop, I'm pretty familiar with the S3 construction and it's pretty rare that the Home button stops working. Has it been repaired or gotten wet or something?
the phone was water damaged I just replaced the main board with a new one and the phone was fine minus the Home Button, and I have tried the SD card thing about 3 times now and it doesn't do anything???
This will save you 8-12 hours of your time if you are lucky. This means that it also includes the meaningful links of 8-12 hours of searching. Sentences in italic are important. 1 link is for the Odin official website, the rest are re-links back into XDA.
The device in question is a SM-925T Tmobile S6 Edge.
The problem was this. I rooted my phone and messed around with Greenify and the Play store. To prepare for rooting, I allowed unknown downloads, unlocked the bootloader, and turned my security lock off (I had set it to a finger print lock). After I was done rooting, I immediately locked the bootloader again(<--A mistake that caused my bootloop/ soft-brick). After I was finished messing with the above apps (Greenify, etc), I wanted my phone to restart. So I held the Power button and selected restart, while I was on the lock screen (may not be important). I noticed that it took a long time to restart, and upon closer examination, I noticed another error under the "kernel is not seandroid enforcing" (which appears to be natural for rooted phones). The error was "Custom Binary blocked by FRP Lock". It was a new error. I investigated this new problem using the internet , and this dude was panicking like hell, but he didn't appear to fix his problem. He did hint that returning to the bootloader to its locked state was a mistake. Looked a bit more and this guy pointed to another thread, which introduced me to flashing and more importantly his fix, which was to flash the stock 5.1.1 image through odin. He used this link, which contains all the stock firmware for the majority of the new Samsung S6 and S6 edge versions. To make a long story short, most of these fixes involved flashing your firmware to the stock version. So I went to the Odin Website, and downloaded every version, as a couple threads have said that different versions worked for them. Here is a thread with everything you need for Odin. Now, after sorting through and finding micro USB cables that are detectable by Odin, an important step because Odin might develop a pattern of detecting then failing to detect your device through that cable, and testing all the usb 2.0 ports, I was ready, and had Odin with my stock firmware. Odin kept saying "NAND Write", then in the next line "FAIL". This was annoying as Odin wouldn't detect my device again unless I unplugged it, restarted it to download mode, then restarted Odin before plugging it back in. I got confused and found links for somehow fixing the .tar files, stock roms, .pit files (DO NOT MESS AROUND WITHOUT KNOWING WHAT THOSE THINGS DO), and other threads/websites that say to boot into recovery mode , factory reset, then wipe your cache. I could only do that once. After me messing around with all of the above file variants and supposed fixes to help with my issue, I couldn't boot into recovery mode, it got stuck on the "Samsung Galaxy S6 Edge" logo. It did not fix the NAND write failing. There however, are a lot of websites allowing you to download stock software for your phones, and I don't think I can link them as it might break a rule. Surprisingly, some have claimed that using a stock file for another device worked to fix their problem. This thread, which convinced me to use Smart Switch when it failed for everyone else, was very useful, although I recommend downloading Smart Switch from the official website of Samsung. None of the Odin flashing had worked so far, including the Roms and .pit files so I tried Smart Switch. I opened it, and upon selecting the "more" tab on the upper right corner, a bunch of tabs drop down. One should be "Emergency Software recovery and initialization". I had to find my S / N (Serial) number, and I was very confused on how to obtain that number as I was locked out. But to obtain it, do the same process to boot into download (hold volume down, home key, and power key), but stay on the prompt and don't go to the screen that has the word download in the middle. Don't do anything other then reaching the prompt confirming if you want to install a custom ROM. Then, press the home key and it should show your S / N number along with your IMEI number. Once I imputed the code I saw on my phone into Smart Switch, it told me to connect the device. Now, by this time, I realized that Odin only detects my device if it is actually in the download screen. Why shouldn't my computer? I booted into Download on my phone and followed the steps on my computer, making sure that the computer can recognize my phone while it is using a valid USB port and Cable. And after some waiting, for me, my problem was fixed and I could use my phone again, it reverted to it's out-of-box state. I hope this drawn out but very specific explanation helps you guys. It's my first post And also, this thread confirms that you can use a USB hub for flashing(at least for ROMS), Smart Switch, and for rooting.
Thank you for this detailed account, however nothing of the above has worked for me. Odin won't flash the firmware of 5.0.2 (and I tried 5.1.1) and Smart switch does not recognize the device to do anything. BTW phone has been rooted for months and last night decided to turn on its FRP lock randomly and now I'm stuck. Any help would be greatly appreciated.
Explain throughly what you have tried. Especially different ports, cables, and computers. Did you have the right device drivers? Did you do anything else?
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Xalmey said:
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Click to expand...
Click to collapse
press vol down home keys and power key once you get to the first blue screen release vol and power keep holdind home but I already tried smart swich didn't help
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
EsperaKing said:
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
Click to expand...
Click to collapse
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
callumbr1 said:
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
Click to expand...
Click to collapse
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
EsperaKing said:
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
Click to expand...
Click to collapse
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
callumbr1 said:
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
Click to expand...
Click to collapse
Thank you for you reply.
Please can you tell me where I can find such software or how to do it clearly! I know how to use Odin but I don't know how to exclude user_data to be wiped. Thank you
Bonafid3 said:
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Click to expand...
Click to collapse
Thank you thank you thank you!!! This is exactly what I was looking for I had just rooted my note 4 running 6.0.1 and had no idea what the oem option was as no rooting method talked about it at all so naturally as soon as i added my Google account phone restarted and locked up.
Kies was the answer I needed as frp lock was active in download mode and my factory reset in recovery failed everytime but running Kies firmware upgrade and entering my model and serial number it installed perfectly in download mode with frp lock still active saved me alot of hassle ?