Alright, so for the last few hours I have apparently been mucking up my phone in the completely wrong manner.
I have a Samsung Galaxy SII running the most recent Gingerbread (2.5.6?) I don't remember. Because I'm rather dull apparently, I can't check either.
When my phone reboots (NO IT'S NOT A REBOOT LOOP.) I am offered some options I can navigate with the up and down buttons on the left. In the past, when I hit the power button on the right it would pick one. Now, because I used the COMPLETELY WRONG FIRMWARE or whatever with Odin when I flashed it, I can no longer use that button to select anything.
I can hover over the option I want and stare at it, but I can't select it. It's saddening.
Here's what I did to create myself a bunch of first world problems, in mostly the right order.
1. Was born stupid
2. Got XWKDD_insecure.tar
3. STUCK THAT ON MY PHONE VIA ODIN
4. noticed screen had become very bright and back button didn't work. Ohgod.
5. Attempted to fix everything by installing a custom ROM (CyanogenMod)
6. As this mod installed, it deleted some things. I don't remember what exactly.
7. Something failed during installation.
8. I am stuck looking at the start screen and have NO OK BUTTON WHATSOEVER and feeling very silly because I can no longer hit on women as well and it is valentines day.
9. I noticed that wouldn't matter because if you can't root a phone, you aren't getting in anyway.
Any help would be appreciated. I mean I already found my helmet so that bit of advice wouldn't help me, but aiding me in getting my phone unbricked and possibly running CyanogenMod would be EXCELLENT.
Summary/TLDR:
I messed up my phone by installing the wrong firmware. I now have a remapped OK button that doesn't exist on my phone and cannot select options in recovery.
If I could select options, I still might not know what to do.
I watched your noob video, that was excellent. Some other sites I use could use one of those.
ON THE START SCREEN it says
--Copying media files--
Successfully copied media files.
# MANUAL MODE #
Updating application...
Successfully updated application
Applying Multi-CSC
Can't access to 'system/csc/att/system/'
Successfully applied multi-CSC
Er, woops, coulda put that in the first post via edit.
And nevermind. I just used this guide here: http://forum.xda-developers.com/showthread.php?t=1313659 to flash it back to bone stock. This particular fix is for the Galaxy S2 and I do not know if it would work for other phones.
Thanks anyway.
I've had this device for years ever since it hit the shelf it has sat in my hand. I have sooo much importance on here I have to get it back here is the...short story.
I installed this: Font Installer (Rooted)
Everything was going fine one thing I noticed is when I downloaded a font it changed it itself but I was like fine leave it be. Then I decided I wanted my system font back so I went to Settings, Display and such and found that the installed font was now default so my next step was to find out where is the fonts located so I went to system, fonts then hit INSTALL on the one I wanted it and boom it crashed. Now it just shows the Samsung sign then it dies then Samsung then dies then repeat.
I hesitated rooting, overclocking and such as a matter of fact overclocking is the only thing I did when I rooted which I felt stupid for because there was no dramatic increase the only benefit it gave me is a GB of storage but otherwise I don't even use root like things. The bad news is I think/assume I need back up and I don't have one I did something backup wise with System Tuner but I don't think it was a system wide backup.
Right now it is siting on my desk in recovery mode or whatever happens when you hold volume up then power. I don't know how but I was thinking I could reflash the default system files but I figured they have to be on the sd card I'm running with guesses tell me if I'm F'd or whatnot. Preferably not F'd -.-
Kenobz said:
I've had this device for years ever since it hit the shelf it has sat in my hand. I have sooo much importance on here I have to get it back here is the...short story.
I installed this: Font Installer (Rooted)
Everything was going fine one thing I noticed is when I downloaded a font it changed it itself but I was like fine leave it be. Then I decided I wanted my system font back so I went to Settings, Display and such and found that the installed font was now default so my next step was to find out where is the fonts located so I went to system, fonts then hit INSTALL on the one I wanted it and boom it crashed. Now it just shows the Samsung sign then it dies then Samsung then dies then repeat.
I hesitated rooting, overclocking and such as a matter of fact overclocking is the only thing I did when I rooted which I felt stupid for because there was no dramatic increase the only benefit it gave me is a GB of storage but otherwise I don't even use root like things. The bad news is I think/assume I need back up and I don't have one I did something backup wise with System Tuner but I don't think it was a system wide backup.
Right now it is siting on my desk in recovery mode or whatever happens when you hold volume up then power. I don't know how but I was thinking I could reflash the default system files but I figured they have to be on the sd card I'm running with guesses tell me if I'm F'd or whatnot. Preferably not F'd -.-
Click to expand...
Click to collapse
Can you put it in download mode?
Then flash stock rom with odin you should be fine after that
Yes
safariking said:
Can you put it in download mode?
Then flash stock rom with odin you should be fine after that
Click to expand...
Click to collapse
I'm stuck on step 5 Go to the PDA section doesn't do anything it pops up a window as if theirs suppose to be a file of some type. Also my device will not pop up on the computer.
http://forum.xda-developers.com/showthread.php?t=1922461
Kenobz said:
I'm stuck on step 5 Go to the PDA section doesn't do anything it pops up a window as if theirs suppose to be a file of some type. Also my device will not pop up on the computer.
http://forum.xda-developers.com/showthread.php?t=1922461
Click to expand...
Click to collapse
Reinstall drivers/odin
safariking said:
Reinstall drivers/odin
Click to expand...
Click to collapse
I have no clue had to do either even with going to the links I have the drivers downloaded as well as Odin I.....don't know what to do. My device doesn't pop up on the computer so how do I install the drivers it's in download mode a message popped up at the bottom on Windows and said installing drivers when I plugged it in.
1. Does Windows install the drivers automatically??
2. How do you use Odin?
3. Could anyone respond help me completely because as a new user I have a 5 minute wait rule at this forum seems slow as mollasess.
All I did was install a stupid font app which decided to kick me out now I can't get back in the links and threads around here are ok but not in depth step by step. I went to a couple threads with brick problems and the per usual seems to be 2 respones then the thread dies I really would like a walk-thru of what should be my next step. Again I can get into download mode, I have ODIN and the SAMSUNG drivers now what do I do I feel some sarcasm stick rubbing, magic remarks began to crop up -.-
Kenobz said:
I have no clue had to do either even with going to the links I have the drivers downloaded as well as Odin I.....don't know what to do. My device doesn't pop up on the computer so how do I install the drivers it's in download mode a message popped up at the bottom on Windows and said installing drivers when I plugged it in.
1. Does Windows install the drivers automatically??
2. How do you use Odin?
3. Could anyone respond help me completely because as a new user I have a 5 minute wait rule at this forum seems slow as mollasess.
All I did was install a stupid font app which decided to kick me out now I can't get back in the links and threads around here are ok but not in depth step by step. I went to a couple threads with brick problems and the per usual seems to be 2 respones then the thread dies I really would like a walk-thru of what should be my next step. Again I can get into download mode, I have ODIN and the SAMSUNG drivers now what do I do I feel some sarcasm stick rubbing, magic remarks began to crop up -.-
Click to expand...
Click to collapse
You should have downloaded an .exe file for the drivers. Run that, reboot pc for good measure, and plug in your device. Open device manager on your PC. The player should show up as "samsung gadget serial" or such. If it does, then it should also appear in odin. If not, hold power and volume down until it reboots back into download mode. It should then. Now click on pda and browse to the .tar or .tar.md5 you downloaded from the stock rom thread. It may be inside a zip or a rar, so if it is extract it first. Make sure repartition and update bootloader are UNCHECKED, and click start.
Sent from my Galaxy Nexus
This is only a complementary reply to mevordel's but here's if you want some files needed:
http://forum.xda-developers.com/showthread.php?t=1922461
You sons of *****es it worked I'm clicking the thanks button for you both I have a bricked HTC device laying around now I get to go harass them. Wow doesn't even express the gratitude I wont be posting any tits but I might lose my man card by throwing up a giant hug and kiss for happiness expressed. Gotdarnit it went thru like magic for the bad I'd say both your threads needs a bit of explaining. Otherwise perfect did I mention I haven't seen Touchwiz or Swype in ages...
1. So I have a question is all flashing this easy and also as per usual....whats the best....fastest.....stable-lest.....popular rom.
2. Is this Stock rom completely stock and if not what am I missing before I play with something and return to XDA.
3. My Auto Rotate has been broke for a couple months I can tell the sensor is completely off although it still works is there anyway to re-calibrate it completely root wise???
Can someone help me I cannot find the MD5 every file I downloaded it does not have it included.
Link?
Edit: This is a slightly new problem nothing to do with the old I bricked it again and I basically can't find the MD5.
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 ?
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.
Hi, long story short, I bricked my phone due to a mistake from my part trying to install TWRP. I was on version V12.0.3.0.RFQEUXM, I have magisk installed and thus no access to OTA update. I saw that the V12.0.5.0.RFQEUXM was out, so decided to update. Before that, I had the bad idea to say to myself that I would take a backup with TWRP, and kabaaaam, I probably made something stupid and bricked my phone.
Luckily, plugging it to my computer showed me that it was in EDL mode. And thanks to the stupidity of Xiaomi at the end of 2020 when they bricked phones with the Android 11 update, I came across the guide of @nullby to unbrick it. Maybe I should have looked at this into more details and only use it to reflash the boot, but I flashed everything.
I followed this guide, except that at the end instead of flashing the repacked service ROM, I directly flashed the V12.0.5.0.RFQEUXM.
Hooray, the phone is unbricked, I reflashed magisk and everything is back to normal. Almost everything I should say, as the fingerprint sensor is not active anymore. Nothing happens when I try to add a fingerprint, so I suppose that it is something like a driver fault. When using Droid Info, I also see no reference next to FOD.
So now, how to resolve this ? My best guess would be to flash the latest firmware found here. It's only 69Mb and by looking at what's in it, there are definitively things that are not included in the full fastboot rom. But before I try, I prefer to ask for some advice instead of bricking it again…
Also, seen my last experience with TWRP, may I flash it with FK Kernel manager instead ? I've never used it, but from what I read, it should work.
Any ideas or suggestions ?
Thanks a lot.
I'm replying to myself in case anyone has the same issue in the future:
Enter the phone dialer and enter the following code: * # * # 64663 # * # * then press on the 3 points above and go to FingerPrint_C.
Press on start, then it will ask to put "FLESH_FLAT" you need to put a white sheet on the fingerprint sensor, in daylight and launch the test.
then you will ask to put "BLACK_FLAT". then you put something black and opaque on the fingerprint sensor and launch the test. Putting the phone upside-down on a table also work.
If you have the "performance_test failed", try again.
When successful, restart the phone and enjoy the fingerprint again.
Credit to u/danmech on reddit.