[Q] Rooting SM-N910P using Linux & Heimdall - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

Need someone with linux and heimdall experience...
Using Kali Linux
Fully updated and upgraded
Heimdall detects my SM-N910P (in download mode)
I have the proper CF-Auto-Root-trltespr-trltespr-smn910p.tar.md5 (which I believe is Odin based)
I have Odin working using Wine but it doesn't detect my phone (believe me I've tried everything)
or the
TWRP - openrecovery-twrp-2.8.1.1-trltespr.img.tar (which the .img [recovery.img] is inside)
I also have the proper SuperSU zip (UPDATE-SuperSU-v2.37.zip)
So cant I just:
"sudo heimdall flash --recovery recovery.img"
"sudo heimdall flash --cache cache.img"
then "adb reboot recovery" and flash the SuperSU .zip?
Thanks for the info and help.

PM @jlmancuso
He is familiar with heimdal. For odin not to detect your phone on windows has to be a driver issue. Uninstall samsung drivers. Reboot. Download the latest drivers and put your phone in download mode BEFORE plugging into your pc for the first time. Usually Win 7 will download and install the correct drivers if their not found on your system. Im thinking youve tried all this already but sometimes we overlook the most simple things.

bostonsean said:
Need someone with linux and heimdall experience...
Using Kali Linux
Fully updated and upgraded
Heimdall detects my SM-N910P (in download mode)
I have the proper CF-Auto-Root-trltespr-trltespr-smn910p.tar.md5 (which I believe is Odin based)
I have Odin working using Wine but it doesn't detect my phone (believe me I've tried everything)
or the
TWRP - openrecovery-twrp-2.8.1.1-trltespr.img.tar (which the .img [recovery.img] is inside)
I also have the proper SuperSU zip (UPDATE-SuperSU-v2.37.zip)
So cant I just:
"sudo heimdall flash --recovery recovery.img"
"sudo heimdall flash --cache cache.img"
then "adb reboot recovery" and flash the SuperSU .zip?
Thanks for the info and help.
Click to expand...
Click to collapse
most likely you will get an error about your partition be invalid if you use those commands. try "sudo heimdall flash --RECOVERY recovery.img". Samsung has their partition names in CAPS. If you need any more help just hit me up and I will share with you what I know.

Related

Install cwm via mac or Linux?

Guys how to install cwm and remove stock recovery via mac or Linux on unlocked device ?
Need help plz!
Tnx!
The procedure is the same as it has always been, in short:
1 - install the Android SDK
2 - unlock your bootloader
3 - download the recovery image file
4 - using the fastboot command in the Terminal, flash it like this (for example)
~/android-sdk-macosx/platform-tools/fastboot flash recovery ./clockworkmod.img
The paths and filenames will depend on where all the files are located.
I'm assuming you have experience with the command line to be able to understand this.
PS: you would have to use the same method to flash boot.img when flashing custom ROMs, as they cannot be installed from recovery yet. Just replace "fastboot flash recovery recovery.img" with "flashboot flash boot boot.img"

Odin Keeps Crashing...

Hi,
I've been trying to update CWM to touch recovery, and I used the toolkit to make a tar file out of the recovery file for the touch version of CWM I downloaded from Clockworkmod website, the phone connects to Odin just fine, just that when I hit "Start" I get an error saying Odin has stopped working. I'm using the "PDA" section, and am in download mode for the phone. I'm using Windows 8, recently upgraded, last I used it on Windows 7 it was working just fine. I did uninstall, reinstall newest version, didn't work. Also older versions didn't work either. I tried installing Kies to install any usb drivers, and still no luck. Anything else I can try? Thanks.
use adb or terminal emulator to push the recovery.img from the root of your internal sd card.
in terminal emulator:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
if you use adb do the same but use 'adb shell' first.
sent from my I747
Or you can flash the recovery.img with mobile odin no problem if your not comfortable using adb
Sent from the scary door.....
Hey guys thanks for the help! I did it through Odin Mobile and it worked. Thing is I noticed I didn't name the image file "recovery.img" which must have been the case because it was also not working in Mobile Odin as well until I did that. Didn't try it on the PC one. Just thought I'd put it out there in case anyone found this thread having the same issue and tried everything. :victory: Thanks again guys.

