can only get to download mode on my e980 but now i cant not flash back to stock - LG Optimus G Pro

ive tried the lg flash tool with both the files it worked before last time i got soft bricked well i flashed that stock kit kat for the f whatever series that is on the e980 dev it flashed a diff recovery on my phone now i cant get to revcovery and download mode fails after it not being a e890 device anymore sorry i have been up all night trying to fix this and now im completly stuck.download mode fails after it not being a e890 device anymore sorry i have been up all night trying to fix this and now im completly stuck. download failed 5 sec says the pid number imei number and then device model is different check phone or dll f0000002

What Rom did you install the stock 4.4 zdk or the sphinx 4.4 flashable Rom?
_________________
Beavers & Ducks!

i flashed the sphinx 4.4 flashable Rom idk why it installed a recovery with it couldnt see sd card then when tried flashing another e980 rom it wouldnt let me said i had the wrong device or something idk im pissed about to smash it
_________________
Beavers & Ducks![/QUOTE]

i was on a cwm before but it ended up flashing a new one and thats when i started having problems now no recovery stuck at lg logo and i know my battery is low

The first thing I would do is pull your battery, wait a few minutes, put the battery back in and connect the charging cable. It may not want to boot but it will charge the battery while the phone is off. Get your battery charged first, then worry about getting it up and running again.
Keep in mind I'm not picking at you or anyone. But why would someone choose to flash a Rom designed for one version to another version? I know our devs make tweaks to allow one to run on the other but it's a chance I wouldn't take. If you have the E980, stick to E980 Roms. It's risky enough flashing Roms as it is because no two devices are the same. You know what I mean? And don't smash you phone. There are many smart people here that can get you up and running again. Smash the phone and you will be upset with yourself later....trust me. I did it and I was pissed at myself later when I found out it was easy to fix....stay calm....lol

i know i knew i should not have idk ive been flashing zips for a very long time guess it happened to still get the best of me even though i read through the thread and i seen a couple e980 users saying it worked haha well not for me i just hope i can get her back up and going soft bricks are ok its when i cant fix this that makes me crazy. slammed around my dual monitors and almost went after my evga build which would not have been good. Man i can not thank u enough i even had to make another account my old one was lows10 and i guess it was inactive for to long but been here since 07 only place i trust to exploit my devices.

Well I'm not the smartest person here. I just got this phone about a month ago and I haven't even got flashing it back to stock down pat yet. It's a work in progress....lol. But just get your battery charged for now. Then you will most likely have to flash it back to stock. I don't know if you have done this process yet on that phone but if you have then you know basically what you need to do. Just don't go flashing any more Roms made for other versions of the g pro....lol

this will be my 3rd time flashing back to stock but with my phone not being read as a e980 i cant get back to stock.

Did you use the Lg Flash Tools method?

Yes lg flash tool has worked perfect until now after that ROM
Sent from my d2lte using xda app-developers app

Ok. Give this method a try....http://forum.xda-developers.com/showthread.php?t=2459825....I don't know if it will work for ya as it didn't work for me. But hey, you gotta try something and maybe you will get luck and it will work for you. Give it a go and see what happens.

Lol idk it thinks its a g2 then it FCS
Sent from my d2lte using xda app-developers app

Tricky bugger it's gonna be ah? Did you try running it in Administrator mode? Be sure to follow the steps exactly as he lays them out.

Well in the left it says lge988at maybe thats why it isnt working with the lg flash? Grrrr idk this sucks and it keeps stopping working and its not in english

It has to be on com 41. I have noticed the lg flash tools method can be hit and miss with allot of people. I finally got it down pat enough to get it to work every time. You could try doing it this way........http://forum.xda-developers.com/showthread.php?t=2432476........He gives a link to a newer lg flash tools. Maybe you will have better results.

damn it still closes with that its right after it gets done loading my phone i guess i cant flash a e988 stock and see if that works? thats what it reads it as right before it closes idk maybe its cause 8.1 but dont think so the app doesnt even open in english idk seems like everyone elses is.

Honestly I don't know why it isn't in English. It is for me but I'm on the stock E980 FW. All I can think is you, somehow, flashed the Korean version of the F240. Just as a precaution I keep a flashable stock 10k on my sd card just in case the need for it arises. But not being able to get into recovery isn't helping your cause here. Keep an eye on the battery as well. If it starts draining down too far just power it off and let it charge more so you don't get so involved with the phone you forget. The problem for me is I'm more of a hands-on person. it's harder for this type of person to walk someone through fixing a gadget.....lol.
An honestly man, I don't know how else to help you. Hopefully someone allot smarter than me is gonna come along any minute now that will know exactly how to fix this issue. All I can suggest now is to keep searching the forum for this type of problem and find a solution. Just don't lose your temper or give up. The solution is here somewhere. I'll search around too. See what I can dig up.

exactly what i thought man ahhh and idk why its not in english either i mean im on my pc there should be no reason for it not to work. Idk I appreciate all your help. havent been in trouble like this since back years and years ago on the old first gen g1 hahahah. and ya flashing the Korean version of the F240 is what i did i really hope there is a way to fix this i had a backup but external sd card quit working so tranfered it on the phone when it still worked flashed back seemed fine went to try flash the e980 baseband and still no good now im just stuck. tempted to try and see if the e988 will work since it wont flash the stock e980 sorry for keep on talking im just going crazy.

It's all good man. I understand your frustration. I have been doing this for a long time now as well. Most of my experience is with moto's and Samsungs. Now I'm learning all over again with another phone myself. But anywho, yeah, give that a try. Flash the e988 if you can. At least if it works you can get into your recovery and sd card to try and flash it back to stock from there and be back on the E980 fw. It's like going around your ass to get to your elbow but hey, if it works who cares right?.....lol. And if you get it working again I suggest putting a flashable stock zip on your sd card just in case. But as I said before, It doesn't help if you cant get into recovery. But when you can it can be a life saver.
I do remember reading there are permission issues if you're running windows 8 or 8.1 on that last method I linked you to. You may want to look into how to overcome that issue and try again. If you haven't already that is.

Hmm at least it says e980 now but can't get past this
Sent from my d2lte using xda app-developers app

Related

