My stock Note 3 (SM-N900W8) running Lollipop, suddenly showed Set Warranty Bit: kernel. It was not rooted, no custom ROMs, nothing done to it at all. My only input into causing this was reinserting the battery - it then booted up into this error. Ran flawlessly until it didn't. I can not get into recovery. The only thing I can do is get to the downloading screen.
To that end, I've downloaded the Bell ROM for SM-N900W8 android 5.0 using latest ODIN (3.13.1). ODIN shows pass but it boots back into recovery booting Set Warranty Bit: recovery error. I tried a recovery .tar file too to reset the recovery file but no luck there either. Error is still the same (i.e. Set Warranty Bit: recovery) which is showing now...
Nothing has worked using ODIN. I don't know if this is a hard or soft brick?
{EDIT} Obviously I am VERY new to this. I HAVE read everything about how to fix this and I've tried many many times with ODIN downloads. Also tried a TWRP file, and so on. Many, many hours later I have made no progress.
I just need one person to point me in the right direction!!!
Would my next step be to use an SD card with an image file?
ANY help appreciated.
Related
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
gr8wing said:
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
Click to expand...
Click to collapse
amazing how difficult people make things.. stock recovery will NOT flash custom roms.. if you are on fresh ni2 just odin the ncg kernal in odin, root, install SS and then odin ni2 kernal back.. now with ss installed, download the ROM you want and flash rom.zip in ss and the kernal for it if necessary..
Every custom rom on here is already knox free. Id recommend not trying to remove knox yourself again or else youll screw it up again from the sounds of it.. leave it to the devs to remove it lol.
On a side note, a brick is a phone that doesnt boot at all.. meaning it sits on a black screen and NOTHING at all boots. If you can get into recovery or dl mode then you most likely do not have a hard brick
elliwigy said:
amazing how difficult people make things.. stock recovery will NOT flash custom roms.. if you are on fresh ni2 just odin the ncg kernal in odin, root, install SS and then odin ni2 kernal back.. now with ss installed, download the ROM you want and flash rom.zip in ss and the kernal for it if necessary..
Every custom rom on here is already knox free. Id recommend not trying to remove knox yourself again or else youll screw it up again from the sounds of it.. leave it to the devs to remove it lol.
On a side note, a brick is a phone that doesnt boot at all.. meaning it sits on a black screen and NOTHING at all boots. If you can get into recovery or dl mode then you most likely do not have a hard brick
Click to expand...
Click to collapse
The issue I have been having is the /dev/uinput. I thought it was because of knox, but now I see it's more than that and nobody has made a work around yet. I may be mistaken, but I think I don't have a chance with the uinput.
gr8wing said:
The issue I have been having is the /dev/uinput. I thought it was because of knox, but now I see it's more than that and nobody has made a work around yet. I may be mistaken, but I think I don't have a chance with the uinput.
Click to expand...
Click to collapse
Youre doing too much.. supersu disables knox and uninstaling anything knox related is all you can do.. messing around with stuff you dont know about you WILL end up bricking your phone
gr8wing said:
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
Click to expand...
Click to collapse
Where can I download the multi cert file?
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_ user_low_ship_MULTI_CERT.tar.md5
I have encountered the exact same problem.
Thanks.
robertb9657 said:
Where can I download the multi cert file?
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_ user_low_ship_MULTI_CERT.tar.md5
I have encountered the exact same problem.
Thanks.
Click to expand...
Click to collapse
Here you go!
https://www.androidfilehost.com/?fid=23622183712474060
Tulsadiver and gr8wing you guys are life savers! Thanks so much! I "ODINed" the firmware only, and then the modem only. after the phone downloaded each, it did not get past boot either time, but I was calm and hopeful. I odined the multi cert file and although it took a lot longer than I thought it would, it worked to perfection and my phone is fully functional and back to where it was two days ago.
I had NI2 rooted, then accidentally did the NK2 OTA update, which lost root. I finally got around to rerooting and decided to get rooted lollipop. I now have changed course and will sit happily with rooted NK2 kitkat.
Thanks!
Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet
HI, I have tried to root my S5 900I but failed badly, have done other phones in the past but somehow stuffed this.
The phone is stuck on downloading screen and cannot do normal boot.
I Started with flashing "recovery.tar.md5" 1st which passed in Odin but phone stuck on downloading screen, then I went into recovery and tried reset and flash CF Auto Root but still not working.
Then flashed twrp.kit.tar and still no normal boot but I can get into recovery Team Win, have tried numerous wipes and installing more CF Auto Root's and also tried flashing Miui Rom.
I believe I have screwed up the stock rom and don't know what to do next.
appreciate any help
brendy79 said:
HI, I have tried to root my S5 900I but failed badly, have done other phones in the past but somehow stuffed this.
The phone is stuck on downloading screen and cannot do normal boot.
I Started with flashing "recovery.tar.md5" 1st which passed in Odin but phone stuck on downloading screen, then I went into recovery and tried reset and flash CF Auto Root but still not working.
Then flashed twrp.kit.tar and still no normal boot but I can get into recovery Team Win, have tried numerous wipes and installing more CF Auto Root's and also tried flashing Miui Rom.
I believe I have screwed up the stock rom and don't know what to do next.
appreciate any help
Click to expand...
Click to collapse
Same happened to my wife's Galaxy Grand Prime months ago; stuck at downloading mode after rooting and installing TWRP recovery. The problem was with the version of TWRP recovery I was installing. Looks like I was installing the wrong one (although the website I downloaded it from states that it's the correct one for the device model). I tried different versions from different websites and was about to wipe everything and flash the stock rom but finally I got the correct one and that fixed the problem. Hope that helps.
iSergiwa said:
Same happened to my wife's Galaxy Grand Prime months ago; stuck at downloading mode after rooting and installing TWRP recovery. The problem was with the version of TWRP recovery I was installing. Looks like I was installing the wrong one (although the website I downloaded it from states that it's the correct one for the device model). I tried different versions from different websites and was about to wipe everything and flash the stock rom but finally I got the correct one and that fixed the problem. Hope that helps.
Click to expand...
Click to collapse
Thanks, I'll keep trying different TWRP, have tries so many but have changed the outcome yet
Hello everyone. One of the ladies I look up to as a mother gave me her broken s4 this morning. It was in a boot loop, and needed to have the full software flashed again. I downloaded OK3 from sammobile and successfully flashed it using Odin 3.11. I then rebooted and flashed CF Autoroot in Odin, rebooted and tried to enter recovery mode. I would get 3 lines of info that left the screen really fast, then the screen was blank for 10 seconds, then it vibrates and reboots into the normal rom. So I went back to Odin and flashed TWRP 3.0.2-0-jftespr.img.tar (unchecking the options for auto reboot, re-partition, f. reset time) and the log says suceed 1/failed 0, I get a green pass and when I try to reboot into recovery I get the seandroid message. So the phone knows I have a non-standard recovery...still after that message I get the same blank screen, 10 second delay, and then vibrate and reboot to the rom. I tried reflashing the stock OK3 and the seandroid message goes away, but recovery mode still does not work for me Other than this recovery issue, the phone appears to work fine and it even downloaded an OTA (which I have not installed.) Any suggestions?
I would try flashing TWRP with a different version of Odin. I recently needed to reflash recently. I had a similar problem. Tried Odion 10.7. Worked fine. You could also install the Flashify app and install your recovery with that.
spaldingsmails said:
I would try flashing TWRP with a different version of Odin. I recently needed to reflash recently. I had a similar problem. Tried Odion 10.7. Worked fine. You could also install the Flashify app and install your recovery with that.
Click to expand...
Click to collapse
Thanks for your suggestions, I will try and let you know the outcome. Of course now, I have the problem with the wifi not turning on...which is only harder to fix without a recovery to boot into. Any thoughts on this new wrinkle?
spaldingsmails said:
I would try flashing TWRP with a different version of Odin. I recently needed to reflash recently. I had a similar problem. Tried Odion 10.7. Worked fine. You could also install the Flashify app and install your recovery with that.
Click to expand...
Click to collapse
Thanks for your suggestion! I tried flashing using odin 3.09 and the white samsung usb cable, and I finally have a recovery! Do you happen to know how to fix the wifi?
No idea on the wifi. That is way over my head.
angel4b said:
Hello everyone. One of the ladies I look up to as a mother gave me her broken s4 this morning. It was in a boot loop, and needed to have the full software flashed again. I downloaded OK3 from sammobile and successfully flashed it using Odin 3.11. I then rebooted and flashed CF Autoroot in Odin, rebooted and tried to enter recovery mode. I would get 3 lines of info that left the screen really fast, then the screen was blank for 10 seconds, then it vibrates and reboots into the normal rom. So I went back to Odin and flashed TWRP 3.0.2-0-jftespr.img.tar (unchecking the options for auto reboot, re-partition, f. reset time) and the log says suceed 1/failed 0, I get a green pass and when I try to reboot into recovery I get the seandroid message. So the phone knows I have a non-standard recovery...still after that message I get the same blank screen, 10 second delay, and then vibrate and reboot to the rom. I tried reflashing the stock OK3 and the seandroid message goes away, but recovery mode still does not work for me Other than this recovery issue, the phone appears to work fine and it even downloaded an OTA (which I have not installed.) Any suggestions?
Click to expand...
Click to collapse
I would suggest you flash TWRP in a different version.
Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
zzThrain is right -- I wouldn't risk flashing custom ROMs at this stage, especially because many contain new bootloaders or other stuff that might make this even worse for you. Just pick up the relevant Samsung stock ROM file (from, for example, SamMobile) and see if it boots normally again. Once it does, re-do the process *after checking all MD5s of the files you used* -- I, too, have had it happen before that a download went corrupted and I flashed it. If all is well, get into Download Mode and let Odin rip.
rixon.d9 said:
Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Click to expand...
Click to collapse
Go to recovery mode & transfer rom to phone using pc. wipe cache, delvikcache, data only. No need to wipe internal sd. Install rom & reboot.
if you phone goes to recovery or download mode, no need to worry. If it doesn't go to neither recovery nor download mode, them your phone might have probably bricked.
It's my pleasure to help you if you still facing this problem
zzThrain said:
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
Click to expand...
Click to collapse
Hi
I tried flashing stock rom from sammobile. I could find for SM-935FD hence downloaded SM-935F.
It got stuck at 90% showing System in ODIN.
From the ZIP file which is the file that needs to be flashed among below ? I tried AP.
AP_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship_meta.tar
BL_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship.tar
CP_G935FXXU2DRAG_CL648265_QB8691891_SIGNED.tar
CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
HOME_CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
Now when I try again it immediately shows FAIL. Am i Flashing the right stock rom ?
It Worked. Thanks to all who helped.
I wasn't running ODIN as Admin and also was using an slightly older version V3.10.7.