I have a RN5p which I bought from China. It was running the global ROM.
I bought it 3 months ago and until now it was working fine.
Yesterday I turned on USB debugging and tried to install ADB, but all I got was "ABD is not a recognized command" on my PC and then I assumed there was some issue with my PC and I unplugged my phone and turned off USB debugging (I used this method: https://www.xda-developers.com/insta...s-macos-linux/ and I never managed to get past step 4 cause powershell was screwing me over).
6-8 hrs later my phone's screen froze and I had to force reboot it (hold pwr button for 10s). Once it restarted it was working fine, but then it froze again, and this time it started to boot loop, never getting past the MI logo, sometimes the android with the 3 dots would show, but it usually just remains there or freezes and then reboots.
After like 15 reboots, I managed to reach the lock screen and unlock the phone and worked fine for 30 mins then froze again.
It took even more reboots this time to get it to boot but same thing, froze after sometime.
Now sometimes it doesn't even manage to get past the lock screen, just freezes and reboots.
Additional Notes: I highly doubt that this boot loop is bcoz of ADB as I never installed it on my phone
I checked online and my phone is running the offical international rom(checked on the mi website)
My bootloader is locked( tho I did unlock the oem unlocking setting for 5 secs just to see what happened and then locked it again, but this was at least 6 weeks ago)
Out of the 4 times I managed to get my phone running normally, it froze 2 times while I was watching Youtube and 2 times while it was locked
Running miui 10.0
I would love to have my phone back to normal
All help is appreciated.
It just turned on (while I was typing this) and I allowed OEM unlocking. I think it will be easier this way. And now its back to boot looping.
Related
Help! my phone freezes and reboots.
ATT phone
Followed the GladRoot method for rooting. (worked fine used it for a day)
Installed GingerBlur 1.1 (Used for half a day then problems started)
Phone was about half battery so I stuck it on the charger.
I come back an hour or two later and the phone has the red Motorola dual core logo frozen on screen, phone was pretty hot.
Took out power and battery and waited for phone to cool.
Re-installed the battery powered up and the phone went into a boot loop (Sometimes with flashing indicator other times without once with a solid red).
Powered off and waited about 15 minutes.
Tried again, same thing.
Powered off removed sim and SD and did a SBF flash with 1.2.6
Flash completed without any problems, and phone booted, powered off and reinstalled sim.
Still having problems. Phone boots now but every 2-3 minutes it freezes and reboots >_< I managed to get through the motoblur setup and tried doing a factory reset. The process completed ok but I'm still having the freeze reboot problem.
Hi guys,
first of all thank you for taking your time and reading through this. I'm not completely new to android, nor using fastboot and recovery. I flashed a few phones over the past years I even resurrected bricked ones. However I have no idea what is happening to my Honor 8. One thing to mention, it's the latest Nougat update, and a STOCK ROM.
It all started this afternoon. The phone suddenly reboot while using it. After that, the android screen came on, then Honor animation and.. freeze. Completely. I had to reboot using the long press method since it was stuck between the bootloader and the rom itself. It started up ok after that.
An hour passed, and while I was typing a message, it froze again. I could go back to home but the phone was really slow. After opening up Messenger again, it froze completely. Had to restart again with the long-press reboot method. It started up ok, entered the sim pin and upon entering the screenlock code it froze again, completely. Long-press reboot, again.
Since then, the phone won't boot. It gets stuck every time on "Honor powered by Android" for about a minute, then it reboots itself. I even got some weird green screen with a blue and a red rectangle, but that just stopped after a few reboots.
I mentioned that I know how to recover and fix stuff when something acts weirdly, but that's not the case, I can't do ANYTHING. No fastboot, no recovery, no button combinations, I can't even turn off the phone. It just keeps rebooting on and on, and yes, the battery will eventually die, but I have no access to any recovery options. I even tried dload but no luck.
It's still under warranty so I can send it back but I just rather fix it at home (without taking it apart), because I don't want to wait 3 weeks to get fixed. But it seems like that is the only option right now, I have never ever seen anything like this happen.
Any help or comment is appreciated. Even if it's not possible to do it at home (hardware issues?), I am really curious what can be the cause of this issue (damaged rom, filesystem permission issues?).
Thanks.
Good morning to alle? for now,
So now to my problem.
I had a lot of time yesterday and wanted to root my new Mi9 and install TWRP to adjust my device a bit. It all worked fine until the phone started into a boot loop and stopped working. Of course I booted into TWRP and reset the phone...without success. Then I deleted everything that was to delete and tried via. Fastboot Miui 11.0.5, which didn't really work. With Miui 10 it worked then and I could set up the device again. Then I thought to myself that it might now work to install Miui 11 via Fastboot (Of course it didn't). That was at 0:30 at night, so I was tired and went to bed. I switched off the mobile phone, the Fastboot mode, so that the symbol doesn't burn into the screen. This morning, about 20 minutes ago I wanted to start a new attempt, so I pressed the power button...and nothing! I also tried to press for about 20 seconds...but without success. I also charged the device for a short time, I noticed that the LED does not light up during charging. But I can't imagine that the device is empty, because yesterday it had 100% battery. Now it is hanging on the charger. I also tried to start the phone via Minimal ADB and Fastboot, didn't work, because no device was detected on the PC.
I hope that is still somehow to save, I was perhaps a little overconfident there. But I think I am in good hands here and a solution will be found.
My Poco F1 is unlocked and I recently rooted it with TWRP and Magisk for trying the Substratum theme engine. Yesterday I was texting over WhatsApp and the phone restarted. Restarted as in the POCO logo was visible for 4-5 seconds and the restart again. This went on. I tried going to TWRP but it wont stay for more than a second on TWRP screen before restarting. Same with FastBoot.
So I left the battery to drain and to start again after charging. But not to my surprise same repeated. Wont detect even in adb for the phone gets restarted every 10 seconds. Can someone help me out here?/I donot want this quarantine to kill me already.
My V30 worked perfectly for years, Android 9 running, had it rooted using the sticky guide, and Magisk installed. I had just boarded a plane on Monday, sat down, and noticed the LG screen with the bootlaoder unlocked message warning you always see when rebooting. Then it just reboots again, I see the LG logo, the bootloader warning message, reboots again after about a minute.
I also could not turn it off because it would just turn itself right back on, and go back into the loop. Eventually the battery drained and it died. When I got home, I held the power button and the volume down then plugged in to go into I think it's recovery mode, which worked, but my only options were to flash or reboot (I think, my memory is fuzzy). Then I ran LGUP and it detected my phone, but said it can't load the model from C:\Program Files\LG Electronics\LGUP\model\com.
Next I tried running adb commands against it which is working, however I"m getting back LGUS9983322eaa5 unauthorized which I don't understand because I clearly had debugging turned on (which I think is what causes that message?)
Any ideas on what to try next, or what could have happened? I had not installed anything new. This data recovery company called Drivesavers quoted me 900 to get my files off, but I have backups, and there's nothing on the internal memory I can't live without.
Thanks for your help!