SM-G930F freeze reboot TWRP problem - Samsung Galaxy S7 Questions and Answers

Hello.
My SM-G930F stock ROM was rooted with TWRP 3.3.1-0 from many years ago.
Until a few months ago i was facing somes freeze and reboot.
Now it's getting worse ,it freeze and reboot often (more than 5 times a day) and it freeze also at Samsung boot logo and need Download mode (Home + Volume down + Power) for power off but often still freeze at boot logo again.
In Download mode ,when i flash any others TWRP than 3.3.1.0 and reboot in Recovery ,it show the right flashed TWRP but in yellow mode (can do nothing , like freezed).
It only accept TWRP 3.3.1.0 but problems are same.
I flashed the whole latest stock ROM G930FXXU8ETI2 ,so loose TRWP but seems ok .
Now i flashed TWRP upper than 3.3.1.0 but still yellow mode, only 3.3.1.0 work but freeze come back.
I think NAND is corrupted in Recovery ,and when reading a particular part of it ,it freeze.
How test NAND?
Thank you for reading.

I am facing the same situation with my note FE. Until a few months ago I was using the same TWRP version on stock pie. The freeze then restart occasions started out of nowhere and the kept increasing, and now the phone is not usable. I was thinking of it being a hardware issue, because the restarts are still too frequent in stock pie without any modifications, so I might send it for repair.
I was told about this https://technastic.com/odin-nand-erase-samsung/, but didn't test it yet. Please let me know if you found any solution.

Hello.
roughlyadvanced said:
I was thinking of it being a hardware issue
Click to expand...
Click to collapse
I think too because when boot on official recovery it cannot reboot to system but still reboot to recovery...

Related

The usual: recovery is not seandroid enforcing! FIXED

