I have had stability issues on marshmallow. I flashed the 35B bootstack and upgraded to the Azadi marshmallow variant. It was working fine, but there had been more updates to the rom, so I flashed those as well (without flashing 35B again). I was getting occasional system reboots, so I switched to the stock 47A firmware (debloated using joshua70448 zip generator). I am still having the same issue - the system randomly reboots, sometimes twice in a row. Also sometimes when I power down, the phone will not power up again until I remove the battery.
I really cannot relate this to any particular situation - it seems to happen at completely random times.
Any help is greatly appreciated.
Did you try what I suggested at the bottom of the reply I sent in the other thread?
http://forum.xda-developers.com/showthread.php?p=66842422
roirraW "edor" ehT said:
Did you try what I suggested at the bottom of the reply I sent in the other thread?
http://forum.xda-developers.com/showthread.php?p=66842422
Click to expand...
Click to collapse
No. Somehow I lost that last sentence in your sig.
So wipe, flash TOT, flash 35B, flash ROM, ???, profit?
B00M! said:
No. Somehow I lost that last sentence in your sig.
So wipe, flash TOT, flash 35B, flash ROM, ???, profit?
Click to expand...
Click to collapse
Flash the 10B TOT, root using the Stump app, use TWRP Manager from the Play Store to install TWRP, wipe Cache, Dalvik/ART and Data, flash the 35B bootstack if you're going to flash a 35B or higher ROM, then flash the ROM.
If you're going to flash a ROM that had a lower version of Android, flash the corresponding Bootstack.
Ok. I will let you know how it turns out.
Is this going to repartition my device?
B00M! said:
Ok. I will let you know how it turns out.
Is this going to repartition my device?
Click to expand...
Click to collapse
I'm not sure what you mean by repartition. It will wipe everything including internal storage. It won't wipe external MicroSD. You'll be back on completely stock 10B, which is easiest to root and put TWRP on.
I thought I read somewhere that one of the updates changed some of the partition sizes, but I guess if that were true, you would know
I was mostly concerned about whether or not my internal storage would be wiped in the process.
Out of curiosity, why do you recommend TOT instead of KDZ method?
B00M! said:
I thought I read somewhere that one of the updates changed some of the partition sizes, but I guess if that were true, you would know
Click to expand...
Click to collapse
Maybe they did, I wouldn't necessarily have noticed.
Out of curiosity, why do you recommend TOT instead of KDZ method?
Click to expand...
Click to collapse
That's answered in my original reply to you in the other thread. Again, just the part at the bottom of my reply.
For anyone who follows this thread:
roirraW "edor" ehT said:
Doubtful, if it's the way you describe it. The only reason I tell people this is because some people ask for help determining when they can get away with not flashing the bootstack again.
It's far simpler to just flash whichever the appropriate bootstack is every time you flash a ROM or restore a TWRP backup. There's just no reason to avoid flashing the right one every time.
If you're experienced enough that you know you don't have to flash it again, then don't. If you're mistaken, you could end up with a temporary brick depending on the exact situation, but it's still not caused by the bootstack.
Also, the wrong bootstack doesn't cause stability issues or reboots. It can cause no signal, not being able to use Advanced/HD Calling and not being able to encrypt your SD card.
....
I recommend flashing the 10B TOT. TOTs flash more partitions than KDZs, as @xdabbeb taught me and I verified. I had a weird problem months ago that wouldn't go away no matter what ROM or KDZ I flashed until I flashed the TOT.
Click to expand...
Click to collapse
This unfortunately did not work. I think I have traced the initial problem to a particular situation. The first crash seems to always happen when I launch navigation. The phone will suddenly turn off and then reboot twice. After this inciting event, the system seems to become unstable and will reboot at random times when I am using it. Is there a way to track what is causing the crash using logcat or something? Any other ideas? I might just have to go back to LP, as I don't think I was having a problem running it.
B00M! said:
This unfortunately did not work. I think I have traced the initial problem to a particular situation. The first crash seems to always happen when I launch navigation. The phone will suddenly turn off and then reboot twice. After this inciting event, the system seems to become unstable and will reboot at random times when I am using it. Is there a way to track what is causing the crash using logcat or something? Any other ideas? I might just have to go back to LP, as I don't think I was having a problem running it.
Click to expand...
Click to collapse
What exactly do you mean by "launch navigation"? If you're on Azadi right now, I haven't used it so I can't particularly advise, although I'm curious if you'd have the problem on a less modified stock ROM, and also curious if you would be able to replicate the problem if you were completely stock unrooted.
Sounds very strange. I haven't had this issue among the ROMs I've used. Currently @xdabbeb 's stock 47A firmware (fully debloated). Previously his VS985 v2.0 (35B) ROM, and previous to that, several versions of JasmineROM up through 9.1 (35B).
I really have no experience with logcats so I can't advise you there.
It's possibly your battery is going bad, as that's been known to cause all sorts of weird issues.
By launch navigation, I mean start a new navigation in google maps. I get to the map just fine, searches just fine, but when I start the navigation, the phone goes black and reboots.
I have had this issue on Azadi as well as the stock 47A version (with debloating as I described in the other thread) both before and after the TOT install. I saved a stock rooted 47A TWRP version during this process, so I could unroot it and see if the problem persists. There does appear to be some relation to the battery, as it will crash and reboot and lose about 10% of the battery in the process. After I plug it in, the battery returns to its "precrash" level. Drain does not seem to be greatly different than before I transitioned to MM.
Again, I really appreciate your help and ideas.
B00M! said:
By launch navigation, I mean start a new navigation in google maps. I get to the map just fine, searches just fine, but when I start the navigation, the phone goes black and reboots.
I have had this issue on Azadi as well as the stock 47A version (with debloating as I described in the other thread) both before and after the TOT install. I saved a stock rooted 47A TWRP version during this process, so I could unroot it and see if the problem persists. There does appear to be some relation to the battery, as it will crash and reboot and lose about 10% of the battery in the process. After I plug it in, the battery returns to its "precrash" level. Drain does not seem to be greatly different than before I transitioned to MM.
Again, I really appreciate your help and ideas.
Click to expand...
Click to collapse
Unrooting a backed up version of 47A wouldn't be the same as actually running the full stock unrooted 47A, not unless you went to a tremendous amount of effort (meaning it's far simpler to flash a KDZ).
I use Maps all the time on stock fully debloated 47A and have done so recently without issue. I'm only saying this because I don't think the ROM is the issue.
I would definitely proceed further with the battery route. Unless there's some tiny piece of detail that I don't know, it's either that or just general hardware failure, but I doubt that.
Just for the heck of it, eject your MicroSD card and leave it out, reboot the phone and do what you can do to replicate the issue while the card's ejected. I hope you eventually solve this, sooner rather than later and hopefully not too much more paintfully.
Alright. Yeah. It has been a PITA trying to get back to a stable setup. I too do not think it is the ROM based on what has happend so far.
The only bit that I haven't mentioned is that the commands are set up through tasker (switches on Bluetooth, launches the apps and starts the navigation). I may try to run the stock, debloated, rooted, 47A rom without tasker next to see if the problem still occurs. This too does not seem like the issue, because sometimes tasker launches everything and it runs well without any crashes. I don't see that anyone is reporting a similar issue in the tasker Google group.
I will keep this thread updated to any progress.
After extensive testing, I am convinced this is a battery issue. New battery is on the way.
No issues after replacing the battery. Life is good again
Related
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
Click to expand...
Click to collapse
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
startswithPendswithOOH said:
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
Click to expand...
Click to collapse
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
dbow32 said:
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
Click to expand...
Click to collapse
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software.
Click to expand...
Click to collapse
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
BladeRunner said:
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
Click to expand...
Click to collapse
To be honest, I'm not sure what drivers I was using. I did a Google search for LG suite and found the closest version I could find. They didn't have the VS985, Only P985. So that might have had something to do with it.
startswithPendswithOOH said:
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
Click to expand...
Click to collapse
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
dbow32 said:
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
Click to expand...
Click to collapse
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
startswithPendswithOOH said:
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
Click to expand...
Click to collapse
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
dbow32 said:
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
Click to expand...
Click to collapse
It's possible the modem could've been causing problems. Is 11c better or worse for you? And its also possible big red was throttling you too. That seems like something they'd do.
If you use/like xposed framework G3 tweaksbox is a good app to get for customizing your phone a little bit. And greenify and amplify are good xposed apps that help your battery life a whole lot. They are worth checking out in the play store.
For reference, there are at least two situations resulting in a black screen on the VS985.
This thread only addresses the issue of purposely rebooting the phone either with an app or built in reboot menu resulting in a black screen and requiring pulling the battery OR mashing down the power button for long enough to turn the phone off and then back on, at which point the black screen issue is resolved. Discuss the other black screen issue(s) or any other issue elsewhere, please.
I am not looking for further guessing/speculation in this thread. If you want to do an extended, detailed series of tests and post your results here, you're more than welcome.
For further reference, this problem has been with the VS985 since it came out. It has happened to myself and to others on official LG builds ranging from 10C to 35B. It previously happened for me personally about two times on either 12B, 10B or 11C. On my phone, the LED does not blink while on this black screen and in my experience that only coincides with the OTHER black screen issue not covered in this post. Additionally, sometimes the VS985 can take longer to shutdown when you choose to either shutdown or reboot, during which it displays a black screen and a blinking LED during this shutdown process for as long as a minute or so, that I've noticed when it happens.
I'm done trying to narrow this down for now, probably permanently.
Link to my documentation of my process and test results: https://docs.google.com/spreadsheets/d/1l65S1FcU_ngh5q4VcMzZMOxGbzutZPlUoiPhLswj2YE/edit?usp=sharing
Summary of the results:
Things that definitely do NOT make the black screen reboot issue happen more often than it did on any other stock or stock-based VS985 ROMs, from 10B through 35B:
1. 35B in general (ROMs, stock, rooted, unrooted...).
2. 35B bootstack.
3. F2FS.
4. @xdabbeb 's kernel that comes with his VS985 v2.0 ROM.
5. Using either the "adrenoidler" or "disableapps" mods for this ROM.
6. I don't think it's Xposed. If it is, it's in combination with something else that's elusive, because I performed 70 reboots in a row with Xposed installed and configured to varying degrees (detailed below in rounds #s 4-11) with no sign of the problem.
7. A huge list of apps that I restored via the built-in LG Backup from my previous installation - the one represented by the first three rounds of testing which did exhibit the issue.
8. Restoring system data via the built-in LG Backup, admittedly taken from an LG Backup from a few weeks previous.
9. I don't think it's the 3MinitBattery mod posted in @xdabbeb 's VS985 v2.0 ROM thread, since in the last several rounds of testing, I was able to reproduce the problem and I hadn't flashed that mod.
I did something at this point in testing which is commonly done by lots of people including myself, (edit for clarity) and after doing this, the problem started happening again in rounds 12-14. I won't report what it was because I can't determine what, precise part of it would cause the problem - *IF* it in fact had anything to do with it. I won't lead anything else to be rumored.
I just had the black screen reboot issue rebooting from TWRP after restoring a nandroid.
This further eliminates:
10. Any ROM.
11. Any kernel.
12. Charging the phone for long periods of time.
I've rebooted 140 times documented and probably at least another 20 or 40 or so undocumented.
Reserved 1.
Reserved 2.
I just had the black screen reboot issue rebooting from TWRP after restoring a nandroid.
This further eliminates:
10. Any ROM.
11. The kernel.
Added to OP.
What ROM and bootstack are you using. I just know what I experienced. My booting to black screen issues started when I flashed Xdabbeb's ROM and 35B bootstack. Before I was on stock 35B unrooted and didn't have any problems.
Running xdabbeb's 2.0 Rom, I had constant issues with booting. It was really bad on cold boots. I like to charge my phone overnight with power off. I find that it helps save battery life. Every morning, it would take me a couple of tries to finally boot. I tried reflashing rom and bootstack. I redownloaded both, flashed and still had issues.
Finally I flashed Jasmine 9.1 but only on 24B bootstack and I have had no issues. Ever boot from cold, reboot, to and from recovery has had no issues. I was going to flash 35B bootstack to run with Jasmine but at this point, I don't want to mess with it. My phone is running great, no need to tempt fate.
I know you are not finding any root causes for your booting problem. But for me, it was clearly my phone, xdabbeb's rom, and 35B bootstack. Those 3 did not play well together at all.
Look at the documentation I linked to.
Thank you for giving this issue some focus, i would not exactly rule out kernel/rom, using jasmines or skydragon 35b rom on my device does not cause the boot issue, also fulmics rom doesn't do it as often as cloudy 2.5. if you flash the kernel from fulmic over cloudys rom,, it improves the reboot problem. Keeping in mind that the original kernel used in cloudy rom will reliably give the issue on every cold boot.
Is there anybody running a non-verizon rom that does not have this issue, if so could you post your root/recovery method?
based of my reading, and i could be wrong, the issue is with running lollipop on a kitkat boot-loader that may be causing the issue, yet again i can be very wrong about all of this.
bulletbeef said:
Thank you for giving this issue some focus, i would not exactly rule out kernel/rom, using jasmines or skydragon 35b rom on my device does not cause the boot issue, also fulmics rom doesn't do it as often as cloudy 2.5. if you flash the kernel from fulmic over cloudys rom,, it improves the reboot problem. Keeping in mind that the original kernel used in cloudy rom will reliably give the issue on every cold boot.
Is there anybody running a non-verizon rom that does not have this issue, if so could you post your root/recovery method?
based of my reading, and i could be wrong, the issue is with running lollipop on a kitkat boot-loader that may be causing the issue, yet again i can be very wrong about all of this.
Click to expand...
Click to collapse
You're welcome.
It you look at the linked documented specifics of the tests, you'll see that I had 70 consecutive reboots with no issue at all while I was on the KitKat bootloader while running on Lollipop.
In order to do process of elimination tests, you have to change very discreet things between tests. This results in a lot of reboots, relatively minor changes between tests, and occasional backups in TWRP.
It's the closest to a "controlled environment" that I can produce.
I'm not about to add even more variables to the mix with using CM or international stock based ROMs when I was able to produce the problem with statistical reliability on a VS98535B stock based ROM.
Thanks anyway.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
Oh i see, i didnt realise that all tests done were on 35b. My device does not hav the issue at all on vzw stock roms only the d855 based roms and aosp i have the issue.
Thanks again and please dont abandon research on the issue.
bulletbeef said:
Oh i see, i didnt realise that all tests done were on 35b. My device does not hav the issue at all on vzw stock roms only the d855 based roms and aosp i have the issue.
Thanks again and please dont abandon research on the issue.
Click to expand...
Click to collapse
No sweat, you're welcome. We'll see, after a while the tediousness of the testing wears me thin plus I achieved my main goals which was to eliminate certain things which had been rumored by some to be causing it to be worse: the 35B bootstack.
I might actually add Xposed and G3TweaksBox to the list of things eliminated because I had 40 reboots (from memory) without a problem while G3TweaksBox was installed and at least I think 20-30 of those with G3TweaksBox's app data restored the same as it was in the first 30 reboots during my initial setup when I was able to reproduce the issue consistently, so I don't really think Xposed or modules have to do with it either.
My observations:
I've never had this issue on my daily driver setup, SkyDragon 2.0.1 (yes, I prefer KK) running 12B bootstack with Xposed (G3Tweaksbox, App Ops, others).
A few days after xdabbeb's ROM was released, I wiped my device, installed the 35B bootstack, and then the xdabbeb ROM. Without doing any additional customization or setup (before I even installed any additional apps), the black screen reboot issue happened every single time I rebooted my G3, requiring a battery pull.
Due to that and the lack of a compatible G3Tweaksbox at the time, I wiped my device, flashed the 12B bootstack again, and restored my SD2.0.1 backup. Have yet to encounter the black screen reboot issue again.
Data point
I bought my first VS985 in August 2014, and I've never seen this. I was rooted (w/ stock recovery) from 10B through 23C, and then reverted to 100% stock.
The other VS985 has never seen it either, but it's less than a month old.
I did have the Reboot black screen issue happen once tonight with the Quick Reboot app. If I resume any testing of my own I'll probably do separate test runs off the Xposed and Quick Reboot methods in case there's some difference. Last times I had tried reproducing the issue I was only bothering to try the Xposed method. It's also possible this "one off" occurred as part of what we consider the normal rate of this happening, since we still expect this to happen some no matter what we do due to our overall previous experience of this happening at least some on this phone.
I'm not sure if this was discussed or not but I'm just going to throw it out there, I can tell on the vibration when its rebooting whether or not it's going to boot to a black screen! If it's going to boot to a black screen it'll be a short vibration, if it's going to boot normally it will be a longer vibration. Have you noticed this?
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
I am thinking it might be a hardware or twrp issue
davidstjohn1 said:
I'm not sure if this was discussed or not but I'm just going to throw it out there, I can tell on the vibration when its rebooting whether or not it's going to boot to a black screen! If it's going to boot to a black screen it'll be a short vibration, if it's going to boot normally it will be a longer vibration. Have you noticed this?
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
I am thinking it might be a hardware or twrp issue
Click to expand...
Click to collapse
That's interesting regarding the vibration, thanks for the info.
Hardware, yes, that's one of the things that has remained a possibility.
TWRP no. As I indicated in my test details, I went through 70 consecutive reboots without failure (and I had TWRP installed the whole time).
roirraW "edor" ehT said:
That's interesting regarding the vibration, thanks for the info.
Hardware, yes, that's one of the things that has remained a possibility.
TWRP no. As I indicated in my test details, I went through 70 consecutive reboots without failure (and I had TWRP installed the whole time).
Click to expand...
Click to collapse
Well i have noticed a significant difference in the vibration duration when closely watching it go through the the process. Also it has happened to me using cm 12.1 on a regular basis as well.
I have a vs985 (total of 3 all together-counting replacements for the casing crack) . I never had this problem until recently, now it happens very frequently. For me it seems to have started since I started flashing bootstacks. I am a novice, but I am wondering if there is a subtle change in the partitions that is left behind by changing the bootstack? I have tried a factory reset. But still have this issue. Very strange as it just started recently. I have never done an internal sd wipe... Was wondering if that can be done and if it would help? Any thoughts?
tmord1 said:
I have a vs985 (total of 3 all together-counting replacements for the casing crack) . I never had this problem until recently, now it happens very frequently. For me it seems to have started since I started flashing bootstacks. I am a novice, but I am wondering if there is a subtle change in the partitions that is left behind by changing the bootstack? I have tried a factory reset. But still have this issue. Very strange as it just started recently. I have never done an internal sd wipe... Was wondering if that can be done and if it would help? Any thoughts?
Click to expand...
Click to collapse
Did you take a look at the details of my testing? I did 70 tests in a row without a problem, both after and before being able to replicate the problem by changing the things I detail. Flashing KDZs and TOTs changes the same things as the bootstacks - actually more than the boostacks. The only exception is the bootloader (aboot.img) and Download mode (laf.img) partitions, which are kept at an older version in order to still be able to get into TWRP, and to be able to flash any KDZs and TOTs you want.
JasmineROM and SkyDragon change most of the same partitions, and either always have, or have since at least v2 or v3 of both.
I'm sorry if I'm a bit harsh, but it's been speculated so many times that it's the boostacks. Please everyone stop spreading rumors and only report what you have strong evidence for that you tested. That's one of the reasons I did these tests to begin with to show all the things that it can't be. Between items 9 and 10 in the first post, I posted that I did something very common, after which the problem started happening a lot more predictably. I'm not reporting what it was because in order to be at least 99% sure, I need to narrow it down further so that more rumors and speculation aren't spread.
I am not looking for further guessing/speculation in this thread. If you want to do an extended, detailed series of tests and post your results here, you're more than welcome.
Again, I'm sorry for being harsh but hearing the same things over and over being rumored without real evidence is really tiring.
I hope we can find a fix for this issue! Good thing the G3 has a removable battery or this problem would be even more annoying. For my G3 this problems seems to happen more when I try select restart and happens less when I just pick power complete off then power back on. Also this has happened while flashing CM nightlys. I select install update, and my G3 powers down then black screens, and then I pull the battery and boot into TWRP manually and the CM updates starts to install automatically. To avoid this issues as much as I can I usually just select soft reboot in the menu. Either way I am glad no matter what devolves found a way to bypass the boot loader and install TWRP. I Don't think I would still have my G3 is there was no way to run AOSP Roms
Here is a question I have.
Does this happen on other G3 models or just the VS985?
Just wondering
Also on back Friday I bought a MOTO 3 for a backup for $10 at best buy so I may have to try doing some test with my G3 and see what the results are!
clapper66 said:
I hope we can find a fix for this issue! Good thing the G3 has a removable battery or this problem would be even more annoying. For my G3 this problems seems to happen more when I try select restart and happens less when I just pick power complete off then power back on. Also this has happened while flashing CM nightlys. I select install update, and my G3 powers down then black screens, and then I pull the battery and boot into TWRP manually and the CM updates starts to install automatically. To avoid this issues as much as I can I usually just select soft reboot in the menu. Either way I am glad no matter what devolves found a way to bypass the boot loader and install TWRP. I Don't think I would still have my G3 is there was no way to run AOSP Roms
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
Here is a question I have.
Does this happen on other G3 models or just the VS985?
Just wondering
Click to expand...
Click to collapse
You can also hold down the power button for like 10 seconds I think, to force shut it off. I don't know the answer regarding if it happens to other G3 variants.
Ok, i'm fairly new to this stuff but have successfully rooted and modified several of my devices over the years. I've been attempting to upgrade my vs985 to as close to stock 5.1.1 as i can and after much reading decided on jasmine. I was rooted on kk 4.4.2 12b and I had no problems. the main reason i wanted to upgrade was for compatibility with my android play car stereo. I didn't have twrp so first i downloaded flashify and quickboot then flashed twrp from flashify. All good so far. Next I downloaded jasmine 9.0 and 9.1 or at least i thought lol. As it so happened i mistakenly ended up with one of the files being just the kernel for 5.1.1 35b. Must of been a long day cause I mistakenly failed to backup my current system and proceeded wipe data, cache, dalvik, and flashed the kernel file. As you might imagine it didn't turn out very good. I was stuck in boot loop. Fortunately I could still get into download mode so I was able to use the lg flash tool and I brought it all the way back to 10b stock firmware. Then i grabbed stump and rooted and flashed twrp again. at some point i noticed my cell signal was all over the place, up, down , no signal and it roamed almost constantly if there was any signal. I've had this phone and service for well over a year and never had anything like this at all. I knew it was something I did. I checked the back cover to be sure it was on properly and had good connection with the antenna and all checked out. I decided to go ahead and do the upgrade to jasmine 9.1 hoping this would correct the issue. Well no dice. I did create a backup this time and proceeded to wipe everything and flash 9.0 reboot then wipe nothing and flash 9.1, i guess as you call it "dirty" then reboot again. Here is a link to where i got the zips and instructions
http://forum.xda-developers.com/showpost.php?p=63305722&postcount=4842
in the instructions it says "RESET factory from within ROM (in Settings) - REQUIRED" . this step seemed strange as why would i do a factory reset on my device and erase everything i just did? would it not return it to original? I wasn't even sure if that was what he meant so i skipped that. After all was finished my signal was still all over the place could hardly make a call. it was bad. So once again I used lg flash tool and returned it to stock 4.4.2 10b, this time I wiped the data, cache, delvik and system. To my complete surprise the signal had not improved, in fact it could have actually been worse. As I said waaaaaay at the top of this post before i started all this i was running 4.4.2 12b, not sure how i ended up with 12b as i don't remember any upgrades after i downgraded to 10b and rooted. I froze the ota's with titanium backup but maybe 12b was pushed before i was able to freeze them. Anyway I couldn't figure out how to get 12b back now so I just flashed the 4.4.2 12b modem instead, This time I wiped cache and delvik before and after the flash then rebooted. This fixed my signal, everything seems normal now. no roaming and good signal. my software build however still shows 10b, but I guess thats correct since I only flashed the modem.
I really want 5.1.1 on my G3 but I need my signal too lol. can any one help me figure out how to get this done, can I flash the 12b modem on 5.1.1 this is where i got the file
http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641 it is way down the bottom of the page. Sorry for the extremely long post i just wanted to make sure i didn't leave any details out.
Any help would be greatly appreciated,
thanks in advance
@Allen227
i dont know if jasmine flashes the L modem when you flash it, but if it doesnt, that would be why you are having issues after flashing the rom.
other than that, i dont know what would cause modem issues.
bweN diorD;4132606 [user=7106818 said:
@Allen227[/user]
i dont know if jasmine flashes the L modem when you flash it, but if it doesnt, that would be why you are having issues after flashing the rom.
other than that, i dont know what would cause modem issues.
Click to expand...
Click to collapse
@Allen227
TL;DR but yes, JasmineROM flashes the appropriate modem. v9.0 only flashes the 24B modem because it doesn't contain a fuller set of the necessary partitions to allow the 35B modem to work by simply replacing the 24B modem with the 35B one.
You can flash the 35B bootstack after flashing JasmineROM 9.0 and the 9.1 update, or SkyDragon 6.x, but you must not be on the 35B bootstack before flashing either UNLESS you also flash the 35B bootstack again after flashing the ROM.
For reasons why: http://forum.xda-developers.com/showthread.php?p=64064555
Edit: I meant to add, the 35B boostack contains the 35B modem and everything needed for it to work with JasmineROM 9.0/9.1.
Hi, anybody from bosses ,plz help, sorry for noob querry... using g3 stock rom 4.4.2 and want to upgrade to lollipop and find jasmine ROM most votes. rooted my device with king root and installed twrp 2.8.7.0 recovry. downloaded jasmin ROM9.0, back up my current rom.
can u please guide me steps,
have i too flash kernal before jasmine ROM? or my existing stock kernal will work fine with jasmine 9.1
placed downloaded ROM in my download folder in phone memory [not in sd Card] , when i would boot in recovry in wipe cache delvik etc will it erase this rom and phone data too???
what if something gone rom? in my g3 there is no option of adb , adb does not work on my g3 dont know why.....
if something gone wrong , can i recover phone?
please see attached pics for some clarification...
sorry for,long post, actualy want to be safe ,,, as i am new for these things ..
tAheEr73 said:
Hi, anybody from bosses ,plz help, sorry for noob querry... using g3 stock rom 4.4.2 and want to upgrade to lollipop and find jasmine ROM most votes. rooted my device with king root and installed twrp 2.8.7.0 recovry. downloaded jasmin ROM9.0, back up my current rom.
can u please guide me steps,
have i too flash kernal before jasmine ROM? or my existing stock kernal will work fine with jasmine 9.1
placed downloaded ROM in my download folder in phone memory [not in sd Card] , when i would boot in recovry in wipe cache delvik etc will it erase this rom and phone data too???
what if something gone rom? in my g3 there is no option of adb , adb does not work on my g3 dont know why.....
if something gone wrong , can i recover phone?
please see attached pics for some clarification...
sorry for,long post, actualy want to be safe ,,, as i am new for these things ..
Click to expand...
Click to collapse
In the future, please do not post the same thing in two different threads. This is against XDA's forum rules. Also, no reason to hijack an only partially related thread. I answered you in the JasmineROM thread.
Sorry for rule breaking, actually i did not aware of that. will avoid surely next time and thanks for reply. hats off to you.
Thanks for your help guys. Last night I figured out my phone was allowing me to send and receive text messages and make outgoing calls but was completely unable to receive any calls. Signal still terribly inconsistent, it would be on 4g one minute then you could watch as it dropped then no service. There'd be no service for 3 or 4 minutes then it would repeat that cycle again. If I switch from global to cdma/let in settings it would immediately regain full signal. Then the cycle of it dropping out would start again. I got to looking through about phone in settings and realized my imei number was missing, all zeros. I'm assuming that probably is the root of my problems. Not sure what to do, I doubt Verizon can help. Phones not insured or under warranty anymore. I haven't researched this New development on te forums yet it got to late last night. If anyone knows of this problem I could use your help. Thanks
Allen227 said:
Thanks for your help guys. Last night I figured out my phone was allowing me to send and receive text messages and make outgoing calls but was completely unable to receive any calls. Signal still terribly inconsistent, it would be on 4g one minute then you could watch as it dropped then no service. There'd be no service for 3 or 4 minutes then it would repeat that cycle again. If I switch from global to cdma/let in settings it would immediately regain full signal. Then the cycle of it dropping out would start again. I got to looking through about phone in settings and realized my imei number was missing, all zeros. I'm assuming that probably is the root of my problems. Not sure what to do, I doubt Verizon can help. Phones not insured or under warranty anymore. I haven't researched this New development on te forums yet it got to late last night. If anyone knows of this problem I could use your help. Thanks
Click to expand...
Click to collapse
If you go into the main Verizon G3 section or possibly the non-Verizon G3 section and use the search field to search for "IMEI" you'll probably find a helpful thread. I think it involves the QPST program on a Windows PC. You'll need the IMEI that it's supposed to have, so hopefully have that on the box or Verizon's website lists it.
Sometimes that's seemed to happen for some people when flashing TOTs, KDZs or ROMs. I've been lucky, it hasn't happened to me through all my flashing over the past year. Once you get it fixed, rooted and put TWRP on, you can back up the IMEI partition in TWRP. It's called something else in TWRP like EI or something - I forget.
Good luck!
roirraW "edor" ehT said:
If you go into the main Verizon G3 section or possibly the non-Verizon G3 section and use the search field to search for "IMEI" you'll probably find a helpful thread. I think it involves the QPST program on a Windows PC. You'll need the IMEI that it's supposed to have, so hopefully have that on the box or Verizon's website lists it.
Sometimes that's seemed to happen for some people when flashing TOTs, KDZs or ROMs. I've been lucky, it hasn't happened to me through all my flashing over the past year. Once you get it fixed, rooted and put TWRP on, you can back up the IMEI partition in TWRP. It's called something else in TWRP like EI or something - I forget.
Good luck!
Click to expand...
Click to collapse
Thanks again I will check that out now
Allen227 said:
Thanks again I will check that out now
Click to expand...
Click to collapse
I have spent sooooo many hours on this. The qpst apk wont see my phone I have done everything the tutorials suggest. the instructions are only applicable if there are no issues, in other words, in a perfect world. I'm sure its something stupid and very simple but I don't even have a place to start. First, its hard to believe this works on all OS's, but it doesn't state anywhere what it is and isn't compatible with. that info would be helpful. i have spent 4 hours a day for over a week trying to get this fixed and I'm no closer than i was when I started. Very frustrating. I'm still open to suggestions or any help that can be offered.
I have a VS985, I have tried the latest CM13 nightly, the latest CM12.1 Snapshot, Fulmics 5.0, latest Resurrection Remix, and AICP MM, I have tried the 24B, 23C, 23B and 34B modems, none of them seem to work, I can call and text on any of these configurations, and i have tried setting my apn on all of these roms, but they either delete the apn automatically, despite me saving it, or it gives no option of adding an apn, im on the normal Verizon network, how on earth do I fix this?! Do I need to flash back to stock using a TOT or KDZ?
Yes, you've flashed so much that who knows what's going on behind the scenes. Flash the 10B TOT, re-root with the Stump app, then use TWRP Manager from the Play Store to install TWRP, then flash the bootstack and ROM you want. Preferably not CM-based nor international stock ROM based. They seem to require more fiddling with to get everything working reliably, especially Mobile Data. I recommend @xdabbeb 's VS985 v2.0 ROM based on 35B (5.1.1) or his stock 47A firmware, which is Marshmallow - the latter along with any further debloating via my debloat post in my signature below.
Of course, right after you flash 10B, before you root and install TWRP, you should verify that Mobile Data is working for you. If it's not, you might need to exchange your SIM card with Verizon for a new one - some others have had to do that because their old SIM card didn't allow Mobile Data to work any more, if I'm remembering correctly.
Ok, will try tomorrow, and i dont really want root anymore, this device is going to a family member thats not really into that stuff, so could i just flash the stock 35B and be done, unless data still doesnt work, in which case, ill go to verizon.
Also, earlier, i was running CM13, and tried to flash the 35B modem again (might want to stop trying) and my twrp crashed to the twrp splash, and i reflashed the 35B, wiped cache, rebooted to system, and it put it into an infinite LG splash logo loop, had to reboot to stock recovery and wipe cache to get to twrp, reflashed my rom, wiped cache and dalvik, and it boot fine after that.
TOTs flash more partitions than KDZs. Sometimes flashing a TOT is necessary to fix strange issues that even flashing KDZs won't. So I suggest down the 10B TOT and then flash the 47A KDZ and be done with it. It's still double check mobile data on 10B.
So theres no 35B TOT? Currently when i try to flash KDZ files, it fails, it detects the device fine, but wont install the software.
When install TWRP and flashed CM12.1 for the first time, my device was on 5.0.1, and data worked fine on CM12.1, but now it doesnt.
Nick80835 said:
So theres no 35B TOT? Currently when i try to flash KDZ files, it fails, it detects the device fine, but wont install the software.
When install TWRP and flashed CM12.1 for the first time, my device was on 5.0.1, and data worked fine on CM12.1, but now it doesnt.
Click to expand...
Click to collapse
No, the only TOT available for our device is 10B. You can always take the OTAs up to 47A from there if you want (assuming you're using an activated Verizon SIM), although it's harder to root after 10B, and harder to put TWRP on after 12B, if that's what you ultimately want.
Are you using the original USB cable with a USB 2.0 port preferably directly connected to the PC - not through a USB hub?
Im using an Insignia cable, connected directly to my pc, nothing in between, I dont think i have the original cable anymore.
Nick80835 said:
Im using an Insignia cable, connected directly to my pc, nothing in between, I dont think i have the original cable anymore.
Click to expand...
Click to collapse
Not saying it is definitely, but not using the original cable could be the problem.
Downloaded the TOT, will try later, ill report back.
When it was installing the TOT, my kitten decided to jiggle the cable (found my original cable!) and caused the phone toose connection, I could still get into dl mode, but that scared the crap out of me, it was sending system when it disconnected.
I installed the TOT, data works, updating, currently at 23C, thanks for the tips.
Successfully went from 10B to 47A without an issue, factory reset on 47A, everything working very good, data has no problems, thanks, MM is very good on this device, but AOSP seems to kill it for me, even LGs skin runs better!
Nick80835 said:
When it was installing the TOT, my kitten decided to jiggle the cable (found my original cable!) and caused the phone toose connection, I could still get into dl mode, but that scared the crap out of me, it was sending system when it disconnected.
Click to expand...
Click to collapse
Nick80835 said:
I installed the TOT, data works, updating, currently at 23C, thanks for the tips.
Click to expand...
Click to collapse
Nick80835 said:
Successfully went from 10B to 47A without an issue, factory reset on 47A, everything working very good, data has no problems, thanks, MM is very good on this device, but AOSP seems to kill it for me, even LGs skin runs better!
Click to expand...
Click to collapse
Glad it worked, thanks for the update! Cats, so cute but so rotten sometimes. We have one too. ?
They love cables! Especially when they are important.
Not sure why mods locked my other post, but I DO NOT have an international version of LG G3, I have a Verizon version, VS985.
And this issue is not about Fulmic's ROM, but is about Xdabebb's 47a Marshmallow ROM which is a stock rom.
So I am going to repost, in hope of getting the help I was looking for originally.
I'm pretty tired of my LG G3 which I've owned now for a few months. It is the VS985 version. Purchased brand new.
I started off on the stock Kitkat it came with. Connectivity with Verizon 4g was fine, but the phone overheated regularly.
Then I updated to Fulmics 5.2, which worked okay, but only gave me slow 3g data.
Next I reverted all the way back to stock 10b, and then tried Xdabebb's Stock 47a. The rom works fine, but 4g connectivity is ****! I get constant blinking triangles (roaming) even though roaming is turned off. Worse yet, I don't get phone calls or texts half the time, and it constantly loses data connection. I got a new sim card, which works fine in my Nexus 6, but fails to be consistent in my LG G3.
Here's my questions:
1. Is there a fix with XDAbebb's 47a? Should I reflash the 35b bootstack?
2. If XDAbebb's 47a is the problem, is there a ROM that people have had good Verizon experience on?
3. Or should I just sell my LG G3 and move onto another phone or go back to my nexus 6 (which I like but it's so huge!)
I don't want to waste a lot of more time on this.
Mods, please don't lock this, as it is a different set of questions/issues from my other Fulmic's thread.
android94301 said:
Next I reverted all the way back to stock 10b, and then tried Xdabebb's Stock 47a. The rom works fine, but 4g connectivity is ****! I get constant blinking triangles (roaming) even though roaming is turned off. Worse yet, I don't get phone calls or texts half the time, and it constantly loses data connection. I got a new sim card, which works fine in my Nexus 6, but fails to be consistent in my LG G3.
Here's my questions:
1. Is there a fix with XDAbebb's 47a? Should I reflash the 35b bootstack?
2. If XDAbebb's 47a is the problem, is there a ROM that people have had good Verizon experience on?
3. Or should I just sell my LG G3 and move onto another phone or go back to my nexus 6 (which I like but it's so huge!)
I don't want to waste a lot of more time on this.
Mods, please don't lock this, as it is a different set of questions/issues from my other Fulmic's thread.
Click to expand...
Click to collapse
1. There's nothing that needs fixing in @xdabbeb 's stock 47A firmware, at least for the majority of people. It's as completely stock 47A as can be possible while being rooted and still being able to get into TWRP - there's no other differences from stock unrooted 47A. The 35B Bootstack is part of what's necessary in order to have a working modem while still being able to get into TWRP.
I doubt if reflashing the bootstack will make a difference but it doesn't hurt anything either. Does your Settings/About menu list a baseband and an IMEI for your device? If it does, it's doubtful that reflashing the bootstack will help, and that would only help if it said you have no baseband, or the wrong one. Just reflash it though if you have any doubts, like I said, it doesn't hurt anything to flash it.
2. @xdabbeb 's VS985 v2.0 ROM (based on 35B) is overall my very favorite ROM although I've been using his 47A and the 46A before it ever since he released them, along with heavy debloating. His VS985 v2.0 ROM is more heavily modified from stock 35B which is why he differentiates between his VS985 v2.0 ROM and his stock 47A firmware and although 47A in general is really smooth, you can tell the pride he took doing the work he did on the 2.0 ROM.
3. Only you can decide this. Have you tried flashing the 10B TOT (which will wipe your data and internal storage too)? As @xdabbeb taught me and I've personally witnessed when I checked into it, TOTs flash more partitions than KDZs do. Flashing the 10B TOT can fix things that flashing any KDZ or ROM won't. I had a weird problem several months ago that no matter what ROM or KDZ (including 10B) I flashed, the problem persisted. It wasn't until I flashed the 10B TOT that the problem went and stayed away.
It's very common that people that flash several ROMs, especially when some of them are CM/AOSP based and/or international stock ROM ports that they have trouble with mobile data afterward until they flash back to stock. I realize (I think you said) that you flashed the KDZ but try the TOT and go from there. Once you flash it, verify if everything is working 100% okay before rooting, putting TWRP on and flashing anything else. Then once you do that, go straight to flashing whichever stock-based ROM you decide on including the appropriate bootstack.
4. Please mail me your Nexus 6 so I have a new toy to play with.
Thanks, and see my replies below.
roirraW "edor" ehT said:
1. There's nothing that needs fixing in @xdabbeb 's stock 47A firmware, at least for the majority of people. It's as completely stock 47A as can be possible while being rooted and still being able to get into TWRP - there's no other differences from stock unrooted 47A. The 35B Bootstack is part of what's necessary in order to have a working modem while still being able to get into TWRP.
I doubt if reflashing the bootstack will make a difference but it doesn't hurt anything either. Does your Settings/About menu list a baseband and an IMEI for your device? If it does, it's doubtful that reflashing the bootstack will help, and that would only help if it said you have no baseband, or the wrong one. Just reflash it though if you have any doubts, like I said, it doesn't hurt anything to flash it.
[My setting DO not list an IMEI. Is there a problem I need to fix?]
2. @xdabbeb 's VS985 v2.0 ROM (based on 35B) is overall my very favorite ROM although I've been using his 47A and the 46A before it ever since he released them, along with heavy debloating. His VS985 v2.0 ROM is more heavily modified from stock 35B which is why he differentiates between his VS985 v2.0 ROM and his stock 47A firmware and although 47A in general is really smooth, you can tell the pride he took doing the work he did on the 2.0 ROM.
[Thanks maybe I'll try this 2.0 version.]
3. Only you can decide this. Have you tried flashing the 10B TOT (which will wipe your data and internal storage too)? As @xdabbeb taught me and I've personally witnessed when I checked into it, TOTs flash more partitions than KDZs do. Flashing the 10B TOT can fix things that flashing any KDZ or ROM won't. I had a weird problem several months ago that no matter what ROM or KDZ (including 10B) I flashed, the problem persisted. It wasn't until I flashed the 10B TOT that the problem went and stayed away.
[Yes, I flashed the Tot file to 10b, before I went to 47A.]
It's very common that people that flash several ROMs, especially when some of them are CM/AOSP based and/or international stock ROM ports that they have trouble with mobile data afterward until they flash back to stock. I realize (I think you said) that you flashed the KDZ but try the TOT and go from there. Once you flash it, verify if everything is working 100% okay before rooting, putting TWRP on and flashing anything else. Then once you do that, go straight to flashing whichever stock-based ROM you decide on including the appropriate bootstack.
[OK, will try the stock Tot 10b again and make sure it's all okay before rooting or upgrading. How do I fix the IMEI though? ]
4. Please mail me your Nexus 6 so I have a new toy to play with.
Click to expand...
Click to collapse
[What's your address? JK, I actually love my Nexus 6 but sometimes want a smaller phone to carry.]
android94301 said:
Thanks, and see my replies below.
Click to expand...
Click to collapse
You're welcome!
[My setting DO not list an IMEI. Is there a problem I need to fix?]
Click to expand...
Click to collapse
I'm attaching screenshots for where you should find the IMEI on 47A (Settings/About/Status) Just to be clear, you're saying you found the spot the IMEI should be in but it's not listed there? And you do have a baseband listed (Settings/About/Software info)? If so, then not having an IMEI is definitely the problem.
[Yes, I flashed the Tot file to 10b, before I went to 47A.]
Click to expand...
Click to collapse
It probably won't make any difference then if you went straight from the 10B TOT, Stump root, TWRP to 35B Bootstack and 47A firmware. Sounds like the no IMEI thing is the problem.
[OK, will try the stock Tot 10b again and make sure it's all okay before rooting or upgrading. How do I fix the IMEI though? ]
Click to expand...
Click to collapse
You can't make phone calls either, right? I'm no expert on fixing no IMEI - I've never had to do that personally. When in TWRP, I use it to backup the EFS which I believe includes the IMEI, so that if it should get lost (which happens sometimes when flashing KDZs and TOTs), I can just restore it via TWRP.
If you don't have a TWRP backup of your EFS, then assuming you have the box the phone came in, or some record of what the IMEI was, I believe you have to use some Windows software - maybe QPST - to manually type the IMEI back in the right place. I know there's threads in the General and Q&A section, and probably those sections in the non-Verizon G3 forums too. I'd have to search for the threads myself though.
[What's your address? JK, I actually love my Nexus 6 but sometimes want a smaller phone to carry.]
Click to expand...
Click to collapse
Every once in a while I'm tempted to go Nexus, but I guess none have attracted me enough yet, either feature/storage/camera/review/size and/or price-wise. I don't think I'd like anything bigger than the G3.
You are a genius! Saved my LG G3 from Craigslist
roirraW "edor" ehT said:
You're welcome!
I'm attaching screenshots for where you should find the IMEI on 47A (Settings/About/Status) Just to be clear, you're saying you found the spot the IMEI should be in but it's not listed there? And you do have a baseband listed (Settings/About/Software info)? If so, then not having an IMEI is definitely the problem.
It probably won't make any difference then if you went straight from the 10B TOT, Stump root, TWRP to 35B Bootstack and 47A firmware. Sounds like the no IMEI thing is the problem.
You can't make phone calls either, right? I'm no expert on fixing no IMEI - I've never had to do that personally. When in TWRP, I use it to backup the EFS which I believe includes the IMEI, so that if it should get lost (which happens sometimes when flashing KDZs and TOTs), I can just restore it via TWRP.
If you don't have a TWRP backup of your EFS, then assuming you have the box the phone came in, or some record of what the IMEI was, I believe you have to use some Windows software - maybe QPST - to manually type the IMEI back in the right place. I know there's threads in the General and Q&A section, and probably those sections in the non-Verizon G3 forums too. I'd have to search for the threads myself though.
Every once in a while I'm tempted to go Nexus, but I guess none have attracted me enough yet, either feature/storage/camera/review/size and/or price-wise. I don't think I'd like anything bigger than the G3.
Click to expand...
Click to collapse
Thanks for your help. As you can see from the pics I've attached, baseband is fine, and there is no IMEI. Must have gotten nuked somehow when I went from Fulmics to 10b to 47A. I have an EFS backup in TWRP, so will try to restore the EFS partition.
I just did, and my IMEI is back, although phone number is blank, IMS registered status is Not Registered, ICCID says unknown. Let's try putting the sim card back in and see what happens.
IMEI is there, as is ICCID. IMS is still not registered. Phone number now shows up. As does PRL. Just tried phone calls and they now work, let's try a text. Works!!!!
Now lets try a data test. Speedtest now is off the charts! 74mbps down, and 13mbps up! Can't beat that.
roirraW "edor" ehT you are a genius, seems like that solved it. Now I guess I should make another nandroid backup while I've got everything working.
One last question, is the improvement of XDAbebb's VS985 v2.0 debloated enough to make it worth going from 47a to that one? Thanks again.
And no stupid blinking triangle of roaming! Tried Google Play store and now things install rapidly.
android94301 said:
Thanks for your help. As you can see from the pics I've attached, baseband is fine, and there is no IMEI. Must have gotten nuked somehow when I went from Fulmics to 10b to 47A. I have an EFS backup in TWRP, so will try to restore the EFS partition.
I just did, and my IMEI is back, although phone number is blank, IMS registered status is Not Registered, ICCID says unknown. Let's try putting the sim card back in and see what happens.
IMEI is there, as is ICCID. IMS is still not registered. Phone number now shows up. As does PRL. Just tried phone calls and they now work, let's try a text. Works!!!!
Now lets try a data test. Speedtest now is off the charts! 74mbps down, and 13mbps up! Can't beat that.
roirraW "edor" ehT you are a genius, seems like that solved it. Now I guess I should make another nandroid backup while I've got everything working.
One last question, is the improvement of XDAbebb's VS985 v2.0 debloated enough to make it worth going from 47a to that one? Thanks again.
And no stupid blinking triangle of roaming! Tried Google Play store and now things install rapidly.
Click to expand...
Click to collapse
Both roms are excellent xdabebbs 2.0 is pretty slimmed down and runs really smooth. And his 47A is as close to stock marshmallow as you can get but still being rooted. I'm always flashing back and forth between the two, sometimes a few times per week lol I would recommend either one since they are both awesome. If you run 47A you can use some debloating zips that the warrior has made, and remove a lot of bloat or only take out what you want. I hope this helps in anyway and glad you got your g3 working now.
Sent from my g3 using XDA Labs
android94301 said:
Thanks for your help. As you can see from the pics I've attached, baseband is fine, and there is no IMEI. Must have gotten nuked somehow when I went from Fulmics to 10b to 47A. I have an EFS backup in TWRP, so will try to restore the EFS partition.
I just did, and my IMEI is back, although phone number is blank, IMS registered status is Not Registered, ICCID says unknown. Let's try putting the sim card back in and see what happens.
IMEI is there, as is ICCID. IMS is still not registered. Phone number now shows up. As does PRL. Just tried phone calls and they now work, let's try a text. Works!!!!
Now lets try a data test. Speedtest now is off the charts! 74mbps down, and 13mbps up! Can't beat that.
[URL=" "edor" ehT[/I][/COLOR][/URL] you are a genius, seems like that solved it. Now I guess I should make another nandroid backup while I've got everything working.
One last question, is the improvement of XDAbebb's VS985 v2.0 debloated enough to make it worth going from 47a to that one? Thanks again.
And no stupid blinking triangle of roaming! Tried Google Play store and now things install rapidly.
Click to expand...
Click to collapse
Awesome! You're welcome. I'm glad it was that relatively simple and that you had an EFS Backup! I (think I) keep a cloud backup of just an EFS TWRP backup of all of my wife's and my devices just in case. Much simpler than fooling around in proprietary software.
I've just luckily seen enough people have the no IMEI problem enough times on this device - glad it hasn't happened to me yet.