Here's to hoping someone can help me out. My phone details before I messed up: LG G3 D850, rooted, TWRP 3.0, running Fulmics 5.2 for about 1 1/2 weeks
I noticed that I was not seeing the LTE indicator on my phone. I checked the HUB and saw the BootD850-30012016 data patch and figured that I just needed to install. So I flashed it and my phone wouldn't start. I was able to boot into recovery, so I figured I would do a clean install of the ROM so I did a full wipe, accidentally wiping EVERYTHING except for my external SD.
Result was that I can access TWRP but am unable to flash any of my backups or zips from my external SD, or OTG. I can see the files, but don't have the option to "swipe". I also am unable to 'mount' or 'install'.
At this point, I noticed that AT&T has finally released the OTA for Marshmallow, so I figured I would just use LG FlashTool and totally un-root and give the update a try. (BTW, I have used the flash tool many times with no problems/issues on both my phone and my son's D855).
Unfortunately, I am getting the dreaded "unable to change to download mode" after 15 seconds. I have uninstalled and re-installed Flash Tool, the LG Drivers and all files and used every port on both of my computers (Windows 10 btw) but can't get past the download error.
So...after many hours of digging, I took a leap of faith and was able to sideload Fulmics 5.1 successfully and install the 5.2 update from the HUB. I made backup of the ROM but TWRP still won't allow me to "swipe" and install/restore. I reinstalled TWRP using Flashify and it installed version 2.8 but still no go on flashing from recovery.
I realize that I'm lucky to have been able to figure out how to get the phone back using the sideload function in TWRP, but I really do want to go back to stock and it bugs me that I am unable to use my backups.
Sorry for the novel, but I wanted to be sure to include everything I did....if anyone can help me out I would be much obliged. My 11 year old is anxiously waiting on me to figure this out before she gets this phone (I'm moving up to the HTC 10 in a couple of weeks!). She still thinks I'm 'SuperMommy' so if I can fix this I get to keep my swagger!
I was also running fulmics 5.1 and updated to 5.2 in my phone but now i was having pretty good laggs and i finally realised that the update provided by the phone was corruped so i went on the official site and downloaded the same 5.2 OTAs from there and flashed it into TWRP recovery to finally get the latest version 5.3..know that is it always advisable to flash zip file when in recovery mode using TWRP recovery...The big mistake was cleaning also the internal memory of your phone.this caused the malfunction of twrp.
The issue is that most often i have seen cases of lagg in those updating to fulmics 5.2 from the Hub .sometimes in twrp recovery the update files will not successfully wipe and then reboot system with 5.2 installed but with many lagg the file downloaded there may be corrupted and not give you permission to swipe..if you really like fulmics and still update to the latest..Try this it may help you solve your problem:1 reinstall the fulmics 5.1 go to xdadevelopers.com/fulmics follow the link given by xpirit to www.fulmics.com and download the OTA 5.2(file size maybe 46 mb).. 2.reboot your phone now in twrp recovery it should now be able swipe and install..(if not then install Twrp 3.0 and try) 3-search the files in your internal memory or wherever you have downloaded it and flash it ..4.reboot system.That should be done!! In case you want to come back to stock and cant install from Twrp then the problem is with Twrp just download the latest version that goes with your phone.
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
dcli23 said:
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
Click to expand...
Click to collapse
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
SofaSpud said:
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Hey there....you can access the Hub after you flash the Fulmics ROM. It's where you can get your tweaks, downloads, mods, etc. You'll find it in your app drawer.
Im currently upgrading my 4.4.4 to a 6.0, to be exact, I use the Kali Nethunter ROM, however I ran into trouble, since it requires a CM 13 as a template. The problem is the following : no matter how many times I've tried, the TWRP just don't want to install the only CM 13 image I could found (which is to be exact a Lineage 13 17-06-10 by kutep0v)
The TWRP-s I've used are ranging from 3.1.2.0 to the last tried and often mentioned 2.8.7.0
The exact model is a bacon with 64GB
And also I use the bacon root toolkit by wugfresh
The two possible cause of this was pointed out in certain other forums said that, there either is a compatibility error with the firmware (which currently displays : UNKNOW, and neither the wifi or sim card is working), or the twrp reads a compatibility error with the image (somehow doesn't gets that A0001 is the same as bacon) I downloaded (there were a forum post about a custom modified twrp, which fixes this error, but the link is broken, and the forum article has been closed in 2015)
Could someone link me the proper firmwares for the Lineage (or CM) 13, and the proper TWRP, which are validated to be working with together?
Or any other thoughts would be helpful
randoomkiller said:
Im currently upgrading my 4.4.4 to a 6.0, to be exact, I use the Kali Nethunter ROM, however I ran into trouble, since it requires a CM 13 as a template. The problem is the following : no matter how many times I've tried, the TWRP just don't want to install the only CM 13 image I could found (which is to be exact a Lineage 13 17-06-10 by kutep0v)
The TWRP-s I've used are ranging from 3.1.2.0 to the last tried and often mentioned 2.8.7.0
The exact model is a bacon with 64GB
And also I use the bacon root toolkit by wugfresh
The two possible cause of this was pointed out in certain other forums said that, there either is a compatibility error with the firmware (which currently displays : UNKNOW, and neither the wifi or sim card is working), or the twrp reads a compatibility error with the image (somehow doesn't gets that A0001 is the same as bacon) I downloaded (there were a forum post about a custom modified twrp, which fixes this error, but the link is broken, and the forum article has been closed in 2015)
Could someone link me the proper firmwares for the Lineage (or CM) 13, and the proper TWRP, which are validated to be working with together?
Or any other thoughts would be helpful
Click to expand...
Click to collapse
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
https://www.androidfilehost.com/?fid=24389512218018449
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
https://dl.twrp.me/bacon/
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.
Mr.Ak said:
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
link
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
link
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.
Click to expand...
Click to collapse
Update I : I just hard bricked it, so I have to rebuilt the whole from scratch (color os and stuff, probably the firmware is wrong too) I had 5.1, but the mobile network somehow didnt worked for me, and I wanted to downgrade to the previously used 4.4, unfortunately not from twrp but just simple flashing, and it somehow did not responded after a certain amount of time. (that won't be a problem)
BUT, I'm sorry to say that, but you are wrong
there are official builds for CM 13 / Marshmallow
they just don't update the main page
look at here : github slash offensive-security slash kali-nethunter slash wiki (sorry, newcomer and I cant post a proper link )in the builds you can find official and nightly packages for it (I can install the kernel, and when I want to install the whole package of marshmallow kali, it says, 'please install a regular Android system first')
that works far better than the Lineage or CM 13, and those are the problematic ones(with the firmware), not the Kali
randoomkiller said:
Update I : I just hard bricked it, so I have to rebuilt the whole from scratch (color os and stuff, probably the firmware is wrong too) I had 5.1, but the mobile network somehow didnt worked for me, and I wanted to downgrade to the previously used 4.4, unfortunately not from twrp but just simple flashing, and it somehow did not responded after a certain amount of time. (that won't be a problem)
BUT, I'm sorry to say that, but you are wrong
there are official builds for CM 13 / Marshmallow
they just don't update the main page
look at here : github slash offensive-security slash kali-nethunter slash wiki (sorry, newcomer and I cant post a proper link )in the builds you can find official and nightly packages for it (I can install the kernel, and when I want to install the whole package of marshmallow kali, it says, 'please install a regular Android system first')
that works far better than the Lineage or CM 13, and those are the problematic ones(with the firmware), not the Kali
Click to expand...
Click to collapse
Good...
Mr.Ak said:
Good...
Click to expand...
Click to collapse
Okay, so since (at least in my opinion) the bottleneck is the CM 13 / Lineage 13, do you have any experience with it?
could you give me a fine working firmware and ROM combo please?
I'll have no problem unbricking it, and after that I'll probably solve the kali installation (since its documented, and seems like working), but due broken links I can't really get the recommended ones at github
Mr.Ak said:
Since you're on KitKat,you need to flash new firmware in order to flash any newer android version ROM.
https://www.androidfilehost.com/?fid=24389512218018449
Wipe everything except internal storage,then flash the firmware,then the ROM and then gapps(optional) and reboot.
About recovery,official twrp will work fine,
https://dl.twrp.me/bacon/
Edit-AFAIK,Kali Nethunter only works with cm 12.1 build as of now as mentioned in the latest thread about Kali nethunter.
Click to expand...
Click to collapse
randoomkiller said:
Okay, so since (at least in my opinion) the bottleneck is the CM 13 / Lineage 13, do you have any experience with it?
could you give me a fine working firmware and ROM combo please?
I'll have no problem unbricking it, and after that I'll probably solve the kali installation (since its documented, and seems like working), but due broken links I can't really get the recommended ones at github
Click to expand...
Click to collapse
This...
Oh, thank you.
I just didn't realised, sorry for that.
BTW do you have any idea why does my opo is undetectable for everything I've tried?
How I hard bricked was the following :
Bacon toolkit, Downgrading to Kitkat
the console was writing the stuff it flashed to the device, and suddenly stopped and said <waiting for device>
after that, nothing
I unplugged after 15 mins, and after that the only lifesign was that, it got how when I plugged it charging (not too hot, just the standard "oneplus one is charging" hot)
I have an xp machine with the proper drivers and the rescue toolkit, but it cannot detect, not even as an unrecognizable usb device which lacks driver
I think the bottleneck is the phone now, but I just don't know what should I do
randoomkiller said:
Oh, thank you.
I just didn't realised, sorry for that.
BTW do you have any idea why does my opo is undetectable for everything I've tried?
How I hard bricked was the following :
Bacon toolkit, Downgrading to Kitkat
the console was writing the stuff it flashed to the device, and suddenly stopped and said <waiting for device>
after that, nothing
I unplugged after 15 mins, and after that the only lifesign was that, it got how when I plugged it charging (not too hot, just the standard "oneplus one is charging" hot)
I have an xp machine with the proper drivers and the rescue toolkit, but it cannot detect, not even as an unrecognizable usb device which lacks driver
I think the bottleneck is the phone now, but I just don't know what should I do
Click to expand...
Click to collapse
Fastboot drivers are not installed correctly...try uninstalling and installing again.
Mr.Ak said:
Fastboot drivers are not installed correctly...try uninstalling and installing again.
Click to expand...
Click to collapse
That could be possible, however I've tried with at least 3 drivers on 2 laptops(Win10 and an old XP), and neither picked it up even as an unrecognisable device (So basically there is literally no difference wheter I plug in or not plug in, from the computers view, or at least I didn't find it at the device manager, neither was there an alert of a device not recognisable). The drivers were :
- QUD.WIN.1.1 10037.3 - Latest from androidbrick
- Driver from colorOS
- The one I've been using before bricking it (and I had no problem with it before)
I've been digging up threads, and the only one I could find so far, where the device wasnt recognised even as an unrecognisable device was due a discharged battery.
randoomkiller said:
That could be possible, however I've tried with at least 3 drivers on 2 laptops(Win10 and an old XP), and neither picked it up even as an unrecognisable device (So basically there is literally no difference wheter I plug in or not plug in, from the computers view, or at least I didn't find it at the device manager, neither was there an alert of a device not recognisable). The drivers were :
- QUD.WIN.1.1 10037.3 - Latest from androidbrick
- Driver from colorOS
- The one I've been using before bricking it (and I had no problem with it before)
I've been digging up threads, and the only one I could find so far, where the device wasnt recognised even as an unrecognisable device was due a discharged battery.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2588979
Try this.
Update :
a friend of mine had an OPO to sell for ~100 USD, so to have a working phone, I bought that
it had Lineage 14.1, with firmware 0241, and TWRP, BUT, when I've tried to install the lineage 13, it said the same error 7
I've updated its firmware to 0011, and same thing happened, error 7 when I've tried to install lineage 13
now its on a factory reset lineage 14.1
maybe my image is bad
any idea where could I find the CM 13 or lineage 13?
and also I've tried the old phone with the adb drivers you've suggested, but no update with that one
randoomkiller said:
Update :
a friend of mine had an OPO to sell for ~100 USD, so to have a working phone, I bought that
it had Lineage 14.1, with firmware 0241, and TWRP, BUT, when I've tried to install the lineage 13, it said the same error 7
I've updated its firmware to 0011, and same thing happened, error 7 when I've tried to install lineage 13
now its on a factory reset lineage 14.1
maybe my image is bad
any idea where could I find the CM 13 or lineage 13?
and also I've tried the old phone with the adb drivers you've suggested, but no update with that one
Click to expand...
Click to collapse
https://www.google.co.in/amp/s/foru.../rom-lineageos-13-0-oneplus-one-t3549203/amp/
Oh, then the problem is not with that
I've used the exact same
what do you thing, what would cause the error 7? how can I overcome with the problem, and finally install cm13? ( or at least some diagnostical features I should check to find the problem )
and do you have any idea what could I do with the bricked one?
randoomkiller said:
Oh, then the problem is not with that
I've used the exact same
what do you thing, what would cause the error 7? how can I overcome with the problem, and finally install cm13? ( or at least some diagnostical features I should check to find the problem )
and do you have any idea what could I do with the bricked one?
Click to expand...
Click to collapse
It's probably a bad download,redownload the zip.
About the bricked one,you have to figure out the fastboot drivers issue.