Hello. I was working on a phone, an samsung galaxy s5 (chinese version) sm-g9006v and I tried to root it in order to add playstore and more to the device.
However, I used odin and a CF-autoroot file for this device.
After that the device went in a blocked white screen with a chinese log and on top left it wrote "set warranty bit recovery" and some other text.
Waited a bit since I thought it was a phase that was required for the root process to continue but it didn't do anything for a few good minutes, however i proceded to remove the battery (since the power button wasn't helping to reset the device) and now it won't start and it won't enter in a download state to use odin to eventually flash something else onto it.
Any help is appreciated as I'm kind of desperate at this point. Thank you.
Edit: if I connect it to the pc it gets in a start-up loop i believe.
scimini said:
Hello. I was working on a phone, an samsung galaxy s5 (chinese version) sm-g9006v and I tried to root it in order to add playstore and more to the device.
However, I used odin and a CF-autoroot file for this device.
After that the device went in a blocked white screen with a chinese log and on top left it wrote "set warranty bit recovery" and some other text.
Waited a bit since I thought it was a phase that was required for the root process to continue but it didn't do anything for a few good minutes, however i proceded to remove the battery (since the power button wasn't helping to reset the device) and now it won't start and it won't enter in a download state to use odin to eventually flash something else onto it.
Any help is appreciated as I'm kind of desperate at this point. Thank you.
Edit: if I connect it to the pc it gets in a start-up loop i believe.
Click to expand...
Click to collapse
Use Samsung KIES 3 and select "Emergency Firmware Recovery" or "Firmware Upgrade and Initialization". This worked for me even after a botched recovery flash that prevented me from going into Download mode.
Related
Hi,
Great forum with an overwhelming amount of knowledge.
Issue background: washed my phone, yep nuf said.
Rinsed with distilled water, desiccant for a week -> powers on but...
Stays at S4 logo screen, download mode works, won't go past blue "recovery booting", battery icon no animation, Kies cannot connect
100% stock never rooted all updates ATT S4
1) Read a lot
http://forum.xda-developers.com/showthread.php?t=2621279
http://forum.xda-developers.com/showthread.php?t=2258628
http://forum.xda-developers.com/showthread.php?t=2504311
http://forum.xda-developers.com/showthread.php?t=2413746
http://forum.xda-developers.com/showthread.php?t=2576329
etc...
2) Downloaded I337MK2_Full_Odin_Tar.tar.md5, Odin3.07
3) Successful completion, no errors, no change in condition
4) Repeat load, no change
5) Try recovery load i337MK2stockrecovery.tar.md5, no boot change
6) Go to AT&T Device Center, load succeeded, still stuck at S4 logo
7) Repeat with Odin3v185 passed, no change
Haven't tried anything ADB related
Any ideas to unbrick? Have not tried any PIT files, etc. just "this will work" vanilla stuff.
Can try sending to Samsung but don't mind experimenting at this point.
Thank you.
K
I dunno what is your firmware prior to bricked. ... If your firmware are MF3 or even MK2 then u can follow my thread from the first link that u posted. .... Check post#2 for guide and image guide from my thread. Either way which firmware that u coming from, this MK2.tar file should bring u back to stock 4.3 MK2 firmware easily. .....tested my self and also confirmed by others....:thumbup::thumbup: try changing usb cable, USB port or different PC (win 7) seem to worked best with ODIN. .... and make sure ONLY auto reboot and F. Reset Time are check inside ODIN
Swyped From MK2 Dark Venom SS Edition
1st sincere thanks for the reply.
I don't have clear confirmation on firmware loaded, but all OTA updates had been applied, so 100% stock and up to date as of 1/2/14. When downloading the information list shows ~knox: 0x0 if this helps.
So repeated the steps from post #2 on another computer (also Win7 x64) used drivers from new Kies install with the combined md5:
Complete - 1.POWER OFF YOUR PHONE AND GO TO DOWNLOAD/ODIN MODE ( VOLDOWN+HOME+POWER)
Complete - 2.DOWNLOAD ATTACHED ODIN BELOW AND MAKE SURE U HAVE THE LATEST DRIVER INSTALL FROM SAMSUNG KIES
Skipped - 3.IF U DOWNLOADED AND EXTRACTED I337MK2-4FILES-TAR.MD5 (FIRST RELEASED) FILES FROM OP (ORIGINAL POST) START ODIN AND FOLLOW THIS IMAGE BELOW IN ORDER WHERE EACH FILE SHOULD GO INTO ODIN SLOT....
Complete- 4.IF U DOWNLOADED AND EXTRACTED ALL-IN-ONE-1337MK2-TAR-MD5 (NEWEST RELEASED) FILES ...JUST PLACE THE MD5 FILE INTO PDA ODIN SLOT ONLY
Everything in Odin said pass, successful.
Unfortunately the result is the same. Phone reboots at end of Odin to "Recovery Booting..." Samsun Galaxy S4 logo screen. Pressing power button on the phone for a few seconds results in return to stuck "Recovery Booting..." Samsun Galaxy S4 logo screen. To be clear I just held power down for 5 second-ish and releases. Phone booted directly back to "Recovery Booting..." Without pressing power button again.
Boot to download mode and then cancel stops the recovery from trying to start so it's just stuck at the logo.
Guess I need to delve into the technical stuff a bit more to determine differences in booting between normal, recovery, and download.
Probably send it to Samsung for fix attempt. At least I had the insurance so I don't have to replace at full price, although I am thinking the waterproof Sony Sirius is a better option since I like to keep my phone so clean.
If your phone got wet, Samsung will probably just reject the warranty and you may be forced to pay full price.
http://www.samsung.com/us/support/service/warranty/SGH-I337ZWAATT
This Limited Warranty does not cover: (a) defects or damage resulting from accident, misuse, abnormal use, abnormal conditions, improper storage, exposure to liquid, moisture, dampness, sand or dirt, neglect, or unusual physical, electrical or electromechanical stresses
flykrs1 said:
1st sincere thanks for the reply.
I don't have clear confirmation on firmware loaded, but all OTA updates had been applied, so 100% stock and up to date as of 1/2/14. When downloading the information list shows ~knox: 0x0 if this helps.
So repeated the steps from post #2 on another computer (also Win7 x64) used drivers from new Kies install with the combined md5:
Complete - 1.POWER OFF YOUR PHONE AND GO TO DOWNLOAD/ODIN MODE ( VOLDOWN+HOME+POWER)
Complete - 2.DOWNLOAD ATTACHED ODIN BELOW AND MAKE SURE U HAVE THE LATEST DRIVER INSTALL FROM SAMSUNG KIES
Skipped - 3.IF U DOWNLOADED AND EXTRACTED I337MK2-4FILES-TAR.MD5 (FIRST RELEASED) FILES FROM OP (ORIGINAL POST) START ODIN AND FOLLOW THIS IMAGE BELOW IN ORDER WHERE EACH FILE SHOULD GO INTO ODIN SLOT....
Complete- 4.IF U DOWNLOADED AND EXTRACTED ALL-IN-ONE-1337MK2-TAR-MD5 (NEWEST RELEASED) FILES ...JUST PLACE THE MD5 FILE INTO PDA ODIN SLOT ONLY
Everything in Odin said pass, successful.
Unfortunately the result is the same. Phone reboots at end of Odin to "Recovery Booting..." Samsun Galaxy S4 logo screen. Pressing power button on the phone for a few seconds results in return to stuck "Recovery Booting..." Samsun Galaxy S4 logo screen. To be clear I just held power down for 5 second-ish and releases. Phone booted directly back to "Recovery Booting..." Without pressing power button again.
Boot to download mode and then cancel stops the recovery from trying to start so it's just stuck at the logo.
Guess I need to delve into the technical stuff a bit more to determine differences in booting between normal, recovery, and download.
Probably send it to Samsung for fix attempt. At least I had the insurance so I don't have to replace at full price, although I am thinking the waterproof Sony Sirius is a better option since I like to keep my phone so clean.
Click to expand...
Click to collapse
Kies can interfere with odin. Remove it. Use 4.3 stock fw for your carrier, flash with odin. Try a new cable as well, or a different usb port /computer. Once flashed with odin, boot into recovery and perform factory reset with stock recovery. Barring that, id knox is 0x0 take it to best buy for free repair.
Sent from my SGH-I337M
Hi everyone. I was attempting to update the firmware on my note 3 using the Verizon software assistant when my son unplugged the phone when it was a little more than halfway done. It's unlocked with Verizon as the original carrier, SM-900V is the model number. I've tried to master reset as well but it just turns off briefly and returns to the same screen, the only other screen I can get to is a warning telling me that downloading a custom OS can cause critical problems and to press volume down or up to continue or cancel. When I press up it says Downloading, don't turn off target but it just stays there. I'm not knowledgeable when it comes to rooting or installing custom OS and such things but I'd just like to restore it back to factory 4.4.2 which it was running previously. Can someone help me out with a relatively simple explanation as to what to do? It's much appreciated, just got this thing yesterday and I'd like to get it up and running asap. Thanks again.
Connect it to Samsung kies and perform an emergency repair.
Alternatively go to sam firmware.com and download the correct firmware you require and flash it using odin un download mode ( the screen that you saw that said downloading)
Hello fellow XDA members!
First off here is a little about my device:
* Rooted using towel root, which is a one click root(No ODIN or anything else needed)
* Android version 4.2.2, stock at&t
* Galaxy S4 SGH-I337
Yesterday my phone kept bugging me to do an OTA update, it's done this before. I always have my phone in "OTA survival mode" in my SU app. Usually i just decline it and then finally it forces me to do the OTA update, giving me no option to cancel and automatically restarting in 30 seconds. Then i just restart it and boot it normally and everything is fine(Also it doesn't ask for OTA often). Unfortunately I managed to break my recovery since the last time it did this trying to install CWM and I never got around to changing it back to stock. Now when i boot my device, no matter what mode i try to boot into it starts to boot into recovery(I see the tiny blue text). Then some tiny white loading text pops up for a split second, I believe it says "SECURE: SECURE MAGIC failure (recovery mode)" then the next line says "Set warranty Bit: recovery", then it goes to a screen that has a tiny red "SECURE FAIL: KERNEL" in the top left and a big caution in the middle of the screen, then finally right below that it says "System software not authorized by AT&T has been found on your phone" this time in a little bit larger font.
I'm pretty sure the phone is done but any help is greatly appreciated. Also on a side note i did try to boot ODIN and also KIES but none seems to work.
Also let me know if there could be any other information i could provide
Thanks in advance!
Hello guys,
A friend of mine gave me his S6EDGE+ because it didnt boot anymore after he woke up. The night before that he installed an update but the phone worked fine after that.
The phone showed this message: http://imgur.com/a/cwLyM
I thought that it was easily fixed by flashing original 7.0 firmware but as you can guess i was wrong... It keeps rebooting right after the "Samsung Galaxy S6 Edge+" screen
So i tried to flash original 6.0.1 firmware but the same result
After that i flashed 7.0 again and after that twrp 7.0 but it never booted into twrp
So i flashed android 6.0.1 and the newest twrp for 6.0.1 but it still didnt booted into recovery and i am not able to boot in recovery.
After that i tried some older versions of twrp for 6.0.1 and it sometimes gave me the error: Recovery is not seandroid enforcing. I tried the same with 7.0 and older twrp versions, same results.
I also tried to flash 5.1.1 but i couldnt flash it.
What i also tried is to flash 7.0 bootloaders and after that 7.0 firwmare and the same for 6.0.1
I'm really desperate and dont know what to do anymore..
Current status: bootloop
I can enter download mode: http://imgur.com/a/XiS6Z
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
kdogguk said:
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
Click to expand...
Click to collapse
i can see that the images aren't working, ill fix that in a sec.
Yes i used odin and downloaded everything from sammobile because ive actualy paid them for de downloadspeed
justanpotato said:
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
Click to expand...
Click to collapse
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
no, u need learn some things about Binary Vercion, ima sure u have a B3 in this moments, so , download any firmware with Binary 3, if need more infor about that, check here http://forum.gsmhosting.com/vbb/f68...combination-compatibility-w-o-errors-2189001/
ruubs said:
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
Click to expand...
Click to collapse
You've never stated the results of your stock firmware flashing, using Odin. This is key, this tells you whether the firmware was flashed correctly or not.. If you picked the wrong stock firmware to flash, Odin will show it "Failed."
If your buddy just updated firmware, then it's likely he's on the newest one, but check in SamMobile to verify if it's accurate. If shows the most current firmware was updated in January or something then he might not be on the most current one, as this shows that he's behind on updating his phone, so it's uncertain which it last updated to.
If I were you, I'd verify first whether the Odin flash passed or not, prior to attempting any custom flashing.. After Odins finished flashing in the upper right corner will either show "Pass" or "Fail," it needs to show "Pass" before you can proceed to do anything else, as this confirm whether the stock firmware flashed correctly or not.
If it doesn't Pass, you have flashed the wrong firmware. Might be good to verify with your buddy, which carrier he had originally. If you indeed have a Samsung S6 Edge+, with the larger 5.7 inch screen, the model numbers begin as so, "SM-G928x" with difference being the "x" at the end, which coincides with whichever carrier it's on, (e.g. "A" for AT&T, "T" for T-Mobile" - U.S. carriers).
It wouldn't be a bad idea to confirm whether you're using the most up to date version of Odin, either. Don't remember what that is but a quick Google search under this topic would do it.
Just for shyts and giggles, you did verify that your PC recognizes the phone, right? And that it lists under "Device Manager" correctly, as well as Odin recognizing it after you plugged it in?
If it does "Pass," it should reboot by itself into the stock firmware since prior to flashing you selected "autoreboot" and "reset time" if it doesn't reboot correctly or gets stuck on the splash screen, unplug it from the PC and manually boot it into stock recovery. Do this by first pressing the following buttons at the same time and holding them till the phone powers off, power button, home button, volume up and volume down.. After it powers off, push and hold, power button, home button and volume up, till the phone boot to stock recovery, amd of course you can let go of the buttons/keys. Then using volume buttons to select factory reset and pressing the power button to confirm the selection. After it factory resets you can then select reboot to system and it should boot normally and you've recovered the phone.
The upper left corner in Odin will show the results of the flash, there shouldn't be a reason for it not booting if it indeed shows "Pass," cuz this confirms firmware flashed correctly, if it shows "Fail" then you flashed the incorrect firmware. You'll need to locate the right one so that Odin shows "Pass," otherwise you wont ever recover your phone, regardless of anything else you find interesting to flash, bootloaders, TWRP, root, ect.. Don't flash anything else till you get the stock firmware flashed correctly. If you're unable to accomplish this then, I'd recommend calling Samsung or your carrier, is it still under warranty? My charging port broke after 2+ years, I have insurance though w/ T-Mobile, called them to see what my options were, was planning on fixing it myself to avoid the $175 insurance deductible, if I made a claim, but as it turns out, since I have insurance, the phones still under warranty and per the CSR, it will continue to hace warranty as long as I pay the $7/month insurance. Thought most warranties are 12 months but I wasn't going to correct her if she was wrong so I went ahead with it and 2 days later new phone came and I sent my broken one back! Old phone has lil scratches on the screen, couple lil dings along the sides, obviously an older phone but now I gotta new one, ita flawless!
It won't to try if this don't work out..
Good luck
Hi guys, a friend of mine asked me if i can fix her child's tablet (It is galaxy tab A 10.1'' with LTE T585.
Her problem was that she factory reset it, because her child set a pattern and forgot it. They also dont remember the password, hence FRP problem.
I tried to flash a new Official rom from Sammobile and tried to flash it via AP option, but it got stuck on about 95% at Meta-data/Fota.zip and the screen is flashing somewhat. Upon further reading i understood that i need newer Odin, hence i had to unplug the cable and start over. However, I am unable to access download menu anymore. When i press home power down and lock nothing happens, until i plug the cable in. Then Odin sees it (although the tab says Error occurred bla bla use Smart switch PC software, which does not support the tablet weirdly). But i cant flash anything like that it gets stuck at initializing.
I am open for any suggestions on how to fix this or i might have to end up buying a new tablet for her.
Thank you guys!
PS: Ive been long away from samsungs (since S5 disappointment so im not really into samsung specifics).
DjIvcho said:
Hi guys, a friend of mine asked me if i can fix her child's tablet (It is galaxy tab A 10.1'' with LTE T585.
Her problem was that she factory reset it, because her child set a pattern and forgot it. They also dont remember the password, hence FRP problem.
I tried to flash a new Official rom from Sammobile and tried to flash it via AP option, but it got stuck on about 95% at Meta-data/Fota.zip and the screen is flashing somewhat. Upon further reading i understood that i need newer Odin, hence i had to unplug the cable and start over. However, I am unable to access download menu anymore. When i press home power down and lock nothing happens, until i plug the cable in. Then Odin sees it (although the tab says Error occurred bla bla use Smart switch PC software, which does not support the tablet weirdly). But i cant flash anything like that it gets stuck at initializing.
I am open for any suggestions on how to fix this or i might have to end up buying a new tablet for her.
Thank you guys!
PS: Ive been long away from samsungs (since S5 disappointment so im not really into samsung specifics).
Click to expand...
Click to collapse
Irrespective of whatever state the tablet is in just hold in this order HOME + VOL DOWN + POWER. Hold until the screen goes blank then when you see the Samsung logo release after a few seconds.
Once in DOWNLOAD mode flash using at least odin 3.12
Tried that already but Odin was staying on initializing. Gave it to a phone mechanic and he fixed it now i need to find a way to know which Android version it has and how to bypass the frp.