Database Users

[Q] Stuck at boot screen after TWRP asking if I want to install SuperSU

I have to think I'm not the first to be in this situation but my searches didn't turn up anything that looked familiar.
I rooted the stock phone and installed TWRP 2.6xx a month or two ago with no issues. Everything's been running great and I decided it was time to make another backup using TWRP.
After a successful backup I wiped dalvik and cache out of habit and went to reboot -- TWRP said I was not rooted and wanted to know if I wanted to install SuperSU? This question was unexpected since I'd been rooted for a long time, and I decided to just say yes. The phone rebooted and stopped at the Samsung Galaxy S4 boot screen. I did up-volume reboot to recovery, but it seemed to hang at the TWRP blue screen -- I later discovered it will eventually get to the menu after a minute or two of the blue screen. I tried wiping cache and dalvik again and rebooting -- every time I try to reboot now it asks if I want to install SuperSU -- whether I say yes or no seems to make no difference -- I've tried both several times. Every time it hangs at the Samsung boot screen, or it takes forever to get to TWRP if I'm booting to recovery.
I've tried wiping cache, dalvik and data with no improvement. I finally tried formatting data, but again no improvement. I also tried restoring my backup several times and wiping cache and dalvik but still stuck.
I prior to today's problems I'd used TWRP a number of times and I don't recall it asking the SuperSU question, so I am thinking that is the key to this problem, and I'm wondering if anyone knows what it means?

You need to go to 2502 twrp, 26+ has hanging problems and possible Partition issues, also what rom are you on? Do you need to flash super su along with the rom /gapps?
Here's the twrp forum for us SPH-L720
The last page has a download link for the most stable build for us good luck!
http://forum.xda-developers.com/showthread.php?t=2262999

I'm running what came on the phone, just unlocked, rooted, and installed TWRP.
I ran CM10.1 on my previous phone and currently on my tablet, but my impression from running it previously is CM is a downgrade in voicemail functionality (you get these annoying text messages and have to call the voicemail), and I'm assuming it doesn't support the special GS4 hardware features like being able to hover your finger.

OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.

Nerva said:
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Click to expand...
Click to collapse
How did you root? CF auto root also installs SuperSU
Do you have a back up from when you were rooted? IF twrp keeps giving you problems, use cwm, are you able to get past the Samsung boot..

Yeah that's what I did back when I rooted it months ago. I tried running CF auto root again today and it didn't work, so I ran it from Odin and it did work that time, but there was no change -- still hangs on the Samsung boot screen, although now I'm back to the stock recovery. So I tried installing the stock MF9 firmware from Odin -- still hangs on the boot screen. I don't know what to do at this point...

After mf9 install avd stock recovery did you factory reset

Yes, I did a factory reset -- followed the video instructions by qbking77. Still hangs on the boot screen.

Take out battery.. Put back in. Go to stock recovery, holding all 3 buttons volume up factory reset.. If you used odin abd flashed mf9 it should fix you?
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Well I guess I tried man, someone who has more knowledge should chime in now
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
This
http://forum.xda-developers.com/showthread.php?t=2400192

Im also stucked with the same problem!! After flashing my rom succesfully it just ask ur device is not rooted swipe to install!! I tried all the posiblities!! but i stuck with the boot image!! pls help me!!

From experience it sounds like you should head over to sammobile and Odin back to stock and start fresh.
1. Odin to stock
2. Root phone
3. Put desired recovery
4. Flash ROM (be sure to read dev install instructions some require reboot of recovery after wipe)
5.try to restore backup (best if you flash ROM that is backup then restore backup)
6.if you went into nae or ng2 you cannot downgrade to me
7.google has many solutions
Sent from my SCH-I545 using XDA Free mobile app

Sorry for necro, but did anyone figure out a solution to this? This just happened to me.

Just Reflash it
We have the same issue, tried to install supersu binary, after installing through twrp recover, my phone went bootloop, as i've tried to search the internet, the issue doesn't fix by by most of the users unless they reflash their device. though its a bit hassle starting from zero, but atleast, you got ur device back

This helps me:
1. Run Odin on your computer and, after entering download mode on your phone, establish a connection between your devices with the help of the USB cable.
2.Note: for download mode – power off your smartphone and then press and hold, at the same time, the Power, Volume Down and Home buttons.
3.Odin will try to recognize your device; if everything works as expected, on the program the “added” message will be displayed and the ID:COM field will be turned yellow, or blue. (Note: if that’s not happening, unplug the USB connection, close Odin, force restart your phone and reinstall the USB drivers on your computer before retrying the steps from above)
4.From the program click on the “PA” button and load the custom recovery image; don’t check Re Partition and Auto Reboot options.
5.When done, click on “start” and wait while TWRP recovery is being added on your phone
6.In the end, Odin will display the “pass” message and the ID:COM filed will be turned green (or other color) with message - RESTART; you can then remove the USB cord and reboot your smartphone.

