Related
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Anyone? Any suggestions at all will be appreciated
No1ustad said:
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Click to expand...
Click to collapse
Sure... You can flash a rom immediately following the flash of cwm.... Did you also install busy box?
Which cwm are you trying to use? 5.8.4.7 seems to do me good....?
Sent from my SPH-L710 using xda premium
Before your phone boots after installing cwm in Odin do a battery pull then boot into recovery （Volume Up+Home+power) then flash your superuser/root package. It will stick then.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Naddict said:
Sure... You can flash a rom immediately following the flash of cwm.... Did you also install busy box?
Which cwm are you trying to use? 5.8.4.7 seems to do me good....?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I tried using that CWM version as well as an older one. Both work and I can get busy box and superuser installed once it boots up. But when I power down and try to go back into recovery, CWM is gone. I do get to keep root though.
iiApotheosis said:
Before your phone boots after installing cwm in Odin do a battery pull then boot into recovery （Volume Up+Home+power) then flash your superuser/root package. It will stick then.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I tried unchecking the auto-reboot button on Odin 4 and 7, and going that route. Both allow me to get into CWM, where I try to flash the recovery v5.zip. Still doesn't stick unfortunately.
My flash counter is up to about 10 now, trying to get CWM to stick..
No1ustad said:
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Click to expand...
Click to collapse
Flashing 5.8.4.7 after renaming it to recovery.img with mobile odin did the trick for me and it stuck.
I used this guide below
http://forum.xda-developers.com/showthread.php?p=28687877
Sent from a Third Galaxy
cbond007 said:
Flashing 5.8.4.7 after renaming it to recovery.img with mobile odin did the trick for me and it stuck.
I used this guide below
http://forum.xda-developers.com/showthread.php?p=28687877
Sent from a Third Galaxy
Click to expand...
Click to collapse
Thanks everyone. I used CWM toolkit, reflashed the stock recovery, then used odin 3.07 to re-flash CWM 5.5.0.4 and it stuck.
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?
Hi, im using CM11 nightly GT-i9100G.. After finish flashing, after updating binary on SuperSU, it ask me to reboot (recommended). When i reboot onto recovery mode, and install aidfarh kernel, it ask me to fix root. everytime if im booting into recovery. Why is that? Please help me. TQ
khyriel said:
Hi, im using CM11 nightly GT-i9100G.. After finish flashing, after updating binary on SuperSU, it ask me to reboot (recommended). When i reboot onto recovery mode, and install aidfarh kernel, it ask me to fix root. everytime if im booting into recovery. Why is that? Please help me. TQ
Click to expand...
Click to collapse
U dont need to select recovery method when super su asked u to updtae su binary.
Thats for htc devices.
Select normal install method
SENT USING VIVELROM_OMNI
corruptionfreeindia said:
U dont need to select recovery method when super su asked u to updtae su binary.
Thats for htc devices.
Select normal install method
SENT USING VIVELROM_OMNI
Click to expand...
Click to collapse
I do select the normal one. but this is when i reboot into recovery mode. its gone now after o change to TWRP recovery from CWM recovery. i will do a backup and see what will happen next.
after update to latest nightly 4.4.2 KK, i make a backup in Nandroid using CWM Recovery, after finish doing backup, it ask me to fix root? am i the only 1 having this? Just a question.
khyriel said:
after update to latest nightly 4.4.2 KK, i make a backup in Nandroid using CWM Recovery, after finish doing backup, it ask me to fix root? am i the only 1 having this? Just a question.
Click to expand...
Click to collapse
Flash supersu.zip
It's available both in infected omni and vivekrom omni thread.
Sent from my GT-I9100 using Tapatalk 2
This is a tutorial for noobs or members who are new to Rooting and want to root their phone.
Downloads:
*Odin 3 v3.0.9
*CWM recovery thread(Downloads available for 4.3 and 4.4 also)
*SuperSU
Steps to root your phone:
1) Download the first two files given above to your laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Vol.down+home+power buttons at the same time for about 7-8 secs)
4)Open the ODIN file you downloaded on your laptop/pc.
5) Connect your phone to your laptop/PC through USB cable(do I have to tell that )
6) When ODIN detects your phone, the ID:COM area will become yellow/blue
7) In ODIN click on PDA and then select the recovery file you downloaded. Also tick the check box beside PDA(if there is any)
8) Click on start. The flashing process will start.
9) If the flashing succeeds, ODIN will show 'PASS'. That means the recovery flashed successfully. Yay!!!
10) Now turn on your phone and download the third file and place it in your external SD card.
11) Turn off your phone.
12) Reboot to recovery(by pressing Vol.up+home+power buttons).
13) The recovery will start. You have to navigate by volume buttons and power button.
Vol.up - move up
Vol.down - move down
Power button - select option
14) Select 'install zip'.
15) Select 'Choose zip from ext_sd or external SD card'.
16)Select the third file you downloaded. Flashing process will start.
17) After it finishes, go back and reboot your phone.
It's upon you, of you want to follow this:
18)Use Knox Remover to remove all Knox files.
Enjoy your rooted Galaxy grand 2!!! Now you can flash other recoveries or flash other custom ROMs or custom kernels.
Some useful tips(Experimental/WIP):
You can use Triangle Away to reset the flash counter after flashing ROMs and make your device status from custom to official. This is a really useful app. Report here if it works. You needn't download from google play, you can scroll down and download from the attachments.
CREDITS:
@shabbypenguin: For CWM recovery.
@Chainfire: For SuperSU and Triangle Away.
@AL_IRAQI: For Knox remover.
Its working or not
Sent from my SM-G7102 using XDA Premium 4 mobile app
Will this work on Kitkat 4.4.2
viewedit said:
Will this work on Kitkat 4.4.2
Click to expand...
Click to collapse
yep.
##W4TCH0UT## said:
yep.
Click to expand...
Click to collapse
I did what was in description,, It didnt work on 4.4.2, but it has modified the phone,, as when I try update it says phone has been modified, try to update through kies...
viewedit said:
I did what was in description,, It didnt work on 4.4.2, but it has modified the phone,, as when I try update it says phone has been modified, try to update through kies...
Click to expand...
Click to collapse
you need to flash supersu in recovery, load up supersu when you have rebooted and have it disable knox, then reboot into recovery and reflash supersu and youll be rooted.
Have you tested it?
sbsharma said:
Have you tested it?
Click to expand...
Click to collapse
I don't have this device, but I think shabbypenguin is right. Follow that method for kk. I'll update the thread, once kk recovery is released.
Sent from my GT-I9082 using Tapatalk
I used towelroot v1 to root my G7102 on JB 4.3
I flashed the indian stock rom to get the update to kitkat and now downloading the update for kitkat
after updating I will test towelroot on 4.4.2 and post results
sbsharma said:
Have you tested it?
Click to expand...
Click to collapse
##W4TCH0UT## said:
I don't have this device, but I think shabbypenguin is right. Follow that method for kk. I'll update the thread, once kk recovery is released.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Similar, I'm in teh US with a nexus 5, in no way shape or form will i ever hold this device in my hand so no way for me to test it out.
there will be no kitkat recovery, the mere fact he booted to recovery and was able to flash the supersu means that is is working. the cwm i put out is already compatible with 4.4
I had even flashed the super user it failed saying couldn't verify signature. When u boot in recovery it doesn't say CMW recovery. In the center of the screen under the logo it says no command and down in the screwn it says manual mode.
About knox I checked there is nothing I can disable. while in recovery..
I have used Cwm in s2. . So I know it's interface..
shabbypenguin said:
you need to flash supersu in recovery, load up supersu when you have rebooted and have it disable knox, then reboot into recovery and reflash supersu and youll be rooted.
Click to expand...
Click to collapse
Sent from my SM-G7102 using Tapatalk 4 Beta
viewedit said:
I had even flashed the super user it failed saying couldn't verify signature. When u boot in recovery it doesn't say CMW recovery. In the center of the screen under the logo it says no command and down in the screwn it says manual mode.
About knox I checked there is nothing I can disable. while in recovery..
I have used Cwm in s2. . So I know it's interface..
Sent from my SM-G7102 using Tapatalk 4 Beta
Click to expand...
Click to collapse
you had stock recovery not cwm
One last Question
Well then the CWM didnt flash through odin,, its funny bec Odin gave all the indication that it successfully flashed the recovery.. Just one last thing I need to know,, I am sure somehing is broken at the recovery/software level now..as when I check for software update, it says ur device has been modified,, how do I fix this.. flashing stock 4.4.2 rom?
shabbypenguin said:
you had stock recovery not cwm
Click to expand...
Click to collapse
You need to uncheck auto reboot in odin. When it finishes flashing disconnect the device and pull battery. Then put it back in and manually boot to recovery
Sent from my Nexus 5 using XDA Free mobile app
Is this process work on sm-g7105 ?
AnTeBiOs57 said:
Is this process work on sm-g7105 ?
Click to expand...
Click to collapse
Don't know. You can try and post here if it works.
Sent from my GT-I9082 using Tapatalk
Booterror
##W4TCH0UT## said:
Don't know. You can try and post here if it works.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
I have "Could not do normal boot" when I boot to recovery
b0rni67 said:
I have "Could not do normal boot" when I boot to recovery
Click to expand...
Click to collapse
use teh new cwm thats for ng4
Help me? NG4?
shabbypenguin said:
use teh new cwm thats for ng4
Click to expand...
Click to collapse
Sorry, what Device is NG4? SG4?
6.0.3.2 for Samsung Galaxy S4 (i9500) ?
Thxs
No. NG4 is the build number of the new 4.4 update for the g7102
Sent from my Nexus 5 using XDA Free mobile app
so, simple, i can't find a goot tutorial on how to flash a recovery, i tried with odin 3.0.4 and i've flashed twpr 2.8.6.1, cwm 6.0.4.7 and another cwm version, after the flash with odin if i restart the phone i still have the original recovery
for now i manage to root it following this: http://forum.xda-developers.com/galaxy-s3/help/how-to-root-galaxy-s3-i9300-android-4-3-t3104969
now let's see if i can flash the recovery with rom manager or odin mobile
done using rom manager, thanks anyway
When you were using Odin did it automatically restart? Or did you uncheck that option?
Phantogenic said:
When you were using Odin did it automatically restart? Or did you uncheck that option?
Click to expand...
Click to collapse
i'm not sure honestly, i think it automatically restart
Letting it auto restart means the stock recovery reinstalls. You need to let it finish without a reboot. Then do a battery pull and then try boot into recovery. Then it will stick.
Phantogenic said:
Letting it auto restart means the stock recovery reinstalls. You need to let it finish without a reboot. Then do a battery pull and then try boot into recovery. Then it will stick.
Click to expand...
Click to collapse
i've already fixed btw, i let it auto restart then i used rom manager and flashed the recovery