So, I was messing around with Busybox on my rooted T350 RUNNING 6.0.1, and I went into scripts, and ran the script to reboot into recovery and I ran it as root. It rebooted fine into recovery. So once I was done in TWRP, I tried to reboot back into my rom, which is stock by the way, and on the top left it won't change from set warranty bit: recovery to set warranty bit: kernel. So I can't get back onto my rom. Any ideas? If possible I really don't want to flash my stock unrooted room, just to read obtain root and have to re-download everything. Thanks in advance
Update - I flashed my stock backup. Still no change to set warranty bit. My tablet is pretty much bricked at this point in time.
Anybody got any ideas? I'm kind of dead in the water.
Solved it myself. Thanks for all the feedback. So, in case anyone ever has this issue again, these are the steps I took to fix being stuck in "set warranty bit: recovery".
1. Connect your tablet to your computer, reboot into download mode, run Odin.
2. Go ahead and check AP and select file twrp_3.0.2-1_sm-t350_mm_9816.tar
3. Flash it, and attempt to get back into TWRP.
If you still want a rooted device:
1. Connect to Odin, reboot to download mode
2. Select AP, select CF-Auto-Root-gt58wifi-gt58wifixx-smt350.tar.md5
3. Flash it, have root.
Somehow, rebooting into recovery via busybox root script will put you in a recovery boot loop. Reflashing TWRP was the only way I could breath life back into my device. I also had a backup of my stock unmodified ROM to restore via twrp, so that is why there aren't any steps mentioned with flashing that.
Hey are u on 7.1.1 or 6.0.1
I am currently running 6.0.1
you saved me
4 months on a shelf and you helped me bring it back to life ..thank you so much man
Related
Hello!
I've flashed a stock ROM on my Samsung Galaxy S5 (SM-G900F) using ODIN 3.07 and now the phone is bootlooping. I guess It's because I need to wipe data and cache partitions and here's the problem.
My home button is not working, so I can't boot in recovery mode. Adb does NOT recognize my device. I'm only able to access download mode using a JIG.
So, is there any way to wipe those partitions or to be able to access recovery using ODIN?
Thanks in advance for your help!
That is a challenging situation! I'd try flashing the stock ROM once more, just on top of the one you already did using Odin and see if it boots this time.
If it didn't, see if Samsung kies would recognize your phone on download mode and get kies to flash the proper stock rom because I know kies does a full wipe before flashing automatically every time.
Yea, you shouldn't need to wipe anything if you use the correct tar in Odin, it should do it automatically. I would try again as stated above. Are you sure you have the correct tar file?
Thank you so much!!
The problem is that I was trying to flash an older firmware to use Towelroot. I've flashed the same firmware and now it's working again!
Now, I really need to root because I need virtual keys (hardware ones don't work) and i have to edit build.prop file.
What's the easiest way to root on a Lollipop firmware? I don't care about Knox and warranty void.
Also, I already tried CF-Auto Root but when the phone rebooted It gave me this message: "RECOVERY IS NOT SEANDROID ENFORCING" and it didn't start anymore, that's why I needed to flash the stock firmware again.
EDIT: Nevermind. I flashed TWRP using Odin and then I flashed SuperSU in the recovery. I've booted in the recovery using "adb reboot recovery". Thanks again!
Glad you got it working!
New to the S4 - did a search and could not find a similar problem as mine...
My friend gave me his S4 and told me it is rooted - which it is. However, there seems to be no recovery on the phone. When I try power-vol up-home, I get the blue recovery note at the top, but then the phone just continues to boot into the system (MF9). I used Odin to go back to stock and then attempted to boot into recovery - no luck. I rooted the phone again via CF Auto Root and tried to install a custom recovery via Odin and TWRP Manager - still no luck. Anyone have any ideas/suggestions? I appreciate the help.
Bumping this up to the top for one more run through...thanks everyone.
Sixbowmans said:
Bumping this up to the top for one more run through...thanks everyone.
Click to expand...
Click to collapse
Maybe go in to Odin mode and flash latest stock making sure to unchecked the auto reboot option. When it finishes flashing unplug and pull the battery, let it boot it'll take a while (took mine about 10-15 minutes). You'll then be on latest stock with latest bootloader and recovery. From there you can go back to Odin mode and flash TWRP. Once again making sure to not auto reboot.
Just to be safe back up apps and msic and picture etc on samsung kies and then do a full recovery delete everything and install the latest firmware then try cf auto root again or if you have trouble with that rhen use kingoroot and then flash twrp or phils recovory and get a rom. If that doesnt work just get cyanogenmod installer which installs root and a stock rom.
Sent from my SM-N910V using XDA Free mobile app
mattzeller said:
Maybe go in to Odin mode and flash latest stock making sure to unchecked the auto reboot option. When it finishes flashing unplug and pull the battery, let it boot it'll take a while (took mine about 10-15 minutes). You'll then be on latest stock with latest bootloader and recovery. From there you can go back to Odin mode and flash TWRP. Once again making sure to not auto reboot.
Click to expand...
Click to collapse
Thanks mattzeller. Your suggestion took me back to my Evo days. I took out the sd card, flashed with Odin, pulled the battery, rebooted the system, and then was also able to boot into recovery.
Note 4 Can't Install TWRP
Hello,
I'm in the process of installing a recovery mod rooting my root 4.
When I try to install TWRP using Odin, I don't get any error messages, it says PASS, everything looks okay.
When I try to boot into recovery, it shows the android bot with the message (installing system updates) under it, and then it loads the default samsung recovery instead of TWRP.
I made sure that I have the correct version of TWRP downloaded (N910H Exynos version, named twrp-2.8.7.0-treltexx.img.tar). I aslo ran Odin as administrator, but it's still not working, the knox counter was tripped however.
Any help would be greatly appreciated, because I can't proceed with the rooting process without TWRP.
Did you root your phone before flashing the recovery?
EDIT: By the way, when you have flashed the recovery, you MUST immediately boot into recovery, or else the stock rom will overwrite it with the default recovery.
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
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.