Related
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
I've got a Rooted (and Bumped) G3 that will absolutely not get out of PTP mode. I've frozen system updates, Unfrozen it, rebooted, tried 30 different USB plugs.
I'm running the stock rom (11B) I believe.
I can't even get the phone to go to MTP mode without being connected.
Help!
eallan said:
I've got a Rooted (and Bumped) G3 that will absolutely not get out of PTP mode. I've frozen system updates, Unfrozen it, rebooted, tried 30 different USB plugs.
I'm running the stock rom (11B) I believe.
I can't even get the phone to go to MTP mode without being connected.
Help!
Click to expand...
Click to collapse
I actually had this EXACT problem. I was convinced my phone was fried until I installed a Lollipop ROM and it worked.
Turns out something is broken/conflicts in the stock ROM from one of the last two updates (probably 11b). I couldn't even select MTP mode, it would just select whatever the prior mode was (that includes mounting that stupid Verizon installer forever)
I was never able to fix it on the stock ROM. I installed Jasmine and never looked back
ulbador said:
I actually had this EXACT problem. I was convinced my phone was fried until I installed a Lollipop ROM and it worked.
Turns out something is broken/conflicts in the stock ROM from one of the last two updates (probably 11b). I couldn't even select MTP mode, it would just select whatever the prior mode was (that includes mounting that stupid Verizon installer forever)
I was never able to fix it on the stock ROM. I installed Jasmine and never looked back
Click to expand...
Click to collapse
Thanks. For the advice. It's incredibly annoying.
How are you liking Jasmine? What's the main difference with it?
eallan said:
Thanks. For the advice. It's incredibly annoying.
How are you liking Jasmine? What's the main difference with it?
Click to expand...
Click to collapse
I'm on the 4.0 Version and it's practically perfect. It's 100% stock (which eliminates the problems with Bluetooth/QI Charging/etc from the other ROMs) but completely debloated. You can choose to install all or none of the GApps/VerizionCrap/LGCrap/AmazonCrap/etc
eallan said:
I've got a Rooted (and Bumped) G3 that will absolutely not get out of PTP mode. I've frozen system updates, Unfrozen it, rebooted, tried 30 different USB plugs.
I'm running the stock rom (11B) I believe.
I can't even get the phone to go to MTP mode without being connected.
Help!
Click to expand...
Click to collapse
ulbador said:
I actually had this EXACT problem. I was convinced my phone was fried until I installed a Lollipop ROM and it worked.
Turns out something is broken/conflicts in the stock ROM from one of the last two updates (probably 11b). I couldn't even select MTP mode, it would just select whatever the prior mode was (that includes mounting that stupid Verizon installer forever)
I was never able to fix it on the stock ROM. I installed Jasmine and never looked back
Click to expand...
Click to collapse
I don't know anything about the issues you guys are having, as I've never had them myself, however, just for future reference and to avoid further potential confusion to others, there is no "11B" update. There is a 10B (initial public launch version), an 11C (version that blocked root exploit), and a 12B (the version which is the latest, and which added VoLTE). Just commenting because I've seen a lot of posts incorrectly referencing 11B, and trying to avoid confusion for those who may be newer to the forums.
Thanks Buddy, installing now.
ulbador said:
I actually had this EXACT problem. I was convinced my phone was fried until I installed a Lollipop ROM and it worked.
Turns out something is broken/conflicts in the stock ROM from one of the last two updates (probably 11b). I couldn't even select MTP mode, it would just select whatever the prior mode was (that includes mounting that stupid Verizon installer forever)
I was never able to fix it on the stock ROM. I installed Jasmine and never looked back
Click to expand...
Click to collapse
ohlin5 said:
I don't know anything about the issues you guys are having, as I've never had them myself, however, just for future reference and to avoid further potential confusion to others, there is no "11B" update. There is a 10B (initial public launch version), an 11C (version that blocked root exploit), and a 12B (the version which is the latest, and which added VoLTE). Just commenting because I've seen a lot of posts incorrectly referencing 11B, and trying to avoid confusion for those who may be newer to the forums.
Click to expand...
Click to collapse
After installing a "12B" rom (Jasmine, as recommend) MTP now works fine. Man that was annoying.
eallan said:
After installing a "12B" rom (Jasmine, as recommend) MTP now works fine. Man that was annoying.
Click to expand...
Click to collapse
Glad to hear you got it figured out!
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.
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
I have a v30 that start out as a VS996. I unlocked and rooted using WTF and then crossed flashed to US998 using LGUP. I stalled 20 F, G and H as they were released and everything was running fine. I just installed MAGISK 19.01 and it screwed up my Tasker Hotspot profile so I restored a TWRP backup which took me back to 20E. I have since upgraded back to 20H.
Now when I reboot, it occasionaly hangs for a long time (45sec) on the V30 THINQ logo screen and then boots into fastboot. Hitting the power button reboots the phone back to the system (most of the time) and everything is fine.
I suspect something is corrupted but I have not clue what to do next.
Lenster45 said:
I just installed MAGISK 19.01 and it screwed up my Tasker Hotspot profile so I restored a TWRP backup which took me back to 20E. I have since upgraded back to 20H.
Now when I reboot, it occasionaly hangs for a long time (45sec) on the V30 THINQ logo screen and then boots into fastboot. Hitting the power button reboots the phone back to the system (most of the time) and everything is fine.
I suspect something is corrupted but I have not clue what to do next.
Click to expand...
Click to collapse
Are you still using Magisk 19? Just curious. Some people have had trouble with it. I was hoping 19.1 stable would be the fix.
ChazzMatt said:
Are you still using Magisk 19? Just curious. Some people have had trouble with it. I was hoping 19.1 stable would be the fix.
Click to expand...
Click to collapse
I uninstalled 19.0 and went back to 18.1 will see what happens.