[Q] Soft Brick,TWRPvsClockwork-Avoiding same mistakes

Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?
Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.
I had a similar problem to yours last night to. Except I didn't really do anything to it. It was just sitting there charging and I took it off the charger and it was doing some kind of boot loop, But every so often it would just stop on a black screen. I lgnpst about six times back but after running root and freegee I would try to get into bootloader and it would do it again. Eventually I tried doing freegee with clockwork instead and it did it again, Than I forced the phone off and pluged it in to my computer to get ready to lgnpst again so I could at least use the phone. All of a sudden I look at the screen and there was a battery charging animation. And then unpluged it and for kicks turned it on and it booted up no problem. Then I tried booting into bootloader and all works now. It was really strange, I did put twrp back though. I like it better then clockwork. I think I sore you asking questions in irc while I was in there asking question to ha.
-Frank
MikeDroid said:
Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.
Click to expand...
Click to collapse
I had the same thing happen and couldn't figure it out so I took it back to sprint told them I did the update and it messed up so they gave me a new phone for 35 bucks and from now on im staying STOCK.........................
DId you try to lgnpst back yet? That may help you.
-Frank
Frank...yup that's how mine worked. Just not sure how to do this. I don't think my failed lgpnst attempts did anything, b/c mine took the update eventually. I'll keep trying. This phone is so temperamental. Does Shellnut have some input on this problem? I can't figure out why some phones take and others don't when doing the same thing.
Talk to Shelnut2 over pm or find him in irc. I just found out there is a special version of freegee that may fix the problem. I seem to have fixed mine but I sent him a pm asking some questions about the problem. I think you are going to need to lgnpst back. Then root and run the special version of freegee. You have to get it from him because it does some things different that may brick the phone permanently. Thats why you have to ask for it. From what I understand it fixes that kind of problem.
-Frank
I will. I'm going to see if this thing will self correct. Otherwise I will check with him on that. The LGPNST is something I'm not looking fwd to doing.
LGPNST is not detecting phone in dl mode but does detect when in recovery. This SUCKS. Frustrated and out of ideas.
When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank
frankt2012 said:
When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank
Click to expand...
Click to collapse
Not sure if I ran as administrator. Assumed that I did. As a casual hack, I'm in over my head.
Sent from my LG-LS970 using xda app-developers app
Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?
Bricked OG
MikeDroid said:
Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?
Click to expand...
Click to collapse
I've been working on mine for a day and a half. I can't figure out the thing with renaming the ".tot" file to ".bin" because I don't even see a .tot file. After I unzipped the big ZV7 there was only one file without an extension so I can't figure out if thats the one I'm supposed to rename. Can you point me in the right direction?:crying:
[ I figured it out, I had to go into Preferences on my file explorer and set it to show all file types...DUHHH ]
In Windows, go to control panel, file settings, show file extensions. Something like that.
Sent from my LG-LS970 using xda premium
Finally got bit working. No more issues. Non of this stuff is very intuitive when your in panic mode. All is good now though.
Sent from my LG-LS970 using xda app-developers app
Apps
MikeDroid said:
Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?
Click to expand...
Click to collapse
Always backup your phone before tinkering with system files, and experimenting with launchers, kernals etc.
Titanium backup in WORTH the investment to upgrade to PRO.
Rom manager is a good one to boot directly into recovery without fiddling in the fastboot menu. And for backing up settings and roms.
Always KNOW what your doing. lol. sometimes even the big guys forget this. RESEARCH!

[Q] I think my S4 got bricked

