My LG G3 seems to have died tonight.
See here: http://forum.xda-developers.com/verizon-lg-g3/help/phone-dying-t3347199
I really do like this phone so I ordered a cheap refurb replacement off ebay.
What's the process to go to from whatever it shipped with to xdabbeb's 47A version found here w/TWRP?
http://forum.xda-developers.com/showthread.php?t=3304365
Bump. Can't imagine it's that hard to get from new phone to 47A rooted with TWRP, but want to do it right the first time.
Does anyone have the steps I should follow?
Various ways are out there. A quick look through the forums will find you a solution to what you're looking for.
Here's a flashable stock firmware image that can be used:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
iBolski said:
Various ways are out there. A quick look through the forums will find you a solution to what you're looking for.
Here's a flashable stock firmware image that can be used:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
Click to expand...
Click to collapse
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
lexluthor said:
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
Click to expand...
Click to collapse
Again, there is a topic exactly for what you need in this specific forum:
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-manually-downgrade-partitions-t3326775
Hope that helps! I myself haven't done this as I'm fully satisfied being on stock 47A unrooted at this point. Once I can verify that the latest CM is pretty stable (which it appears to be but there are still a few nagging issues), I'll probably eventually go to that, but I want to wait and see if LG and VZW are done with updating this phone.
lexluthor said:
Yes, i see that thread, but i may have to go backwards, root and twrp before that, right?
Those are the steps I'm looking for.
Click to expand...
Click to collapse
Note that unless you truly can't, I always recommend the 10B TOT method with the .DLL from the 35B KDZ over the instructions in the thread that was linked. It works for me fine both times I've tested it but several people ended up having to TOT their phone after those instructions anyway.
Once you're on 10B, root with the Stump app then use TWRP Manager in the Play Store to flash TWRP.
roirraW "edor" ehT said:
Note that unless you truly can't, I always recommend the 10B TOT method with the .DLL from the 35B KDZ over the instructions in the thread that was linked. It works for me fine both times I've tested it but several people ended up having to TOT their phone after those instructions anyway.
Once you're on 10B, root with the Stump app then use TWRP Manager in the Play Store to flash TWRP.
Click to expand...
Click to collapse
The .tot does seem easier than the instructions in the other thread. At least, that's if no complications with getting Windows set up to do the .tot right.
So if the phone comes and it's 35B or higher, TOT to 10B w/35B DLL (where's the correct .35B DLL, I wasn't sure exactly which file to use?), stump root, install TWRP Manager from play store and flash TWRP, reboot to TWRP, flash 35B bootstack, flash xdabbeb's 47A. Done? I'll then still have TWRP, be rooted and be on 47A, right?
If the phone comes lower than 35B, can I just .kdz to 10B and then do the same?
lexluthor said:
The .tot does seem easier than the instructions in the other thread. At least, that's if no complications with getting Windows set up to do the .tot right.
So if the phone comes and it's 35B or higher, TOT to 10B w/35B DLL (where's the correct .35B DLL, I wasn't sure exactly which file to use?),
Click to expand...
Click to collapse
My Android File host link at the bottom of the first post of the other thread by @annoyingduck has both the 10B_3 TOT (don't accidentally get the 10B_01 KDZ) and the 35B .DLL you need.
stump root, install TWRP Manager from play store and flash TWRP, reboot to TWRP, flash 35B bootstack, flash xdabbeb's 47A. Done? I'll then still have TWRP, be rooted and be on 47A, right?
Click to expand...
Click to collapse
Correct.
If the phone comes lower than 35B, can I just .kdz to 10B and then do the same?
Click to expand...
Click to collapse
Yes.
47a kdz just came out as another easy option if you want stock
Sent from my VS985 4G using Tapatalk
gspinelli said:
47a kdz just came out as another easy option if you want stock
Click to expand...
Click to collapse
Can that be rooted though? Do I still go back to 10b, stump root, installed TWRP and then kdz to 47a?
If I'm going to do that, I'm probably just better off using xdabbeb's 47a. I've been happy with his 46a.
Or can I just go from whatever version my phone comes with, kdz to 47a and then root there using ?? (kingroot)? Then I'll be on 47a stock/rooted, but no TWRP? That may suffice for my needs. I like that xdabbeb's 46a had systemless root and I was able to get android pay working.
lexluthor said:
Can that be rooted though? Do I still go back to 10b, stump root, installed TWRP and then kdz to 47a?
If I'm going to do that, I'm probably just better off using xdabbeb's 47a. I've been happy with his 46a.
Or can I just go from whatever version my phone comes with, kdz to 47a and then root there using ?? (kingroot)? Then I'll be on 47a stock/rooted, but no TWRP? That may suffice for my needs. I like that xdabbeb's 46a had systemless root and I was able to get android pay working.
Click to expand...
Click to collapse
When you flash a KDZ, even with LG Flash Tool 2014's "Normal" option versus "CSE", it overwrites everything currently installed: System (your ROM), Modem, Bootloader, Kernel, Recovery and other partitions. "Normal" mode enables keeping user apps and user and system data, although doing that works best when only "upgrading" from perhaps the previous official release.
In other words, if you're going to root and install TWRP, flashing a KDZ would just undo all that so yes, absolutely, it would be easier/better to just flash @xdabbeb 's stock 47A ROM.
You can temporarily root 47A with Kingroot. You have to re-root whenever you reboot, and Kingroot is very invasive. You don't want to use Kingroot. The only times I recommend it is as a temporary solution, as for my alternate way of installing TWRP which you're already aware of.
Flashing newer KDZs is more for those people who want to stay 100% stock unrooted, especially for those who don't actually use Verizon so they don't receive OTAs.
roirraW "edor" ehT said:
When you flash a KDZ, even with LG Flash Tool 2014's "Normal" option versus "CSE", it overwrites everything currently installed: System (your ROM), Modem, Bootloader, Kernel, Recovery and other partitions. "Normal" mode enables keeping user apps and user and system data, although doing that works best when only "upgrading" from perhaps the previous official release.
In other words, if you're going to root and install TWRP, flashing a KDZ would just undo all that so yes, absolutely, it would be easier/better to just flash @xdabbeb 's stock 47A ROM.
Click to expand...
Click to collapse
Yes xdabbab's 47A is the way to go for me.
Just got the new phone and its on 35B. I'm trying to TOT to 10B with the 35B DLL. I did the COM41 in device manager. I've got the phone in download mode. I'm running the LG Flash tool as admin in Windows 10. I load the 2 files and click the start arrow. It goes through some things where it says BIN CRC check or something like than and then it just sits and says READY!! in yellow, but nothing ever happens.
Am I doing something wrong?
EDIT: Unlplugged USB and plugged it back in and it's going now. Stand by, could maybe use some more help getting through this
Optimizing apps on 47A (hopefully). I'm sure finding my Titanium folder on the external drive will be a pain as always, but hopefully smooth sailing from there.
The process worked great. East to TOT, install stump root, then TWRP and then flashed 35b bootstack and 47a xdabbeb with some wiping data/caches in between.
Titanium took a good few hours to restore my 300+ apps. I don't know why that took so long. There's probably a better way, but even though Titanium always takes long, it's easy to automatic backups during the week and it usually gets my apps back to a nice spot.
Back up and running on my replacement phone today. The ebay listing said it was B+ condition. Screen is in great shape, some scraping on the sides, but I don't care about that. I used my back cover that I had put an NFC sticker on when I got the original phone. All working great so far.
Thanks for the help here.
Thanks!
David
lexluthor said:
Titanium took a good few hours to restore my 300+ apps. I don't know why that took so long. There's probably a better way, but even though Titanium always takes long, it's easy to automatic backups during the week and it usually gets my apps back to a nice spot.
Thanks for the help here.
Thanks!
David
Click to expand...
Click to collapse
Were you charging at the same time as restoring backups? Maybe it was throttling down due to heat.
Yeah, for me since Lollipop, even with Mount Space Separation disabled (and then phone rebooted), besides TB taking a long time it also would get hung up on restoring an app occasionally. I'd have to reboot and then resume restoring, and any that it would get hung up on I'd skip until after. Then I was able to restore those one by one and then TB handled them fine.
I've been using the built in LG Backup since 12B and it's fast. It has a couple quirks such as I find it resets my keyboard to stock when backing up, may have killed other things that I normally had running in the background, but I don't recall for sure.
When restoring I have a pet peeve that it forces the screen to stay on during the process, even once it finishes and is waiting for you to select the button to reboot.
Taking OTAs manages to let you know it's successful after it automatically reboots, why can't they have LG Backup do the same?
Still, overall, I prefer it for speed and reliability/stability, but TB is still a must have tool.
You're welcome!
roirraW "edor" ehT said:
Were you charging at the same time as restoring backups? Maybe it was throttling down due to heat.
Yeah, for me since Lollipop, even with Mount Space Separation disabled (and then phone rebooted), besides TB taking a long time it also would get hung up on restoring an app occasionally. I'd have to reboot and then resume restoring, and any that it would get hung up on I'd skip until after. Then I was able to restore those one by one and then TB handled them fine.
I've been using the built in LG Backup since 12B and it's fast. It has a couple quirks such as I find it resets my keyboard to stock when backing up, may have killed other things that I normally had running in the background, but I don't recall for sure.
When restoring I have a pet peeve that it forces the screen to stay on during the process, even once it finishes and is waiting for you to select the button to reboot.
Taking OTAs manages to let you know it's successful after it automatically reboots, why can't they have LG Backup do the same?
Still, overall, I prefer it for speed and reliability/stability, but TB is still a must have tool.
You're welcome!
Click to expand...
Click to collapse
I've never gotten LG Backup to work right for me. Never seems to restore nearly everything or get errors when backing up. Not worth looking into it more as I don't start fresh much.
I was using the phone much of the time TiBU was working, so that didn't help, but still slow going even if I plugged it in and let it sit. It missed about 30 apps the first time around that I did in a 2nd pass. Didn't get hung too much in the main batch, at least. And if It does hang, no need to reboot. Just FC TiBU and then start it back up and leave the hung app off to do as a one by at the end.
I did just discover a strange problem with the new phone. I can't restart it. If I try to restart it goes blank after a bit and a battery pull is needed to get it back on. I can power off, let it go off and power on, that works fine. Only fails when I do it as a restart.
Any ideas?
lexluthor said:
I did just discover a strange problem with the new phone. I can't restart it. If I try to restart it goes blank after a bit and a battery pull is needed to get it back on. I can power off, let it go off and power on, that works fine. Only fails when I do it as a restart.
Any ideas?
Click to expand...
Click to collapse
It's a common problem on this phone. There's no particular known reason why it happens, nor any solution - there's only been a ton of speculation without any strong evidence other than a thread I had made about this subject, during which I made a detailed test of rebooting the phone about 140 times under different circumstances (10 times in a row in each specific circumstance). I'm fairly certain I would have to at minimum do about 1500 more reboots in various circumstances to only possibly get closer to narrowing down the problem.
Some people will tell you they think it's caused by a particular (35B) bootstack. I don't believe it because I had 70 reboots in a row while on the 35B bootstack without having the problem during part of my testing.
I also have had the problem before 35B even came out. I haven't had the problem happen at all in the past couple of months - since the last time I had TOT'd back to 10B (and I've done various KDZ flashes since then when testing things for myself and for others).
Rebooting
I noticed the reboot problem started after I installed a 64GB memory card. Without the additional memory card...rebooting works normally. With it inserted, a battery pull is needed 2x out of 5 to bring the phone back from limbo. I'm on Jasmine 9.1
Circlesqr said:
I noticed the reboot problem started after I installed a 64GB memory card. Without the additional memory card...rebooting works normally. With it inserted, a battery pull is needed 2x out of 5 to bring the phone back from limbo.
Click to expand...
Click to collapse
Definitely not my issue. My phone was rebooting in download mode without even a SIM or memory card installed.
Related
I've tried searching and reading through the various downgrade and upgrade available threads, but can't seem to find anything concrete on the matter. Has anyone confirmed that rollback has OR has not been blocked in the latest OTA - 12B? I'm assuming the tot method wouldn't work since it didn't work with 11C, so I'm most specifically wondering about the kdz method. I'm trying to figure this out for a friend. Thanks!
ohlin5 said:
I've tried searching and reading through the various downgrade and upgrade available threads, but can't seem to find anything concrete on the matter. Has anyone confirmed that rollback has OR has not been blocked in the latest OTA - 12B? I'm assuming the tot method wouldn't work since it didn't work with 11C, so I'm most specifically wondering about the kdz method. I'm trying to figure this out for a friend. Thanks!
Click to expand...
Click to collapse
This topic is of interest to me as I started on 10B and never took any OTA. I rooted, bump'd and started running Beanstown 11C, Cyanogenmod 11, BlissPop 5.0.1 and now SkyDragon 2.0.0. I have seen some report that the .tot method has been met with mixed success for people that took the 11C update but I haven't seen any details. Does the LG Flash Tool have issues laying down the base 10B image when it sees 11C? I would guess if that is the case, the same would be for 12B. Has anyone tried formatting with TWRP etc.?
I have never done the LG Flash Tool with .tot but was always keeping it in my toolbox for when the official Lollipop 5.0.x build comes from Verizon. I would be interested to see why the .tot method fails or the KDZ method for that matter.
Don't know about 12b (but I think someone else did reply to this question in another forum and stated that yes, you can downgrade back to 10b), but this post says downgrading from 11c possible:
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
iBolski said:
Don't know about 12b (but I think someone else did reply to this question in another forum and stated that yes, you can downgrade back to 10b), but this post says downgrading from 11c possible:
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Click to expand...
Click to collapse
Yep, I know all about that. I've tot restored 10B a couple different times, and kdz'ed an 11C install back to 10B once, so I'm very familiar with both of those. I'm really curious to know though specifically if anyone has been able to confirm if 12B can be kdz'ed (or tot'ed for that matter, but I doubt it), back to 10B. If a new phone is bought in the next few weeks an comes out of the box with 12B flashed, I need to know whether this I would be stuck as unrootable/unlockable for the time being.
done.
I did it. Was curious about Advanced Calling so I downgraded since I forgot to make a backup of stock recovery. Got back to stock with no root and no custom recovery. Then I took the OTA updates to 12B. Found out I could not root from there and crossed my fingers and downgraded again. Had a moment of panic as the first attempt failed. Instead of getting a success msg on my computer and a big red number 3 on my phone I had a big red number 2. Restarted the process again and this time it took it. Rooted first this time, then took the updates. Not really interested anymore in custom ROMS and am happy with stock and root. I am curious though if I will be able to install TWRP from here. Haven't tried it.
I'd be careful though and get one more confirmation before you try it. When I said panic, that is really putting it lightly lol
ohlin5 said:
Yep, I know all about that. I've tot restored 10B a couple different times, and kdz'ed an 11C install back to 10B once, so I'm very familiar with both of those. I'm really curious to know though specifically if anyone has been able to confirm if 12B can be kdz'ed (or tot'ed for that matter, but I doubt it), back to 10B. If a new phone is bought in the next few weeks an comes out of the box with 12B flashed, I need to know whether this I would be stuck as unrootable/unlockable for the time being.
Click to expand...
Click to collapse
I can tell you this, I was rooted and the 12B update is on my phone and I'm still rooted. I'm going to try and flash back to 10B to see if it works or not. I'm trying to download the KDZ file, but it keeps aborting. The connection is REAL slow.
I haven't tried the TOT file yet either.
I used the TOT file myself.
A couple of things to consider, the tot download is to 10b_3 (the released version) and kzd is to version 10b_1.
The main difference is that 10b_3 Will take OTA updates while 10b_1 Will not.
Sent from my VS985 4G using XDA Free mobile app
tomlow said:
I used the TOT file myself.
Click to expand...
Click to collapse
Awesome! That's what I wanted to know. I'll probably stay on 12b rooted for now then.
---------- Post added at 11:37 AM ---------- Previous post was at 11:36 AM ----------
tomlow said:
I did it. Was curious about Advanced Calling so I downgraded since I forgot to make a backup of stock recovery. Got back to stock with no root and no custom recovery. Then I took the OTA updates to 12B. Found out I could not root from there and crossed my fingers and downgraded again. Had a moment of panic as the first attempt failed. Instead of getting a success msg on my computer and a big red number 3 on my phone I had a big red number 2. Restarted the process again and this time it took it. Rooted first this time, then took the updates. Not really interested anymore in custom ROMS and am happy with stock and root. I am curious though if I will be able to install TWRP from here. Haven't tried it.
I'd be careful though and get one more confirmation before you try it. When I said panic, that is really putting it lightly lol
Click to expand...
Click to collapse
Oh, and yes. You can install TWRP. As long as you're rooted, use Flashify to flash it. I can't seem to get to it via the button pushes though, so I installed Quick Boot and use that to boot into recovery, although at this time, I have no use for the recovery except for doing nandroid backups.
tomlow said:
I used the TOT file myself.
Click to expand...
Click to collapse
Thanks a ton for these confirmations....I have to say though, it's very interesting that tot worked for you when so many people had such trouble using the tot when 11C came out. Thanks again though!
ohlin5 said:
Thanks a ton for these confirmations....I have to say though, it's very interesting that tot worked for you when so many people had such trouble using the tot when 11C came out. Thanks again though!
Click to expand...
Click to collapse
I'm just surprised SuperSU survived the OTAs as I thought it wouldn't since the exploit probably does some modification to the system partition. On Motorola phones it usually caused issues.
I downgraded from 12b using the kdz method. No problems what so ever other than the flash tool crashing at the end.
cbrehob said:
I downgraded from 12b using the kdz method. No problems what so ever other than the flash tool crashing at the end.
Click to expand...
Click to collapse
Interesting....well then I'll ask you another couple off topic questions then, since the only experience I had with the kdz method turned out SUPER sketchy haha. So when I started the flash tool program up and began the process of flashing, I had 2 weird occurrences and want to know if you experienced anything similar. The first weird thing that happened is I never had any confirmation that the software was "seeing" the phone as being connected. I don't have it in front of me as I'm at work, but I recall one screen having boxes in the lower left corner that seemed like they should show something if it were seeing a device connected, but they were completely blank - do you know what screen I'm referring to, and did this happen to you?
And the second thing that happened that about gave me a heart attack (since it was on a friend's phone hahaha), was that when I couldn't get those boxes described above to populate and give me any indication/confirmation that the software was actually "seeing" anything, I just bit the bullet and decided to hit next, at which point the flash tool took off and began flashing, but both the flash tool program itself, and the dialogue boxes that popped up during the process were completely full of question marks.....nothing at all readable. Did you also experience anything like this?
Just figured I'd ask as since I did this to a friend's phone a month or so ago, it's always bugged me as to why it occurred, and so I've been very hesitant to ever use it again should I have to, so I at least wanted to see if I was in the minority on these experiences haha Thanks in advance!
ohlin5 said:
Interesting....well then I'll ask you another couple off topic questions then, since the only experience I had with the kdz method turned out SUPER sketchy haha. So when I started the flash tool program up and began the process of flashing, I had 2 weird occurrences and want to know if you experienced anything similar. The first weird thing that happened is I never had any confirmation that the software was "seeing" the phone as being connected. I don't have it in front of me as I'm at work, but I recall one screen having boxes in the lower left corner that seemed like they should show something if it were seeing a device connected, but they were completely blank - do you know what screen km referring to, and did this happen to you?
And the second thing that happened that about gave me a heart attack (since it was one friend's phone hahaha), was that when I couldn't get those boxes described above to populate and give me an indication/confirmation that the software was "seeing" anything, I just bit the bullet and decided to hit at which point the flash tool took off and began flashing, but both the flash tool program itself, and the dialogue boxes that popped up were completely full of question marks.....nothing at all readable. Did you also experience anything like this?
Just figured I'd ask as since I did this to a friend's phone a month or so ago, it's always bugged me as to why it occurred, and I've been hesitant to ever use it again should I have to, so I am least wanted to see if I was in the minority haha Thanks in advance!
Click to expand...
Click to collapse
Yah, it was sketch. I did see all the ?????? all over the screen but I trusted the directions on the thread.
As far as the software seeing the device, the only indication that I had was the program showing the available memory on the device, so I knew it was reading it.
I did it once, it worked, I'm not really a seasoned flasher. I just got my G3 last week and I had OTAd before rooting and unlocking.
cbrehob said:
Yah, it was sketch. I did see all the ?????? all over the screen but I trusted the directions on the thread.
As far as the software seeing the device, the only indication that I had was the program showing the available memory on the device, so I knew it was reading it.
I did it once, it worked, I'm not really a seasoned flasher. I just got my G3 last week and I had OTAd before rooting and unlocking.
Click to expand...
Click to collapse
Lol well I appreciate your confirmation that I'm not the only one who felt the sketchiness. I never noticed the available memory as being shown, but maybe I overlooked that. And I'm a pretty seasoned flasher, at least as far as custom rom flashing goes, but yeah that process definitely grew a little hair on my knuckles lol. Thanks again!
is 12B even worth upgrading to?
I have been reading alot about the update to 11 and 12B. is it really worth it to upgrade?...I got my phone it had 10B out of the box (I think) and phone immediately said there was an update as I was on my way home from the verizon store, so I thought sure and did the update, got home and started looking into root and realized I had to downgrade to 10 to get root, did it KTZ method, rooted, installed TWRP so I can make backups, and here I am ever since, as far as I can tell from reading is the only thing 12B gives you is advanced calling or whatever it is, I dont really care if I have that, I dont really even care if I have that unless someone can chime in and tell me whats its all about, is it worth upgrading and risking loosing root and stuff just for this advanced calling feature?...what is it and what does it do?
This is VoLTE or Voice over LTE. Someone will correct me if I'm wrong, but it doesn't do anything on the G3 other than allow your voice conversations to travel over the LTE line. This update was required for the Turbo, Sony, and other new phones that could not talk and surf at the same time. The G3 never had that problem.
nice tips, i was at 10b and rooted. i just couldnt take the annoying update available pop up anymore.
so i unrooted, udpated to 12b, then realized i cant root 12b. i just re flashed back to 10b.
my questions:
1) do i root 10b then upgrade to 11c? if so how, this was my original version and my problem was it always failed to update?
2) do i upgrade to 11c first, then root? if so how, i cant find directions to root 11c?
3) once rooted at 11c, how to i upgrade to 12b while keeping the root?
only reason i root is for wifi tethering on a unlimited verizon plan, if there is another way to be updated and have tethering, please share.
thank you.
i am a newbie at rooting, so specific links/steps are appreciated.
Yes. I went from 12 to 10,just follow the instructions.
jadams161 said:
Yes. I went from 12 to 10,just follow the instructions.
Click to expand...
Click to collapse
im not sure if you are trying answering my questions or not. if you are, i am rooted at 10b again. how do i keep my root but update to at least 11c, but preferably 12b?
update, i found a temp solution in another thread thanks to user Wildcat2083 :
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
this at least gets rid of the update pop up. but i would still like to know how to upgrade to 12b well keeping my root.
Hello, my Verizon Lg g3 wont boot at all. The screen wont turn on but the phone vibrates. Thats it. Any suggestions or comments would be greatly appreciated.
Phoner44 said:
Hello, my Verizon Lg g3 wont boot at all. The screen wont turn on but the phone vibrates. Thats it. Any suggestions or comments would be greatly appreciated.
Click to expand...
Click to collapse
Please explain more. Was it rooted? TWRP? What did you do before it couldn't boot?
Sent from my VS985 4G using Tapatalk
NBreunig3 said:
Please explain more. Was it rooted? TWRP? What did you do before it couldn't boot?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
mine has same problem..was rooted with kingroot and replaced by supersu..on stock Lp 5.1.1...stock recovery..
..was doing anything with phone ..left unplugged last night and battery died and plugged in this morning and all it does is vibrate periodically..cant get to download mode does nothing when i try..can take battery out and plug in and it gives the battery question mark on screen but thats it
i ran lg flashtool 2014 blind (meaning i hooked phone to computer still black screen) changed LGE Androidnet for VZW USB serial port to COM41 and used vs98535b kdz...it loaded firmware and started right up
verizon funny business
I haven't had to reboot my VZW LG G3 in a while, I have stayed back on 23C Lollipop since I was perfectly happy with it and had Hotspot mod working fine with root. Otherwise the phone was just stock 23C. I lost power last night and wanted to charge my phone a little faster so I turned it off to charge for an hour. When I tried to boot now I just get to the red Verizon screen and the phone gets pretty warm and I get a notification beep every 10-15mins, but no boot. I didn't have any update pending (I always remove the update files from cache/fota). So I guess now I need to do a stock recovery if I can get the phone to come up in Download mode. I'm pissed at VZW because I did not OK the installation of any updates, VZW basically disabled my perfectly good 23C phone. Any chance they target phones with 'root' modification flag set now with 'mainenance' updates?
What next?
I still haven't done anything with my G3 that is currently stuck on the 'Red Verizon' screen indefinitely at bootup. This was rooted and running otherwise stock 23c and I simply kept declining updates (have unlimited data so just deleted OTA files when they showed up). I want to make sure I proceed using the best approach to get back to a working state. I did *NOT* accept any updates, so scratching my head why simply rebooting would change anything. I'm ready to take the plunge to xdabbeb's flashable 46a if I can recover from the red vz screen.
Any suggestions on best course of action?
skay said:
I still haven't done anything with my G3 that is currently stuck on the 'Red Verizon' screen indefinitely at bootup. This was rooted and running otherwise stock 23c and I simply kept declining updates (have unlimited data so just deleted OTA files when they showed up). I want to make sure I proceed using the best approach to get back to a working state. I did *NOT* accept any updates, so scratching my head why simply rebooting would change anything. I'm ready to take the plunge to xdabbeb's flashable 46a if I can recover from the red vz screen.
Any suggestions on best course of action?
Click to expand...
Click to collapse
Try removing the Micro SD card. Try Factory Reset if on stock recovery, or wiping Cache and Dalvik if on custom recovery. If the latter doesn't help, try wiping Data. Second to last resort, wipe internal storage.
If all that fails, use LG Flash Tool 2014 on a Windows PC with the 10B KDZ in CSE mode, which will wipe all data including internal storage.
Use the Stump app to root and TWRP Manager to put TWRP on, then flash the ROM of your choice.
roirraW "edor" ehT said:
Try removing the Micro SD card. Try Factory Reset if on stock recovery, or wiping Cache and Dalvik if on custom recovery. If the latter doesn't help, try wiping Data. Second to last resort, wipe internal storage.
If all that fails, use LG Flash Tool 2014 on a Windows PC with the 10B KDZ in CSE mode, which will wipe all data including internal storage.
Use the Stump app to root and TWRP Manager to put TWRP on, then flash the ROM of your choice.
Click to expand...
Click to collapse
You are such a champ reverse "rode" . I was set to try the method you suggested, but figured since you mentioned first removing the micro SD that I might as well just trying rebooting after removing it, and 'voila' as they say, it booted right up!
Ever heard of a rebooting issue with micro SD cards inserted? I've been running for a long time with the same card (64gb Samsung EVO) so it baffles me why *this* reboot caused the boot hang?
So I think now it's time to dive in completely and get setup for TWRP with flashable ROM of 46a (thnx xdabbeb).
I just tried sticking the micro SD card back in after clean shutdown and get the same behavior, hanging at 'Red Verizon' boot screen. Could it be a micro SD formatting issue? Like I said I have been running the phone with the same 64gb card for over 2 months?
skay said:
You are such a champ reverse "rode" . I was set to try the method you suggested, but figured since you mentioned first removing the micro SD that I might as well just trying rebooting after removing it, and 'voila' as they say, it booted right up!
Click to expand...
Click to collapse
Thanks and you're welcome! ?
It's happened occasionally to other G3 users.
Do you have TWRP installed? You can use it or a Windows PC and delete the Android and android-secure folders and it might work after that. Otherwise, I suggest a reformat, preferably from within running Android.
roirraW "edor" ehT said:
Thanks and you're welcome!
It's happened occasionally to other G3 users.
Do you have TWRP installed? You can use it or a Windows PC and delete the Android and android-secure folders and it might work after that. Otherwise, I suggest a reformat, preferably from within running Android.
Click to expand...
Click to collapse
Wow, this appears to be a bona-fide micro SD failure. I have bought cheapo Chinese copies in the past, and learned my lesson that you won't get a decent card (either smaller than advertised, slow, etc.). But this card was purchased at my local Walmart and I ran the Crystaldiskmark suite on it and it was fine. Now ~2 mos later it's not functioning properly, but at least I could 'read' the data off of it. Samsung gave me an RMA to send it in for a replacement.
But now I psyched for MM 46a so I will get TWRP installed and try flashing xdabbeb's ROM. Can I install TWRP straight to my stock 23c rooted phone?
skay said:
Wow, this appears to be a bona-fide micro SD failure. I have bought cheapo Chinese copies in the past, and learned my lesson that you won't get a decent card (either smaller than advertised, slow, etc.). But this card was purchased at my local Walmart and I ran the Crystaldiskmark suite on it and it was fine. Now ~2 mos later it's not functioning properly, but at least I could 'read' the data off of it. Samsung gave me an RMA to send it in for a replacement.
But now I psyched for MM 46a so I will get TWRP installed and try flashing xdabbeb's ROM. Can I install TWRP straight to my stock 23c rooted phone?
Click to expand...
Click to collapse
It happens. Depends on a lot of factors and flash storage can be finicky. The easiest/best way to install TWRP on 23C is @bender_007 's autorec TWRP app. You can find the 23C version in the Play Store. It works ONLY on 23C. Never try to use it on anything else. He makes a 24B version - it's in his thread for autorec TWRP in the non-Verizon G3 General section, I believe, if you ever find yourself on 24B. Again, don't use that one on anything else.
The app takes asks for root permissions. Once you grant it, it appears to be frozen but that's because it's making a backup of your current recovery. Then you can press the button to install TWRP and it'll let you know when it's done.
Once you've got it installed, if it's not at least v2.8.7.0, flash either v2.8.7.0 or v3.0.0 from the version of TWRP the app installs, then choose Reboot Recovery from TWRP.
roirraW "edor" ehT said:
It happens. Depends on a lot of factors and flash storage can be finicky. The easiest/best way to install TWRP on 23C is @bender_007 's autorec TWRP app. You can find the 23C version in the Play Store. It works ONLY on 23C. Never try to use it on anything else. He makes a 24B version - it's in his thread for autorec TWRP in the non-Verizon G3 General section, I believe, if you ever find yourself on 24B. Again, don't use that one on anything else.
The app takes asks for root permissions. Once you grant it, it appears to be frozen but that's because it's making a backup of your current recovery. Then you can press the button to install TWRP and it'll let you know when it's done.
Once you've got it installed, if it's not at least v2.8.7.0, flash either v2.8.7.0 or v3.0.0 from the version of TWRP the app installs, then choose Reboot Recovery from TWRP.
Click to expand...
Click to collapse
I see the (VS985) LG G3 AutoRec-Lollipop from neko_dugacko_ime. It looks like that is the installer you are referring to, correct?
skay said:
I see the (VS985) LG G3 AutoRec-Lollipop from neko_dugacko_ime. It looks like that is the installer you are referring to, correct?
Click to expand...
Click to collapse
Yep, that's what I found. https://play.google.com/store/apps/details?id=b007.autorecvs985&hl=en
Many thanks. Just one more question, I really would like to jump on xdabbeb's flashable 46a ROM. But it looks like he wants the bootstack from 35B, and it looks like TWRP is not compatible with 35B? Not sure which is the best path OR if I should just install TWRP from GPlay and then flash another 46a ROM when/if it becomes available? I figured the xdabbeb 46a would get me to the most recent MM official release but I could keep root if done properly.
skay said:
Many thanks. Just one more question, I really would like to jump on xdabbeb's flashable 46a ROM. But it looks like he wants the bootstack from 35B, and it looks like TWRP is not compatible with 35B? Not sure which is the best path OR if I should just install TWRP from GPlay and then flash another 46a ROM when/if it becomes available? I figured the xdabbeb 46a would get me to the most recent MM official release but I could keep root if done properly.
Click to expand...
Click to collapse
I'm not sure what you mean about TWRP not compatible with 35B.
If you're on any stock ROM other than 10B, you can't install TWRP as simply as going to Google Play. At minimum you have to downgrade your aboot.img (bootloader) and @xdabbeb likes to keep the laf.img (Download mode) matching the aboot, to 12B's aboot and laf.
I usually recommend to people to just downgrade to 10B via TOT or KDZ (TOT is only option if coming from unrooted stock 35B) for the easiest way to root using the Stump app, and to install TWRP via TWRP Manager.
Thanks edor. But a little more confused. I thought the GPlay auto-rec install from https://play.google.com/store/apps/d...recvs985&hl=en made for an easy TWRP install on 23c with root (exactly my configuration). I thought I could install TWRP and download and flash xdabbeb's 46a flashable ROM.
If the best approach for staying on the latest ROM images is going back to 10B or 12B and starting from there with TWRP I'll go that route, but my main goal now was simply to be able to flash the 46a ROM from xdabbeb http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365. Now that my phone is working fine I want to take the time to set it up in the best possible way for installing ROM images going forward since it appears each new release gets more difficult to get root access and I want to keep the hotspot mod going since I have unlimited data. Though I admit I miss having the stock unrooted NFL Mobile working, but I have a while till next season rolls around !
skay said:
Thanks edor. But a little more confused. I thought the GPlay auto-rec install from https://play.google.com/store/apps/d...recvs985&hl=en made for an easy TWRP install on 23c with root (exactly my configuration). I thought I could install TWRP and download and flash xdabbeb's 46a flashable ROM.
If the best approach for staying on the latest ROM images is going back to 10B or 12B and starting from there with TWRP I'll go that route, but my main goal now was simply to be able to flash the 46a ROM from xdabbeb http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365. Now that my phone is working fine I want to take the time to set it up in the best possible way for installing ROM images going forward since it appears each new release gets more difficult to get root access and I want to keep the hotspot mod going since I have unlimited data. Though I admit I miss having the stock unrooted NFL Mobile working, but I have a while till next season rolls around !
Click to expand...
Click to collapse
You confused me when you said you heard TWRP isn't compatible with 35B or 46A, whichever you said. TWRP is compatible. The Autorec app to put TWRP on is only compatible with 23C and 24B - the one in the Play Store for 23C, then there's one in @Bender007 's Autorec thread for 24B.
It's just my opinion but yes, I always recommend going back to 10B for the easiest way to root and put TWRP on.
You may be able to get away with simply flashing the 12B aboot.img (bootloader) and laf.img (Download mode) in a terminal emulator with superuser permissions. The commands are near the bottom of @bweN diorD 's stickied thread in General. I recommend copy and paste because if you get the commands slightly wrong you could at least temporarily brick your device.
Then you should be able to flash TWRP either also in terminal emulator or you might be able to use TWRP Manager then.
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!
Greetings,
Seemingly out of the blue, I have started having major wifi problems. The problem is that the wifi connection either doesn't connect, giving a "Wifi Connection Failure" or will connect briefly with no actual access to the internet. This problem occurs on multiple routers from multiple ISPs. I have already ensured the router is working, going so far as factory resetting it and providing a static IP for my phone. I have even factory reset my phone. Same problem, though it does seem to stay connected to my wifi longer but still no internet. Even in Safe Mode, I cannot get any internet access via wifi.
Verizon LG G3, Unrooted with 47A release (No custom ROMs)
Any suggestions?!?!
Hi!
What ROM are you on? The latest 47A Marshmallow? Are you rooted?
Regardless I suggest flashing the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that nothing else can, so even if you want to stay unrooted flash the TOT first, test WiFi, and if WiFi works then flash the 47A KDZ with the CSE option, and test WiFi again. Both will wipe all user apps and all data and internal storage so move everything you want to keep. You can use the built in LG Backup to backup your user apps and data to your Micro SD card.
If you wanted rooted, then while on 10B use the Stump app to root and use TWRP Manager from the Play Store to flash TWRP, then flash the ROM you want and appropriate Bootstack.
roirraW "edor" ehT said:
Hi!
What ROM are you on? The latest 47A Marshmallow? Are you rooted?
Regardless I suggest flashing the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that nothing else can, so even if you want to stay unrooted flash the TOT first, test WiFi, and if WiFi works then flash the 47A KDZ with the CSE option, and test WiFi again. Both will wipe all user apps and all data and internal storage so move everything you want to keep. You can use the built in LG Backup to backup your user apps and data to your Micro SD card.
If you wanted rooted, then while on 10B use the Stump app to root and use TWRP Manager from the Play Store to flash TWRP, then flash the ROM you want and appropriate Bootstack.
Click to expand...
Click to collapse
Sorry for leaving out info.
Stock ROM, Unrooted with 47A release.
I was thinking about flashing but I was hoping I wouldn't have to. The 47A release fixed a couple of nagging issues but this issue is obviously worse. At this point, I'm kinda desperate...
someguyouknew said:
Sorry for leaving out info.
Stock ROM, Unrooted with 47A release.
I was thinking about flashing but I was hoping I wouldn't have to. The 47A release fixed a couple of nagging issues but this issue is obviously worse. At this point, I'm kinda desperate...
Click to expand...
Click to collapse
Understood. No problem! I've been on 47A since it came out - first unrooted and then rooted so hopefully the 10B TOT and then 47A KDZ should get and keep the WiFi working unless it's a hardware issue. Hopefully just software though.
roirraW "edor" ehT said:
Understood. No problem! I've been on 47A since it came out - first unrooted and then rooted so hopefully the 10B TOT and then 47A KDZ should get and keep the WiFi working unless it's a hardware issue. Hopefully just software though.
Click to expand...
Click to collapse
I appreciate your response! I'm watching the youtube video on how to do it right now. Thanks!
roirraW "edor" ehT said:
Hi!
What ROM are you on? The latest 47A Marshmallow? Are you rooted?
Regardless I suggest flashing the 10B TOT. TOTs flash more partitions than KDZs and can fix problems that nothing else can, so even if you want to stay unrooted flash the TOT first, test WiFi, and if WiFi works then flash the 47A KDZ with the CSE option, and test WiFi again. Both will wipe all user apps and all data and internal storage so move everything you want to keep. You can use the built in LG Backup to backup your user apps and data to your Micro SD card.
If you wanted rooted, then while on 10B use the Stump app to root and use TWRP Manager from the Play Store to flash TWRP, then flash the ROM you want and appropriate Bootstack.
Click to expand...
Click to collapse
Flashing to 10B didn't seem to work. It's starting to look like a hardware problem. Really disappointing as I have only had this phone for less than 2 years.
Thanks for the suggestion, though.
someguyouknew said:
Flashing to 10B didn't seem to work. It's starting to look like a hardware problem. Really disappointing as I have only had this phone for less than 2 years.
Thanks for the suggestion, though.
Click to expand...
Click to collapse
Sorry to hear that! I was really hoping it was software. Sorry to be a squeaky wheel but I just wanted to make sure, you flashed the 10B TOT, not just the 10B KDZ, right? You're welcome and good luck with what options you might have. You could try sending to LG and seeing what they would charge you but unless you have a backup phone that would be tough. I had an awesome experience with their repair for my tablet but that was under warranty.
roirraW "edor" ehT said:
Sorry to hear that! I was really hoping it was software. Sorry to be a squeaky wheel but I just wanted to make sure, you flashed the 10B TOT, not just the 10B KDZ, right? You're welcome and good luck with what options you might have. You could try sending to LG and seeing what they would charge you but unless you have a backup phone that would be tough. I had an awesome experience with their repair for my tablet but that was under warranty.
Click to expand...
Click to collapse
Yea, definitely used the .tot method. I am typing up an email to LG right now. Hopefully it isn't out of warranty.
someguyouknew said:
Yea, definitely used the .tot method. I am typing up an email to LG right now. Hopefully it isn't out of warranty.
Click to expand...
Click to collapse
Let us know how things work out.
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.