Related
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
and finglha
bradleyrogers89 said:
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
Click to expand...
Click to collapse
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
lossofsilence said:
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
Click to expand...
Click to collapse
Yea it has happened to me too, I just powered off with a long press on the 'N' and power button. Restarted and it worked fine.
Actually i'm on 10.1 too.
This thing happens sometime. This is normal for early alfa soft.
On first clean install test i had 3 or more times stop on Cyanogen logo. But it started work on fourth time. Same happened with second clean install too (messed Adnroid to death with my hard tests and modifications ). Power OFF/On have sometime magical power.
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
bradleyrogers89 said:
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
Click to expand...
Click to collapse
I have no problem adjusting brightness on 1/28
codya321 said:
I have no problem adjusting brightness on 1/28
Click to expand...
Click to collapse
It's weird. I couldn't get it to work without using the Tablet UI. Once I switched, it started working. Oh well, it's working fine now. Thanks for the help, you guys are the best.
CM 10.1 needs some time for settle. Then it works wthout lag
Sent from my GT-I9100 using Tapatalk 2
So after 8 hours my battery still said 100% and even shut off due to dead battery and it still said 100% full. In TWRP it also shows 100% full. Any ideas? I have it on the turbo charger now, since it died, and will wait about 2 hours then try to reset battery stats. Not sure what else to try. Nothing new installed, phone is stock other than rooted and TRWP.
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
huh?
The phone was rooted the day I got it, Nov 9th, and it just started doing it today. So how does root automatically cause the issue?
Anyway, any ideas would be great I think resetting the batterystats has worked just curious what may have started it.
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
I've never had issues from just rooting. Rooting a phone doesn't cause issues but rather installing root apps and changing things causes issues. I would try to flash back to stock (backup data first) and then root it again to see of that fixes it.
Also did you use CF-Autoroot or one of the tool kits?
I fixed the issue, after that battery died I let it charge for about 4 hours with the quick charger and then reset the battery stats by using an app that deletes the batterystats.bin file. Then did a reboot and now the battery level is no longer stuck on 100%.
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
lifeisfun said:
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
Click to expand...
Click to collapse
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
root has nothing to do with breaking your phone. all root does is give you superuser permission. what breaks phones are dirty hacks that you yourself chose to use.
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
lifeisfun said:
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
Click to expand...
Click to collapse
I would just put it down to "OS Confusion "
danarama said:
I would just put it down to "OS Confusion "
Click to expand...
Click to collapse
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
lifeisfun said:
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
Click to expand...
Click to collapse
Yeah maybe battery firmware confusion. I don't know where TWRP gets its reading from.
Still Works!
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
Thanks.
I have a Sunshine unlocked Turbo that has recently began randomly shutting down. I have tried a few roms to see if there was any difference, but couldn't get anything to work. I also tried installing a stock, unmodified rom to no avail (kept getting an error on the install). I could get CM12.1 installed the best, but after a couple of minutes it would shut down again. I tried wiping everything off the phone through TWRP (system, cache, dalvik, and internal storage) to no avail. I was able to get it to run longer on CM without GAPPS, about 10 minutes or so before the shutdown. Any ideas?
EDIT:
Not sure what the exact issue was, but I downloaded the Droid Turbo OEM from HERE. Waited 8 hours to download (original links don't work anymore and the mirror is stupid and charges for a fast download), unzipped the file, then ran the VRZ_XT1254_SU4TL-44_44_CFC.bat and it booted right up and has been working fine. I then simply installed TWRP, flashed SuperSU, then edited the build.prop to get hotspot working.
flametail2518 said:
I have a Sunshine unlocked Turbo that has recently began randomly shutting down. I have tried a few roms to see if there was any difference, but couldn't get anything to work. I also tried installing a stock, unmodified rom to no avail (kept getting an error on the install). I could get CM12.1 installed the best, but after a couple of minutes it would shut down again. I tried wiping everything off the phone through TWRP (system, cache, dalvik, and internal storage) to no avail. I was able to get it to run longer on CM without GAPPS, about 10 minutes or so before the shutdown. Any ideas?
Click to expand...
Click to collapse
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
TheSt33v said:
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
Click to expand...
Click to collapse
Mine just shuts off around 13~17% percent battery without warning. Not sure why though.
GreaterLesser said:
Mine just shuts off around 13~17% percent battery without warning. Not sure why though.
Click to expand...
Click to collapse
It's a long shot, but you might want to try a battery calibration app. You phone could be reading 13-17% when it's actually at 0%. I think it's more likely that it's some sort of hardware issue, though.
TheSt33v said:
It's a long shot, but you might want to try a battery calibration app. You phone could be reading 13-17% when it's actually at 0%. I think it's more likely that it's some sort of hardware issue, though.
Click to expand...
Click to collapse
Even though the percentage aforementioned is read from the bootloader? I get this percentage when my phone is off and I plug in the changer it read the battery is charged to 13~17%.
GreaterLesser said:
Even though the percentage aforementioned is read from the bootloader? I get this percentage when my phone is off and I plug in the changer it read the battery is charged to 13~17%.
Click to expand...
Click to collapse
Honestly, I have no idea.
I agree yes try recalibrating the battery. Or do a clean flash. It should recalibrate the battery when you do this.
The calibration is simply a file based on battery reads.
TheSt33v said:
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
Click to expand...
Click to collapse
It is immediately shutting down without a warning.
I'll try the VUA tomorrow and see how that goes. Hopefully a fresh, OEM install will fix the issue so I can get CM12 installed.
flametail2518 said:
It is immediately shutting down without a warning.
I'll try the VUA tomorrow and see how that goes. Hopefully a fresh, OEM install will fix the issue so I can get CM12 installed.
Click to expand...
Click to collapse
Hmm. That sounds like a hardware issue to me, but you'll find out once you run the upgrade assistant.
I had a problem once where the phone seemed like it was powering off, but it was actually just never waking up when the screen went dark. Reflashing all images didn't help. I ended up sending it in to Motorola for a warranty replacement, which was a surprisingly easy process.
My phone likes to shut down around 1-8% without warning, but it does say Powering down as it does it. It's kind of annoying, but I'm sure that's not similar to what you're experiencing.
TheSt33v said:
Hmm. That sounds like a hardware issue to me, but you'll find out once you run the upgrade assistant.
I had a problem once where the phone seemed like it was powering off, but it was actually just never waking up when the screen went dark. Reflashing all images didn't help. I ended up sending it in to Motorola for a warranty replacement, which was a surprisingly easy process.
Click to expand...
Click to collapse
I can't get VUA or the Repair Assistant to even recognize the device. Are there any guides to flashing the stock firmware? I can't seem to find one online and it's a bit of a pain. I'm glad I have a N5X to use instead.
flametail2518 said:
I can't get VUA or the Repair Assistant to even recognize the device. Are there any guides to flashing the stock firmware? I can't seem to find one online and it's a bit of a pain. I'm glad I have a N5X to use instead.
Click to expand...
Click to collapse
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
TheSt33v said:
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
Click to expand...
Click to collapse
See previous post. I got it fixed today.
Sent from my SHIELD Tablet using Tapatalk
TheSt33v said:
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
Click to expand...
Click to collapse
If I just double click the .bat it automatically flashes everything. Is that the wrong way? There's no "entry for Quark" in the .bat.
It worked for about 48 hours this time before it did another shutdown.
flametail2518 said:
If I just double click the .bat it automatically flashes everything. Is that the wrong way? There's no "entry for Quark" in the .bat.
It worked for about 48 hours this time before it did another shutdown.
Click to expand...
Click to collapse
Sorry, I missed a step. Yes, double clicking on the .bat file should work fine. I got confused. If doing that didn't fix it, you might want to think about getting a warranty replacement if possible, or a new phone. Motorola has an option where you pay $25 and they ship you a new phone without inspecting the old one. It even comes in the original packaging, which makes me suspect that it's actually new, not refurbished. This is the option I chose when I replaced the phone that I had modified with Moforoot. The process went smoothly despite my "modified" system status.
TheSt33v said:
Sorry, I missed a step. Yes, double clicking on the .bat file should work fine. I got confused. If doing that didn't fix it, you might want to think about getting a warranty replacement if possible, or a new phone. Motorola has an option where you pay $25 and they ship you a new phone without inspecting the old one. It even comes in the original packaging, which makes me suspect that it's actually new, not refurbished. This is the option I chose when I replaced the phone that I had modified with Moforoot. The process went smoothly despite my "modified" system status.
Click to expand...
Click to collapse
I'll have to try that. I dropped my VZW insurance when I got the N5X since Nexus Protect is better and cheaper than VZW. Do I just go through Motorola's site for it?
Sent from my Nexus 5X using Tapatalk
flametail2518 said:
I'll have to try that. I dropped my VZW insurance when I got the N5X since Nexus Protect is better and cheaper than VZW. Do I just go through Motorola's site for it?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Here you go: https://motorola-global-portal.custhelp.com/app/mcp/service/session/
Click on "request a repair" and follow the prompts. You won't even have to interact with a person.
One caveat though: I read recently that someone tried to do this and they tried to give him a Droid Turbo 2 as a replacement. I'm not saying that will happen, but it's something to be aware of.
TheSt33v said:
Here you go: https://motorola-global-portal.custhelp.com/app/mcp/service/session/
Click on "request a repair" and follow the prompts. You won't even have to interact with a person.
One caveat though: I read recently that someone tried to do this and they tried to give him a Droid Turbo 2 as a replacement. I'm not saying that will happen, but it's something to be aware of.
Click to expand...
Click to collapse
Thanks for this! It was covered and I can get it done for free since I don't need my Turbo.
flametail2518 said:
Thanks for this! It was covered and I can get it done for free since I don't need my Turbo.
Click to expand...
Click to collapse
I avoided the free option since I got the impression that they inspect your phone first to ensure that nothing is wrong with it that would make its warranty void. Like, say, an unlocked bootloader. But it could be that they just check for physical damage. I dunno. Good luck!
TheSt33v said:
I avoided the free option since I got the impression that they inspect your phone first to ensure that nothing is wrong with it that would make its warranty void. Like, say, an unlocked bootloader. But it could be that they just check for physical damage. I dunno. Good luck!
Click to expand...
Click to collapse
The free option said they look for physical damage first then go on to the repair.
Basically, I had to do a battery pull on my LG D415, after the better pull, I booted up the device like I normally would. After starting the device, I am now experiencing an issue where I am unable to get past the CM13 boot logo, where it will continue the booting animation with the CM13 logo, and then the device will just shut down. Attached is a video of this happening.
Is this essentially the inevitable bootloop that is found in many Android devices? If so, how can I go about fixing the issue? I had a lot of stuff on the device and would prefer to not have to reflash anything, as I spent already hours setting up the device in the first place.
Here is the video: https://www.youtube.com/watch?v=1kgh-DFxKBg&feature=youtu.be
darkgiant said:
Basically, I had to do a battery pull on my LG D415, after the better pull, I booted up the device like I normally would. After starting the device, I am now experiencing an issue where I am unable to get past the CM13 boot logo, where it will continue the booting animation with the CM13 logo, and then the device will just shut down. Attached is a video of this happening.
Is this essentially the inevitable bootloop that is found in many Android devices? If so, how can I go about fixing the issue? I had a lot of stuff on the device and would prefer to not have to reflash anything, as I spent already hours setting up the device in the first place.
Here is the video:
&feature=youtu.be
Click to expand...
Click to collapse
Usually a bootloop restarts your phone or doesn't pass the CM (in this case) logo.. I think u can classify as bootloop nevertheless.. u can try reflashing the same version of cm13 on top of that.. you maybe won't loose anything important but I don't know what you had done in your device.. it's just my opinion..
Warimation said:
Usually a bootloop restarts your phone or doesn't pass the CM (in this case) logo.. I think u can classify as bootloop nevertheless.. u can try reflashing the same version of cm13 on top of that.. you maybe won't loose anything important but I don't know what you had done in your device.. it's just my opinion..
Click to expand...
Click to collapse
So if I were to flash CM13 (without wiping anything) I should be safe in terms of not wiping anything? Would I also need to flash GAPPS again?
darkgiant said:
So if I were to flash CM13 (without wiping anything) I should be safe in terms of not wiping anything? Would I also need to flash GAPPS again?
Click to expand...
Click to collapse
I don't know.. again it's your decision.. but if your going to flash, try 1st without Gapps.. if they don't stay then flash Gapps.. btw I saw u want to download cm13.. that's a bummer because cyanogen is over.. they closed CyanogenMod OS. So no more cm's for anyone. Instead u have lineage OS that's made by CM team and we don't have official. It's the same with changed brand.. I don't know if you will succeed downloading a cm13 version but search here in L90 forums.. maybe you find a solution..
Warimation said:
I don't know.. again it's your decision.. but if your going to flash, try 1st without Gapps.. if they don't stay then flash Gapps.. btw I saw u want to download cm13.. that's a bummer because cyanogen is over.. they closed CyanogenMod OS. So no more cm's for anyone. Instead u have lineage OS that's made by CM team and we don't have official. It's the same with changed brand.. I don't know if you will succeed downloading a cm13 version but search here in L90 forums.. maybe you find a solution..
Click to expand...
Click to collapse
Oh yeah, I totally forgot that CyanogenMod closed down its OS. This is a huge bummer, as this essentially means I need to find a new ROM anyways...
Any suggestions? Anything super stable, and runs fast is what I was looking for. If not, I might just go back to the stock ROM and stay rooted or something.
darkgiant said:
Oh yeah, I totally forgot that CyanogenMod closed down its OS. This is a huge bummer, as this essentially means I need to find a new ROM anyways...
Any suggestions? Anything super stable, and runs fast is what I was looking for. If not, I might just go back to the stock ROM and stay rooted or something.
Click to expand...
Click to collapse
I'm currently using Aicp os. Its super fast and it's working good.. it's nougat so expect a better battery life but still have some bugs.. It's going to become official.
forum.xda-developers.com/lg-l90/development/rom-android-ice-cold-project-12-1-t3559656/page3
Warimation said:
I'm currently using Aicp os. Its super fast and it's working good.. it's nougat so expect a better battery life but still have some bugs.. It's going to become official.
forum.xda-developers.com/lg-l90/development/rom-android-ice-cold-project-12-1-t3559656/page3
Click to expand...
Click to collapse
Thanks for the advice, I'll go ahead and take a look at it! As long as it's stable, and good to use as a daily driver, it works for me.
Though, I am currently having an issue with booting into TWRP to flash the ROMs, as I keep trying the volume up + power button steps to get into recovery, but it's just sending me directly to the CM13 loading logo. And because I can't even get into CM13 because of the boot issue, I am not sure if I can connect the device to a computer... Any advice on how I can fix this issue?
darkgiant said:
Thanks for the advice, I'll go ahead and take a look at it! As long as it's stable, and good to use as a daily driver, it works for me.
Though, I am currently having an issue with booting into TWRP to flash the ROMs, as I keep trying the volume up + power button steps to get into recovery, but it's just sending me directly to the CM13 loading logo. And because I can't even get into CM13 because of the boot issue, I am not sure if I can connect the device to a computer... Any advice on how I can fix this issue?
Click to expand...
Click to collapse
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. doesn't bring root by default but just flash SuperSU 2.79 (last version I think) and will work ok
Warimation said:
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. doesn't bring root by default but just flash SuperSU 2.79 (last version I think) and will work ok
Click to expand...
Click to collapse
Haha silly me, yes volume down + power did the trick. I always get confused with that because it seems to be different for many devices. Yeah as I posted in my other thread, this phone is meant for a friend who uses it daily, it sounds like that lineage 13 is pretty much fit for the task? Would it receive updates in the future? I am always open for trying other ROMS of course, as long as they are 100% working and have no issues/
darkgiant said:
Haha silly me, yes volume down + power did the trick. I always get confused with that because it seems to be different for many devices. Yeah as I posted in my other thread, this phone is meant for a friend who uses it daily, it sounds like that lineage 13 is pretty much fit for the task? Would it receive updates in the future? I am always open for trying other ROMS of course, as long as they are 100% working and have no issues/
Click to expand...
Click to collapse
As it is now lineage 13 is the best option for stable.. But dont expect updates on 13.. Later you can use 14.1 but now it have some issues..
Warimation said:
As it is now lineage 13 is the best option for stable.. But dont expect updates on 13.. Later you can use 14.1 but now it have some issues..
Click to expand...
Click to collapse
Oh okay, thanks! I'll go ahead and just do a fresh install since I forgot this phone has an SD card, so the majority of the data needed is already there. Thanks for your help! I'll keep looking at 14.1 and rest of the Nougat ROMs, and consider flashing it if they become stable soon.
Warimation said:
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. cumps
Click to expand...
Click to collapse
So I installed lineage OS, but for some reason can't provide root access to apps? Attached a screenshot, not sure why it's not allowing me to select apps, and only showing ADB...
EDIT: No idea how, but the SIM card reader stopped working... I tried flashing another ROM just to see if it was lineage, but it wasn't. The phone is still under warranty, but I assume if I send it back it'd have to be unrooted... any idea how I can go about that?
darkgiant said:
So I installed lineage OS, but for some reason can't provide root access to apps? Attached a screenshot, not sure why it's not allowing me to select apps, and only showing ADB...
EDIT: No idea how, but the SIM card reader stopped working... I tried flashing another ROM just to see if it was lineage, but it wasn't. The phone is still under warranty, but I assume if I send it back it'd have to be unrooted... any idea how I can go about that?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Do this and you have a warranty covered phone.
Warimation said:
https://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Do this and you have a warranty covered phone.
Click to expand...
Click to collapse
Oh great, thanks! I used to have the old myTouch 4G, and unrooting that phone was such a pain, I nearly spent 6 full hours because of all the steps needed and it was so easy to mess up. This looks pretty straight forward. On the bright side, I now know once I get the phone back I can flash lineage OS and should be good to go.
darkgiant said:
Oh great, thanks! I used to have the old myTouch 4G, and unrooting that phone was such a pain, I nearly spent 6 full hours because of all the steps needed and it was so easy to mess up. This looks pretty straight forward. On the bright side, I now know once I get the phone back I can flash lineage OS and should be good to go.
Click to expand...
Click to collapse
Before you flash kdz maybe the problem was bootstack.. Dont really know if that was the problem because its supposed to work if you still have a KitKat bootstack installed but try changing that.. Just be carefull to choose the right one..
https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632/page7
Flashed Oreo following all directions. Updated twrp and firmware. I've tried every Oreo rom and charging is hit or miss on every one. Leads me to believe it's not the roms but something else. I did a full format and never reflashed a stock type rom first. I'm back on 7.1.2 now and it charges fine. I have no idea where to go from here. Any ideas?
Charging has been inconsistent on every single Oreo ROM I've used. Sometimes it charges slowly, sometimes normally and sometimes quickly.
gavin19 said:
Charging has been inconsistent on every single Oreo ROM I've used. Sometimes it charges slowly, sometimes normally and sometimes quickly.
Click to expand...
Click to collapse
The same issue was occurring on S6E+. It was hundred percent a kernel issue which was fixed under the kernel title. Could it be same? ?
Sent from my Xiaomi Mi Mix using XDA Labs
I've tried every Oreo ROM, Pixel experience is the only ROM that still enables it to quickly charge. All 7.1.2 ROMs work, so I'm sure it's software
Konstantine34 said:
The same issue was occurring on S6E+. It was hundred percent a kernel issue which was fixed under the kernel title. Could it be same? ?
Sent from my Xiaomi Mi Mix using XDA Labs
Click to expand...
Click to collapse
More than likely. Clearly fast charge support is present in the kernel since it works at times, but why not all the time. Odd.
I searched about this a while back and it seems a number of other devices had issues with flaky quick charge after updating to Oreo too. Maybe this is something that Psy can address with his kernel.
Works for me with Psyman Pixel experience, no problem, won't work with any other Oreo ROM though unfortunately
rrat said:
Works for me with Psyman Pixel experience, no problem, won't work with any other Oreo ROM though unfortunately
Click to expand...
Click to collapse
Every ROM I've used is capable of quick charging. The problem is that they don't always do so right away, or they do for a while and then step down to normal/slow charging. I've never used one yet where quick charging is outright broken.
Yeah Im not sure what's going on. Something's wierd here. I formated my internal again and tried to flash a miui rom and kept getting a screen telling me a reset was necessary....which took me to recovery then looped back to the same screen. Wierd. None of the miui rooms would work. Strange things going on with my phone! Back on good old 7.1.2. now.
ti325 said:
Yeah Im not sure what's going on. Something's wierd here. I formated my internal again and tried to flash a miui rom and kept getting a screen telling me a reset was necessary....which took me to recovery then looped back to the same screen. Wierd. None of the miui rooms would work. Strange things going on with my phone! Back on good old 7.1.2. now.
Click to expand...
Click to collapse
Yeah that's a miflash reset, careful not to relock bootloader.