I downloaded an older version of P3Droid's toolbox and tried enabling a different battery indicator. Suddenly, everything on the phone was FC'ing. I restarted but the phone won't get past the boot logo. I have RSD Lite installed and I downloaded the .890 SBF (because I updated), and went into AP Fastboot, but the battery is too low to flash it. I may be wrong in assuming the battery won't charge when my phone is stuck like this, but idk. Is there any other way to fix it?
Oh, and I had Koush's bootstrapper installed
Edit: It seems now there's a tweaked version of Koush's bootstrapper, by Hashcode, that allows booting into CWR by selecting BP-Tools. That would've prevented me from having to flash an SBF,
then rooting, then restoring a nandroid.
plug the phone in and try. if it wont charge you can try to let the battery die and take it to verizon and just say it stopped taking charges. if they throw in a new battery and boot it up and see your are boot looped they might get suspicious but maybe there will be enough juice to use rsdlite? idk
MyDrodonWall said:
plug the phone in and try. if it wont charge you can try to let the battery die and take it to verizon and just say it stopped taking charges. if they throw in a new battery and boot it up and see your are boot looped they might get suspicious but maybe there will be enough juice to use rsdlite? idk
Click to expand...
Click to collapse
The light next to the usb port on the phone lights up. Is that an indication that it's charging?
That usually means that it is charging
I goofed up my D3 into a similar situation playing with metamorphs. Using recovery I did a factory reset then used voice command to access the market and install a launcher to correct my mistakes (assuming your launcher is currently confused). Its a bit messy but it got me in. I wasn't going to run the risk of Verizon denying my exchange.
Sent from my DROID3 using XDA App
If I could access ClockworkMod, this wouldn't be an issue. I'd just restore one of my backups. I can't get into it though
Related
Dear Sir/Madam,
Before Spring Break, I rooted my droid bionic using motofail for windows. I do not know what the software version is, but I will include the software (motofail) in this email. On Thursday March 28, 2012 I decided to try installing ROMs to my Droid Bionic. I saw that Liberty Rom, Blurr3d Rom, and Eclipse Rom were cool roms. so first, I got Bootstrap (I will include it in this email) Bootstrap is a .apk file. I also got ROM manager, titanium backup, and one more, but i do not recall what it was. I made a backup of the stock ROM with ROM manager. and i installed bootstrap. little did i know that if something bad happens to the phone during a ROM install, you cannot restore a previous backup. So i cannot get my stock ROM back on. later on, before i had a problem with bootsrap i installed liberty ROM. then i got board with it then got blurr3d. then i got eclipse ROM. that's when i started to have problems. After i installed the eclipse ROM, noticed that i could not get any cell service or data service. I could get data from wifi though. So i freaked out and got liberty ROM. i read up on it and someone said i should get safestrap. Safestrap is like bootstrap but it is safer because you can access the recovery menu from boot and not have to access it through an application on the phone like with bootstrap. So after i got safestrap i installed it, rebooted it and made a back up. Before i made the backup i put plurr3d back on becasue i thought that the radio files from eclipse were not compatible with the radios on the bionic for some reason. This was all on Thursday. well, this time, it took 3-4 hours for blurr3d to get passed the welcome to andorid please touch the android to continue screen. on the screen it said, "please wait... this may take a few mins" after about 20 mins i got worried so I pulled the battery and rebooted the phone. and got back to the same screen. After i got back to the welcome to android screen, i had to go to football practice and dinner afterwards. when i got home, which was 3-4 hours later, I checked on the phone and it was past that screen and i was able to add my gmail account to it. For some reason or another, the cell and data services were not working. so i left it at that for a day or so and on Friday, I tried using what a lot of people are saying on the Internet which is, RSD lite. you can use RDS lite to flash a stock ROM onto the droid bionic. at that point, i thought that if i got the stock ROM back on, the radios would start working again. well, when I put the phone into fastboot mode it said,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Connect USB
DATA Cable
It also said the same thing when i connected the USB cable to the phone and the computer. RSD lite did not recognize the phone so i tried for a couple hours with the same result. Later on, I read that restarting the computer with the phone in AP Fastboot while the phone was plugged in would get the phone to say,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
This worked, but RSD lite still would not recognize the phone. So then i remembered that i had a stock ROM backup with bootstrap and i did. so i un-installed safestrap (one of the worst mistakes i made so far) and installed bootstrap. so i booted into recovery via bootstrap to restore to stock ROM. things did not go as planned... for some reason or another, it booted up normally. without going to recovery. then it wont to the dual core screen then the bionic eye screen with someone's ROM underneath it (it didn't say someones ROM but it said some one's name then the word ROM) then blurr3d ROM booted up and it kept crashing. so i ended up staying up to around 2-4 AM trying to fix that. i ended up saying forget this and going to sleep.
When i woke up in the morning, i looked at the phone and i had my data and my cell service back so i was confused so i started texting my friends and when i tried to go tot he home screen, nothing happens. but what i learned earlier is that when i reboot the phone, my data and cell service goes away for a couple of hours. So here i am now with my droid bionic, and cant do anything but text and call. i can only call when i get a text from someone, open up the text, and click on the phone number and click call when it brings me to the contact page for the number. I am also not able to access the home screen, the settings folder, or anything besides the notification bar. i really need my phone to use email, games, software (learning how to write java code), and for school in some instances. Any help would be greatly appreciated.
Thank you for your time,
NH85
Seems to me...you lost data along the way.
A possible reason rsdlite is not recognizing your phone might be because you dont have the proper moto drivers installed.
Try this rsdlite and install the correct drivers for your pc...http://dl.dropbox.com/u/63864500/rsd_drivers.zip
Make sure your battery does not die!
Boot into AP fasboot (power and down volume)
Use the cable that came with your phone.
See if rsdlite recognizes the phone.
If it does, you can flash the full 902 xml file (make sure your pc has 4g of RAM tho)
Do you have the full 902 xml file...if not, let me know.
Drivers
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
i notice that you didn't once mention a wipe data or otherwise cleaning of previous ROM before flashing another (correct me if im wrong). also DO NOT have bootstrap and safestrap installed at the same time, this could be what caused all your problems. in order to switch between the two (which i've had to do for webtop issue), you have to return to STOCK +root, uninstall the currently used strapper, reboot, then install the other. things start getting even hairier if you forget that safestrap has both a safe/non-safe system. you need to be doing the switch on the non-safe system if necessary.
the purpose of safe-strap isn't that it can boot to recovery, it's that it *creates a an isolated ROM installation while preserving your "safe" system in case things like everything your experiencing occur. from what i can tell, you did not change to safe system before flashing new ROMs, again correct me if im wrong. at any rate, a bit of advice for the future is follow directions to the dot, but before even attempting the install read through AT LEAST 3 or 4 pages of user feedback to see what the common issues or install goofs are!
that being said...
having your computer recognize the phone as storage device does not necessarily mean you have the right drivers installed, however it does mean that you probably have the right cable (this is important, bionic is finicky without the proper moto cable). you will know if you have the right drivers if you see in device manager Motorola ADB. when you plug your USB cable in, there should be an option for "PC Mode" which will force the computer to search for the drivers you claim to have installed correctly. if not found, here is your chance to install them properly and test RSD to make sure device is detected.
nh85 said:
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
Click to expand...
Click to collapse
Obviously you don't.
Mass storage and ADB are not the same drivers.
If you are in fastboot mode and your device doesn't connect, it's most likely your missing or don't have the fastboot drivers installed on your computer properly.
Once you get the ADB driver from motorola you can use fastboot start flashing.
The information you need is here
http://forum.xda-developers.com/showthread.php?p=22758211 .
I had trouble using RSD to flash the .902 FXZ.
What I had to do is extract the .img files from the ZIP, and use fastboot through CMD to get everything up and running.
Just open up the XML file inside the zip, it will show you the commands you need to type to flash each section and when to reboot the bootloader
Hi
(pleas) can someone explain
how to migrate from Safestrap 1.8x to Safestrap 2.01.....
What's the difference between 2.00 and 2.01? Battery thing? I missed it
To go from 1.8x, you'll need to be in a non-safe system ROM with the stock GB kernel (I have MavROM installed). While in non-safe system ROM, disable safe system, remove recovery, and uninstall 1.8x Safestrap, and then install 2.01 Safestrap. Then install recovery and then if needed enable safe system. It depends on how you have your phone set up. I dual boot so I have MavROM as non-safe system, and have safe system for whatever else. PLEASE CORRECT ME IF I'M WRONG.
DoubleYouPee said:
What's the difference between 2.00 and 2.01? Battery thing? I missed it
Click to expand...
Click to collapse
This was Hash's explanation:
Hashcode said:
You bring up a good point.
I made a very important change in Safestrap, that I may need to undo.
Many users were experiencing low battery and then unable to get to charge mode. And this was causing a sort of "stuck" behavior.
I made this latest Safestrap bypass the 2nd rom if booted while plugged into ac power. This should allow for charge mode under any circumstance.
The downside is that if you reboot while plugged in, your going to bypass the 2nd rom. I'll come up with a better option for the future which avoids the confusion.
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
So if some users were plugged into AC while booting, they might not be able to enter charge mode. So if a user say got into a bootloop, or some such issue, their battery would drain. My guess is that it was just to get faster boot times.
So did he undo it and that's 2.01 or what?
DoubleYouPee said:
So did he undo it and that's 2.01 or what?
Click to expand...
Click to collapse
not yet
ovelayer said:
not yet
Click to expand...
Click to collapse
So whats changed?
pm2gonzales said:
To go from 1.8x, you'll need to be in a non-safe system ROM with the stock GB kernel (I have MavROM installed). While in non-safe system ROM, disable safe system, remove recovery, and uninstall 1.8x Safestrap, and then install 2.01 Safestrap. Then install recovery and then if needed enable safe system. It depends on how you have your phone set up. I dual boot so I have MavROM as non-safe system, and have safe system for whatever else. PLEASE CORRECT ME IF I'M WRONG.
So if some users were plugged into AC while booting, they might not be able to enter charge mode. So if a user say got into a bootloop, or some such issue, their battery would drain. My guess is that it was just to get faster boot times.
Click to expand...
Click to collapse
I dont understand your first response. You toggle to the safe system to install the 2.0 safestrap, so it shouldnt matter what rom you have installed on the non safe system. I would like more detail on the correct way to upgrade from 1.8 to 2.0.
As far as the 2.01 battery upgrade, you got it wrong i believe. When I read hash's response, it sounds to me like he made version 2.01 ALWAYS boot the SAFE system rom (stock rom/kernel) when the phone is plugged into a charger. I'm guessing that while people are playing around with kexec that it has charging issues and if the phone goes dead, there is no way to get it to charge again. So to avoid being "stuck", you just plug it in and it boots the stock rom/kernel and starts charging. This would avoid you needing to access recovery manually and switch modes.
insanespain said:
I dont understand your first response. You toggle to the safe system to install the 2.0 safestrap, so it shouldnt matter what rom you have installed on the non safe system. I would like more detail on the correct way to upgrade from 1.8 to 2.0.
As far as the 2.01 battery upgrade, you got it wrong i believe. When I read hash's response, it sounds to me like he made version 2.01 ALWAYS boot the SAFE system rom (stock rom/kernel) when the phone is plugged into a charger. I'm guessing that while people are playing around with kexec that it has charging issues and if the phone goes dead, there is no way to get it to charge again. So to avoid being "stuck", you just plug it in and it boots the stock rom/kernel and starts charging. This would avoid you needing to access recovery manually and switch modes.
Click to expand...
Click to collapse
Safe mode is your non stock rom. Non safe is the stock. And yes his directions are correct. Boot to non safe(stock), uninstall old recovery and apk, then install new one.
When I did it I did not even remove the recovery, just installed the new apk and when I launched it, it said I had an old recovery, just installed the new right over it.
Edit: you are correct in saying it doesn't matter which rom you have installed in non safe, but since safestrap doesn't allow flashing the non safe side, most ppl leave it stock, since it's much more work to flash something onto it.
Sent from my XT860 using xda premium
I just upgraded to 2.01 from my safe system (non-stock) without issue. It doesn't seem to matter where you install from
Sent from my DROID3 using xda app-developers app
insanespain said:
I dont understand your first response. You toggle to the safe system to install the 2.0 safestrap, so it shouldnt matter what rom you have installed on the non safe system. I would like more detail on the correct way to upgrade from 1.8 to 2.0.
As far as the 2.01 battery upgrade, you got it wrong i believe. When I read hash's response, it sounds to me like he made version 2.01 ALWAYS boot the SAFE system rom (stock rom/kernel) when the phone is plugged into a charger. I'm guessing that while people are playing around with kexec that it has charging issues and if the phone goes dead, there is no way to get it to charge again. So to avoid being "stuck", you just plug it in and it boots the stock rom/kernel and starts charging. This would avoid you needing to access recovery manually and switch modes.
Click to expand...
Click to collapse
2.00 always boots safe system, no matter if ac is plugged in or not. No charge only mode.
2.01 boots non-safe kernel if ac is plugged in. But there is a problem. If the phone is switched off and you plug in ac, then it will go into charge only mode - like it should. If ac is plugged in and you try to do a normal boot or reboot it loads the non-safe-kernel, too, but gets stuck into bootloop. So normal boot of safe-system is only possible without ac. Thats the bug he will work on for safestrap 2.02.
tobby88 said:
2.00 always boots safe system, no matter if ac is plugged in or not. No charge only mode.
2.01 boots non-safe kernel if ac is plugged in. But there is a problem. If the phone is switched off and you plug in ac, then it will go into charge only mode - like it should. If ac is plugged in and you try to do a normal boot or reboot it loads the non-safe-kernel, too, but gets stuck into bootloop. So normal boot of safe-system is only possible without ac. Thats the bug he will work on for safestrap 2.02.
Click to expand...
Click to collapse
Thanks for the clarification on that. I will probably install 2.01 tonight.
Sent from my XT862 using Tapatalk 2
Hey all, hopefully someone can help me out. Ill post the full story and the tl;dr version at the end.
So, my Xperia TL (LT30at) has been rooted for over a year and a half. Since i rooted it it never charged when turned off. I did research and couldnt figure out why, so i left it and have lived with it for the last year and a half. However, i just updated my phone to JB 4.3 by Dark Lord (Ultimate Pure XT ROM) so the model number is actually Xperia T (LT30) Anyways, the phone dies a lot quicker than before so the other day it died and because it wont charge when it is off i usually wrap a rubber band over the power button so itll charge enough to turn on and then charge by itself after that. However, it would only charge enough this time to boot, but then turn right back off. I did this for well over a day and got sick of it not working so i tried messing with things. In the process, I was in recovery (it was philz cwm or something like that, by the way im quite a noob when it comes to all of this, hence why im having problems) and i flashed the xposed disabler zip, thinking it would get rid of cwm because i didnt know what I was doing. It did end up getting the phone to turn on, and its charging great. However, the system UI crashes, and the "unfortunately the system UI has stopped working" pops up repeatedly so you cannot physically do anything on the phone. I tried going back into recovery to flash my backup to fix everything, but it was downgraded back to an older version of cwm, the version i origonally had on it before the 4.3 update. its like 6.0.3 or something, by david marcos or something. Anyway, itll go into recover but a bunch of error messages come up, like unknown volume path, no etc/recover.fstab, stuff like this. There is no way to flash any recoveries because it basically says it cannot find the paths. It will not backup, restore, wipe anything, flash from sideload, nothing. Ive tried all i can think of. Basically cwm comes on but i cant use it for anything. Instead i tried reinstalling cwm to try to fix it, but when i do it says "system cannot find path specified" so it wont download.
tl;dr version, cwm wont work at all after flashing xposed-disabler.zip. i cannot flash any recoveries or install anything through the usb. What do i need to do to fix this? because the system ui keeps crashing my phone is basically useless. thanks for dealing with a numskull..thanks in advance.
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.
Sent from my Xperia T using cm12
arniks8 said:
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.
Sent from my Xperia T using cm12
Click to expand...
Click to collapse
why i didn't think of that, i dont know.
This worked as far as getting the phone to boot and whatnot, however the phone died and because it doesnt charge when it is off, i cant turn it on. it will boot and itll get all the way to the home screen but it immediately shuts back down, even though it is plugged in. Is there any way to fix this charging bug? i did some research and found it is linked to cwm, however now that i flashed the stock rom i no longer have cwm on the phone, so why does it still not charge when off? Thanks for the help by the way..
This morning I flashed last nights CM12.1 Nightly. After it finished I hit reboot and let it do its thing for awhile, only to come back to a blank screen, I rebooted thinking I'd just hop into safestrap, flash a recovery, and be back to normal, but for God knows why, it wasn't letting me get into safestrap.
The next logical step was to run it through unbricking procedure which since RSDlite doesn't like me I have a batch file setup to run it through the manual commands which worked at first, but then I found myself sitting at the stock boot animation for an extended period of time. Not being sure of how long this normally takes because I haven't had to unbrick this phone in awhile, I just let it go.
Realized it was stuck, and decided I'd run through manually and see how that went. Went through the commands, got a couple errors for a low battery but just running the command again seemed to get it through, then I finished, told it to reboot, and then it went right ****ing back into AP Fastboot, saying that there was a boot failure and that cdrom and system weren't flashed correctly. No big deal right? So I go back to run the commands to flash them all again, and now the battery level has completely made me it's new *****.
I have no money to purchase a factory cable, but I feel that if given instructions I could handle it myself. I've seen that the RAZR has a way to get around the low battery level but it didn't seem to work on the Bionic. SO, if anyone has any words of advice, instructions, or methods they want me to try, any and all help would be greatly appreciated. :good:
I know this won't be helpful, but I ran into the same problem. The only solution I found was to use a different battery.
Keep searching around...i found a work-around, but I couldn't tell you exactly where. It involved using an extra usb cable, splicing, and 'straight wiring' the battery. It worked for me is all I can say.
Sent from my HTC6500LVW using Tapatalk
Luckily only cdrom and system didn't flash properly, simply by plugging the USB into AC power first was able to trick the phone into thinking the battery was fine. I was able to get those flashed and it booted just fine.
Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!
LiquidArrogance said:
Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!
Click to expand...
Click to collapse
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.
muniz_ri said:
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.
Click to expand...
Click to collapse
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop
Is there physical damage on the phone, thus why att didn't do the warranty?
Sent from my HTC One_M8 using Tapatalk
LiquidArrogance said:
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop
Click to expand...
Click to collapse
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck
muniz_ri said:
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck
Click to expand...
Click to collapse
No idea what just happened. I've been messing around throwing the kernel you recommended at it as well as the stock partitions. Kept getting back to boot loop but at one point it stuck out, said it was upgrading, optimizing apps, and now it's running. So weird.
I'm way too scared to do the factory reset at this point, though.
Thank you again for your help, I really appreciate it!
Edit: Unplugged the USB cable and it immediately shut off and went back into boot loop. Wow.
this sounds like a hardware problem.. i sent my phone to Samsung and they actually repaired it, it was the pba board, i had the same problem.. i flashed everything it needed to recover from a bootloop. and sometimes it would become non responsive. go to best buy and see what they tell you.
Sent from my UNROOTED SAMSUNG-SM-G900A on OF2
Update:
Thanks to everyone for their replies. I was able to get the phone to boot thanks to everyone's help. Did this by flashing kernel then partitions which would allow the phone to boot.
I finally figured out that the phone would only boot if plugged directly into a power source. As soon as I disconnected the power cable, it would send it right back into the boot loop. I ran some battery "repair" and "calibration" tools but these did not fix the issue. Whenever I would run a battery drain tool, the stress on the battery would cause the phone to shut down.
All of this led me to believe it was an issue with the battery. I held my wife's S4 battery to the contacts on the S5, and it works just fine, even disconnected, and even with the stress test on the battery.
SO -- I'm going to buy a new battery and see if this fixes my problems. I think I just had the perfect storm of battery issues coupled with firmware problems.
I'm pretty sure I know what caused the battery to go haywire. I work in a max security prison and have to leave my phone in the car all day. Outside temperatures regularly hit 105F+ during the summer, so who knows how hot it's getting in the car. Obviously I always leave the phone turned off, but I suspect the high temperatures caused the damage.
Going to try to find a new battery today. Will keep everyone posted! Thank you again for all of the replies.
I had the same issue and would just like to thank you for the files! They helped me unbrick my phone! Much appreciated.