Help! bootloop + no command error - Android Q&A, Help & Troubleshooting

I have Blu Studio 6.0 HD, that got stuck on bootloot, i did: (chronological order) (it was rooted but without a custom recovery)
-factory reset (still on bootloop)
-wipe cache (still on bootloop)
-tried to sideload stock rom through adb: it didn't allow me (not even load the file)
-flash stock rom with sp flash tool, it seemed to work but NO: at this point was still on bootloop but when i enter to the recovery it said no command + screen was doing a strange blinking while "booting":
original recovery menu changed, including volume navigation. (at first I could go up and down with volume buttons and select with power button, now a navigate with volume down button and select with volume up, power button appears/disappears recovery menu).
-tried again sideload stock rom thru adb, it loaded and reached 100%, and the phone keeps aborting installation.
-tried to install CWM thru adb (there's no TWRP for this phone or any BLU phone), adb still works but when I tried to get on fastboot mode it says error: closed (adb reboot bootloader command)... (I think I should've done this at first place, but didn't know, so...)...
Is there another way to install a custom recovery?? so I can flash the rom properly.. HEEEEELP!! (don't know why it got stuck on bootloop at the beginning, this is my mom's phone and she didn't know what even happened)

Related

[Q] [Brick] [Lanix Ilium x200] Flashed twrp.img as boot image in Flashify

Hi all!!
I have a Lanix ilium x200, which is a legacy device running 4.4.4. I rooted it with iRoot, and I followed an online tutorial I found to try to get twrp. It told me to download an unofficial flashify by Christian Göllner and flash twrp.img as a boot image. I did that, but halfway, I realized that didn't make a lot of sense, so I stopped it, killed the app, then flashed it as a recovery. Then, I didn't think much about it until my phone ran out of battery.
I tried to boot system, and it flashes white for a second, then nothing. Same thing with recovery (If I press volume up + volume down + power button, it gives me the option to boot system of recovery). I tried executing fastboot commands in the vol up + vol down + pwr mode (I can't tell if it's bootloader or fastboot mode or even either of then), but it isn't listed in fastboot devices, and it quickly (attempts) to boot into system. I tried using SP flash tool to flash stock recovery and boot.img, but it won't detect the device either. The phone just shows the battery charging indicator (even if I try booting it, it just flashes white and goes back to the battery indicator), and SP flash tool doesn't detect a thing (yes, I tried installing the drivers). Does anyone have an idea on how this can be fixed?
Thanks!!
TL;DR rooted and flashed twrp.img as boot image and as recovery in flashify. Cannot boot system or recovery. Not detected by SP Flash tool
Rip.
Sent from my SM-G386T using Tapatalk
Got any advice to say?
[SOLVED]
Nevermind. I fixed it myself. Turns out I didn't install the correct drivers for SP Flash tool. This time, it detected my device and flashed to my phone perfectly. I'm now running stock 4.4.4 without any problems.

Galaxy A40 - Stuck in Bootloop after flashing wrong ROM, can't enter Recovery

Hello XDA Community,
I just got a Galaxy A40 (SM-A405FN/DS) and flashed TWRP.
Everything was going well, so I decided to try to flash an unofficial LineageOS GSI.
I followed some instructions I found on a website:
- Wipe Vendor, Dalvik/ART cache, Wipe Cache, Data, System, Internal Storage using TWRP Advanced Wipe
- Flash Image to System Partition (Used: lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img.xz)
- Reboot & Pray
I am now stuck in a bootloop, sometimes I am able to start TWRP, but I have tried to flash other images but wasn't successful.
(Loop: Bootscreen -> Warning (Press Power Key) -> Bootscreen -> Blackscreen (Reboot))
I am currently downloading the stock image.
How can I enter recovery mode? Is there anything else I can try?
Got the same goal, installing a Lineage GSI ROM. But... I got stuck in a bootloop just like you after flashing TWRP.
You have any tips getting out of it?
Solution: Okee, I drained my battery first. Then I pressed volume up and down together and connected it to my pc. This way I got it in download mode. (thank god!)
So i managed to get into download mode after being stock in restart loop by holding off button. When screen got black, i plugged my phone into my pc and pressed volume up and down buttons. It worked. I am a genius.
Anyone managed to get a custom ROM to work on that device ?
welpitwentwrong said:
So i managed to get into download mode after being stock in restart loop by holding off button. When screen got black, i plugged my phone into my pc and pressed volume up and down buttons. It worked. I am a genius.
Click to expand...
Click to collapse
YOU ARE AN ABSOLUTE LEGEND THX ALOT

Magisk 21.2 bootloop

Hi everybody,
I tried to install Magisk 21.2 on my stock Oreo rom with Magisk 20.4 already installed. I've used the recommended method for installation in Magisk Manager, and I left the AVB/dm-verity option unchecked. It resulted in a bootloop.
Before updating I did a backup of the boot partition, so I could restore the previously working Magisk 20.4. Now I have two questions:
1) Is there something else I should do other than restoring the boot partition after a bootloop?
2) Is there a way to install the new Magisk or should I just dismiss the update notification?
Happened to me As well on my G6.
I had to reinstall the rom. good thing i had backup.
I've downloaded the zip file of Magisk 21.2 and flashed it with the rom after wiping almost everything, and even tried flashing a different rom with it (I'm using stock A9)., but it seems it resulted in a bootloop every time.
There is a new magisk 21.3 from yesterday, which i hope fixed those issues as i am not planning to go though that hassle again.
I tried the new 21.3, and still it causes bootloop, at least I'm glad I'm not the only one.
DannyynnaD said:
Happened to me As well on my G6.
I had to reinstall the rom. good thing i had backup.
I've downloaded the zip file of Magisk 21.2 and flashed it with the rom after wiping almost everything, and even tried flashing a different rom with it (I'm using stock A9)., but it seems it resulted in a bootloop every time.
There is a new magisk 21.3 from yesterday, which i hope fixed those issues as i am not planning to go though that hassle again.
Click to expand...
Click to collapse
It happened to me, same setup as the OP and did the direct install method from Magisk Manager. My phone is stuck in bootloop at the triangle/! scrren and I can't access TWRP via the normal buttons manner. Also, can't get any ADB to detect the phone (I am using a new PC that probably never connected to this phone despite loading ADB, drivers, etc. - I am going to resurrect the previous PC to see if can connect).
May I ask how you restored the saved boot image? via TWRP restore?
I've rooted and played with many ROMs on various android devices, but I'm no expert and this one has me stumped.
Yes, I did a backup of the boot partition before flashing Magisk and then I restored using TWRP restore. It's not the first time that a new Magisk version causes bootloops on the G5, to I was prepared this time.
By the way, if you don't have a backup, you may try to flash the Magisk Uninstaller zip, and without rebooting, the old Magisk 20.4. In theory it should do the job.
tremalnaik said:
Yes, I did a backup of the boot partition before flashing Magisk and then I restored using TWRP restore. It's not the first time that a new Magisk version causes bootloops on the G5, to I was prepared this time.
By the way, if you don't have a backup, you may try to flash the Magisk Uninstaller zip, and without rebooting, the old Magisk 20.4. In theory it should do the job.
Click to expand...
Click to collapse
Thanks, But how to access TWRP or flash the zip? I haven't found any technique to access recovery (Power+VolDn doesn't work, only allows Factory Reset screen). How to access Fastboot to use ADB (I assume that would be the technique)? I did manage to bring up some odd screen that had a two-line message about fastboot by, I believe, using Power+VolUp.
For clarification this is what I now have:
Phone off (remove battery). Insert battery. Press power button until brief vibrate (1-2 seconds). Release power button. Triangle with "!" displayed "Your device cannot be checked for corruption. Lock the bootloader. " screen displays for about 3 seconds, screen goes black a second or less. Back to the previous warning screen.
Press and hold Power button + Vol Dn acts just like the above, but if I press power + press/release/press/release... I can get the factory data reset (Yes or No(Exit) options) - I haven't accepted that.
I've tried connecting PC to the USB port and two things: as soon as I connect it, the phone powers on and does the looping again. My PC doesn't see the phone in Device Manager and ADB won't list it. I did (one time) manage to bring up the two-line fastboot message at the top of the screen.
BTW: when it first tries to power on, before the Lock the bootloader screen, there is a small, scrambled white area (text?) at the bottom of the screen.
I don't know when was the last time (if ever) I attached to the phone via USB (probably a few years ago when I initially installed TWRP). Haven't really done much other than upgrading TWRP (via TWRP), Magisk (via Magisk Manager), and the very occasional nandoid backup via TWRP (I have one from 3 months ago).
Any further assistance or info would be greatly appreciated.
To access TWRP, turn off the phone, then keep pressed Volume down+Power and once you see the LG logo release the power button and press it again. The phone should ask you if you want to reset everything: if you press yes and then confirm, you will:
1) Enter in TWRP, if you have TWRP installed, or
2) Erase the whole internal memory, if you don't have TWRP installed.
As you already have TWRP installed, it should be quite safe to go through the reset procedure, or at least that's what happens on my phone. If you don't want to take the risk, you can still use fastboot to boot a TWRP image you have on the pc, just write
Code:
fastboot boot <path_to_twrp.img_on_pc>/twrp.img
To do so, you first need to boot into fastboot: you can just turn off the phone and, keeping the Vol- pressed, connect the USB power cable to the phone. It will boot into fastboot.
One more method could be booting into download mode (Vol+ and connect the USB cable) and flashing an original firmware using LGUP, but that is way too much for a phone that already has both TWRP and fastboot accessible.
tremalnaik said:
To access TWRP, turn off the phone, then keep pressed Volume down+Power and once you see the LG logo release the power button and press it again. The phone should ask you if you want to reset everything: if you press yes and then confirm, you will:
1) Enter in TWRP, if you have TWRP installed, or
2) Erase the whole internal memory, if you don't have TWRP installed.
As you already have TWRP installed, it should be quite safe to go through the reset procedure, or at least that's what happens on my phone. If you don't want to take the risk, you can still use fastboot to boot a TWRP image you have on the pc, just write
Code:
fastboot boot <path_to_twrp.img_on_pc>/twrp.img
To do so, you first need to boot into fastboot: you can just turn off the phone and, keeping the Vol- pressed, connect the USB power cable to the phone. It will boot into fastboot.
One more method could be booting into download mode (Vol+ and connect the USB cable) and flashing an original firmware using LGUP, but that is way too much for a phone that already has both TWRP and fastboot accessible.
Click to expand...
Click to collapse
My phone never got past the bootloader screen (i.e. never got to the LG logo screen). When I booted into fastboot mode with the Vol+ button, I could issue commands like "fastboot devices" which would return that it saw my phone, but attempting to use fastboot to reload TWRP didn't work - some say the LG fastboot has been neutered.
Eventually, I had to indeed use LGUP/Uppercut and reload the stock Oreo and the phone came back up. BUT attempting to reboot into bootloader not only didn't come up in TWRP, but I got the little dead Android image. I ultimately had to downgrade to OEM nougat, jump through a few hoops, and finally got TWRP installed. Then it was just a matter of restoring a backup or reflashing a newer ROM (I ended up loading lineage 16, no gapps, with microg etc.).
Somehow the magisk upgrade really trashed my recovery partition somehow (??). I've always made sure to have at least a couple of TWRP backups, but this time I was screwed royally when I couldn't access recovery. I forgot what an ordeal it was to get TWRP & root on this phone originally.
Thanks for your help.

