Database Info

[Solved-BADUSB]I think I managed to brick this Captivate

I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.

So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.

Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.

hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.

I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.

Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.

Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.

If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App

jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.

[Q] Galaxy Ace (S5830i) headache with stock email deletion

HI guys, I'm hoping you can help me with a problem that's led me to start threatening my galaxy ace (S5830i) with a hammer.
Actually it's not the phone's fault it's purely my own stupidity, but none-the-less I'm here for help because I've spent all day and night trawling the net, trying to figure out how to proceed to resolve my issue on my own but I simply cannot make sense of the conflicting information I'm finding.
I promise you thing thing if nothing else, I have tried my very best to read around a hundred other forums, pages, and how 'to's but I'm finding that I have no resolution that I can work with because either:
- The tutorials turned out to be for the S5830 - not the i model - when I got to the forum
- The youtube videos all seem to be spoken in accents I cannot understand or not explained clearly, or are too technical
- Links I go to to get apk files etc are broken, wrong or leading me up another path I cannot follow
- Software does NOT look on my screen as it does on tutorials or websites (SDK for example)
- The people explaining the resolution type with such poor English I cannot understand what they're actually saying
- The solutions that work for others are too technical or advanced for me to understand and I'm finding it difficult to learn as I go (apart frm the root instructions which I found quite easy)
Anyway, I'll start at the beginning:
I have a samsung galaxy ace (S5830i) running:
- Gingerbread 2.3.6
- Baseband version S5830iXXLK1
- Kernel version 2.6.35.7
- Build number GINGERBREAD.XXLK3
I've already rooted it so I have superuser access, and I managed that perfectly well on my own
I installed titanium backup and somehow I managed to uninstall the stock email that comes with the phone. I think this is my problem because I now cannot download anything from google play, nor can I add a new gmail account to do so, so I'm stuck in no mans land not able to use googleplay (because my gmail account is now missing from my phone) nor can I seem to figure out how to get th apk file directly into the phone so that I can start fresh.
I'm also absolutely stuck on how to flash the phone and start again because nothing I seem to read is explaining it in simple clear terms that a layman can understand. When I do find a simple explanation, I find it's only for the non 'i' version of the phone, or if I find a simple instruction it's zip files for the rom do not contain all the files I need to use with odin v1.5
Also, there are conflicting explanations on flashing the rom on different forums/sites so I dare not use one over the other because another one contradicts it. I do not want to ruin my phone as right now it still basically works for now as a phone.
In my phone menu, the gmail icon is still there, just not the icon/app that said "email". The icon is now missing from my menus and with it there is now no way to use the play services without a gmail account on the phone.
When I click the gmail icon, it stats to open and then just shuts off quickly, not opening gmail, so I'm pretty sure all this is due to me deleting the email app using titanium backup.
Make sense?
What I'd really be grateful for is if on of you guys could help me out and explain in very simple terms what I need to do to either install the apk directly (preferred) so that I can add a gmail account to the phone and get access to google play again, or failing that a simple how to flash the rom with stock gingerbread, together with links to software that's known to be bonafide.
I am literally being driven mad going around in circles on forums and sites to keep going back to square one.
Any help will be very gratefully received. Or I'm afraid this may mean I'm going to smash my new phone int a wall and never use a smartphone again, because obviously I'm too stupid to play around with them on my own.
I really appreciate your help if someone would be able to invest a little time here.
Thanks very much for your time, guys
Jobeeey

additional info
Right, these are the instructions I found on this forum, but I'm unclear if I'm approaching this right..
Flashing s5830i with Odin v1.85
1.Turn off the phone and put it in Download mode by pressing Power+Volume Up+volume down.
2.Open Odin v1.85.Run as Administrator!.
3.Put the files in Odin and don't touch the settings
4.If it's a one-file firmware put it in PDA section.
If it's multiple put the files in the correct section.
5.Click start and don't touch the phone!Don't turn off computer and don't unplug the phone!It will reboot automatically and the first boot will take some time,so don't panic!
Click to expand...
Click to collapse
I've found a rom (which is a single file) and if I'm reading this right I place that in the PDA section of Odin after installing the usb drivers onto my pc (done that and windows recognizes my phone in the sense that it isn't now hassling me for drivers every two seconds).
Ok.. so I seem to have got the correct rom for my specific ace model.. and the instructions seem to be that I now:
1) Connect usb cable
2) Boot my phone into download mode (I can do that I think).. but at what point do I press vol down to download a new os.. before or after pressing start in Odin?
3) Open Odin and add file as in my attached screenshot (I can do that)
4) Click 'start' in Odin
5) Wait for my phone to reboot
And that should be job done, the phone should be flashed with the stock rom again and that should get me back on track, right? Or am I about to screw up my phone and ruin it even further?
Thanks for reading. I hope someone can advise if I'm doing this right as I've seen other forums say that I should tick the 'Re-partition' box, and other that say I shouldn't, and this one says nothing about it at all.
This is one of the tings that's confusing me, and once I'm now flashing a phone for the first time it's flippin scary to do it on my lonesome!

