Hi guys.
I have tried to take a logcat of my phone when it bootloops upon restarting after install. Here is the code I used:
Code:
adb -d logcat>C:\adb>Bootloop.txt
However, the output file is empty.
My issue is that I can install any stock-based ROM, but not any custom ROMs (CM or AOSP). When I try to install custom ROMs (CM or AOSP) it always bootloops.
So I am trying to trace the phone when it bootloops. My PC does recognise the phone, as I get the message "This device can perform faster if blah, blah, blah".
Is there another way I can trace the boot up process to find out what errors its throwing out?
Thx in advance.
theKramer
I don't know if USB Debugging is turned on my default on custom ROMs - it isn't on stock ROMs, so logcat wouldn't work via ADB until that would be enabled, which if the custom ROM bootloops from the very start, obviously you wouldn't be able to turn it on.
Have you re-wiped Cache, Dalvik/ART and Data? Flash the appropriate Bootstack? Try moving what you want to keep from your internal storage, eject your MicroSD card/keep it ejected and wipe/reformat your internal storage from TWRP. You can always turn the phone off from TWRP after flashing the custom ROM/Bootstack and then eject the card. Last but not least, try flashing the TOT to start fresh, reroot with the Stump app, put TWRP on with TWRP Manager, and flash the custom ROM and Bootstack like that, although if you go back to stock again after that, I recommend flashing the TOT again before doing so, as some people have trouble with signal or mobile data coming from non-stock or international-stock based ROMs.
Edit: Just noticed you're on the D855, so I don't know the TOT situation there - I only know the VS985, but the advice still stands.
roirraW "edor" ehT said:
I don't know if USB Debugging is turned on my default on custom ROMs - it isn't on stock ROMs, so logcat wouldn't work via ADB until that would be enabled, which if the custom ROM bootloops from the very start, obviously you wouldn't be able to turn it on.
Have you re-wiped Cache, Dalvik/ART and Data? Flash the appropriate Bootstack? Try moving what you want to keep from your internal storage, eject your MicroSD card/keep it ejected and wipe/reformat your internal storage from TWRP. You can always turn the phone off from TWRP after flashing the custom ROM/Bootstack and then eject the card. Last but not least, try flashing the TOT to start fresh, reroot with the Stump app, put TWRP on with TWRP Manager, and flash the custom ROM and Bootstack like that, although if you go back to stock again after that, I recommend flashing the TOT again before doing so, as some people have trouble with signal or mobile data coming from non-stock or international-stock based ROMs.
Edit: Just noticed you're on the D855, so I don't know the TOT situation there - I only know the VS985, but the advice still stands.
Click to expand...
Click to collapse
Hi @roirraW "edor" ehT
This is a long ongoing issue. Basically it surfaced after flashing back to stock as I was having random reboots and thought it might be custom ROM related, but after flashing stock I still had the reboot issues, so figured out battery was toast so changed that and reboot issues were resolved.
But since flashing stock MM on my D855, I cannot get any custom ROM (CM/AOSP) to boot on my ROM except Bumped 5.0.1 ROMs.
I can install any stock or stock-based ROM without any issue, however, custom, no go. The funny thing is that I was running custom ROMs on my phone for more than a year without issue. I could throw any custom ROM at it, and where other people might have issues, my phone would always run them flawlessly.
Not anymore
I have flashed stock Lollipop about 7 or 8 times (via LGUP and LG Flash Tool 2014) and stock KK about another 4 times, so I should have blown out any MM remnants at this stage.
The weird thing is that my phone doesnt boot up with stock based KK either (all of them just hang on bootup), but LP or MM is no issue. I am running LIMITLESS ROM v10.2 at the moment (based on v30a). I cannot remember if I tried v10b actually, I did so many of them..
I have rooted from LP each time, and it is always successful (I have used 3 or 4 different rooting methods) and TWRP is successfully bumped each time.
I have tried numerous versions of TWRP (2.6/2.8/3.0/3.0.2).
I have done a full wipes (cache/dalvik/data/system), even including a format data after and still no luck..
The reason I was asking about methods to get some kind of log info during bootup was so I could maybe get some info on why it doesnt boot custom ROMs..
theKramer said:
Hi @roirraW "edor" ehT
Click to expand...
Click to collapse
Hi! Argh. Sounds really frustrating! Bear with me since it sounds like you know what you're doing and again I have the VS985. Among the 100% stock unrooted you flashed, did you only flash KDZs or is there a TOT available and did you try that? The reason I ask is that TOTs flash more partitions than KDZs and can fix problems that KDZs and ROMs can't. I can personally attest to that but once I experienced it and asked an experienced developer, it became clear that's expected, and when I extracted the partitions out of the VS985 10B TOT and compared to the KDZ I indeed noticed one or two more partitions.
Again, don't mind me if I'm telling what you already know. The other thing is the Bootstack situation, although I haven't ever experienced a bootloop due to the wrong Bootstack, only non-working modem or dangerous combo of our Marshmallow sbl1 partition along with the BUMP-vulnerable 12B aboot (bootloader), necessary for TWRP and for root on Marshmallow. Reference this VS985 post if needed http://forum.xda-developers.com/showpost.php?p=63438031&postcount=2. I don't really expect that to be the issue and since you tried from a variety of stock ROM situations, I wouldn't have expected you to have an issue with every combo you tried.
Edit: actually, the remaining item is the MicroSD card. I know it sounds silly but it's happened. Try it without the card and see what happens. While you're at it, try with the SIM ejected too just for the heck of it, won't hurt to try.
Good luck! Hope you figure it out.
roirraW "edor" ehT said:
Hi! Argh. Sounds really frustrating! Bear with me since it sounds like you know what you're doing and again I have the VS985. Among the 100% stock unrooted you flashed, did you only flash KDZs or is there a TOT available and did you try that? The reason I ask is that TOTs flash more partitions than KDZs and can fix problems that KDZs and ROMs can't. I can personally attest to that but once I experienced it and asked an experienced developer, it became clear that's expected, and when I extracted the partitions out of the VS985 10B TOT and compared to the KDZ I indeed noticed one or two more partitions.
Again, don't mind me if I'm telling what you already know. The other thing is the Bootstack situation, although I haven't ever experienced a bootloop due to the wrong Bootstack, only non-working modem or dangerous combo of our Marshmallow sbl1 partition along with the BUMP-vulnerable 12B aboot (bootloader), necessary for TWRP and for root on Marshmallow. Reference this VS985 post if needed http://forum.xda-developers.com/showpost.php?p=63438031&postcount=2. I don't really expect that to be the issue and since you tried from a variety of stock ROM situations, I wouldn't have expected you to have an issue with every combo you tried.
Edit: actually, the remaining item is the MicroSD card. I know it sounds silly but it's happened. Try it without the card and see what happens. While you're at it, try with the SIM ejected too just for the heck of it, won't hurt to try.
Good luck! Hope you figure it out.
Click to expand...
Click to collapse
Hi.
I didnt know that about there being more partitions in TOT vs KDZ files actually..
I have tried flashing without SD card also already.. I haven't tried without sim card, so why not
Is there a specific reason you mentioned flashing v10b, by the way?
theKramer said:
Hi.
I didnt know that about there being more partitions in TOT vs KDZ files actually..
I have tried flashing without SD card also already.. I haven't tried without sim card, so why not
Is there a specific reason you mentioned flashing v10b, by the way?
Click to expand...
Click to collapse
In the case of the VS985, 10B is the first or earliest build we have, and we have a TOT of it, so I was just using it as an example. I've only ever noticed a leak of one TOT per variant of a device at the most, but if you have more than one available I would choose the earliest.
Mostly useless information to you, but the VS985 does have a 10B KDZ, but it's 10B_01, whereas the TOT is 10B_03. 10B_03 was the official release so it can get OTAs, and 10B_01 was a leak so it can't. From what I've seen, the sub-build _## is only available as part of the filename when you get a hold of the KDZ and TOT. 10B for the VS985 is also the easiest to root because we can just use the Stump app with its brute force option. For us, rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. Both 10B and 12B are still KitKat. 23C and 24B 5.0.1 are rootable via PC/USB/adb script. As far as I remember, 35B 5.1.1 and definitely 46A through 48A 6.0 has no method of permanent root, only KingRoot on 35B through 47A which gives temporary and suspicious root.
roirraW "edor" ehT said:
In the case of the VS985, 10B is the first or earliest build we have, and we have a TOT of it, so I was just using it as an example. I've only ever noticed a leak of one TOT per variant of a device at the most, but if you have more than one available I would choose the earliest.
Mostly useless information to you, but the VS985 does have a 10B KDZ, but it's 10B_01, whereas the TOT is 10B_03. 10B_03 was the official release so it can get OTAs, and 10B_01 was a leak so it can't. From what I've seen, the sub-build _## is only available as part of the filename when you get a hold of the KDZ and TOT. 10B for the VS985 is also the easiest to root because we can just use the Stump app with its brute force option. For us, rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. Both 10B and 12B are still KitKat. 23C and 24B 5.0.1 are rootable via PC/USB/adb script. As far as I remember, 35B 5.1.1 and definitely 46A through 48A 6.0 has no method of permanent root, only KingRoot on 35B through 47A which gives temporary and suspicious root.
Click to expand...
Click to collapse
So, I haven't actually flashed v10b as I have handed my phone in to a phone repair shop as I have been having a number of hardware issues such as wifi not working, high temperatures at the back of the phone and SIM card detection issues (most likely related to the phone heating up).
However, before I had handed it in to the shop, I flashed a custom kernel (Gabriel stock-based) on the stock ROM I was running at the time, and that reminded me that I have flashed Gabriel kernel on a number of different stock and stock-based ROMs, and if I flashed a stock-based custom kernel, I also got the same bootloop error.
So I was wondering if that might help in any way to pinpoint what is going on with my phone...
theKramer said:
However, before I had handed it in to the shop, I flashed a custom kernel (Gabriel stock-based) on the stock ROM I was running at the time, and that reminded me that I have flashed Gabriel kernel on a number of different stock and stock-based ROMs, and if I flashed a stock-based custom kernel, I also got the same bootloop error.
So I was wondering if that might help in any way to pinpoint what is going on with my phone...
Click to expand...
Click to collapse
I don't think that's specific enough to narrow things down any in this case, but doesn't hurt to note the info! Good luck with your phone!
roirraW "edor" ehT said:
I don't think that's specific enough to narrow things down any in this case, but doesn't hurt to note the info! Good luck with your phone!
Click to expand...
Click to collapse
So my feeling is that there is something up with my boot image, even though my phone is rooted and bumped and TWRP is bumped, there is something my phone doesnt like in AOSP/CM or modified stock-based kernels that is not visible in LG stock.
Is there any tool/script that I can run that would collect info on the boot process...
theKramer said:
So my feeling is that there is something up with my boot image, even though my phone is rooted and bumped and TWRP is bumped, there is something my phone doesnt like in AOSP/CM or modified stock-based kernels that is not visible in LG stock.
Is there any tool/script that I can run that would collect info on the boot process...
Click to expand...
Click to collapse
I'm not very knowledgeable about logs or experienced collecting or looking through them, but maybe collecting a logcat through adb (over USB) while booting would help? You'd have to have USB Debugging turned on, and make sure it stays on across reboots - there's a common issue that is easy to resolve where if USB Debugging doesn't stay on after you reboot, turn it on, plug it into a PC, manually switch the USB connection mode on the phone from MTP and PTP and back to MTP and then disconnect the cable, and it'll stay on then.
roirraW "edor" ehT said:
I'm not very knowledgeable about logs or experienced collecting or looking through them, but maybe collecting a logcat through adb (over USB) while booting would help? You'd have to have USB Debugging turned on, and make sure it stays on across reboots - there's a common issue that is easy to resolve where if USB Debugging doesn't stay on after you reboot, turn it on, plug it into a PC, manually switch the USB connection mode on the phone from MTP and PTP and back to MTP and then disconnect the cable, and it'll stay on then.
Click to expand...
Click to collapse
So, I was suggested the app Liveboot, which was created by Chainfire of SuperSU fame. This app outputs a log to the screen and to a log file on the device of all the calls that are made during bootup (with user selectable level of detail).
Running this app, I did two traces. One with just stock LG and the second after flashing a modified stock kernel..
The stock log is 21KB, the log from when I flashed the modified kernel is 904KB.
Liveboot Stock
Liveboot with kernel
This is not an issue with the modified kernel per se, but with some settings in modified kernels. Any way to pinpoint the offending code/parameter?
This is not directed at you "roirraW "edor" ehT", but to any and all that could help me to figure out what is going on..
theKramer said:
So, I was suggested the app Liveboot, which was created by Chainfire of SuperSU fame. This app outputs a log to the screen and to a log file on the device of all the calls that are made during bootup (with user selectable level of detail).
Click to expand...
Click to collapse
Just wanted to say thanks for a reminder about that app. I had even tested the app when it first came out and I somehow keep forgetting about it.
So I have isolated the issue to some kind of hardware issue.
If I leave my phone turned off for a while with battery out, I can get it to boot custom ROMs. I have tried with 2 different batteries, so its definitely the phone itself. If I reboot the phone once the phone has booted up, then it boot loops again, even if the phone is only booted for a few minutes.
I had to debick my phone a couple of months ago using the short circuit method (due to some stupidity on my part) and it seems that that has fried something in my phone.
Since I brought my phone back to life I have been having issues with Wifi and SD-card slot not working, plus lots of heat and terrible battery life.
I would love to know though what it is in custom ROMs/Kernels that causes my phone to bootloop.
It would be great if I could isolate that somehow.
Anybody have any ideas, by any chance?
Related
Hi all
i'm running a 16GB/2GB D855 and decided to go back to stock 20F lollipop the other day from the Cloudy G3 rom and I now can't get write access to the internal storage. When I initially flashed the kdz file I also lost the system ui and wifi. Flashing back to 10l fixed all three problems and I've since tried flashing lollipop via the LG PC Suite (20F) and via the LG Flashtool (20F and 20H), but the outcome is always the same with no write access to internal storage, wifi and system ui are back though.
From what I've been able to workout its an issue with the SELiniux content, but I haven't been able to find a way to fix it as I don;'t have root on Lollipop.
Since going back to 10L I can see the phones root files in ES, but can't edit them, so its kind of half got root access.
Anyone have any ideas of how to fix it other than going back to a custom rooted rom? (I have nothing against custom Roms, but I get much better battery life on stock which is why I'd like to stick with it.)
bribric said:
Hi all
i'm running a 16GB/2GB D855 and decided to go back to stock 20F lollipop the other day from the Cloudy G3 rom and I now can't get write access to the internal storage. When I initially flashed the kdz file I also lost the system ui and wifi. Flashing back to 10l fixed all three problems and I've since tried flashing lollipop via the LG PC Suite (20F) and via the LG Flashtool (20F and 20H), but the outcome is always the same with no write access to internal storage, wifi and system ui are back though.
From what I've been able to workout its an issue with the SELiniux content, but I haven't been able to find a way to fix it as I don;'t have root on Lollipop.
Since going back to 10L I can see the phones root files in ES, but can't edit them, so its kind of half got root access.
Anyone have any ideas of how to fix it other than going back to a custom rooted rom? (I have nothing against custom Roms, but I get much better battery life on stock which is why I'd like to stick with it.)
Click to expand...
Click to collapse
when flashing an kdz file ALWAYS do an CSE flash to prevent these problems, just try it
suljo94 said:
when flashing an kdz file ALWAYS do an CSE flash to prevent these problems, just try it
Click to expand...
Click to collapse
I've tried a number of cse flashes to various lollipop versions, but with the same outcome each time. Im guessing that the file system has been screwed up so I will probably need to root on KK and then try to sort it through TWRP.
In the end I found solution which is:
1. Flash a KK ROM through the LG flash tool, 10l in this case
2. Root with purpledrake
3. I stall TWRP
4. Install Cloudy G3 as well as a full wipe and format data.
For know I'm sticking with Cloudy G3 as I ain't be stuffed messing around with it anymore
Hi, just encountered a similar problem.
When you say format data, you mean the internal sd storage as well? That's one thing i haven't tried yet.
Thanks
kinnyfaifai said:
Hi, just encountered a similar problem.
When you say format data, you mean the internal sd storage as well? That's one thing i haven't tried yet.
Thanks
Click to expand...
Click to collapse
I used the format data option in TWRP under the advanced wipe menu, which I believe just formats your data partition.
I've since flashed a 20H ROM over Cloudy G3 through TWRP and haven't encountered the same problem again.
I even had a same issue couple of days back..here is what i did
flashed kitkat rom tot method and reinstalled lollipop..everything got automatically corrected
I'm going to be away soon and won't have easy access to a non-professional PC (meaning any computer I may have access to - I won't have admin rights with). I didn't want to wait for a root+TWRP dev package for Lollipop to be released. I wanted to just get it done, (I was having bad problems with KitKat on some select apps because of LG's 4.4 coding, long story, but I won't even go there...)
I saw that I can go to the LG support site via a link from Android Central and manually upgrade to Lollipop way before the OTA rollout even begins. I had heard rumors of people having problems, read posts, and learned how to avoid it all. I reset everything before upgrading. I did many factory resets after getting Lollipop, (I know, a lot). I got rooted and set mostly everything up.
I wanted to get Xposed loaded, BADLY. I looked it up for Lollipop and realized that I'd have to flash a custom recovery. I expected as much. When I looked that up, I realized that I would have to either use a downgrade-upgrade method (which I didn't feel like going through) or a mandatory requirement of factory reset though a process. I had already set up all of the system stuff and restored from Titanium backup most of my apps. There was no way I would factory reset because I hate resetting-up the system stuff. - - - - - BIG MISTAKE 1
So I found a thread for the D850 (AT&T) version (no I didn't flash a bad radio or anything, I thought I knew what I was doing because I was only flashing recovery stuff for Lollipop, not an AT&T rom or radio.) This was to install TWRP without downgrading or resetting. The instructions said to copy files from an aboot.img and other boot images and such (to replace the recovery) on to the internal memory and use a terminal to type in code. I did it and rebooted it.
I made a horrible mistake.
When I held the power button on the phone, nothing happened. I found out that when plugging it in to the PC, it seems to be in download mode. It was fully charged. When using the restore/brick recovery software, I have tried different cables, different computers, checking to see if anything is corrupt, different USB ports, etc. with the files... Nothing will work. I keep getting an error with a red box about the model or something. "Model Information Check Fail"
So basically I have broken boot images on my device. I need to fix these.
Where do I go from here? All because I wanted Xposed on Lollipop without resetting.
Click to expand...
Click to collapse
I have this situation. I messed up with laf.img and aboot.img too (from D850, thinking it was harmless since trying to install custom recovery only) and device won't turn on but PC recognizes as download mode but can't flash. Please read above. I'm bricked and all restore methods have failed so far.
Source from u/nicksteron on reddit.
I'm having this issue now too. It seems the thing I downloaded and tried broke my boot images.
Have you been able to fix this?
I'm trying the LG Flash Tool but it stops me at the model check fail as well. Gonna try a kdz method next.
EDIT: I tried the KDZ method with LG Flash Tool 2014 using both a KitKat and Lollipop based ROMs and I get an error. The S/W Upgrade progress gets to 4% and then the error shows up. I need my phone. Help?!
Full disclosure, I'm 100% new to all of this and I'm having a hard time picking up the lingo. I flashed the 47a kdz onto my g3 and it all went well. Everything is working on the phone except my internet. I have none. After doing some reading I'm assuming it is because I need the 35b bootstack for the modem. I had downloaded the 35b bootstack, unzipped it, and moved the files into my internal storage. I thought this was all I needed to do, but apparently I did something. Can someone help me with how exactly to flash a bootstack, or whatever else I could have done wrong that is causing my internet not to work. Everything is working perfectly. Thank you very much in advance.
You shouldn't have to flash the 35B bootstack, that's for people that use a custom recovery.
You have the latest 47A images (same ones that the 35B bootstack uses, but newer) and there is no reason to downgrade your images.
First try a hard factory reset, if I have to guess that'll fix your issue.
Else redownload and reflash your KDZ (yes, redownload it; some of the images could be messed up and/or the flash might have messed up).
Else, try a new SIM card; sometimes (rarely from what I have seen) this can be the issue so this is a last resort.
PS: When you have a file to flash, it's supposed to be left zipped and done in custom recovery. You will not need to flash though, like previously stated that bootstack is for users that have a custom recovery.
Ariac Konrel said:
You shouldn't have to flash the 35B bootstack, that's for people that use a custom recovery.
You have the latest 47A images (same ones that the 35B bootstack uses, but newer) and there is no reason to downgrade your images.
First try a hard factory reset, if I have to guess that'll fix your issue.
Else redownload and reflash your KDZ (yes, redownload it; some of the images could be messed up and/or the flash might have messed up).
Else, try a new SIM card; sometimes (rarely from what I have seen) this can be the issue so this is a last resort.
PS: When you have a file to flash, it's supposed to be left zipped and done in custom recovery. You will not need to flash though, like previously stated that bootstack is for users that have a custom recovery.
Click to expand...
Click to collapse
I will give it a try! Thanks so much for the help. I'm at work on the wifi, I'll give it a go tomorrow. Should it Make any difference that the phone is being used on straight talk?
I tried a hard reset and still nothing. 3g/4g shows up at the top but the bars showing it's active are non existent, and I have no mobile network. I will try to re download and flash again tomorrow. Thanks again for the help.
Edit: I think I used this http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
I think I may have used the wrong one? But it's the only stock kdz I saw. Unfortunately I'm brand new to all of this ?
Ariac Konrel said:
You shouldn't have to flash the 35B bootstack, that's for people that use a custom recovery.
You have the latest 47A images (same ones that the 35B bootstack uses, but newer) and there is no reason to downgrade your images.
First try a hard factory reset, if I have to guess that'll fix your issue.
Else redownload and reflash your KDZ (yes, redownload it; some of the images could be messed up and/or the flash might have messed up).
Else, try a new SIM card; sometimes (rarely from what I have seen) this can be the issue so this is a last resort.
PS: When you have a file to flash, it's supposed to be left zipped and done in custom recovery. You will not need to flash though, like previously stated that bootstack is for users that have a custom recovery.
Click to expand...
Click to collapse
Tried everything you said, and tried this http://www.mylgphones.com/how-to-flash-android-6-0-m-stock-firmware-on-lg-vs985-using-lg-up-software . I did not try a different sim card yet, as I only have this one, but the internet will still not work.
stevehug said:
I will give it a try! Thanks so much for the help. I'm at work on the wifi, I'll give it a go tomorrow. Should it Make any difference that the phone is being used on straight talk?
Click to expand...
Click to collapse
It may, I think you just have to set your APNs.
This is the Straight Talk APN.
stevehug said:
Tried everything you said, and tried this http://www.mylgphones.com/how-to-flash-android-6-0-m-stock-firmware-on-lg-vs985-using-lg-up-software . I did not try a different sim card yet, as I only have this one, but the internet will still not work.
Click to expand...
Click to collapse
That's a full ROM that is used to be flashed in TWRP (AKA custom recovery).
THIS is the KDZ method I use:
Guide that always works for me here.
VS98547A KDZ download here.
Extract the 7Z file until you just have the KDZ file.
This method will COMPLETELY wipe your phone, pictures, videos, games, apps, etc.
Make backups!
THIS is the KDZ method I use:
[URL="http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140" said:
Guide that always works for me here.[/URL]
VS98547A KDZ download here.
Extract the 7Z file until you just have the KDZ file.
This method will COMPLETELY wipe your phone, pictures, videos, games, apps, etc.
Make backups!
Click to expand...
Click to collapse
I'm following the guide spot on, when I try to flash back to 10b, I get an error and the process won't continue the "upgrade". This is so frustrating, I guess I should have left well enough alone when I got the phone instead of wanting the newest update
Ariac Konrel said:
It may, I think you just have to set your APNs.
This is the Straight Talk APN.
That's a full ROM that is used to be flashed in TWRP (AKA custom recovery).
THIS is the KDZ method I use:
Guide that always works for me here.
VS98547A KDZ download here.
Extract the 7Z file until you just have the KDZ file.
This method will COMPLETELY wipe your phone, pictures, videos, games, apps, etc.
Make backups!
Click to expand...
Click to collapse
I was able to flash back to 35b and my phone is fully functional again, I cannot thank you enough for your help. My wife was ready to kick my butt! haha. Maybe I will try going to 47a now knowing that I can go to 35b and be funtional if it doesn't work. Again, I cannot thank you enough for your kindness and your help, you saved me a large headache!
stevehug said:
I was able to flash back to 35b and my phone is fully functional again, I cannot thank you enough for your help. My wife was ready to kick my butt! haha. Maybe I will try going to 47a now knowing that I can go to 35b and be funtional if it doesn't work. Again, I cannot thank you enough for your kindness and your help, you saved me a large headache!
Click to expand...
Click to collapse
Since this is the Verizon version, my suggestion is go to the Verizon specific forums. And yes, if you took one of the 47a images, that's not an official image. And yes, you must have the 35b modem and bootstack because TWRP will not work with those and the 47a image assumes that's what you have. Usually, it can result in a brick which requires a TOT or KDZ flash to fix.
Hey all,
Fairly new to custom roms, so hopefully I'm asking a legit question. My phone is a D855, currently on DU 10.3. I wanted to upgrade to the 10.4, doing a clean install, but I seemingly cannot wipe anything. TWRP (using 3.0.2) will give an error message: failed to mount \[...]. Interestingly, flashify labels the recovery as Stock, so maybe there is a connection.
I have been doing some googling/"xda-ing" and as it seems, going back to stock can help. BUT, for one, I hope that there's an easier way, and also I would like to know what's causing this issue. Maybe it can be avoided somehow? So maybe someone can help me with that?
Cheers.
Just going to add a few more specific questions. As I am rather unexperienced, I don't want just to try things out without a confirmation that it's safe to go:
- TWRP: can I just try and reflash the newest one via flashify? Or maybe recover an old backup and update? Might it solve the issue and is it safe to go?
- If I have to revert back to stock: I'm coming from stock MM -> root -> Dirty Unicorns. Can I revert back to MM directly using that LG up method, or would you rather recommend flashing Lollipop, if I want to root again anyways? There seems to be a plethora of options for flashing stock (MM to MM, MM to LP, LP to MM, ...) and I am not sure which one applies here...
Hey. I had similar problem with my ls990. And tried all means to fix. Twrp was not mounting the system and sometimes internal storage appears as 0mb. It was so frustrating. So i resorted back to stock. But why flashing stock i got hooked at 98% and since then i was not able to do anything. My phone hardbricked.
Ugh, great prospects. :\
Really hope I can sort this out. At least, my phone is running fine so far, so no need to hurry. Glad for any idea!
Dellocatus said:
Ugh, great prospects. :\
Really hope I can sort this out. At least, my phone is running fine so far, so no need to hurry. Glad for any idea!
Click to expand...
Click to collapse
Wait. Let me understand you well. U can boot up phone? U mean the only issue is you not able to flash anything via recovery right?
Oh, forgot to mention explicitly that the phone is still running fine. So yeah - I just cannot wipe and thus cannot flash anything. So for now, I am stuck with the rom I am on, unless I find a solution to the problem.
[HELP][G3][VS985]issue connecting to PC on fastboot, need to reflash TWRP & SuperSU
Hello, thank you for this great forum with helpful members, I'm having an issue with an LG G3 VS985, fastboot won't recognize it while in bootloader, I need to reflash TWRP.
First of all, thank you for reading this long testament [most important details in bold if TL;TR], wanted to be as detailed as possible, maybe it will help you help me better hehe sorry about that.
Let me give you the event sequence if it helps.
> Phone had Cloudy G3 2.5 rooted with SuperSU and TWRP 2.8.6.0 since I rooted it back in 2016.
I was having some issues with phone not recognizing micro sd card and OTG-USB after messing around with encrypting it, I was curious but didn't need it, anyways. Although I dropped the phone in water a couple weeks prior so there is a chance the issue is hardware related.
That was like 4-5 months ago.
Finally decided to do a file backup and reinstall everything yesterday apr-5-2019.
> Rebooted into TWRP and erased everything (data, cache, dalvik, system, even internal storage) because I wanted a new install on everything.
> Flashed the latest official TWRP version for my device (3.0.2.0)
> Had a lot of issues flashing crDroid, found out I downloaded the wrong build, although I had to edit updater-script on the right one to make it work.
> Flashed crDroid 5.2_20190326 with open GApps for Android 9.0 Stock
> First issue encountered, I couldn't charge the phone turned off, because the battery logo appears but but doesn't do the animation and reboots the phone, I read it might be an issue with TWRP.
> Tried to flash SuperSU 2.82 SR5 with TWRP but had a LG secure boot error and couldn't boot up android.
> RE-flashing android and open GApps fixed this issue.
> Re-attempted the process several times, even wiping everything down more than a couple times, including re-flashing android several times to no avail, I was not able to flash SuperSU successfully.
I even flashed an old tool "MR.Bump" but system kept unrooted so unsuccessful.
> Reflashed Android for the last time and start reading again (after 8 hours attempting to do it well), I read that TWRP version might be the problem to flash SuperSU, so
HERE is where I have the current issue:
> Downloaded the official TWRP version 3.1.0 and flashed it.
There is no official support for 3.1.0 for the VS985 so I'm guessing it was a generic .img, of course I messed up TWRP.
> Downloaded and installed official LGMobile Drivers 4.2.0 (latest), downloaded android drivers (15 second ADB installer 1.4.3) and Android platform tools 28.0.2 on windows.
> When conected in PTP and transfer files in win7 it recognizes all the drivers well, was able to reboot the phone into bootloader from android platform tools successfully, means there is good communication between the device and PC.
The issue is once the phone is in the bootloader and trying to flash TWRP, win7 has issues installing CDC serial drivers, in the end in device manager all drivers seems installed but win notification center says there was a problem installing LGE AndroidNet for VZW USB Modem, seems to be issues with CDC Serial or something, when trying to access the properties on the VZW USB Modem it freezes so there's an issue here.
That means when doing adb devices or fastboot devices command, doesn't find anything.
Tried the same in win10, had different driver problems but in the end everything gets installed after rebooting. Same issue, no response from phone when in bootloader.
Message is "Waiting for any device".
Maybe there is an issue with some low-level driver/kernel/firmware that is creating this issue, I would even consider to flash stock LG Android to start from scratch, if you have any guide on how to do it please provide the links!
Additional note: When connecting the phone in USB Tethering win7 gives bluescreen.
> FORTUNATELY I messed TWRP but the phone can still boot android so it's not rendered unusable (yet lol).
I must admit I wasn't super careful downloading some stuff, I did it old school (trial and error) and most of the times it works, I consider myself being a little tech savvy, but right now I'm stuck, I guess I could continue using the phone like this but if I have any issues it would be difficult to resolve and I would lose functionality without root (I could live unrooted though but I wanna resolve this) and honestly I love the G3 so why change it? haha.
BTW I found these on the net, do you recommend it? what TWRP do you recommend for the VS985?
I downloaded and wanted to install this one https://forum.xda-developers.com/lg-g3/development/recovery-unofficial-multirom-twrp-artx-t3657524
and found this one supposedly 3.2.1 for the vs985 here: https://basketbuild.com/devs/yshalsager/TwrpBuilder/lge/vs985
Any help will be greatly appreciated.
Cheers.
I posted it on a different area and got no response, so here it is the G3 area.
@disrupted_mind, wow, that was a great detailed post. Alas, can't think of anything much to suggest at the moment. Just a few things come to mind.
Make sure to use a USB 2.0 port on the computer. I've heard of issues with USB 3.0.
Use a good cable but I assume yours is good or original.
There's another TWRP from @HardStyl3r, v3.2.3. Since he's one of our last ROM devs I'm sure it might be the one to use, especially if you're trying Pie.
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.2.3.0][UNOFFICIAL] TeamWin Recovery Project for LG G3
Let us know if that one works or not.
LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
@disrupted_mind, wow, that was a great detailed post. Alas, can't think of anything much to suggest at the moment. Just a few things come to mind.
Make sure to use a USB 2.0 port on the computer. I've heard of issues with USB 3.0.
Use a good cable but I assume yours is good or original.
Click to expand...
Click to collapse
Thank you for replying, now that you mention it, all the ports on the PC's I've tried are USB 3.0, I think I have an older lappy with USB 2.0 and I will try that next. If that doesn't work I was planning on rooting the phone temporarily with kingroot or kingoroot, so I can use flashify and re-flash TWRP (just thought about it last night hehe) and then re-flash the ROM since according to this thread, kingroot and kingoroot might be malware.
marcdw said:
There's another TWRP from @HardStyl3r, v3.2.3. Since he's one of our last ROM devs I'm sure it might be the one to use, especially if you're trying Pie.
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.2.3.0][UNOFFICIAL] TeamWin Recovery Project for LG G3
Let us know if that one works or not.
LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Thanks, yes, precisely yesterday I kept reading trying to find a solution and bumped into @HardStyl3r's version, already downloaded it
I like Pie very much by the way, but I think it drains the battery a little faster than CloudyG3 (android 5), maybe the old hardware struggles too much haha, but I will keep using it for some time. By the way, do you think AppOps is still necessary with Android integration to allow/deny permissions (sorry, noobie question since I'm just transitioning from old to newer android with that feature).
Any ideas on the charging the phone off issue?
I will update the thread with any news
Cheers.
I have good news and bad news.
I was able to reflash stock KitKat using TOT method, only way it could work since I had no connection to PC with fastboot commands on cmd.
Updated android over the air and PC, it update to 5.0.1 over the air and wanted to go faster so tried to do it from PC, what a mistake, when I was downloading Marshmallow info on xda I found that it might be difficult to root android 6, so cancelled the operation from LG Update Software on PC. That went "fine", didn't update to Marshmallow.
Rooted the phone using the One-Click root method, worked fine apparently. Installed flashify and flashed the Unofficial 3.2.3 TWRP, that didn't go well, I dont have access to Recovery mode nor Bootloader/Download mode now. "Recovery" ("vol-" + "Power Button") mode gives "certificate/secure boot error", Regular "Bootloader/Download mode" is non-existant or I can't access it in any given way, tried "vol+" while off + "Power Button", tried to reboot to it from Rashr, nope, it just continues to boot android, the other "Download mode ("Vol+" + "Connect USB cable to PC")" (don't know if it's the same as Bootloader) gives "certificate/secure boot error". I even flashed the latest official TWRP for vs985 and 2.8.6 that I knew definately worked before, didn't work.
I was able to boot into fastboot following "this" thread but it doesn't perform commands.
When booting to Android I kept receiving notification that I had a pending update, I managed to wipe /data and /dalvik from adb shell, that resolved that issue.
Attempted to reflash stock KitKat again, but I can't, since phone doesn't have bootloader or recovery no more.
At least I still have working rooted 5.0.1 Lollipop, but have the other issues. I want to attempt to re-flash aboot.img, laf.img and sbl1.img to fix those issues but since its my main phone don't want to hard brick it right now.
Any input is welcome and appreciated, will keep reading a lot, think I might open a different thread for this.
Cheers.