Related
I'm going to be switching to a TMO unlimited plan and would like to move over my rooted G3, which is currently on 11C with the tethering hack, and would like to move with a more recent version. What's going to be the most straightforward way to get there? I'd like to have root on 46A for TB but that's about the only reason.
If I could simply unroot and take the OTA's that would be fine but my vague recollection is that it's not as simple as that. While the OTA method would be nice so I don't need to reload everything, going from scratch would be OK.
If you have TWRP installed, follow a ROM's directions to flash a 46A ROM. Update TWRP to the latest (either 2.8.7.0 or 3.0.0) first. Always make a backup first and store it somewhere that won't be affected by a factory reset or stock flash of TOT or KDZ (in other words, on your MicroSD card).
Just in case you're not aware, the built-in LG Backup (Settings / Backup) works really fast and I've been using it instead of TB for restoring user apps and data.
I was thinking of using the stock ROM listed here but it talks about installing a 35B bootstack first as does the Azadi ROM.
I've already upgraded to TWRP 2.8.7.0 so that's done as is the LG Backup. So do I then need to flash the 35B bootstack and then the 46A ROM or is there a "complete" 46A that can be installed from scratch? I've poked around and everything basically says I'll need to be on the 35B bootstack before going to 46A.
tgmorris said:
So do I then need to flash the 35B bootstack and then the 46A ROM
Click to expand...
Click to collapse
Yes.
Success - sort of.
I did 35B & 46A from TWRP and rebooted but ran into com.android.phone has stopped errors. Seemed like the simplest solution was a factory reset, which did cure it. However now I've lost root so I need to investigate how to get that back on 46A
Thanks for the help as at least I'm now current.
tgmorris said:
Success - sort of.
I did 35B & 46A from TWRP and rebooted but ran into com.android.phone has stopped errors. Seemed like the simplest solution was a factory reset, which did cure it. However now I've lost root so I need to investigate how to get that back on 46A
Thanks for the help as at least I'm now current.
Click to expand...
Click to collapse
You're welcome, glad you've had some success. You could try flashing the latest beta (made for Marshmallow) SuperSU.zip (v2.67?), or dirty flashing the ROM.
roirraW "edor" ehT said:
You're welcome, glad you've had some success. You could try flashing the latest beta (made for Marshmallow) SuperSU.zip (v2.67?), or dirty flashing the ROM.
Click to expand...
Click to collapse
That worked after manually booting into recovery and hoping to get to TWRP.
Once there I flashed v2.6.7 and seem like I'm good to go. Now just need to set things upo the way I was.
Really appreciate all the fast help.
tgmorris said:
That worked after manually booting into recovery and hoping to get to TWRP.
Once there I flashed v2.6.7 and seem like I'm good to go. Now just need to set things upo the way I was.
Really appreciate all the fast help.
Click to expand...
Click to collapse
You're welcome!
I just found out Verizon released Marshmallow for the G3 not too long ago so I thought I might switch back over to my old G3. Before doing so, I wanted to update the phone first and see how I like it. OTA update(on wifi) didn't find any new updates so I used the software upgrade assistant. The upgrade assistant found new updates and updated my phone to what I thought would be Marshmallow. To my surprise, it updated to Lollipop 5.1.1. I figured it must have to upgrade to Lollipop first, so I went back into the upgrade assistant and it says my phones up-to-date. Same goes for the OTA update.
It's been a couple hours now and my phones still not seeing any Marshmallow update. Does my phone have to have a sim card and be active in order to update to Marshmallow? What would cause me not to be able to update to Marshmallow?
Do you have an activated Verizon SIM in? Sometimes it can take days for the OTA to show up after restoring to stock.
roirraW "edor" ehT said:
Do you have an activated Verizon SIM in? Sometimes it can take days for the OTA to show up after restoring to stock.
Click to expand...
Click to collapse
No, I do not have a sim in. My current Verizon phone uses a nano sim so unfortunately, I can't just swap them out. I wanted to see how I liked Marshmallow before getting a new sim. However, I was able to upgrade to lollipop without a sim.
Designer17 said:
No, I do not have a sim in. My current Verizon phone uses a nano sim so unfortunately, I can't just swap them out. I wanted to see how I liked Marshmallow before getting a new sim. However, I was able to upgrade to lollipop without a sim.
Click to expand...
Click to collapse
The computer software doesn't require a SIM, but as you discovered, they haven't released the 46A Marshmallow KDZ yet, which is why it only took you to 35B 5.1.1 since all the software does is download the latest released KDZ and flash it.
For OTAs on the phone itself, it does require an activated Verizon SIM for it to even recognize that there's an OTA available. I know there are adapters to change SIM sizes, but I've never had to use one.
If you root and put TWRP on (second link in my signature below), you can flash @xdabbeb 's completely stock 46A ROM in the Development section.
roirraW "edor" ehT said:
The computer software doesn't require a SIM, but as you discovered, they haven't released the 46A Marshmallow KDZ yet, which is why it only took you to 35B 5.1.1 since all the software does is download the latest released KDZ and flash it.
For OTAs on the phone itself, it does require an activated Verizon SIM for it to even recognize that there's an OTA available. I know there are adapters to change SIM sizes, but I've never had to use one.
If you root and put TWRP on (second link in my signature below), you can flash @xdabbeb 's completely stock 46A ROM in the Development section.
Click to expand...
Click to collapse
Thanks for clearing that up. Maybe I will flash adabbeb's rom instead of waiting for Verizon to release the KDZ.
Designer17 said:
Thanks for clearing that up. Maybe I will flash adabbeb's rom instead of waiting for Verizon to release the KDZ.
Click to expand...
Click to collapse
You're welcome! Yeah, Verizon/LG are taking an extraordinarily long time to release this one. Complicating matters is that they changed things so that an old pattern of URL we were able to use in the past to check for the KDZ no longer works.
I was restoring my phone to a JasmineROM 9.1 TWRP backup to check a few times every day with the official computer software to see when it would start downloading the 46A KDZ but I've given up checking - it was a lot of backing up and restoring - someone else probably would find the news sooner anyway.
roirraW "edor" ehT said:
You're welcome! Yeah, Verizon/LG are taking an extraordinarily long time to release this one. Complicating matters is that they changed things so that an old pattern of URL we were able to use in the past to check for the KDZ no longer works.
I was restoring my phone to a JasmineROM 9.1 TWRP backup to check a few times every day with the official computer software to see when it would start downloading the 46A KDZ but I've given up checking - it was a lot of backing up and restoring - someone else probably would find the news sooner anyway.
Click to expand...
Click to collapse
I know all about Verizon taking forever to release updates. My current phone, Sony Xperia Z3v, just got Lollipop a couple weeks ago. It's been nearly 2yrs since Verizon promised it would get Lollipop. I was quite shocked when I found out Marshmallow was already available for the G3.
Designer17 said:
I know all about Verizon taking forever to release updates. My current phone, Sony Xperia Z3v, just got Lollipop a couple weeks ago. It's been nearly 2yrs since Verizon promised it would get Lollipop. I was quite shocked when I found out Marshmallow was already available for the G3.
Click to expand...
Click to collapse
Wow, that is a LONG time!
We were all quite surprised when 46A released so quickly. Even before it was official, there were a few helpful people who got the OTA I think it was a couple of weeks or maybe even a month before anyone else, and with our help, they imaged the 46A partitions for us. Since we haven't had the KDZ available to extract, that's what the 46A-based ROMs are using. @xdabbeb and I compared all the files/partitions from the "leak" and the official OTA and they're identical, however, so no danger the ROMs are any different than the official besides that the rooted ROMs *have* to use the 35B modem because the 46A modem requires the 46A sbl1 partition, and the 46A sbl1 in combination with the 12B aboot (bootloader) which we require to be able to get into TWRP put the phone into QHSUSB_BULK mode. @xdabbeb tried modifying files to get the 46A modem and sbl1 to work with the 12B aboot, but no luck.
I remember when at least one user (I don't remember who) on here was insistent that we wouldn't get 5.1.1 and when the earliest reports of the OTA occurred, they thought it was fake. I was cautiously optimistic. Very grateful that we got 35B. If we never get another OTA to hopefully fix just the few quirks with 46A, I'd probably restore back to @xdabbeb 's VS985 v2.0 based on 35B as it's overall the cat's meow in my opinion. It gives me that warm, fuzzy feeling of knowing just how professional a job he did with it. I do admittedly find it hard to move "backwards" though, knowing there's a more recent stock ROM.
roirraW "edor" ehT said:
The computer software doesn't require a SIM, but as you discovered, they haven't released the 46A Marshmallow KDZ yet, which is why it only took you to 35B 5.1.1 since all the software does is download the latest released KDZ and flash it.
For OTAs on the phone itself, it does require an activated Verizon SIM for it to even recognize that there's an OTA available. I know there are adapters to change SIM sizes, but I've never had to use one.
If you root and put TWRP on (second link in my signature below), you can flash @xdabbeb 's completely stock 46A ROM in the Development section.
Click to expand...
Click to collapse
Were is this completely stock Marshmallow Rom located.All the ones I've found have been modified in someway.
AtrixHDMan said:
Were is this completely stock Marshmallow Rom located.All the ones I've found have been modified in someway.
Click to expand...
Click to collapse
In the Development section, the one that says 46A firmware, thread by @xdabbeb. That's as close to 100% stock rooted you can be while still being able to get into TWRP.
There's only one other stock 46A-based ROM in the Development section.
roirraW "edor" ehT said:
In the Development section, the one that says 46A firmware, thread by @xdabbeb. That's as close to 100% stock rooted you can be while still being able to get into TWRP.
There's only one other stock 46A-based ROM in the Development section.
Click to expand...
Click to collapse
Oh ok. I saw that.I'm guessing since I'm on 12B rooted I can just install TWRP and that 46A Rom and keep root and TWRP installed.Is that correct.If so I'm going to proceed but not if exposed can't be installed or since I already have exposed install will it still be after update to Marshmallow?
AtrixHDMan said:
Oh ok. I saw that.I'm guessing since I'm on 12B rooted I can just install TWRP and that 46A Rom and keep root and TWRP installed.Is that correct.
Click to expand...
Click to collapse
As @xdabbeb says and links to in the first post of that thread, you have to be on the 35B bootstack, so flash the 35B bootstack before flashing that ROM.
Before you flash any ROM, in TWRP you select to wipe Cache, Dalvik/ART and Data. I wipe System as well.
Otherwise yes. You can, if you wish, use the built in LG Backup to backup your user apps and user data, and limited system data.
If so I'm going to proceed but not if exposed can't be installed or since I already have exposed install will it still be after update to Marshmallow?
Click to expand...
Click to collapse
When you flash a ROM, it overwrites your old one, which includes overwriting Xposed or any other system modifications because when you flash Xposed or other system mods, it installs to the same place the ROM is. Xposed for Marshmallow works fine for me.
roirraW "edor" ehT said:
As @xdabbeb says and links to in the first post of that thread, you have to be on the 35B bootstack, so flash the 35B bootstack before flashing that ROM.
Before you flash any ROM, in TWRP you select to wipe Cache, Dalvik/ART and Data. I wipe System as well.
Otherwise yes. You can, if you wish, use the built in LG Backup to backup your user apps and user data, and limited system data.
When you flash a ROM, it overwrites your old one, which includes overwriting Xposed or any other system modifications because when you flash Xposed or other system mods, it installs to the same place the ROM is. Xposed for Marshmallow works fine for me.
Click to expand...
Click to collapse
I'm still a little confused about how to install this.I'm on 12B and it sounds like I need to be on 35B before I can flash this 46A Rom.So do I need to install TWRP and 35B Rom first or can I go from 12B Rom to 46A Rom but I will need to flash 35B bootstack to go from 12B to 46A.
AtrixHDMan said:
I'm still a little confused about how to install this.I'm on 12B and it sounds like I need to be on 35B before I can flash this 46A Rom.So do I need to install TWRP and 35B Rom first
Click to expand...
Click to collapse
No.
or can I go from 12B Rom to 46A Rom but I will need to flash 35B bootstack to go from 12B to 46A.
Click to expand...
Click to collapse
Yes.
Install TWRP using TWRP Manager. Like I said in the other thread, don't "kill" me if I'm wrong but I believe that 12B was the last version that you could simply use TWRP Manager to install TWRP - after 12B it's not that simple. So what I'm saying is, be prepared, have everything backed up if you care about it, moved to your external storage in case you need to flash a KDZ to restore to stock, etc.
Follow the link in @xdabbeb 's 46A thread and download the 35B bootstack and the 46A ROM. If you wish you can download debloat zips that I provided in the third post of that thread.
Use an app like Quick Boot in the Play Store to reboot to TWRP Recovery, or with the phone off, press and hold the Down Volume button and while keeping it pressed, also press and hold the Power button. When you see it load a stock-looking recovery with white background, let go of both buttons right away. If you hold the power button for too long, it'll turn off or reboot. Then select Wipe Cache from the stock-looking recovery to manually go into TWRP. You can also press Factory Reset to get to TWRP but since I'm not positive if using TWRP Manager on 12B is fine, just use the Wipe Cache option. I know for a fact TWRP Manager is just fine on 10B because 10B is what I always root and install TWRP on.
From TWRP, wipe Cache and Dalvik/ART, and Data.
Again from TWRP, flash the 35B bootstack you downloaded.
Once more from TWRP, flash the 46A ROM you downloaded.
If you so wish you can flash any debloat zips.
Reboot.
roirraW "edor" ehT said:
No.
Yes.
Install TWRP using TWRP Manager. Like I said in the other thread, don't "kill" me if I'm wrong but I believe that 12B was the last version that you could simply use TWRP Manager to install TWRP - after 12B it's not that simple. So what I'm saying is, be prepared, have everything backed up if you care about it, moved to your external storage in case you need to flash a KDZ to restore to stock, etc.
Follow the link in @xdabbeb 's 46A thread and download the 35B bootstack and the 46A ROM. If you wish you can download debloat zips that I provided in the third post of that thread.
Use an app like Quick Boot in the Play Store to reboot to TWRP Recovery, or with the phone off, press and hold the Down Volume button and while keeping it pressed, also press and hold the Power button. When you see it load a stock-looking recovery with white background, let go of both buttons right away. If you hold the power button for too long, it'll turn off or reboot. Then select Wipe Cache from the stock-looking recovery to manually go into TWRP. You can also press Factory Reset to get to TWRP but since I'm not positive if using TWRP Manager on 12B is fine, just use the Wipe Cache option. I know for a fact TWRP Manager is just fine on 10B because 10B is what I always root and install TWRP on.
From TWRP, wipe Cache and Dalvik/ART, and Data.
Again from TWRP, flash the 35B bootstack you downloaded.
Once more from TWRP, flash the 46A ROM you downloaded.
If you so wish you can flash any debloat zips.
Reboot.
Click to expand...
Click to collapse
Just making sure root will hold and get TWRP from Play Store?
AtrixHDMan said:
Just making sure root will hold
Click to expand...
Click to collapse
Answered in the first post of @xdabbeb 's thread for his 46A ROM.
and get TWRP from Play Store?
Click to expand...
Click to collapse
I answered that in the other thread.
roirraW "edor" ehT said:
Answered in the first post of @xdabbeb 's thread for his 46A ROM.
I answered that in the other thread.
Click to expand...
Click to collapse
I`ve updated and my phone is not rooted.Tried a few apps that require root and it is not rooted.How to fix?
AtrixHDMan said:
I`ve updated and my phone is not rooted.Tried a few apps that require root and it is not rooted.How to fix?
Click to expand...
Click to collapse
Try dirty flashing the ROM? @xdabbeb 's 46A ROM is pre-rooted. Had you wiped anything AFTER flashing the ROM?
You could download the SuperSU.zip off of @Chainfire 's website and flash it in TWRP. It would have to be the same version @xdabbeb used on his ROM, though - I think 2.67.
I haven't had this problem when flashing his ROM so I don't know what else to suggest.
roirraW "edor" ehT said:
Try dirty flashing the ROM? @xdabbeb 's 46A ROM is pre-rooted. Had you wiped anything AFTER flashing the ROM?
You could download the SuperSU.zip off of @Chainfire 's website and flash it in TWRP. It would have to be the same version @xdabbeb used on his ROM, though - I think 2.67.
I haven't had this problem when flashing his ROM so I don't know what else to suggest.
Click to expand...
Click to collapse
I got it to work,but I`m having several problems with this rom.Like very slow charging.weather not working,brightness not working,and if you shut phone off and try to boot back up it buzzes but no boot up.Have to pull battery out in order to boot up.
AtrixHDMan said:
I got it to work,but I`m having several problems with this rom.Like very slow charging.weather not working,brightness not working,and if you shut phone off and try to boot back up it buzzes but no boot up.Have to pull battery out in order to boot up.
Click to expand...
Click to collapse
I don't have those problems. Maybe you should post in the ROM thread to see if anyone else who's running that ROM has those problems or suggestions.
Had you wiped Cache, Dalvik/ART and Data before flashing the ROM?
Hey everyone, I have a verizon g3 with firmware version 47a. I'm hell bent on rooting it and it's hell bent on stopping me at any cost XD So the problem is, I'm trying to flash the 10b kdz file, and when I load up the tool and start the flash, it gets the bar to 100% and then gives me an error that says can't connect to server. After that, I just click OK and watch my phone for activity, and there is none. The firmware update bar on my phone remains on 0%. Any solutions would be very much appreciated.
Thanks in advance.
*IF* you're not rooted/haven't flashed one of @xdabbeb 's Bootstacks, then you can't flash anything older than the 35B KDZ from (stock unrooted) 35B or higher. You have to use the 10B TOT along with the .DLL that's extracted from the 35B KDZ. You can find both in my Android File Host section linked to at the bottom of @annoyingduck 's stickied return to stock thread in the General section, also linked to in my signature below.
Regarding no connection to server, read the second or third post of the thread I reference above. But as I said above, if you're coming from 100% stock unrooted 47A, you have to use the TOT method to downgrade to the easily rootable 10B, where you can then use the Stump app on XDA to root it using the brute force option, and then use TWRP Manager from the Play Store to put on TWRP. Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B.
roirraW "edor" ehT said:
*IF* you're not rooted/haven't flashed one of @xdabbeb 's Bootstacks, then you can't flash anything older than the 35B KDZ from (stock unrooted) 35B or higher. You have to use the 10B TOT along with the .DLL that's extracted from the 35B KDZ. You can find both in my Android File Host section linked to at the bottom of @annoyingduck 's stickied return to stock thread in the General section, also linked to in my signature below.
Regarding no connection to server, read the second or third post of the thread I reference above. But as I said above, if you're coming from 100% stock unrooted 47A, you have to use the TOT method to downgrade to the easily rootable 10B, where you can then use the Stump app on XDA to root it using the brute force option, and then use TWRP Manager from the Play Store to put on TWRP. Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B.
Click to expand...
Click to collapse
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
andr0id187 said:
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
Click to expand...
Click to collapse
Are you clicking on analyze phone? You don't need to do that. And I know in the past that has messed me up.
Sent from my One M8 using XDA Labs
andr0id187 said:
Hey, thanks so much for the help and reply. So I followed everything you said and everything in the guide, and i still have a small problem. When I start the flash, it's fine. It detects the phone and "analyzes phone setting". Then, it gets to the software extraction part, and **** hits the fanXD. Basically, the connection to server lost window pops up, and the original window states "Upgrade stopped due to an error". And of course, my phone has no activity, the firmware update bar is still on 0%. What gives??
Click to expand...
Click to collapse
You're welcome!
Did you wait 5-10 minutes since the connection to server dialog is normal? Commonly if you wait 5-10 minutes and not have touched any buttons in any dialogs in the software that pop up, you'll find the phone is flashed.
Can you confirm since you haven't said - are you 100% stock unrooted or rooted and have previously flashed one of @xdabbeb 's Bootstacks? Like I said, if you're 100% stock unrooted, you have to use the TOT method, not KDZs. TOT uses a different tool. Just Google for it. "TOT Method"
If waiting 5-10 minutes doesn't help, try the TOT method. It's better overall anyway, even if it's less user friendly (except that LG Flash Tool 2014 throws up bogus error dialogs).
---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------
jurington said:
Are you clicking on analyze phone? You don't need to do that. And I know in the past that has messed me up.
Click to expand...
Click to collapse
^^^^^^^^^^ yep, definitely, what @jurington said.
roirraW "edor" ehT said:
You're welcome!
Did you wait 5-10 minutes since the connection to server dialog is normal? Commonly if you wait 5-10 minutes and not have touched any buttons in any dialogs in the software that pop up, you'll find the phone is flashed.
Can you confirm since you haven't said - are you 100% stock unrooted or rooted and have previously flashed one of @xdabbeb 's Bootstacks? Like I said, if you're 100% stock unrooted, you have to use the TOT method, not KDZs. TOT uses a different tool. Just Google for it. "TOT Method"
If waiting 5-10 minutes doesn't help, try the TOT method. It's better overall anyway, even if it's less user friendly (except that LG Flash Tool 2014 throws up bogus error dialogs).
---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------
^^^^^^^^^^ yep, definitely, what @jurington said.
Click to expand...
Click to collapse
Goddamit you're right, I'm stupid, I didn't read that I AM on stock, unrooted so I'm going to have to use TOT. So will the file remain the same? vs98510b?
andr0id187 said:
Goddamit you're right, I'm stupid, I didn't read that I AM on stock, unrooted so I'm going to have to use TOT. So will the file remain the same? vs98510b?
Click to expand...
Click to collapse
I'm not clear on your question. It's a 10B TOT (and the .DLL I mentioned previously) instead of the 10B KDZ, so it's a different file.
roirraW "edor" ehT said:
I'm not clear on your question. It's a 10B TOT (and the .DLL I mentioned previously) instead of the 10B KDZ, so it's a different file.
Click to expand...
Click to collapse
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
andr0id187 said:
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
Click to expand...
Click to collapse
Did you flash xdabbebs 47A rom? Also did you did you do any wipes in twrp before you flashed the rom? And what version of twrp do you have?
Sent from my One M8 using XDA Labs
andr0id187 said:
Ok, so I flashed the 10b tot, rooted it with stump, installed SuperSU and TWRP. Then, according to this article: http://androiding.how/root-verizon-g3-47a-marshmallow-firmware/
I'm supposed to flash the 35b bootstack which I also did successfully. Then, I can flash back to 47a and keep the root. Only problem is, after installing the bootstack, when I try to flash 47a, it's not rooted, and gives me a "con.android.phone has stopped working" error. I think this might have something to do with the fact that in the article, it says NOT to let TWRP install SuperSU when flashing 47a. When i flash it, it gives me no option to accept or deny the installation of Super SU. Is this the problem? Or is it something else entirely? Thanks again.
Click to expand...
Click to collapse
I'd wipe Cache, Dalvik /ART and Data and reflash @xdabbeb 's VS985 stock 47A firmware.
TWRP v3.0.0 is systemless root (or at least Marshmallow) aware so doesn't offer to flash SuperSU.
2.8.7.0 isn't aware and asks since it won't be able to find SuperSU where it looks.
If you do wipes after flashing the ROM, it's common to lose root. Just reflash the ROM.
Also optional debloat zips in post three of his ROM thread.
Ok so first of all, yes I have the xdadev 47a rom, yes I did a wipe in twrp, is that bad? And I have twrp 3.0.0.0(latest?) If you need any more information please ask, I'm really hoping to solve this problem. Thanks
andr0id187 said:
Ok so first of all, yes I have the xdadev 47a rom, yes I did a wipe in twrp, is that bad? And I have twrp 3.0.0.0(latest?) If you need any more information please ask, I'm really hoping to solve this problem. Thanks
Click to expand...
Click to collapse
No, you're supposed to wipe in TWRP, he was just covering all bases. Did you re-flash the ROM?
You can also/instead potentially flash the latest SuperSU.zip from @Chainfire 's website.
roirraW "edor" ehT said:
No, you're supposed to wipe in TWRP, he was just covering all bases. Did you re-flash the ROM?
You can also/instead potentially flash the latest SuperSU.zip from @Chainfire 's website.
Click to expand...
Click to collapse
so whats happening is, every time after i flash the xdadev 47a rom(i dont wipe mind you, i just reboot), it's giving me the com.android.phone has stopped error and no root. I really don't understand why
andr0id187 said:
so whats happening is, every time after i flash the xdadev 47a rom(i dont wipe mind you, i just reboot), it's giving me the com.android.phone has stopped error and no root. I really don't understand why
Click to expand...
Click to collapse
Check the ROM zip MD5 hash? I assume you're meaning you don't wipe after. Did you try wiping again before flashing it?
roirraW "edor" ehT said:
Check the ROM zip MD5 hash? I assume you're meaning you don't wipe after. Did you try wiping again before flashing it?
Click to expand...
Click to collapse
yes i've tried wiping before flashing and it still gives me the error, I'm currently wiping after flash to see what happens, hopefully i dont lose root
andr0id187 said:
yes i've tried wiping before flashing and it still gives me the error, I'm currently wiping after flash to see what happens, hopefully i dont lose root
Click to expand...
Click to collapse
That's not going to make a difference but you will likely not be rooted. You'll still have TWRP though.
roirraW "edor" ehT said:
That's not going to make a difference but you will likely not be rooted. You'll still have TWRP though.
Click to expand...
Click to collapse
so how do i go from 10b to 47a and keep root?
andr0id187 said:
so how do i go from 10b to 47a and keep root?
Click to expand...
Click to collapse
The only way I know is what we've already discussed and what you already did. Did you check the ROM zip MD5 hash? I've flashed my (and my wife's) G3's many times with these files when I was doing tests and haven't had this problem. I'm perplexed as well but if you should check the MD5 hash to eliminate that as a problem. That said, you might need to reflash the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that flashing KDZs and ROMs can't. I once had a weird issue that it didn't matter what KDZ or rooted ROM I flashed, the problem persisted. I don't recall the exact problem but it conceivably could've been the same as similar to yours. Once I flashed the 10B TOT, all was well and when discussing with @xdabbeb, that's when he educated me that TOTs have more partitions than KDZs. I'm a diehard TOT fan ever since (I preferred KDZ when possible previously).
I know you already flashed the TOT but we're running out of ideas. If the MD5 hash of the 47A ROM and 35B Bootstack match what they're supposed to (listed on the Android File Host download page for each file). Make sure and
You should also get in the habit of flashing the appropriate Bootstack every time you flash a ROM, or after every time you restore a TWRP backup. Even if you know you're already on the 35B Bootstack - mind you, I'm not meaning this as "snake oil" or as a solution to the trouble you're having, and flashing it more than once won't change anything, but I just wanted to make sure you know this since some ROM's (JasmineROM and SkyDragon) include a partial Bootstack and can cause a brick (so the Bootstack should be flashed after the ROM in their case), and TWRP Backups/Restores don't backup or restore the entire set of partitions including in the Bootstack, so if you happen to be on a ROM that you were using the 24B Bootstack with, and restore a TWRP Backup of a 35B or higher ROM, you might not have a signal.
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
@andr0id187 I also want to be completely clear since I read back and I don't think you specified. Sorry for the repetetiveness but when you wipe before flashing, you're wiping Cache, Dalvik /ART and Data correct?
roirraW "edor" ehT said:
The only way I know is what we've already discussed and what you already did. Did you check the ROM zip MD5 hash? I've flashed my (and my wife's) G3's many times with these files when I was doing tests and haven't had this problem. I'm perplexed as well but if you should check the MD5 hash to eliminate that as a problem. That said, you might need to reflash the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that flashing KDZs and ROMs can't. I once had a weird issue that it didn't matter what KDZ or rooted ROM I flashed, the problem persisted. I don't recall the exact problem but it conceivably could've been the same as similar to yours. Once I flashed the 10B TOT, all was well and when discussing with @xdabbeb, that's when he educated me that TOTs have more partitions than KDZs. I'm a diehard TOT fan ever since (I preferred KDZ when possible previously).
I know you already flashed the TOT but we're running out of ideas. If the MD5 hash of the 47A ROM and 35B Bootstack match what they're supposed to (listed on the Android File Host download page for each file). Make sure and
You should also get in the habit of flashing the appropriate Bootstack every time you flash a ROM, or after every time you restore a TWRP backup. Even if you know you're already on the 35B Bootstack - mind you, I'm not meaning this as "snake oil" or as a solution to the trouble you're having, and flashing it more than once won't change anything, but I just wanted to make sure you know this since some ROM's (JasmineROM and SkyDragon) include a partial Bootstack and can cause a brick (so the Bootstack should be flashed after the ROM in their case), and TWRP Backups/Restores don't backup or restore the entire set of partitions including in the Bootstack, so if you happen to be on a ROM that you were using the 24B Bootstack with, and restore a TWRP Backup of a 35B or higher ROM, you might not have a signal.
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
@andr0id187 I also want to be completely clear since I read back and I don't think you specified. Sorry for the repetetiveness but when you wipe before flashing, you're wiping Cache, Dalvik /ART and Data correct?
Click to expand...
Click to collapse
Yes, I'm doing the default TWRP wipe which includes all of the above(right?)
andr0id187 said:
Yes, I'm doing the default TWRP wipe which includes all of the above(right?)
Click to expand...
Click to collapse
No idea. As with backups it might default to what was chosen previously. I don't know what it defaults to on flash of TWRP from freshly rooted. I look at the list and make sure those three are checked everytime. Sometimes I wipe other things like internal storage or just Cache and Dalvik /ART so other times I want to make sure I have selected exactly what I want.
If I have Rooted 5.1.1 can I go to 6 via LGUP without loosing all my data or is it a total wipe situation?
I am ready to give up root, but to lazy to resetup my phone
whatsinaname said:
If I have Rooted 5.1.1 can I go to 6 via LGUP without loosing all my data or is it a total wipe situation?
I am ready to give up root, but to lazy to resetup my phone
Click to expand...
Click to collapse
Just like most ota upgrades. I'm sure you won't lose anything other than root. Although I'm not completely sure if 6.0 will even install unless you go back to an unrooted phone. All you can do is try.
Kickin' it on my VS990
You can do the upgrade in LGUP and not lose your data. However when I did it, it seemed most of my apps did not work and I ended up doing a reset... Also, many apps did not work after the LG restore from backup and I had to uninstall/reinstall them... So, I'd recommend doing a reset from tbe beginning...
Thanks for the input, I should just wipe it.... clean start is always nice.
I am not new to flashing but I think I am missing something.
I see that there is the new kdz file with Version v10i. Since I am on v10e, I would like to have the latest version on my device. But if I Flash the kdz, it will wipe everything, right?
With my Nexus, I was able to just flash the system partition, which would leave my data intact. Later, when I was on a custom rom, I had flashable zip files which would also only update the system partition.
My questions are:
Do I really have to backup everything, install the kdz and then restore everything?
Is there any way to just update the system partition or do I have to wait for a flashable zip or the OTA file?
You can use LG Up and update only which does what you are asking however, in my experience, this can often lead to future issues.
I always do a clean install and even if I update over ota, I perform a factory reset and subsequently I experience very few of issues that people report on here.
Sent from my LG-H850 using XDA-Developers mobile app
I'm in the same boat as you, want to update from V10e -> V10i but no luck with OTA or LG Bridge so tryed LG Flash tool but it doesent recognize my Phone ! YES LG FLASH TOOL WILL WIPE YOUR PHONE !
Go here and do what alexander did, i did it and it worked.
http://forum.xda-developers.com/showpost.php?p=69122610&postcount=229
bobsie41 said:
You can use LG Up and update only which does what you are asking however, in my experience, this can often lead to future issues.
I always do a clean install and even if I update over ota, I perform a factory reset and subsequently I experience very few of issues that people report on here.
Click to expand...
Click to collapse
Thank you. It worked perfectly. Since this update does not contain a new version of Android, I think updating the existing Android is not that bad. When Android 7 comes out, I will definitely start from zero.