This is what I mean..
I've just tested going into download mode with odin ready, and the phone gets there (vol up+down + power on).. but each time it gets into download mode it seems to disconnect from odin and no com port is open. I get the windows device disconnected/connected beeping and the connection seems to sever.
What the Fffff...
This is exactly what I'm talking about.. nothing seems to be working like it's meant to be and I'm getting nowhere with any instructions I can find after god knows how many hours researching this.
:crying:

update (lol)
Mornin all,
So, just in case anyone finds this useful..
The flashing problem is kind of irrelevant now because:
A) Odin (tried several versions) simply will not stay connected to my phone when it boots into download mode, and having checked many tutorials for this it sees that this is a problem some of us cannot get past.
Anyway, one of the methods to resolve this was to wipe the cache and clear all data etc, which I did, and now my phone is stuck on the "pres the android" screen, and my phone will no longer get past that. Tried pressing clockwise in all four corners but still nothing.
No probs.. so we move on to a new step of trying to split the roms via cygwin, but guess what? Every single time I try to download the cygwin files, that freezes at about 98% and will not download, no matter which mirror I select.
So, this is what I call a curse that isn't going to be lifted by me no matter hat. It's not not meant to be.
Therefore, what I'm going to do is take it to a local shop that unlocks mobiles and give it to them to flash back to stock rom for me.
If that doesn't work, do you know what I'm gonna do?
Nothing. Because there's nothing you can do when the processes do not follow the same progress as they do in the tutorials.
I hope other novice S5830i users save themselves all his time and trouble and don't bother following the same process and become locked out of their phone at the touch android screen.

Update
Yipee,
Right, I stumbled across a solution that worked for me.
What I did was get my 2gb msd card that came with the phone and slapped MindCR v1.0.12 on the card and whacked that in my phone (this bypassed not being able to get a new rom on the sd card as it wasn't unmounted before the crash, so my pc wouldn't recognise the date to put it on via the pc).
Then I updated the rom from that 2gb card (vol up + menu + power to get into recovery mode) and it took it a few minutes to update the firmware and give me back the full use of my phone, and with a shiny new os on it. Whoop!
I didn't bother with CWM as I'd forgotten to add it before flashing, but it worked none-the-less and I'm now back in business (wiped it manually).
As it turned out this version of MindCR works really well so far as I can tell. I realise there are updated roms now but I've come to the conclusion after the scare I had that if you're not entirely sure what you're doing, it's best to leave it alone if it ain't broke.
SO.. now I have a phone with what seems to be a better os than the stock and less bloatware on it, no phone problems I can see after thorough testing... and from what I can tell it turned out to be better than it was before the disaster.
And I learned a bit in the process. Like for example, don't feck around removing apps from smartphones with titanium unless you've backed them up and you're prepared to stress out for over 20hrs wondering what to do about it.
And, also, don't expect much help from a forum because you may not always get it. << That' not a dig at xda by the way. It's just a BIG forum so your threads may not be seen by the right person before they get buried in past pages.
Hope my little journey helps another unsuspecting S5830i user who comes across the thread.

[Q] I9000 Not working due software mess-up

