Related
So i have been getting boot loops on every rom i've tried to flash from my sdcard in cwm. I tried using heimdall one-click on my mac but it keeps getting stuck at "claiming interface". I've already searched many threads but found nothing. Any help on how to fix this?
not to many people are giving up information on heimdall with a Mac. I know the web page talks about something called codeless kext but I don't have a Mac and have no idea what that is. my suggestion is to put Ubuntu on it.... jk but heimdall on Ubuntu is stupid easy, getting the video and wifi and cd-rom can be another story depending on your hardware. I think most Mac users are not to savvy or they'd just be running Linux I know osx is a great OS but it seems to lack users that like to tinker. well not totally true but with so few users the guys that really know Macs are hard to come by.
are you getting that message when you are installing one click to mac ?
Hello!
I had rooted my phone last week or so using the Motochopper script. I didn't (and don't) know much about rooting and I ended up accepting an OTA update a few days ago or so, losing my root. I ran Motochopper again, but I either get "Failure [Install_Failed_Already_Exists]" or just "Failure." I've tried uninstalling Superuser, but reinstalling it doesn't give me root back. I've tried to use this guide that the search linked me to:
http://forum.xda-developers.com/showthread.php?t=1985699
But it requires doing a fastboot. I've installed this program:
http://forum.xda-developers.com/showthread.php?t=2317790
And it seems to work, but I get nothing when I run "fastboot devices" while my phone is connected. I don't know how to boot my phone into fastboot mode - holding the volume down button while booting just puts me into Safe Mode, and not even a Google search seems to reveal how to do one for my phone.
Is there any way I can ever get root access back? Is a factory reset my only option? I apologize if this post/topic is incorrectly done, but I've tried searching high and low through the forums and even asked a question in the Newbie Q&A and have gotten nothing.
Bump. I guess my phone is pretty unpopular.
Bump again. Is there somewhere else where I could ask this question?
Anybody?
Well, whatever. I guess I'll do a factory reset then.
Upon looking it up, I see that doing a factory reset won't affect any issues with rooting because it won't mess with the system files. It seems I'll have to flash the original ROM, but I can't find how to do that for my phone.
Alright, got it. If anyone ever comes across this topic through a google search, follow the directions here:
http://www.lg-phones.org/how-to-flash-unbrick-lg-optimus-f6-back-to-stock.html
And then run Motochopper again after finishing the flash.
Thanks for all your help, guys!
O.M.G. Someone else has this phone! I tried to root for the first time, yesterday. No go. FN update. If I get the chance to try this, I'll be sure to post what happens. Thanks for making this thread.
itzTHATguy said:
O.M.G. Someone else has this phone! I tried to root for the first time, yesterday. No go. FN update. If I get the chance to try this, I'll be sure to post what happens. Thanks for making this thread.
Click to expand...
Click to collapse
Yeah, no problem. It seems that if you take the update, you can't root. You'll have to do the flashing thing I put in my last post and just consistently deny the new update. You can do stuff to make it not nag you to update, but the biggest thing is not to take it.
Remember to use Motochopper too.
About the F6 root:
Just now caught this thread.
I've had the F6 for about 2 weeks now. Just getting used to it.
Then the "i" updated came in OTA by itself (sort of)...the standard consumer methods of rooting the phone wouldn't work for me.
That's fine, too, because most of the standard methods use nefarious means of rooting the phone, and should probably be avoided anyway. Several (maybe not MotoChopper) are actually Chinese trojan-ware, which you really don't want.
Most use exploits to trick the phone, and it's ENTIRELY unnecessary.
Use saferoot. This script based routine requires ADB, and if you're in Windows THAT requires the USB drivers for the F6, but you'll want those drivers anyway. Google for downloading ADB by itself. I have ADB because I have the entire development system for Android (and in my case, I use Linux for that).
ADB, if you're not familiar, is the "Android Device Bridge" - software which allows developers to control the phone for development purposes. Using ADB, one can simply ask for root (well, it's more complicated, hence the scripts of saferoot) - but that's what it boils down to. It doesn't use security vulnerabilities to root the device - which LG and the service providers have recently closed anyway.
After the "i" update, saferoot provided a permanent (it seems, anyway) root access to my F6 in about 3 minutes.
The F6 is quite recent, and while it's considered a mid-level product, it's actually quite good. It's recent release date, however, is why you're not yet finding much popularity - it will take a while before sufficient F6's are sold to acquire a following. Give it a few months.
thank you! saferoot worked great! on Metopcs an hoping for a rom soon!
So I've come across a new problem.
I need to flash my phone because of a problem with the Google Play Store. I ran through the instructions on the site I posted - which worked before - but it then asked for the B2CApp to be updated, which I couldn't do through the program.
I then tried to follow the steps on http://forum.xda-developers.com/showthread.php?t=2085344, but when the phone update began, it hit an error:
20:15:21 : Model.dll load error. Please check model.dll was built Debug mode
20:15:21 : Model.dll must be build Release mode.
20:15:21 : Please check model.dll is correct.
20:15:21 : Model.dll Load ½ÇÆÐÇÏ¿´½À´Ï´Ù. Debug mode·Î ºôµåµÈ model.dllÀÏ ¼ö ÀÖÀ¸´Ï È®ÀÎ ¹Ù¶ø´Ï´Ù.
20:15:21 : Model.dllÀº Release mode·Î ºôµå µÇ¾î¾ß ÇÕ´Ï´Ù.
20:15:21 : Æ÷ÇÔ µÈ DLLÀÌ Model.dllÀÌ ¸Â´ÂÁö DLL ¸íÀ» È®ÀÎÇϼ¼¿ä.
20:15:21 : Page_Error ºÎºÐÀÔ´Ï´Ù
20:15:31 : =======Cancel button click : m_nStep(6)
I have absolutely no idea what the matter is, as I've been able to flash this phone repeatedly before. There's also sharing violations with pictures in C:\ProgramData\LGMOBILEAX\images during the process, but I'm so frustrated with this that I don't want to replicate it now. I can provide the information as necessary.
F6 does not support Fastboot
Time will tell if this phone will ever have an unlocked bootloader. In what little free time I've had to experiment with my Linux box, I've come to the conclusion that the F6 isn't capable of utilizing Fastboot.
There is a TON of information out there, but I will try to educate myself on using ADB/SDK tools to try and find a solution. The downside is the demands on my time can be formidable, so it'll be slow-going (and I'm not a fast reader). Hopefully the XDA community will come through for all of us so we can move forward (Many Thanks in advance for the superior intelligence of all the Devs here !).
For what it's worth, the F6 is a very nice phone in my opinion. Coming from a now 2-year old Samsung Admire, I find the available 1.2GB quite sufficient! The Admire had only 137MB! I also don't live on my phone, and don't need that many apps.
I decided to root my Galaxy S8,and im pretty uneducated on how to do those sorts of things, but there is what looked to be an very easy tutorial (snapdragon).
while following those instructions, i missed the requirement of needing adb, and so odin(prince) failed. well, i disconnected my phone. took it out of download mode.
now its forever stuck in an infinite installing system update loop.
i checked for solutions online. go to commands, a factory reset. ect ect
except i get a:
#fail to open recovery_cause(missing file)
which leads me to believe i messed up my software, no biggie, i can just fix it though oden... right?
wrong. opening oden ive come to realize i can no longer get my phone into download mode, and neither does oden recognize my phone as a well... a phone.
so im at a loss of what exactly to do.
do i go through my provider, hoping they fix the issue?
do i wait for a solution here, one i might not have the skills to accomplish?
or do i pay out the pocket to get someone to fix this thing. i really dont know
OU812?? said:
I decided to root my Galaxy S8,and im pretty uneducated on how to.........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
OU812?? said:
I decided to root my Galaxy S8,and im pretty uneducated on how to do those sorts of things, but there is what looked to be an very easy tutorial (snapdragon).
while following those instructions, i missed the requirement of needing adb, and so odin(prince) failed. well, i disconnected my phone. took it out of download mode.
now its forever stuck in an infinite installing system update loop.
i checked for solutions online. go to commands, a factory reset. ect ect
except i get a:
#fail to open recovery_cause(missing file)
which leads me to believe i messed up my software, no biggie, i can just fix it though oden... right?
wrong. opening oden ive come to realize i can no longer get my phone into download mode, and neither does oden recognize my phone as a well... a phone.
so im at a loss of what exactly to do.
do i go through my provider, hoping they fix the issue?
do i wait for a solution here, one i might not have the skills to accomplish?
or do i pay out the pocket to get someone to fix this thing. i really dont know
Click to expand...
Click to collapse
Try to intsall smartThings on your pc or lap and then download drivers for your phone and it will autom.reopening to bootloader hope that will help i tried before
I've been getting help in the Newbie thread, but it's time I start a new topic, since it's getting harder and harder to find replies.
All I'm trying to do is upgrade an old LG from Android 5.0 to 6.0. That's it.
I've got the drivers installed. I've downloaded three different versions of Flash Tool. The only one I got to do anything was "Flash Tool 2014".
The first time I ran it (following the directions on the web page where I found it), I picked "CDMA", "DIAG", and "CSE Flash". I was able to pick "Other Country" and "English" and got the phone to start installing. However, it only got as far as 4% and gave me an error. Now, when I run it, I pick "Other Country" and can't even pick a language. They're all blank. If I continue, all the messages consist of Question Marks, however, it still gets as far as 4% before stopping.
The phone is bricked in Download Mode. I have tried two different USB cables, two different computers, one of which has Windows 7 & 8.1 installed. I've tried all different USB ports to make sure I'm on USB 2.0 and not 3.0. I've tried running in Administrator Mode.
I see many posts about the 4% Error. The solution involves downloading a "wx.dll" file and putting it in the C:\system32\LGMOBILEAX\PHONE folder, but that didn't work. I also so one that said when you get the error, take the battery out of the phone, unplug it, put it all back together, and then Continue. That didn't work either.
What else can I possibly do? Thanks.
Hey, I have been trying to find a rom for 6.0 and I can't find anything. The only way to get to 6.0 is through ota. If you have 5.0 then your lucky. Ota can only be used if you still have a sim card that's active in the phone. There isn't roms for stock android 6. I would try and help but I can't.
If anyone finds away to get stock 6.0 please let me know.
Talking about your issue of your phone being bricked, there is many unbrick methods. I personally used https://forum.xda-developers.com/t/...n-qualcomm-hs-usb-qdloader-9008-mode.2933853/ it helped and fixed my issue. I still had my device info wiped off my phone somehow but at least it works. Your at a issue with a flash tool, fresh reflash with that method I sent if you can use it and start over. I can guide you through it if needed.
You might be stuck at a stand still, tell me what your phone says in device manager. You probably flashed a bad firmware. In that case I used the method above.
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
micheal3chaife said:
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
I'm a part-time Linux user also but I can't say that I've ever had luck with using Heimdall to flash Samsung devices. Many people have used it and had success but for me it has always been a pain getting the right "extra" packages installed and configured correctly for Heimdall to function correctly, it involves more than just installing and running Heimdall.
In my experience, Odin on a Windows PC is hands down the best way to go for flashing Samsung Devices.
Also, when you say they all fail in the end, what do you mean? Are they not working at all or are you able to begin the flash but it fails before it finishes the flash?
Droidriven said:
I'm a part-time Linux user also but I can't say that I've ever had luck with using Heimdall to flash Samsung devices. Many people have used it and had success but for me it has always been a pain getting the right "extra" packages installed and configured correctly for Heimdall to function correctly, it involves more than just installing and running Heimdall.
In my experience, Odin on a Windows PC is hands down the best way to go for flashing Samsung Devices.
Also, when you say they all fail in the end, what do you mean? Are they not working at all or are you able to begin the flash but it fails before it finishes the flash?
Click to expand...
Click to collapse
Hi, thanks for the sympathetic response (read: 'shouder to cry on').
"Break" in the sense that eventually, each of the programs I have tried - Heimdall, JOdin3, and Odin - have shown errors that, so far, have proven fatal:
*Heimdall requires 'Heimdall Packages' that seem to exist nowhere
*Odin fails to communicate with the phone
*JOdin3 returns a 'corrupted file' message when one directs it to the firmware to upload and flash. This issue has been reported to the maintainer's github as of 12 days ago, meaning it is a very recent issue.
The Heimdall issue *may* have a workaround - one can try, as per the maintainer's instructions on his github, feeding the component files one by one to the main process. I will try that.
A further possibility lies in the fact that previously, I had not enabled 'USB debugging' on the phone itself, which may or may not help with the interface.
There is also ADB, which I took a cursory look at last night. ADB appears to be able to work to move packets between a computer and a phone.
There is the option, on Samsung phones, to 'Appy update from SD card', which is what I propose to try now.
Latly, there is the option of installing an entirey different OS on the phone, and to hell with Android (?).
I will keep all you folks who are now rooted to the edge of your seats updated as things move along.
micheal3chaife said:
Hi, thanks for the sympathetic response (read: 'shouder to cry on').
"Break" in the sense that eventually, each of the programs I have tried - Heimdall, JOdin3, and Odin - have shown errors that, so far, have proven fatal:
*Heimdall requires 'Heimdall Packages' that seem to exist nowhere
*Odin fails to communicate with the phone
*JOdin3 returns a 'corrupted file' message when one directs it to the firmware to upload and flash. This issue has been reported to the maintainer's github as of 12 days ago, meaning it is a very recent issue.
The Heimdall issue *may* have a workaround - one can try, as per the maintainer's instructions on his github, feeding the component files one by one to the main process. I will try that.
A further possibility lies in the fact that previously, I had not enabled 'USB debugging' on the phone itself, which may or may not help with the interface.
There is also ADB, which I took a cursory look at last night. ADB appears to be able to work to move packets between a computer and a phone.
There is the option, on Samsung phones, to 'Appy update from SD card', which is what I propose to try now.
Latly, there is the option of installing an entirey different OS on the phone, and to hell with Android (?).
I will keep all you folks who are now rooted to the edge of your seats updated as things move along.
Click to expand...
Click to collapse
USB debugging makes a difference. Have you tried using older or different versions of Heimdall?
Are you running a VM to run windows and windows programs on linux or are you using wine to run windows programs? Wine doesn't work well enough to make it a viable option to run Odin.
I really suggest you bite the bullet and use a Windows system to use Odin. As long as you haven't corrupted any of the partitions on the device, flashing via Odin on a Windows PC will be effortless, a few clicks and a few minutes, done and done.
I think it could be dependent on the quality of the packages built by the packagers for your distro as to whether 'heimdall' works for you. I recently flashed LineageOS (2 days ago) on my old Galaxy Note 10.1 (2014) tablet using heimdall. I posted about it here: https://forum.xda-developers.com/f/galaxy-note-10-1-2014-edition-q-a-help-troubl.2502/
Note that hardware aspects such as a quality USB cable can at times be issues, and you may have better luck using a PC's USB-2 port instead of a USB-3 port.
In my case, for openSUSE LEAP-15.2 I successfully used heimdall-1.4.2
I also used android-tools-9.0.0 packaged for same openSUSE version, which provided 'adb' and 'fastboot'. While 'adb' worked for me, I could not not get 'fastboot' to detect my tablet when the tablet was in 'Odin' mode - and hence I could not flash with 'fastboot'. Fortunately heimdall did detect the Tablet when the Tablet was in 'odin' mode, and I was thus able to flash TWRP from 'heimdall'. I note specifying 'RECOVERY" in 'heimdall' did not work for me, but instead specifying the 'Entry' location for the flash (after checking the PIT) did work for me. Again, documented the details in that thread above.
In all cases on my GNU/Linux I used command line and not GUI front ends.
Goodl luck in your efforts.
Droidriven said:
USB debugging makes a difference. Have you tried using older or different versions of Heimdall?
Are you running a VM to run windows and windows programs on linux or are you using wine to run windows programs? Wine doesn't work well enough to make it a viable option to run Odin.
I really suggest you bite the bullet and use a Windows system to use Odin. As long as you haven't corrupted any of the partitions on the device, flashing via Odin on a Windows PC will be effortless, a few clicks and a few minutes, done and done.
Click to expand...
Click to collapse
I do not have ready access to a Windows machine, alas... Thanks for the other suggestions. Yes, I've been trying with wine, but with USB debugging disabled. My next attempt will probably be with Heimdall + USB debugging.
If I go the VM route, do you have a suggestion on how to set that up?
RE: Heimdall, I was under the impression that the most recent version (1.4.2, if I'm not mistaken) is best.
Again, thanks for the imput. Wish me ... maybe not luck, but continued systematic determination. And a little common sense.
You can run ADB wirelessly, means over Wi-Fi. So no Windows machine is required.
xXx yYy said:
You can run ADB wirelessly, means over Wi-Fi. So no Windows machine is required.
Click to expand...
Click to collapse
I"m not sure that helps them.
micheal3chaife said:
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
....
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
I hope you managed to finally succeed.
'Fresh' on the successful install of LineagOS-14.1 on my Samsung Galaxy-10.1 (2014) using adb and Heimdall on openSUSE-LEAP-15.2 (v.1.4.2 of heimdall) I then a couple of days ago proceeded to install LineageOS-14.1 on my wife's old Samsung Note-8 tablet.
As before, I pre-positioned the zip files for lineageOS and for GAPPS on her tablet, and then used heimdall to flash TWRP from my GNU/Linux PC.
it took me 3 attempts to flash TWRP, with the first failed attempted breaking the regular Android 4.1 boot to the Tablet, but fortunately it would still boot to the Tablet's recovery 'download' (flashboot) mode. The issue with the failures with me was a somewhat flaky USB cable. This is the best of about a dozen USB cables I own, and it works great for charging .... but for data transfer in a flash, my experience is the cable has to be very very VERY good. Note I was using a USB2 port.
Once TWRP was flashed, I tried to boot the Tablet to recovery mode, but the darn thing booted instead to the old Android 4.1. I was afraid that would wipe the TWRP, ... so I then with the Tablet still powered, ran 'adb' with appropriate recovery reboot options (from my GNU/Linux with Tablet connected), and the Tablet fortunately booted to TWRP (and it had not yet been wiped).
With TWRP running it was a simple matter to flash LineageOS and GAPPS. This time, BEFORE rebooting after the LineageOS/GAPPS flash, I was then careful to ensure TWRP re-flashed/installed, and it kept TWRP on the Samsung Galaxy Note-8. With my previous Samsung Galaxy Note-10.1 (2014) install I did not do that, and I had TWRP wiped after my reboot to LineageOS.
Again good luck in your efforts. I can say heimdall in GNU/Linux does work (together with adb).
micheal3chaife said:
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
Look here.