Question Bootloop - POCO M3 Pro / Redmi Note 10 5G

gonna make this short cuz I'm tired rn but my phone keeps bootlooping. if I connect to WiFi it crashes INSTANTLY this is just a big pain in the butt since my bootloader is locked. can someone help

Related

Stuck at padlock screen then reboots into recovery

i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.
prelude91sit said:
i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.
Click to expand...
Click to collapse
Dear Brother !!
This same thing happened to me!!
I looked everywhere for an easy solution BUT THERE IS NONE !! Yet.
The reason why is because there are no easy "Odin back to stock files" yet is because at&t is a fn a-hole and locked the bootloader !!
I brikt my shıt about 4 days after I brought it home from costco.
I combed through the interwebs for the 48 hrs straight like a mad tweaker!! because of course this is our 800 dollar babies we're talking about !!
I kept getting the same error message as you are mentioning about the kies update connect your pc blah and so I tool it back to costco and played dumb and said that I got a notification to update and clicked ok and it did some stuff and "now its stuck on this screen with some error??" .. the lady at the kiosk looked it up and down and said someone else had come in last week with the same error message . LoL !!
I walked out of there with a brand new baby !!
Maybe you can do the same thing? Just hoping you are within your return timeframe.
your last but definitely not last worst case scenerio option is to stick your sim card in another phone and wait till someone from our awesome family here finds away around/through that damn bootloader and drops the beautiful Odin+files to give new birth to your 5.7 beast of an angel !!
Hope this helped in any sort of way. Good luck dear Brother!!
Please let us know how it goes. I think there are many brothers on here in the same predicament.

Having trouble with the N Preview.

So, I've been running the N Preview since just after finding out that there was a beta program to join, about 5 days ago, give or take. 2 days ago, my phone's wifi started acting up. I put it down to go to sleep and it was fine, and I woke up the next morning and found out it was constantly disconnecting, shutting off on it's own after I just turned it on, and the wifi hotspot list was glitching out, flickering, and connecting/disconnecting rapidly to my home network. About an hour ago, I decided that I had had enough of it disconnecting while I was streaming content (for whatever reason, my house is just out of range of the T-Mobile LTE cell tower for this area, or I'd be streaming it from that and not worrying about the wifi), and made the decision to do a factory reset to see if it would fix the glitching. It seems now that that was a mistake, as it's been stuck on the Erasing screen for about an hour. Not sure what to do at this point. Any advice and help would be greatly appreciated at this point.
[Disclaimer: I am fully aware that this software is still in beta, and that things will be broken and/or not working, and that it was not recommended to install on daily driver devices. However, what's done is done, and I'd like to have my phone working again. So please refrain from scolding/harassing me about any of this.]
What do you mean by 'stuck on the erasing screen'?
Slender Troll said:
So, I've been running the N Preview since just after finding out that there was a beta program to join, about 5 days ago, give or take. 2 days ago, my phone's wifi started acting up. I put it down to go to sleep and it was fine, and I woke up the next morning and found out it was constantly disconnecting, shutting off on it's own after I just turned it on, and the wifi hotspot list was glitching out, flickering, and connecting/disconnecting rapidly to my home network. About an hour ago, I decided that I had had enough of it disconnecting while I was streaming content (for whatever reason, my house is just out of range of the T-Mobile LTE cell tower for this area, or I'd be streaming it from that and not worrying about the wifi), and made the decision to do a factory reset to see if it would fix the glitching. It seems now that that was a mistake, as it's been stuck on the Erasing screen for about an hour. Not sure what to do at this point. Any advice and help would be greatly appreciated at this point.
[Disclaimer: I am fully aware that this software is still in beta, and that things will be broken and/or not working, and that it was not recommended to install on daily driver devices. However, what's done is done, and I'd like to have my phone working again. So please refrain from scolding/harassing me about any of this.]
Click to expand...
Click to collapse
Is your bootloader unlocked? If it is, just reflash the latest M image.
chapelfreak said:
Is your bootloader unlocked? If it is, just reflash the latest M image.
Click to expand...
Click to collapse
Or un-enroll from the android beta programm and the latest public stock firmware will be installed by OTA if the bootloader is locked.
gee2012 said:
Or un-enroll from the android beta programm and the latest public stock firmware will be installed by OTA if the bootloader is locked.
Click to expand...
Click to collapse
True, but I've read some people not getting the ota after unenrolling. I'd rather just do it myself since the first thing I did was unlock the bootloader lol either way the phone is going to get wiped. I hope the OP phone doesn't get borked because it hung up on factory erasing the phone, and his bootloader is locked
chapelfreak said:
True, but I've read some people not getting the ota after unenrolling. I'd rather just do it myself since the first thing I did was unlock the bootloader lol either way the phone is going to get wiped. I hope the OP phone doesn't get borked because it hung up on factory erasing the phone, and his bootloader is locked
Click to expand...
Click to collapse
Aah oke, got my rollback OTA last week in a minute or so
Ok, so just woke up and it seems to have shut off. Turning the device on now...
And it seems to have successfully reset. It's currently on the setup screen, and I'm going through it now.
And for the moment, the wifi seems to have been fixed, at least for now. Not sure if the device is on N or Marshmallow though, but we'll see.