Hey guys!
First off, i was searching through loads of forums and attempted different solutions. Anything to get it back working. This only made it worse
What happened was as follows:
After having CM 10.1 or some version of it (had the OS at 4.3 i believe), my phone was very slow, so slow in fact that i got so mad at it that i almost bit through it. So one day when i was in a tent at the foot of a mountain all alone (not that long ago) i decided to rollback the phone to its original state from backup i made some months ago before i upgraded the OS. At the same time just before this i backed up the current build just in case. Using ClockWorkMod 3pointsomething.
It went through everything and then asked me: Do you want to root this device? (or something in those lines). I, having no clue, clicked one of the million "no" on the screen.
After this it rebooted with errors saying "Can't detect this drive can't detect that drive". In other words, it couldn't detect niether Internal SD nor External SD. While having the Samsung logo being displayed without booting if i didn't go into "Volume Up, Menu Key and Start your tiny engines!".
I thought i could fix it and looked through tremendous amount of internets in attempt to fix it. Neither Odin nor Heimdall Frontend could detect the device even after installing the drivers and samsung kies and messing about with those two in between.
After a while i ended up with "Phone . . ! in a orange triangle . . PC" aka black screen of death, while the phone can go into download mode. Which in my hand is equally useless as no program can detect it still.
Now i just decided to start a new thread even though there is endless amount of other threads but none seem to cover exactly this as i haven't yet managed to fix it. Plus a response on progress is always pleasant as i personally don't know when i succeed unless phone works fully again.
How bad off am i?
Any input will be greatly appreciated! :victory:

Hoping not to have to spend money on a new one and as far as i've gathered this can be solved - Anybody can give me some tips on where to look or what i could try?

Adventurove said:
Hoping not to have to spend money on a new one and as far as i've gathered this can be solved - Anybody can give me some tips on where to look or what i could try?
Click to expand...
Click to collapse
First you are posting in the wrong location as i9000 has its own forum here for Q&A and others too
second click on My Android Solutions (link below) and try methods to fix USB connection problems first after that get into download mode and use a rescue kit from MY Android Collections (link below) or follow this to flash a Gingerbread JVU stock ROM
Check this out! You , YES! you are an " Android ". Not your phone but U.​

information overload

Over the last couple of years my SM-G860P (Sprint G5 Sport) has gotten rooted and flashed and had a update go real bad. I'd like to just run it back to factory stock. Any version. No custom rom. no custom recovery. Just like it's out of the box. But the amount of information out there has me ready to throw both my phone and computer against a wall. I don't understand the techno speak. (dodxed? Bootloader? undodexed MOAR? Kernals?)
I've been trying for 3 days to get back to plain simple stock with a root. Ever since the update when bad it will run but things like bluetooth don't work. Rotate screen locked on one profile etc. But the sheer number of pages from various dates and various versions of various programs has me frustrated.
Is there a simple way to put it back to out of the box stock? I can let keis or regular updates handle the rest. A "how to go back to stock for idiots"?
Captain Quack

You really shouldn't be flashing anything if you don't know what those terms mean. But anyways, download the correct file for your phone from sammobile.com. MAKE SURE IT IS THE CORRECT ONE FOR YOUR PHONE. Then use Odin (program, you can find it pretty easily if you look for it). Put in the file you got from sammobile, plug in your phone to the computer. Power down your phone, then press Vol Down, Power, and Home at the same time. Follow what it says on screen. Press the button on Odin to send the file over to your phone. DO NOT UNPLUG YOUR DEVICE. After that's done, wait for your phone to reboot. It might take a while (upwards to an hour). If you did it right, then you should be back on stock. There are plenty of videos on YouTube if you need help.

followed the videos. followed the tutorials. had 3 different versions of Odin and 3 or 4 different ROM and kernal files. did everything you said more than once. still not working. tried keis3 and that killed it. can't boot into anything and doesn't show up on the computer. I'm just going to give up on it. we find it interesting my wife's identical phone is starting to act up now. she has data. but no text or phone. off to the service center!

you cant even got download mode? if not, then hes dead Jim. youd need to sent it off for a force flash direct to the mobo

Neither bypass nor Filter Wizard recognizing the phone.

I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?

ignaycyhry said:
I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?
Click to expand...
Click to collapse
If u install a recovery rom and you did it wrong you can boot to fastboot, no?