I have had this prob on a few things , if you have a backup,flash any mod that will go to the device will do then run the backup and reflash should work .and if you have twrp try to reformat all but the system and see if that helps.
Good luck.

Hi to everyone.
Today, I installed the TWRP and the ROM and both were installed correctly on a Le Pro3 X722. The problem started when the Google services were updating. Suddenly, the phone restarted and entered in a bootloop. I was not even able to enter the TWRP. The page freeze on LE-Recovery logo and then crashed (fill full of lines). I disconnected the battery for a while and then, I was able to enter the TWRP for 2 time but recovery crashes in few seconds. I wanted to wipe and install a clean rom but I cannot enter TWRP anymore.
Please, Is there someone that could help me?
Thank you very much in advance
PS. My phone is not recognized via ADB. I tried with the AIO Tool but my device is not detected.

Hi, I followed the whole process for Qfil explained here:
Leeco Le Pro3 x720 Hard Brick
So the phone was running lineageos 15.1 nightly from 22.08 which i guess was kind of really unstable (even opening twitter in the morning could turn off the device. It could be turned back on right away though), xposed framework v90 w/yt...
forum.xda-developers.com
Installation was correct but nothing change in my phone:
- same start page and bootloop
- Same problem trying to access the recovery.
Now, i can connect via fastboot and I would like to install a fastboot rom (preferable EUI stock 20) but I cannot find one. All links are dead.
Thank you very much in advance

Strange Wifi Problem

Background: So i bought this used S5 900f from someone and it gave me "recovery is not seandroid enforcing" error while rooting and installing recovery. i found a workaround for this error by immediately pulling the battery trick after root. I have installed TWRP and root and they work but this "Recovery is not seandroid enforcing error" still displays when i try to enter recovery for about 2-3 seconds and then the recovery boots.
Now the Problem is : My s5 900f is not saving Wifi password on any of the lollipop builds i have tried Many UK 5.0 (BTU) Builds from Sammobile , and Nordic Countries 5.0 as soon as i restart or shutdown m phone Wifi password is reset and i have to enter it again after turning my phone on again. Surprisingly When i downgrade to any of the kitkat Builds Wifi starts saving passwords just fine?
Things i have tried
Format, Clear dalvik cache, cache, data, system, internal Storage and install different 5.0 builds.
Enabling disabling Google backup, it doesn't help.
Kindly Help me out does Wifi not saving password has anything to do with this "Seandroid not enforcing Error" . And how to fix this issue i am at verge of smashing this phone. .....:angel:

http://forum.xda-developers.com/galaxy-s5/general/s5-forget-wifi-passwords-reboot-fix-t3105976

Thanks alot buddy, you just saved my phone....Phewwww do you know why it happened in the first place?

Buggy ROM is all I can think, it happened to me with a clean install of the latest LP ROM so I went looking for a fix for myself
I tweeted to Samsung UK about it, and they just talked to me like I was stupid, I guess they don't want to admit to it being their fault

UPDATE NOW after the build prop fix, i rebooted fine once... After installing TWRP the phone is crashing on boot up....touchwiz crashes along with all other programs it wont let me boot up. Maybe TWRP messed something up.

Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it

*Detection* said:
Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it
Click to expand...
Click to collapse
does your phone display "recovery is not seandroid enforcing" just before entering twrp? i tried clearing cache and battery pulling didnt work....now flashing earlier 5.O btu.

Yea, just means it's a custom recovery

*Detection* said:
Yea, just means it's a custom recovery
Click to expand...
Click to collapse
Some folks are able to flash any 5.0 build and they don't get the Build.Prop issue. i just reflashed and the issue came back...will re edit the build.prop till now i have rooted + installed TWRP no issues so far only build.prop left to be edited..... could you please tell me why is it persistent on some phones that even reflashing, formating doesn't help.

Unfortunately Nothing works....I have been more than patient with this device...been flashing and trying different things for 18 hours now. It works fine but after going to recovery (Just by entering it) and then rebooting will freeze my phone with "Unfortunately Media storage has stopped working...and everything else like touchwiz also crashes".......i was so...so wrong to move to a samsung This Definitely is my last samsung phone...for now i will keep trying different things.

Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are

