I have the relevant TWRP firmware, JOdin, and Heimdall on my Linux system. It took me a while to find the relevant firmware, but I got it. I have to use Heimdall and JOdin because fastboot, for some reason, will not work with my tablet. I have obtained the PIT file and used JOdin with the TWRP tar as a PDA file. This process succeeded. When I reboot and run adb reboot recovery, I get a text-based recovery screen with seemingly no connection with TWRP. Before this screen shows up, it says "Downloading updates" and then "Command failed" or something like that.
I was directed here from the Arch Linux forums. The question I posted there asks for some way to get fastboot to work, but I think that's a lost cause now.
Does anyone know why TWRP is not being written to the tablet? Is there any way to boot into the image, excluding fastboot? And, if possible, it would be great if fastboot worked.
Followed this guide from steps 10-13 and it worked! Will mark this as solved.
Related
After getting my GS3/i9300 I realized that I didn't have a Windows computer anymore to root it. So I was stuck finding an alternative to Odin. I had trouble finding one aggregated source of Mac info that was relatively recent (last post I see is from Feb 2012) and all in one place.
I'm on MacOS X 10.7.5 (Lion) which isn't the most current version. I'm also a noob so maybe I got lucky as I've seen many comments within the various threads where my steps didn't work for other people.
When you download Chainfire's Auto-Root zip file, you'll need to do things a bit differently than with Odin. After unzipping, you'll need to untar the .tar file as well. You'll want the recovery.img and cache.img files in a folder on your PC. You'll need to know the path to that directory.
Instead of using the Heimdall GUI (which I found confusing), I ended up finding Chainfire's comments about using the Linux/Terminal commands in one of his old posts. He said it was "hearsay" but I can confirm that it worked on my GS3. Credit goes to jzuijlek for posting it (his post).
You'll want to install Heimdall from here
Currently they're saying to install version 1.3.1 instead of 1.3.2.
After Heimdall installs, I suggest rebooting your Mac.
Now to the good stuff...
Boot your phone into download mode:
1) Unplug your phone from the computer.
2) Turn your phone off
3) Hold both the volume down + home button. Then press and hold power until download mode comes up. Then press the volume up key to continue.
3) Plug in your phone
4) Open up Terminal and then cd to your recovery/cache.img files directory
5) Then type in this command:
sudo heimdall flash --recovery recovery.img --cache cache.img
If all goes well then you'll see stuff being installed and your phone will reboot and you'll be DONE!
However, if you're like me, you got an error. The response from Heimdall said, "Claiming interface failed". It turns out that there may be conflicts with Kies kexts if you have it installed. If you don't have it installed and you're seeing this error, I'm not sure if I can help. I suggest uninstalling Kies as you won't need it after you root. I searched Google with my error and finally found this gem from March 2012!
http://blog.scott.wallace.sh/2012/03/getting-heimdall-to-work-on-your-mac.html
As such, if you've installed Kies on your Mac and you're having this error, I suggest using the following commands. It seems some kernel extensions that Kies installs conflict with Heimdall.
sudo kextunload -b com.devguru.driver.SamsungComposite
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
After this, I tried to flash again and it worked like a charm!
Now you're rooted.
However, Chainfire doesn't support CWM in his CF-Autoroot anymore so you'll need to get CWM or some other recovery image (Philz, TWRP, etc.). You can search these forums but these links should be mostly correct
CWM (find the Samsung Galaxy S3 i9300 in the list: http://www.clockworkmod.com/rommanager
Philz (built on CWM): http://forum.xda-developers.com/showthread.php?t=2002953
TWRP: http://forum.xda-developers.com/showthread.php?t=1943592
You'll flash the same way as above with just the .img file
Boot into download mode using sequence above.
(Example with CWM)
Open up Terminal and cd to the directory with your .img file.
Then type:
sudo heimdall flash --recovery recovery-clockwork-6.0.2.7-i9300.img
For reference...to boot into recovery:
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
I hope this helps! Let me know if you think I got anything wrong!
Is this still theway to root on mac?
I have s3 uk 3 network. 4.1.2 xxella.
I blieve my phone was open to sds attack before the xxella update. can i keep this recovery?
I would strongly advise against using Heimdall. Nothing against the authors, but I tried it and would recommend avoiding it. Simpler approach is to setup Windows (In my case Windows 7) in a VM environment (I bought VMware Fusion) and just use the normal Odin. You'll get far more support from people here, and less headaches.
While i agree that Odin is easier and gives you more help from the community, i used Heimdall anyway due to not having any wish at installing windows on my mac.
This method does work (as of may 2013), however:
-Uncheck the "reboot after flashing" option in Heimdall. When Heimdall has done its job, manually boot into recovery. This way your custom recovery wont be overwritten by stock recovery.
Happy flashing!
There's a painful brick story behind this, and I'll share those details if needed, but let me start with my current situation.
I've got a D800 (AT&T). I can boot to Android (almost stock D80030f, rooted), but I can't get to recovery. I've tried AutoRec to install TWRP, but when I reboot to recovery, it takes me to fastboot mode instead. I would try to flash recovery from fastboot, but the only fastboot command that ever returns is getvar, and it comes back empty for most variables. Anything else I've tried just hangs (erase, flash, reboot). I see the command printed on the phone's screen, but nothing happens after that. This is the same as it was while I was bricked and stuck in fastboot mode. I've tried from Linux, from Windows in a VM, and from a Windows host.
I can get to download mode, but I can't flash anything there, either. The drivers are installed and everything is set up correctly according to all the guides, but when I try to flash, I get an error that the version doesn't match (or something, I can get the exact error message if needed). I suspect this is related to the fastboot problem, because it shows version strings that are either empty or null, I don't remember which. I get the same behavior from both my Windows VM and my Windows host. Both are Windows 7 64-bit.
It would be nice to get fastboot and download mode working, but what I really care about is TWRP, of course. Is there anything I can do to get this working while booted to Android?
I've already short circuited this thing once, and that's how I got this far. I dd'ed every partition (from http://downloads.codefi.re/autoprime/LG/LG_G2/D800/Stock_Firmware/30f_partitions) except for modem and dbi, and a TWRP image for the recovery partition. So if I have to short circuit again, I'm not afraid to.
Edit:
I'm not sure if this is in any way indicative of the problem, but I just noticed that my GPS isn't working. Honestly, I'd be happy to start with a fresh TOT if I could just get it to flash.
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
alajoy said:
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
Click to expand...
Click to collapse
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Choose an username... said:
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Click to expand...
Click to collapse
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
alajoy said:
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
Click to expand...
Click to collapse
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Choose an username... said:
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Click to expand...
Click to collapse
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
alajoy said:
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
Click to expand...
Click to collapse
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Choose an username... said:
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Click to expand...
Click to collapse
I have adb and fastboot installed on my Mac and I can't remember how I got it working on my phone in the first place, but I've only ever used a Mac for all this. Terminal recognizes my device and responds to commands until I try "fastboot flash recovery twrp.img" then it says "<waiting for any device>" and does nothing.
Thanks again for the help. I'll keep hunting though. I don't have access to any Windows computer.
Cheers
Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me
Format data?
What your twrp version ? your twrp version must be version support 11.
You cant flash Magisk via TWRP. It doesn't work, Install the magisk App
Wrong place to ask this stuff
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I was following this guide: https://forum.xda-developers.com/t/...-to-install-lineageos-18-1-gsi-gapps.4418289/
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
Flashed the firmware using ODIN to: XAR-T290XXU3CUK4
I downloaded and used the latest .md5.tar TWRP: twrp-3.6.1_11-0-T290XXU3CUK4-20220327.tar.md5
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet.
I cannot also see the tablet with ADB using the command "adb devices", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
Well, if you want my two cents I bet on that twrp not just being a recovery but containing also other stuff not being flashed into the right place could have caused what you describe, in fact I wonder how you are supposed to flash something that belong to bootloader to recovery. Open that recovery in 7z and you will see it. Also the files inside that tar.md5 are compressed again using .lz4 where another recovery posted by the same author is double the size and is just a recovery.img as we should expect. In my opinion this serves other purposes: https://androidfilehost.com/?fid=14655340768118442879 and should not be used, Instead the one on onedrive seems the right one.