Related
Dear all,
I'm coming from Galaxy Nexus, got a great deal for an LG G2 D802 so here I am!
I've rooted a number of devices, so I know how it works in general. I'm running only linux or Mac, I can't access windows machine easily, and unfortunately I noticed already that LG tools (for downgrading to 4.2 for example) are mostly for windows.
I honestly dislike LG UI, it's a shame how kitkat have been distorted on this phone, I've forced myself to try the UI and have an honest judgment, and now that's it. I really dislike it... especially compared to plain AOSP. I would just save the knock knock feature.
In my experience I already bricked devices unfortunately, and I know how hard and scary can be revive them... if it's even possible in some case. In particular, I know for experience that messing the partition table is one of those things that can screw a device up for good.
So bottom line: my phone is coming with 4.4.2 pre-loaded out of the box, I want to get rid of it and jump to CM11, or at least have the possibility to install a custom ROM not running LG software.
Reading the LG G2 forum I've learned that the partition table is different from 4.2 to 4.4, and 4.4 partitions can't be used as-it-is if I want to run a custom ROM/recovery... is that true?
I already rooted my LG G2 with IOroot25 -that worked OK at least-, I've tried to install TWRP and I was facing to "change partition table".
I can't understand what is the status of the things, since there are post contradicting each other, and I don't want to touch the partition table unless it's super safe.
I might be spoiled by coming from a Nexus, but I found really confusing all this options just to root and be able to install custom roms.
I expect many of you to reply "can't you just read the forum!", but I did, and it was just really, as I mentioned, confusing!
If I would go to 4.2 stock, what I would lose/gain (remember I don't give a damn of LG software, I'm talking about radio, bootloader and so on.)
Why it's not possible to just unlock the bootloader and deal with it like any other device?
Thanks and be patient with an old man who does not understand!
Cheers
79bass said:
Dear all,
I'm coming from Galaxy Nexus, got a great deal for an LG G2 D802 so here I am!
I've rooted a number of devices, so I know how it works in general. I'm running only linux or Mac, I can't access windows machine easily, and unfortunately I noticed already that LG tools (for downgrading to 4.2 for example) are mostly for windows.
I honestly dislike LG UI, it's a shame how kitkat have been distorted on this phone, I've forced myself to try the UI and have an honest judgment, and now that's it. I really dislike it... especially compared to plain AOSP. I would just save the knock knock feature.
In my experience I already bricked devices unfortunately, and I know how hard and scary can be revive them... if it's even possible in some case. In particular, I know for experience that messing the partition table is one of those things that can screw a device up for good.
So bottom line: my phone is coming with 4.4.2 pre-loaded out of the box, I want to get rid of it and jump to CM11, or at least have the possibility to install a custom ROM not running LG software.
Reading the LG G2 forum I've learned that the partition table is different from 4.2 to 4.4, and 4.4 partitions can't be used as-it-is if I want to run a custom ROM/recovery... is that true?
I already rooted my LG G2 with IOroot25 -that worked OK at least-, I've tried to install TWRP and I was facing to "change partition table".
I can't understand what is the status of the things, since there are post contradicting each other, and I don't want to touch the partition table unless it's super safe.
I might be spoiled by coming from a Nexus, but I found really confusing all this options just to root and be able to install custom roms.
I expect many of you to reply "can't you just read the forum!", but I did, and it was just really, as I mentioned, confusing!
If I would go to 4.2 stock, what I would lose/gain (remember I don't give a damn of LG software, I'm talking about radio, bootloader and so on.)
Why it's not possible to just unlock the bootloader and deal with it like any other device?
Thanks and be patient with an old man who does not understand!
Cheers
Click to expand...
Click to collapse
well not all phones can just unlock bootloader (have you seen the galaxy s4 it has a locked bootloader) the reason we need mixed partitions(only one partition need to be changed) on kk to have recovery is because we use loki to bypass the locked bootloader and flash custom roms/recoveries, sadly the exploit we were using to install loki was patched in kk and we aren't sure if there is some other vulnerability, so the awesome developers found a loophole which is we downgrade the bootloader to the jellybean bootloader(plus a modified kk kernel which allows kitkat to boot off of the jb bootloader) and now we have recovery, the best way to do this is to use an app called AutoRec and you want to flash cm then keep in mind the kk baseband doesn't play well with aosp so you will need a kk baseband for your specific g2 that has been modified for aosp or the jb baseband or things will be broken when you flash cm(touch, rotation, radio, etc)
hopefully my little rant explains things to some extent, if you have any other doubts than ask
Wow! That's was easy. I usually don't trust this kind of approach, I prefer to do all by adb on a terminal.
But I was feeling brave and luckily AutoRec didn't brick my device!
With cm11 is a whole new phone, now I'm really happy with it. Two tab on/off works out of the box, which was the only feature I wanted from lg stock.
Only thing: I've noticed that the sdcard size is not the much:
I have the 16Gb model. The storage size is ~10Gb... and the app are saved on it!?
That's mean that cm11 is installed on a non-writable /system partition of 5gb.. Mostly empty, and there is a real /data partition... Isn't this a waste? Am I missing something?
Sent from my LG-D802 using Tapatalk
79bass said:
Wow! That's was easy. I usually don't trust this kind of approach, I prefer to do all by adb on a terminal.
But I was feeling brave and luckily AutoRec didn't brick my device!
With cm11 is a whole new phone, now I'm really happy with it. Two tab on/off works out of the box, which was the only feature I wanted from lg stock.
Only thing: I've noticed that the sdcard size is not the much:
I have the 16Gb model. The storage size is ~10Gb... and the app are saved on it!?
That's mean that cm11 is installed on a non-writable /system partition of 5gb.. Mostly empty, and there is a real /data partition... Isn't this a waste? Am I missing something?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
well you have to remember that out of the 16gb about 14bg is usable on the phone and then there's the os/system partition which take about 2.5-4 gb also there is no /data partition on the phone(I should know I've extracted g2 kdz/tot files and know all the partitions on it)
*I flashed a CM12.1 nightly on top of one that was a couple days old, and the new one had all kinds of force closes. This was through CM's internal update function, which sets a recovery script and reboots into recovery to install it (which BTW failed).
So I went into TWRP and flashed the backup I made not a couple hours earlier. But now I have kind of a bootloop. Most of the time, the LG logo shows up, then it just reboots back into recovery. One time it got stuck on the logo, and I was able to see it with ADB but it told me init.sh was missing when I tried to adb shell into it.
I have three backups I tried restoring, which had /boot, /recovery, /system and /data, plus I wiped the Dalvik cache and /cache, but nothing I've tried will kick this thing loose. I've even tried formatting it back to EXT4 from F2FS, and erasing and recreating the partitions in fastboot. It seems like there's a flag somewhere telling it to reboot into recovery, but I can't find anything pertinent online. I'm really at a loss as to how to fix it, and out of ideas now.
Have you tried using the lg support tool to bring the phone back to stock?
audit13 said:
Have you tried using the lg support tool to bring the phone back to stock?
Click to expand...
Click to collapse
Yeah, I was going to edit the OP to say I've also now tried to flash back to stock, using the 20a KDZ and the LG Flash Tool 2014. When it gets to the point where it's actually about to flash, it says "USB is not connected". I have all the latest drivers, and have tried different cords, to no avail. It has been transferring files while connected in TWRP, so I'm not sure what that's about.
What about using the lg support tool to flash stock?
LG Mobile Support Tool is what LG Flash Tool calls to actually flash the ROM (otherwise you have to depend on what LGMST decides to download). It saw the phone the last time I used it, but wouldn't show LP 5.0.2 as being an available update, even though it had been released.
This thread has the instructions I've been working off of, which was posted around the time the ROM was released. It "should" work, it just doesn't. If I'm not mistaken, there may be another tool you can use, but I haven't been able to find it.
There's one other way I suppose I could go about this, but it would be delicate. I could push all the individual IMG files from a ZIP archive I have of the KDZ, but I don't know what all the partition names are, and there are like 10 of them, including laf, aboot, etc. For example, the /data partition is actually named "userdata" when you use fastboot flash.
I didn't know about the difference between the LGMST and Flash Tool.
All I know is that the LGMST was able to download the correct LP ROM for my phone, install it, and get me back to stock after I screwed things up when trying to get root.
i have same problems , here is my solutions
- use SKR tool -> 4 .fix utility -> 5.unbrick ,
if u want go back to stock, try use TOT file to go back JB
cant use kdz way
Dễ.Thương said:
i have same problems , here is my solutions
- use SKR tool -> 4 .fix utility -> 5.unbrick ,
if u want go back to stock, try use TOT file to go back JB
cant use kdz way
Click to expand...
Click to collapse
+Thanks, I have never even heard of that. But I'll give it a try. By any chance were you using F2FS?
Though I am not sure, but I'm leaning towards some kind of hardware failure -- this is a refurbished phone, so there's no telling what it's been through inside. T-Mobile sent another one overnight, which I should have in a few hours, but I still need to clean up this one if it has to go back.
audit13 said:
I didn't know about the difference between the LGMST and Flash Tool.
All I know is that the LGMST was able to download the correct LP ROM for my phone, install it, and get me back to stock after I screwed things up when trying to get root.
Click to expand...
Click to collapse
Mine told me I had the latest version, which is peculiar. Was your phone rooted at the time? Because I could understand it refusing in that case: I ran into a soft-brick on a D800 because of an OTA once. Otherwise, I'm not sure why one would work, and the other wouldn't.
voxluna said:
+Thanks, I have never even heard of that. But I'll give it a try. By any chance were you using F2FS?
Though I am not sure, but I'm leaning towards some kind of hardware failure -- this is a refurbished phone, so there's no telling what it's been through inside. T-Mobile sent another one overnight, which I should have in a few hours, but I still need to clean up this one if it has to go back.
Click to expand...
Click to collapse
i dont use f2fs , just use SKR tool with luck but i think u need flash a stock rom first
Dễ.Thương said:
i dont use f2fs , just use SKR tool with luck but i think u need flash a stock rom first
Click to expand...
Click to collapse
The reason I ask is that I had a debate in another thread about using F2FS instead of EXT4 for the filesystem. Most people suggested it's buggy and causes problems, so I wondered if that's what happened here.
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
audit13 said:
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
Click to expand...
Click to collapse
If u can boot your phone ,try to use Tot file , lg flash tool doesnt work anymore
LGMST fixed my 802 so there was no need for a tot file.
audit13 said:
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
Click to expand...
Click to collapse
I wish I had a D802 -- it's ubiquitous, and thus has more support on XDA, I think. I'm not sure why T-Mobile chose to have a customized model. Same goes for AT&T, since they both use the same frequencies... and I don't know what the hell Verizon was thinking with those hideous buttons. The only differences I see between most of them is the SAR.
I am not sure that all g2 phones support the same frequencies. My 802 will not connect to LTE in Canada.
audit13 said:
I am not sure that all g2 phones support the same frequencies. My 802 will not connect to LTE in Canada.
Click to expand...
Click to collapse
Well, they don't, especially Verizon and Sprint being entirely incompatible because of CDMA. I looked it up just now, and while there are several variations of your phone, it actually looks like it has a lot less frequencies than the T-Mobile device. I was under the impression it was the other way around, but I dunno exactly -- yours is supposed to be a D803 up there. It depends on the carrier/region, and which LTE bands they're using. It may be that you get LTE somewhere else eventually.
I don't know why the hell they don't just make the phone with all the bands you expect to encounter on a continent, but I'm sure it has to do with lock-in. Because the SoC should already have that stuff baked in.
I actually have an 802 (International version, unlocked) that I bought off a guy on Kijiji. It was an incredibly cheap price because it had some scratches on the screen which are not very noticeable. Once I applied a tempered glass screen protector, you could only see the scratches from an oblique angle. The guy even included an official LG flip case which wakes and sleeps the phone This phone even has a stock LP ROM.
I love the glass protectors! That gel adhesive just melts on the screen and leaves not a single bubble. And yeah, it gets into scratches and improves them, too. I'll never use film ones again. I've personally never broken a screen, but Gorilla Glass can be scratched under the right conditions. Hey, as long as it's working for you, cheap is always good. HSPA+ isn't anything to sneeze about either -- I've had some amazing speeds on T-Mobile with it, for years now. It's a great fallback for LTE.
Okay, I managed to recover the original phone!
Something in my previous build was triggering the boot loop into recovery. This happened when the CyanogenMod updater tried to flash a new nightly, so there's a possibility it set a flag that kept it looping. But it's also possible Xposed went haywire somehow, and/or a module did. I'm not really sure why it decided to fail like this, when I had been using it without issue.
All my backups did the same thing, yet those builds ran okay when I backed them up. And I don't know why I could see the COM41 port, but not use it -- the drivers were perfect, I went to a lot of trouble to uninstall and replace them. That meant no LGFlashTool, and manual restoration (ye olde commande line).
So, what I did was use fastboot to flash every partition I could get my hands on, not just the ones you can format in TWRP. I used the 20c files from here. You basically do:
fastboot erase aboot
fastboot flash aboot.img
fastboot erase laf
fastboot flash laf.img...etc. Then you format the /system partition, and flash a Cyanogenmod nightly into there. I also flashed the /data partition, but left /data/media alone, which saves the internal storage. Then I erased and flashed /recovery just for good measure.
This is a somewhat specific fix, but maybe if someone else comes across it, it can help.
Hey guys I just want to let you all know that after installing 1 new Rom (upgraded from MM to stock Nougat that worked great) and then messing it up (build.prop) and restoring my phone to backups in TWRP caused my phone to fail with black screen of death.
This is a direct result of restoring back and forth from MM and Nougat FULL TWRP backups. I think I restored backups about 4 times and the last time (5) it restored fine then went to reboot and then the phone was totally unresponsive. No fastboot, download mode, TWRP or IMEI screen, nothing whatsoever works. The only thing that does work on the screen is the battery ? when no battery inserted on USB.
I just want to put this out there so that people realize that they should be careful and not flash and restore and whatever else many times without possible consequences of damaging their LG G4 permanently.
Everything was working great when I first unlocked and flashed a upgrade to Nougat and I just had to mess with things and screwed it up. I figured from using Moto phones in the past that you could flash multiple different roms and restore as you please without any issues but not the LG G4...
Every thread about all the roms and kernels all say that you can damage your phone and it will break etc so this is not saying that I wasn't warned over and over before following different guides or procedures.
Thanks for all the fun and now the phone is off to LG warranty and fingers crossed and I will see what they say and post updates here.
Correlation does not equal causation. You may well have encountered ILAPO
As you, I tried a Nougat rom but I restored my phone to stock because I didn't have LTE. Sometimes, I had to restore more than once to get it back to stock (MM).
My LG G4 is the only cellphone I got so many problems to restore. When I had my HTC Sensation, I restored it so many times I can't count and it never bricked!
The effect can happen when you
... flash/restore a stock aboot after UsU'd
... flash/restore the bootloader stack but not completely
... have not taken care of the ARB! Especially when flashing and testing several stock ROMs.
All 3 types can be recovered by my sdcard unbrick if you know your highest flashed ARB. But LG will repair it anyways.
Sent from my LG-H815 using XDA Labs
obvious said:
Correlation does not equal causation. You may well have encountered ILAPO
Click to expand...
Click to collapse
Exactly I just hope my post makes people a little more careful than I was.
Well for all the LGE bashing and disappointment, I have to give props to the warranty service of LGE!!! Sent from BC to ON on friday and had the phone back in my hand with mainboard replaced by wednesday! So that's 5 days including the the weekend!
So now I am back unlocked running Nougat stock rooted. The only hickup was the phone is no longer carrier unlocked and restoring the modemst's didn't work because of the new IMEI. The company I purchased from (Easycell in Vancouver) gave me a new code in a few hours!
Now I am being very conservative on doing TWRP cache and dalvic wipes, and so far I have just flashed to stock Nougat and done one TWRP backup. I think that should do it for a while!
Cheers!
HAHA damn I permanently SIM locked the phone by screwing the code up! Restored backup of MM and unlocked the network. So letting phone cool down and then re-flash Nougat. I first tried to restore the EFS but didn't work. Well fingers crossed I just want stock Nougat and be done (at least for a while LOL)!
The title of your thread implies that multiple TWRP restores have "caused" your brick. I for one, have done multiple TWRP restores on my UsU unlocked H812 with not even the slightest issue arising as a result. The title of your thread is totally misleading IMO and not warranted.
I believe your problem lies solely with going off script somewhere, i.e., more likely a result of operator error for one of the reasons steadfasterX suggests in his post # 4 above. As obvious correctly notes in post # 2 , Correlation does not equal causation ...
Your thread would be better titled: "Be careful with what you are flashing with TWRP as you may not be able to restore properly when you have royally screwed up by flashing what you did".
sdembiske said:
The title of your thread implies that multiple TWRP restores have "caused" your brick. I for one, have done multiple TWRP restores on my UsU unlocked H812 with not even the slightest issue arising as a result. The title of your thread is totally misleading IMO and not warranted...
Click to expand...
Click to collapse
Good point! I didn't even realize I left out flashing of ROM's and yes it sure isn't a TWRP problem. I didn't flash all kinds of ROM's all carelessly, just stock a few times with some restores of backups.
I just wanted to try and prevent people from possibly having the same issue (I have warranty others might not) as I did with my particular device.
Cheers!
grantdb said:
Good point! I didn't even realize I left out flashing of ROM's and yes it sure isn't a TWRP problem. I didn't flash all kinds of ROM's all carelessly, just stock a few times with some restores of backups.
I just wanted to try and prevent people from possibly having the same issue (I have warranty others might not) as I did with my particular device.
Cheers!
Click to expand...
Click to collapse
I note that you flashed the LuPuSv2.4 kernel (I presume for the H811) to do your stock restore on the H812. While it did work when I flashed the same kernel, I felt the restore ran with higher than normal temperatures - it is possible, with the higher temperatures, that you did overheat and trigger ILAPO with one too many restores but I still feel it is more likely you flashed a rom other than those posted in steadfasterX's OP in the bootloader unlock thread that led to your brick whether because of the arb version or bootloader stack in the rom.
sdembiske said:
... but I still feel it is more likely you flashed a rom other than those posted in steadfasterX's OP in the bootloader unlock thread that led to your brick whether because of the arb version or bootloader stack in the rom.
Click to expand...
Click to collapse
For ROM's I only flashed was the v29a listed in steadfasterx's thread (G4_ARB-any_v29a_FULL-STOCK-ROM_UsU.zip), thats it no others. I can say the arb was 0 when I unlocked the bootloader however I didn't check it again after that but that ROM is supposed to be for any arb.
Anyways I am happy to be back on stock 7.0!
Peace!
the G4 is a proven dog, prone to bootloops and intense heat, even while idle.
Mine has had 3 refurb roundtrips to LG Texas, 2 in the last month; with perhaps 10 roms tried.
Now that I have it back, other than TWRP, I have it pretty close to OEM (20x) with no custom, just some hidden and disabled apps via Apex.
When I bought these phones they were pretty fresh to the market yet were half off. I think LG knew they had a dog and did their best to dump it and the V20 after.
My HTC Sensation had no such issues and my 5yo HTC M7 is still my back-up working admirably while the G4 was at refurb.
While I'm glad LG "refurbed" my phone I am very disappointed with LG. Prior to smart phones, the half dozen flips I bought were LG.
My wifes G4 was also refurbed, but because it got trashed. She paid for her refurb, which I suspect was a new phone.
It has never had any issues. My experience says that at least a couple of LG phones were released not ready for prime time.
I have a bricked LG G2 that is stuck in a boot loop.
I was running a custom rom and lent the phone to my ex-gf and she tried said yes to OTA update. Then instead of telling me she attempted the fix the phone herself and in doing so used TWRP to wipe backups/all data/everything.
I can get into TWRP. I can use adb sideload.
That is it. No recovery mode, No download mode.
Can't get device detected by qhsusb_bulk
I think I need to fix the stock firmware/image. LG flashtool doesn't work and I think that is because I cannot boot the phone into android and because I can't get into Download mode.
Here is a semi-revelant thread on XDA, I posted there but haven't had a lot of replies, I doubt many people check the G2 forums as its an old phone at this point, yet its still in perfect condition, has a 1080p screen and runs fast.
https://forum.xda-developers.com/showthread.php?t=2582142&page=375
Please please help. Ill paypal someone $75 if they can help me get it working.
Thanks
Which variant? D802? Which firmware were you using before, kitkat, lollipop, stock or custom ROM? PM me if you want, I have bricked and unbricked mine many times
bigfamine said:
I have a bricked LG G2 that is stuck in a boot loop.
I was running a custom rom and lent the phone to my ex-gf and she tried said yes to OTA update. Then instead of telling me she attempted the fix the phone herself and in doing so used TWRP to wipe backups/all data/everything.
I can get into TWRP. I can use adb sideload.
That is it. No recovery mode, No download mode.
I think I need to fix the stock firmware/image. LG flashtool doesn't work and I think that is because I cannot boot the phone into android and because I can't get into Download mode.
Here is a semi-revelant thread on XDA, I posted there but haven't had a lot of replies, I doubt many people check the G2 forums as its an old phone at this point, yet its still in perfect condition, has a 1080p screen and runs fast.
https://forum.xda-developers.com/showthread.php?t=2582142&page=375
Please please help. Ill paypal someone $75 if they can help me get it working.
Thanks
Click to expand...
Click to collapse
Yeah sure can help.had this problem before too
zizuka said:
Which variant? D802? Which firmware were you using before, kitkat, lollipop, stock or custom ROM? PM me if you want, I have bricked and unbricked mine many times
Click to expand...
Click to collapse
D803
I was running a custom rom. I *think* it was lollipop.
Basically the phone sat in my desk for two years without use as I had a work from home job and could get by with a free app on my iPad, I lent it to my ex and this happened a few days later
I now need a mobile phone for a new job I am starting and this phone is still beautiful I would really like to use this instead of dishing out multiple hundreds of dollars
Not a problem to help. I've bricked my old G2/my wife's G2 not less than 10 times, and all gonna Ok later. If you has TWRP saved backups - then I can help unbrick it even if it stuck on "LG" logo! Can PM me foor details
As long as EFS is not wiped or you have a backup you can just flash a new ROM with TWRP right? Or flash a backup?
As long as you can access TWRP you can also connect to USB in case you do not have any ROMS stored on the phone and transfer them that way.
Hi
When I wipe devik, data, cache and system partition using TWRP and reboot, the phone take forever to boot it stuck in LG logo. I don't understand why it stuck when I wipe those partitions. I've tried combination keys to boot in TWRP recovery but it doesn't work. Now I'm stuck. I don't know what to do. My phone is LG G3 (F460L) Android 4.4.2. Please see the photo.
EDIT: I didn't read the system partition thing before answering below... If I'm not completely wrong, your phone can't boot, because there is no system which could be loaded, so your phone is more or less empty, when you wiped the system partition. No more Android 4.4.2 :/ I don't know, why booting into TWRP doesn't work. Maybe you carefully could try to unbrick your phone and reinstall stock rom again.
Hej,
have you ever had booting problems with your phone? I'm in constant bootloop trouble with my D855. Some say it's a battery issue, which I can not confirm since I've tried 4 different ones (including 2 brand new ones). Some others say my mainboard has kind of an unrepairable defect. As I go with this possible explanation, I ordered a new used mainboard from China, hoping for it to arrive in Europe and not beeing fished by the authorities...
I can't say for sure what is the exact issue with my or your phone, the only thing I can tell is that there are tons of posts that can be found on the internet about the G3 having bootloop issues after a couple of years of normal usage. And for most users this came all of a sudden. Believe me, I've invested days of research, uncounted attempts of unbricking my phone (I thought I bricked it somehow, but it wasn't the case) and flashed stock rom and LOS as hard as I could. All ended up in my phone not running stable, crashing and then bootlooping. Sometimes (most of the times) if it's shut down and I want to turn it on, it gets stuck on the LG boot splash screen. It seems that somehow the energy management is not capable of running the phone stable under low voltage, since at least for me the probability of successfull boots slightly rises with a higher state of charge. But I can't take it for granted...
Good luck for you, I will keep reading this thread.
I wipe System Partition which contains Kitkat 4.4.2 but I already flash new ROM (CM13 Unofficial f460) after. There should be CM13 in system partition. I don't know why it can't boot. On the other hand, I can't find official firmware 4.4.2 for F460L (3hours search still no luck). I found only official firmware 6 Marshmallow which I'm afraid I won't be able to root forever if I flash it. I'm really appreciated if you can find one somewhere.
Rexkh said:
I wipe System Partition which contains Kitkat 4.4.2 but I already flash new ROM (CM13 Unofficial f460) after. There should be CM13 in system partition. I don't know why it can't boot. On the other hand, I can't find official firmware 4.4.2 for F460L (3hours search still no luck). I found only official firmware 6 Marshmallow which I'm afraid I won't be able to root forever if I flash it. I'm really appreciated if you can find one somewhere.
Click to expand...
Click to collapse
You could follow the link in this post which leads to a russian site. I saw a 4.4.2 version of Android in there. Good luck!
Thanks. I found official firmware lollipop and flash it. I've been searching for a way to root it but most of the method is for D855. Do you know if F460L Lollipop is rootable?
Rexkh said:
Thanks. I found official firmware lollipop and flash it. I've been searching for a way to root it but most of the method is for D855. Do you know if F460L Lollipop is rootable?
Click to expand...
Click to collapse
You can use the search function within the forums or search engines like startpage. I don't actually own a F460L and I'm not an expert either, so I don't know, how it works exactly. Punchin the keywords "F460L Lollipop root" into startpage.com brought me the following link as first result:
https://forum.xda-developers.com/lg-g3/general/guide-everything-lg-g3-cat-6-f460s-t3542542
Just follow the guide in OPs post
I already try LG One Click Root. It doesn't work. When it reach 45% (Looking for LG Serial Port), the phone restart (normal reboot) and it stay at 45% definitely. I manually reboot to Download Mode, still, 45%. Any suggestion?
Rexkh said:
I already try LG One Click Root. It doesn't work. When it reach 45% (Looking for LG Serial Port), the phone restart (normal reboot) and it stay at 45% definitely. I manually reboot to Download Mode, still, 45%. Any suggestion?
Click to expand...
Click to collapse
Sorry, as I'm on a D855, I don't really know. I rooted via King Root which only works with a specific Android version. I used this guide which helped me a lot: https://www.youtube.com/watch?v=8VOgM3jLas4
It's for the D855 but it could work with the F460 too. In the video description, there is a download link to the specific stock rom version for F400 models. The guide tells you where and what to download and how to install. You could try this and I'll keep reading Good Luck!