I think i bricked it lol

Long story short my Desire 510 decided that it wanted to reboot its self constantly. Yes i was annoyed but i think i done diddly messed up. I tried flashing new roms and it wouldn't work. In TWRP i think there is a option to revert image to stock or something along those lines. I tried that in a desperate attempt to fix it and it stayed the same for some time but then after an hour or so and it wouldn't even turn on. I cant even get into TWRP and its not responding to anything. This is probably frustrating to the pros on here and im sorry in advance but if i can have any help i appreciate it completely.

Marshmallow OTA update failed

My S5 got the update this morning, it keeps failing at 92% on update and looping. I can't even get to recovery console holding down power, volume and home key. What should I do, my phone was paid off already. I don't know if AT&T will give me a new one because their update screw it up or is there something I can do to restore it? :crying:
Your best bet is probably to just take it in and ask them about it. Unless something is terribly wrong, they may be able to get it to update properly. You can also try just leaving it to try on a loop and hope it sticks eventually. I've had to try to update a half dozen times before it stuck before. Make sure your battery is sufficiently charged, as well. They don't like to update as much with less than 70% charge.
I was able to get into Odin Mode...it says Downloading Do Not Turn Off target!!. Not sure what is downloading but can I do anything to restore it? Maybe there is some hope before I have to get another phone.
I'm so happy, I fixed it...thank god for XDA, just had to do some digging around the forum. I try http://forum.xda-developers.com/att...x-samsung-s5-att-sm-g900a-lollipop-5-t3305497 which got me stuck at the logo screen then I did http://forum.xda-developers.com/att-galaxy-s5/general/galaxy-s5-android-version-6-0-1-t3419016 which got me back to 5.1.1. Atleast I have a working phone now. Honestly I had no clue wtf I was doing but I thought about trashing the phone and getting a S7.

(Problem) S5 G900A keeps restarting

Hi guys. This issue just started happening a couple of days ago, it started when I was playing games (phone wasn't hot) then it turned off by itself. My battery was still at 80% so I turned it back on, after it started saying "starting apps" it turned off again and the phone is now constantly rebooting. It doesn't seem to be bricked at all as it sometimes boots to the menu but when i start tapping on an app it shuts off and does the constantly rebooting issue again. It could be a hardware issue which means I'm gonna need to send my phone to the service center for a repair but one thing that makes me think there could be a way of fixing this without paying a technician is, when i boot to download mode, it doesn't do its constant reboot issue. I was even able to flash a firmware via Odin but when the phone started to boot after firmware installation, It did the spontaneously rebooting in the middle of the boot process again. If any of you guys have any idea on how to fix this or if there's even a way to, Please help me. Thanks! Cheers!
junnelle said:
Hi guys. This issue just started happening a couple of days ago, it started when I was playing games (phone wasn't hot) then it turned off by itself. My battery was still at 80% so I turned it back on, after it started saying "starting apps" it turned off again and the phone is now constantly rebooting. It doesn't seem to be bricked at all as it sometimes boots to the menu but when i start tapping on an app it shuts off and does the constantly rebooting issue again. It could be a hardware issue which means I'm gonna need to send my phone to the service center for a repair but one thing that makes me think there could be a way of fixing this without paying a technician is, when i boot to download mode, it doesn't do its constant reboot issue. I was even able to flash a firmware via Odin but when the phone started to boot after firmware installation, It did the spontaneously rebooting in the middle of the boot process again. If any of you guys have any idea on how to fix this or if there's even a way to, Please help me. Thanks! Cheers!
Click to expand...
Click to collapse
Try flashing the experimental firmware from the rooting guide, and if that doesn't work then it is most likely a hardware issue, and I have a strong suspicion that it is.
If you have an external SD card, remove it and see if problems persist. Honestly that sounds like a firmware scrambled.

Categories

Resources