OK, I know this is a problem that many before had and I've researched the subject thoroughly. But I've only found ways to recover your phone from the soft-brick (one of those fake rubber bricks used in movies:laugh status which was something I did by myself by flashing a stock recovery via odin.
Now my problem is a different one: I have updated my s6 to stock 6.0.1 and all went fine. I then rooted the phone by installing SpaceX kernel and went on to flash recovery via odin. That is when the problem occurred and I've not been able to solve it. I tried flashing also via flashify but with the same result, i.e. phone frozen at the samsung galaxy s6 screen with the damn "recovery is not ......".
What could I try? Anyone knows how to circumvent this issue?
Thanks for any help.
Luca
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
DJPops said:
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
Click to expand...
Click to collapse
Thanks: I will try that right away and report back here. Is the procedure of rebooting and shutting down the phone permanent or is it just the 1st boot (I sense it is a permanent thing, but I hope it isn't). If, later on I flash a custom rom and then re-flash the recovery, will this thing go away?
Why is this seandroid thing happening? Are you able to explain it to me?
It's not permanent
Just the first boot. "It erase a boot script that say to your device to boot into recovery" (small explanation, it's not exactly that).
This happen sometimes when you try to update the Su binary via the SuperSU app (it try to reboot the device into recovery, but sometimes it doesn't work and the device is "stuck" on the recovery)
This message shows up on every boot if you have a custom kernel, and if you boot on recovery, it will maybe shows up (depend of your recovery).
It was stucking on this screen because the recovery that you tried to flash is not compatible with marshmallow bootloader. The link in my first answer is a working marshmallow TWRP, for S6 (not S6 edge/+).
DJPops said:
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
Click to expand...
Click to collapse
Woohoo! It worked! I have a custom recovery, although i have to reboot the phone with a crank
Thanks a lot. Now I'm gonna go on messing it up some more!
DJPops said:
It's not permanent
Just the first boot. "It erase a boot script that say to your device to boot into recovery" (small explanation, it's not exactly that).
This happen sometimes when you try to update the Su binary via the SuperSU app (it try to reboot the device into recovery, but sometimes it doesn't work and the device is "stuck" on the recovery)
This message shows up on every boot if you have a custom kernel, and if you boot on recovery, it will maybe shows up (depend of your recovery).
It was stucking on this screen because the recovery that you tried to flash is not compatible with marshmallow bootloader. The link in my first answer is a working marshmallow TWRP, for S6 (not S6 edge/+).
Click to expand...
Click to collapse
Alas, it seems that it is permanent! It doesn't reboot into anything (neither system nor recovery. Haven't tried download, but I assume it would be the same thing). Furthermore it gets stuck and needs to be rebooted by pressing voldown and power. then it turns on into recovery again. It is a small price to pay, so no worries, but I always like to understand why things happen!
Could I have done another mistake?
Out of interest what random recovery did you give him? lol
Try arter97s mod of twrp 3.0.0-0
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Seems to be the best working mod of latest twrp at the moment. No issues booting etc, just no USB otg support currently.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Out of interest what random recovery did you give him? lol
Try arter97s mod of twrp 3.0.0-0
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Seems to be the best working mod of latest twrp at the moment. No issues booting etc, just no USB otg support currently.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Oh yes!! This one really works all the way, reboot and all. However, af as you know, is there any of the previous version of TWRP that "agrees" with M bootloader?
Thanks mate
Luca
ManhIT modded recovery not a random recovery you know :mrgreen:
Haha, I was just wondering since it was just a mediafire link saying flash this.
Glad that arters recovery worked a bit better for you.
Recovery's are a bit hit and miss at the moment. That's the best one I've found so far.
I still haven't even got marshmallow, still rocking the latest lollipop which suffers similar problems.
Sent from my SM-G920I using Tapatalk
Oh okay, I'm french and I found this link on a french forum...
I used this recovery on my 920F and apart the reboot, it's working perfectly !

Not able to get into TWRP recovery, stuck on "Your device is booting now..."

Not able to get into TWRP recovery, stuck on "Your device is booting now..."
Hey everyone,
I just unlocked my bootloader and now want to flash TWRP and SuperSU. My Phone is already Nougat with Emui 5.
The Problem is that I'm just not able to enter the recovery. When pressing volume down + power or trying "adb reboot recovery" in the command line, the phone starts in the "unlocked bootloader warning screen". But not like in the normal warning screen it doesn't give me options but just shows a white line saying "Your device is booting now..." and thats where it gets stuck. Only gets hotter...
The fun thing is I already was in the recovery but wasn't able to flash the SuperSU (r275). Maybe it was not compatible with Nougat. TWRP just couldn't mount various things. After reflashing the recovery below instead of some other version (don't know anymore) I'm not able to enter the recovery again.
Feels like I searched the whole Internet and there is nearly nobody with the problem or a solution. Tried this as well: https://forum.xda-developers.com/honor-8/help/honor-8-boot-to-twrp-recovery-lost-root-t3567462. It seems like nobody who published a Honor 8 + Nougat + TWRP + SuperSU "How To" acutally tried it himself.
I used this TWRP https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Please help me I can't use WhatsApp because I need to restore it with Titanium (Database way doesn't restore all chats... Other problem)
Thanks everybody I just can't stand this anymore
I had this issue after downgrading to EMUI 4.1 and upgrading to 5.0 again via twrp. I flashed some old 3.0.2.0 version from another developer. Booted into that, flashed the update.zip package for emui 5.0 and then i was able to successfully flash and boot into 3.1.1.0
sysak said:
I had this issue after downgrading to EMUI 4.1 and upgrading to 5.0 again via twrp. I flashed some old 3.0.2.0 version from another developer. Booted into that, flashed the update.zip package for emui 5.0 and then i was able to successfully flash and boot into 3.1.1.0
Click to expand...
Click to collapse
Thank you I got it!
So I got my L09 with Nougat/Emui 5 on it. Then just used TWRP from https://forum.xda-developers.com/showpost.php?p=70228949&postcount=252 (bootable, think ist ist 3.0.2.0) then flashed 3.1.1.0 from https://forum.xda-developers.com/honor-8/development/twrp-t3566563 (bootable) and finally flashed SuperSu from first Link again. Other SuperSU versions (like the phh r275) WERE NOT flashable.
Magisk is the most compatible root solution for the Honor 8 on Nougat. The only thing that doesn't work (seamlessly) is MagiskHide, but the root itself works and flashes fine from TWRP.
I have tried to flash twrp multiple times to no success. I have tried multiple variations of the tool but for some reason when I go try to boot into recovery it takes me to erecovery which fails to do anything.
Are you sure about button combination
If you're trying to boot in to recovery with your phone plugged in to the computer it will także you to erecovery. If only i could find the person who całe up with this stupid idea that caused me hours of struggles, they'd pay for it. also when you use the pwr + vol.down combination let go off the power when you feel the vibration and further hold the vol.down until you see the boot screen appear.
sysak said:
If you're trying to boot in to recovery with your phone plugged in to the computer it will także you to erecovery. If only i could find the person who całe up with this stupid idea that caused me hours of struggles, they'd pay for it. also when you use the pwr + vol.down combination let go off the power when you feel the vibration and further hold the vol.down until you see the boot screen appear.
Click to expand...
Click to collapse
OK so i go to bootloader flash twrp then when i try to reboot ive tried disconnecting from computer and holding vol up and power then when it vibrates release power and hold vol down too. It still just boots to unlocked bootloader screen then to os
Dalg1991 said:
OK so i go to bootloader flash twrp then when i try to reboot ive tried disconnecting from computer and holding vol up and power then when it vibrates release power and hold vol down too. It still just boots to unlocked bootloader screen then to os
Click to expand...
Click to collapse
Try adb reboot recovery in command line on your PC when phone is turned on
0mrwhatsupguy0 said:
Try adb reboot recovery in command line on your PC when phone is turned on
Click to expand...
Click to collapse
I tried this like 20 times but this time it worked! I know have TWRP working. weird think tho is that no keyboard or default Huawei apps are preinstalled and BT isn't working.
Few problems with Binary SU and BusyBox
My phone seems to be rooted. Titanium Backup works but I have to accept every App instalation manually. With other settings restoring gets stuck. Also SuperSU reminds me every time that my BinarySU needs an actualisation but fails if it tries. And finally BusyBox just isn't able to get itself installed.
I'm thinking about restoring stock firmware, update to Nougat, and flash the two TWRP Versions and SuperSU again but hate to spend ours on my phone. OnePlus One rooting was sooo easy...
Dalg1991 said:
I tried this like 20 times but this time it worked! I know have TWRP working. weird think tho is that no keyboard or default Huawei apps are preinstalled and BT isn't working.
Click to expand...
Click to collapse
Is there a number of times you have to do it? How should I transition from this stupid "Your device is an enemy of the state" screen to something that will connect to adb?

black screen when booting into twrp

does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
Hey funny you should say that. I'm actually on my second Asus 3 ultra. The same thing happened to my first one got stuck during a firmware update, or corrupted firmware zip.,now the phone won't boot to twrp or bootloader, just vibrates like yours. If I plug the charging cord in vibrates then just get those red led notification light blinks,computer won't even recognize the device so can't flash the bootloader back to the phone to fix, so I guess it's hard bricked paperweight. I only had it for about a week before the brick, had to buy a new one. The thing that's funny to me the first one would boot to twrp no problem, now this new one seems to boot to twrp but just presented a black screen, it's in twrp recovery because you can feel the vibrations for the buttons, just can't see the screen. I would love to be able to fix the bricked one it's brand new, and can't send for warranty because I'm in the US, sucks.
If you have the address for the foreign country's location of manufacturing, you can send it in for repairs. That's what we are working on doing. The horrible thing is, after reading about stories of other customers, Asus really rakes you over the coals price wise for the repair, & then does similarly for return shipping. So we are still trying to find a way around the high shipping prices, at least.
.
gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
What stock keeping unit (SKU) is your phone? WW, TW, CN, or JP?
What version of TWRP did you flash?
hillg001 said:
You're doing MUCH better than i am. After loading twrp & making a backup, it appears the bootloader corupted when i tested it with the restore. Now, if i try & reboot, all it does is vibrate. If it's pluged in while rebooting, it'll vibrate & the red led blinks. In other words, hard bricked. I got 2 disney tickets offered to anyone who can un-hardbrick it. I've un bricked several Samsung's, but the Zp3ultra has me stumped. If i were you, i'd try reloading the original OS.
Click to expand...
Click to collapse
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
i think the mistake people may be making is flashing stock rom through twrp
twrp only for supersu zip and other things imo
stock rom just flash through the stock recovery apply update from sd (microsd card) need to make sure the recovery and rom match
can you get to stock recovery? also charge it first to a good 80 to 90 if not 100 percent
gubbilo144 said:
does anyone know how to fix this issue im having.i was on android 6.0 when trying to boot into twrp recovery would only have a black screen,only once in a blue moon it will boot into twrp regular.i updated to 7.0 thought it might fix the issue but it is the same .ive tried all the twrp versions through adb,but when booting into twrp just presented a black screen,ive tried factory reset,reflash firmware,still the same.The only way to get to twrp normal is to adb (fastboot/boot/twrp.img/,on my computer
Click to expand...
Click to collapse
After you get that black screen, just press once the power button to close and then press it again to open, just like you do when you normally close and open the screen. You will see after that the twrp interface.
qbchung said:
i got the same problem when i use TWRP to install the oldest rom from asus website UL-ASUS_A001-WW-13.6.6.17-user.zip, the installation completed but i got black screen the same signs like you did, i offer 50 Euros for those who could help me unbrick my zenfone ultra
thanks a lot in advance!!!
Cordially
CHUNG
Click to expand...
Click to collapse
read your post again...noticed...
one thing-if you were on ww-14 i.e. android nougat then cannot simply flash the ww 13 marshmallow as I believe the bootloader is different - think that is why the flash did not work (know this from other zenfone forums where you cannot simply downgrade by flashing a previous android level rom) if it was not a case of downgrading then maybe because of using twrp for stock rom instead of the update process using stock recovery
I tried to flash ww 13 when on ww 14 through stock recovery and it was giving me an error (saying version is not ww which was not the case anyway)-found out through other forums that it is because one cannot downgrade in that manner - therefore I think cause of flash error is the bootloader version. For downgrading one needs the raw file. I found raw file for our ultra (WW13 level) at a Vietnamese site and the flashing tool but have not tried it (no reason to) but am keeping it just in case.
you can get stock recovery from here (note the ww 13 or ww 14 types pick the right one)
https://mega.nz/#F!9tEj2azZ!QKmvc-VJZR1Iqk6H7alQnQ
flash it through fastboot
need to have fastboot drivers installed
https://developer.android.com/studio/releases/platform-tools
or
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
make sure path variable has fastboot folder in it in environment variables of computer
preferably have recovery image in that folder too so you don't have to type some long path names
power off
volume up press and hold then press power
get to bootloader fastboot mode
connect by usb
open command prompt window in folder where fastboot installed
check fastboot devices to verify phone is seen
filename.img = filename of the twrp.img
twrp flash recovery filename.img
if successful then
twrp boot filename.img
may have to press power or volume up to get to the screen
while in stock recovery better to do factory reset too before update
then apply update from sd card
btw I have successfully used the twrp march version 3.2.1 (also at the above mega link) with the latest stock ww 14 (from jan 8 2018) backed up restored successfully, rooted, and have xposed as well
a note on twrp restore if ever having to (just don't check system image restore in twrp when restoring)
trying to do miui port
Can anyone help me???My device isn't opening after twrp flashing.when I reboot I see dark screen,not twrp recovery... please somebody help me,fast.....
Same problem with my iball tablet
Even flashing stock recovery doesn't give me recovery back i have also tried philz recovery but no luck i need help too

Phone stuck at Boot screen after installing TWRP recovery 3.2.1-berlin

I have BLN-L22 device. I installed TWRP recovery 3.1.1- berlin and it installed correctly. Then I found the latest version 3.2.1-berlin on official TWRP app. So I flashed that one and rebooted to recovery. Since then the phone is stuck at the bootscreen which shows 'Phone is unlocked, booting' message.
I can't connect to PC and how can I recover to original?
Official TWRP app (and relative site obviously) leads to a non working build of TWRP, i stumbled upon the same scene too while flashing official 3.1.0 version took by their site... Don't know why. Modded versions of TWRP made by OpenKirin team and HassanMirza01 works correctly instead. Here https://forum.xda-developers.com/honor-6x/development/twrp-honor-6x-hassanmirza01-t3733201 you'll find a working 3.2.1-0 version, i tested it by myself.
Now, to get rid of this and flash a working TWRP, you have to boot to fastboot mode with manual method, so begin with completely shut off the phone by keeping held power button for 10+ seconds.
Then, connect the phone to PC with the USB cable, and boot it up by keeping pressed power button and held down volume - immediately as you hear the vibration. From fastboot, you'll be able to flash back the working TWRP.
Problem Solved
RedSkull23 said:
Official TWRP app (and relative site obviously) leads to a non working build of TWRP, i stumbled upon the same scene too while flashing official 3.1.0 version took by their site... Don't know why. Modded versions of TWRP made by OpenKirin team and HassanMirza01 works correctly instead. Here https://forum.xda-developers.com/honor-6x/development/twrp-honor-6x-hassanmirza01-t3733201 you'll find a working 3.2.1-0 version, i tested it by myself.
Now, to get rid of this and flash a working TWRP, you have to boot to fastboot mode with manual method, so begin with completely shut off the phone by keeping held power button for 10+ seconds.
Then, connect the phone to PC with the USB cable, and boot it up by keeping pressed power button and held down volume - immediately as you hear the vibration. From fastboot, you'll be able to flash back the working TWRP.
Click to expand...
Click to collapse
Hi Thank you so much. The phone was restarting continuously after holding the power button. So I tried by pressing the power and volume down button which took me to fastboot.
Then I could install the compatible version of TWRP successfully.:good:
kpk1307 said:
Hi Thank you so much. The phone was restarting continuously after holding the power button. So I tried by pressing the power and volume down button which took me to fastboot.
Then I could install the compatible version of TWRP successfully.:good:
Click to expand...
Click to collapse
Good job!
RedSkull23 said:
Good job!
Click to expand...
Click to collapse
Hello there!!! help me. i too installed the 3.1 berlin and got stuck.even i have tried installing 3.2 and still i am stuck.no error while installing in both the images though.the screen just got stuck your device is booting..plz help
Venom0425 said:
Hello there!!! help me. i too installed the 3.1 berlin and got stuck.even i have tried installing 3.2 and still i am stuck.no error while installing in both the images though.the screen just got stuck your device is booting..plz help
Click to expand...
Click to collapse
Did you solve your issue.....I am also having same issue now. ..whatever recovery I flash....its get success but still it gets stuck on you are booting now
nokiasatyam said:
Did you solve your issue.....I am also having same issue now. ..whatever recovery I flash....its get success but still it gets stuck on you are booting now
Click to expand...
Click to collapse
You can successfully flash even non compatible images. the problem only arises when you boot them. Simply, they won't be able to boot because they're incompatible.
first, get into fastboot, flash compatible recovery(they are different for emui 5 and 8, so check before you flash). Then boot to recovery by pressing and holding power and volume up button at once from the fastboot mode itself.
Update me with the result. I'll tell you what to do next based on whether the flash works or not.

HELP : Zenfone6 Bootlooping Constantly and Cannot Go Past TWRP Logo

Help.
I was on Android 10 and I just flashed latest 2021 MARCH full firmware.
following this: https://forum.xda-developers.com/goto/post?id=84193795
Update was fine and phone rebooted successfully.
Magisk was fine too.
I flashed Magisk afterwards (flash to inactive slot after OTA)
Then, I found out that I did not have TWRP anymore,
so I went into Bootloader mode, and via ADB, booted up TWRP 3.4.0.0
then, I flashed TWRP [twrp-3.4.0-0-I0W1D-Q-mauronofrio]
and rebooted to recovery, to see if TWRP was there...
...and now my Zenfone 6 cannot boot up anymore.
I think I flashed TWRP 3.4 and not 3.5
I really, really don't know what to do now,
ie. phone screen is black but I can briefly see the TWRP logo,
before phone goes black again.
I cannot go into Bootloader mode nor does pressing down on the power button down for 10-seconds do anything.
EDIT:
it's the same situation as this
-- https://forum.xda-developers.com/t/...enfone-6-stable.3937844/page-12#post-84205699
It seems official android 11 support is broken. Twrp logo flashes for a sec and then bootloops. Any chance for quick update?
I managed to boot into the phone (by pressing VOL down + POWER).
Basically, my TWRP is corrupt or incompatible with Android 11.
So, I got to figure out how to remove TWRP completely (because I have lost root too)
MODS,
please delete this thread because i am certain now that
the cause of my bootloops, etc... were due to TWRP
not being compatible with Android 11

Categories

Resources