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?
Related
Hello everybody,
First I'd like to thank to community for the hard work. I v read a countless amount of pages of this forum and I can't even imagine the time people spent helping on issues or writing tutorials.
So thank you if you re up to spend few minutes on my specific case (and sorry for the bad english).
Here is my device and the different version of kernel ...
1/ Rooting my device (tutorial in french translated from xda)
http://www.cnetfrance.fr/produits/guide-rooter-son-galaxy-s2-39763841.htm
S-Root version used: http://forum.xda-developers.com/showthread.php?t=1125414
Everything went pretty well when I rooted the GS2. I got the Superuser app so i figure it's ok.
I just used a modified kernel found on xda who was corresponding the my base band version (just the PDA in Odin).
2/ Installing a new ROM (Cyanogenmod by Rom Manager)
I followed : http://www.redmondpie.com/install-cm7-on-galaxy-s2-using-rom-manager-how-to-tutorial/ and http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide (official guide) using Rom Manager premium.
When i tried to reboot in Recovery (manually or with Rom Manager), i can't find the "Install the zip" option, I have 4 available: "Update from the zip", the 2 wiping/delete options and the reboot.
So obviously if i try to wipe files, wipe the cache then to update with the zip I have the following Error:
E: failed to verify whole-file signature
Do you have any idea what went wrong in the process ?
Should i flash the phone withOdin and change my base band version to another one ?
For info, I did the Permission Fix option in Rom Manager too. Didnt help.
Thanks a lot.
U need clockworkmod instaled first..
Sent from my GT-S5570 using xda premium
sgt_ray said:
Do you have any idea what went wrong in the process ?
Click to expand...
Click to collapse
You didn't install ClockworkMod Recovery.
Thanks for theses answers but I think I installed it with Rom Manager and i flashed it to the last version.
(joined file 1 : cwm rom manager.jpg)
When i reboot in recovery mode here is the only options available (and it's the problem i pointed out) :
(joined file 2 : 20111125_13221022.jpg)
Maybe a problem with my SD card ?
sgt_ray said:
but I think I installed it with Rom Manager and i flashed it to the last version.
Click to expand...
Click to collapse
As we've already said, you haven't installed CWM Recovery. You see at the top of your second photo where it says "Android system recovery (3e)"? That's stock recovery.
you can't install CWM recovery thru ROM manager.
just flash the CF Root Kernel for KI4 thru ODIN , you will have CWM recovery.
Hmm I understand about the CWM version I'm booting with, but as you can see on the first capture, my kernel version is a modified one i got after using Odin (puting this Kernel : GT-I9100_XXKI4_insecure.tar from http://forum.xda-developers.com/showthread.php?t=1101671).
I got the root access by S2 Root.
Ok I think I installed only the Kernel and not CF Root available here : http://forum.xda-developers.com/showthread.php?t=1103399
I ll try to redo Odin and stuff and let you know if I'm still alive.
So it's not great right now. I have installed CF Root with Odin, so I had CWM on my phone (I could see the application). Then after reboot with CWM Recovery and installing Cyanogenmod, the phone doesnt want to start anymore.....
I tried to apply the insecure kernel again with Odin but still impossible to download. I'm stuck on the screen with the yellow sign and written Galaxy S2.
HALP !!
I just tried to put back the official firware version : http://forum.xda-developers.com/showthread.php?t=1075278 and put it in my phone with Odin.
Ok, I dont have the yellow sign anywore but the phone is still stuck on the boot screen (where it's written Samsung GALAXY s II)...
What should I try ?
I'm still able to boot with CWM recovery but I didn't make any backup and nothing work.
Do you think the phone is dead ?
5 posts in a row?
So, just to clarify, you've tried to install CM7, which amongst other things tells you to do a nandroid backup, and also to flash twice in succession. Did you do either of these things? The instructions are there to be followed, don't just ignore them.
Ok my bad I didn't backup anything because I had no data to backup. This was maybe a bad move...
Anyway, I tried to flash it twice yes. Right now, i'm working with a modified Kernel (with CF Root), and booting in CWM Recovery. When I want to flash again by installing from the .zip I get a Satus 7 Error.
In CWM, every advanced options are apparently available but I dont know anything about them.
And just so you know, on my SD Card i have 1 update.zip and the update-cm-7.1.0-Galaxys2.... .zip from Cyanogen.
sgt_ray said:
Ok my bad I didn't backup anything because I had no data to backup. This was maybe a bad move...
Anyway, I tried to flash it twice yes. Right now, i'm working with a modified Kernel (with CF Root), and booting in CWM Recovery. When I want to flash again by installing from the .zip I get a Satus 7 Error.
In CWM, every advanced options are apparently available but I dont know anything about them.
And just so you know, on my SD Card i have 1 update.zip and the update-cm-7.1.0-Galaxys2.... .zip from Cyanogen.
Click to expand...
Click to collapse
Flash a stock rom with Odin and then root your phone again. Start reading and follow procedures when you want to flash custom roms again .See Intratechs`s thread for a stock rom
Thanks for your reply.
I did it, it didn't work, I mean i could flash with Odin but the reboot doesn't work : the start screen appeared without the yellow sign, but it's stuck on it.
--- update
FYI, I installed Rom Manager yesterday, it way interact in a bad way with CWM Recovery.
For now i can mount USB by CWM Recovery but cannot do anything else.
If you have a method to clean completely the phone ? Maybe the bootloader is broken...
sgt_ray said:
I just tried to put back the official firware version : http://forum.xda-developers.com/showthread.php?t=1075278 and put it in my phone with Odin.
Ok, I dont have the yellow sign anywore but the phone is still stuck on the boot screen (where it's written Samsung GALAXY s II)...
What should I try ?
I'm still able to boot with CWM recovery but I didn't make any backup and nothing work.
Click to expand...
Click to collapse
Wipe data and cache after flashing..
Sent from my GT-S5570 using xda premium
I did it. 20 times .
Maybe I should re partition my SD card...
--- update ---
I re partitionned my SD Card with Odin and tried to install a new stock ROM. Everything pass with Odin but to finalize the set up (while reboot), I got some errors and still the same problem during the boot. It's stuck !
I installed a insecure Kernel so I can access CWM Recovery but still stuck and now I can't mount anything .
Sorry to post again...
Finally I ordered a USB jig in case of...
I found this solution : http://forum.xda-developers.com/showpost.php?p=16902269&postcount=8
May try it this we.
sgt_ray said:
Sorry to post again...
Finally I ordered a USB jig in case of...
I found this solution : http://forum.xda-developers.com/showpost.php?p=16902269&postcount=8
May try it this we.
Click to expand...
Click to collapse
Good luck...
Sent from my GT-S5570 using xda premium
Hello.
This is urgent. I need this phone to work as soon as possible
I'm new to the modding scene, and I have decided to install 5.1.1 Lollipop on my Samsung SII GT-i9100.
I tried to download this ROM off this page: http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-12-t2955551
It says I need :"Kitkat Compatible Recovery". I suspect this was the problem as I had Jellybean 4.1.2, not any KitKat version but I was attempting to install Lollipop 5.1.1 (if any of this makes any sense at all).
This is the page that I found after googling "KitKat Compatible Recovery": http://www.ibtimes.co.uk/install-an...ible-cwm-recovery-galaxy-s2-i9100-how-1434170
The page says to flash "GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar" onto my gt-i9100 using Odin, which is what I did.
When the flash was completed and I saw the "PASS" message in Odin, the page said the phone should reboot automatically. This did not happen. When I tried booting manually, I was shown "Samsung Gallaxy SII GT-I9100" with a yellow triangle and exclamation mark underneath. Then the boot sound played but the screen stayed black. After this the phone screen stayed black and did not boot.
I did some searching on how to remove said triangle, but in all the examples I have found the phone booted. Mine didn't.
All I'm asking is if someone knows how to fix my phone back to normal, or a redirect to a link where this issue is already addressed.
Thanks for your help.
P.S. Recovery and Download are accessible normally
Clone1303 said:
Hello.
This is urgent. I need this phone to work as soon as possible
I'm new to the modding scene, and I have decided to install 5.1.1 Lollipop on my Samsung SII GT-i9100.
I tried to download this ROM off this page: http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-12-t2955551
It says I need :"Kitkat Compatible Recovery". I suspect this was the problem as I had Jellybean 4.1.2, not any KitKat version but I was attempting to install Lollipop 5.1.1 (if any of this makes any sense at all).
This is the page that I found after googling "KitKat Compatible Recovery": http://www.ibtimes.co.uk/install-an...ible-cwm-recovery-galaxy-s2-i9100-how-1434170
The page says to flash "GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar" onto my gt-i9100 using Odin, which is what I did.
When the flash was completed and I saw the "PASS" message in Odin, the page said the phone should reboot automatically. This did not happen. When I tried booting manually, I was shown "Samsung Gallaxy SII GT-I9100" with a yellow triangle and exclamation mark underneath. Then the boot sound played but the screen stayed black. After this the phone screen stayed black and did not boot.
I did some searching on how to remove said triangle, but in all the examples I have found the phone booted. Mine didn't.
All I'm asking is if someone knows how to fix my phone back to normal, or a redirect to a link where this issue is already addressed.
Thanks for your help.
P.S. Recovery and Download are accessible normally
Click to expand...
Click to collapse
When you boot into recovery which version do you have? If it is the 6.0.2.9 CWM, then flash the CWM 6.0.4.5 mentioned (from recovery) then reboot back into recovery(not system). You should now have CWM 6.0.4.5. Now from this recovery, do a full wipe(factory reset, wipe cache and dalvik cache(from advanced in menu) and format system. Then flash the rom and gapps(if you want them). Then reboot to system.
If you have the stock 3e recovery, you need to enable root access. Let us know if this is the case
I have CM v5.8.1.8, but I flashed 6.0.2.9.
That's weird
Don't worry about the triangle for now, just goto recovery flash a lollipop rom with gapps, after you are in the rom just use the triangle away app and remove it (I have done this loads of times) but be sure you have the correct KitKat recovery or this might not work.
Sent from my GT-I9100 using XDA Free mobile app
Clone1303 said:
I have CM v5.8.1.8, but I flashed 6.0.2.9.
That's weird
Click to expand...
Click to collapse
I've got no idea what the 5.8.1.8 is but from this recovery(it says cwm right?) try flashing the newer one like I said in the last post
cm-kernel-09-05-2015-TWRP-2.8.6.0
noppy22 said:
I've got no idea what the 5.8.1.8 is but from this recovery(it says cwm right?) try flashing the newer one like I said in the last post
Click to expand...
Click to collapse
I used this last time I flashed with odin and tick reboot in odin so it reboots automatically, when it is rebooting use the keys to go to recovery and flash the ROM of your choice
noppy22 said:
I've got no idea what the 5.8.1.8 is but from this recovery(it says cwm right?) try flashing the newer one like I said in the last post
Click to expand...
Click to collapse
Could you explain how to flash it? It's a .zip file not .tar.
If you mean that I should put the .zip in the root of my phone, I can't do that as I when I plug in my phone to my PC I can't access root. (I suspect this is because my phone is not booted and I can't get it to boot)
Clone1303 said:
Could you explain how to flash it? It's a .zip file not .tar.
If you mean that I should put the .zip in the root of my phone, I can't do that as I when I plug in my phone to my PC I can't access root. (I suspect this is because my phone is not booted and I can't get it to boot)
Click to expand...
Click to collapse
You need the .tar file to flash using Odin, use the tar file I attached in the previous post it should work
Sent from my GT-I9100 using XDA Free mobile app
akiwiz said:
You need the .tar file to flash using Odin, use the tar file I attached in the previous post it should work
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
I know this much, but the problem is that I don't have a ROM on my phone, and I can't access root so I can't place it there. I see an option called "sideload" in the recovery menu, but I don't know what this means and how I could use it.
I have flashed the .tar file you attached. Now I can't access recovery mode.
Okay I've managed to enter recovery by removing the battery and going into download, pressing down-volume to boot and then entering recovery normally. Now what.
I can now enter recovery. What do i do now
Clone1303 said:
I can now enter recovery. What do i do now
Click to expand...
Click to collapse
Now you can flash the ROM you want, you do know how to flash a rom right?
Sent from my GT-I9100 using XDA Free mobile app
Clone1303 said:
I have flashed the .tar file you attached. Now I can't access recovery mode.
Click to expand...
Click to collapse
GUYS I got it to work. I flashed the two files from the description of this video, and used cm-kernel-09-05-2015-TWRP-2.8.6.0 to flash both of these files. It took some firguring out, but I got there in the end. The ROM is Lollipop 5.1.1 with CyanogenMod version 12.1-20150504-UNOFFICIAL-i9100.
Thanks for all the help you guys supplied, I couldn't have done this without you.
Now enjoy lollipop
Sent from my GT-I9100 using XDA Free mobile app
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!
Every time I try to root my tmobile-galaxy s5, which in now on 5.1.1 and on the newest update fol1, I install the newest version of twrp for this device but every time I install twrp the error message "set warranty bit kernel" pops up. Any idea to get passed this so I can root my phone?
This guy needs help said:
Every time I try to root my tmobile-galaxy s5, which in now on 5.1.1 and on the newest update fol1, I install the newest version of twrp for this device but every time I install twrp the error message "set warranty bit kernel" pops up. Any idea to get passed this so I can root my phone?
Click to expand...
Click to collapse
The set warranty bit isn't a problem, it's just the phone's way of showing you have a custom recovery installed. I get the same notification every time I boot up but I was able to root successfully. I assume you're using the correct version of TWRP and the superSU zip?
thisisapoorusernamechoice said:
The set warranty bit isn't a problem, it's just the phone's way of showing you have a custom recovery installed. I get the same notification every time I boot up but I was able to root successfully. I assume you're using the correct version of TWRP and the superSU zip?
Click to expand...
Click to collapse
I flashed twrp on Odin and went into twrp but when I flash supersu in twrp I hit boot in to system but it says set warranty bit kernel in the top left corner for a while. Please help me I need root acess
This guy needs help said:
I flashed twrp on Odin and went into twrp but when I flash supersu in twrp I hit boot in to system but it says set warranty bit kernel in the top left corner for a while. Please help me I need root acess
Click to expand...
Click to collapse
Which superSU version and which TWRP version? Also did you check the md5 on both? It sounds like you might have a bad download; this method has worked to root countless other people's devices with no issue
thisisapoorusernamechoice said:
Which superSU version and which TWRP version? Also did you check the md5 on both? It sounds like you might have a bad download; this method has worked to root countless other people's devices with no issue
Click to expand...
Click to collapse
I downloaded twrp and supersu on a thread you were on and you said they were good. I have a question though, how long did the first boot up take for you rooted phone?
This guy needs help said:
I downloaded twrp and supersu on a thread you were on and you said they were good. I have a question though, how long did the first boot up take for you rooted phone?
Click to expand...
Click to collapse
Same as normal boot up if I remember correctly. I also hadn't set anything up yet, even skipped the initial setup wizard that runs when you first start the phone, because I knew I planned to install cyanogenmod as soon as I was rooted. I only booted into system after I rooted once to run a couple of apps that require root in order to verify that I was, in fact, rooted. After that I wiped everything in order to install CM
thisisapoorusernamechoice said:
Same as normal boot up if I remember correctly. I also hadn't set anything up yet, even skipped the initial setup wizard that runs when you first start the phone, because I knew I planned to install cyanogenmod as soon as I was rooted. I only booted into system after I rooted once to run a couple of apps that require root in order to verify that I was, in fact, rooted. After that I wiped everything in order to install CM
Click to expand...
Click to collapse
When I installed twrp and the used it than flashed supersu, I hit boot into system and then it didn't boot into system, it just said "set warranty bit kernel". Please help.
This guy needs help said:
When I installed twrp and the used it than flashed supersu, I hit boot into system and then it didn't boot into system, it just said "set warranty bit kernel". Please help.
Click to expand...
Click to collapse
I need logs or something, because as I've said, "set warranty bit kernel," isn't a problem, that's normal and expected. I can't know what's wrong with your device with no information.
Did you try starting from the beginning? Flashing the stock OL1 Odin file, booting that up (not setting anything up except a Wi-Fi connection), and trying rooting with that? Did you try opening the TWRP tar file with 7zip or WinRAR and extracting the img file to verify the download wasn't corrupted? Did you try doing a similar check with the superSU zip? What version of supersu are you trying to use? Have you tried clearing cache and dalvik after installing supersu (not necessary but sometimes helps clear up issues)?
thisisapoorusernamechoice said:
I need logs or something, because as I've said, "set warranty bit kernel," isn't a problem, that's normal and expected. I can't know what's wrong with your device with no information.
Did you try starting from the beginning? Flashing the stock OL1 Odin file, booting that up (not setting anything up except a Wi-Fi connection), and trying rooting with that? Did you try opening the TWRP tar file with 7zip or WinRAR and extracting the img file to verify the download wasn't corrupted? Did you try doing a similar check with the superSU zip? What version of supersu are you trying to use? Have you tried clearing cache and dalvik after installing supersu (not necessary but sometimes helps clear up issues)?
Click to expand...
Click to collapse
All I did was flash the latest file of twrp. Then when it said pass I went straight into download mode and then flashed supersu (the latest version for my phone. After that I rebooted but it only says "set warranty bit kernel" in the top left corner in yellow. I tried this twice but same result (on the second time I flashed fol1 again before I tried).
This guy needs help said:
All I did was flash the latest file of twrp. Then when it said pass I went straight into download mode and then flashed supersu (the latest version for my phone. After that I rebooted but it only says "set warranty bit kernel" in the top left corner in yellow. I tried this twice but same result (on the second time I flashed fol1 again before I tried).
Click to expand...
Click to collapse
you don't flash SU in download mode... you reboot into recovery to flash it.
mgp53 said:
you don't flash SU in download mode... you reboot into recovery to flash it.
Click to expand...
Click to collapse
Sorry I mean I went in to recovery mode and flashed it
When you rooted did it say "set warranty bit kernel " when you booted back to Android after flashing supersu with twrp?
thisisapoorusernamechoice said:
I need logs or something, because as I've said, "set warranty bit kernel," isn't a problem, that's normal and expected. I can't know what's wrong with your device with no information.
Did you try starting from the beginning? Flashing the stock OL1 Odin file, booting that up (not setting anything up except a Wi-Fi connection), and trying rooting with that? Did you try opening the TWRP tar file with 7zip or WinRAR and extracting the img file to verify the download wasn't corrupted? Did you try doing a similar check with the superSU zip? What version of supersu are you trying to use? Have you tried clearing cache and dalvik after installing supersu (not necessary but sometimes helps clear up issues)?
Click to expand...
Click to collapse
Do I have to factory reset to root with this method?
This guy needs help said:
Do I have to factory reset to root with this method?
Click to expand...
Click to collapse
No
I found it out
For some reason I had to clear the cache and dalvik cache after the flash. That did it now I'm rooted!
This guy needs help said:
For some reason I had to clear the cache and dalvik cache after the flash. That did it now I'm rooted!
Click to expand...
Click to collapse
Hi!! Okay, I am having the same problem you had and need to know exactly what you did to fix it.
I followed the instructions exactly. I am stuck on the "set warranty bit kernel screen. I want to know what you did to fix this.
(When you were flashing the supersu for the second time, before you had to clear cache and dalvik, did you just go into recovery mode and flash it again, or did you have to delete something before you did that)
Please get back to me anyone, advice needed!
I cleared the caches before i rebooted into the system ( well i think this is what i did , it was a week ago) good luck bud?
ktberr said:
Hi!! Okay, I am having the same problem you had and need to know exactly what you did to fix it.
I followed the instructions exactly. I am stuck on the "set warranty bit kernel screen. I want to know what you did to fix this.
(When you were flashing the supersu for the second time, before you had to clear cache and dalvik, did you just go into recovery mode and flash it again, or did you have to delete something before you did that)
Please get back to me anyone, advice needed!
Click to expand...
Click to collapse
Oh yeah i forgot. You need to say no if twrp says to you " your phone appears to not be rooted , do you want root " because this just bricks your phone. P.s. my phone is rooted and is still says it but it is not true because it just bricks your phone
I tried to root my Samsung Galaxy S5 using Odin and an autoroot file. After that failed, I researched how to restore my phone to its original OS. I have not been able to do that either. I either can only boot to the Odin Mode screen or am locked on the T-Mobile logo screen.
BTW, I am new to phone rooting so more detailed explanations would be appreciated.
Are you able to boot to recovery? [ home+volume up+power]
If so you can reset from there.
If not you should be able download the stock firmware and flash it with Odin.
FOL1 is the latest - it takes a long time to download from Sam's.
http://www.sammobile.com/firmwares/database/SM-G900T/
Jim
otisdog is right, sammobile takes forever to download which is why you should download the exact same file they linked to, but from here:
https://www.androidfilehost.com/?fid=24407100847293882
Since cf-autoroot didn't work for you, 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. Now wipe cache and dalvik
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.
Thanks OtisDog and thisisapoorusernamechoice.
While I am downloading TMB-G900TUVS1FOL1-20160111153316, I tried your directions for installing TWRP and had success. I was able to boot into TWRP. (First boot success since I started 10 days ago.) I downloaded supersu zip and have it on my Windows 10 computer. I assume that I do not unzip it in Windows, correct?
From TWRP I clicked on Install and got the phone's files. When I clicked on Select Storage, the USB storage choice has 0MB so the option is disabled. Should I have started TWRP with my USB cable still connected? My computer still recognizes that I am connecting something to it while TWRP is running.
If that is not the problem, how do I install supersu zip into my phone?
Dave4237 said:
Thanks OtisDog and thisisapoorusernamechoice.
While I am downloading TMB-G900TUVS1FOL1-20160111153316, I tried your directions for installing TWRP and had success. I was able to boot into TWRP. (First boot success since I started 10 days ago.) I downloaded supersu zip and have it on my Windows 10 computer. I assume that I do not unzip it in Windows, correct?
From TWRP I clicked on Install and got the phone's files. When I clicked on Select Storage, the USB storage choice has 0MB so the option is disabled. Should I have started TWRP with my USB cable still connected? My computer still recognizes that I am connecting something to it while TWRP is running.
If that is not the problem, how do I install supersu zip into my phone?
Click to expand...
Click to collapse
The supersu zip needs to be in your phone's internal storage or micro SD card. USB storage is not used for this
thisisapoorusernamechoice said:
The supersu zip needs to be in your phone's internal storage or micro SD card. USB storage is not used for this
Click to expand...
Click to collapse
Since my phone has no SD card slot, this sounds like a Catch 22. I can't get my phone to work without installing the supersu zip, but I can't install the supersu zip without getting my phone to work.
Fortunately, the file that OtisDog suggested DID work. THANK YOU. THANK YOU. THANK YOU.
My wife is also thrilled that I don't have a $160 brick. She sends hugs to both of you.
Dave4237 said:
Since my phone has no SD card slot, this sounds like a Catch 22. I can't get my phone to work without installing the supersu zip, but I can't install the supersu zip without getting my phone to work.
Fortunately, the file that OtisDog suggested DID work. THANK YOU. THANK YOU. THANK YOU.
My wife is also thrilled that I don't have a $160 brick. She sends hugs to both of you.
Click to expand...
Click to collapse
You don't need the SD card, you can put the supersu zip file in your phone's internal memory and flash it from there in TWRP. Also if you have a Galaxy S5, you have an SD card slot. It's on top of, yes literally on top of the SIM card slot, can be a little confusing and hard to see until you know what you're looking for (see attached pic for clarification, sorry for my halfassed paint job lol).
thisisapoorusernamechoice said:
You don't need the SD card, you can put the supersu zip file in your phone's internal memory and flash it from there in TWRP. Also if you have a Galaxy S5, you have an SD card slot. It's on top of, yes literally on top of the SIM card slot, can be a little confusing and hard to see until you know what you're looking for (see attached pic for clarification, sorry for my halfassed paint job lol).
Click to expand...
Click to collapse
Thanks for the photo. That helps.
My latest problem is that every time I restart my phone, some shortcuts (Hi, Google; Gallery; magazines; exercise; camera) are added to my home screens and the default home screen is changed. I suspect that by clearing one of the caches, I can fix this. What do I need to do?
You can go into settings and find "backup and reset".
In there uncheck the backup and then do the factory reset. This will wipe all data and reload the os like when the phone was new - you can then put on it what you want.
MAKE SURE you have anything that's on the phone now, that you want, backed up on your computer because it will get wiped off the phone.
Once you get the phone to where you want it we can work on rooting it.
Jim
The instructions from thisis... worked great for me, although I accidentally did a full wipe from TWRP - no biggie, I was backed up. Thanks!
I appreciate the clear and concise instructions I've seen so far, I got as far as flashing superSU zip and wiping cache and dalvik, what next?
NexMortifer said:
I appreciate the clear and concise instructions I've seen so far, I got as far as flashing superSU zip and wiping cache and dalvik, what next?
Click to expand...
Click to collapse
Reboot lol
Sent from my SM-N920G using XDA Labs
ShinySide said:
Reboot lol
Click to expand...
Click to collapse
wouldn't it be nice if that just worked?
sorry, enough sarcasm, I'll clarify, I got that far with everything going as intended, but after reboot, it's not rooted (according to rootchecker) and I don't know why. Additional device info:
SM-G900T
running 4.4.2 (it doesn't want to let me update for some reason, and I thought maybe old versions might be easier to root)
Baseband Version G900TUVU1CNK2
Build # is KOT49H.G900TUVU1CNK2
(if there's other info you need, let me know.)
NexMortifer said:
wouldn't it be nice if that just worked?
sorry, enough sarcasm, I'll clarify, I got that far with everything going as intended, but after reboot, it's not rooted (according to rootchecker) and I don't know why. Additional device info:
SM-G900T
running 4.4.2 (it doesn't want to let me update for some reason, and I thought maybe old versions might be easier to root)
Baseband Version G900TUVU1CNK2
Build # is KOT49H.G900TUVU1CNK2
(if there's other info you need, let me know.)
Click to expand...
Click to collapse
Yeah that's weird. Since you're running kit Kat should of installed system root. Or maybe I'm wrong on the zip being able to root kitkat/use system root instead of systemless.
Open the supersu app and see if it asks to update su binary
Otherwise I'd just try flashing it again in twrp or finding a much older supersu zip to flash. (Probably a 1.×× version)
You don't need to wipe caches tho.
Sent from my SM-N920G using XDA Labs
ShinySide said:
Open the supersu app and see if it asks to update su binary
Click to expand...
Click to collapse
App isn't showing up either, don't know if that's useful info or not.
NexMortifer said:
App isn't showing up either, don't know if that's useful info or not.
Click to expand...
Click to collapse
You are flashing it in twrp correct?
Because you should have SuperSU installed then
Sent from my SM-N920G using XDA Labs
ShinySide said:
You are flashing it in twrp correct?
Because you should have SuperSU installed then
Sent from my SM-N920G using XDA Labs
Click to expand...
Click to collapse
Yes, I did, and no, it didn't.
Well, I eventually gave up on that root technique, and ended up using This instead, so now I'm running 6.0.1, and it seems to be working alright, but SuperSU says "The SU bianary needs to be updated!" and when I click it, it offers me the options of "normal" and "TWRP/CWM" as ways to install the SU bianary.
I know just enough to know that I don't know what I'm doing, and thought I'd get some advice before I proceed to screw something up.
Which option should I go for, and if TWRP, do I need to re-flash it with Odin like I did to install the 6.0.1 ROM, or is the process different now?
NexMortifer said:
Well, I eventually gave up on that root technique, and ended up using This instead, so now I'm running 6.0.1, and it seems to be working alright, but SuperSU says "The SU bianary needs to be updated!" and when I click it, it offers me the options of "normal" and "TWRP/CWM" as ways to install the SU bianary.
I know just enough to know that I don't know what I'm doing, and thought I'd get some advice before I proceed to screw something up.
Which option should I go for, and if TWRP, do I need to re-flash it with Odin like I did to install the 6.0.1 ROM, or is the process different now?
Click to expand...
Click to collapse
I always just click normal. Then it'll ask to reboot and just allow it and you'll be good to go
Sent from my SM-N920G using XDA Labs
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
use that guide, follow it precisely and you will be fine