Hey I faced similar or even worse (twice), I had a similar story to yours,
FIrst itme:
I first bricked my phone, but it was cool, the phone just flashed MIUI for a fraction of a second when trying to go to recovery, other than that, nothing, I tried flashing, wich made it much much worse, black screen, no key combo did nothing, windows not just did not recognize it,it told me there was no way of recognizing it, (error 43 in devices admin, its not posible to reinstall the driver, nor do crap at this point) filter wizard showed nothing, bypassing imposible, etc.
It got pretty similar to what you had:
I just left the phone do some charging discharging cycles (at least 4 days with me checking if the phone did anything at all almost once every day, just so you know the phone was really bricked) and it eventually responded after all that (Im not quite sure what fixed this, I dont kno if it was complete discharge or what, but something happened and it vibrated when holding the pwr button.
Once that worked, I managed to install the filter by pressing volup voldown and conecting the phone to the USB port (dont use 3.0, it works worse for some reason) at the same time, you need to connect and press the buttons and connect at the same time (
at 1:30 he does it, video on spanish) and then you can install the filter.
Then you can Bypass and attempt to flash with SPflash tool, I recomend autoconcect, UART never made it for me, Im thinking thats for when you can put it in EDL mode by presing the test points, but I dont know enough to say for sure, point is, UART never worked for me, even tho I eve know what comms I was using.
second time:
I was running Custom ROM ArrowOS 12, ArrowOS13 came out some weeks ago, so I decided to lash it, it was better in some areas and worse in others, the contacts app did not work, but now Volte fingerprint(irrelevant to us redmi 9a users) and face unlock did so I decide to test some stuff, I wasnted to flsh boot.img from original MIUI ROM on top of ArrowOS13, to check if that fixed some stuff (that worked wonders on ArrowOS12) that bootloped thephone but it was fixable from recovery, I did that and decided to flash MIUI ROM to check if flashing ArrowOS13 from MIUI ROM worked, and flashing MIUI bricked my phone.
unrecgnized with error 43, not posible to fix from software, black screen no response whatsoever from any key combo (all 7 combos) no charging, no filter, no nothing, I know I had around 50% battery (days ago I remembered the exact number, now I forgot it, but just so you know, its not a hunch, I knew it had battery) I tried doing the same stuppid crap, charging and leaving it alone for couple hours, but after one night nothing worked, so I assumed I would have to repeat the procees I did before (I wrote it complete on an unbricking thread so I knew I could go back there and redo that or variate it until it worked), but I decided to do one final thing.
I knew it had battery, so I decided to try and forcedrain the battery, I took a piece of TP and gave it a turn around the phone over the buttons (this is just to not dirty the phone) then with electrical tape, I left the power button and the vol down button pressed) this for around 7 hours my plan was leaving it like that for a full day, but around 6 hours I thought I heard a vibration from the phone, so I kept it with me, then after a while I thought it happened again, but I also had my own phone with me so I thought it was that and some other things distracted me so Im guessing I missed a few, but after that I started to take time from every vibration and yeah, around every 8 - 10 minutes the phone vibrated
I decided to connect the phone (I hadnt before because it would just slowdown the battery draining process) and the phone conected to the pc, still bricked, but it was a lot better, I quickly installed the filter, wich I dont quite remeber, but it wasnt easy, I had some hickups, cmd bluescreened my PC when using Bypass like 6 times, so I switched to powershell and that worked (to do that you need to press shift+right click and open powershell here, then run "python main.py") that worked, but I did not flash using SP flash tool.
I was trying to avoid turning on the phone for fear it would go back to the previus state, but after a while pluged on the PC it showed the no battery logo so I tried to tun it on and it was bootlooped, I was able to go to recovery and fastboot (not normally, I pressed the keys, the phone try to go into those menus, it showed no battery, and in the next cycle after splash logo no matter what you did it sent you to the previus key combo menu) I tried leaving it charging on fastboot, but that did not work, I tried flahing a rom from recovery (wich said I had 47% battery) and it successfully did but when trying to reboot to system it again showed no battery logo. so I put it on fastboot and tried flashing MIUI with Miflsh, did not work but it told me the ROM was bad (same one I had use before) I made sure to extract it again and again nothing, I assume it was the antirollback, so I downloaded the next one on line 12.5.6.0 (I was on 12.5.4.0) and that finally worked (Miflash actually gave me lots of errors but you can google them and most of them have easy fixes, like creating a log folder, etc)
that was yesterday, after it worked it showed me the phone had around 60% batterywich lasted around 30 minutes to 40%, then it took 10 minutes to spend the next 20% (it told me that) and then it drained 1% every second (Im not exagerating I thought I had fried my battery with all that power button pressing) but I had hopes of it just being a configuration issue of the phone not knowing how much battery it had so I just left it power of and pluged it then so the phone knew what was his zero, now the phone as been on 100% for like 2 hours (sharing internet), so yeah, I think the battery has some issues but its better than nothing so Im happy with that.
that is my whole experience, I hope it helps you, see if you manage to get any response from the phone and if you do you can try contact me for help in any point along the way.
Update, it just got to 99% after 2 hours 10 minutes aprox IDK, I would need to test more to be sure