*Detection* said:
Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are
Click to expand...
Click to collapse
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks

dork997 said:
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks
Click to expand...
Click to collapse
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted

*Detection* said:
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted
Click to expand...
Click to collapse
Thanks for your Help, i guess this problem is too complicated. Anyway this time i installed Philz recovery > formatted everything > remove user content and data > custom formatted everything > flashed 5.0 BTU. and surprisingly its saving WiFi passwords without any build prop changes. So i am going to leave it here . 5.0 Unrooted with stock recovery everything working (FOR NOW) . This time i used Odin 3.10 instead of 3.07. I hope it does not get stuck at boot logo and start crashing. Only one problem it kept connecting to "update server" evem tho i had disabled the auto update option from settings>about >updates . i restarted immediately hopefully it wont try to update again. Thanks again for your help.

[Q] Attempted to install TWR & SuperSU - T330 won't boot past Samsung Logo

I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.

SebringTech said:
I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.
Click to expand...
Click to collapse
Have you tried wiping dalvik and cache through recovery? If that doesn't help maybe do a factory reset before restoring the factory image?
Sent from my SM-T330 using Tapatalk
Edit: I think this might be what you need
http://forum.xda-developers.com/showthread.php?t=3176668

I tried to wipe cache and dalvik - still gets stuck at the Samsung logo... Tried to do a factory reset from TWRP and after rebooting from recovery it continues to get stuck. I'll try flashing the kernel but I don't understand why that would have gotten messed with from flashing the recovery and installing the SuperSU part.

Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!

SebringTech said:
Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!
Click to expand...
Click to collapse
You're very welcome. Good luck.
Sent from my SM-T330 using Tapatalk

Screen stuck on preparing to start.. starting app.. after flashing crdroid 6.0.1

I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.

khushboop said:
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
Click to expand...
Click to collapse
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.

sk.shehbaz said:
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
Click to expand...
Click to collapse
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.

khushboop said:
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
Click to expand...
Click to collapse
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/

sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.

khushboop said:
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
Click to expand...
Click to collapse
I still have no idea why it got bricked. So after searching on google and youtube I came across this: https://androidmtk.com/download-yu-stock-rom-for-all-models . I followed the steps and now KitKat is running except launcher is not working, instead play store open's every time I try to go to home screen. So tried the nova launcher but that still doesn't work with home button, have to open through playstore->my apps, every time. But rest is working.

sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
dude!! i tried the above method and thankfully my phone is working now the only major problem now is whatsapp is not opening...when clicked opens for 0.01 sec and returns back to previous screen (flashes) ....please somebody help me with this. Anybody can help me, Thanks in Advance.

Boot loop after trying to install an older version of Magisk

I had Magisk 16.0, but Magisk Hide didn't work very well. I wanted to see if it would work with Magisk 14. Not it's stuck in a boot loop. It shows the "Samsung Galaxy S8 powered by android" for a few seconds then reboots. I can still boot into TWRP recovery and access the storage. Download mode works too. I tried uninstalling Magisk and flashing the stock boot image. Neither worked. Is there anhthing I can do to make my phone work again without losing my data?
Update: if I have to flash the stock ROM, I'm planning to do the next thing: back up my data partition to an external hard drive with TWRP. After I flash the ROM and wipe everything, I want to reinstall TWRP and restore that backup. Would this cause any issues?

vladone97 said:
I had Magisk 16.0, but Magisk Hide didn't work very well. I wanted to see if it would work with Magisk 14. Not it's stuck in a boot loop. It shows the "Samsung Galaxy S8 powered by android" for a few seconds then reboots. I can still boot into TWRP recovery and access the storage. Download mode works too. I tried uninstalling Magisk and flashing the stock boot image. Neither worked. Is there anhthing I can do to make my phone work again without losing my data?
Click to expand...
Click to collapse
I think you cant, since your phone is bootlooped there is no way to get your data back ..
You should backup your data even before root your phone ..
Just flash latest TWRP img.tar from odin, disable auto reboot from the options on odin , after the success flash you need to press the buttons to enter recovery mode .
https://android.gadgethacks.com/how...-s8-into-recovery-mode-download-mode-0177223/

StonebridgeGr said:
I think you cant, since your phone is bootlooped there is no way to get your data back ..
You should backup your data even before root your phone ..
Just flash latest TWRP img.tar from odin, disable auto reboot from the options on odin , after the success flash you need to press the buttons to enter recovery mode .
https://android.gadgethacks.com/how...-s8-into-recovery-mode-download-mode-0177223/
Click to expand...
Click to collapse
I already have TWRP.