Please: Options to Update recovery 6.0.3.6 in IMG file ? (fastboot not work here)

I did download the CMW 6.0.3.6 Direct page of Cyanogen team.
The file came in IMG.
How do I do the update? Only via fastboot?
Tried with fastboot but could not, the command is not recognizing my Note2.
Edit: Heimdall not work, too.
Can anyone give me a hand?
PS: i use windows 8, and the prompt command is:
(Windows Button + X) and open list of various options, i click Prompt.
Open in my user, i use the command: cd "folder" to open the folder when have the ADB and the IMG file, then i put "fastboot devices" and not list my device. I try reboot, and nothing...my Note is not recognized.
In the past, i use this folder to my Galaxy Nexus. It would be a problem of incompatible file or something?
Other method to update this recovery 6.0.3.6 ?
Thanks for attention.
------------------------------------------------
Solved.
I used Mobile Odin Pro.
Moderation: could be delete this thread.
Thanks.

Samsung Galaxy Tab 3 Lite SM - 110 only recovery and bootloader is going to boot

I try to root my Galaxy Tab 3 Lite with heimdall.
Code:
heimdall print-pit
Code:
heimdall flash --RECOVERY recovery.img
As this doesnt work creating with dd a img file that is filled with nothing and name it cache.img
Code:
heimdall flash --RECOVERY recovery.img --cache cache.img
Now my Tablet completly stocks after a restart I got some message that the Firmware is broken.
I try again
Code:
heimdall flash --RECOVERY recovery.img
Then the light of my display is flickering and the device turn complete of.
After I start the phone back on I only can boot in recovery and with the shorcut HOME + Volume Down + Power Button I starting the bootloader or how ever it is calling also the Download Mode.
I try to install different ROMS button no ROM works so what can I do?
I cannot use Samsung Kies anway, because I have no Windows Computer.
I am on Linux yet.
unityself said:
I try to root my Galaxy Tab 3 Lite with heimdall.
Click to expand...
Click to collapse
heimdall does not support the T100 device yet.
i guess there is no open source for the actual flash business

help rooting?

I have the latest driver's installed.
I have tried multiple adb drivers and multiple windows 10 computers with no luck
I have downloaded latest firmware. I extracted it. I got the boot img. I loaded it on my phone.
I patched it with magisk.
When I open up cmd promo and type fastboot devices I'm given an id
But when I go to flash the boot img cmd says partion not there. Can someone please help?
Jmcarls20 said:
I have the latest driver's installed.
I have tried multiple adb drivers and multiple windows 10 computers with no luck
I have downloaded latest firmware. I extracted it. I got the boot img. I loaded it on my phone.
I patched it with magisk.
When I open up cmd promo and type fastboot devices I'm given an id
But when I go to flash the boot img cmd says partion not there. Can someone please help?
Click to expand...
Click to collapse
I patched it with magisk. , This file need to be in adb folder .
Are you trying to adb sideliad or fastboot it?
Personally i would use the following command:
Fastboot flash boot magisk_patched.img
This of course assumes a few things:
1) that you have put the phone in bootloader mode
2) that you are connected via usb cable to a pc
3) that the adb devices command shows your device
4) that you didn't rename the patched boot image file magisk created for you
5) that the fastboot, adb and patched magisk file are all in the same location and that you issued that command from that same location.
Not trying to ignore the topic of this thread, but shouldn't this be under discussions? It's currently under ROMs and Kernels and Development, which is reserved for new projects rather than questions about rooting..

Categories

Resources