[Q] Somehow lost CM10 after flashing - Barnes & Noble Nook Tablet

I recently flashed CM10 onto my Nook Tablet - thanks to all those who helped!!
Everything was working perfectly for about 1 week, then the kids ran the battery all the way down. I plugged it in to charge it, and it started doing funny things. As soon as I plugged it in, it would turn on to the initial screen with the sliver N, then it would turn right back off (presumably because the battery was drained). It just kept repeating this. I didn't do anything because I figure that once it charged everything would be back to normal. However, I turned it on the next morning and it started walking me through B&N's initial setup. My CM10 is gone and I'm back to stock OS. What happened, and how do I prevent it from happening again?
(I was surprised that the stock OS was even still there.)

I suppose an "8 failed boots" could have been performed, and that triggers the built in recovery. I'm surprised it managaed to boot back to stock though.

asawi said:
I suppose an "8 failed boots" could have been performed, and that triggers the built in recovery. I'm surprised it managaed to boot back to stock though.
Click to expand...
Click to collapse
Is there a way to stop the table from automatically trying to boot when it's plugged it - maybe this will correct the problem when trying to charge a fully-drained battery. Is there any reason I shouldn't do this (assuming it's possible)?

Related

[Q] Vibrant won't boot - USB appears to be stuck on

I picked up a used Vibrant last week and it initially worked fine. However, it still had 2.1 installed so I decided to update to 2.2 with Kies Mini. After 4 hours of screwing around and with it and much searching of forums, I finally got it upgraded, but something seems to have happened to the phone in the process.
The phone acts like the USB is permanently on, even if no cable is attached. The USB plugged in notification stays on even when the cable is unplugged. After I charge the phone and unplug it, the battery indicator continues to show that it is charging. The main problem is that the phone gets stuck in some kind of loop when the phone is turned off and never truly turns off. Initially, what would happen was that the little loading circle indicator would appear then the battery charging icon would pop up for a moment. However, since there was no cable plugged in, it would disappear. After several seconds of a black screen, the loading circle would come back up. This loop would simply continue over and over. Pulling the battery and putting it back in did nothing; the loop would just start over again the moment the battery was inserted. The phone would not respond to the power button while this loop was going.
At this point, I was still able to get the phone to boot by plugging in the USB cable, waiting until it started to charge (with the green battery icon) and then hitting the power button. This went on for several days. Today, I decided to take the battery out for several hours to see if anything would reset. However, things only got worse. The loading icon still pops up but now the charging icon doesn't come up, even if the USB is plugged in. I just get a loop where the loading circle pops up, disappears, comes back, and so on. I am now also not able to power on the phone with the power button.
I am still able to get into download mode (but not recovery mode) so I flashed everything back to stock using Odin and the instructions on this forum. This does get the phone booted back up, but as soon as I turn it off again everything starts all over.
So now I have a phone that, if it is ever turned off or loses power, has to be reset, wiping everything in the process. Does anyone have any idea how to fix this? Is it some kind of bootloader issue?
Odin, put 2.1 stock rom back.
Like the post before me mentioned, Odin back to stock 2.1
And personally, I'd much rather install stock froyo with ODIN rather than KIES.
Or just use a Custom ROM altogether.
As I mentioned in the original post, I've already restored the phone with Odin several times and it has absolutely no effect. It allows the phone to boot once but as soon as it is turned off again the loop starts over.
mordrid52 said:
As I mentioned in the original post, I've already restored the phone with Odin several times and it has absolutely no effect. It allows the phone to boot once but as soon as it is turned off again the loop starts over.
Click to expand...
Click to collapse
I have heard of KIES updates screwing phones before! I would contact T-mobile and tell them the situation....letting them know its used and had stock T-mo 2.1 and after using KIES to upgrade to 2.2 it screwed your phone.
Eventhough its used and You didnt buy it from them, they would probably fix it for you for free since their update program caused the issue...If it was a stock phone then they will probably fix it.
edit: in your story to them, leave out the part about you using ODIN...i am sure they will call that a void of the warranty.

[Q] weird CM7 experience

I recently decided to try CM7, SD card install, on my 16GB Nook, after running Indirect's Root+Gapps. Install went well, looks great, but I've experienced a couple of odd problems.
On two occasions, my WiFi would fail to come back after sleep and, when I went into Settings, it showed "Shutting down..." It seemed that it couldn't complete the shut down, and would not turn back on. Finally, both times I rebooted, and it came back fine. On both occasions battery was well charged.
The other problem appears a bit more serious. Yesterday I charged the Nook to 88%, unplugged it, put the screen to sleep, and went to bed. I would have charged it completely, but didn't want to leave it on the charger overnight. When I picked it up this morning, it wouldn't come on at all! Totally non responsive. I thought "Hmmm, battery?" and plugged it back in. A few minutes later, it came on, showing 2% battery.
Apparently, it had completely discharged over the course of 8 hours. Now I'm at work, with the nook plugged in, showing 32% charge, and it seems to be working fine.
Has anyone experienced either of these things? Does anyone have any advise to try?
Okay, first things first. Lets back up a bit.
You say you have a CM7 install on sdcard, but that you also used Indirect's root + gapps.
What exactly did you do? Did you put cm7 on an sdcard while also rooting the internal rom? Or did you put clockworkmod on an sdcard and then install the zip file to root and install gapps on the internal memory?
Ah! I'd been running Indirect's root for several months. My 3 year old got ahold of the tablet, deleted a lot of stuff, etc. Since I was going to have to do so much to get it back to normal, I decided it was a good time to play with other ROMs.
I used Ubuntu recovery to reset completely back to stock. Then installed Root and CWM, but not Gapps. I then booted into recovery, mounted USB storage, copied CM7 to the root of the SD card, factory reset, clear cache, rebooted, and it all came up normally.
Theoretically, I should have nothing on except for CWM and CM7.
And, as I said, it's working completely as expected, except for these issues.
Thanks for your response. I'll be glad to give any other information if I've forgotten anything.
RobWoodall said:
I then booted into recovery, mounted USB storage, copied CM7 to the root of the SD card, factory reset, clear cache, rebooted, and it all came up normally.
Click to expand...
Click to collapse
This is the part that confuses me and I just want to clarify. You say you copied CM7 to the sd card. Did you install this zip file then via "install from zip" in clockworkmod recovery?
RobWoodall said:
I recently decided to try CM7, SD card install, on my 16GB Nook, after running Indirect's Root+Gapps. Install went well, looks great, but I've experienced a couple of odd problems.
On two occasions, my WiFi would fail to come back after sleep and, when I went into Settings, it showed "Shutting down..." It seemed that it couldn't complete the shut down, and would not turn back on. Finally, both times I rebooted, and it came back fine. On both occasions battery was well charged.
The other problem appears a bit more serious. Yesterday I charged the Nook to 88%, unplugged it, put the screen to sleep, and went to bed. I would have charged it completely, but didn't want to leave it on the charger overnight. When I picked it up this morning, it wouldn't come on at all! Totally non responsive. I thought "Hmmm, battery?" and plugged it back in. A few minutes later, it came on, showing 2% battery.
Apparently, it had completely discharged over the course of 8 hours. Now I'm at work, with the nook plugged in, showing 32% charge, and it seems to be working fine.
Has anyone experienced either of these things? Does anyone have any advise to try?
Click to expand...
Click to collapse
i too have had the wifi problem after sleep. it's been mentioned by several forum members , so is a bug. the recommendation ( and what i do also ) is to have the link ( to wifi ) on the desktop, and toggle it off when you know you're not going to be needing it.
Cubanluke88,
Yeah. I downloaded the image, burned it to a formatted SD card. Inserted the card, and held down the "n" and power key until the Nook came on then went off. then pressed only the power button to boot into CWM. Selected "Install .zip from SD card," selected the CM7 zip and confirmed. After the install I reset and cleared my caches, and rebooted into CM7.
I've installed a few ROMs on the Kindle and the Viewsonic G-tab. I don't know of any other way to install a ROM. I don't think I'm doing anything differently than anyone else...
Thanks old_fart,
I'll definitely give that a try!
Ok perfect, now I have a more complete understanding of your current setup. Your wording in the original post was just a bit weird (no fault of yours, this stuff takes some getting used to).
So basically right now you have CM7 running on the internal memory and are having some issues regarding battery drain and wifi disconnect.
As for wifi, as someone else said, you should toggle wifi on/off as necessary. I'm not sure of the Wifi settings on CM7, but for CM9, if I go to wifi in settings and then go to advanced, there is an option to determine when wifi is kept on during sleep. I have this set to "never." Now with a device whose wifi doesn't have bugs, this is nice because when it wakes up it automatically turns wifi back on (my Xoom does this). However with the nook, you have to toggle wifi off and back on in order for it to do this. With this "never" setting selected, my current battery time is at 2days and 19 hours with very very little use (basically the battery shouldn't be going down while its sleeping if wifi is off).
So you can either find this setting and make it so wifi doesn't stay on while its sleeping or you can have a manual toggle (I believe there is a way to add wifi to your notification bar in CM7 settings, if its not already there) and just toggle wifi on as necessary.
You could probably find a toggle widget on the play store as well.
tl;dr it sounds like your wifi is staying on when it shouldn't be and you need to rectify that
I had the wifi issue as well, but I set it to "never" turn off (as cubanluke88 mentioned already) and I haven't had an issue ever since.
Thanks, cubanluke88!
Yeah, I'm still not completely up on the terminology, plus I was trying to keep the posts as short as possible, without leaving out important information.
I've installed a toggle widget. Seems to be working fine, so far.
I actually use the Kindle a lot more than the Nook. Nook has superior specs, but the Kindle just seems more stable...
No problem. Check out my post here for a bit of an introduction on android tinkering that should help clarify some of the terminology.

[Q] Bootlooping. Opinions on issue?

Last night my phone started bootlooping very frequently. I was running the CM10 built with Samsung source that was posted in this section for a while with absolutely no problems, when suddenly the phone shut off and started doing short, quick vibrations repeatedly. Like the vibration that the phone makes when it first turns on and shows the Samsung logo. I pulled the battery but it continued once I put the battery back in. Eventually I got it to boot but soon after it booted it started again. I am now running Blackjelly v1, and though less frequent, the problem still persists...does anyone have any idea what could be causing this?
zefir738 said:
Last night my phone started bootlooping very frequently. I was running the CM10 built with Samsung source that was posted in this section for a while with absolutely no problems, when suddenly the phone shut off and started doing short, quick vibrations repeatedly. Like the vibration that the phone makes when it first turns on and shows the Samsung logo. I pulled the battery but it continued once I put the battery back in. Eventually I got it to boot but soon after it booted it started again. I am now running Blackjelly v1, and though less frequent, the problem still persists...does anyone have any idea what could be causing this?
Click to expand...
Click to collapse
Mine did the same thing... It was crazy...Nothing I did fixed it... Flashed away at any 4.2.2 Rom and It was consistent bootloop... Decided to take phone apart and clean power button (read somewhere power button gets stuck) Same issue bootloop... I odined back to stock...bam it worked...now the capacitive buttons don't work... So after booting stock I flashed TWRP recovery and attempted to flash 4.2.2 rom to no prevail, I am only capable of flashing BlackJelly v1 any other rom sends me into (App is upgrading screen after boot after apps say Starting Apps bootloop) nonstop bootloop...
I honestly wonder if my phone is the only phone that will not accecpt 4.2.2 roms...
kaljr1980 said:
Mine did the same thing... It was crazy...Nothing I did fixed it... Flashed away at any 4.2.2 Rom and It was consistent bootloop... Decided to take phone apart and clean power button (read somewhere power button gets stuck) Same issue bootloop... I odined back to stock...bam it worked...now the capacitive buttons don't work... So after booting stock I flashed TWRP recovery and attempted to flash 4.2.2 rom to no prevail, I am only capable of flashing BlackJelly v1 any other rom sends me into (App is upgrading screen after boot after apps say Starting Apps bootloop) nonstop bootloop...
I honestly wonder if my phone is the only phone that will not accecpt 4.2.2 roms...
Click to expand...
Click to collapse
It's now bootlooping like crazy. It'll turn on for like 5 minutes and then go right back to bootlooping. My USB port is kinda screwy so it's hard to odin anything. I'm at a loss for what to do.
zefir738 said:
It's now bootlooping like crazy. It'll turn on for like 5 minutes and then go right back to bootlooping. My USB port is kinda screwy so it's hard to odin anything. I'm at a loss for what to do.
Click to expand...
Click to collapse
I had boot looping problems several times now. For me, it's always been sticky power button. One time, I forgot it had that problem at work and looped for 30 minutes. I just take out the battery for about an hour, then get the power button unstuck. My button gets stuck at the bottom of the button, so I can normally mess with the top part to fix it.
So the issue has escalated even further now. It is a sticky power button, i believe, but now when the phone tries to turn on it shows both samsung logos and then shuts right back off and refuses to turn on again unless i do a battery pull...I'm not even sure if it's turning off, actually. It turns on immediately after inserting a battery into the device. But right now I have a fancy brick.
Definitly a power button issue
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Similar Issue
My phone started doing a crazy bootloop just out of the blue last night. I have never had a problem. I took the battery out to put my memory card back in. I'd been using it for my digital camera. This is not out of the ordinary. I do it all the time. But after I replaced the card, battery and cover it started this continuous boot loop. Sometimes it will go to the main screen and allow me to perform some functions, but then it goes right back to the bootloop. I am running the Padawan JB rom. I did the complete wipe, factory reset and re-flash. But it still did the bootloop. The only time it does NOT exhibit this issue is when the phone is on the charger. Then and only then it works perfectly. Is it the battery? Why will it bootloop without the charger and work fine when on the charger?
It is probably your battery
cayjominara said:
My phone started doing a crazy bootloop just out of the blue last night. I have never had a problem. I took the battery out to put my memory card back in. I'd been using it for my digital camera. This is not out of the ordinary. I do it all the time. But after I replaced the card, battery and cover it started this continuous boot loop. Sometimes it will go to the main screen and allow me to perform some functions, but then it goes right back to the bootloop. I am running the Padawan JB rom. I did the complete wipe, factory reset and re-flash. But it still did the bootloop. The only time it does NOT exhibit this issue is when the phone is on the charger. Then and only then it works perfectly. Is it the battery? Why will it bootloop without the charger and work fine when on the charger?
Click to expand...
Click to collapse
The Note won't run without a proper battery installed. I had the problem where I swapped out my dead battery for a fully charged one (I do this everyday) and all of a sudden it kept bootlooping.I spent a few hours, when I got home, flashing it back to stock etc to no avail. I could get into download mode, and download to my hearts content but when I tried to boot the phone, it looped. Samsung, samsung, samsung....
I swapped back my, now charged, spare and BAM it booted into stock android no problem. I think my first (stock samsung battery actually) is finished. Or at least has some serious issues, and the phone refuses to boot with it in but my spare (Anker battery) works fine.
I hope this works for you's, it did for me
---------- Post added at 03:27 AM ---------- Previous post was at 03:25 AM ----------
Also, if I had just charged my phone using my working battery, I would have saved myself some serious grief, and hours wasted. Here's to hoping you don't too!

Rezound won't power on or adb after Tachyon power-down

Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
DentalAppointment said:
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
Click to expand...
Click to collapse
So, if you disconnect the USB cable, remove and reinsert the battery (also, try another battery), then press and hold POWER+VOL DN for a few seconds are you able to get into HBoot? If not, it is likely borked, but not because of flashing a ROM, it was probably just it's time to go...
got it working
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
DentalAppointment said:
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
Click to expand...
Click to collapse
I had some unfortunate nastiness happen to my Rezound a while back which prompted me to go out and get an M8, but I did eventually get the Rezound 99% functional again.
First off, cell phones in general rely on something called NAND memory for all mass storage. It's decently quick stuff, but not the most reliable storage medium in the known universe. Basically, it slowly dies with use. NAND only has so many read/erase/write cycles before it begins to degrade. This can lead to very quirky corruptions in the partitions, and that's kind of what it sounds like has happened to your Rezound. The fix that got mine back to working order was a complete stock RUU restoration followed by a "factory reset" through Hboot. That will wipe and rewrite all of your partitions. Then flash your custom recovery, ROM, and kernel.
As for flashing ROM's and kernels in the right order, you want to flash the ROM and then the kernel. A lot of devs recommend flashing the ROM, then booting it up, then flashing a custom kernel, however, if you know you've got a working combination of ROM and kernel, there is no reason you can't just flash the ROM and kernel (in that order) at the same time in recovery.

XT912 Boots, then immediately shuts down

Sorry for this long-winded question but this puzzle has lots of pieces.
The USB port on my XT912 stopped working for charging, so I jerry-rigged the phone by soldering a a LiPo charging module like this one onto the back of the case and putting little copper-foil contacts on the back of the phone, until I could get around to fixing my hot-air rework station. It's been working okay for the past year and a half, but the time to shut-down has been getting shorter - even with the battery level showing high.
I just re-flashed stock ROM VRZ_XT912_9.8.2O-72_VZW-16-5 on the phone, it booted, I went through the setup, and it worked well - until I rebooted. Then, upon booting up fully, it would immediately shut down, even though it showed a full charge. I re-flashed again, re-did the setup, and again it worked. I rooted, and installed SafeStrap, with which I installed Lineage OS. Again the stock would shut down. After switching to Lineage, Lineage would shut down - not what I expected.
Okay, I know I need to fix or replace the rework station and replace the jack, but I don't have time for that right now. Even if I did, it would still reboot. Any ideas? Do I need to reset some sort of low-level battery stats file?
Thanks
Chip

Categories

Resources