So I followed the usual procedure to install twrp via Odin (all the required files on my computer, as well as both usb debugging and oem unlock enabled on my phone)
To my surprise, after getting the "Passed" message on Odin my phone Bootlooped for a bit, but worked perfectly after I restarted it from the stock recovery menu. But I´m still without twrp and no root access.
Was it because of an incorrect tar file or what?
By the way, I used "twrp-3.1.0-0-hero2lte.img.tar" on a g935F
I need some help.
Before flashing with Odin untick reboot option from there. Flash TWRP (but before that be sure u have 2 files on ur phone ,flashaable super su and no verity opt encrypt) flash TWRP,power off ,the start the phone with vol up and power to enter TWRP , format data flash no verity then SuperSU. Hope it helps
Related
Hi, just bought an S5 G900F (international version)... and i wanted to install a custom recovery than root.. than flash rom. Im experienced in this matter... but ... im having all sorts of odd problems. I tried several reocvery (openrecovery, twrp, philztouch)... non stick when i reboot?
I tried several times... odin says everything installed fine.
I wanted to install cf-root... i did it win odin and when phone restarted it says: "recovery booting.... recovery is not seandoird enforcing ... set warranty bit : recovery
Who can help me??
PS Im on lollipop 5.0 if it makes any difference. All attempts were realized with different versions of odin
People have success with TWRP 2.8.7.0 and ODIN 3.10.6
Then SuperSU from TWRP if it sticks
http://forum.xda-developers.com/showthread.php?t=2727406
Tried no luck. I simply get the stock recovery all the time after restart
daniel_cassian said:
Tried no luck. I simply get the stock recovery all the time after restart
Click to expand...
Click to collapse
Try unchecking "Auto reboot" in ODIN, and once the flash has finished, pull the battery, replace and boot into recovery
just tried it... still no go (... do you think i would have more success trying from adb?
Lol this phone has smth against me.
Tried adb: as long as i have it in "desktop" mode adb devices finds it; as soon as i adb reboot bootloader, using the fastbootdevices... adb doesnt see it anymore... so i cant proceed to the flashig
I know you know what you're doing when it comes to this stuff, as you said
But just to make sure, can you post the exact step by steps you're using to try and flash CF Auto-Root and TWRP etc with ODIN?
Yes of course. As i doesn't work for me... i (even) hope im doing something wrong, so we can get to the bottom of this.
So, installed S5 drivers, Enabled usb debuggin in phone (dev menu). Put phone in dl mode (vl dwn+power+home), open odin, select at AP the recovery (tried about 3 recoveries, older versions and newer ones, twrp, phil, open). I have both (by default) checked auto reboot and f-reset time... connect phone with usb cables (tried 2) (connected directly to mb, no extension)... hit start... get the pass message.. phone resets... goes into android. I power off, go to recovery mode (vl up+power+home) and... i get the stock recovery every single time.
Tried something wierd... flashed through Odin CF-root first (with intention to flash after twrp ... as it says phone needs to be rooted first)... it flashes ok (odin says pass, successful 1), reboot (or go to recovery mode)... i get that seandroid error.
Tried to to with with apps from android as well... it doesnt let me.. obviously as most ask phone to be rooted.
What am I missing?
Those are the correct steps, it definitely should have flashed
Doing this from a native PC yes? Ive seen people trying it from Macs and it fails every time
Only thing I can think of right now is try using a different PC
You don't need USB debugging enabled for flashing with ODIN, download mode has no idea what settings you have enabled in Android
Like your method, I just do this:
Samsung Drivers (KIES3 installs them for you anyway)
Vol Down & Home & Power for Download Mode
Connect phone to PC USB
Leave ODIN defaults set (3.09 or 3.10.6)
Select CF-Auto-Root-klte-kltexx-smg900f.tar.md5 in AP/PDA section of ODIN
Wait for it to become ready
Hit start
Phone reboots, and I have root
You could try factory resetting the phone, and trying again, see if that does anything, or at least clear the caches from stock recovery first
Hi,
I am trying to install open recovery on my note 4 n910c android 5.1.1, using odin and openrecovery-twrp-2.8.3.0-treltexx.img.
Odin says that the flash is successful, but when I try to reboot in recovery mode I obtain the green android and after that the laid down android with 'no command' message to finally ending up in the normal recovery mode.
I have tried several methods to flash it, I even tried to root the phone (I had boot loop and reflashed the stock rom).
Can anyone help.
Thanks in advance
Hello,
Did you have the autoreboot option UNCHECKED in Odin when you flashed the recovery? it must be unchecked, the device can not be allowed to reboot into system after flashing. After flashing with the option unchecked and you get the green pass, you have to manually boot the device to recovery with the button method, then you will keep the recovery, if you boot it to any other modes immediately after flashing then it reverts back to stock recovery, it requires booting directly to the recovery immediately after flashing, then it will be retained.
Hi,
Well it make sense, I had the reboot option ticked on. I actually went through another way by flashing the 5.0.1 bootloader which then allowed me to flash the custom recovery.
To be honest I am not sure whether or not I had the reboot option ticked on (my guess would be that it was as it's the default option in Odin).
Anyway, thanks for the tips I hope it will help others.
i tried everything, but i can't install twrp. i tried to install via odin 3.12.3 but nothing. how can i resolve this issue? i tried also with a pre-rooted firmware.
hello,
fedetrevi1 said:
i tried everything, but i can't install twrp. i tried to install via odin 3.12.3 but nothing. how can i resolve this issue? i tried also with a pre-rooted firmware.
Click to expand...
Click to collapse
dude write some more info will you, i dunno whether
your device is locked
you have developer drivers on your laptop
what TWRP version you are trying to install
but anyways if the whole process is completed without any results consider starting odin as an administrator then flash TWRP
Hello sir
Follow my steps for successful TWRP/ROOT
1.)Download and install Samsung USB Drivers
2.)Download TWRP 3.0.2.0
3.)Download Odin
4.)Download SuperSU.zip file
For download links message me or add me on facebook facebook. com/fRoD.cs
After you complete this 4 steps shutdown your phone and enter into Download Mode
Volume Down + Power + Home
Select continue by Volume Up key
Now connect phone with usb cable into pc and run Odin as administrator
Click on AP box and select the twrp.tar file you download before
Go to Options tab and uncheck Auto Reboot, make sure that only F, Reset Time is checked and click start
After successfully installed TWRP , remove the battery, put it back and make sure that you go into recovery mode immediately!!! Volume Up + Power + Home
If you boot up the phone it will restore the original recovery. Thats why you need to go to recovery mode first.
First time you boot in recovery it will be shown a TWRP screen asking to allow modifications to system partition. Swipe to accept that.
Now select Install option and select SuperSU.zip file. By default it should be in Download folder, and swipe to start install
After installing click reboot and your SM-G361F will be rooted. You should have SuperSU app in the menu
Working Recovery
stevo4 said:
Hello sir
Follow my steps for successful TWRP/ROOT
1.)Download and install Samsung USB Drivers
2.)Download TWRP 3.0.2.0
3.)Download Odin
4.)Download SuperSU.zip file
For download links message me or add me on facebook facebook. com/fRoD.cs
After you complete this 4 steps shutdown your phone and enter into Download Mode
Volume Down + Power + Home
Select continue by Volume Up key
Now connect phone with usb cable into pc and run Odin as administrator
Click on AP box and select the twrp.tar file you download before
Go to Options tab and uncheck Auto Reboot, make sure that only F, Reset Time is checked and click start
After successfully installed TWRP , remove the battery, put it back and make sure that you go into recovery mode immediately!!! Volume Up + Power + Home
If you boot up the phone it will restore the original recovery. Thats why you need to go to recovery mode first.
First time you boot in recovery it will be shown a TWRP screen asking to allow modifications to system partition. Swipe to accept that.
Now select Install option and select SuperSU.zip file. By default it should be in Download folder, and swipe to start install
After installing click reboot and your SM-G361F will be rooted. You should have SuperSU app in the menu
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...sm-g361f-unofficial-twrp-2-8-7-3-0-2-t3425402
hi
I have a problem with my g361f. After few sec proces of flashing twrp failed.. Can you help ?
thocenski said:
hi
I have a problem with my g361f. After few sec proces of flashing twrp failed.. Can you help ?
Click to expand...
Click to collapse
Ah, opportunely, I have the exact same device.
Now, I have actually installed TWRP before so I can help.
Usually, if it stops the flashing process, it may be a case of the Custom binary being blocked by the FRP lock on the device. Have you OEM unlocked it?
On the device, when you boot it into download mode, does it say FRP LOCK: ON on the screen?
If not, skip this step.
If so, you need to do the following:
1) Reboot the device normally
2) Go into Settings, Developer Options (note: to enable it, go to About Device and spam the Build Number box until it says that you are a developer)
3) Find where it says 'OEM Unlock'
4) Confirm the change
Now, there is an extra step which I had to take if you have a Google account signed in on your device. You might not need to, but it's best just in case:
1) Go to Settings, Accounts and Google
2) Click the Google account on the device
3) Click 'Remove Account' and confirm
Note: You will need to sign in to use any of the GApps, but you cannot access the recovery whilst being signed in because of the FRP lock.
4) Reboot your device into download mode and try again.
This may not be the case, though.
Also, don't bother with adding that guy on Facebook. I have all the downloadable things you need here, but I advise you do follow his guide, except the Download folder section. He missed out that you need to download the SuperSU binary to your device. Downloads are here:
Here are the Samsung USB Drivers for Mobile Phones (NOTE: You may not need these at all since you can actually begin the flashing process without them, so don't bother):
http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Here is the TWRP recovery (NOTE: Please download the 3.0.2.0 version, since it is more up-to-date and more likely to succeed:
https://forum.xda-developers.com/ga...sm-g361f-unofficial-twrp-2-8-7-3-0-2-t3425402
And here is ODIN (You already have it, but here it is anyway. Also, download the first one, not the second one, since the first one is newer):
https://odindownload.com/download/
Also, the SuperSU binary (Note: It's easier to open it in your Android browser and download the file from there. That avoids the need to transfer the file from the PC to the phone):
http://www.supersu.com/download
Now, it could, in fact, be a problem with the USB cable. It's highly unlikely, but mine is a bit tempermental, insisting that if I nudge it, it'll stop working.
Notify me how it goes, because this worked first time for me.
fedetrevi1 said:
i tried everything, but i can't install twrp. i tried to install via odin 3.12.3 but nothing. how can i resolve this issue? i tried also with a pre-rooted firmware.
Click to expand...
Click to collapse
Go to developer settings and check OEM Unlocking (if its already checked recheck it) and then reboot. Then close the phone and install TWRP.
Hi I've managed to install the correct twrp on my device but when I go into recovery I get the same message not seandroid enforcing. I've followed all the steps but I can't get it into recovery on twrp. Does anyone have a solution please?
Hello, I've been trying to root my G928T on version 5.1.1 for the first time to no success. I even followed the steps but if someone could point me out on what I did wrong, then I would appreciate it. This is what I did
1. Download Odin 3.12.3, arter97 kernel g928t v22.0, the provided arter97 twrp recovery v22, supersu v2.79
2. Connect device to pc, launched odin and picked twrp recovery tar file
3. disconnect device, went into developers setting and enable oem and usb debugging
4. connect device in download mode, unchecked autoboot in odin, and clicked start
5. pass box, everything seems to be going well
6. now this is the part where i think it's supposed to be installing the recovery but nothing happens to my phone after i click start, it just stays on the download mode screen
7. i restart and enter recovery mode on the phone but it does not launch twrp, enters the default recovery screen
I would also appreciate if someone could just send me a guide on how to root for this model on version 5.1.1 thanks
What i did stepwise -
1. Unlocked bootloader of my g5 plus
2. Flashed twrp-3.2.3-1-potter.img via adb
3. Booted to TWRP
4. Wiped to decrypt phone
5*. Booted to system to enable usb debugging, enabled it . Transfered magisk , arrow 9.0 rom , gapps to my internal storage of phone
6. Open bootloader , selected recovery mode and got nothing except error "No Command"
So i cannot flashed anything what i wanted to
What and Where i made the mistake ?
How can i get TWRP back?
Thanks all in advance
Solution
1. Flashed magisk17.1 and lazyflasher
2. Updated magisk manager and got root
3. Installed official TWRP app , granted root and downloaded same TWRP.img from which i decrypted the phone.
4. Flashed twrp fom the official twrp app.
5. No irritating No Command error again
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
echo92 said:
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
Click to expand...
Click to collapse
Thanks for your answer sir , but it didn't work
What I did again
1.I flashed same twrp from adb
2. Booted to recovery , but this time TWRP didn't asked password and I could see internal storage in twrp but not on my PC
3*.However I took the whole backup of stock nougat and cross check from restore option as there was backup in TWRP folder. I wanted copy that backup to my PC . But PC cannot detect my phone while in recovery
4. So booted to system and my PC detected my phone but there was no backup in TWRP folder.( But around 6gb(backup) of storage was used but I couldn't see it)
5.Again booted to recovery mode but "No Command" showed again .
I tried several times but I keep losing TWRP and couldn't see the backup which I make
Same problem. Resolved by flashing alternately several times twrp-3.2.1-0-potter.img and twrp-3.2.1-1-potter_persist.img and finally updated twrp-3.2.3-1-potter.img
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
NZedPred said:
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
Click to expand...
Click to collapse
I flashed magisk 17.1 and lazyflasher ,i got magisk and root but cannot install modules may be becoz of f2fs bug . By the way i lost twrp after booting to system again and No command still present in recovery mode . I am frustrated Moto software is just pain in head :silly: