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?
So I'm rooting my best friend's Vibrant, which is on Froyo. I did all the workarounds needed to root while on Froyo and I managed to root the phone and get recovery running (the reinstall packages one). But, I've been trying to install CM11 from recovery and it doesn't let me. First, whenever I picked the zip to install it, it would throw me with the Status 0 error, so either the zip was corrupt or the CWM was too old. So, I downloaded another CM11 and it still threw me the same error, which meant the problem was recovery. With the AIO toolbox, I managed to get a newer recovery running, but when I select the zip it says it couldn't mount /sdcard. And then /sdcard becomes unreadable in recovery until I reboot the phone. /Sdcard can be read fine when booted into the OS so I don't think it's the encryption bug. But, I can't install any ROM, and can't find any other CWM image that's more recent or maybe a TWRP image. What to do?
Sent from my HTCONE using xda app-developers app
Update: I flashed the KK 4.4 kernel and now can't get into recovery, it goes into a bootloop booting into recovery.
Sent from my HTCONE using xda app-developers app
Update 2: managed to enter recovery and flashed CM11. Fixed phone. Close thread if needed.
Sent from my HTCONE using xda app-developers app
Hello everyone...I was running Android HD v40 with philz touch 6.0.4.5. today, I decided to flash boeffla kernel and selected reboot to recovery from the 4 way reboot menu (Wanam Xposed)..the phone rebooted..but instead of the normal recovery menu..all i could see was a blank recovery page with the navigation keys at the bottom..it stayed for a second and rebooted itself, again to the same state. All i can access is the download mode..I tried flashing philz recovery again using odin..the process was a success..but it didnt change anything..what i am planning to do is, go home in the evening and flash a stock rom using odin and see if it makes any changed.
Have anybody had a similar experience? Should I try something else?
sree_rag said:
Hello everyone...I was running Android HD v40 with philz touch 6.0.4.5. today, I decided to flash boeffla kernel and selected reboot to recovery from the 4 way reboot menu (Wanam Xposed)..the phone rebooted..but instead of the normal recovery menu..all i could see was a blank recovery page with the navigation keys at the bottom..it stayed for a second and rebooted itself, again to the same state. All i can access is the download mode..I tried flashing philz recovery again using odin..the process was a success..but it didnt change anything..what i am planning to do is, go home in the evening and flash a stock rom using odin and see if it makes any changed.
Have anybody had a similar experience? Should I try something else?
Click to expand...
Click to collapse
Yes dude,use Odin for flash the stock rom,and then flash the custom again MAYBE with ADB you can explore the internal storage and save something but i don't know how it works sorry
sree_rag said:
Hello everyone...I was running Android HD v40 with philz touch 6.0.4.5. today, I decided to flash boeffla kernel and selected reboot to recovery from the 4 way reboot menu (Wanam Xposed)..the phone rebooted..but instead of the normal recovery menu..all i could see was a blank recovery page with the navigation keys at the bottom..it stayed for a second and rebooted itself, again to the same state. All i can access is the download mode..I tried flashing philz recovery again using odin..the process was a success..but it didnt change anything..what i am planning to do is, go home in the evening and flash a stock rom using odin and see if it makes any changed.
Have anybody had a similar experience? Should I try something else?
Click to expand...
Click to collapse
Try to flash again using the newest version (6.15.4): http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300
Sent from my GT-I9300 using Tapatalk
I have a similar issue... But without recovery menu.
Just boot loop with "No command". Odin does not see phone (drivers OK).
Help me please!!!! I've rooted my samsung galaxy young GT-S6310N a few days ago. I used odin 3.07 to flash CWM recovery in my phone. That was an easy process and after installing CWM recovery I choose reboot then some options appeared and I selected 'Root device' (or something like this I can't remember now) then my phone booted well and I installed SuperSU. everything was well untill I booted my device again into CWM recovery by pressing home+vol(up)+lock button. I tried to create rom backup but it said, " can't mount /sdcard " I tried this two or three times but all the same. Then I went back and selected 'reboot' but my phone rebooted to CWM mode again! Every time I selected reboot but the device rebooted again and again into CWM mode. So I wiped data, wiped cache..... but still phone boots into CWM mode. I took out the battery and inserted after a few minutes. But same result. Now what to do..... Please help......
(forgive me for my bad english)
I think you have pressed the "reboot recovery" button on recovery.. am i right??
Sent from my GT-S6312 using XDA Free mobile app
yes!!! I selected reboot recovery!! so this is the problem!! however I fixed this by flashing cwm again via odin. now it's ok. I'll never do that again!!
Sent from my Galaxy Young GT-S6310N using XDA Premium 4 mobile app
[URGENT HELP]
I was updating apps from playstore. So there was an update for superuser and i updated it as well. After the update superuser asked for some binary file update and had an option for installation through CWM/TWRP Recovery . Since i had it installed i selected that option and the phone botted to recovery and then nothing happened. I was expecting it to auto install. I try to reboot the phone but it boots to recovery everytime. What can i do to solve this? i dont want to flash a ROM because i need to backup contacts first
Next time, choose the "normal" option.
For your problem, reflash CWM through Odin or flash stock recovery.
Sent from my Nexus 5 using Tapatalk
freitaz said:
Next time, choose the "normal" option.
For your problem, reflash CWM through Odin or flash stock recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks Man! Worked phew.!