Since I don't have 10 posts, I am not allowed to post links. You'll have to copy and paste. Sorry!
There are several guides and videos that explain how to root/install a custom recovery, but they all require Odin (of which distribution is of questionable legality), or at least Windows. I made this guide for those that can't or don't wish to use Windows/Odin.
Prepare
If your phone still has the MDC software, let it update to the MDL version. Updating to MDL will not cause any problems with the following process.
Download and install [bitbucket.org/benjamin_dobell/heimdall/downloads] Heimdall 1.4.0 on your PC. (You don't need the frontend)
[techerrata.com/browse/twrp2/jfltespr] Download the latest TWRP version and save it on your PC. (Get the .img file)
Get a TouchWiz-based kernel and save it on your PC. Several are listed in the "TW KERNELS" section of [THREAD="2303917"]inlineboy's directory[/THREAD]. You can also pull the boot.img file out of a TouchWiz based ROM, which is what I did.
The rest of this guide assumes you are in a terminal window, in the directory where the TWRP and kernel IMG files are located.
Verify Compatibility
With phone off and no USB cable connected, hold volume down and power. When you feel the vibration, release power, but not volume down.
Once you see the warning screen, release volume down.
Press volume up once to continue.
Connect the USB cable.
Type the following command:
Code:
sudo heimdall detect
If you don't see "Device detected", something isn't working correctly. Don't continue any further until you resolve that issue.
The following two commands get the PIT file from your phone and verify the MD5 of the PIT file.
Code:
sudo heimdall download-pit --output stock.pit
md5sum stock.pit
If the MD5 is not cc4f7331a6434a93000b3dd2684b7204, then stop. Something is different with your phone. The MD5 may vary when (if) a 32GB or 64GB version is released. I have only tested with the 16GB version.
You can optionally create a human-readable version of the PIT file with the following command:
Code:
sudo heimdall print-pit --file stock.pit > stock_pit.txt
Disconnect the USB cable and power off the phone.
Flash the Recovery and Kernel
Follow the instructions in steps 1-4 of the "Verify Compatibility" section above to get back to download mode.
Verify (again) that Heimdall sees your phone and then flash the new recovery and kernel.
Code:
sudo heimdall detect
sudo heimdall flash --RECOVERY recovery.img --BOOT boot.img
The phone will reboot into the normal Android OS. Power it off and disconnect the USB cable.
Verify Recovery Mode
With the phone off, hold volume up and power. When you feel the vibration, release power, but not volume up.
Once you see the "Recovery booting...." text in very tiny blue letters, release volume up.
Assuming everything worked, you should see something similar to the below TWRP splash screen and then the actual TWRP interface a few seconds later. From here, you can flash the ROM of your choice or just flash zip file mods.
i.imgur.com/r32KChJ.jpg (I'm not allowed to post images either - *sigh*)
Notes
Although I think it should work, I could not get the custom recovery to load without replacing the kernel. I read somewhere that this is a Samsung thing.
If at any time you see "ERROR: Protocol initialisation failed!", just start over.
I used Heimdall 1.4.0 64-bit on Xubuntu 12.04.2 LTS with TWP 2.5.0.2 and the FreeGS4 2.0.0 Agat-FreeGS4 kernel. Other combinations should work, but you may want to try these exact versions if you are experiencing issues.
I have only tried this with the Sprint version of the Samsung Galaxy S4, which is why I posted in the Sprint forum. The process should be the same with other carriers, but you may need to use a different recovery or kernel. If you have success with another carrier, please share your experience in the comments.
The following is the terminal output of the actual flashing procedure: (with the protocol and 3 repeating letter subdomain removed from the the URLs)
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
(Reserved)
thank you. keep up the good work
Very helpful, thanks for writing this up!
I installed only the recovery and had to add '--no-reboot' to get this to work.
md5
i know this thread is old but just trying to get my cell back, if i can be pointed in the right direction would greatly appreciate it. Been trying and searching for days , but basically the md5 i get is d41d8cd98f00b204e9800998ecf8427e . not sure what to do, kinda regret getting rid of windows now
jillythedog said:
i know this thread is old but just trying to get my cell back, if i can be pointed in the right direction would greatly appreciate it. Been trying and searching for days , but basically the md5 i get is d41d8cd98f00b204e9800998ecf8427e . not sure what to do, kinda regret getting rid of windows now
Click to expand...
Click to collapse
Well, you should probably start a new thread after you've exhausted search results (in this forum and Google). When you do start that thread, give some details about the problem you're experiencing and what you've tried.
Unfortunately, you'll find a lot fewer people using Heimdall than Odin. It was a lot of trial an error for me, and that's why I posted this guide. Both programs do a lot of the same things, but with different interfaces.
Hi guys:
For so long I see anyone trying to flash the ROMS on any UBUNTU/Debian Linux O.S. . 4 or 5 years ago I tested something similar that also worked with Win XP. Thank you for the detailed procedure. I think there's no need for images, but links could help.
It's nice to see someone thinking out of "the Windows box", I know it will help everyone follow that with Win10 issues !
Would this work with the OK3 5.0.1 s4? I'm so lost trying to figure out how to root it because the dates.
imcarloslol said:
Would this work with the OK3 5.0.1 s4? I'm so lost trying to figure out how to root it because the dates.
Click to expand...
Click to collapse
I stopped doing OTA updates on this phone, so I never had that version to test with. I've just flashed custom images since initially rooting it.
CF-Auto-Root does what you're asking for. You could probably just use Heimdall instead of Odin with the tar.md5 file Chainfire provides for this phone. As far as I can tell, there is no magic in the Odin files he provides.
DynamicBIts said:
I stopped doing OTA updates on this phone, so I never had that version to test with. I've just flashed custom images since initially rooting it.
CF-Auto-Root does what you're asking for. You could probably just use Heimdall instead of Odin with the tar.md5 file Chainfire provides for this phone. As far as I can tell, there is no magic in the Odin files he provides.
Click to expand...
Click to collapse
Well I guess I can confirm it for you. It works fine with my phone and I updated from OK3 OTA update 5.0.1 to the 6.0.1. I used the basic Odin method to flash cf root. Then I proceeded to download clockwork mod. Flashed it. Updated to 6.x touch. Then I just flashed the cm13 ROM and the Gapps. I also flashed the Capos. Everything works fine. But is there a way to improve data ? I've been getting just 1x if even that. Would I be able to flash the OK3 modem again? What is the lowest firmware I can flash things to? This bootloader is unlocked correct?
Related
Phone: S4 Active GT-I9295
This is a collection of knowledge from xda-forum and own experience. Consider information found here as advise to avoid possible issues.
Please give feedback if material presented here helped or need correction. Contributors are welcome and due credit will be placed.
Remember to give credit when you copy advice from my thread.
Qcomm based phones i9295 and i9505 need same procedure when flashing. Files to flash is not interchangeable between the phones. Method to flash any item SUCCESSFULLY in Download Mode using Odin is described in this thread.
Some guides may tell you to flash firmware, baseband or modems twice using Odin in Download Mode to "make it stick" or say there is an "unknown bug somewhere". People usually loose IMEI and/or WiFi because they have entered download mode using wrong method and started flash of modem, non-hlos.bin or firmware.
The reason the flashed file won't stick on first attempt is that you have entered download mode by software reboot menu or holding Vol- while rebooting. Don't enter download mode when phone is rebooting.
Remember that you are responsible for every action you do to your phone.
If you don't have Samsung Kies the Samsung USB drivers is reccomended to install before running Odin and connecting PC-USB-PHONE.
Never run Odin to flash phone in Download Mode on the same PC where Samsung Kies is running. Odin and Kies will fight to gain control of USB connected device. Close all running Kies processes in Task Manager or uninstall Kies.
Some Windows installations need to run a Fix It from Microsoft Support to properly detect Samsung phone even after installation of Samsung Android USB driver.
Always connect phone directly to 5V-powered PC USB port - never USB hub.
Use original USB cable or make sure it is in good condition. Cable working for charging can have broken wire making it unusable for communication and file transfer.
GSM modem (modem.bin, *.tar, *.tar.md5) or LTE modem (NON-HLOS.bin, *.tar, *.tar.md5 ) can be flashed using Odin form PHONE/CP without repeating the flash twice.
Download Mode
Why
To flash (change/update) phone recovery, firmware, kernel, bootloader or modem using computer software Odin or Heimdall with phone connected by USB to computer.
How
Completely Power Off , wait at least 5 seconds after vibration or led stop blinking. Now you can enter download mode:
Power + VolDown buttons pressed
Release Power after vibration
Release VolDown when screen turn on
VolUp to confirm
Start Odin as Administrator
Connect USB cable PC-PHONE and make sure ID:COM confirm "Added" phone in Odin
Remark: Home button is NOT USED
Recovery Mode
Why
To flash (change/update) phone custom recovery, custom ROM, SuperSU or kernel by install zip from Custom recovery like TWRP or CWM.
How
Can be entered from the phone reboot menu OR from phone in powered off state:
Power + VolUp buttons pressed
Release Power after vibration
Release VolUp when you see blue text RECOVERY BOOTING.... in upper left corner of screen
Remark: Home button is NOT USED
ROOT
When you have stock recovery and plan to flash a custom recovery like TWRP or CWM (ClockWorkMod) the first time, you need to enter Recovery Mode immediately on first boot after Odin flash custom recovery.
The steps are independent of the stock Android version currently installed on your phone, this is how it's done for both Kitkat 4.4x and Lolipop 5.0x
The steps are also independent of which custom recovery (CWM-based or TWRP)
you prefer.
Advice to use the latest version custom recovery built for i9295 - linked in post #3
WARNING: The CWM built by LeJay back in 2013 on CM10.2 source (=CWM-Recovery-gt-i9295_v1-2.tar.md5) do not support external SD card or Nandroid backup/restore for Samsung Kitkat 4.4x or Lolipop 5.0.x. That recovery is outdated.
Make sure you have minimum 60% battery capasity
1st step - Install custom recovery
Copy SuperSU(latest).zip to phone storage
Power off, Boot phone to Download Mode
Start Odin with AutoReboot disabled, Re-Partition disabled
Connect USB cable PC-PHONE
Odin flash (CUSTOM-RECOVERY).TAR.MD5 as PDA
Disconnect USB cable
Remove phone battery - wait - insert battery
Enter Recovery Mode
2nd step - Install SuperSU from custom recovery, TWRP or CWM
TWRP touch "install" / CWM go to "install zip" by VOLUME buttons
TWRP touch-select / CWM select by pressing POWER button
Browse to and select SuperSU(latest).zip
Reboot
Download files from links in post #3:
(USB drivers, Odin, Custom recovery, SuperSU)
If you wonder what is baseband, baseband version, GSM modem, LTE/4G modem, and find time to read and courtesy to suppress the urge to ask same question recently explained -
... here is a treat for you:
MODEM.BIN and NON-HLOS.BIN HOW-TO flash using Odin
Alternative solution
Thanks @Formhault
What version of modem.bin can you flash?
Thanks @hawkerpaul
Make sure you have non-hlos.bin and bootloader version match:
http://forum.xda-developers.com/showthread.php?p=62994941
Samsung lettercode decoded for firmware/bootloader/modem
Example: I9295XXUCNE4
I9295 = phone model
XXU = baseband (XXU is Global, valid almost everywhere, any country regardless of carrier)
C = baseband build version
NE4 = datecode
Datecode
N = year = 2014 (14th letter of alphabet)
E = month of year (May in this case, 5th letter of the alphabet)
A = build # of that month (10th for, "A", as they start 1-9, then letters)
NE4 = 2014, May, Build 4
NE5 = 2014, May, Build 5
NH2 = 2014, Aug, Build 2
Identify your bootloader
Make sure you have LTE/ audio/ network certificate (=NON-HLOS.bin) version matching your bootloader (=ABOOT, SBL*, TZ) version. Reason explained in 1st post.
NON-HLOS.bin inside the apnhlos partition /firmware and the bootloader is never updated or downgraded by AOSP/CM ROMs or custom recovery flashing. Some customized stock ROMs may mess with the relationship between bootloader and NON-HLOS.bin. Or you have messed up because you wanted to have the latest modem and flashed a *N-- version NON-HLOS.bin on your *M-- version bootloader. This will have bad impact on sound and WiFi functionality leading to you can not activate WiFi.
Earlier versions of PhilZ CWM recovery had an option to wipe partitions
/firmware
(LTE, audio, network certificate, NON-HLOS.bin)
/firmware-mdm
(GSM-modem, MODEM.BIN)
This wipe was not needed because flashing to this partitions overwrite the existing content. Wiping the same partitions without flashing modem or complete stock ROM can render telephone, audio and network functionality useless.
The partitions /firmware and /firmware-mdm is removed from later PhilZ Recovery fstab.
Ref. PhilZ Recovery 6.23.9 change log http://forum.xda-developers.com/showpost.php?p=51389599&postcount=3520
Identify bootloader and select corresponding NON-HLOS.bin
NON-HLOS.bin is also called LTE-modem or WiFi-fix when discussed in xda-forum
1. Connect phone from ADB or use Terminal app and do this command:
Code:
getprop ro.bootloader
( ADB =Android Debug Bridge )
The output is Samsung lettercode and will tell what version of bootloader you currently have.
2. Select version of NON-HLOS.bin to flash according to 3rd last letter of Samsung lettercode bootloader:
BOOTLOADER 3rd last letter = NON-HLOS.bin 3rd last letter
I9295xxxxMxx = I9295xxxxMxx JellyBean 4.2.x
I9295xxxxNxx = I9295xxxxNxx KitKat 4.4.x
I9295xxxxOxx = I9295xxxxOxx Lollipop 5.0.x
Not known exactly what's first version of i9295 firmware/bootloader that has Knox feature. Strong indications nominate all KitKat 4.4.x to have it on QualComm based phones. And GT-I9295 has QualComm chipset.
Updating bootloader to a higher version should not trigger Knox 0x1, but downgrade Knox featured bootloader may cause that.
Status of KNOX is shown in Download Mode upper left corner of screen.
This S4 thread discuss the limitation introduced by Knox:
http://forum.xda-developers.com/showthread.php?p=45666586
Samsung firmware
Sammobile and Samdownloads links removed for violating XDA rules 11 & 13
7-zip v9.3x beta
- Bootloader, modem.bin, NON-HLOS.bin can be extracted from firmware tar package using 7-zip. The extracted files can be flashed one-by-one using Odin or Heimdall.
Heimdall
- a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung mobile devices.
Odin v3.07
- Samsung (leaked) tool to flash firmware files to phone from Windows.
- default setup with unticked Auto Reboot, best setting for recovery 1st time flash.
- faster summary of flash results, 10 seconds.
(attachment)
Samsung USB Drivers for Mobile Phones (v1.5.45.0)
MultiROM TWRP
- custom recovery
[quote name="O-T" post=57277967]Interested in replace CWM 6.0.5.0 with TWRP. Not sure if ready to use the rest of mulirom setup yet. Is TWRP stand-alone capable of replacing CWM in a single ROM setup?[/QUOTE]
Developer spegelius reply:
"Yes, TWRP works without MultiROM. There are few checkboxes, like Inject MultiROM that need to be disabled when installing roms for example, but basic stuff works without multirom."
CF-Auto-Root
- install and enable SuperSU on your system, so apps can gain root access.
- Odin included and pre-setup to flash root to phone from Windows.
What's installed
SuperSU binary and APK
Stock recovery (note that any other recovery you may have installed will be overwritten !)SuperSU
- install and enable SuperSU on your system, so apps can gain root access.
- SuperSU flashable zip is installed using custom recovery (like TWRP)
What's installed
SuperSU binary and APK
Credits
@spegelius MultiROM TWRP
@Chainfire CF-Auto-root, SuperSU
Bevare the Thanks Button under each post - it's there for you to show you are happy to receive help
Dear friend,
I read carefully all the tread but was unable to determine weather my device can be TWRP recovered via Odin or not (multirom_twrp_20150215_000001.zip - from your repository).
I feel a bit dumb to ask but would really appreciate some help.
GT-I9295
4.4.2
I9295XXUCNI1
Default KARNEL
Already ROOTED - CF-Auto-Root-jactivelte-jactiveltexx-gti9295.zip
Thanks in advance and sorry for bothering you
Thomas.A.A said:
Dear friend,
I read carefully all the tread but was unable to determine weather my device can be TWRP recovered via Odin or not (multirom_twrp_20150215_000001.zip - from your repository).
I feel a bit dumb to ask but would really appreciate some help.
GT-I9295
4.4.2
I9295XXUCNI1
Default KARNEL
Already ROOTED - CF-Auto-Root-jactivelte-jactiveltexx-gti9295.zip
Thanks in advance and sorry for bothering you
Click to expand...
Click to collapse
If you're still running Samsung default recovery start to flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin. Zip packed twrp recovery has built in update script made for updating from custom recovery only. You can use zip packed to update or change only after custom CWM based or TWRP recovery is installed in phone. Zip file can then be copied to phone internal storage or SD card and run from custom recovery to update when you want to update/downgrade or change to a different recovery.
Custom recovery doesn't run tar or tar.md5 files. They are made for Odin or Heimdall flashing.
O-T said:
If you're still running Samsung default recovery start to flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin.
Click to expand...
Click to collapse
Thanks for the quick reply (really appreciated!)
Though... I am now even more confused X*X*X!!
Still I will follow your lead:
1. I will Flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin
2. I will do NOT Flash multirom_twrp_20150215_000001.zip in Download Mode using Odin, because...
O-T said:
Zip packed twrp recovery has built in update script made for updating from custom recovery only.
Click to expand...
Click to collapse
and also because...
Custom recovery doesn't run tar or tar.md5 files. They are made for Odin or Heimdall flashing.
Click to expand...
Click to collapse
3. Afterwards, I can freely do the hack I want with ZIP packed, since:
You can use zip packed to update or change only after custom CWM based or TWRP recovery is installed in phone. Zip file can then be copied to phone internal storage or SD card and run from custom recovery to update when you want to update/downgrade or change to a different recovery.
Click to expand...
Click to collapse
Sorry I am so dumb.... Thanks for posting
Really appreciated
1 yes
2 yes
3 yes. Perhaps update root to latest SuperSU 2.46 by recovery flashing.
http://forum.xda-developers.com/showthread.php?p=23427715
All right. Read some posts about TWRP in that thread to learn how to use recovery.
Is it possible to downgrade from 5.0.1 bootloader to 4.2.2?
tasken said:
Is it possible to downgrade from 5.0.1 bootloader to 4.2.2?
Click to expand...
Click to collapse
The link in 1st post to investigation by Chainfire is for S4 i9505 from 442 to 422.
Did you read that?
I was able to do it through odin without breaking knox
tasken said:
I was able to do it through odin without breaking knox
Click to expand...
Click to collapse
If you have been recovery flashing CM12 5.0.1 lately the bootloader is never touched or updated to any version.
Are you sure you had OB4 lollipop 5.0.1 bootloader?
Update
Add confirm step in download mode
Rearrange paragraph in OP
Update
add SuperSU and TWRP to recovery Why
Update:
- added link to latest Samsung USB drivers
- tidy up post #3 with inline links
Bevare the Thanks Button under each post - it's there for you to show you are happy to receive help [emoji106]
Update :
- rooting steps in post #1
The steps are independent of the stock Android version currently installed on your phone, this is working for both Kitkat and Lolipop.
The steps are also independent of which custom recovery (CWM-based or TWRP)
you prefer. Advice to use the latest version built for i9295 - linked in post #3.
CWM and TWRP steps added to post #1
to Root ANY version of Android
MODEM.BIN and NON-HLOS.BIN
- rewrite how to flash correct version
Hi.
I have a i9295 and I experience problems with log-offs or sim disconnects while wifi is working well.
Will a reflash of modem.bin help?
If yes: where can i get the file required for odin of recovery flash?
Thanks in advance
augek said:
Hi.
I have a i9295 and I experience problems with log-offs or sim disconnects while wifi is working well.
Will a reflash of modem.bin help?
If yes: where can i get the file required for odin of recovery flash?
Thanks in advance
Click to expand...
Click to collapse
Shouldn't be needed if you did this http://forum.xda-developers.com/showthread.php?p=61418876
correctly.
You can do a factory reset.
Read post 1-3 slowly if you need modem.bin, non-hlos.bin or bootloader of right version for you.
ThumbsUp button under every post is free to use in case you're in the mood to show appreciation.
Hi.
I did read and still am not sure about it.
I've done factory reset with every flash but still the problem persists.
Tried a different sim, still on joy.
From the thread linked i can not see where to find the modem for lollipop.
When the mobile disconnects phono tells me ihre some 14 - 16 asu. So service is available.
Drives me nuts.
I've been looking around for ways to root my S3 mini, but it seems the only ways I've found are:
- Using VRoot
- Install another firmware
Problem with VRoot is that it's a Windows application and I only have Linux machines here (both Android and Debian). Problem with installing another firmware is that I'm not sure yet whether I really want to do that.
I tried to install CWM or TWRP but it seems that my S3 mini's firmware is one that doesn't pay attention to the recovery partition, so after Heimdall uploads those recovery.img thingies I'm still stuck the the stock recovery (even though it the upload went successfully and the machine's status is labeled "custom").
In the mean time, I stumbled upon a web-page that suggested that Towelroot might work on my machine.
I tried it and it seems to have worked to some extent: no need for any external computer (neither Windows nor otherwise) and no need to install another firmware. And it did install a `/system/xbin/su` executable which gives me root/
But Lil'Debi doesn't seem satisfied (and Superuser tells me my `su` needs to be updated, tho it's not clear how I could do that), so I made progress but I'm not quite there yet.
Hello,
I successfully flashed three s3minis according the description of www dot goebel-consult dot de slash blog slash install-cyanogenmod-on-s3-mini-using-linux
System (PC): Linux Mint 17
Download files from novafusion.pl/
(first I flashed cm11.0_golden.nova.20150303.ODIN_TWRP.zip and from that newer/different custom roms)
I flashed recovery.img, boot.img and system.img with one command -> for me it was "sudo heimdall flash --Kernel boot.img --Kernel2 recovery.img --SYSTEM system.img", but you should check your partitions on the phone with heimdall, if the partitions are the same.
ps. because of new user, I may not post URLs -> hope you can understand the correct link to goebel-consult
ciao
mofft said:
Hello,
I successfully flashed three s3minis according the description of www dot goebel-consult
Click to expand...
Click to collapse
Thanks, but as pointed out in my original answer I wanted to root my current firmware rather than install a new (rooted) firmware.
When I issue the print-pit command it fails, can't communicate with the device. I install the drivers, debugging mode is on, I know that heimdall works on a Galaxy S4 phone. Thoughts?
I also tried with a 2016 8" several times last weekend, on ubuntu 16.04 and failed.
In the end I decided to go with odin on windows and that worked immediately.
rcook55 said:
When I issue the print-pit command it fails, can't communicate with the device. I install the drivers, debugging mode is on, I know that heimdall works on a Galaxy S4 phone. Thoughts?
Click to expand...
Click to collapse
Why are you attempting to install Lineage with Heimdall instead of TWRP?
Ah, I wanted to install twrp so I could then install lineage.
Good question to OP though.
ashyx said:
Why are you attempting to install Lineage with Heimdall instead of TWRP?
Click to expand...
Click to collapse
Was following these directions: https://wiki.lineageos.org/devices/gts210vewifi/install which suggests that I use Heimdall to install TWRP. I'm glad to use a different method, can you link to a good guide?
rcook55 said:
Was following these directions: https://wiki.lineageos.org/devices/gts210vewifi/install which suggests that I use Heimdall to install TWRP. I'm glad to use a different method, can you link to a good guide?
Click to expand...
Click to collapse
What?
Your title was Trying to install Lineage not TWRP?
ashyx said:
What?
Your title was Trying to install Lineage not TWRP?
Click to expand...
Click to collapse
I am trying to install Lineage, as part of installing Lineage I need to install TWRP, however following the posted direction at the Lineage wiki I am having an issue with Heimdal so I'm having a time installing TWRP so that I can install Lineage. You were the one that focused on TWRP. My question is, while a bit vauge, still valid. To re-ask this question a better way, how can I get TWRP installed without using Heimdal on my Tab S2?
rcook55 said:
I am trying to install Lineage, as part of installing Lineage I need to install TWRP, however following the posted direction at the Lineage wiki I am having an issue with Heimdal so I'm having a time installing TWRP so that I can install Lineage. You were the one that focused on TWRP. My question is, while a bit vauge, still valid. To re-ask this question a better way, how can I get TWRP installed without using Heimdal on my Tab S2?
Click to expand...
Click to collapse
Just in case anyone else comes across this: I ran into the same problem. Here's some notes to help anyone else who runs into this.
The current release (1.4.0) is known to not work.
The current source version (1.4.2) when compiled on windows progressed further: I could read the PIT table, but could not load TWRP recovery. It would successfully upload, but then get a timeout error. Restarting and booting into recovery crashed.
The current source version (1.4.2) when compiled on linux worked fine.
One subtle thing not clearly noted on the lineageos page: after you load recovery onto the tablet, you need to restart the tablet (home+vol-down+power), then switch *immediately* to "enter recovery" (home+vol-up+power) as soon as the screen blanks from the power down.
So my advice: install (or run from a livedcd, or use virtualbox) linux and do your heimdall run there; don't waste time on windows.
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recovery And Install PreRooted Firmware Of Your Choice!.
I posted this because the current unlock methods are not easy to do. This should make process easier
If you already have unlocked bootloader and want to change bootloader versions then goto post 2
Downloads
EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK_2021.7z
Instructions
1, You need working adb on your computer. The latest samsung drivers installed. A Sdcard inserted in the phone preferably a 32 gig or less. Must be at least 1 gig. Phone will be wiped! A data connection or wifi is also required.
2. Download and extract the EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK.7z
3. Reboot phone to download mode (pwr+voldwn+home_button). In Odin_Files folder use odin and flash the COMBINATION_VZW_FA44_N910VVRU2APB1.tar.md5 in BL slot in odin
4. Once phone is booted up and connected to computer run 1Install_KingRoot.cmd. This will install kingo root and kingroot app on phone.
5. Once installed make sure phone has data via cell or wifi. Run kingo root to root phone. Phone may kernel panic and reboot just keep trying. Once root is successful move to step 6 if unsuccessful try kingroot if thats succesful click on root permissions in the kingo root app and click on system adb and change prompt to allow. This is not necessary if rooted with kingo app
6. Make sure phone is connected to computer and run1Replace_With_SuperSu.cmd then once this process finishes run 2UnlockBootloader.cmd. This will change CID to Dev edition and then unlock that bootloader. If first time unlocking phone it will change your cid to dev edition then reboot during process. This is fine you will not loose root. Close cmd window wait for phone to reconnect then run again this time it will unlock the bootloaders when done phone will once again power off. Remove sdcard this is very important so I will say again remove SDCard from Phone your phone will not boot with sdcard in until it is reformated! Reboot to download mode you should notice it says DEV Mode.
7. Reboot phone and now you are ready to choose your bootloader you want to be on for this guide we will assume you want to be on latest QL1 Marshmallow bootloader.
8. Make sure phone is connected and run 3UnlockBootloader_MM_QL1.cmd or what ever one you choose. When done Phone will power off and now the bootloader is updated.
9. Now choose the firmware that matches your unlocked bootloader from below
N910VVRU1ANJ5_DEV_ROOTED.tar.rar Kit Kat 4.4 Rooted Firmware
N910VVRU2BOG5_DEV_ROOTED_SUPERSU.tar.rar Lollipop 5.0 Rooted Firmware
N910VVRU2BPA1_DEV_ROOTED_MAGISK.tar.rar Lollipop 5.1 Rooted Firmware
N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar Marshmallow 6.0 Rooted Firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z Marshmallow 6.0 EFTSU Rooted Latest Firmware!!
10 Reboot phone to download mode and flash above firmware that matches your bootloader version Im using N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar as example. Extract N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar and use provide odin from EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK and choose N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.md5 or the one you choose and in odin BL slot uncheck auto reboot and flash. When flash is done make sure to reboot to TWRP recovery which will be installed and wipe data then reboot. You are done!
11. Above firmware running magisk root may til you additional steps are needed and download magisk zip. You can skip this step if you want as it is rooted and magisk apk is installed but if you want I will provide magisk zip used in root if you want to reflash
Upgrade Bootloaders For EMMC 15 VZW DEV Unlocked Phones
This process requires flashing back all stock firmware in order to upgrade/downgrade bootloaders. So I have made a special rom just for doing this which should make process easy. Its all done with odin and flashire.
Downloads
EMMC_15_VZW_NOTE4_BOOTLOADER_UPGRADE_ZIPS_2021.7z
N910VVRU1ANJ5_DEV_ROOTED.tar.rar Kit Kat 4.4 Rooted Firmware
N910VVRU2BOG5_DEV_ROOTED_SUPERSU.tar.rar Lollipop 5.0 Rooted Firmware
N910VVRU2BPA1_DEV_ROOTED_MAGISK.tar.rar Lollipop 5.1 Rooted Firmware
N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar Marshmallow 6.0 Rooted Firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z Marshmallow 6.0 EFTSU Rooted Latest Firmware!!
Instructions
You must be on EMMC 15 unlocked bootloader if not goto post 1 to unlock bootloader
1. Download the EMMC_15_VZW_NOTE4_BOOTLOADER_UPGRADE_ZIPS.7z and extract this will contain the zips and special firmware for upgrading bootloader. Download above firmware you want to upgrade/downgrade too.
2. You will probably need to wipe data so reboot to TWRP recovery wipe data then reboot to download mode use provide odin in the Odin_Files folder and choose FIRMWARE_FOR_UPGRADE_DOWGRADE_BOOTLOADERS.tar.md5 and flash in BL slot.
3. This will reflash stock firmware and a prerooted special rom with a flashfire preinstalled and minimal files just to boot rom. Your bootloader will be locked for the time being as this is necessary to upgrade bootloaders.
4. When rom is booted choose the zip that matches the firmware you want to install from the FlashFire_Zips folder and place on phone storage.
5. Open flashfire grant root access choose add zip choose the zip you placed on phone click on reboot tab in flashfire and choose reboot to bootloader in will say dev mode this means your unlocked again
6, Now choose above firmware you downloaded extract the tar.md5 file from the rar file and flash in BL slot in odin Uncheck auto reboot when don flashing force reboot to TWRP recovery and wipe data again then reboot phone. You are now Upgraded or downgraded which ever you choose to do.
Mine
This has been needed in our forum for a long time. Fantastic work, thanks!
jrkruse said:
Mine
Click to expand...
Click to collapse
Hello
I want ask u do you know how to open bootloder for huawei mate 20 pro lya.l09
Thx
theohtc said:
Hello
I want ask u do you know how to open bootloder for huawei mate 20 pro lya.l09
Thx
Click to expand...
Click to collapse
Maybe ask in the huawei thread.
Sent from some device I modified
How many times does it usually take for kingroot?
UPDATE: Tried many times and eventually it said "Root Failed" "no strategy now"
DeeXii said:
How many times does it usually take for kingroot?
UPDATE: Tried many times and eventually it said "Root Failed" "no strategy now"
Click to expand...
Click to collapse
I would start over completely. Reflash the Odin files then make sure you have internet access i would use wifi when running kingroot app
Sent from some device I modified
jrkruse said:
I would start over completely. Reflash the Odin files then make sure you have internet access i would use wifi when running kingroot app
Sent from some device I modified
Click to expand...
Click to collapse
Ok I will reflash...
Yes I had internet access, Kingroot does not even function without it.
Thanks for the fast reply!
---------- Post added at 06:15 PM ---------- Previous post was at 05:54 PM ----------
Can't seem to get passed 35%
---------- Post added at 06:41 PM ---------- Previous post was at 06:15 PM ----------
UPDATE:
I used Kingroot desktop version and it rooted the first try.
On to the next step.
---------- Post added at 07:20 PM ---------- Previous post was at 06:41 PM ----------
How long does N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.md5 take to flash?
It has not errored out at all but it seems to be taking longer than I have ever seen.
It's on tz.mbn.
@jrkruse THANK YOU for putting this into such a simplified method that doesn't require large downloads, multiple command lines, or having to downgrade and re-upgrade just to be able to achieve an initial root, unlock, and TWRP!!! I read through way too many methods that were a MILE long before I happened across this one. The ONLY issue i ran into during this process (should help others), was that I had to insert a newer version (and rename it to match the script) of the KingRoot APK to be able to achieve root on my existing CQL1 firmware. I tried the provided APK many times without success, but a newer version was able to achieve root on CQL1 after only a few attempts/reboots. I downloaded the newer APK (version 5.3.7) from the post provided by @Kingxteam at https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461. If anyone is looking for a simple way to root and unlock CQL1 without having to downgrade first, THIS IS IT!!! Thanks again jrkruse for the automated script, and thank you Kingxteam for the thread and links for a KingRoot APK that works with CQL1!!!
I'm getting a bit fustrated by the rooting process. Hopefully someone would be able to help me out.
Once I finished step #3 and boot into the dev and I try to root, it fails. I have tried several times and keep on failing. I took a different route and approach by reinstalling the image and re installing the kingroot and the same. Finally I gave up, and replaced the kingroot apk by its newest release. Eventually I get rooted, but once i try to unlock the boot loader i get the following message "/system/bin/sh: su: not found" .Randomly I was able to successfully run unlookbootloader once, but once the device reboots, i lose root.
Im not sure what to do, to keep root at this point.
Jalh said:
I'm getting a bit fustrated by the rooting process. Hopefully someone would be able to help me out.
Once I finished step #3 and boot into the dev and I try to root, it fails. I have tried several times and keep on failing. I took a different route and approach by reinstalling the image and re installing the kingroot and the same. Finally I gave up, and replaced the kingroot apk by its newest release. Eventually I get rooted, but once i try to unlock the boot loader i get the following message "/system/bin/sh: su: not found" .Randomly I was able to successfully run unlookbootloader once, but once the device reboots, i lose root.
Im not sure what to do, to keep root at this point.
Click to expand...
Click to collapse
Did you install the combo firmware because you don’t loose root when on the combo firmware
Sent from some device I modified
Hello all. I'll start by acknowledging that I am a noob with very little experience but can follow technical instructions to achieve desired results when they are described easily for the uninitiated. That said, I too have 2 Verizon note 4s running marshmallow with build numbers ending in CQL1. Following your tutorial, I was able to get one of my phones to step 4 where as described, it kept showing the kernel panic error no less than 10 times. I took the suggestion of another user and was finally able to achieve root with the Kingroot desktop app on my PC. I then clicked on root permissions and changed the prompt to allow. At this point I proceeded to step 6 and after clicking 2UnlockBootloader.cmd, the phone did not reboot as described and the command window returned the following message:
D:\Desktop\EMMC>adb wait-for-device
You May Need To Accept Root Dialog On Phone ...
Files/n4unlock\: 1 file pushed. 1.2 MB/s (23432 bytes in 0.018s)
cd /data/local/tmp/n4unlock
chmod 777 unlock
chown root.root unlock
./unlock
yes
exit
/system/bin/sh: su: not found
Process Complete.
Press any key to continue . . .
No dialog box appeared on my phone and I'm not sure why it says SU not found or what the significance of that missing item is to the process. Am I missing a step? Assuming I have not unlocked the bootloader with step 6, what now? What should I do at this point to achieve the desired result? I do realize that these are older phones and some might care less but making them work now could help my family in a big way. I'd gladly share some of those savings with anyone willing to help troubleshoot... thanks in advance.
Hanging on 1st BL file
Not my first time but seems like im getting hing up during the first flash. how long does it normally take for this 1st BL to flash over
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 636 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
Hung here for about 10min any help would be great thanks!
jrkruse said:
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recovery And Install PreRooted Firmware Of Your Choice!.
I posted this because the current unlock methods are not easy to do. This should make process easier
If you already have unlocked bootloader and want to change bootloader versions then goto post 2
Click to expand...
Click to collapse
Working perfectly & really much much easier (than the original method which I have done twice so far so I know what I am talking about)!! Thank you
I have to throw in my hat saying that this method didn't work for me either. Like others I got stuck at the rooting stage, I tried numerous times to get root, it didn't work. I then used the upgraded KingRoot, it worked but step 6. 2UnlockBootloader.cmd script wouldn't take, since it seemingly kept losing root. But don't worry, if you've tried this method and are stuck you can still salvage it by going through the manual methods.
Make sure reactivation lock is off if you have the option (I didn't on the firmware that OP installed on the phone), usb debugging is on and adb devices brings up your phone)
----
Flash back to stock
----
I had to flash it to a stock rom using Odin (stick them in AP and make sure re-partition in options isn't checked) Android version 5.1.1, as going through the steps below (which are basically what's in 2UnlockBootloader.cmd) manually still wouldn't take: https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
----
Root and bootloader unlock
----
I used the android version of KingORoot to root
I used this guide (the files used in this walkthrough are the ones largely used in the others below and downloads faster): https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Which has a video here: https://www.youtube.com/watch?v=cfpehEkhfyg
and a text walkthrough with photos (that I like more) from the same guy here: https://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
(Since I largely used this make sure you put "samsung_unlock_n4-fix" in the fastboot folder)
Mine however began to bootloop (I'm unsure why they tell you to reboot to system on step 19 after installing the systemonly firmware but do it anyways I guess. But you had to install the kernel and superuser in twrp as addressed here: https://youtu.be/dhcV93GuHB4?t=1285
After that it booted up to 5.1.1 download rootcheck to root check it.
----
Rooting for Marshmallow
----
After that's done if you want to flash MarshMallow roms, including rooted stock 6.0.1 then you need to further go through the process here, which is basically doing it all over again:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
(Going through this process will kill your wifi connection, the KingORoot PC program didn't work to re-root mine, so you must have a sim card data connection I guess (or reverse tethering if you can get that to work(I had data so I didn't go through that).
then here when you get to the part about flashing a rom:
https://forum.xda-developers.com/no...firmware-safe-upgrade-to-marshmallow-t3402727
(Flashed with Odin (AP) not TWRP)
Anyway, I'm now rooted and bootloader unlocked. It wasn't too hard, once I found the guides it went pretty smoothly. Good luck!
using this method I get a black screen after booting up any aosp rom... logs from booted lineageos17.1:
https://pastebin.com/7yhL7FzM
I rooted 3 910v phones with this method. and am running unofficial Lineage 18.1 roms on all 3 kingroot for pc worked for me.
I updated root files and method too work on newer computers
Added latest firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z
jrkruse said:
I updated root files and method too work on newer computers
Added latest firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z
Click to expand...
Click to collapse
Thank you again for making our life easier, the ones who will appreciate your efforts are the ones who have done it manually ROCK ON!
Long story short: I tried to install a GSI so I installed TWRP and flashed some necessary zips (vbmeta, mutidisabler, ...) from different sources and the GSI, but maybe it was a bad idea to follow multiple sources, because the phone was bootlooping when I tried to reboot into system. I then wiped everything and reflashed everything but that didn't fix it. After meddlilng around for a while, I was able to get into the download mode, so I thought of flashing the factory firmware with Heimdall. I used samloader and downloaded the supposedlly correct firmware (M215FXXU2BUH6/M215FODM2BUI1/M215FDDU2BUH1/M215FXXU2BUH6, region is BKD). When I was adding the files, I found out that I was missing the following files:
md5.img (MD5HDR)
efs.img (EFS)
sec_efs.img (SEC_EFS)
nad_fw.bin (NAD_FW)
param.bin (PARAM)
steady.bin (STEADY)
uhuh.bin (UHCFG)
blcmd.bin (BLCMD)
spu.img (SPU)
ul_key.bin (UL_KEYS)
nad_refer.bin (NAD_REFER)
dqmdbg.img (DQMDBG)
There were other partitions, but no files were listed for them, so I think they are not supposed to be flashed. There were also two different "fota.zip" files, but I didn't know what to do with them. Anyway, I flashed the other files, but the phone started bootlooping with the bootloader unlocked warning screen. I locked the bootloader from the download mode and tried again but no luck. I tried reflashing everything again, but the flashing stopped halfway with the message "super.img blocked by OEM" or something like that. I performed a force reboot with volume down + power and it rebooted into the "Emergency Recovery Function" screen. I reflashed everything again, but this time, without super.img, and it flashed fine, but the same bootloop problem remained. Looking up on the internet, it seems that efs.img has something to do with the IMEIs. I don't have any backup of it. I also don't know how to get the rest of the files (if all of them are even necessary), or what they even do/mean.
Basically, I'm trying to get it back to the factory software, or salvage it in any other way. Does somebody have any idea how to fix it?
Naah... Stuff like this happens to me all the time.
Download this ODIN first: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then download this firmware: https://samfw.com/firmware/SM-M215F/BKD/M215FXXU2BUG2
Now first a few things:
1. You probably downloaded a engineer firmware that isnt allowed as of now.
2. Heimdall is mostly dead, last I checked. It isnt very wise to use it.
3. LOCKING THE BOOTLOADER IN A UNSTABLE STATE IS FOOLISHNESS. I do not mean to offend anyone, but pls dont do this.
4. I think you are using ErfanGSI/ some other port. These will NOT work. Only phhusson's GSI's have worked for me so far.
So coming back to the topic, Just open up the ODIN and connect up your phone. It will get recognized. If it is not in emergency/ download modes, just hold vol down + power, then press both vol buttons and connect to pc immediately - it will boot into dl mode.
Select the BL, AP, CP and HOME_CSC. Flash these.
It should reboot right back up into stock.
Also, are you using my vbmeta zip from ItsMeKande's thread?
Chill
GuruPrasadAH
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
GuruPrasadAH said:
Also, are you using my vbmeta zip from ItsMeKande's thread?
Click to expand...
Click to collapse
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
newt23 said:
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
Click to expand...
Click to collapse
My to-go answer is always crdroid. Its lightweight, customizable, and comes in variants with gapps, foss and vanilla. The one you're looking for is vanilla. Here's the post where u can find the link
Any official or unofficial lineage OS for Samsung galaxy M21
Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!! 🙏🏾🙏🏾🙏🏾
forum.xda-developers.com
Hmm, it didn't work. I get bootloops...
Did you follow all the instructions given in that thread?
Only if you flash vbmeta, Multidisabler it will boot.
Then too magisk is recommended. The zips are in that thread.
Follow the instructions and let me know. On guy OldNoobOne also successfully flashed and booted a gsi
Let me know if it works
Chill
GuruPrasadAH
For Multidisabler just do a google search one for samsung devices will appear
Here's what I did (stock firmware, unlocked bootloader):
1. Boot into dl mode
2. Flash TWRP and boot into it
3. Wipe > Format data > "yes"
4. Reboot > Recovery
5. Advanced > Terminal
6. "cd external_sd/flash"
7. "super mount system"
8. "super flash system crdrom-v313-210921-arm64-bvZ-lite.img"
9. Install > vbmeta.zip, multidisabler-samsung-3.1.zip"
10. Reboot into system
And I get bootloops. Multidisabler detects Android 10, doesn't find the stock recovery and fails to mount /system. Maybe that's the problem? I'm using this one.
Also try flashing magisk... I dont really understand what is happening to you.
Maybe you set the system as read only? Really not sure.
Also, a ROM might be coming soon
Chill
GuruPrasadAH
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
newt23 said:
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
Click to expand...
Click to collapse
Use Overlay-Fix by dev Yillie. It had worked for me on crd too. You will find Yillie on telegram 'Galaxy M21 Updates' group, download from there.