I have samsumg galaxy S6. Today G920F 6.0.1 I downloaded a stock ROM from Sammobile for G920F 6.0.1 it loads fine flashes fine, But at first when I flashed TWRP it wouldn;t boot into recovery. Then it wouldn't even boot normally it just sits at the first samsung logo until I reflash my ROM via Odin, so I searched a bit and found a thread that said to install UniKernal for it to work, so I did now TWRP loads up but my system won't boot up normally. SO I can't get onto my system normally
EDIT: I managed to get it to work, I flashed Magisk, Systelmess xposed 86.4 and supersu rebooted, systemless said it was installed went to check supersu and it wouldnt load so i reflashed it and now xposed says ther eis no framework installed, so i reflashed that and Xposed does not detect it.
Can someone please help me I have searched on here and google and cant find any options that fixes my problem. My phone has been broken for over 24 hours now
Flash G920FXXU4DPGW (XEF) ROM via Odin. (You can download it via SamFirm).
After you've flashed, flash this TWRP via Odin and boot into it;
http://www.arter97.com/browse/S6/kernel/21.1/g920fi/arter97-recovery-g920fi-21.1-twrp_3.0.2-0.tar.md5
When you boot into it, flash this via TWRP;
download.chainfire.eu/supersu
After you've flashed it, reboot the system. When you've rebooted, reboot into TWRP and flash this;
https://www.androidfilehost.com/?fid=24591020540824278
When you've flashed this, reboot the phone and install this apk;
http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
forumber2 said:
Flash G920FXXU4DPGW (XEF) ROM via Odin. (You can download it via SamFirm).
After you've flashed, flash this TWRP via Odin and boot into it;
http://www.arter97.com/browse/S6/kernel/21.1/g920fi/arter97-recovery-g920fi-21.1-twrp_3.0.2-0.tar.md5
When you boot into it, flash this via TWRP;
download.chainfire.eu/supersu
After you've flashed it, reboot the system. When you've rebooted, reboot into TWRP and flash this;
https://www.androidfilehost.com/?fid=24591020540824278
When you've flashed this, reboot the phone and install this apk;
http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
Click to expand...
Click to collapse
Also, that rom cant be found on samfirm.
Jordy87pack said:
Also, that rom cant be found on samfirm.
Click to expand...
Click to collapse
It can be
forumber2 said:
It can be
Click to expand...
Click to collapse
Lol. I always thought samfirm meant sammobile firmware section. Where do I get that program? Is it used to flash firmware? Looks nice.
Related
..
you asked the same question I was going to ask....hopefully someone replies to you, I'll keep asking around the interwebs for a solution I already asked Max Lee and still no reply. I'm rooted too (cf auto root) but i want twrp just in case.
I'm trying for 2 days for my 920i and I ha e twrp now I flashed 920f and boot fine!
https://www.fshare.vn/file/B38M8WL1ZQDE
merrykid said:
I'm using G920I Australia version.
I can successfully root using CF-Auto-Root.
But I can not get into TWRP recovery after I flashed that (tried both versions of the recovery) using odin. It stops at the first screen (samsung logo). I tried using adb commond reboot recovery and the hardware key (volum up+power+home), both of them do not let me in to the custom recovery.
I had tried enabled knox before flash TWRP, which made it into boot loop. And then recoveried using the official firmware. Now I can only get into the official recovery.
Any suggestions for how to get into the TWRP?
BTW, how to backup the pit file using adb? On previous models it was mmcblk0, but Galaxy S6 seems to have changed the memory map to sda1, sda2, etc.
Click to expand...
Click to collapse
I got the 920i Aus version too. I was told two different things.
Update firmware to AOD1 and flash TWRP and it should work.
-or-
Use the 920t as jah2110 says. I would find the file from somewhere more 'reputable'.
Downloading a AOD1 firmware now from sammobile which is awful slow. First one I tried to flash gave me fail in odin so im trying a different one.
Stuck at the Samsung logo after trying to flash the recovery via twrp app, now it doesn't even boot normally. so if you want to install twrp don't use the app, G920I telstra version
Just flash an AOD1 firmware or more. The new zealand firmware for instance and then twrp is gonna work.
If you are stuck after flashing twrp on the australian firmware just flash root using odin and you will be able to start your device again
massacreur75010 said:
Just flash an AOD1 firmware or more. The new zealand firmware for instance and then twrp is gonna work.
If you are stuck after flashing twrp on the australian firmware just flash root using odin and you will be able to start your device again
Click to expand...
Click to collapse
really? i didn't know that, anyway, if you want to update/reinstall the stock firmware, sammobile is so bloody slow, i deem it unusable, so i found this gem, much faster than sammobile, i downloaded at 1.3MB/s so it takes just over 20 minutes for the whole firmware. http://galaxys6root.highonandroid.com/galaxy-s6-stock-firmware/ give it a try if sammobile just pisses you off.
Yes it took me a few days to figure it out and everyone kept saying that twrp should work ...but thats just a matter of firmware version.
So is there a fix? I can get root but TWRP just sites and the boot screen.
I've been in the same situation using a Aussie Voda 920i, I was able to root using CF auto root but then had deep sleep issue & couldn't install TWRP. Now i've installed the singapore firmware & also got TWRP running but cant root.
If I use ODIN to root its gets stuck on logo screen & If I use TWRP it appears to go OK but just doesn't work. Also although CPU Spy says I am getting deep sleep battery life seems awfull
Twrp gave me the boot screen for infinite as well. I live in Alaska. I had to reflash root file to boot. Never got twrp to work. I tried to flash via app. I don't even want more possible headache flashing it with Odin.
Surely if you've got root you can install twrp from the app store and let it replace the recovery.
Same issue
I had exactly the same issue, flashed TWRP from a reliable source and my phone bricked at start up logo screen, could only get into download mode, once i did that i reflashed with ODIN and autoroot file and phone came back alive. Thank god.
---------- Post added at 10:47 PM ---------- Previous post was at 10:43 PM ----------
Tried to install TWRP from official APP, said it installed recovery successfully would you like to attempt reboot and get into recovery, got stuck again at boot screen LOLLLL awesome...... piece of ****ware.
Same for me G920F. I tried twice both failed.
First time use this thread The phone was successfully rooteded. I installed "TWRP Manager.apk". It cause phone infinitely reboot.
Then I restore the stock ROM (you won't know how painful to download the 1.5G+ ROM).
Second time, I rooted again. And tried use freshily (?) to manually install an img in sdcard. It said success and reboot. But it stayed in boot logo.
I restore the stock ROM again (but the kies3 needs to download ROM again!).
I will not try a third time unless there is an right answer.
__________________
btw, the first one say 'oem unlock' must be checked. But I do not have this option, maybe because my phone is unlocked already (not binded to any one).
GrandMstrBud said:
So is there a fix? I can get root but TWRP just sites and the boot screen.
Click to expand...
Click to collapse
im a Noob but i was told that my TWRP was being overwritten during the reboot and that i Must flash a custom kernal after rooting so that the TWRP wouldn't be overwritten
SillyTAO said:
im a Noob but i was told that my TWRP was being overwritten during the reboot
Click to expand...
Click to collapse
This only happens when you fail to force the reboot into recovery yourself.
If you let the phone reboot automatically after flashing, it will be stuck @ bootloop; so you have to be faster & hold the vol up+home+power buttons *immediately* when Odin finishes the process.
Don't bother removing the cable or waiting for the screen to change, that will be too slow.
Cant boot in twrp after flashing thru odin
knox counter trips
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
cgrimm9 said:
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
Click to expand...
Click to collapse
Did you fastboot boot into TWRP, then flash twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip? Were you stock prior?
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
cgrimm9 said:
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
Click to expand...
Click to collapse
Yes, you are not supposed to install twrp, just boot into it. If you install it by mistake, you go back, flash stock boot.img, and do it again.
This is from Dees_Troy's post located here
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Tulsadiver said:
Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
Click to expand...
Click to collapse
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
alienjon said:
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
Click to expand...
Click to collapse
Things have changed with 8.1. you have to root with magisk. From slot b you cannot fastboot flash boot_a boot.img?
I believe the instructions now are to boot to TWRP, install TWRP pixel installer zip, then flash Magisk zip
Here is where TWRP files are here
https://dl.twrp.me/sailfish/
Tulsadiver said:
From slot b you cannot fastboot flash boot_a boot.img?
Click to expand...
Click to collapse
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
alienjon said:
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
Click to expand...
Click to collapse
Yes, the zip file that is located where the flash-all.bat is. Unzip it and flash the boot.img.
I bought a Pixel 2 on swappa. It had different bootloader's on slot a and slot b. I couldn't flash updates when on slot a. I thought I was hosed but from slot b I could flash to slot a so now I'm fine. Slot a had a preview bootloader.
Hi
This is really frustrating. I own many Samsung devices and never had any issue installing twrp, so I am not a noob when it comes to firing up Odin and flashing the image however I am stuck with this device.
I used couple guides with no success. ;( I cant get rid of the Samsung recovery and replace with TWRP. Odin says success but that is just a lie.
I tried both the lollilop bootloader and the older one then TWP with various versions (3.1x , 2.8.x) No luck.
Can anyone please provide me "working files" with "simple steps" in case I am missing out on some minor details. This is SM-P900 Kitkat 4.4.2 version.
- I flash the bootloader using the BL slot in dl mode
- I reboot to downloader again and and install TWRP
- I type adb revoot recovery
Boom, I am back to frigging Samsung recovery
Hi ,
This is a follow up
The only guide that worked for me is this one. It might be helpful to others.
https://forum.xda-developers.com/ga...guide-install-official-lollipop-p900-t3154362
I had trouble getting TWRP to take at first too. It seems Samsung overwrites the recovery upon rebooting so even though TWRP flashed successfully it just gets overwritten when the system restarts. The simple solution for me was to disable the Reboot option in Odin, install TWRP, manually shut down and then enter Recovery mode. Hope that helps. I came across this suggestion either in the thread linked to above or while googling.
Im installing into properly rooted and I have twrp 2.8.7. I want 3+ TWRP.
I flash with PDA/AP and with "autoreboot" unchecked. I power off and power+home+volUP for recovery.
Tablet enters a "enttering recovery" bootloop which can be only disrupted by going into power+home+volDWN to enter Download, and than I can flash with ODIN 2.8.7.
2.8.7 is the latest I can boot into. WHAT IS WRONG?!!!!!!!!! I lost hope, with flashing 100x
Did you try updating TWRP from inside TWRP?
Sent from my Samsung SM-P900 using XDA Labs
try do a full wipe from stock recovery . after that flash twrp selecting the ap and bl in ODIN twrp3.1....tar booth of them (AP & BL)
no no no i tried everything. but than I found out this post : https://s4.postimg.org/s3pel2ekd/this_guy.png and that solved the day!!
With p900 work perfect, but install hard. With this twrp 3.1 i install lineage 14.1, all works good.
Hello guys,
I have flashed TWRP via Odin on my stock sm-g920f on nougat, Odin said "pass" and I can use the recovery normally, but the phone won't start and is stuck in bootloop. I have read (I should have done this before...) that TWRP Needs a kernel which Supports dm-verity.
So what can I do to make the s6 run again?
thanks!
You need just flash latest SuperSU zip via TWRP.
Worked! Thanks a lot.
I have a samsung j111f rooted with a twrp recovery via flashing superSU zip but when i wanted to change to magisk i couldn't uninstall superSU via full unroot , I managed to do that many times before and rooted it again via twrp, but the problem now is that when i try to do a full unroot it asks me to revert to stock boot image i hit yes then it asks to revert to stock recovery so i hit no because i need it to flash magisk so it fails to full unroot, but when i hit no at recovering boot image it bypass but magisk dont want to flash because i have a modified boot partition; So please would you help me ?
PS : I have an unlocked bootloader witch i got since my first rooting following this : https://forum.xda-developers.com/android/development/root-samsung-galaxy-j1-ace-sm-j111m-f-t3395520
Also i have installed twrp recovery via odin on that unlocked bootloader because it always boot to stock recovery when i try to flash it on stock firmware
Never mind i found the sollution just full unroot without fixing bootloader from supperSU ,booted into twrp recovery flashed stock boot.img then magisk.zip and rebooted that's it got evrything worked
Click to expand...
Click to collapse