Hi,
I got a Xiaomi mi 11 and Installed the Pixel Experience ROM. Everything runs smoothly until today I accidentally pressed "install system updates" inside device setting.
Now the device stuck in a loop like in the video (3 hours already) . It's not my video but it shows the same thing.
The powerbutton isn't working, and when I tried format the phone using ADB, it gave me "ADB unauthorized".
Can anyone please help me?
Related
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.
Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.
I need help. My K01A tablet is stuck on the Asus boot logo, Droidboot works ok, fastboot also, my main issue is that I can't go into recovery 'cuz it says "installing system update" and then "error" in about 1 or 2 seconds...
That's about it. Cannot flash another FW image, and it's so frustrating. :-|
Any ideas, please?
hi
did you manage to solve this problem ?? thks
I have a redmi 4x and i tried flashing pixel experience rom on it but was not successful in doing that . Also didn't take any backup . And i was struck in the twrp recovery for a couple of days . Then i flashed the miui stble rom through my sd card and didn't get any error . But when i was going to boot it said "No OS installed" . So i thought of having a backup before booting for the first time and as i tried having a backup then phone switched off and showed no signs that it was working . It didnt even boot and was bricked . So i thought it was hard bricked . But after a day and some charging the notifictaion light light started working on charing and also phone vibrated on pressing down the power button . But when i try to boot it the phone shows some backlight but nothing on the screen and it goes off . Is it Hard Bricked or Soft Bricked ?
Bhagyesh2491 said:
I have a redmi 4x and..........
Click to expand...
Click to collapse
I don't have this device but, you may be able to obtain some member guidance within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3800104
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
Showing "No OS installed" it did happened with me when few months back i flashed first Global beta MIUI 10, the installation went perfectly good with message "No OS installed" it was strange when flashing was went right.
after rebooting it to system it was stuck in bootlogo. i do not know why it said "No OS installed" despite installation went perfect.
at first i did checked if system is checked for boot or not in recovery(it was not) so i checked it and rebooted but it still refused to boot and keep getting stuck in bootlogo but after flashing latest Redwolf treble recovery at that time solved issue for me(currently using redwolf recovery) and i was able to boot into system and later other ROMs.
anyways this solution worked for me "No OS installed". (writing this because it might help someone if they have same issue)
what is current state of your device? are you able boot in fastboot or recovery ? if any one of this works i would recommend you to flash if you are able boot into fastboot then flash latest stable Global MIUI ROM via Mi flash tools or flash latest treble supported recovery via fastboot.
if it isn't booting at all or it refused boot into any mode you might have to go for test point method to revive your device as you can see in above mentioned comment by xda recognized contributor's thread you can find test point method is mentioned by OP or here is link for it http://en.miui.com/thread-693884-1-1.html
you can also find video for the same on youtube.
proceed with precaution.
No it isn't booting at all . It is detected by my PC as a Battery but it shows it is android . Also notification light turns on after trying to charge it and it also vibrates . When i hold down the power button its shows some kind of a backlight but it doesnt boot . Is it hard bricked or soft bricked ?
Bhagyesh2491 said:
No it isn't booting at all . It is detected by my PC as a Battery but it shows it is android . Also notification light turns on after trying to charge it and it also vibrates . When i hold down the power button its shows some kind of a backlight but it doesnt boot . Is it hard bricked or soft bricked ?
Click to expand...
Click to collapse
I am not sure if it is hard bricked or soft bricked.
It detects on computer and doesn't shows anything on display.
Try connecting to PC and see if detects on Mi flash tools if it does then flash latest stable ROM through it.
Try using mi flash tool. This happened to me too, tried flashing pixel experience pie on mine and bricked it. Couldn't even access the twrp and my phone was stuck on fastboot screen. Luckily I had mi flashing tool and knew how to flash official MIUI rom through it. I did a clean flash of MIUI rom and it pretty much reverted the phone back to original conditions but few hours later i re installed twrp and went back to pixel exp OREO.
Do we get a ota update from pixel experience oreo to pixel experience pie rom ?
Have you tried to boot into the fastboot mode?
if yes then flash miui stable rom via mi flash tool
Carefully Read instruction bro :----
PC required windows 8 or Up..
1-Firstly installed Adb
2.twrp installer for redmi 4x zip
3-Extract all file in zip
4-Click .bat file and follow instruction of command window
5-twrp successfully installed in your device automatic device boot in recovery mode
6-Sd card inserted do you want flash ROM by TWRP
7- FLASH do you want any thing ..
8- Lazy Flasher is Compulsory flash
9 - enjoyed ROM without Bug
I recently installed Magisk Manager on my phone. and after a few days, my phone got stuck on a bootloop. I tried flashing an official jasmine ROM but failed. I tried to factory reset and then my phone booted up. And then it showed me "System UI has stopped working" I tapped on wait and then it turned black. Now it can't get past the Android One logo.
Messing with system files always a big risk :/
Try to boot into EDL and than flash the original rom with mi flash. Choose the clean all option.
You can find tool ( or fastboot commands ) in A2's xda forum to boot into EDL
Good luck!
Sent from my Xiaomi Mi A2 using XDA Labs
mrJoedadriane said:
I recently installed Magisk Manager on my phone. and after a few days, my phone got stuck on a bootloop. I tried flashing an official jasmine ROM but failed. I tried to factory reset and then my phone booted up. And then it showed me "System UI has stopped working" I tapped on wait and then it turned black. Now it can't get past the Android One logo.
Click to expand...
Click to collapse
can you boot in fastboot?
I got it working agian. Thanks
Hi there!
I'm stuck in a bootloop with dm verity error message. Phone turns off and on continiously. I'm not able to get into recovery / fastboot using button combo :\.
How I got into this:
I tried unlocking my merlinx, but ... didn't want to wait 7 days with the official tool. So I used https://github.com/bkerler/mtkclient and did the "unlock bootloader" procedure. Phone booted fine, though there was dm verity error message and I had to press the power button to continue booting.
Then I followed this guide: https://forum.xda-developers.com/t/...roid-for-redmi-note-9-merlin-merlinx.4333179/
Then, I downloaded shrp recovery, crDroid rom, gapps and firmware. Booted in fastboot, did `fastboot flash recovery shrp.img` and booted to recovery. Then I took backup of IMEI, wiped the data and saw an interesting builtin zip for dm verity disabling. Flashed that, then proceeded with custom rom installation. All went smooth.
I booted the rom. There was no dm verity message, nor Redmi logo, but phone booted normally. If I remember correctly, I didn't have to press the power button to continue (there was no message about it.)
Proceeded with phone setup. Camera didn't work ... Tried rebooting, once again no Redmi logo but phone boots fine. "Ok then, I'll try a different ROM and hopefully camera works". I choose "advanced restart -> recovery" and phone turned off. Screen turned on (like you'd expect) but then turned off again. Again, no Redmi logo or dm verity message.
And now the phone does that. Screen turns on and off after ~30 seconds.
My first thought was that bootloader got locked again somehow. Using the mtkclient tool, linked above, I relocked and unlocked the bootloader.
There's still no Redmi logo present, though I can see the dm verity message again.
What have I done wrong? I know it could be the impatience with 7 day waiting, but since phone booted fine 2 times ..? Was it the recovery dm verity zip?
Does anyone know what to do here? I'm able to use mtkclient tool. Button combos for recovery and fastboot seem unresponsive ...
Thank you very much.
Hello.
I did exactly same think with my Redmi Note 9 and I can say you hard bricked your phone. But don't worry there is a way to solve it. You need to follow vagelis199's guide exactly and there should be no worries. It is not so easy but not so hard too.
Sending this from my Redmi Note 9 with android 12 R vendor.
I'm not so knowledgeable about this part of tech but crDroid guide is outdated in my opinion and it should be replaced with new one, that is a big problem and should be considered. I installed Android 12 S vendor, most recent one from my android 11 MIUI and it bootlooped, after installing with Firmware of Global MIUI it was hardbricked. So I am waiting a little and trying to install most resent crDroid with EU MIUI Firmware which very recently was published with MIUI 13 Android 12 EU. I am not sure why it didn't work because EU and Global are very similar.
Thank you, will try that.