Being an habitual Linux user, what options and tools will be available to me to help root an S3?
Hello Linux user!
Heimdall works on Linux: http://forum.xda-developers.com/showthread.php?t=755265
But I don't know whether it works to specifically root the SGS3 with. I've never used Heimdall myself, so I'm just providing the link, and you can investigate further...
Sorry guys, site has been down for the last few days due to my server changing nodes and the DNS records being out of date.
It might take a while for the DNS records to propagate out to whichever DNS servers you're using, however you should be able to find Heimdall at my website:
http://www.glassechidna.com.au/
I haven't tried Heimdall with SGS3 yet, however I do own one. Official support will be coming when I get a chance (probably next weekend).
Related
I was curious if any of the dev gurus had a nice Linux setup that they could make a Android Development distro from?
I keep running into repo issues when trying to set up my system. This led me to go.....'why isn't there a precompiled dev distro??'
If there is....please point me towards it, as I have been searching, but if it exist it's in a deep dark part of the internet I'm yet to discover.
Thanks
(ps. I wanted to make a clockwork recovery for an unsupported device.)
I keep running into repo issues when trying to set up my system.
Click to expand...
Click to collapse
I think the best Idea is to set up an Ubuntu based system at the moment.
With fedora based distros (fuduntu) I allways get some issues as well.
Some month ago I ran into a site that provided some Ubuntu based virtual box images with the Android SDK installed, but as it changes alot lately I don't think it's up to date, and I can't find it anymore anyway.
Maybe the guides aren't accurate anymore??
The distro I tried was the newest Ubuntu, but with everything I attempted to install I would get permission issues and sometimes the links to repo's weren't live any longer..
Perhaps what I should ask is 'Where can I find an accurate, reliable guide to setting up my linux distro for dev use?'
eh, I'm not completely dumb to Linux, but I require a bit of assistance :/
Ya, Ubuntu is kinda mandatory considering the way the kernel in AoS forked from it. Ubuntu is a common one, should be able to do what you need off the USB bootable even.
Really depends on your hardware setup. I've been playing around with a portable Puppy lately - something I can use at work and on my ancient semi-sandbox laptop. If you like I can put a vanilla package together for you.
There is a distro from 2010 made by a beginning builder specifically for linux/android developers. I haven't used it but it may be worth a go: http://www.simply-android.com/discu...oid-developers-have-their-own-linux-distro/p1
Hi,
I'm a dev working on Mozilla's Boot2Gecko project. We've run into an issue with heimdall, and I'm trying to get ahold of the dev to discuss this further.
One of my coworkers created an issue on github, and I've added some comments, but neither one of us has received any replies, so I'm posting here to see if that helps.
The problem that we've run into, is that I can use heimdall fine when our system.img file is 100Mb or less, but get failures or corruption when system.img is 100Mb or larger.
My phone is a Samsung GT-I9100 (Samsung Galaxy S II). I upgraded the firmware to ICS using the XXLPQ firmware (I used this page: www dot theandroidsoul dot com slash xxlpq (the form won't let me post the url since I've posted less than 8 times), so its possible that the problem is related to newer bootloaders.
I have a system.img file that is 115Mb, and the command line I use is:
heimdall flash --factoryfs system.img
Under 1.3.1, there is a noticable pause at 87%, then it continues on to 100% and reports success, but the image that is burned into flash is corrupted.
Under 1.3.2, it stops at 87% and reports a failure.
Running with --verbose, the 87% corresponds to 800 packets of 128K each (which is 100 Mb)
If I reduce system.img to under 100 Mb, then both 1.3.1 and 1.3.2 work fine.
My dev machine is running Ubuntu 12.04, and I have a Windows 7 VirtualBox. I see the same behaviour from the Windows 7 VM as I see from ubuntu.
If I use odin (v1.83) from the Windows 7 VM, then it burns it properly.
I took a quick look at the source code and tried increasing the 800 limit (kMaxSequenceLength) and the 128K limit (kDefaultPacketSize), but those both fail as well.
I have packet wireshark captures of the USB streams under linux, and I installed a trial version of USBlyser under windows and have packet captures from both odin and heimdall, should those prove useful.
From the packet captures, odin seems to be transferring 1Mb at a time.
I had the same problems with my ET4G. I posted a pull request on the project's github. I'd link you there but I am not allowed since I am a new user, it is pull request #47. Works for me... maybe it will help you out.
bleffij said:
I had the same problems with my ET4G. I posted a pull request on the project's github. I'd link you there but I am not allowed since I am a new user, it is pull request #47. Works for me... maybe it will help you out.
Click to expand...
Click to collapse
this is certainly not fixed for me for an SHW-M250K (korean SGS II and compatible with I9100 ROMS with minor caveats).
I get extremely similar symptoms(identical as far as I can tell): Consistent corruption where files don't diff against the loopback mounted ROM files and are reprodicibly corrupt for any particular ROM. I saw this on.. I think it was 1.3.2 and then grabbed the latest 1.4RC1 from git and still see the same thing. Flashes with odin on the same hardware in fact in a windows vm within the same host OS.. work just fine. This is really bad especially since, sometimes the corruption isn't that obvious.
It seems to be scattered bits or bytes. Often the system boots but encounters various amounts of bugginess (depending on the EXACT rom, just adding or removing a file from the rom not surprisingly changes which bits and bytes are corrup)t. I guess it's many small chunks that are corrupt because I see typically maybe 80% of files are corrupt but still things kind of work. That tells me it's like a bit byte or small chunk here or there for every few MB probably. Enough to get most files but little enough it doesn't get every file or break them entirely.
I don't have a github account. Maybe I need to make one.
Im writing a Network Scanner currently in Python/Kivy for Android. I could do everything i wanted if i could execute a Python module called Scapy from the shell(Obviously this is a rooted app), but unfortunately its not possible. Atleast not with alot of work and when the App is finished i dont want my users to have to go through installing countless dependencies to get it working!
I've stumbled along a little unix program called Arp-Scan but i cant find a port for Android. I'm not sure how to port this to Android so i can execute it from a shell.
I have no experience with compiling and needless to say this is frustrating the hell out of me! . This one little stumbling block has been plaguing me for 2 weeks. The rest i will be able to do in pure Python, namely PortScanning and such.
The way the Android OS works is that an APK is unable to use raw sockets. But you are allowed to run a shell as root.
I have the option to use Nmap but if there was ever to be a paid version of my app i would have to buy a license and i simply cant afford it.
All i need is to execute a program from shell: like Arp-Scan to obtain an IP and MAC from the LAN.
Any help will be greatly appreciated.
Thanks in advance.
The installation instructions for the Linux-based are minimal, and give very little guidance on precisely what is required. There is no specification of which distros or versions it is supposed to be compatible with, but it definitely does not run on Ubuntu 14.04 (which is still current and supported until this time next year).
The application is clearly not statically linked, and running it on Ubuntu 14.04 fails to execute after failing to load libpng16.so.16, which was not introduced until much later in the Ubuntu release cycle.
Q1: Is the flash tool known to run on any particular release of Ubuntu?
Q2: Which distro and release was it developed on/released for originally?
Q3: Would it not make more sense for it to be statically linked (as Nokia did for the maemo-flasher which still works with the N900 'phone to this day, despite the end of official support about 7 years ago)?
Q4: Who do I need to take these other queries up with at Planet? There seems woefully little proper contact information.
cain.mosni said:
The installation instructions for the Linux-based are minimal, and give very little guidance on precisely what is required. There is no specification of which distros or versions it is supposed to be compatible with, but it definitely does not run on Ubuntu 14.04 (which is still current and supported until this time next year).
The application is clearly not statically linked, and running it on Ubuntu 14.04 fails to execute after failing to load libpng16.so.16, which was not introduced until much later in the Ubuntu release cycle.
Q1: Is the flash tool known to run on any particular release of Ubuntu?
Q2: Which distro and release was it developed on/released for originally?
Q3: Would it not make more sense for it to be statically linked (as Nokia did for the maemo-flasher which still works with the N900 'phone to this day, despite the end of official support about 7 years ago)?
Q4: Who do I need to take these other queries up with at Planet? There seems woefully little proper contact information.
Click to expand...
Click to collapse
Ubuntu 14.04 sounds unreasonably old to me to be complaining about this, but you make a fair point that the issue could be avoided altogether. I'm also used to rolling release and having the latest kernel on most devices, though. I still just have Android on my Gemini due to difficulties finding info and files on this whole process. I run GNU/Linux myself, so hopefully I'll manage to figure out the flasher without needing to borrow a Windows machine.
From what I've gathered, there's a public file for setting up Android/Debian dual-boot, but I don't see anything about having Debian as the only OS, and it seems files for builds of the other distros with support (Sailfish, Ubuntu, postmarketOS) are private. Support for them is lacking right now, but I still found it frustrating to think I had a lot of choices and then see that I was a bit misled. It'd be nice if I could find an IRC channel dedicated to the Gemini so I could discuss this with knowledgeable people in a more fast-paced manner.
soundtoxin said:
Ubuntu 14.04 sounds unreasonably old to me to be complaining about this, but you make a fair point that the issue could be avoided altogether.
Click to expand...
Click to collapse
The whole point about the Ubuntu LTS releases is that they ARE LTS (long-term support - stable but supported for up to 5 years), so it's perfectly reasonable to still be running it.
I've since tried on Ubuntu 16.04, and same problem.
I'm also used to rolling release and having the latest kernel on most devices, though. I still just have Android on my Gemini due to difficulties finding info and files on this whole process. I run GNU/Linux myself, so hopefully I'll manage to figure out the flasher without needing to borrow a Windows machine.
From what I've gathered, there's a public file for setting up Android/Debian dual-boot, but I don't see anything about having Debian as the only OS, and it seems files for builds of the other distros with support (Sailfish, Ubuntu, postmarketOS) are private. Support for them is lacking right now, but I still found it frustrating to think I had a lot of choices and then see that I was a bit misled.
Click to expand...
Click to collapse
That is irritating. As is the woeful lack of meaningful support.
Progress
Progressing...
Having cloned the Github source, it is now compiled and fully operational on both 16.04 LTS (xenial) and 14.04 LTS (trusty) .
git clone the source from Github - dguidipc/SP-Flash-Tool-src (board will not allow me, as a new user, to post the full link)
Install dependencies
qt4-dev-tools
libqtwebkit4
libqtwebkit-dev
alter the make configuration for the location of qmake
Code:
cd ${gitrepo}/SP-Flash-Tool-src/Build/
#backup the original build config just in case
f=build-linux.mk; cp -vp ${f} `date --reference=${f} "+${f}-%Y%m%d%H%M%S"`
In
Code:
build-linux.mk
change the path config for
Code:
qmake
to read:
Code:
QMAKE := /usr/bin/qmake
compile
Code:
cd ${gitrepo}/SP-Flash-Tool-src/
make
Binary will be in
Code:
../_Output
along with the object modules and a supporting shell script.
cain.mosni said:
Progressing...
[*]alter the make configuration for the location of qmake
Click to expand...
Click to collapse
No longer required. The linux I tweaked the linux build file to detect when it's on Ubuntu, and that tweak is now incorporated in the official source.
Dear XDA helpers,
I have done pretty comprehenisve searches for a day or so but I am having trouble. I have a Samsung S5 SM-G900F... I am trying to install lineage 18.1 using a MAC (OS 10.15.5 CATALINA) I can't find a version of heimdall suite that works on Catalina. Heimdall suite 1.4.0 doesn't install on Catalina. I got Heimdall-1.4.1-Unofficial-Signed to install but I can't find the front end and I can't find the installed app location on my hard disk. Also I downloaded the official lineage-18.1-20220828-recovery-klte.img but the image is not recognised and I can't open it on a Mac machine.
Basically I am having a cross patform nightmare, I can get some things installed on Catalina (such as Jodin3) but some of the necessary support files are not compatible with Mac Catalina (such as lineage-18.1-20220828-recovery-klte.img).
Am I wasting my time trying to do this on my mac? I would need a relatively straight forward process anyway because I am a noob, so these extra cross platform issues are not helping.
Is there a thread with instructions using Catalina? I haven't been able to find much useful in a day of wide ranging searching.
Thanks for your help
All the best Tim