Can't install TWRP on nougat - Samsung Galaxy S7 Questions and Answers

Hi all
I have a brand new S7 (G930F) untouched...
can't install TWRP !!!
I've tried the Odin mode with various Odin versions (3.11.1, 3.12.3...
of course OEM Unlock and USB debugging allowed
when the phone is in DL mode, I have the following info on left side up screen
ODIN mode
ODIN DOWNLOAD SPEED FAST
Product name G930F
Current binary Samsung official
Sytem status official
FRP Lock Off
Secure Download enabled
Warranty void 0
RP SW Rev R:1 K:0 S:0
I'm uisng twrp -3.1.1-0-herolte.img.tar wich goes in Odins's AP (Always followed tuto's...)
Hit START and everything goes well..
tel recognized, flashing progresses nicely, got PASS...and nothing more happenrs
It stays for ever in DL mode, phone almost dead !!!
After having waited 30 minutes, I disconnected the phone and had to push the power button for another minute before the phone accaepts to shut down.
I I try ot reboot in recovery, I'm getting the original recovery andnot TWRP.
If a reboot the phone, it comes to life again and works as usual
Absolutely no idea about what is preventing TWRP to get installed...
Any idea more than welcome
All the best

Try this.

harisyks said:
Try this.
Click to expand...
Click to collapse
Hi
Thks for the link !!!
During the night, one question popped up...and this may be what I missed !!!
question is: Do I need to unlock Bootloader first ?

zorglub! said:
Hi
Thks for the link !!!
During the night, one question popped up...and this may be what I missed !!!
question is: Do I need to unlock Bootloader first ?
Click to expand...
Click to collapse
You already did by enabling OEM Unlock
What did you think OEM unlock was for, and why did you enable it if you didn't know it was to unlock the bootloader?
Read through this thread
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770

*Detection* said:
You already did by enabling OEM Unlock
What did you think OEM unlock was for, and why did you enable it if you didn't know it was to unlock the bootloader?
Read through this thread
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Click to expand...
Click to collapse
thks again
i've already read this thread but...
i'm always stuck after the TWRP odin step.
I've seen RECOVERY ( beeing written I think..)
I'm getting a nice PASS ( in green) but the phone stays with this Downloading Do not turn off target screen for ever
Power + Up or Down + Center button all frozen
and of course, no access to TWRP
Don't know what it is expecting or what blocks the process
Weird !!!
And if the problem was not there ?
I have noted something strange with the fastboof command
Fastbot reboot bootloader does not do what it is supposed to do (AFAIK..lol).
It reboots the phone instead of going to the DL mode !!!

You have to hold --power --- volume down --home button down after flashing TWRP. Then when the screen blanks switch to volume up, home and power.

Deep Nox said:
You have to hold --power --- volume down --home button down after flashing TWRP. Then when the screen blanks switch to volume up, home and power.
Click to expand...
Click to collapse
THks...but I know that...and have already done it zillion of times
but the problem was that the screen NEVER blanks and stays On for ever
Finally, I've been able to tame the beast..and discovered that a partition couldn't be mounted !!!
( and this with a phone havind the stock S/W..)
I erased evetything, format everyting, reinstalled the latest firm, then root the phone and now it is working great again

Glad to hear you got it.

Related

[Q] HTC One S - Cannot get into Bootloader

I have searched the forum but no luck on this one.
When I Press Power and Down Vol HTC One S just reboots - it does not go into Bootloader menu.
I cant take the battery out as suggested elsewhere because battery is non-removable.
Fast Boot is Off in the Power Menu.
Any suggestions ?
zobojoe said:
I have searched the forum but no luck on this one.
When I Press Power and Down Vol HTC One S just reboots - it does not go into Bootloader menu.
I cant take the battery out as suggested elsewhere because battery is non-removable.
Fast Boot is Off in the Power Menu.
Any suggestions ?
Click to expand...
Click to collapse
Go to terminal Emulator and type "su" and then "reboot download".
Thanks for this.
I'm not rooted so I cant do su in Terminal Emulator
Can I do ...
adb reboot download
from Mac instead ?
Can you explain what this does ?
zobojoe said:
Thanks for this.
I'm not rooted so I cant do su in Terminal Emulator
Can I do ...
adb reboot download
from Mac instead ?
Can you explain what this does ?
Click to expand...
Click to collapse
Hi,
maybe you can use the ADB to get in the bootloader.
just look onto this HERE
the text there is english because i've only the german explaining and so i don' need to translate it.
EDIT: Finally got into bootloader by connecting phone to a PC with USB Debugging enabled and entering "adb reboot bootloader" in console.
Hi zobojoe, any luck with getting to the bootloader? I have HTC One S imported from Germany with T-Mobile branding and I want to get rid of that branding by flashing the stock ROM but can't get in to the bootloader same as you. What version of phone do you have?
Hi guys i've search the xda maybe this could help you to get the debranding off and get root acess on the phone i don't testing it because i've only the HTC sensation
TUT
Hope i can help you
dagger780 said:
Hi guys i've search the xda maybe this could help you to get the debranding off and get root acess on the phone i don't testing it because i've only the HTC sensation
TUT
Hope i can help you
Click to expand...
Click to collapse
Hey, thank's for trying to help! I've seen the thread you posted before - used it to get CWM and root but I've spent last 3 hours trying to get the stock ROM in my phone (I really hate the T-mobile branding) and nothing worked. What I did was I downloaded RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501 S.19_10.12.31501S.06L_release_251412_signed.exe and tried to flash that using RUU. It didn't let me. So I at least got the zip file from the exe (temp method) and tried to flash that in CWM but id didn't work either (probably because it was not signed). So I tried to extract the system.img and radio.img and pack it again in a new zip and sign it myself - didn't work either. Kinda stuck now. Help from someone familiar with packing ROMs would be highly appreciated. I can't be the only one trying to debrand my phone .
Maybe the bootloader is Not unlocked?
Sent from my Sensation using XDA
dagger780 said:
Maybe the bootloader is Not unlocked?
Sent from my Sensation using XDA
Click to expand...
Click to collapse
Yes it it. Before I unlocked it, the RUU update ended with error 170. After unlocking it RUU update started kinda flashing something, but then ended with black screen with HTC logo and then turned into RUU fail! red warning.
Hi Andrew SM
I too have been able to adb reboot into bootloader but can't understand why power + vol down just reboots the phone and not go into bootloader as it should ?
Is it the case that it is rebooting straight into recovery mode when I do power + vol down and then just boots ? - what should I normally expect to see when I boot into recovery mode ?
zobojoe said:
Hi Andrew SM
I too have been able to adb reboot into bootloader but can't understand why power + vol down just reboots the phone and not go into bootloader as it should ?
Is it the case that it is rebooting straight into recovery mode when I do power + vol down and then just boots ? - what should I normally expect to see when I boot into recovery mode ?
Click to expand...
Click to collapse
I don't think it is recovery - you would se a black screen with a phone icon in the midddle of it with stock recovery.
But I was able to get to bootloader with VOL DOWN + POWER finally after unlocking bootloader via htcdev.com (bootloader screen starts showing *** TAMPERED *** on the top, but that is normal). And you have to disable Fast boot in Settings -> Power of course.
Good luck!
Boot loader
Little late to the party, but I've found the best way to get into boot loader wiht any consistency is to hold the volume down and power button for five seconds or so, then let go of the power button (while holding volume down), then tapping the power button. Boot loader should pop up
Hope this helps!
Brilliant! Worked perfectly! Thanks very much.
no99sqrd said:
Little late to the party, but I've found the best way to get into boot loader wiht any consistency is to hold the volume down and power button for five seconds or so, then let go of the power button (while holding volume down), then tapping the power button. Boot loader should pop up
Hope this helps!
Click to expand...
Click to collapse
BOOM this saved the day, thANKS!!
no99sqrd said:
Little late to the party, but I've found the best way to get into boot loader wiht any consistency is to hold the volume down and power button for five seconds or so, then let go of the power button (while holding volume down), then tapping the power button. Boot loader should pop up
Hope this helps!
Click to expand...
Click to collapse
Thanks for this!
Was right before going into rage-mode. But luckily I found your post.
AndrewSM said:
EDIT: Finally got into bootloader by connecting phone to a PC with USB Debugging enabled and entering "adb reboot bootloader" in console.
Hi zobojoe, any luck with getting to the bootloader? I have HTC One S imported from Germany with T-Mobile branding and I want to get rid of that branding by flashing the stock ROM but can't get in to the bootloader same as you. What version of phone do you have?
Click to expand...
Click to collapse
I cannot enter the bootloader too, so I have follow your instruction and now I can enter inside bootloader. I was wondering why this was necessary.
Anyway I just have the massage : locked and NOT the TAMPERED advice.
Anyway I will wait to unlock my one s, I wanna see if a different unlock way from htcdev cames out because I do not wannt risk that the warranty could be void. Have anyone tried this: http://forum.xda-developers.com/showthread.php?t=1578908 ?
Thanks a lot for this trick! This works immediatly!
Another easy way to get into boot loader every time is :
1. power off phone
2. hold the volume down button ( until boot menu open )
3. press power button for about 2-3 seconds then let go
new developer need 10 posts in general discussion sry

root failed (bootloader exception)

Hi everyone,
I followed the guide about the root for my S7 ITV. I've done everything step by step and flashed with odin the cf-autoroot.
When rebooted I had a blackscreen and and this error "bootloader exception", with the impossibility to enter in bootloader mode with the botton combination.
Found a way to return to downlaod mode and reflashed the stock rom.
Now my question is how to have root permissions.
I'd like to try again (I always rooted all my android devices and never had an error like that) but I'd like to understand what i did wrong before doing it again.
Thanks
gerazzo said:
Hi everyone,
I followed the guide about the root for my S7 ITV. I've done everything step by step and flashed with odin the cf-autoroot.
When rebooted I had a blackscreen and and this error "bootloader exception", with the impossibility to enter in bootloader mode with the botton combination.
Found a way to return to downlaod mode and reflashed the stock rom.
Now my question is how to have root permissions.
I'd like to try again (I always rooted all my android devices and never had an error like that) but I'd like to understand what i did wrong before doing it again.
Thanks
Click to expand...
Click to collapse
And how did you get back into download mode, as you do not say?
Thank you
UPDATE:- I tried to root my new S7 and ended up with bootloader error.
In order to get back to download mode this was procedure.
When you get lovely green and red writing in error.
Press all 4 buttons, power, vol down, vol up and home, hold all til screen goes black, then straight away, remove JUST your finger off the vol down button.
This will boot you back into recovery mode.
Do not wipe, clear or reset as it will not work, due to your bootloader corrupt which will prevent your phone ever booting correctly.
Press System off and let phone power off,
Leave for approx 30 seconds.
Now Press Vol down, Home and power buttons and phone will boot into download mode.
I am downloading original firmware, the same one which was is currently on phone to save any issues.
I will then be able to freshly install firmware with odin and then read how to root again without trying to get the bootloader error again.
Best wishes

I Flashed My Note 20 Ultra With Recovery.img And Now Its Stuck On Orange State "Bootloader Unlocked" Warning Message!

Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not

My SAMSUNG Galaxy A8 2018 isn`t work

After rooting my smartphone, I turned it off and on again, and it booted up infinitely. I was embarrassed and touched this and that, then went to wipe->advanced wipe menu and accidentally changed the system file. After that, my smartphone doesn't work at all. I'm posting this because I wanted to know how to turn on this smartphone, so I hope someone who knows about this part will reply.
(OEM seems to have turned off as the OS disappeared when I judged it.)
So can you boot into anything? Try all button combinations possible.
Or it is just black screen without a single text no matter how ?
LR7875 said:
So can you boot into anything? Try all button combinations possible.
Or it is just black screen without a single text no matter how ?
Click to expand...
Click to collapse
Now all of a sudden, a lightning bolt icon appears on the black screen, which appears to be charging.
Do not unplug your phone. Press and hold the Power key and the Volume down key simultaneously for more than 7 seconds. As soon as the screen goes black hold down Volume Down + Volume Up for a few moments.
LR7875 said:
So can you boot into anything? Try all button combinations possible.
Or it is just black screen without a single text no matter how ?
Click to expand...
Click to collapse
The power button and the volume bottom button were pressed at the same time and pressed for 7 seconds or more. The smartphone was turned off. Since I used TWRP in this state, I have been routed using the powerward button and the power button to move the powerward button and the power button for a long time to move the BACKUP entry, and the system image is displayed, but the system is displayed as 0 MB. And if you try to reboot, the NO OS Installed error will be opened and you want to install the TWRP app, and Failed to Mount / System (No Such Devices) Error appears. Now this is the symptoms of my smartphone.
LR7875 said:
Do not unplug your phone. Press and hold the Power key and the Volume down key simultaneously for more than 7 seconds. As soon as the screen goes black hold down Volume Down + Volume Up for a few moments.
Click to expand...
Click to collapse
First, I asked you to go to download mode. How do I have since that? (OEM seems to be forcibly turned off when the OS itself is gone. I turned on the routing before.)
You are in twrp now, but shows system as 0mb?
Can you press mount> system or wipe> factory reset?
holyfonts6754 said:
First, I asked you to go to download mode. How do I have since that? (OEM seems to be forcibly turned off when the OS itself is gone. I turned on the routing before.)
Click to expand...
Click to collapse
No. With OEM locked, even if your phone is locked as tight as bill gates's wallet, you can still boot into download mode. However You can only flash stock ROM in that case. This is the definition of OEM lock: you can flash, but cannot flash anything except stock rom.
You must not be meaning OEM lock.
LR7875 said:
You are in twrp now, but shows system as 0mb?
Can you press mount> system or wipe> factory reset?
Click to expand...
Click to collapse
I've just tried it, and they all give me a "failed to mount '/system' (no such device)" error.
LR7875 said:
You are in twrp now, but shows system as 0mb?
Can you press mount> system or wipe> factory reset?
Click to expand...
Click to collapse
Although I am looking for information on the Internet, it seems that a program called Odin is necessary for Samsung phones. The internet says that you can upload the genuine firmware, but is there any other way to upload this genuine firmware other than using Odin? And what should I do if my smartphone is not recognized?
What happens of you press reboot> bootloader in twrp?
LR7875 said:
What happens of you press reboot> bootloader in twrp?
Click to expand...
Click to collapse
When I enter reboot from twrp, four items are displayed on my smartphone: system, power off, recovery, and download. If you go to system, the Galaxy A8 logo is displayed and it stops, and if you go to download, it goes into download mode.
The bootloader entry is not visible.
holyfonts6754 said:
Although I am looking for information on the Internet, it seems that a program called Odin is necessary for Samsung phones. The internet says that you can upload the genuine firmware, but is there any other way to upload this genuine firmware other than using Odin? And what should I do if my smartphone is not recognized?
Click to expand...
Click to collapse
Look inside here:
Samsung Flash File Download (Stock ROM) - RepairMyMobile.co
Download Sasmung Flash file/stock rom/firmware for your phones. Original files has direct link and site...how to flash without box z3x, ufs hwk odin tool
repairmymobile.in
jwoegerbauer said:
Look inside here:
Samsung Flash File Download (Stock ROM) - RepairMyMobile.co
Download Sasmung Flash file/stock rom/firmware for your phones. Original files has direct link and site...how to flash without box z3x, ufs hwk odin tool
repairmymobile.in
Click to expand...
Click to collapse
When I went to this site, there was nothing of the Galaxy A8 2018 I wanted. So what should I do? Is it possible even if the OEM is locked?
LR7875 said:
What happens of you press reboot> bootloader in twrp?
Click to expand...
Click to collapse
When I went to the path where I had touched the system setting incorrectly and changed the system setting to ext2, what was displayed as 0MB was displayed as 7MB. After I just selected ext2 it was still showing 0MB, but now it shows 7MB.
But the no os installed error is still displayed.
However, the Failed to Mount / System (No Such Devices) error no longer appeared.
holyfonts6754 said:
When I went to this site, there was nothing of the Galaxy A8 2018 I wanted. So what should I do? Is it possible even if the OEM is locked?
Click to expand...
Click to collapse
1. Then request phone's Stock ROM directly from Samsung.
2. As you were already told flashing a phone's Stock ROM doesn't require phone's bootloader is unlocked.
You reported you have flashed TWRP successfully: this means your phone's bootloader got successfully unlocked.
Take note that TWRP is used to flash Custom ROMs.
Stock rom: www.samfw.com
For odin and usb drivers just search
Flash in download mode
LR7875 said:
Stock rom: www.samfw.com
For odin and usb drivers just search
Flash in download mode
Click to expand...
Click to collapse
Odin doesn't seem to recognize my phone. Since the USB driver is a Samsung phone, I downloaded and installed the Samsung integrated USB driver. Yet it is not recognized. Download mode is now in the state.
jwoegerbauer said:
1. Then request phone's Stock ROM directly from Samsung.
2. As you were already told flashing a phone's Stock ROM doesn't require phone's bootloader is unlocked.
You reported you have flashed TWRP successfully: this means your phone's bootloader got successfully unlocked.
Take note that TWRP is used to flash Custom ROMs.
Click to expand...
Click to collapse
I'm still a beginner, so I don't know how to flash custom roms or anything like that. Is there a way to flash a custom rom or original firmware using TWRP? Now, it enters the download mode and waits for it to be recognized by Odin, but it is still not recognized by Odin.
Does it usually take a long time for the smartphone to be recognized by Odin?
Do you have other phone? Is the cable good and transfering files?

Question [SOLVED] Flashed a file from TWRP Official App choosing my device from the list and got stuck on the "Downloading do not turn off target" screen

Device:
- Samsung Galaxy A12
- Rooted
- Magisk and Magisk Manager both updated
- Model sm-a127m
- Problem context: I could not find a recovery for my particular model and during the rooting process I somehow ended up not being able to access the recovery, after a long time I tried to install one from the TWRP Official App and this ended up happening.
Bafif said:
Device:
- Samsung Galaxy A12
- Rooted
- Magisk and Magisk Manager both updated
- Model sm-a127m
- Problem context: I could not find a recovery for my particular model and during the rooting process I somehow ended up not being able to access the recovery, after a long time I tried to install one from the TWRP Official App and this ended up happening.
Click to expand...
Click to collapse
Going back to stock by flashing latest via Odin is what I would do and then start from scratch.
You took TWRP for a125f didn't you?
They have very different hardware, but I think it will work to return to stock.
bmwdroid said:
Going back to stock by flashing latest via Odin is what I would do and then start from scratch.
You took TWRP for a125f didn't you?
They have very different hardware, but I think it will work to return to stock.
Click to expand...
Click to collapse
Instead I re-flashed twrp, this time a version supposedly for a127m unofficially and the phone ended up blinking on and off a totally black screen. Now it doesn't enter download mode or recovery mode and the computer doesn't recognize it. I'm pretty ****ed up.
Bafif said:
Instead I re-flashed twrp, this time a version supposedly for a127m unofficially and the phone ended up blinking on and off a totally black screen. Now it doesn't enter download mode or recovery mode and the computer doesn't recognize it. I'm pretty ****ed up.
Click to expand...
Click to collapse
Was it fully loaded before you started?
Is it possible that the battery is empty?
I'd leave for hours connected to the charger and test tomorrow again to get into download mode.
bmwdroid said:
Was it fully loaded before you started?
Is it possible that the battery is empty?
I'd leave for hours connected to the charger and test tomorrow again to get into download mode.
Click to expand...
Click to collapse
The battery is fine, it was loading almost the whole process because I flashed the last time from the PC and was at 70% before starting. The only thing it does since yesterday (it was not turned off at any time) is to flash between the screen turned on showing pure black color and the screen off.
If I press Volume Down Key and power key what it does is not to enter the Download Mode as before but show the Samsung A12 logo and then the warning of "unlocked bootloader" with the "Press Power Key to continue", then the same screen From Samsung A12 but with a warning of Custom Software and then begins to blink again.
I cannot turn it off or enter the recovery mode or enter the download mode. The battery is inaccessible to me although I could find a way to do it if it served something.
@Bafif one last idea:
did you enable USB debugging in dev options before?
Then adb commands might be working.
1 To test if adb can see it (device connected to PC) :
command <adb devices>
Perhaps necessary to enter twice.
If yes you'll see a notification on the screen.
2 Then you can <adb reboot bootloader> to enter download mode.
If you don't get the notification I'm probably not able to give any further hints.
bmwdroid said:
@Bafif one last idea:
did you enable USB debugging in dev options before?
Then adb commands might be working.
1 To test if adb can see it (device connected to PC) :
command <adb devices>
Perhaps necessary to enter twice.
If yes you'll see a notification on the screen.
2 Then you can <adb reboot bootloader> to enter download mode.
If you don't get the notification I'm probably not able to give any further hints.
Click to expand...
Click to collapse
No luck, I guess it's bricked
PS C:\> adb devices
List of devices attached
PS C:\> adb reboot bootloader
error: device not found
PS C:\>
Bafif said:
No luck, I guess it's bricked....
Click to expand...
Click to collapse
Sorry to read that.
Tried very long pressing power button (2 minutes or so) or other button combo like Vol up + down together plus power?
I don't own that device so can't test for you.
bmwdroid said:
Sorry to read that.
Tried very long pressing power button (2 minutes or so) or other button combo like Vol up + down together plus power?
I don't own that device so can't test for you.
Click to expand...
Click to collapse
I GOT IT . What I did was wait for the battery to run out totally and then keep the two volume buttons pressed and connected the cable with the phone off, that opened the download mode. I just had to wait two days for completely draining. Thanks for paying attention to me
Bafif said:
I GOT IT . What I did was wait for the battery to run out totally and then keep the two volume buttons pressed and connected the cable with the phone off, that opened the download mode. I just had to wait two days for completely draining. Thanks for paying attention to me
Click to expand...
Click to collapse
Glad to hear that.

Categories

Resources