Related
Okay, so I'm coming from a Vibrant and trying to get Mobile AP going on a friend's Epic. Should be no problem, right?
First: His phone was completely 100% Stock (DI18)
Guess not. So I manually rooted using the following:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb push root.sh /data/local/root.sh
adb shell chmod 755 /data/local/root.sh
adb shell /data/local/root.sh
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
adb shell rm /system/etc/install-recovery.sh
adb push joeykrim-root.sh /system/bin/joeykrim-root.sh
adb push jk-su /system/bin/jk-su
adb push Superuser.apk /system/app/Superuser.apk
adb push playlogo-orig /system/bin/playlogo-orig
adb push playlogo /system/bin/playlogo
adb push busybox /system/bin/busybox
adb push resolv.conf /system/bin/resolv.conf
adb push remount /system/bin/remount
adb shell chmod 755 /system/bin/joeykrim-root.sh
adb shell chmod 755 /system/bin/playlogo
adb shell chmod 755 /system/bin/busybox
adb shell chmod 755 /system/bin/remount
adb shell chmod 755 /system/bin/playlogo-orig
adb shell /system/bin/busybox --install -s /system/xbin
adb reboot
Which is the same as the one click root except I killed the DI18 recovery.sh thing.
Now everything looks pretty good, but I didn't test root (guessing this is my big ****up) and so I went on to install ROM Manager and then flash ClockworkRecovery for the Epic from ROM Manager and it seems to succeed. Asks for Superuser, I hit okay when the Superuser box pops up, and yay, I'm in the home stretch, right?
NOPE.
So I reboot to recovery and it goes like it's loading Clockwork, but then it says that it failed signature check. Uh oh. Well, whatever, reboot and try again later. Or not - now it won't do anything except reboot into recovery and it says "manual mode" at the bottom. It lets me scroll up and down, but not select anything - yes, I tried every single button on the phone.
On to Odin, then! So I download the tar (DG27) and pit (512 first, then 513, later), but it hangs at param.lfs every time, and now it gives the good old phone--!--pc bit. Can get back to download though.
Suggestions, please, anyone?
dorsai3d said:
Okay, so I'm coming from a Vibrant and trying to get Mobile AP going on a friend's Epic. Should be no problem, right?
First: His phone was completely 100% Stock (DI18)
Guess not. So I manually rooted using the following:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb push root.sh /data/local/root.sh
adb shell chmod 755 /data/local/root.sh
adb shell /data/local/root.sh
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
adb shell rm /system/etc/install-recovery.sh
adb push joeykrim-root.sh /system/bin/joeykrim-root.sh
adb push jk-su /system/bin/jk-su
adb push Superuser.apk /system/app/Superuser.apk
adb push playlogo-orig /system/bin/playlogo-orig
adb push playlogo /system/bin/playlogo
adb push busybox /system/bin/busybox
adb push resolv.conf /system/bin/resolv.conf
adb push remount /system/bin/remount
adb shell chmod 755 /system/bin/joeykrim-root.sh
adb shell chmod 755 /system/bin/playlogo
adb shell chmod 755 /system/bin/busybox
adb shell chmod 755 /system/bin/remount
adb shell chmod 755 /system/bin/playlogo-orig
adb shell /system/bin/busybox --install -s /system/xbin
adb reboot
Which is the same as the one click root except I killed the DI18 recovery.sh thing.
Now everything looks pretty good, but I didn't test root (guessing this is my big ****up) and so I went on to install ROM Manager and then flash ClockworkRecovery for the Epic from ROM Manager and it seems to succeed. Asks for Superuser, I hit okay when the Superuser box pops up, and yay, I'm in the home stretch, right?
NOPE.
So I reboot to recovery and it goes like it's loading Clockwork, but then it says that it failed signature check. Uh oh. Well, whatever, reboot and try again later. Or not - now it won't do anything except reboot into recovery and it says "manual mode" at the bottom. It lets me scroll up and down, but not select anything - yes, I tried every single button on the phone.
On to Odin, then! So I download the tar (DG27) and pit (512 first, then 513, later), but it hangs at param.lfs every time, and now it gives the good old phone--!--pc bit. Can get back to download though.
Suggestions, please, anyone?
Click to expand...
Click to collapse
Did you try flashing the PIT by itself? If not, try it. Sometimes that will get you back up and running.
Also, the DI18 tar is available now.
http://rapidshare.com/files/423321746/SPH-D700-DI18-8Gb-REL.tar.md5
Yep, tried pit by itself, and I just downloaded DI18 .pit, still nothing. He gave up and is on his way to get a replacement.
But I saw (somewhere...so many threads in such a short time period....) that I think someone executed something to do with rageagainstthecage while doing the manual root - that wasn't in the one click root I downloaded from the sticky in the development section. Could that have anything to do with it? I wouldn't think so, but I'm really quite curious how this could fail so hardcore - this is the first andriod device I've not been able to recover from (modded to hell and back a G1, Magic, Droid, and a Vibrant...)
EDIT: wait, pit...no, didn't do the pit by itself - I'm a dumbass, I tried tar by itself. Guess that's what I get for being in a rush
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
infamousjax said:
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
Click to expand...
Click to collapse
The PIT file is nice to have around in case you bork your phone from a bad flash or if you're flashing a kernel or radio independently from a ROM. But if you're just flashing a stock system tar, then you are correct in saying it's not needed.
Hmm...I always opened Odin, had the phone in download, then plugged it in. It recognized it fine, and that's how I flashed my Vibrant. Oh well, that's not the real oddity here. I'm more concerned about why it was stuck in stock recovery mode and you couldn't select anything (but could scroll?!). Why would this happen, and why did clockwork recovery fail the signature check on first install? I still want to get this working, but I don't think he's going to put his (now functional replacement) up for tinkering after that scare, but I'll be getting one relatively shortly.
I got stuck in the same place - used the one-click root method and had Superuser and Titanium and Rom Manger said they had root. So I flashed the clockwork recovery mod and that seemed to work fine, but when I went to backup my current ROM, I got stuck exactly in the same place with the stock recovery "manual mode" where I could scroll but not select anything.
I did however run Odin and flashed it back and worked perfect the first time I tried, so not sure why it isn't working in your case.
Coming from the EVO I didn't know there was an issue but I read that you can't use Clockwork Mod on the stock kernel? I don't know but since this is my wife's phone and I've bricked it once I'll just play with my EVO for now
Okay, so it's reproducible. That's a start. I'm assuming you downloaded Clockworkmod through ROM Manager as well?
When you reflashed, what OS/bit operating system was it? I did it from Windows 7/64-bit. Wondering if maybe the drivers have something to do with it... (oh samsung, you write such awful software but your hardware is oh-so-tasty....)
yes - I downloaded clockwork mod from Rom Manager and it had a choice for the Epic so I thought all was good.
I usually use my Macbook Pro which works fine with my Evo but wouldn't work with the Epic when I rooted so I used my Windows 7/64 bit machine for both the root and then the Odin recovery. I installed the 64bit drivers found somewhere here initially so those are what were installed when I ran Odin. I did use the DI07 tar for some reason (it was this past weekend and I'm not sure DI18 was posted here yet or I just grabbed the wrong one), so maybe try that one if you haven't yet.
Okay, so long story short, don't use ROM Manager for the Epic. Should've done it manually like I usually do instead of taking the lazy way out. Oh well, live and learn, no permanent damage done and I hope this will prove helpful to others.
dorsai3d said:
Okay, so long story short, don't use ROM Manager for the Epic. Should've done it manually like I usually do instead of taking the lazy way out. Oh well, live and learn, no permanent damage done and I hope this will prove helpful to others.
Click to expand...
Click to collapse
ROM Manager works fine if you have a compatible kernel installed first. Most of the newer custom kernels have the compatibility built in.
Right, but the compatibility isn't there in the stock kernel, hence the issue. I don't remember if there's any kind of PSA about this in the dev/root/clockwork threads, perhaps there should be. If there is, forgive me, for it's late and my attention is divided...
irwinm said:
I got stuck in the same place - used the one-click root method and had Superuser and Titanium and Rom Manger said they had root. So I flashed the clockwork recovery mod and that seemed to work fine, but when I went to backup my current ROM, I got stuck exactly in the same place with the stock recovery "manual mode" where I could scroll but not select anything.
I did however run Odin and flashed it back and worked perfect the first time I tried, so not sure why it isn't working in your case.
Coming from the EVO I didn't know there was an issue but I read that you can't use Clockwork Mod on the stock kernel? I don't know but since this is my wife's phone and I've bricked it once I'll just play with my EVO for now
Click to expand...
Click to collapse
dorsai3d said:
Okay, so it's reproducible. That's a start. I'm assuming you downloaded Clockworkmod through ROM Manager as well?
When you reflashed, what OS/bit operating system was it? I did it from Windows 7/64-bit. Wondering if maybe the drivers have something to do with it... (oh samsung, you write such awful software but your hardware is oh-so-tasty....)
Click to expand...
Click to collapse
mattallica76 said:
The PIT file is nice to have around in case you bork your phone from a bad flash or if you're flashing a kernel or radio independently from a ROM. But if you're just flashing a stock system tar, then you are correct in saying it's not needed.
Click to expand...
Click to collapse
I went through the same thing. Stuck in Clockwork recovery. Here is the way I got out. First I flashed the mixup kernel from clockwork. Then I backed up my ROM. THEN I simply restored the ROM and presto...back in the OS. Once I had everything up and smooth THEN...I finally added the MobileAP update zip via the file fixed by Firon.
Not stuck at clockwork, though. Stuck in the stock recovery. Something it just seems you have to odin out of because you can't flash anything.
infamousjax said:
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
Click to expand...
Click to collapse
DuDe, what a save! The steps you described are what got me out of a hole I had been in since 2pm. I can't believe that's what fixed it. Thanks!
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!
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Trickee360 said:
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Click to expand...
Click to collapse
Can you get into bootloader with power+vol down?
boot into the bootloader, then via fastboot..
fastboot boot recovery recoveryname.img(press enter)
remember to put the recovery img file in the same folder that fastboot is located, on your computer.
bootloader's good to go and I'm in recovery but I need a way to get the rom on my tablet. Mounting sdcard doesn't appear to do anything while connected to my pc
EDIT: tried the CWM flash from sideload option and my command line says it "cannot read 'sideload'" do I need to start/restart the server another way? I feel like a total noob, lol
adb push rom.zip /sdcard/
Pirateghost said:
adb push rom.zip /sdcard/
Click to expand...
Click to collapse
started the daemon then got error: closed
Trickee360 said:
started the daemon then got error: closed
Click to expand...
Click to collapse
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Pirateghost said:
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
no Can I do that through the sdk manager or do I have to update the sdk itself?
sdk manager can handle it
Pirateghost said:
sdk manager can handle it
Click to expand...
Click to collapse
Ugh. SDK manager won't install anything. EIther it says whatever package I'm working on requires API17 (which I'm trying to get, lol) OR it just plain can't "find" the package because acces is denied? What am I doing wrong?
My OS is Linux Mint 17. I'm running 4.4.2 NAE and haven't found not one tutorial explaining how to Root, Flash Custom Recovery and ROMS with this particular software number. I installed Samsung drivers and installed with Wine but get and error when device connected sometimes:
"Unable to mount Samsung Android"
"Unable to open MTP device '[usb:001,008]'"
Even though I get the error message my device's files are accessible from my Linux based pc. Please tell me I can Root my device and how
My device specs are:
Phone: Samsung Galaxy S4 SPH-L720
Android version: 4.4.2
Software number: L720VPUFNAE
Kernel version: 3.4.0-481102
Baseband version: L720VPUFNAE
Build number: KOT49H.L720VPUFNAE
TowelRoot app with Sprint code " 1337 0 1 7380 4 0 " worked for me my first attempt at root. Thanks Mr. W0lf and anyone else involved. Video tutorial link below:
http://youtu.be/ZGwMs8JPBhE
I still would like to see tutorials on how to Root, Flash Recovery and Roms for Linux Mint users
Sent from my SPH-L720 using XDA Developers App
Josey Wales said:
My OS is Linux Mint 17. I'm running 4.4.2 NAE and haven't found not one tutorial explaining how to Root, Flash Custom Recovery and ROMS with this particular software number. I installed Samsung drivers and installed with Wine but get and error when device connected sometimes:
"Unable to mount Samsung Android"
"Unable to open MTP device '[usb:001,008]'"
Even though I get the error message my device's files are accessible from my Linux based pc. Please tell me I can Root my device and how
My device specs are:
Phone: Samsung Galaxy S4 SPH-L720
Android version: 4.4.2
Software number: L720VPUFNAE
Kernel version: 3.4.0-481102
Baseband version: L720VPUFNAE
Build number: KOT49H.L720VPUFNAE
Click to expand...
Click to collapse
You don't use wine or samsumg drivers when rooting from linux. Install heimdall and flash using the heimdall command line.
untar the odin package, then flash the extracted image files separately with heimdall
heimdall on linux is all I use for flashing odin packages. Note The partition names are case sensitive, and differ between phones, but this example is for gs4.
mv odinpack.tar.md5 odinpack.tar
tar -xvf odinpack.tar
extracting blah blah blah...
boot.img
recovery.img
system.img.ext4
...
eg. > heimdall flash --RECOVERY recovery.img --BOOT boot.img --SYSTEM system.img.ext4 ...etc.
here's the gs4 partition names and typical gs4 image file names for heimdall command reference:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --ABOOT aboot.mbn
heimdall flash --BOOT boot.img
heimdall flash --HIDDEN hidden.img.ext4
heimdall flash --MDM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --RPM rpm.mbn
heimdall flash --SBL2 sbl2.mbn
heimdall flash --SBL3 sbl3.mbn
heimdall flash --SYSTEM system.img.ext4
heimdall flash --TZ tz.mbn
heimdall flash --CACHE cache.img.ext4
I use fedora, which uses yum for installation:
> sudo yum install heimdall
I think mint uses synaptic, which I'm not familiar with, so you're on your own there. You could go crazy and use synaptic to install yum, then use the above yum command. Probably a bit much.
Thanks for your input. I read through the Hemidall topic posted here but I guess I didn't read enough. I'm kind of new to Linux, still learning my way around performing commands from terminal. I'll go ahead and uninstall Samsung drivers from my home pc when I get in later and give Hemidall a shot
Sent from my SPH-L720 using XDA Developers App
Yes it was a bit much lol I did however manage to install Heimdall using the tutorial from the Cyanogen wiki:
http://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall#Installing_prerequisites
Now where do I get the .tar files and a step-by-step install/flash recovery tutorial without getting the KNOX bootloader. My device has Root
Sorry but I'm just trying to be cautious and through
Josey Wales said:
Yes it was a bit much lol I did however manage to install Heimdall using the tutorial from the Cyanogen wiki:
http://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall#Installing_prerequisites
Now where do I get the .tar files and a step-by-step install/flash recovery tutorial without getting the KNOX bootloader. My device has Root
Sorry but I'm just trying to be cautious and through
Click to expand...
Click to collapse
You should find the tar files inside the odin rom zip files
If you're trying to be cautious, you might want to test out the heimdall functionality first by flashing say, just the cache only from one of the stock roms. If it fails halfway through, it's no biggie. Just clear cache until you get it working. Use the above flash command that contains the --CACHE partition as a reference. Just be careful not to flash boot.bin from NAE or you're done. The procedure is the same as using odin, except you unzip and untar the rom manually with linux, and flash the untar'd images with the heimdall command as above.
r0ckstar said:
You might want to test out the heimdall functionality first.
Click to expand...
Click to collapse
Only if I'm able to flash a Recovery. I tried flashing Philz Recovery and CWM but failed. I followed the CyanogenMod tutorial posted here:
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltespr#Installing_a_custom_recovery_on_Galaxy_S4_.28Sprint.29
several times but kept getting this error heimdall flash --recovery recovery.img --no-reboot
ERROR: Failed to open file "recovery.img"
after typing "heimdall flash --RECOVERY recovery.img --no-reboot" in terminal. I extracted both recovery folders to my Desktop even changing folder names from:
recovery to RECOVERY
philz_touch_6.15.4-jfltespr to PHILZ or philz
Heimdall is install and working correctly v1.4.1. Heimdall-frontend is installed as will. I don't need frontend to flash a Recovery. I don't know what else to do here
Josey Wales said:
Only if I'm able to flash a Recovery. I tried flashing Philz Recovery and CWM but failed. I followed the CyanogenMod tutorial posted here:
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltespr#Installing_a_custom_recovery_on_Galaxy_S4_.28Sprint.29
several times but kept getting this error heimdall flash --recovery recovery.img --no-reboot
ERROR: Failed to open file "recovery.img"
after typing "heimdall flash --RECOVERY recovery.img --no-reboot" in terminal. I extracted both recovery folders to my Desktop even changing folder names from:
recovery to RECOVERY
philz_touch_6.15.4-jfltespr to PHILZ or philz
Heimdall is install and working correctly v1.4.1. Heimdall-frontend is installed as will. I don't need frontend to flash a Recovery. I don't know what else to do here
Click to expand...
Click to collapse
You still have to go into the folders to access the files. you flash the files, not the folders. cd into the philz directory, look for the recovery.img or whatever name it is there, then from that directory: heimdall flash --RECOVERY <case sensitive name that's in there>, hopefully recovery.img as to be unambiguous. If you're flashing from the correct directory, you should see the file when you do ls -la command. Otherwise, you would have to add the path to the file name when flashing from a different location. You're almost there.
I tried flashing Philz Recovery in Heimdall a few times and got this error:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.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:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
I tried different USB cables and the one included with my device
Josey Wales said:
I tried flashing Philz Recovery in Heimdall a few times and got this error:
I tried different USB cables and the one included with my device
Click to expand...
Click to collapse
There may be some issue with your linux permissions. Try running the command as root, also the phone has to be in download mode when you run the command. And... make sure the usb port is at least a usb2.0, and not an external hub.
r0ckstar said:
There may be some issue with your linux permissions. Try running the command as root, also the phone has to be in download mode when you run the command. And... make sure the usb port is at least a usb2.0, and not an external hub.
Click to expand...
Click to collapse
Issue with permissions? I used "sudo" command, file path is a directory, all 6 onboard usb2.0 ports are functional. I don't know what else to do. I flash the latest CWM recovery using Flashify. . .
I really would like to get this sorted out as I want to get into flashing with Heimdall.
Sent from my SPH-L720 using XDA Developers App
Josey Wales said:
Issue with permissions? I used "sudo" command, file path is a directory, all 6 onboard usb2.0 ports are functional. I don't know what else to do. I flash the latest CWM recovery using Flashify. . .
I really would like to get this sorted out as I want to get into flashing with Heimdall.
Sent from my SPH-L720 using XDA Developers App
Click to expand...
Click to collapse
Usually, this type of error means that either something else in linux is already using the usb port, or there's a heimdall installation issue.
check permissions (755) on heimdall.kext if your version has it.
I don't know where mint puts it.
The simplest thing to do is try every port one by one, BUT restart the computer before each attempt. I've had to do this myself in the past. If that fails, try downgrading your heimdall installation to 1.4.0. I think that's the earliest version that still supports L720. Every flavor of linux is a bit different in this regard, and there's many variables involved here. These kinds of things are typical for linux users. It's not for everyone, only people with awesomeness. Remember, we're pioneers of sorts using heimdall/linux when everyone else is using windows. Failure is not an option (or at least the admission of failure is not an option)...
I would really appreciate some help on this one... I attempted to flash the updated Mahdi Rom (09/20 build) this morning. I'm using the latest Philz Recovery if that matters. I performed the normal wipe procedure and when I went to flash the rom it told me the file was invalid. I think I might have tried to use a zip that wasn't fully downloaded.
I didn't have any other recoveries on my phone (I know... not smart) so I need to figure out how to flash a new rom without using recovery. I'm not completely hopeless and I'm willing to do what it takes to get my phone back!
Any help would be great! Thanks.
Have you tried adb? Your phone will be called sideload when you command adb devices.
Sent from my LG-D800 using Tapatalk
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Rogueharvest said:
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Click to expand...
Click to collapse
You can load adb on Mac. I believe there's a zip somewhere on xda with only the three files need, or download the package from Android. Place it in whatever your username folder is too make life easier. Also add ./ (dot slash) before every command.
Here's the command order for my setup.
cd Android/platform-tools
./adb devices
./adb sideload **DRAG FILE INTO TERMINAL**
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Update: I think I figured it out. The command prompt needed to be reinitiated.
Thanks again for you help! Moments like that are always a little scary!
Rogueharvest said:
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Click to expand...
Click to collapse
Does it recognize sideload when you type ./adb devices? If not and you're in adb on Philz unplug/replug the charger.