[CLOSED] Am I going Mad :-)

HI,
I inherited this phone. ( D6503 )
Fixed a few hardware problems, now looking at software improvements.
I have unlocked the bootloader , but for the life of me I cannot get a recovery on this phone??
I have previoiusly done flashing on nokia, motorola and Nexus, but I am having no luck with this sony
I am able to connect using ADB, and can get to fastboot, but it stops there.
Issuing '' fastboot boot twrp.img'' ( to try and boot temporarily to twrp ) gives me a blank screen.
issuing ''fastboot flash recovery twrp.img'' does the same.
I cannot get a bootloader screen at all, even using the key combinations.
I cannot boot any recovery at all.
Is there someone here who can put me out of my misery
I am not looking to perform anything fancy, I just want to flash the latest lineage to see how it performs
Many Thanks in advance.
pootler.
Anybody???
I have rooted the z2 by dropping down to 5.11, installed the twrp app, then flashed recommended version of twrpl
Then when I power off the phone, and press the power and volume down buttons, instead of booting into twrp after 7 or so seconds, it just reboots after abour 2-3 seconds???
Can anybody help?-------please
I have even tried rooting , then installing twrp by either 1) fastboot or 2) twrp app.
I then installed NDR utils, to reboot to recovery - it still reboots to main system??
HEEELLPP !
I also tried flashing TWRP with 1) fastboot and 2)the twrp app,
I then installed NDR utils ( i have root ) , and it still wont boot into recovery, just straight into system???
HEELLPP!!
Thread closed on request of OP @pootler

Switched ROMS (Evolution X -> Nusantara) -> NOW Bootloop

Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.

Categories

Resources