I have a tmobile gs5 that I tried rooting with cf root. I went into odin it detected my phone and I ran the .tar file under ap even though the directions said hit pda but there is no pda. Everything looked good and odin said pass. But my phone was stuck in a boot loop and read in yellow set warranty bit kernel. So I cleared the cache and the boot loop was gone and the phone works fine. But every time I reboot the yellow error is still there. I tried to odin again and the same thing boot loop reset cache all is good yellow error is still there. What happened? And how can I get root? I have used odin on my gs3 and no problem. I'm lost right now. Thanks ahead for any replys
Sent from my SM-G900T using XDA Free mobile app
@dpshptl You should just install TWRP with Odin and use TWRP to flash supersu zip, that's more or less what cf auto-root is doing anyway. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file.
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.
thisisapoorusernamechoice said:
@dpshptl You should just install TWRP with Odin and use TWRP to flash supersu zip, that's more or less what cf auto-root is doing anyway. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file.
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.
Click to expand...
Click to collapse
I tried this method. But I can't uncheck auto reboot. All of the choices are shaded and you can't check or uncheck any boxes. Should I try a different version of odin? I can't believe im having so much problems rooting a samsung.
Sent from my SM-G900T using XDA Free mobile app
dpshptl said:
I tried this method. But I can't uncheck auto reboot. All of the choices are shaded and you can't check or uncheck any boxes. Should I try a different version of odin? I can't believe im having so much problems rooting a samsung.
Click to expand...
Click to collapse
Try Odin v3.09 and try this version of the supersu zip
What do I do
So do I take out the battery after Odin and then reboot to twrp
This guy needs help said:
So do I take out the battery after Odin and then reboot to twrp
Click to expand...
Click to collapse
You can, or just hold down home, vol+, and power when Odin is done (status bar is full)
@dpshptl try twrp-2.8.6.0-klte.tar or twrp-2.8.7.0-klte.img.tar and this supersu zip
thisisapoorusernamechoice said:
Try Odin v3.09 and try this version of the supersu zip
Click to expand...
Click to collapse
TWRP got installed and so did supersu but on reboot phone is stuck on the samsung screen for over 25 mins. So I went back into recovery and wiped cache but that did not do anything either. Whats my options? I hope I dont have to do a factory reset and wipe everything.
What do I do
I was on twrp then I flashed supersu but I keep getting set warranty bit kernel message
This guy needs help said:
I was on twrp then I flashed supersu but I keep getting set warranty bit kernel message
Click to expand...
Click to collapse
Even though you hijacked my thread ill still help you.
I have the same error and i think its from the knox security being tripped but i could be wrong. did your phone boot up? after supersu install?
dpshptl said:
Even though you hijacked my thread ill still help you.
I have the same error and i think its from the knox security being tripped but i could be wrong. did your phone boot up? after supersu install?
Click to expand...
Click to collapse
No I had to reflash the stock rom, thanks for helping
This guy needs help said:
No I had to reflash the stock rom, thanks for helping
Click to expand...
Click to collapse
Apparently I got the set warranty bit kernel message after I flashed twrp
Related
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
peshmann said:
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
Click to expand...
Click to collapse
Sorry to persist, but has anyone got any suggestions on how to fix this? I'm on Jeboo kernel v1.2, stock JB firmware.
Thanks
Same problem for me, I updated the last version of SU and try to update binary choossing cmw/trwp. Now I have a bootlopp. onece it started few seconds after the phone reboot again and again.
peshmann said:
Sorry to persist, but has anyone got any suggestions on how to fix this? I'm on Jeboo kernel v1.2, stock JB firmware.
Thanks
Click to expand...
Click to collapse
Same problem for me. In download mode I flashed a stock jb rom, siyah kernel, then I restored the backup from cwm.
Sent from my GT-I9100 using xda app-developers app
chrisXL said:
Same problem for me. In download mode I flashed a stock jb rom, siyah kernel, then I restored the backup from cwm.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
After a few hours of struggling, I managed to get my phone back up and running.
All I did was flash the kernel with a Stock one eg. Philz (as I have stock JB firmware). Once flashed my phone booted up.
However I do have a issue with the SD card now, apps which were installed on my SD card were all greyed out even though I can access the data such as music and films off the card. Slightly strange. I did try mounting and unmounting, as well as reboot and that didn't help.
Considering downloading the apps again and simply moving to SD card and see if that works rather than an uninstall and reinstall.
SuperSU 1.86 binary update
Hi, i using HTC ONE with ARHD31.6 stock kernel. Also i have encountered bootloop issue after i did a update for superSU from v1.8 to v1.86. Tried both options and it stills resulted to bootloop. So far havent been able to find a solution for this so other then restored back to my previous backup.
Hi,
I have a rooted galaxy S2 on stock with the SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM (as that's my recovery tool). My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help? I have a feeling I would need to flash the kernel but am not really sure what the best way to fix this is. If possible I would like to keep all my data intact.
Any help is appreciated
Also apologies if I have posted this to the wrong section.
Thanks
Click to expand...
Click to collapse
I had the same problem (bootloop issue) on my Samsung win I8552 and I solved that reinstalling CWM trought ODIN :
1. First be sure USB Debugging is checked in ur device ( Settings>Developer Options>USB Debugging )
2. Extract the Odin file from the zip.
3. Open Odin3 (Run As Administrator).
4. Put your device in download mode. To do so, press Volume Down And Home And Power Button all together and when it vibrates release
Power Button but keep pressing left ones. You should have a triangle with an android janitor while it's saying downloading ..
VOL UP TO CONTINUE...
5. Now connect USB to PC ,you should see a blue rectangle with COM:xx and saying Added. It means that your device is ready to be flashed!
6. Go into the PDA section and select your .tar file.(CWM Recovery)
7. Dont check any option (F.reset time and Auto reboot are checked by default) So just uncheck Auto Reboot.
8. Now click Start.
9. When it's finished, it should say that "Res OK" in Odin..
10. Now remove ur USB and remove ur battery and put it back and power on your phone.
It must work now!
:highfive:
SuperSU Binary Update Boot problem
I have a rooted galaxy S2 using jeboo kernel and SuperSU application. I updated the SuperSU application today and when I opened it, it advised me to update the binary. I selected the option to update the binary via CWM. My phone then tried to reboot but is now stuck on the splash screen, I have access to ODIN mode which currently says CUSTOM BINARY DOWNLOAD: Yes (1 counts) but no access to CWM.
Please could anyone help
Try to reinstall a kernel via odin then reboot.
Sent from my GT-I9100 using XDA Free mobile app
I know this is an old topic, but the recent supersu update caused my phone to get stuck during booting:
The new update came over the playstore, it asked me to update the app. After that it said that the Super User Binary needs to be updated. I chose the option that does the update process in the CWM recovery.
Then this happend:
System shuts down, boots, I see that some kind of black screen gets displayed(softkeys on and the display stays blank), then it reboots and stops the boot on the Galaxy S2 splash screen. Now that I didnt even get to the samsung splash screen I flashed the Apolo Kernel as an tar file through odin
after that I was able to get one step further and was able to get the Samsung splash Screen but the Splash screen keeps on repeating over and over but after that I also had my recovery back.
Now I tried to Install SuperSU 2.16 as zip in the recovery. but the endless samsung screen persited. After that I used the 2.15 Beta file. but this didnt work either.
I also fixed permissions wiped cache & dalvic cache
Why wouldnt my system boot after the first initial update and how can I finally fix the boot "loop"?
Thank you very much guys!
Heraku said:
I know this is an old topic, but the recent supersu update caused my phone to get stuck during booting:
The new update came over the playstore, it asked me to update the app. After that it said that the Super User Binary needs to be updated. I chose the option that does the update process in the CWM recovery.
Then this happend:
System shuts down, boots, I see that some kind of black screen gets displayed(softkeys on and the display stays blank), then it reboots and stops the boot on the Galaxy S2 splash screen. Now that I didnt even get to the samsung splash screen I flashed the Apolo Kernel as an tar file through odin
after that I was able to get one step further and was able to get the Samsung splash Screen but the Splash screen keeps on repeating over and over but after that I also had my recovery back.
Now I tried to Install SuperSU 2.16 as zip in the recovery. but the endless samsung screen persited. After that I used the 2.15 Beta file. but this didnt work either.
I also fixed permissions wiped cache & dalvic cache
Why wouldnt my system boot after the first initial update and how can I finally fix the boot "loop"?
Thank you very much guys!
Click to expand...
Click to collapse
Try to reinstall your rom without wipe data. Don't update supersu via cwm!
Sent from my GT-I9100 using XDA Free mobile app
chrisXL said:
Try to reinstall your rom without wipe data. Don't update supersu via cwm!
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
I was able to pull a logcat:
Could someone look into it and perhaps tell me how to fix it?
Heraku said:
I was able to pull a logcat:
Could someone look into it and perhaps tell me how to fix it?
Click to expand...
Click to collapse
Sorry to repeat myself, reflash your rom (no wipe). You will not lose anything.
It's the easiest way.
Sent from my GT-I9100 using XDA Free mobile app
after using complete unroot s6 keep in boot loop how to fix it?
If you use TWRP like me and have a recent backup of your system just restore it and it'll fix the boot loop.
chrisXL said:
Sorry to repeat myself, reflash your rom (no wipe). You will not lose anything.
It's the easiest way.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
thank u very much, this saved me from freaking out. it absolutely worked.
supersu binary reboot problem
first of all, get into recovery mode and copy the rom and gapps files to your internal storage through pc via usb cable.
then wipe the data, and make a clean flash of rom and gapps and reboot system.
I know this method will surely lose our data. but I have not found a solution at that particular instant other than this.
It happened to me.
Hope someone will surely solve this problem.
Thank you chrisXL, came across this thread from a Google search regarding my OnePlus2 using LinageOS after the SuperSU binary update. I simply went to INSTALL in TWRP and didn't use any wipe options. Phone booted right up after that! Thanks!!
Hi Guys, please help me. I flashed my moto g peregrine with the latest lineage os version. After that, i enable the the root option via TWRP with the addonsu.
After that, i downloaded via google store the SuperSU app i it asks to update the binary. I choosed the option via "TWRP" since the other option didn't work. After that, my phone is on bootloop (the symbol of lineage os is moving) and i can't acess to recovery mode.
What i can do?
j_moreno91 said:
Hi Guys, please help me. I flashed my moto g peregrine with the latest lineage os version. After that, i enable the the root option via TWRP with the addonsu.
After that, i downloaded via google store the SuperSU app i it asks to update the binary. I choosed the option via "TWRP" since the other option didn't work. After that, my phone is on bootloop (the symbol of lineage os is moving) and i can't acess to recovery mode.
What i can do?
Click to expand...
Click to collapse
Same problem here I had my mokke Rom pre rooted but titanium used to ask for SuperSU so installed the app from Google play and tried to install it via cwm/twrp and now it's stuck on the mokkee boot logo and can't even access my recovery what did you do solve the problem?
I just got myself a note 3 for sprint, and it had the OC5 Lollipop update on it. I flashed CF-Auto-Root on it, and it booted up fine. Used it for a bit, and then I tried putting TWRP on to flash Xposed Framework. TWRP flashed fine, and worked fine, but now the phone will not boot into the stock rooted rom. I have tried flashing the factory image again, that didn't fix it. Even tried flashing a kitkat factory image, and that didn't work either. The only way i can get the phone to boot into the OS is if i run a custom kitkat rom, and then everything seems to work fine. So where can i go from here to get the factory lollipop rooted with a custom recovery working?
tellem24 said:
I just got myself a note 3 for sprint, and it had the OC5 Lollipop update on it. I flashed CF-Auto-Root on it, and it booted up fine. Used it for a bit, and then I tried putting TWRP on to flash Xposed Framework. TWRP flashed fine, and worked fine, but now the phone will not boot into the stock rooted rom. I have tried flashing the factory image again, that didn't fix it. Even tried flashing a kitkat factory image, and that didn't work either. The only way i can get the phone to boot into the OS is if i run a custom kitkat rom, and then everything seems to work fine. So where can i go from here to get the factory lollipop rooted with a custom recovery working?
Click to expand...
Click to collapse
I'd say go back to NK4 and then accept the update to OC5 and root.
You'll need these files, please thank the OPs of the threads.
NK4 tar from [Odin] Mirrors for Official Samsung Tars for MJ4, NAB, NC5, NH7 & NK4
twrp-2.8.6.1-hltespr-4.4.img.tar from TWRP hltespr page
UPDATE-SuperSU-v2.46.zip from [STABLE][2015.02.13] SuperSU v2.46
Copy SuperSU zip file to your sdcard.
boot to recovery and factory reset, wipe partition cache and dalvik cache.
Then power the phone off from recovery.
Boot to download mode Volume Down + Home + Power ... then Volume Up.
(from the OFF state, booting into download mode from a ROM or recovery never works correctly when using odin)
Using Odin 3.09 flash NK4 tar, let it reboot, it will take it a while to start the first time.
when the phone restarts, unplug the usb cable.
you can skip all the setup stuff and then get the ota to get back to OC5; Settings, System Update, Firmware Update
once ota is completely done, power the phone off
go into download mode
odin the twrp tar (uncheck everything in odin)
once odin says pass unplug the usb cable and press Volume Up + Home + Power until the phone vibrates and you see the blue writing - this will get you into recovery w/o having to pull the battery.
flash the SuperSU zip file.
reboot to system, you should be on OC5 stock rooted.
jdelano said:
I'd say go back to NK4 and then accept the update to OC5 and root.
You'll need these files, please thank the OPs of the threads.
NK4 tar from [Odin] Mirrors for Official Samsung Tars for MJ4, NAB, NC5, NH7 & NK4
twrp-2.8.6.1-hltespr-4.4.img.tar from TWRP hltespr page
UPDATE-SuperSU-v2.46.zip from [STABLE][2015.02.13] SuperSU v2.46
Copy SuperSU zip file to your sdcard.
boot to recovery and factory reset, wipe partition cache and dalvik cache.
Then power the phone off from recovery.
Boot to download mode Volume Down + Home + Power ... then Volume Up.
(from the OFF state, booting into download mode from a ROM or recovery never works correctly when using odin)
Using Odin 3.09 flash NK4 tar, let it reboot, it will take it a while to start the first time.
when the phone restarts, unplug the usb cable.
you can skip all the setup stuff and then get the ota to get back to OC5; Settings, System Update, Firmware Update
once ota is completely done, power the phone off
go into download mode
odin the twrp tar (uncheck everything in odin)
once odin says pass unplug the usb cable and press Volume Up + Home + Power until the phone vibrates and you see the blue writing - this will get you into recovery w/o having to pull the battery.
flash the SuperSU zip file.
reboot to system, you should be on OC5 stock rooted.
Click to expand...
Click to collapse
Thanks! I actually got it working before i saw this by flashing the TWRP backup that someone posted on here, but i may try doing this to see if i can get xposed working with it, because it still isn't for me.
Not working
Everything working for me except when I flash twrp, it says pass, then comes to "android" recovery screen, so I can flash susuperuser
tellem24 said:
Thanks! I actually got it working before i saw this by flashing the TWRP backup that someone posted on here, but i may try doing this to see if i can get xposed working with it, because it still isn't for me.
Click to expand...
Click to collapse
Won't happen. It's all over xposed doesn't work on lollipop tw. Just search.
Sent from my 0x1 Note 3...... I love tep
Cybed said:
Everything working for me except when I flash twrp, it says pass, then comes to "android" recovery screen, so I can flash susuperuser
Click to expand...
Click to collapse
Try wiping data
Sent from my SM-N900P using XDA Free mobile app
kaos420 said:
Won't happen. It's all over xposed doesn't work on lollipop tw. Just search.
Sent from my 0x1 Note 3...... I love tep
Click to expand...
Click to collapse
Xposed will not work on 5.0 so don't try.... that is why you got a boot loop
jlechner said:
Try wiping data
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Working now Tks
Chaz187 said:
Xposed will not work on 5.0 so don't try.... that is why you got a boot loop
Click to expand...
Click to collapse
did you mean to quote me? i know it wont work silly . i was telling him that.
kaos420 said:
did you mean to quote me? i know it wont work silly . i was telling him that.
Click to expand...
Click to collapse
Sorry quoted by accident
Chaz187 said:
Sorry quoted by accident
Click to expand...
Click to collapse
i forgive you but only when you drop a new rom lol
kaos420 said:
i forgive you but only when you drop a new rom lol
Click to expand...
Click to collapse
As soon as we get the base rom built it will come!!!!
Ok So I with the help of ShinySide the Creator of Hispasain and TrapKernel. Have created a t900 root kernel for the new 5.1.1. you will have to install TWRP via ODIN and then flash this. This is a stock kernel that is set to permissive. It also installs the SU Binary's at the same time. I learned a lot in the last 3 days. Thank you @ShinySide
I know we don't have any Custom 5.1.1 Roms out yet but if your already Touchwiz 5.1.1 on some custom rom and only want my kernel then Skip to part 2.
Part 1
Ok if you are on 4.4.2 you will have to Odin Flash your tablet to 5.1.1 Stock. (Probably 2) times to get it to boot up.
If you are on CM(what ever version) Go into TWRP and WIPE Advanced SYSTEM / DATA / Cache / Dalvik Cache Then reboot into download mode and Odin the 5.1.1 (I've not done it this way might still need 2 try's)
Make sure tablet boots and you are now on stock 5.1.1 power down tablet.
Hold POWER VOLUME DOWN AND HOME and wait for Download Mode.
Load Odin. Connect your cable Select the TWRP.tar file . UN CHECK THE REBOOT OPTION! Flash the TWRP.tar file with Odin.
Now hold down just VOLUME UP AND POWER till you see a message at the top about Non-Enforcing recovery and then let go of the power button but not the up button. The screen should got black. let go of the volume button TWRP should start.
If you did not into TWRP You did not help the buttons right and are now looking at a Stock Recovery and will have to jump back up to "Make sure tablet boots into 5.1.1" and go from there again.
BACK UP Stock WITH TWRP BEFORE YOU FLASH !!! FOR THE LOVE OF GOD !
BACK UP Stock WITH TWRP BEFORE YOU FLASH !!! FOR THE LOVE OF GOD !
BACK UP Stock WITH TWRP BEFORE YOU FLASH !!! FOR THE LOVE OF GOD !
Part 2
Flash My Stealthee-Kernel.zip Below in TWRP (It already is set to install SU Binaries)
Reboot and DO NOT LET TWRP INSTALL SU Binaries or you will need to at least restore the system part of your Backup. If you did not back up before and missed the 3 lines saying so I can't help you. (Will not actually sorry) You will have to start over.
Remember at your own risk.. .boom. and all that
This Kernel also has Init.d support Although the current Stock Rom does not support this by Default. I was able to use terminal emulator and make mine work and show up So I could test Synapse. I don't work BTW Not supported.
GITHUB Source for Kernel is up
https://github.com/Stealthee/SM-T900_Kernel
If you would like to buy me a soda since i don't drink. But learning to kernel edit might of drove me to it. Feel free to donate
https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=j71rivera%40gmail%2ecom&lc=US&item_name=Stealthee%27s%20Soda%20Fund¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted
Thanks go to
ShinySide: for all the help and his githubs
toolhas4degrees: For the fixed zip with the correct block I kept messing up
g.lewarne: For UniKernel that made all this happen.
Side note im not sure im ready to learn how to over clock and all that. But who knows.. One day.
stealthee said:
Ok So i with the help of ShinySide the Creator of Hispasain and TrapKernel. Have created a t900 root kernel for the new 5.1.1. you will have to install TWRP and then flash this. Left my tablet at work its going to be stuck there over the weekend. So i need A brave soul that would be willing to give this a flash. It's just the kernel and root. Its either a OMG you rock. or damn you Stealthee (as you load up twrp to restore.) BACK UP WITH TWRP BEFORE YOU FLASH !!! FOR THE LOVE OF GOD !
http://www.filedropper.com/stealthee--kernel
Remember at your own risk.. .boom. and all that .. or OMG.. I would of already flashed if my tablet was here.
Click to expand...
Click to collapse
@ShinySide
su binary does not install. su apk is present
So the kernel did install too correct? I forgot to name it correctly so it will say. [email protected] and can you check se for android status under setting about device and tell if it shows permissive.
https://plus.google.com/photos/albu...6193636469279682626&oid=110078731989156903833
I have first flashed the ROM with Odin. Then flashed the other insecure kernel with Odin. Then flashed TWRP in Odin. Then flashed SuperSu and your kernel. But it only boots into recovery, not to system anymore. Just restored to CM again. Let's hope somone will succeed making a new root tool for Samsung 5.1.1 and up.
That's exactly what happened with my custom kernel. It would boot straight to recovery.
Planet X said:
I have first flashed the ROM with Odin. Then flashed the other insecure kernel with Odin. Then flashed TWRP in Odin. Then flashed SuperSu and your kernel. But it only boots into recovery, not to system anymore. Just restored to CM again. Let's hope somone will succeed making a new root tool for Samsung 5.1.1 and up.
Click to expand...
Click to collapse
ok you have to wipe everything except storage and flash the 5.1.1 update tar 2 times some times to get it to work. Then once you have that you have a stock 5.1.1 then flash the twrp tar. THEN flash my root kernel test. I need to know since i dont have my tablet here right now if the se android status under setting general about this device says "Permisive" or what it says" if it does then great i need to fix the librarys so sayeth the ShinySide. Or i need to update superuser in my ramdisk if it does cause i have the wrong one. thats why im asking abou tthe SE Status. If someone could answer this I'll know if i need to recompile the kernel again with a different passive fix. Just flashing 1 time the 5.1.1 TW rom will not work if you have not wiped everything. Took me 2 odins to get it running. and i was stock 4.4.2 rooted. if your on CM you will need to wipe and then flash. The tar does not seem to wipe data it just overlays it seems.
toolhas4degrees said:
@ShinySide
su binary does not install. su apk is present
Click to expand...
Click to collapse
K. But Is it set to permissive in settings?
I really know how to flash. And for me flash stock rom has worked the first time. But how do you flash the recovery without first flashing @andrewnelson23 kernel ? Your kernel is not tar.md5 but zip. If you try to flash TWRP after you have flashed stock rom the recovery doesn't get flashed. I have read the post about boot to recovery while pressing start in Odin but that didn't work for me. May be you can make a tar.md5 package with your kernel?
B.t.w. I have tried flashing with Flashfire but that results in Bootloop too.
Planet X said:
I really know how to flash. And for me flash stock rom has worked the first time. But how do you flash the recovery without first flashing @andrewnelson23 kernel ? Your kernel is not tar.md5 but zip. If you try to flash TWRP after you have flashed stock rom the recovery doesn't get flashed. I have read the post about boot to recovery while pressing start in Odin but that didn't work for me. May be you can make a tar.md5 package with your kernel?
Click to expand...
Click to collapse
I'm confused on why you think a recovery gets flashed when flashing a kernel. Or are you saying twrp isn't sticking after you reboot?
ShinySide said:
I'm confused on why you think a recovery gets flashed when flashing a kernel. Or are you saying twrp isn't sticking after you reboot?
Click to expand...
Click to collapse
Indeed, the recovery doesn't stick than.
Planet X said:
Indeed, the recovery doesn't stick than.
Click to expand...
Click to collapse
Simple fix. Flash recovery boot directly to recovery before going to the os
ShinySide said:
Simple fix. Flash recovery boot directly to recovery before going to the os
Click to expand...
Click to collapse
Do you mean i should be booted into twrp when starting flash with Odin?
Edit: I see. But that is what I did. Flash recovery and after flash your kernel. But then it boots right into twrp. Also wiped dalvik cache but that makes no difference.
Planet X said:
Do you mean i should be booted into twrp when starting flash with Odin?
Click to expand...
Click to collapse
No. If you have flashed twrp while in download mode and rebooted to android and then tried to go to twrp and it took you to stock recovery IE. twrp didn't stick, you need to flash twrp while in download mode and when it goes to reboot do your key combo to go to recovery before booting to android. Or Uncheck auto reboot, flash twrp, disconnect cable, hold power button til it shuts off then go directly to recovery before booting to android.
Your post didn't make much sense to me so assuming you meant you flashed twrp, let it reboot and when you tried rebooting to twrp it wasn't there.
ShinySide said:
No. If you have flashed twrp while in download mode and rebooted to android and then tried to go to twrp and it took you to stock recovery IE. twrp didn't stick, you need to flash twrp while in download mode and when it goes to reboot do your key combo to go to recovery before booting to android. Or Uncheck auto reboot, flash twrp, disconnect cable, hold power button til it shuts off then go directly to recovery before booting to android.
Your post didn't make much sense to me so assuming you meant you flashed twrp, let it reboot and when you tried rebooting to twrp it wasn't there.
Click to expand...
Click to collapse
By that's exactly what i did. I unchecked reboot in Odin and flashed twrp and tried to boot into twrp but all i get was stock recovery.
B.t.w. if you uncheck auto reboot in Odin you will have to flash the rom twice. That's right. But if leave auto reboot checked you will only have to flash one time
Planet X said:
By that's exactly what i did. I unchecked reboot in Odin and flashed twrp and tried to boot into twrp but all i get was stock recovery.
Click to expand...
Click to collapse
I'm beyond confused now after reading your previous posts edit and this one.
ShinySide said:
I'm beyond confused now after reading your previous posts edit and this one.
Click to expand...
Click to collapse
I have re-edited my post again. May be it's more clear now.
Okay one minute you have twrp, next minute twrp isn't sticking..... also talking about recovery not flashing an entire firmware with unchecked auto reboot
Planet X said:
By that's exactly what i did. I unchecked reboot in Odin and flashed twrp and tried to boot into twrp but all i get was stock recovery.
B.t.w. if you uncheck auto reboot in Odin you will have to flash the rom twice. That's right. But if leave auto reboot checked you will only have to flash one time
Click to expand...
Click to collapse
ok after you flash twrp and uncheck reboot after it flashes. hold down ONLY volume down and power untill you see the selinux msg on top. let it go. it should goto a black screen and then into twrp. do not hold HOME. you only get 1 chance if you boot into stock recovery you have to start all over and get back into download mode and flash twrp tar again. But once you do it 1 time it sticks and stock recovery is replaced by twrp.
stealthee said:
ok after you flash twrp and uncheck reboot after it flashes. hold down ONLY volume down and power untill you see the selinux msg on top. let it go. it should goto a black screen and then into twrp. do not hold HOME.
Click to expand...
Click to collapse
Boot into twrp
Wipe advanced system, data, caches
Reboot to download mode
Flash stock rom with odin 3.10
Go through setup
Switch off
Boot into download mode
Start odin and uncheck auto reboot
Flash twrp 3.8.7.0
Switch tablet off
Start tablet with volume up and home pressed to enter twrp
All i have is stock recovery
So i power off tablet
Power + volume down + home pressed to enter download mode
Start Odin and uncheck auto reboot
Flash @andrewnelson23 kernel
Power off tablet
Start download mode again with power + volume down + home button pressed
Start odin switch off auto reboot
Flash twrp again
Power off tablet
Enter twrp with power + volume up + home pressed
Flash SuperSu and your kernel in one time
Power off tablket
Power on tablet but only enter recovery
That's all. Is that clear to you?
---------- Post added at 07:04 PM ---------- Previous post was at 07:00 PM ----------
stealthee said:
ok after you flash twrp and uncheck reboot after it flashes. hold down ONLY volume down and power untill you see the selinux msg on top. let it go. it should goto a black screen and then into twrp. do not hold HOME. you only get 1 chance if you boot into stock recovery you have to start all over and get back into download mode and flash twrp tar again. But once you do it 1 time it sticks and stock recovery is replaced by twrp.
Click to expand...
Click to collapse
Okay. I will try that once again. And immediately flash this kernel than if that works.
Planet X said:
Boot into twrp
Wipe advanced system, data, caches
Reboot to download mode
Flash stock rom with odin 3.10
Go through setup
Switch off
Boot into download mode
Start odin and uncheck auto reboot
Flash twrp 3.8.7.0
Switch tablet off
Start tablet with volume up and home pressed to enter twrp
All i have is stock recovery
So i power off tablet
Power + volume down + home pressed to enter download mode
Start Odin and uncheck auto reboot
Flash @andrewnelson23 kernel
Power off tablet
Start download mode again with power + volume down + home button pressed
Start odin switch off auto reboot
Flash twrp again
Power off tablet
Enter twrp with power + volume up + home pressed
Flash SuperSu and your kernel in one time
Power off tablket
Power on tablet but only enter recovery
That's all. Is that clear to you?
---------- Post added at 07:04 PM ---------- Previous post was at 07:00 PM ----------
Okay. I will try that once again. And immediately flash this kernel than if that works.
Click to expand...
Click to collapse
Start tablet with volume up and home pressed to enter twrp
All i have is stock recovery
Wrong i said power and volume down. i explicitly said NO HOME BUTTON. you hold them after twrp flash. when you see unenforcing msg let go.
Hello, I am new here and also new to using an android device. I followed instructions to root my phone and now I can access the command "su" in a local terminal. But when I go to download SuperUser it says my device is not rooted. Did I miss something? And if I did mess up and didn't install the right kernel, autoroot or whatever, how do I check my android's model number?
thakyZ said:
Hello, I am new here and also new to using an android device. I followed instructions to root my phone and now I can access the command "su" in a local terminal. But when I go to download SuperUser it says my device is not rooted. Did I miss something? And if I did mess up and didn't install the right kernel, autoroot or whatever, how do I check my android's model number?
Click to expand...
Click to collapse
On the back either on the better cover when you peel it off or under the battery it should say something like G900T or G900V depending on your carrier and type of phone I'll help if I can just need to know which model you are actually you might be able to skip my instructions below and just go to install super su and that night work but if not just follow those instructions and you'll be golden if you got any questions pm me or just click the reply button and ask and I'll do my best to answer it
Download the rom you want and kernels that go with it depending on your phones settings such as oj4 OL1 it'll say under settings and about device those versions are the last 3 characters in the field (that confused me at first just a heads up) etc etc make sure theyre all the same also don't forget to download supersu (I can't remember where to find it just go on my topic and someone posted the link there
Put them onto your SD card
Download TWRP 2.8.whatever the newest one is on your computer
Download Odin and on the AP slot or PDA click it then find the TWRP file and click that then go under options on Odin and uncheck autoreboot
Turn your phone off and put it into download mode (press the volume down button and home button and power button at the same time) then the volume up button once the confirmation screen comes on
Then flash the TWRP and once it's done it'll Stat on that screen so you have to remove the battery then put it back in and boot into recovery mode (volume up home button and power button at same time)
Now go into the install button and navigate to your SD card and find the super su and click the install or flash button I can't remember which it is and slide the slider thing and hit reboot phone
When it asks to install super su before you reboot don't click install just reboot it since you've already installed it it'll work
Then go in and you'll have supersu and be rooted
Now boot back into recovery and install/flash the rom and kernel and ignore the supersu install thing again and you'll be good to go I also highly advise making a backup if you have the space for it
Ok I have done that, but now my phone is stuck on the T-Mobile logo...
thakyZ said:
Ok I have done that, but now my phone is stuck on the T-Mobile logo...
Click to expand...
Click to collapse
hmmm did you do the whole process or just the supersu or what part did it get stuck on?
Veid71 said:
hmmm did you do the whole process or just the supersu or what part did it get stuck on?
Click to expand...
Click to collapse
It was after I chose to reboot my device so superSU could build the cache manifest with twrp
thakyZ said:
It was after I chose to reboot my device so superSU could build the cache manifest with twrp
Click to expand...
Click to collapse
okay after you slid the slider bar and click the reboot button when it asked to install supersu did you click install? or did you just click reboot and ignore it? and did you install this super su?https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip id say just redownload it and make sure it wasnt a messed up download and boot back into recovery mdoe and try it again
Veid71 said:
okay after you slid the slider bar and click the reboot button when it asked to install supersu did you click install? or did you just click reboot and ignore it? and did you install this super su?https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip id say just redownload it and make sure it wasnt a messed up download and boot back into recovery mdoe and try it again
Click to expand...
Click to collapse
Well I couldn't find that link but thanks for giving me it. I downloaded SuperSU from google play instead. But I started SuperSU and it wanted to rebuild the cache or something and it gave me the options to do it normally or with twrp so I chose twrp. It rebooted started twrp and started building it, then it started back up and was stuck on the T-Mobile screen. But I downloaded a new rom from sammobile.com and I couldn't get it to work then I renembered something about you have to use a secific Odin version, so I went from 3.10.7 to 3.09 and nothing changed, so then I cleared cache and nothing. So, I went to Odin3 3.07 and nothing so I went back up to 3.09 and it started to stop being soft bricked. And I just have to set everything back up, which will not take long, about 2 hours. So, I will download the SuperSU from that site and I will see if it works again.
Note to self: keep the stock rom, damn it's a huge file.
thakyZ said:
Well I couldn't find that link but thanks for giving me it. I downloaded SuperSU from google play instead. But I started SuperSU and it wanted to rebuild the cache or something and it gave me the options to do it normally or with twrp so I chose twrp. It rebooted started twrp and started building it, then it started back up and was stuck on the T-Mobile screen. But I downloaded a new rom from sammobile.com and I couldn't get it to work then I renembered something about you have to use a secific Odin version, so I went from 3.10.7 to 3.09 and nothing changed, so then I cleared cache and nothing. So, I went to Odin3 3.07 and nothing so I went back up to 3.09 and it started to stop being soft bricked. And I just have to set everything back up, which will not take long, about 2 hours. So, I will download the SuperSU from that site and I will see if it works again.
Note to self: keep the stock rom, damn it's a huge file.
Click to expand...
Click to collapse
No problem I figured that's what had happened and I used Odin 3.10.6 I think it was and yeah if you do it with the TWRP one it ducks it up for some reason I think it's an old supersu version or some thing and it's not compatible but I'll also post a link to download the stock rooted rom for you to flash
http://forum.xda-developers.com/tmo...t/how-to-update-to-g900tof6-5-1-1-pc-t3141404
Veid71 said:
No problem I figured that's what had happened and I used Odin 3.10.6 I think it was and yeah if you do it with the TWRP one it ducks it up for some reason I think it's an old supersu version or some thing and it's not compatible but I'll also post a link to download the stock rooted rom for you to flash
http://forum.xda-developers.com/tmo...t/how-to-update-to-g900tof6-5-1-1-pc-t3141404
Click to expand...
Click to collapse
Which one do I want to download?
thakyZ said:
Which one do I want to download?
Click to expand...
Click to collapse
Either or it really doesn't matter me personally I like deodex just because there's more customizability with it but both do the job also if you do the deodex one it'll take about 10-15minutes to come on after you flash/install it in twrp where as regular should just come on like a normal boot maybe 5 minutes
After about a month of making sure it works I have successfully rooted my phone! Thank you very much!
back up all your data before starting​
Code:
#include <std_disclaimer.h>
/*
*
* I'm not responsible for bricked devices, dead SD cards,
* before flashing it! YOU are choosing to make these modifications.
Features:
- magisk works.
- encryption/decryption doesn't work.
Install guide:
1. you are in stock rom ..
2. go to settings and remove your google accounts ...
3. reboot to stock recovery ..
4. wipe data/cache
5. reboot to boot-loader ( download mode )
6. open Odin... choose AP and select the downloaded file TWRP_3.tar
7. connect your phone to usb and click start... immediately click volume up + power button tail you are in twrp
8. if you cant open internal storage on computer... format data on twrp.
Download:
https://mega.nz/#!SWYwAQAb!bbLnex8yhT7tyBTdTMr2wIS-tzITjg5VMJ_p1msXenQ
install this decrypter .
thanks to geiti94 and Mauronofrio and Zackptg5
......
reserved
this one too
can i update to latest of magisk ?
thanks for hard work
On booting to recovery using the key combination, my phone got stuck at the TeamWin splash screen and won't go beyond it. Now it just boots to that screen when using the normal key combination as well instead of Android. Anything I did wrong or is there any other issue?
I was using Magisk with stock recovery prior to flashing this. Going to flash the stock ROM again using Odin and try this once again.
Edit: Since all reboot options now lead to the TWRP splash screen, there doesn't seem to be a way to get in to download mode. Most likely seems that I have to let the battery drain out. A word of caution for anyone else trying this out.
t3chg33k said:
On booting to recovery using the key combination, my phone got stuck at the TeamWin splash screen and won't go beyond it. Now it just boots to that screen when using the normal key combination as well instead of Android. Anything I did wrong or is there any other issue?
I was using Magisk with stock recovery prior to flashing this. Going to flash the stock ROM again using Odin and try this once again.
Edit: Since all reboot options now lead to the TWRP splash screen, there doesn't seem to be a way to get in to download mode. Most likely seems that I have to let the battery drain out. A word of caution for anyone else trying this out.
Click to expand...
Click to collapse
have you formatted data? and rebooted directly to bootloader?
when stuck on spash screen means data is encrypted.
zvox said:
have you formatted data? and rebooted directly to bootloader?
when stuck on spash screen means data is encrypted.
Click to expand...
Click to collapse
I had removed all accounts and formatted data/cache partitions before flashing the TWRP file. However, the first time I missed booting immediately in to recovery and the OS started booting instead. So, I rebooted in to recovery and it is stuck on the TWRP splash screen since then. So, did the half boot in to the OS result in encryption of the data partition once again?
Tried just about everything but still stuck on the splash screen. I don't know when the battery will run out now but do hope that I will be able to get in to download mode once it does so or otherwise I think I got myself a brick.
t3chg33k said:
I had removed all accounts and formatted data/cache partitions before flashing the TWRP file. However, the first time I missed booting immediately in to recovery and the OS started booting instead. So, I rebooted in to recovery and it is stuck on the TWRP splash screen since then. So, did the half boot in to the OS result in encryption of the data partition once again?
Tried just about everything but still stuck on the splash screen. I don't know when the battery will run out now but do hope that I will be able to get in to download mode once it does so or otherwise I think I got myself a brick.
Click to expand...
Click to collapse
no needfor battery to drain, just Press volume up + down + power with USB plugged in and when the phone turn off release power and keep pressing up/down buttons. and you'll be directed to download mode
zvox said:
no needfor battery to drain, just Press volume up + down + power with USB plugged in and when the phone turn off release power and keep pressing up/down buttons. and you'll be directed to download mode
Click to expand...
Click to collapse
Thanks, that's the combination I was looking out for. I did that combination without the USB connected and used some other combination when the USB was connected. After a fresh ODIN flash, I was able to boot in to TWRP without any issues, so great job with the recovery.
Update 1: After powering off the device, it is now only booting to stock recovery, no sign of TWRP. Selecting the 'Reboot to system' option in stock recovery results in a "cannot load android system" and "data may be corrupt" message. Selecting "factory reset" option in stock recovery booted me to Android.
Update 2: Booted to system after the factory reset and powered off. Now the phone won't go past the Samsung logo with the message "only official binaries are allowed to be flashed"
t3chg33k said:
Thanks, that's the combination I was looking out for. I did that combination without the USB connected and used some other combination when the USB was connected. After a fresh ODIN flash, I was able to boot in to TWRP without any issues, so great job with the recovery.
Update: After powering off the device, it is now only booting to stock recovery, no sign of TWRP. Selecting the 'Reboot to system' option in stock recovery results in a "cannot load android system" and "data may be corrupt" message. Selecting "factory reset" option in stock recovery booted me to Android.
Click to expand...
Click to collapse
wipe data again and reboot to bootloader and flash twrp again, once youre in twrp.. mount system... open file manager and go to system/system and rename recovery-from-boot.p to recovery-from-boot.p.bak.
i forget to mention that.
dont forget to flash the decrypter before booting.
zvox said:
no needfor battery to drain, just Press volume up + down + power with USB plugged in and when the phone turn off release power and keep pressing up/down buttons. and you'll be directed to download mode
Click to expand...
Click to collapse
zvox said:
wipe data again and reboot to bootloader and flash twrp again, once youre in twrp.. mount system... open file manager and go to system/system and rename recovery-from-boot.p to recovery-from-boot.p.bak.
i forget to mention that.
dont forget to flash the decrypter before booting.
Click to expand...
Click to collapse
I had to first boot in to the OS and check for updates to register the device with the OEM unlock option enabled once again before the "official binaries only" message disappeared. Thereafter things worked out fine as per your instructions and I have permanent TWRP. Will try out Magisk-patched TWRP later and post the results.
Would you mind attaching the kernel source?
Anyone else tried this TWRP? is this really a permanent TWRP?
zidane02 said:
Anyone else tried this TWRP? is this really a permanent TWRP?
Click to expand...
Click to collapse
TWRP is permanent but it always boots to TWRP irrespective of key combination and from there one has to reboot to System.
Also, I patched the recovery image with Magisk and it doesn't seem to work. When rebooting to recovery from TWRP the first time, it leads to a blank screen and on rebooting it gets stuck at the Samsung boot logo.
t3chg33k said:
TWRP is permanent but it always boots to TWRP irrespective of key combination and from there one has to reboot to System.
Also, I patched the recovery image with Magisk and it doesn't seem to work. When rebooting to recovery ffrom TWRP the first time, it leads to a blank screen and on rebooting it gets stuck at the Samsung boot logo.
Click to expand...
Click to collapse
I see. But what is TWRP without magisk? Nandroid is ok, but my main purpose of TWRP is magisk.
So my 2nd question is, will this work on any firmware?
zidane02 said:
I see. But what is TWRP without magisk? Nandroid is ok, but my main purpose of TWRP is magisk.
So my 2nd question is, will this work on any firmware?
Click to expand...
Click to collapse
Not much use for non-Magisk TWRP I am afraid. So I am going back to Magisk with stock recovery for now since I chiely use Titanium backup.
I am on the ASE2 firmware and since this TWRP boots it up fine, I am assuming it is the same kernel version as used in the stock version since its source code was released recently. Hence, it might not work with other firmware but I am in no position to check that out.
t3chg33k said:
Not much use for non-Magisk TWRP I am afraid. So I am going back to Magisk with stock recovery for now since I chiely use Titanium backup.
I am on the ASE2 firmware and since this TWRP boots it up fine, I am assuming it is the same kernel version as used in the stock version since its source code was released recently. Hence, it might not work with other firmware but I am in no position to check that out.
Click to expand...
Click to collapse
I see. Then I'll be preserving my knox for the mean time until a stable and Magisk-able TWRP is available.
There is magisk with stock recovery? Can you tell me where can I find this thread? Also will this method trip your knox? Thanks.
zidane02 said:
I see. Then I'll be preserving my knox for the mean time until a stable and Magisk-able TWRP is available.
There is magisk with stock recovery? Can you tell me where can I find this thread? Also will this method trip your knox? Thanks.
Click to expand...
Click to collapse
You can always install Magisk with stock recovery for any firmware using topjohnwu's guide over here. However, Magisk installation will always trip Knox.
Also, TWRP might be helpful in flashing various patches, especially for GSI releases that you cannot do with the stock recovery.
t3chg33k said:
You can always install Magisk with stock recovery for any firmware using topjohnwu's guide over here. However, Magisk installation will always trip Knox.
Also, TWRP might be helpful in flashing various patches, especially for GSI releases that you cannot do with the stock recovery.
Click to expand...
Click to collapse
Thank you so much for the link. I'm good without TWRP for now, not a fan of GSI since many things are broken, magisk is what I really needed. Thanks again.
Eamo5 said:
Would you mind attaching the kernel source?
Click to expand...
Click to collapse
Good to see you here lol