hey guys. have my redmi note 7 here with me
i successfuly installed the LOS 17 rom on it, through OrFox (after unsucessfully trying with with the unofficial TWRP, not following the developers advice!), but it had some bugs and i decided to try his previous LOS 16 rom
after wiping system, data, cache and dalvik partition i tried flashing the rom zip file - i got back and error and it didn't flash. i rebooted to recovery to retry flashing but got the same error
as has happened to me before in other devices, i suspected the file could be corrupted, since i had a very slow connection that day and paused the download 2 times, and also decided to download the correct firmware just to be sure, in order to flash the two
since i was waiting a lot for the download to finish, i left the phone overnight without a rom installed. i think i left it turned on recovery and so next day, when i pick it up it had no battery
i tried to boot it and got a "no battery" sign right after the splash screen. so i plugged it into the adapter.
as soon as it got plugged, the phone screen turn on with the splash screen and right after a "no battery" sign again. (i think think is normal and then you usually get the "charging battery" animation, after some seconds?)
but the then it just rebooted: splash screen again and the "no battery" sign once more. and then again...so it seems to be stuck on a charging bootloop, always showing the "no battery" sign and getting no charge at all, no matter how much time it stays plugged in
i tried connecting it with a different charger and another cable and get the same result..even tried with a charger with no fast charge (i read it would be a solution to some other device) but still the same bootloop
i can boot it into fastboot but it reboots quickly also (with the "no battery" sign right after)
so i can't get back into recovery or whatever since the phone gets no charge at all.
does anyone know a solution for this? thank you
Related
Looking for some help, my phone broke so a friend gave me his old g1 that has been rooted. when i power on the phone i get stuck in the boot cyctle of the g1 logo and then off and the repete.
i cant get the g1 to do a restore, the only change i can get is when i hold the back key when i turn it on. i get the rainbow scree and "serial 0" cant get into fast boot....
if possible i would like to get this device usable and even better with a cstm rom and froyo or what ever is reccommended.
any help would be amazing.
a small update, i did get it to boot recovery mode once, so i rebooted the phone and android started. i got a low battery notice and pluged in the usb cable and it imeditaly rebooted and started the cycle over and over agian. i have not clue why that time it actualy booted, i let the battery charge for 30min and tried agian with no luck.
Hallo,
i hope someone can help me here.
After a low battery my phone doesnt turn on any more. After some research i thought it might by the "death battery problem". So i but the phone on Laptop Charge port for 6 hours and i got it booted in to system.
But only for some seconds and it turned of again. So i decided to buy a new battery. Installed it and tried to boot. Sometimes it bootet in to System, sometime just got Blackscreen. I tried hard reset in it showed some errors. That was some days ago. Now it boots and everytime blackscreen. I tried also longer presses like 10 secs and 60secs. I tried fast press for hard reset with boot logo. I have no detection on Windows. I never rooted the phone and it has still stock rom. Must be the latest kitkat 4.4.2 i guess. I checked every cable. No charge led or logo.
Hey dude check out my video https://youtu.be/rpmbk9RFE_U there is step by step instruction how to reflash your rom... Just watch im here for any questions.
Hi,
I have a Note 4 t-mobile that is "brick" right now. and I hope if anyone offer assistance.
It is running Android 6. Ever since the last upgrade the phone would freeze and reboot on its own. I fixed that problem by installing Wake Lock. After that it would still experience sluggish at time but the phone is still very much usable.
Lately, after watching a bit of streaming video the phone would slow down so much that a reboot is needed. But yesterday my last reboot turned my phone into a brick. After that reboot the phone rebooted itself to the download mode. So I took the battery out, waited for a few minutes and put the battery back in and started the phone. Instead of booting normally the phone displayed the message including "set warranty bit: recovery" and then followed by the flashing TWRP splash screen. By "flashing TWRP splash screen" I mean the TWRP splash screen ( with the TEAMWIN logo) would be shown on the screen for a second, then the screen black out for a couple of seconds, then the splash screen is back on for a second, and the screen black out for a couple of seconds, etc, and never successfully boot into TWRP recovery. I had left the flashing splash screen overnight and nothing changed. Connect the phone to my pc via usb and fastboot wouldn't recognize my phone when phone was flashing the TWRP splash screen. So I tried to flash TWRP again by starting my phone in download mode "volume down + power". When I connected my phone to my pc Odin recognized my phone. But when I tried to flash a custom recovery (TWRP or CWM) it seems the download started but never finished (on the phone I could see the progress bar started but never progress further).
Any suggestions would be greatly appreciated1
Additonal info
I just wanted to add that my phone is still running the stock ROM.
Problem solved
Problem solved. Once I used a different cable and the download process actually worked and I was able to flash stock ROM using Odin.
My phone has been operating perfectly fine up until a video meeting I had today, where the phone went from 100% to 0% by the end. This Axon 7 has had a lot of wear and tear on the battery so that is normal. Today the phone was very very hot during shutdown.
Upon trying to reboot, I am stuck in a bootloop. I have Lineage installed, and tried Stock but that wouldnt even get to the booting animation. I uninstalled Magisk before these tests. Now I am back on Magisk, in LineageOS (latest build) and managed to get back to the booting animation.
Does anyone know any kind of damage that could occur with a hot phone during normal operation (not boot or shutdown) shutting down? A bootloop seems like a strange result.
If you can still boot to twrp, just stay there and let it charge a bit, maybe 20% + battery level. I experienced this situation twice already.
The first one I experienced this, it won't even boot or even charge while it's off. I even opened up the phone to reconnect the battery. The second time, I was able to boot to twrp. So I let it charge while in twrp. HTH
otaconremo said:
If you can still boot to twrp, just stay there and let it charge a bit, maybe 20% + battery level. I experienced this situation twice already.
The first one I experienced this, it won't even boot or even charge while it's off. I even opened up the phone to reconnect the battery. The second time, I was able to boot to twrp. So I let it charge while in twrp. HTH
Click to expand...
Click to collapse
This was the solution, however, along with something else.
The phone only charged correctly in TWRP, so I advise that. Definitely uninstall magisk so it doesnt patch other installs (I've noticed its installer gets called every time I flash a rom). I still had bootloop so I assume all my hard-resetting didnt help. I got it to fully boot on Bliss, but since I kinda miss Lineage I may return to it later today. (I love my "0% brightness" and blue light filter among other lineage features).
It's been a few months but it would either get stuck in the "Galaxy A36" screen or during the "SAMSUNG" screen and after some time just reboot itself on its own, like again and again. A single time it actually went into the OS but crashed after about 15 seconds and never did the same thing ever again. Since then it's been really unpredictable. Sometimes it turn on, sometimes it doesn't react, no matter what kind of buttons you push. Not being able to see the battery state doesn't help either.
Got this phone from a coworker. He's not the type of person to fiddle around with the system, so he didn't try to install a different firmware or anything. I can imagine something went wrong while updating (when did it last get an update though...) or while installing some kind of app or catching a virus. Or maybe the motherboard is just fried, that would be my guess actually.
So, what did i try next? Recovery mode... it seemed to be loading something and crashed shortly after. Next up i tried getting KIES and Smart Switch to work with it, but no response. Got the USB drivers atleast and ODIN connects with it. Tried flashing it with the original firmware. For some reason it failed the first couple of times (i've been reading battery has to be atleast 50% for it to work) but a day later after charging for long time it "worked" and shown me a green PASS. However it still didn't boot up, no matter how long i waited.
Tried recovery mode again but it just shows me a passed out Android man, lol. Tried booting up and sometimes got some messages in red like "Custom binary blocked by FRP lock" and "Recovery is not seandroid enforcing" whatever that means. I know ODIN has some more options, to wipe internals but i'd rather save everything on there. Running out of ideas here. Anyone?