Related
Ok, so I am a hardware guy not software.
I have all the hardware put together to run a I777 without a battery.
I can get the phone to boot all the way to the home screen, Then within a couple seconds I get the 0% battery warning after which the phone shuts itself back off.
After some research I found someone reference:
services/java/com/android/server/BatteryService.java in android_frameworks_base
I attempted to do a adb pull of systemui.apk
After much frustration of adb not working correctly I could open the adb shell if the phone was connected, I could type the su command and the phone displayed the confirmation that shell had been granted su, but then I could go no further adb devices showed nothing connected, 1 billion driver reinstalls, computer and phone restarts later, I finally got the phone to connect using MyPhoneExplorer program.......
So I get the sustemui.apk and attempt to use a couple different windows based decompilers (again I am hardware not software) and that is where I am currently stuck.
I have spent countless hours on this now and would much rather just offer a reward to someone to get this fixed.
So here is the offer.
$25 if you can change whatever needs to be changed so the phone will not shut off even though no battery is connected, thus the battery level will always report 0%
As noted above, I think it is just the one small piece of code needs to be changed, recompiled and put back on my phone. However, it may go deeper than that as I have found nobody that has actually done this complete, several threads here and elsewhere of people asking but they are usually only a couple posts in a thread then nothing.
I can pull and send whatever files are needed to be changed, if it becomes massively time consuming I may be willing to renegotiate payment, but I think for someone who knows what they are doing this should be fairly quick.
Hit me up with a PM and we will get some direct communication going, skype, google talk etc lets get this going.......
PS, I can pay with either paypal, or if you prefer something else like a amazon gift card, google play credit etc.
I saw on YouTube that you successfully got this to work.
What ROM and power supply did you use?
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Wow - you're in a difficult situation...
You being on stock I can only imagine the bootloop is caused by something you installed.
So if you can access settings and are able to uninstall apps, just keep doing it until you are back to the original stock setup.
Are you sure the files you are trying to save are still on the SD card? Don't know how you flashed 10.6.1.14.8, but flashing a complete firmware package ususally erases /data - although your persisiting bootloop indicates it didn't...... if the bootloop is caused by an app. And I can't imagine what else would cause it.
You could try to do a factory reset in Backup&Restore but you will loose the contents of your /data partition...
You can flash the 10.6.1.14.10 firmware file, but most likely you will also loose your data.
The only way I can think of to replace your bootloader and firmware without data loss is if you try to find a copy of the 10.6.1.14.10 dlpkgfile. That is the OTA update file Asus pushes out to users. It's a patch file, meaning it only replaces/updates new files and leaves everything else alone.
If you find the dlpkgfile on some forum you would have to place it into your /cache directory and reboot - and I don't know if you can copy it to your tablet before it bootloops again.
Unfortunately the reason for your bootloop is probably an app on the same partiton with the data you don't want to loose. Unless you manage to uninstall the culprit I don't see much hope....
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
_that6042401 said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
He's bootlooping..... How does he go into settings and turn on USB debugging?
I think the best option maybe to flash a stock Asus ROM from their site but that will wipe all data including those photos......
zanadoo22 said:
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Click to expand...
Click to collapse
I have not use this method but you could try.
You need a boot OS tool on your external sd and run it from your external sd so you can access to your internal sd to copy files from there. You can search on the internet and you should find more information on how to use them depending on what boot os you are using.. Good luck.
zanadoo22 said:
and I only have about 10 seconds before it freezes and restarts.
Click to expand...
Click to collapse
sbdags said:
He's bootlooping..... How does he go into settings and turn on USB debugging?
Click to expand...
Click to collapse
Preferably FAST.
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
LetMeKnow said:
You need a boot OS tool on your external sd
Click to expand...
Click to collapse
What is a boot OS tool?
_that said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
zanadoo22 said:
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
Click to expand...
Click to collapse
What Windows version do you have on your PC?
You can check your drivers in Device Manager. Open it, look for your tablet under Portable Devices and check if the driver has a yellow exclamation mark next to it. You should be able to update/install/uninstall the driver from here.
Try to find out if there is a setting in your Windows version to only allow Microsoft signed drivers and disable it.
Sent from my DROID4 using Tapatalk 2
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
WildZontar said:
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
Click to expand...
Click to collapse
Plug it into your computer, or a wall outlet with the battery out. See if it mounts as a strange drive or the led light flashes for a second.
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
WildZontar said:
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
Click to expand...
Click to collapse
At least it isn't completely fried, this method should work:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure it has no other sign of life first.
If you were on 4.1 then make sure you don't use a 4.3 file and lock your phone. Might have to do some digging around to find them, but they are around here somewhere.
Hi folks.
I updated my mate 9 last night using firmware finder, phone rebooted, did the update thingy and then switched off. It didn't boot back up so tried turning on - nothing. Plugged in the charging cable, no light came on to indicate it was charging.
I have tried connecting to my computer using the USB 3 port and the computer does seem to recognise it as it makes that jungle sounds when connected (computer) and again when disconnected. I have tried doing the power vol down and that seems to create the PC to make the sounds again but there is nothing displaying on the phone itself. If you looked it at you'd think it was off.
So I guess it's a positive that the PC is getting some kind of response, and the phone must be working.
Can anybody suggest as to how I can get things back up and running? Remember the screen doesn't work on the phone since the update. I am on C636 converted from AL00 early last year.
Have tried HiSuite just in case but phone isn't recognised.
Thanks.
DT.
adb commands
Shooting from memory here...but have you tried any of the adb commands to see if the computer is seeing the phone?
adb kill-server
adb start-server
adb devices
If you get something from the devices command, then you should be able to
adb reboot
Also, if you are able, find another computer and install ADB as well has HiSuite software/drivers.
dwcasey said:
Shooting from memory here...but have you tried any of the adb commands to see if the computer is seeing the phone?
adb kill-server
adb start-server
adb devices
If you get something from the devices command, then you should be able to
adb reboot
Also, if you are able, find another computer and install ADB as well has HiSuite software/drivers.
Click to expand...
Click to collapse
Thanks for the reply.
Nope - doesn't seem to work. No idea what's happend but it appears to be kaput. Other than my PC recognising that I am connecting something when I plug it in to a USB socket, there is no other way of knowing if the device is even on. I've left it on charge over night, tried the power up/down (even though I can't see the screen) and have tried the appove. It did list a port that was open but no devices appeared as listed.
Will continue having a look to see if there are any other methods. Appreciate your help dwcasey.
DT
Totally at a loss as to what's happend. If I leave it plugged in to my PC it seems every 5 minutes the PC disconnects and reconnects to the phone (notifaction sounds). When plugged in, if I press the power button it gives the same notification sound to indicated disconnected and reconnected. Have tried updating drivers. Device is not listed under ADB when I type the command. It's a Chinese AL00 6/128gb so can't get it reparied locally (UK). Debating whether to bin it as I fear the worst. Will opening up and removing the battery do anything? A bit like removing the cmos battery from a motherboard and it resets?
Cheers for any help.
I've come to the conclusion that the phone is dead and that I have a few options.
1 hope for a repair but it'll cost a fair bit given it's a Chinese model and I'm in the UK.
2 sell it on fleabay, but it contains personal data.
3 stick it in a drawer and console myself with my Note 4, that's it originally replaced.
Phone is definitely toast. When I connect to a PC it loads as USB SER. It still makes some sort of connection but it's impossible to access the phone Absolutely no response from ADB/Fastboot.
Clearly an issue with the update using FF given It was this that caused things to go tits up.
Back to my Note 4. First time I've ever had this happen. Fingers burned, dammit.
btblue said:
3 stick it in a drawer and console myself with my Note 4, that's it originally replaced.
Click to expand...
Click to collapse
If you leave it long enough for the battery to go down (no idea how long that might be) then from a 'drained' phone state to plugging in, you might see a 'powered off charging' screen which would be nice. At least you might have a starting place once again.
Happened to me if you have no warranty ,then it will cost about 200-300 dollars to replace your motherboard.
btblue said:
Totally at a loss as to what's happend. If I leave it plugged in to my PC it seems every 5 minutes the PC disconnects and reconnects to the phone (notifaction sounds). When plugged in, if I press the power button it gives the same notification sound to indicated disconnected and reconnected. Have tried updating drivers. Device is not listed under ADB when I type the command. It's a Chinese AL00 6/128gb so can't get it reparied locally (UK). Debating whether to bin it as I fear the worst. Will opening up and removing the battery do anything? A bit like removing the cmos battery from a motherboard and it resets?
Cheers for any help.
Click to expand...
Click to collapse
Instead of binning it I suggest you disassemble your phone completely with the help of video guides and some fine screw drivers and replace the motherboard yourself. They shouldn't be too expensive on AliExpress. The phone and its components are quite easy to wrap ones head around. Just be wary of the glue they use to stick the battery to the case. It can be a bit of a bastard to get off, but it's worth trying for sure! I've opened it up for screen and camera replacement myself. And I don't count myself as a "phone repair geek" Best of luck on this endeavor!
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