Hi all,
from a big smile to sad face... that is how it's been for the past 24 hours
I rooted the phone then went to back up the stock rom after that wiped data, cache, dalvik then went on trying to instal Omega 4.0 and suddenly i got this message my external sd is unreadable. rebooted the phone and noticed that it takes me directly to the downloader screen. i tried to fix the phone by bringing it back to it's stock condition but no luck. I used Odin and so far it's the only thing the phone responds to but no luck with fixing it... I am trying to download the official stock fw hint this link
http://forum.xda-developers.com/showthread.php?t=2267895
but it stops and never finishes the whole amount of data... this seems the only way for me revive my phone back to life!
any suggestions what should I do now? it stopped showing the downloader screen now since I flashed the kernel drive for the S4 through Odin and now shows the black screen with the "Samsung Galaxy S4" writing.
by the way it keeps telling me that my phone isn't rooted but I did root it! am using twrp recovery.
I just got the phone from t-mobile 2 days ago and am debating on returning the phone back to them as the phone is still bootable to the recovery and that might revoke my warranty "i guess?"
Is it possible just to walk in to t-mobile store and swap the phone with another one since it didn't pass the 2 weeks returning window? I also got the phone insurance for it.
Please help, I sure need my phone back in working condition...
Omega 4 is for the octa core so thats why your phone bricked. If you can grt into download mode odin the stock files. If you can get into recovery try flashing a rom made for the phone. Dont freak out just read read read and youll be fine.
cwalker0906 said:
Omega 4 is for the octa core so thats why your phone bricked. If you can grt into download mode odin the stock files. If you can get into recovery try flashing a rom made for the phone. Dont freak out just read read read and youll be fine.
Click to expand...
Click to collapse
ayeeee ppl trying to reach me over the phone and they can't because of this stupid brick! well stupid me because I didn't know that Omega is for Octa core phone version... Yeah I can get it to download mode and recovery mode but is it possible just flash the stock file from the recovery instead of odin? I am waiting for that stock fw download to finish hint it's on hotfile and going in turtle speed!
your bricked, im pretty sure flashing stock wont help you (hasnt from my past experience) but doesnt hurt to give it a try.
i dont think will just give you another one, even though its in the two week window, because its your fault and not the result of hardware failure. the age old "oh i updated and not it wont turn on" probably wont wort because there are little to none reports of that happening. plus (and this is me assuming, correct me if im wrong) but when in download mode it probably shows custom status, which auto voids any warranty. but once again, doesnt hurt to try.
Unfortunately, from my past experience, your SOL
If the phone turns on and has download and recovery you are not bricked....only soft brick and the odin file should work. Just be patient and wait for it to finish
TheAtheistOtaku said:
your bricked, im pretty sure flashing stock wont help you (hasnt from my past experience) but doesnt hurt to give it a try.
i dont think will just give you another one, even though its in the two week window, because its your fault and not the result of hardware failure. the age old "oh i updated and not it wont turn on" probably wont wort because there are little to none reports of that happening. plus (and this is me assuming, correct me if im wrong) but when in download mode it probably shows custom status, which auto voids any warranty. but once again, doesnt hurt to try.
Unfortunately, from my past experience, your SOL
Click to expand...
Click to collapse
yeah i have that feeling but again nothing hurts trying... i hope something will work out
thanks for the cheer up though :good: lol
You can get to download mode so don't worry a bit.just flash stock with odin(is odin available for s4?)
Sent from my LT30p using xda premium
cwalker0906 said:
If the phone turns on and has download and recovery you are not bricked....only soft brick and the odin file should work. Just be patient and wait for it to finish
Click to expand...
Click to collapse
fingers crossed!
josephnero said:
You can get to download mode so don't worry a bit.just flash stock with odin(is odin available for s4?)
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
I used odin for the flashing in the beginning i think i have odin v307
I am waiting right now for the download to finish, been waiting for the past 2 hours even though it's slow transfer but steady 250kbps, i failed doing that with the fast link and tried it over 15 times! no luck
theatheistotaku said:
your bricked, im pretty sure flashing stock wont help you (hasnt from my past experience) but doesnt hurt to give it a try.
I dont think will just give you another one, even though its in the two week window, because its your fault and not the result of hardware failure. The age old "oh i updated and not it wont turn on" probably wont wort because there are little to none reports of that happening. Plus (and this is me assuming, correct me if im wrong) but when in download mode it probably shows custom status, which auto voids any warranty. But once again, doesnt hurt to try.
Unfortunately, from my past experience, your sol
Click to expand...
Click to collapse
yes unbricked!!!
Should I proceed with the rooting again and recover the rom then instal CM rom?
Glad you got your phone back....knew you would like I said only a soft brick....if you do continue and please read always so you know what you are doing before you do it afterall these phones are expensive
redshark80 said:
Should I proceed with the rooting again and recover the rom then instal CM rom?
Click to expand...
Click to collapse
Yeah go ahead and root again just be careful with the rom you flash make sure its for m919. I stayed with stock because no rom has the options that came with the phone such as motions and gestures and the camera.
Sent from my SGH-M919 using xda premium
cwalker0906 said:
Glad you got your phone back....knew you would like I said only a soft brick....if you do continue and please read always so you know what you are doing before you do it afterall these phones are expensive
Click to expand...
Click to collapse
Thanks! indeed they are expensive
atlprettygirl2145 said:
Yeah go ahead and root again just be careful with the rom you flash make sure its for m919. I stayed with stock because no rom has the options that came with the phone such as motions and gestures and the camera.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I just did the motochopper method and as I am reading now about the possibility of loosing your root access by future OTAs so am planning to flash that file that keeps your root safe even from future updates "SetUID Restriction" I will prolly keep my basic rom and wait for something better in future.
Thanks
atlprettygirl2145 said:
Yeah go ahead and root again just be careful with the rom you flash make sure its for m919. I stayed with stock because no rom has the options that came with the phone such as motions and gestures and the camera.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Ummm all TW ROMS on the development forum have the exact same features that come with the phone except they're tweaked....
whytechapel_x said:
Ummm all TW ROMS on the development forum have the exact same features that come with the phone except they're tweaked....
Click to expand...
Click to collapse
would you suggest me instal the CM? I am debating over here and for sure I will make a good use with the space that can free if I do... hint I have a 64gb msd installed on the phone
the motochopper root didn't go through by the way so I used odin and patched twrp plus did the SetUID restriction thing.
thnx
redshark80 said:
would you suggest me instal the CM? I am debating over here and for sure I will make a good use with the space that can free if I do... hint I have a 64gb msd installed on the phone
the motochopper root didn't go through by the way so I used odin and patched twrp plus did the SetUID restriction thing.
thnx
Click to expand...
Click to collapse
Well if you want to flash CyanogenMod, make sure its for the m919. I'm kinda lost though, did you still want all the features that Touchwiz has like air gesture, motions etc? Or you don't care for those?
whytechapel_x said:
Well if you want to flash CyanogenMod, make sure its for the m919. I'm kinda lost though, did you still want all the features that Touchwiz has like air gesture, motions etc? Or you don't care for those?
Click to expand...
Click to collapse
am not really decided about that, does it really matter? all i care about is the blazing speed, low battery consumption and for sure the freedom of moving all the apps to the extSD ... I think all these new features are gimmick and it may take another generation for it to get the best of it. I picked S4 over the HTC one just because the 1080p feature and the funny thing is that I missed on there is no HDMI port on this phone! lol no biggie
tell me more about the touchwiz kernel, is it worth it? I don't see many CRs out there at the moment
redshark80 said:
am not really decided about that, does it really matter? all i care about is the blazing speed, low battery consumption and for sure the freedom of moving all the apps to the extSD ... I think all these new features are gimmick and it may take another generation for it to get the best of it. I picked S4 over the HTC one just because the 1080p feature and the funny thing is that I missed on there is no HDMI port on this phone! lol no biggie
tell me more about the touchwiz kernel, is it worth it? I don't see many CRs out there at the moment
Click to expand...
Click to collapse
Well right now I don't think CM is as stable compared to a TW ROM. FYI there are a lot or ROMS as of now. You have Wicked, Infamous, Darth Stalker, Deathstar. There is also faux and ktoonez kernal available for TW. As for the extsd, you will need to format the card to fat32 for the phone to read it properly.

How to flash d2spr Lollipop Roms on the d2lterefreshspr (SPH-L710T Tri-Band Model)

