Welcome guys,
I have Galaxy S4 and I wanted to install Custom ROM. Unfortunately when I installed TWRP (the newest build), my phone displays "Set warranty bit: kernel" and then it boots into Recovery Mode (twrp works fine), but stock ROM doesn't boot. I don't know how to deal with it. Will custom ROM install fix that problem? I don't want to brick it.
I have access to download mode, TWRP (as I said before, when I turn phone on, it boots into TWRP instantly), but unfortunately ODIN doesn't recognize phone at all.
Please help :crying:
Does the computer recognize the phone?
After installing, did you select the option to allow changes to the internal memory?
Tried different USB cables and USB ports?
If you get the phone recognized by Odin, I suggest flashing a stock ROM via Odin and checking the phone to ensure complete functionality. Once you know the phone is working on a stock ROM, maybe start with an older version of TWRP such as 2.87.
Flashing a custom recovery should not prevent the phone from booting a stock ROM.
audit13 said:
Does the computer recognize the phone?
After installing, did you select the option to allow changes to the internal memory?
Tried different USB cables and USB ports?
If you get the phone recognized by Odin, I suggest flashing a stock ROM via Odin and checking the phone to ensure complete functionality. Once you know the phone is working on a stock ROM, maybe start with an older version of TWRP such as 2.87.
Flashing a custom recovery should not prevent the phone from booting a stock ROM.
Click to expand...
Click to collapse
I'm such an idiot. When knox is tripped you cant run stock ROM, so basically I just installed LineageOS and it works hah
Tripping knox does not prevent a phone from running a stock ROM.
audit13 said:
Tripping knox does not prevent a phone from running a stock ROM.
Click to expand...
Click to collapse
So it's strange though. I couldnt boot stock ROM and the only thing I had to do was install a custom one. Anyway, thanks for the answer
I've flashed TWRP to a number of Samsung phones which cause Knox to trip and the warranty bit to change from 0x0 to 0x1. Despite this, I have been able to flash and use stock ROMs with a tripped Knox indicator.
Maybe the phone needed a factory reset using the stock recovery after being flashed with Odin?
audit13 said:
I've flashed TWRP to a number of Samsung phones which cause Knox to trip and the warranty bit to change from 0x0 to 0x1. Despite this, I have been able to flash and use stock ROMs with a tripped Knox indicator.
Maybe the phone needed a factory reset using the stock recovery after being flashed with Odin?
Click to expand...
Click to collapse
Aaaand here we got the problem. I tried to install twrp many times and unfortunately the stock one stopped running (dont ask, i dont know how it happened). Despite this everything worked but I wanted to install custom ROM and then that problem happened. It was just the lack (??) of stock ROM or knox blocked the availability to boot it.
Oh, completely forgot. I installed TWRP by LineageOS' tutorial on their page
It all worked out in the end which is the important part.
Thanks for sharing your solution.
Related
guys,
My I9505 has a hardware problem: the VOL DOWN is unresponsive.
That's a nasty problem, because rebooting the phone gives a lot of problems (warnings about a custom rom, and then nothing works anymore)
So I'd like to return it, but have to restore the phone for warranty.
I managed to flash latest stock MH8.
Here are my questions:
1. before, I've flashed autoroot - does that make the flashcounter go up?
2. before, I've flashed philz recovery - does that make the flashcounter go up?
3. I've flashed the new stock firmware, but still see a clockworkmod folder. can I safely remove that?
4. are there other folders I've to remove to NOT void my warranty?
5. is it necessary/safe to use triangle away on MH8 with the new bootloader?
thanks for any insights!
mailman
mailman123 said:
guys,
My I9505 has a hardware problem: the VOL DOWN is unresponsive.
That's a nasty problem, because rebooting the phone gives a lot of problems (warnings about a custom rom, and then nothing works anymore)
So I'd like to return it, but have to restore the phone for warranty.
I managed to flash latest stock MH8.
Here are my questions:
1. before, I've flashed autoroot - does that make the flashcounter go up?
2. before, I've flashed philz recovery - does that make the flashcounter go up?
3. I've flashed the new stock firmware, but still see a clockworkmod folder. can I safely remove that?
4. are there other folders I've to remove to NOT void my warranty?
5. is it necessary/safe to use triangle away on MH8 with the new bootloader?
thanks for any insights!
mailman
Click to expand...
Click to collapse
Be VERY VERY careful if you're running the new knox firmware that you don't trip the eFuse and change KNOX Warranty void status.
If you have flashed stock firmware MH8 in Odin I would simply do a factory reset in the STOCK recovery and wipe everything that way and send to repair centre.
Do not flash ANYTHING custom or otherwise, even older Stock firmware in Odin.
If you do you will trip the eFuse, your KNOX warranty status will change and you'll be f***ed mate.
Obagleyfreer said:
Be VERY VERY careful if you're running the new knox firmware that you don't trip the eFuse and change KNOX Warranty void status.
If you have flashed stock firmware MH8 in Odin I would simply do a factory reset in the STOCK recovery and wipe everything that way and send to repair centre.
Do not flash ANYTHING custom or otherwise, even older Stock firmware in Odin.
If you do you will trip the eFuse, your KNOX warranty status will change and you'll be f***ed mate.
Click to expand...
Click to collapse
Thanks, that's very good advice. will keep it in mind.
Do you know the answer to my questions about the flashcounter going up by flashing recoveries in stead of custom roms?
thanks,
mailman
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
wethestill said:
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
Click to expand...
Click to collapse
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
wethestill said:
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
Click to expand...
Click to collapse
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Gage_Hero said:
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Click to expand...
Click to collapse
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
wethestill said:
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
Click to expand...
Click to collapse
If your coming from 4.3 there are a number of good roms... unfortunately they are all around 1.2 to 1.4 GB so if you have a slow connection it will take a while... I run Danvh's 4.4 http://forum.xda-developers.com/showthread.php?t=2537495 , there is also this one that people seem to like but I haven't tried it.... http://forum.xda-developers.com/showthread.php?t=2375180 you will need a custom recovery.... both of these suggest twrp.... I flashed with 2.6... 2.7 is out now and I don't know how it reacts but you will need a custom revovery to flash the zip file....
I guess the issue is you have to restore to stock via odin but you don't know what version bootloader you have? Guess you'll have to use samsung tool which will probably install knox?
Can you install custom recovery via odin?
Try with the new 4.4 files
sent from my mobile device
Knox is already tripped. I'd go into recovery, do a factory restore again and then plug it into the computer and do a restore with Kies.
Sent from my SGH-I337M using Tapatalk
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 a new Samsung S4 (i9505) (yep - new with waranty, apparently). The phone came with Lollipop but I downgraded to Kitkat (4.4.2) to root without tripping Knox.
I have successfully rooted (after several soft bricks) and my Knox counter remains at 0x0 - but I cannot boot to recovery (the phone says "recovery booting..." in blue small text at the top but then goes to a normal boot with boot loop). I can boot in to the normal mode, and can boot to safe mode, and can boot to download mode - but not to recovery. And cannot factory reset the phone (from settings - the procedure just leaves the phone as it is). I have tried (successfully) to flash the Lollipop bootloader, and have tried (unsuccessfully) to flash the image file extracted from the stock lollipop ROM (extracted recovery.img, used 7zip to create a tar file, and tried flashing as AP with Odin 3.09 but it fails to write the file)... I also tried the OTA update back to Lollipop (using the settings, update option on the phone) but that too failed.
The phone seems to work but I just cannot get in to recovery mode (and cannot factory reset the phone). I am using the original usb cable and a usb port directly connected to the mother board (and have successfully flashed other components). Any suggestions as to how to re-enable or restore the recovery (without tripping Knox warranty counter)?
Many thanks for any help
Flash the whole firmware with Odin.
Custom recovery is a no-go as it will trip Knox.
GDReaper said:
Flash the whole firmware with Odin.
Custom recovery is a no-go as it will trip Knox.
Click to expand...
Click to collapse
Thanks for that.
I was leaving a complete reflash to Lollipop (with Odin) as a last resort - as this would cause me to lose root. However, yesterday I chose the backup function on FlashFire to backup (to the external SD card) the phone with Kitkat and root and... following the backup, all apps (system and user) fail on boot so I have no option but to reflash anyway (worked without issue). Not sure what happened with FireFlash - all I did was to select backup - but is must have affected the phone in some way... I guess it is incompatible with the S4 or Kitkat (or both).
I am still confused: what will have prevented the phone from booting to recovery with the Kitkat image (and prevented me from reflashing the stock Lollipop recovery via Odin)? And what is the issue with FireFlash (I can not understand why taking a backup should cause a problem when rebooting the phone).
I will start again trying to gain root without tripping Knox (downgrading to Kitkat, using TR to root, then, hopefully, upgrading via Mobile Odin with everroot)...
Thanks again for your help.
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
GDReaper said:
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
Click to expand...
Click to collapse
Thanks again for your response. When I tried removing Knox with the Knox removal script in Mobile Odin having downgraded my device to Kitkat, I got a soft brick which did take a while to fix (but did get fixed eventually). I had thought of perhaps trying to upgrade from rooted Kitkat to Lollipop using FireFlash but was a bit disconcerted at the way it crashed my device when I only tried backing up the phone (and not flashing anything at all) using it.
Do you know whether the issue I had with FireFlash is indicative of FireFlash being incompatible with my device or is the symptom I had just something that may randomly occur (ie is there any point trying to use FireFlash upgrade from rooted but not Knoz tripped 4.4.2 to rooted and not Knox tripped 5.01)?
Many thanks for all your help and best wishes, Boris.
bprtzel said:
Thanks again for your response. When I tried removing Knox with the Knox removal script in Mobile Odin having downgraded my device to Kitkat, I got a soft brick which did take a while to fix (but did get fixed eventually). I had thought of perhaps trying to upgrade from rooted Kitkat to Lollipop using FireFlash but was a bit disconcerted at the way it crashed my device when I only tried backing up the phone (and not flashing anything at all) using it.
Do you know whether the issue I had with FireFlash is indicative of FireFlash being incompatible with my device or is the symptom I had just something that may randomly occur (ie is there any point trying to use FireFlash upgrade from rooted but not Knoz tripped 4.4.2 to rooted and not Knox tripped 5.01)?
Many thanks for all your help and best wishes, Boris.
Click to expand...
Click to collapse
Sorry - FlashFire not FireFlash!
Mobile Odin and bricked phone?
GDReaper said:
FlashFire is still in beta. Such problems can happen.
Also, be very careful with Mobile Odin. I bricked my device using it.
Mobile Odin is outdated, I don't know if it works on anything above Android 4.3.
Click to expand...
Click to collapse
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
bprtzel said:
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
Click to expand...
Click to collapse
I tried to update my modem and bootloader with it. I also was on a custom ROM.
bprtzel said:
Hi GDReaper
Can you say anymore about bricking your phone with Mobile Odin? The rooting without tripping Knox recipe was published on XDA (downgrade to 4.4.2 Kitkat, root with TR, remove Knox with Knox removal script and Mobile Odin (this doesn't work on my device), then upgrade to 5.01 with Mobile Odin with root injection, factory resetting and reflashing the Boot Loader - and off you go). This was published over a year ago but hopefully still works... If this is the type of operation that bricked your phone however, I will stay very clear of it...
Many thanks and best wishes, Boris.
Click to expand...
Click to collapse
Just to say I finally got my phone to Lollipop (5.01) rooted with Knox guarantee void remaining at 0x0.
I downgraded (again) to 4.4.2 with Odin, installed the GF1 kernel, used towel root (my wifi was still working though it would not remember the wifi passwords), the used FireFlash to upgrade back to stock 5.01 plus SU beta.zip as OTA/ZIP. All worked great - except I now cannot get the wifi to switch on. Used Odin to load the Lollipop BL and also Lollipop kernel, and did a factory reset for good measure too but still no wifi... (can't switch the switch to on). Guess I will try the GSM modem to just to see if that helps (unless anyone has other suggestions)...
Managed to get the phone rooted, but then the System UI wouldn't load after a couple restarts. Used the phone's recovery to reload the OS, but after one restart, the phone got locked in a bootloop. So I tried to go back to stock first with Kies, but my USB cable popped off which softbricked the phone (yay). Download mode still works, so I tried to flash the stock ROM in Odin. Odin sees my phone just fine, but when it goes to flash the ROM it gets stuck at like 1%. Just tried again in Kies but still nothing. Here's what comes up on screen
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224, 1440]
How screwed am I?
What error are you getting in Odin? Using original Samsung USB cable?
audit13 said:
What error are you getting in Odin? Using original Samsung USB cable?
Click to expand...
Click to collapse
No, no error of any kind. Just that it sets up the transfer, then that's it. I left the phone for hours and the progress bar didn't budge. Also, no, I don't have that original cable anymore.
Tried different USB cables and USB ports?
audit13 said:
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Okay, took me a bit to go out to the Samsung store to get the cheapest cable they had. But I'll be damned if it didn't work. Okay, so now that the phone is back to normal, does that mean I can do the same thing in Odin to get the OS I actually want to get loaded?
You want a custom rom? If yes, flash the tar version if twrp for the i9505, then flash roms made for the 9505 and i337.
audit13 said:
You want a custom rom? If yes, flash the tar version if twrp for the i9505, then flash roms made for the 9505 and i337.
Click to expand...
Click to collapse
Okay, twrp's site has a version specifically for the jfltecan, which everywhere I've looked up says is the phone I have, the i337m. Why do you recommend the one for the i9505?
If you flash twrp for the jfltecan, you'll run into errors when twrp runs the 9505 ROM's updater script. With the i9505 version of twrp, no error.
audit13 said:
If you flash twrp for the jfltecan, you'll run into errors when twrp runs the 9505 ROM's updater script. With the i9505 version of twrp, no error.
Click to expand...
Click to collapse
Okay, then. A final question then. The phone is already as if I just bought it. All my data was lost. So can I use Odin to install a new OS first, and then install TWRP? Because trying to install TWRP first is what started my troubles.
If you intend to flash a custom ROM, just flash TWRP and then flash the custom ROM.
Not sure how you tried to install TWRP but I have not had any trouble flashing TWRP via Odin. No need to root the phone before flashing TWRP.
audit13 said:
If you intend to flash a custom ROM, just flash TWRP and then flash the custom ROM.
Not sure how you tried to install TWRP but I have not had any trouble flashing TWRP via Odin. No need to root the phone before flashing TWRP.
Click to expand...
Click to collapse
Using the TWRP Manager app, which did require rooting. And, uh, sorry to keep bugging you. There is no i9505 on the TWRP site. Just i9500 and i9506.
edit: Ah, I assume you meant the TWRP file for the jfltexx?
I have never used the TWRP manager to install. I always use either fastboot commands for non-Samsung phone and Odin for Samsung phones.
https://dl.twrp.me/jfltexx/