1st let me just say I'm not a developer at all just someone who enjoys custom roms as much as everyone else here! I'm not very good at explaining things so please try to bear with me and try to understand this the best you can! If any real developers read this please help us by adding support for our device and if any developers can explain this better please do so! For anyone with the d2lterefreshspr (SPH-L710T Tri-Band) wanting to flash almost any Lollipop Roms made for the d2spr you can flash them! You might 1st have to unzip the rom and go to the updater-script and delete the 1st part where it checks the recoveries build to see if your device is the d2spr or the d2lte and so on. Then repack the rom back into a zip file the flash it in recovery as you normally would. Then once the Rom boots you won't have a baseband or service or anything but I will tell you why and how to fix this. The d2spr's modem-image file are labeled different from our modem! At the bottom of this I will show you the list of each modems links so you can see which 1s are different and what you have to delete and resymlink to get the Rom to reconize your baseband and get your service working! But using a file manager with root access navigate to the files in "/system/etc/firmware/ " and delete the wrongly symlinked modem-images! Once you have done that navigate to "/firmware-mdm/images/" folder and start symlinking the correct files to "/system/etc/firmware/" folder. After this you might want to modify the buid.prop and change all parts that say d2spr to d2lterefreshspr but only if you want. Once you have done this reboot to recovery and flash the Lte apn fix zip then reboot. Now everything should work with service and everything! I have tried this on the latest SlimLP 5.1.1. Beta and A..I.C.P. Lollipop and a few other Lollipop Roms for the d2spr. If you would like to download some of the Roms I have modified the updater-scripts so they will flash on our device and the APN zip I flash with a flashable build.prop I have already modified just send me a message and I will send you a link to my drive account. I'm trying to create a zip we can flash in recovery that will delete the wrong symilinked files and symlink the correct files to help save us the trouble of this process and for people that don't know how to create a symlink file! But as I stated I'm not a developer so I might be able to but if any developers that could help us by creating 1 for us please please feel free to do so and let us know! But take a look at the 2 lists of symlinked files and delete the necessary files and create the new symlinks that our device needs! If the files show the correct symlinks on 1st boot but you still don't have service click on the symlinks and view its details and you will see it'ssymlinked to the wrong files. Just delete all symlinks and create the correct new 1s.
Example of the d2spr modem symlinked images are:
symlink("/firmware-mdm/image/dsps.b00", "/system/etc/firmware/dsps.b00");
symlink("/firmware-mdm/image/dsps.b01", "/system/etc/firmware/dsps.b01");
symlink("/firmware-mdm/image/dsps.b02", "/system/etc/firmware/dsps.b02");
symlink("/firmware-mdm/image/dsps.b03", "/system/etc/firmware/dsps.b03");
symlink("/firmware-mdm/image/dsps.b04", "/system/etc/firmware/dsps.b04");
symlink("/firmware-mdm/image/dsps.b05", "/system/etc/firmware/dsps.b05");
symlink("/firmware-mdm/image/dsps.mdt", "/system/etc/firmware/dsps.mdt");
symlink("/firmware-mdm/image/modem.b00", "/system/etc/firmware/modem.b00");
symlink("/firmware-mdm/image/modem.b01", "/system/etc/firmware/modem.b01");
symlink("/firmware-mdm/image/modem.b02", "/system/etc/firmware/modem.b02");
symlink("/firmware-mdm/image/modem.b03", "/system/etc/firmware/modem.b03");
symlink("/firmware-mdm/image/modem.b04", "/system/etc/firmware/modem.b04");
symlink("/firmware-mdm/image/modem.b05", "/system/etc/firmware/modem.b05");
symlink("/firmware-mdm/image/modem.b06", "/system/etc/firmware/modem.b06");
symlink("/firmware-mdm/image/modem.b07", "/system/etc/firmware/modem.b07");
symlink("/firmware-mdm/image/modem.mdt", "/system/etc/firmware/modem.mdt");
symlink("/firmware-mdm/image/modem_f2.b00", "/system/etc/firmware/modem_fw.b00");
symlink("/firmware-mdm/image/modem_f2.b01", "/system/etc/firmware/modem_fw.b01");
symlink("/firmware-mdm/image/modem_f2.b02", "/system/etc/firmware/modem_fw.b02");
symlink("/firmware-mdm/image/modem_f2.b03", "/system/etc/firmware/modem_fw.b03");
symlink("/firmware-mdm/image/modem_f2.b04", "/system/etc/firmware/modem_fw.b04");
symlink("/firmware-mdm/image/modem_f2.b05", "/system/etc/firmware/modem_fw.b05");
symlink("/firmware-mdm/image/modem_f2.b06", "/system/etc/firmware/modem_fw.b06");
symlink("/firmware-mdm/image/modem_f2.b07", "/system/etc/firmware/modem_fw.b07");
symlink("/firmware-mdm/image/modem_f2.b08", "/system/etc/firmware/modem_fw.b08");
symlink("/firmware-mdm/image/modem_f2.b09", "/system/etc/firmware/modem_fw.b09");
symlink("/firmware-mdm/image/modem_f2.b10", "/system/etc/firmware/modem_fw.b10");
symlink("/firmware-mdm/image/modem_f2.b13", "/system/etc/firmware/modem_fw.b13");
symlink("/firmware-mdm/image/modem_f2.b14", "/system/etc/firmware/modem_fw.b14");
symlink("/firmware-mdm/image/modem_f2.b21", "/system/etc/firmware/modem_fw.b21");
symlink("/firmware-mdm/image/modem_f2.b22", "/system/etc/firmware/modem_fw.b22");
symlink("/firmware-mdm/image/modem_f2.b23", "/system/etc/firmware/modem_fw.b23");
symlink("/firmware-mdm/image/modem_f2.b25", "/system/etc/firmware/modem_fw.b25");
symlink("/firmware-mdm/image/modem_f2.b26", "/system/etc/firmware/modem_fw.b26");
symlink("/firmware-mdm/image/modem_f2.b29", "/system/etc/firmware/modem_fw.b29");
symlink("/firmware-mdm/image/modem_f2.mdt", "/system/etc/firmware/modem_fw.mdt");
symlink("/firmware-mdm/image/q6.b00", "/system/etc/firmware/q6.b00");
symlink("/firmware-mdm/image/q6.b01", "/system/etc/firmware/q6.b01");
symlink("/firmware-mdm/image/q6.b03", "/system/etc/firmware/q6.b03");
symlink("/firmware-mdm/image/q6.b04", "/system/etc/firmware/q6.b04");
symlink("/firmware-mdm/image/q6.b05", "/system/etc/firmware/q6.b05");
symlink("/firmware-mdm/image/q6.b06", "/system/etc/firmware/q6.b06");
symlink("/firmware-mdm/image/q6.mdt", "/system/etc/firmware/q6.mdt");
symlink("/firmware-mdm/image/tzapps.b00", "/system/etc/firmware/tzapps.b00");
symlink("/firmware-mdm/image/tzapps.b01", "/system/etc/firmware/tzapps.b01");
symlink("/firmware-mdm/image/tzapps.b02", "/system/etc/firmware/tzapps.b02");
symlink("/firmware-mdm/image/tzapps.b03", "/system/etc/firmware/tzapps.b03");
symlink("/firmware-mdm/image/tzapps.mdt", "/system/etc/firmware/tzapps.mdt");
symlink("/firmware-mdm/image/vidc.b00", "/system/etc/firmware/vidc.b00");
symlink("/firmware-mdm/image/vidc.b01", "/system/etc/firmware/vidc.b01");
symlink("/firmware-mdm/image/vidc.b02", "/system/etc/firmware/vidc.b02");
symlink("/firmware-mdm/image/vidc.b03", "/system/etc/firmware/vidc.b03");
symlink("/firmware-mdm/image/vidc.mdt", "/system/etc/firmware/vidc.mdt");
The correct modem images you need to symlink for the d2lterefreshspr are:
symlink("/firmware-mdm/image/dsps.b00", "/system/etc/firmware/dsps.b00");
symlink("/firmware-mdm/image/dsps.b01", "/system/etc/firmware/dsps.b01");
symlink("/firmware-mdm/image/dsps.b02", "/system/etc/firmware/dsps.b02");
symlink("/firmware-mdm/image/dsps.b03", "/system/etc/firmware/dsps.b03");
symlink("/firmware-mdm/image/dsps.b04", "/system/etc/firmware/dsps.b04");
symlink("/firmware-mdm/image/dsps.b05", "/system/etc/firmware/dsps.b05");
symlink("/firmware-mdm/image/dsps.mdt", "/system/etc/firmware/dsps.mdt");
symlink("/firmware-mdm/image/modem.b00", "/system/etc/firmware/modem.b00");
symlink("/firmware-mdm/image/modem.b01", "/system/etc/firmware/modem.b01");
symlink("/firmware-mdm/image/modem.b02", "/system/etc/firmware/modem.b02");
symlink("/firmware-mdm/image/modem.b03", "/system/etc/firmware/modem.b03");
symlink("/firmware-mdm/image/modem.b04", "/system/etc/firmware/modem.b04");
symlink("/firmware-mdm/image/modem.b06", "/system/etc/firmware/modem.b06");
symlink("/firmware-mdm/image/modem.b07", "/system/etc/firmware/modem.b07");
symlink("/firmware-mdm/image/modem.b08", "/system/etc/firmware/modem.b08");
symlink("/firmware-mdm/image/modem.b09", "/system/etc/firmware/modem.b09");
symlink("/firmware-mdm/image/modem.b10", "/system/etc/firmware/modem.b10");
symlink("/firmware-mdm/image/modem.mdt", "/system/etc/firmware/modem.mdt");
symlink("/firmware-mdm/image/modem_fw.b00", "/system/etc/firmware/modem_fw.b00");
symlink("/firmware-mdm/image/modem_fw.b01", "/system/etc/firmware/modem_fw.b01");
symlink("/firmware-mdm/image/modem_fw.b02", "/system/etc/firmware/modem_fw.b02");
symlink("/firmware-mdm/image/modem_fw.b03", "/system/etc/firmware/modem_fw.b03");
symlink("/firmware-mdm/image/modem_fw.b04", "/system/etc/firmware/modem_fw.b04");
symlink("/firmware-mdm/image/modem_fw.b05", "/system/etc/firmware/modem_fw.b05");
symlink("/firmware-mdm/image/modem_fw.b09", "/system/etc/firmware/modem_fw.b09");
symlink("/firmware-mdm/image/modem_fw.b10", "/system/etc/firmware/modem_fw.b10");
symlink("/firmware-mdm/image/modem_fw.b11", "/system/etc/firmware/modem_fw.b11");
symlink("/firmware-mdm/image/modem_fw.b12", "/system/etc/firmware/modem_fw.b12");
symlink("/firmware-mdm/image/modem_fw.b13", "/system/etc/firmware/modem_fw.b13");
symlink("/firmware-mdm/image/modem_fw.b15", "/system/etc/firmware/modem_fw.b15");
symlink("/firmware-mdm/image/modem_fw.b16", "/system/etc/firmware/modem_fw.b16");
symlink("/firmware-mdm/image/modem_fw.b17", "/system/etc/firmware/modem_fw.b17");
symlink("/firmware-mdm/image/modem_fw.b18", "/system/etc/firmware/modem_fw.b18");
symlink("/firmware-mdm/image/modem_fw.b23", "/system/etc/firmware/modem_fw.b23");
symlink("/firmware-mdm/image/modem_fw.b24", "/system/etc/firmware/modem_fw.b24");
symlink("/firmware-mdm/image/modem_fw.b25", "/system/etc/firmware/modem_fw.b25");
symlink("/firmware-mdm/image/modem_fw.b27", "/system/etc/firmware/modem_fw.b27");
symlink("/firmware-mdm/image/modem_fw.b28", "/system/etc/firmware/modem_fw.b28");
symlink("/firmware-mdm/image/modem_fw.b31", "/system/etc/firmware/modem_fw.b31");
symlink("/firmware-mdm/image/modem_fw.fli", "/system/etc/firmware/modem_fw.fli");
symlink("/firmware-mdm/image/modem_fw.mdt", "/system/etc/firmware/modem_fw.mdt");
symlink("/firmware-mdm/image/q6.b00", "/system/etc/firmware/q6.b00");
symlink("/firmware-mdm/image/q6.b01", "/system/etc/firmware/q6.b01");
symlink("/firmware-mdm/image/q6.b03", "/system/etc/firmware/q6.b03");
symlink("/firmware-mdm/image/q6.b04", "/system/etc/firmware/q6.b04");
symlink("/firmware-mdm/image/q6.b05", "/system/etc/firmware/q6.b05");
symlink("/firmware-mdm/image/q6.b06", "/system/etc/firmware/q6.b06");
symlink("/firmware-mdm/image/q6.mdt", "/system/etc/firmware/q6.mdt");
symlink("/firmware-mdm/image/tima_key.b00", "/system/etc/firmware/tima_key.b00");
symlink("/firmware-mdm/image/tima_key.b01", "/system/etc/firmware/tima_key.b01");
symlink("/firmware-mdm/image/tima_key.b02", "/system/etc/firmware/tima_key.b02");
symlink("/firmware-mdm/image/tima_key.b03", "/system/etc/firmware/tima_key.b03");
symlink("/firmware-mdm/image/tima_key.mdt", "/system/etc/firmware/tima_key.mdt");
symlink("/firmware-mdm/image/tima_lkm.b00", "/system/etc/firmware/tima_lkm.b00");
symlink("/firmware-mdm/image/tima_lkm.b01", "/system/etc/firmware/tima_lkm.b01");
symlink("/firmware-mdm/image/tima_lkm.b02", "/system/etc/firmware/tima_lkm.b02");
symlink("/firmware-mdm/image/tima_lkm.b03", "/system/etc/firmware/tima_lkm.b03");
symlink("/firmware-mdm/image/tima_lkm.mdt", "/system/etc/firmware/tima_lkm.mdt");
symlink("/firmware-mdm/image/tima_pkm.b00", "/system/etc/firmware/tima_pkm.b00");
symlink("/firmware-mdm/image/tima_pkm.b01", "/system/etc/firmware/tima_pkm.b01");
symlink("/firmware-mdm/image/tima_pkm.b02", "/system/etc/firmware/tima_pkm.b02");
symlink("/firmware-mdm/image/tima_pkm.b03", "/system/etc/firmware/tima_pkm.b03");
symlink("/firmware-mdm/image/tima_pkm.mdt", "/system/etc/firmware/tima_pkm.mdt");
symlink("/firmware-mdm/image/tzapps.b00", "/system/etc/firmware/tzapps.b00");
symlink("/firmware-mdm/image/tzapps.b01", "/system/etc/firmware/tzapps.b01");
symlink("/firmware-mdm/image/tzapps.b02", "/system/etc/firmware/tzapps.b02");
symlink("/firmware-mdm/image/tzapps.b03", "/system/etc/firmware/tzapps.b03");
symlink("/firmware-mdm/image/tzapps.mdt", "/system/etc/firmware/tzapps.mdt");
symlink("/firmware-mdm/image/vidc.b00", "/system/etc/firmware/vidc.b00");
symlink("/firmware-mdm/image/vidc.b01", "/system/etc/firmware/vidc.b01");
symlink("/firmware-mdm/image/vidc.b02", "/system/etc/firmware/vidc.b02");
symlink("/firmware-mdm/image/vidc.b03", "/system/etc/firmware/vidc.b03");
symlink("/firmware-mdm/image/vidc.mdt", "/system/etc/firmware/vidc.mdt");
symlink("/firmware-mdm/image/wcnss.b00", "/system/etc/firmware/wcnss.b00");
symlink("/firmware-mdm/image/wcnss.b01", "/system/etc/firmware/wcnss.b01");
symlink("/firmware-mdm/image/wcnss.b02", "/system/etc/firmware/wcnss.b02");
symlink("/firmware-mdm/image/wcnss.b04", "/system/etc/firmware/wcnss.b04");
symlink("/firmware-mdm/image/wcnss.mdt", "/system/etc/firmware/wcnss.mdt");
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Hey man this is great! This opens up a whole new world of wonders for this device. You have any idea how I can fix having to manually select apn after each reboot?
triband
RootSuperSU said:
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Click to expand...
Click to collapse
now that i found it, are you going to be around for me to throw questions at. i know what to do but the problems ive had made me leery of flashing.
pgellen said:
now that i found it, are you going to be around for me to throw questions at. i know what to do but the problems ive had made me leery of flashing.
Click to expand...
Click to collapse
Yea man i work til 4-5pm but after that i can try to help ya! My S3 bricked on me and i dont have a 16gb sd to flash the unbrick image to but im always willing to try and help if i can
Sent from my LGLS885 using XDA Labs
rom flashing
RootSuperSU said:
Yea man i work til 4-5pm but after that i can try to help ya! My S3 bricked on me and i dont have a 16gb sd to flash the unbrick image to but im always willing to try and help if i can
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
well, come to find out flashing octos, made for triband,,,,who knew, not me until today, anyway, its very easy. haha probably easier than ANYTHING i've done up to this point. i dont remember how much i've told you but the triband that i was fighting with so much may have had a problem from the very beginning. getting into recovery continually got harder and harder until it just wouldn't go. i tried about 8 times and it completely died. i mean its dead.im sad for that. that drops me to one sph-l710 with a crumpled usb and so i have to charge it wirelessly which is cool but its fragile. so ive got another refurb triband which im about to flash. WHY? ill be damned if i know why. this phone is rooted and cleaned out and runs beautifully. but, i want more. i guess or im just stupid which by reading this i may be. ill let you know.
triband
pgellen said:
well, come to find out flashing octos, made for triband,,,,who knew, not me until today, anyway, its very easy. haha probably easier than ANYTHING i've done up to this point. i dont remember how much i've told you but the triband that i was fighting with so much may have had a problem from the very beginning. getting into recovery continually got harder and harder until it just wouldn't go. i tried about 8 times and it completely died. i mean its dead.im sad for that. that drops me to one sph-l710 with a crumpled usb and so i have to charge it wirelessly which is cool but its fragile. so ive got another refurb triband which im about to flash. WHY? ill be damned if i know why. this phone is rooted and cleaned out and runs beautifully. but, i want more. i guess or im just stupid which by reading this i may be. ill let you know.
Click to expand...
Click to collapse
tonight if your not busy with other people ill have some questions for you. im looking forward to it. i loaded the rom, gapps and now theupdate has been in a holding cycle for half an hour. it vibrates a little every so often. so i guess ill let it go. i want in so i can finish setting it up. ive got a lot of work to do. i know you must.
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
octos
yakob97 said:
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
Click to expand...
Click to collapse
hey, supersu, help me fix this s3 triband when you get home and you feel like it. i can wait if you need. don't you come from work? let me know however, the biggest problem im having is my bluetooth doesnt work for music. works for everything else,that's a strange one. i'll wait for a reply.
yakob97 said:
Will this zip work for KK roms too? Or is it only Lollipop? I'm willing to test it out but I just want to be sure that I won't brick my S3 since I can't afford a new phone right now.
Click to expand...
Click to collapse
Yes it should work and no flashing it wont brick ur device at all! Nothing is flashed or installed it only deletes the wrong symlinks and creates the correct ones!
Sent from my LGLS885 using XDA Labs
pgellen said:
hey, supersu, help me fix this s3 triband when you get home and you feel like it. i can wait if you need. don't you come from work? let me know however, the biggest problem im having is my bluetooth doesnt work for music. works for everything else,that's a strange one. i'll wait for a reply.
Click to expand...
Click to collapse
Idk how to fix the bluetooth problem! Im not a developer or programmer i just google search alot and read very thoroughly and spend alot of time using FX File Explorer to study my system files! But whats the problem ur having other then bluetooth
Sent from my LGLS885 using XDA Labs
octos
RootSuperSU said:
Idk how to fix the bluetooth problem! Im not a developer or programmer i just google search alot and read very thoroughly and spend alot of time using FX File Explorer to study my system files! But whats the problem ur having other then bluetooth
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
its about time you showed up again. i thought like these other senior members that once you dealt with the senior citizen with debatable alzheimer's you had fled the country also. hehe man i don't know. on my other triband i had no music at well, no sound at all, none. and i had no cell service. now everything works except the bluetooth on the music. as soon as i boot it up the music locks up. its weird. i was just prepping my phone to go back to stock. i think these tribands are better stock with the bloatware removed and not too much of that. ya, i spend alot of time with my file manager. have you tried total commander? its great. you get it from gizmos freeware. im just getting to know it but i have it on the computer and its pretty good.
pgellen said:
its about time you showed up again. i thought like these other senior members that once you dealt with the senior citizen with debatable alzheimer's you had fled the country also. hehe man i don't know. on my other triband i had no music at well, no sound at all, none. and i had no cell service. now everything works except the bluetooth on the music. as soon as i boot it up the music locks up. its weird. i was just prepping my phone to go back to stock. i think these tribands are better stock with the bloatware removed and not too much of that. ya, i spend alot of time with my file manager. have you tried total commander? its great. you get it from gizmos freeware. im just getting to know it but i have it on the computer and its pretty good.
Click to expand...
Click to collapse
Idk wat to say about that never had that problem! What room are u running? If oct os then ask them about it! I like the Slim Roms and S.O.K.P. the best but thats just me!
Sent from my LGLS885 using XDA Labs
I just flashed the final d2lte CM11 snapshot and your zip file, and it worked! After flashing everything the ROM runs super fast and runs wonderfully! So far as I can tell everything works perfectly. Camera, SMS and MMS, GPS, Mobile Data, and Screen Rotation all work perfectly. My steps for flashing were:
Modify Updater-scripts file to remove device checking
Wipe system, dalvik and cache, and data.
Flash CM11 snapshot
Boot to system
Reboot into recovery and flash Gapps and APN fix (I'm on virgin mobile)
yakob97 said:
I just flashed the final d2lte CM11 snapshot and your zip file, and it worked! After flashing everything the ROM runs super fast and runs wonderfully! So far as I can tell everything works perfectly. Camera, SMS and MMS, GPS, Mobile Data, and Screen Rotation all work perfectly. My steps for flashing were:
Modify Updater-scripts file to remove device checking
Wipe system, dalvik and cache, and data.
Flash CM11 snapshot
Boot to system
Reboot into recovery and flash Gapps and APN fix (I'm on virgin mobile)
Click to expand...
Click to collapse
I never liked CM myself! I prefer Slim or S.O.K.P. Roms more then any other! You can use alot of the non triband roms kernels and tweaks but just not the bootloaders or modems!
Sent from my LGLS885 using XDA Labs
octos
RootSuperSU said:
I never liked CM myself! I prefer Slim or S.O.K.P. Roms more then any other! You can use alot of the non triband roms kernels and tweaks but just not the bootloaders or modems!
Sent from my LGLS885 using XDA Labs
Click to expand...
Click to collapse
guess what? my second triband died last night. just running, fine. so, went to turn it on and it wouldn't come back on. is there any kind of a reset for the samsungs thAT I DONT KNOW ABOUT? the exact same thing happened with the other triband i had. so i take the phone back to the store and they give me another triband, they said. so i get it home and looked at it and immediately knew that it wasn't a triband. it was the original sph-l710 that i bought", to begin with. these guys dont know what they are selling. id like to complain but to who? this is truly a beautiful phone wit the brushed blue metal look and its one of the "grade A" refurbished phone so i guess maybe i have faith that this one will work.however im a little short on faith right now.
Wow! Good luck man. Honestly, if I had to choose I'd want the original one over the tri-band.
broken tribands
canodroid15 said:
Wow! Good luck man. Honestly, if I had to choose I'd want the original one over the tri-band.
Click to expand...
Click to collapse
ill tell you what, when it ran it ran very well. so what i want to know is tell me what you would do with this phone rom wise and maybe point me where to go get it. also i need all the stock files in case i have to flash this. this phone is very easy to fix. way easier than the triband but those had the same problem and i didn't know it until they up and died. so, if you have a minute. i've got all rooted. i've got selinux fixed and so, ....what is the latest liquid out there? by the way i watch the tide religiously. have for years. i also just noticed your logo. are you part of octos? ah, i think i saw your name. so i had octos on my triband when it died but i didnt have bluetooth on music. it worked on phone. tell me how to set up octos. man i liked it but i have to have that bluetooth music. how do i fix that?
rom flashing
RootSuperSU said:
For anyone unsure about creating the symlinks I have a very simple zip file to flash in recovery to delete the bad symlinks and make the right 1s! I have tested on SlimLP, A.I.C.P., Exodusand Pac-Man d2spr Roms. It will not mess up anything on your S3! It only does as stated. If you wanna check it its all in the script-updater. Just flash this after flashing a d2spr Lollipop rom and if you are also confused on modifying the script-updater for the rom so it will flash on the d2lterefreshspr then just flash the TWRP 2.8.7.0 recovery from TWRP's website and you wont have to worry about changing it!
Fixing Modem Symlinks For SPH-L710T.zip
https://drive.google.com/file/d/0B-Zg_yh4ytvLaS1xSzZ3bWhuTVk/view?usp=docslist_api
Click to expand...
Click to collapse
are you active this night? im about to flash octos. first, i want to ask a couple questions,,,first, what about xposed, is that runnable on a sph-l710? what about dirty? i know it wouldn't run on a triband but this 710? ok enough. how about googles N? is it.
pgellen said:
are you active this night? im about to flash octos. first, i want to ask a couple questions,,,first, what about xposed, is that runnable on a sph-l710? what about dirty? i know it wouldn't run on a triband but this 710? ok enough. how about googles N? is it.
Click to expand...
Click to collapse
Since you're not on a triband just flash the d2spr build, not the d2refresh build. You can run xposed on our ROM if you wish. We always recommend a clean flash, especially if coming from stock or any other ROM. Even if its Oct-L to Oct-M. ??

Canada LG G3 Wifi issues since 5.0.1 what do I do to fix this

I've found since the update my cell signal has dropped significantly, my wifi is dropping every 30 seconds or so and I'm getting frequent System UI crashes. I've done a wipe and reinstall but not much has changed. The System UI crashes are less but that's about it.
I was thinking of going back to KitKat as that seemed to work the best but there also looks to be some good roms out there like Carbon, CM12 or CM13 etc. I don't know much about this so would need some direction and advice concerning the best route to take.
I have rooted the phone so it has super user and TWRP installed as well. I've also downloaded a bunch of stuff like the LG flash tool, GAPPS (a couple different versions), and some roms (Euphoria 1.1 D852, CM13 Nightly D852, and Carbon 5.1.1 Unofficial D852) as they looked like they may be good options for me. Still haven't found a good KitKat option so if anyone could point me in a good direction there that would be great.
I've backed up my phone so I think I'm ready to go. Can I just use TWRP to install the roms or do I need to use the LG flash tool for anything?
Please help, I'd like to have a properly working phone again. Especially WiFi as I'm on vacation, hard to do much when it's dropping every 30 seconds or so.
Thanks for your time and help. I'm pretty much a newby so please take that into consideration. If it makes any difference I have the 16gb version that's unlocked. Currently with Fido though.
If I was you, I'd restore my phone with this: http://forum.xda-developers.com/showthread.php?t=2785089
And I'd give a try to this rom: http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
with this kernel: http://forum.xda-developers.com/lg-g3/development/kernel-xceed-t3222211
I'm running it on my device and I got no problem so far.
If you want to go back to kitkat, only use my first link!
Thanks for the links. I did download a .kdz file already. I had to enter my IMEI and then it supplied what I assume is the proper one for my phone. Although I can't remember now if that was Kitkat or something else haha. The link you sent me only had files linked to a carrier whereas mine is an unlocked phone that wasn't tied to anything. I don't know if that makes a big difference or not but I'd rather not use one from Rogers (as an example) if it's not necessary.
I appreciate the other links as well but I would have no clue how to use them, as I mentioned I'm a newbie so without direction I'd be lost. Plus being on vacation I'm hoping not to spend hours and hours researching this if I don't have to. Or at least more hours and hours than I've already spent.
Cheers and hopefully I can get some more opinions or recommendations.
Thanks
RapHaeL_4_4_4_ said:
If I was you, I'd restore my phone with this: http://forum.xda-developers.com/showthread.php?t=2785089
And I'd give a try to this rom: http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
with this kernel: http://forum.xda-developers.com/lg-g3/development/kernel-xceed-t3222211
I'm running it on my device and I got no problem so far.
If you want to go back to kitkat, only use my first link!
Click to expand...
Click to collapse

R.I.P. G3?

Hey guys,
got a big issue: My LG G3 D855 International Version is not working properly. I was using Fulmics Rom (6.5 I believe).
At some point phone just turned off. I was rebooting and then there were some weird noses from the speaker after rebooting into the system, like cracking.
This happened twice. Afterwards it did not boot at all (Not sure if it bootlooped or went just straight black).
I then went into TWRP recovery and wanted to wipe and flash Fulmics.
Everytime I want to do this i get through Aroma Installer and then at the Installation part at around 10% it goes black again.. (first time I was afraid I bricked it but it happens exactly like this all time)-
Same thing happens when I want to restore an old Backup file. It goes to around 200 MB and then dies.
Already changed the battery to a new one, so that's not the deal. I'm afraid this is an hardware issue? Hope you can help!
Edit: Reproducable when I'm doing tasks so that CPU heats up (as shown in TWRP).
Does the phone work properly on stock? If it does not, it sounds like a hardware problem.
Well, problem is I can't flash anything so impossible to tell. As I said, everytime I do something more that just moving through TWRP phone dies..
theFUNKY**** said:
Well, problem is I can't flash anything so impossible to tell. As I said, everytime I do something more that just moving through TWRP phone dies..
Click to expand...
Click to collapse
Did you try flashing a KDZ or TOT firmware?
Saratoga79 said:
Did you try flashing a KDZ or TOT firmware?
Click to expand...
Click to collapse
That sounds like a really bad idea if the phone keeps turning off when processing ramps up. If it quits during the flash, he'd be screwed.
Oven trick to prolong the life by a little bit, maybe?
Yeah, I'm afraid KDZ TOT firmware flashing would screw me up even more.
If there are no other ideas I'll go with some rougher methods like trying to cool down the CPU with heatpaste-trick or in the end oven.
Ordered a new phone anyway and got nothing to lose. I'll let you guys know!
theFUNKY**** said:
Yeah, I'm afraid KDZ TOT firmware flashing would screw me up even more.
If there are no other ideas I'll go with some rougher methods like trying to cool down the CPU with heatpaste-trick or in the end oven.
Ordered a new phone anyway and got nothing to lose. I'll let you guys know!
Click to expand...
Click to collapse
Plug your phone to the charger when you install Fulmics.
If you see any difference's then it's your battery and you'll need to replace it.
It is working now!
What did I do: Baked the Mainboard for 10 minutes at 200° C. Additionally i applied thermal paste on the CPU.
Running like a charm for two weeks now.

Categories

Resources